Bulk retagging of Tesla Superchargers and Destination chargers in the United States

Communities United States
1

Hello OSM US community!

As SotM US is this week and the approval of the formal proposal is rather imminent (well above the threshold and no votes against,) I would like to start the discussion on retagging these stations.

Currently, in the United States, Tesla Superchargers and Destinations chargers share the same hardware, which is now standardized into the North American Charging System and represented in OSM as socket:nacs.

For this bulk retagging, and in agreement with the proposal, I would like to retag any amenity=charging_station or man_made=charge_point that has socket:tesla_supercharger or socket:tesla_destination to be socket:nacs. Please see the table below:

Current Tag Applies to Revised Tags
socket:tesla_supercharger
socket:tesla_supercharger:*		 amenity=charging_station
man_made=charge_point		 socket:nacs
socket:nacs:*
frequency=0
socket:tesla_destination
socket:tesla_destination:*		 amenity=charging_station
man_made=charge_point		 socket:nacs
socket:nacs:*
frequency=60

For this change, I will not be doing any further quality analysis on these stations, all values will remain the same, only the subkey will be updated. This can be done with an Overpass query loaded into JOSM quite easily.

I will not make these changes until the proposal is formally complete. I would like feedback on the following:

  • If there is objection to this edit following proposal approval.
  • If there is a data consumer in the US that does not currently support socket:nacs but does support one of the soon-to-be deprecated keys. If so, I would like to get issues raised and PRs in order to address that early!

Thank you!

2 Likes
2

One bit of implied information you’re losing here is the fact that socket:tesla_supercharger supports DC Fast Charging (~250kW) while socket:tesla_destination is level 2 (typically 11kW max). I realize that the socket:* prefix doesn’t/shouldn’t imply this information, but do you have a plan for capturing the charging rates in another tag so this information isn’t lost?

1 Like
3

As with most of my import / cleanup of EV information I use frequency=0 to notate a DC charging station, so any non-zero value in frequency=* can be assumed to be AC charging. In the United States, AC charging is frequency=60. I have updated the post with a table to show this, thank you!

If we know for a fact all destination chargers are 11kW, I can add that in socket:nacs:output but I don’t have the knowledge to say for certain and that borders on mission-creep for this effort.

As far as Superchargers, these can be 72, 120, 150, 250, 325, or 500kW according to Supercharge.info’s source code so these will not be getting socket:nacs:output tagging and will require an import (working on it) or survey to check the label on the stall itself.

4

@GA_Kevin They are not all 11kW. They vary a lot just a quick look of random destination on the tesla site I charges I saw 8, 11, 16, etc

You should also retag the socket:old tesla tag:output too in this to socket:nacs:output (and I suppose any others tesla:old tesla tag:voltage, etc)
It will not make sense to leave that there (and it will be just wrong) and it preserves the output kW that @iandees was worried about.

Another that may happen here is what if a station is tagged with both socket:tesla_supercharger and socket:tesla_destination that might need looking at as they will get the same tag and confusion/errors.
Maybe a sweep of the data to see if any of these occur before you run it.

5

I have updated the table to make it clear I also mean subtags, thanks!

It would come out as a semicolon delimited list such as:

socket:nacs=20
socket:nacs:output=250;11
frequency:0;60

I suspect they are rare, but will run a few overpass queries to confirm that theory before proceeding. Finer grain detail (like how many of each) would come from the nearby man_made=charge_points which would be even more valuable to tag in a station configuration like this.

1 Like
6

Great. That is all covered then.
Yeah shouldn’t be many with both types. AFDC database considers these to be separate stations. Can probably go by hand to check the few of them, if needed, to separate them.

7

As much as I am liking doing imports, I do enjoy some artisanal mapping as well! :slight_smile:

1 Like
8

Good news! Using the following overpass query there were zero OSM elements in the US that have all 3 tags:

amenity=charging_station
socket:tesla_supercharger
socket:tesla_destination

[out:json][timeout:25];
{{geocodeArea:United States of America}}->.searchArea;
nwr["amenity"="charging_station"]["socket:tesla_supercharger"]["socket:tesla_destination"](area.searchArea);
out meta;

Given that I am planning to import the rest of supercharge.info from the US this weekend, I will switch the values for socket:tesla_supercharger and subtags to socket:nacs then to avoid duplicate socket information from the import. Once the proposal finishes next week I will make a second changeset to convert the destination chargers.

1 Like