United States/Charging Stations

From OpenStreetMap Wiki
Jump to navigation Jump to search

United States Electric Vehicle (EV) Charging Stations

In the United States, EV adoption is on the rise, and with it more EV charging stations. In OSM worldwide, we use the tags tagamenity=charging_station and tagman_made=charge_point to tag these elements. This page should serve as a reference for United States contributors interested in adding these stations.

Tagging

For tagging, elements that a tag can be placed on will be in the TagInfo boxes for each key/tag.

Required Tags (Choose 1)
Tag Usage in the United States When to Tag
amenity=charging_station Each station has a single (1) charging station node node or area area.
According to tagamenity=charging_station an area is preferred, but in practice nodes enjoy a much higher usage. Both are OK.
If you choose to mark the station as a node node, place it in the center of the station.
If you choose to mark the station as a area area, surround the area, including dispensers and parking spaces, of the charging station in a closed way.
man_made=charge_point Each station can have theoretically unlimited charge points (we call them dispensers in the United States.)
Note: The number of dispensers does not always equal the capacity of a station.
Place a node node on each dispenser. It is highly recommended (but not required) that you add connector information, please see connectors below.
Recommended Tags
Tag Usage in the United States Applies to When to Tag
frequency=0
frequency=60

nodeareaamenity=charging_station
nodeman_made=charge_point
For DC fast chargers, use tagfrequency=0.
For AC slower chargers, use tagfrequency=60.

See connectors below for examples of DC and AC chargers in the United States.
brand=*
brand:wikidata=*

nodeareaamenity=charging_station
nodeman_made=charge_point
The brand of a charging station or dispenser should be the prominent name signed or otherwise displayed in or around the station or dispenser. This may or may not be the same as the keymanufacturer=* of the dispensers or the host of the station (where the station is located.)

Charging stations and dispensers rarely have a keyname=*. Typically, this is reserved for large "hub" style stations where they will be signed or cutesy names given to the dispenser (EVgo likes to do this.)
Connectors
AC:socket:type1=*
DC:socket:type1_combo=*
DC:socket:nacs=*
DC:socket:chademo=*



nodeareaamenity=charging_station
nodeman_made=charge_point
Connectors are crucial for an EV driver to know. If a station does not support the type of connector their car supports or they have an adapter for, a driver cannot charge there. This is the count of each type of connector.

In the United States, NACS is quickly becoming the standard, while many stations and dispensers still support CCS (type1_combo) connectors, and CHAdeMO support is being deprecated.

Please see the keysocket=* page for images and descriptions of all options.

Subkeys
Do not add units, only the numerical value.
socket:<type>:output=* - For the kW output.
socket:<type>:current=* - For the amperage (A).
socket:<type>:voltage=* - For the voltage (V).
Additional Tags to Consider
Tag Applies to Usage in the United States Notes
ref=* nodeareaamenity=charging_station
nodeman_made=charge_point

|| The reference number of the station or dispenser.
Examples: Valueref=01 on dispenser; Valueref=12345 on station.

manufacturer=* nodeman_made=charge_point

|| The manufacturer is typically on a regulatory label on the dispenser.

model=* nodeman_made=charge_point

|| The model is typically on a regulatory label on the dispenser.

opening_hours=* nodeareaamenity=charging_station

|| DCFC tend to be open 24/7.

access=* nodeareaamenity=charging_station

|| tagaccess=yes - Publicly accessible chargers.
tagaccess=customers - Restricted access by location or capability (Tesla & Rivian have exclusive chargers in some places.)
tagaccess=no - Private chargers.

fee=* nodeareaamenity=charging_station

|| If a charging station charges a fee.

charge=* nodeareaamenity=charging_station

|| If tagfee=yes, the amount charged. Example: Valuecharge=0.39 USD / kWh.

EV Brands and Networks in the United States

When mapping or importing, you may find the additional brand information handy

Brand Name Wikidata Website Chargers Used
7Charge by 7-Eleven [W]Q134716089 https://www.7-eleven.com/7charge
ABM [W]Q4650338 https://www.abm.com/solutions/service-line/ev-charging
To be continued...

Imports

There are several imports that are in various stages of completion. They are as follows:

Possible Imports
Source OSM Wiki / Discussion Progress Reference Key Description
AFDC from the U.S. DOE Weekly Updates Not OK... Ongoing A centralized self-reported database maintained by the United States Department of Energy. Endpoints include those for station data and charge point data. This is the primary import for OSM in the United States. Weekly insights from this import are being posted to the community forum under the tag state-of-charge. This is written weekly on Sunday by GA_Kevin (on osm).
Supercharge.info Discussion OK! Initial Import
Not OK... Ongoing Sync
Rovastar (on osm) is an admin on Supercharge.info as well as a contributor to OSM. In June 2025, GA_Kevin (on osm) reached out to the Supercharge.info team about a possible import and it was encouraged and use of data approved. This data is available worldwide, but only a United States import (achavi, OSMLab, FacilMap) has been completed. Ongoing sync is planned for updating stations in OSM as well as Supercharge.info using the reference key to link the databases.
Open Charge Map Stale Discussion Nay! Not Started chuq (on osm) and a few other contributors have reached out in the past to discuss a possible import. At the time, data structure in OSM left a lot to be desired surrounding charging stations and it seemed the heavy lifting was left to be hypothetical. Furthermore, OCM's license may not be completely compatible with OSM, at least not the entire dataset (user contributions may be licensed differently.) If an import is desired, please revive the old discussion with concrete steps moving forward and who will be doing the heavy lifting and ask about license compatibility if they are willing to let OSM use their data.