FlowsBook a callSign inCreate free accountSign up
Business and places data

How to get a list of EV charging stations in a city, district by district

Every public charger in a city as a table: operator, connectors, highest power and status, with the fast ones counted for each district you draw on the map.

Part of the guide Location intelligence automation

By the xMap team · · 5 min read

A useful list of EV charging stations in a city has one row per station with its operator, address, number of charge points, the plugs it takes, its highest power in kW and whether it was working when last reported. In xMap Flows the EV charging block builds that table for any city you name: draw the districts you care about, run it, and you also get how many stations, charge points and fast chargers each district has.

Who asks for this? Charge point operators sizing a city before they bid, councils checking where public charging is thin, fleet managers placing vans near fast chargers, property teams answering tenants, analysts writing a market note. Each needs the same table, cut a little differently. Below: what each row holds, how to cut the city into areas, how to read power and status, and where the register behind it is weak.

What each station row holds

FieldWhat it means
name, operatorThe station and the network that runs it
address, city, lat, lngWhere it is, ready for a map
pointsHow many vehicles can charge at the same time
connectorsThe plug types, such as CCS or Type 2
max_power_kw, fastThe highest power on site, and whether it reaches 50 kW
status, usageWorking or not as last reported, and public or restricted
last_verifiedWhen that status was last confirmed

The fields the EV charging block passes on for each station it finds.

Keep last_verified in any report. A station marked working that nobody has confirmed for two years tells you less than one checked last month.

Cutting the city into areas

Set Area of interest to the city, and EV charging to look in the Area of interest. Each area is searched from its middle out to its edge, up to 25 km, and only stations inside the area are kept. Up to 8 areas go in one run, and up to 500 stations come back, fast and nearest first.

A city name alone gives one big area and one big list. For a district view, draw the districts instead. Each drawn shape is searched on its own, and every station comes back with area, the name of the district it falls in. Drawing eight districts of a city such as Amsterdam, Lyon or Bangkok takes a few minutes on the map and is the step most people skip and later wish they had not.

Fast, ultra-fast and the rest

The Charging power setting keeps only stations that reach a level: 7, 22, 50 or 150 kW. The block calls 50 kW and above fast. Run it twice to see the shape of a city: once with any power for the full picture, once with 150 kW for the stations that matter to drivers on a long trip.

  • Slow and medium (up to 22 kW): car parks, offices, hotels, streets. Cars stay for hours.
  • Fast (50 kW and up): supermarkets, fuel stations, retail parks. Stops of about half an hour.
  • Ultra-fast (150 kW and up): main roads and hubs. Short stops on long trips.

A district with many slow points and no fast ones is a district where people charge at home or work and stop briefly elsewhere. That is not always a gap; it depends on whom you serve.

Counting by district

To get one line per district rather than one per station, ask a question of the station rows. The Data analyst block, asked "how many stations, charge points and fast stations are there in each area, and the main operator of each", works it out with a small program and passes on a table with one row per district. Sort and limit then puts the districts with the fewest fast stations first. Add xMap LLM set to work on the whole list, and it writes a short note on where the city is well served and where it is not, using only the figures it was given.

A made-up example

Say a city transport team wants a monthly view of public charging across six districts. The flow runs on the first Monday of the month, reads the six drawn districts and finds every station at any power. One branch counts them by district with the Data analyst; a second branch adds Only new, so the email lists stations that appeared since last month. The team gets two things: the table of districts, and a short list of what changed.

Where the list falls short

  • Private chargers at homes and depots are not in a public register, so a list of public stations undercounts all charging in a city.
  • Prices, opening hours and whether a bay is free right now are not part of the list.
  • Status is as last reported. A broken charger fixed yesterday may still read as out of order.
  • Each area is searched from its middle, up to 25 km, and one search reads the 200 stations nearest that middle; the step says when an area held more. A sprawling metro area is better drawn as several shapes.

For how this fits with other place data on a timetable, see location intelligence automation.

Questions

How many stations can one run return?

Up to 500 in all, fast ones and the nearest first, and up to 200 from each area searched. For a large city, draw districts so each area's stations come back in full.

Can I see which stations are new since last month?

Yes. Keep the station rows and add Only new after the EV charging block, with the flow on a monthly schedule.

Does the list show whether a charger is free right now?

No. It shows the station's status as last reported and when that was confirmed, not whether a bay is in use.

Can I count chargers around my own sites instead of districts?

Yes. Bring your sites in from My data and set the block to each incoming place, with counts, at a distance from 500 m to 10 km.

Templates that do this

Read next

More on business and places data · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.