ChargingNear.me

For state, regional and federal staff

EV Charging Data for Agencies

Where public charging falls short along highways, which stations meet the federal NEVI minimums, how chargers hold up, and how the network grows. Free to use in plans, grant applications and reports, with credit.

Quick answer ·

What EV charging data can agencies get from ChargingNear.me?

As of November 4, 2026, ChargingNear.me publishes 18 free files on U.S. public EV charging, as CSV and JSON, rebuilt every day. They include 883 U.S. highway stretches where DC fast chargers are more than 50 miles apart, a NEVI check of 15,890 DC fast stations, and every fast charger on 6 Colorado corridors. Each has a version, the date its rows last changed and a “Cite as” line; a key-free API, an MCP server and a weekly file on request cover the rest.

Browse the files Email the data team

Which datasets are available, and what does each answer?

Grouped by the question they answer. Each title opens the file’s entry on our open data page, with its column dictionary, methodology, sources and changelog.

Where are the gaps between fast chargers on U.S. highways?

Which DC fast stations meet the federal NEVI minimums?

How reliable are public chargers, by network, county and corridor?

Where is every public charging station?

What are drivers reporting about stations?

How much charging does each Colorado county have, and how fast is it growing?

How do states compare on public charging?

Where are the fast chargers on Colorado's highway corridors?

How do we cite the data?

Each file has its own “Cite as” line: publisher, file title, version, the date its rows last changed, the link and the license. The version goes up only when the rows change, so a citation always points to the same rows.

Example, todayChargingNear.me. “U.S. highway charging gaps over 50 miles.” US EV Charging Open Data, version 3, November 3, 2026. https://chargingnear.me/data#us-highway-charging-gaps. CC BY 4.0.

License: our own files are Creative Commons Attribution 4.0 International (CC BY 4.0); station facts from AFDC are U.S. public domain. In the corridor files, rows sourced from Open Charge Map are CC BY 4.0 from its contributors; credit them too.

Can our systems pull the data automatically?

  • Stable file links. Every file keeps its address, such as https://chargingnear.me/data/us-highway-charging-gaps.csv, and is replaced in place each day.
  • Read-only API, no key. /api/v1/open-data/charging-gaps (filter by state, highway, minimum miles, designation), /api/v1/open-data/corridors/{corridor}/chargers for each of the 6 Colorado corridors and /api/v1/open-data/nevi-status (state, grade, network, highway). Each answer carries the file’s version, date and “Cite as” line. Up to 60 requests a minute.
  • MCP server. https://chargingnear.me/api/mcp offers the same as get_charging_gaps, get_corridor_chargers and get_nevi_status, for AI assistants and agents.
  • Catalog. /data.json is a DCAT-US 1.1 catalog of every file, for data.gov-style harvesters.

Station-by-station data, live availability and reliability history are in our Developer API, under its own terms.

Can we get a weekly file?

Yes. Tell us the files, the area (a state, a region, a list of counties or corridors) and the format your team uses, and we will send a weekly file on request. Write to reserve@winsparking.com.

How do corrections get back to AFDC?

Most station facts come from AFDC’s Station Locator, which we sync every day. When drivers or our field team find a station down, repaired, moved or listed with the wrong hours, access or price, the report becomes a row in one of three public files, each keyed to the station’s AFDC ID:

AFDC and agencies can join those rows to the Station Locator on afdc_station_id and fix the record at the source. Reports not yet reviewed by our team are marked unverified. Our station file keeps AFDC’s facts as AFDC publishes them, so a fix made at the source reaches it with our next daily sync. To report an error in one of our files, write to reserve@winsparking.com.

How is the data built?

Our methodology page covers the sources and refresh schedule, how duplicate stations are merged, the Working-Now Score, corridor matching, the NEVI test and the known limits. Every file is rebuilt daily (Daily 07:30 UTC).

Questions from agencies

Is this EV charging data free for government use?

Yes, for any use, with credit. Our own files are CC BY 4.0; station facts from the U.S. Department of Energy’s Alternative Fuels Data Center (AFDC) are U.S. public domain. No account or key is needed to download them.

How do we cite a file in a plan or report?

Copy the “Cite as” line shown with each file; it names the file, its version and the date its rows last changed. Today the highway gap file’s line reads: ChargingNear.me. “U.S. highway charging gaps over 50 miles.” US EV Charging Open Data, version 3, November 3, 2026. https://chargingnear.me/data#us-highway-charging-gaps. CC BY 4.0.

How often is the data updated?

Every file is rebuilt once a day (daily 07:30 utc) from our live database. A file’s version goes up only when its rows change, so a cited version always means the same rows. The refresh schedule for each source is on our methodology page.

Can we get a weekly file for our state or region?

Yes. Write to reserve@winsparking.com with the files, the area and the format your team uses, and we will send a weekly file on request.

Do the files include personal information?

No. They never include reporter names, emails, phone numbers, user IDs or IP addresses, or anything a driver typed in their own words.

Can our systems query the data without downloading files?

Yes. Three read-only endpoints need no key: /api/v1/open-data/charging-gaps, /api/v1/open-data/corridors/{corridor}/chargers and /api/v1/open-data/nevi-status. Our MCP server at https://chargingnear.me/api/mcp offers the same to AI assistants, and /data.json is a DCAT-US catalog for data.gov-style harvesters.

What does the NEVI check not test?

It tests ports, power and distance to a designated corridor only, not 24-hour access, payment methods, uptime or networking, and AFDC lists each plug’s top power rather than what four ports deliver at once. Every known limit is on our methodology page.

Who do we contact?

The ChargingNear.me data team: reserve@winsparking.com. Write for a weekly file, a question about how a figure was built, or an error in a file.