RfC: Deprecate socket:tesla_supercharger and socket:tesla_destination tags

Ok, lots of messages since I was last online. I think we need to step back a moment. Some key points:

  • Nobody is doing this with the intent of breaking existing data consumers processes. We want good quality data in OSM, have identified that a tag change will make this easier, have followed all the steps related to RfCs and I have tried to share this as widely as I can (e.g. I submitted it to WeeklyOSM). There has also been plenty of time - this has not been rushed through.
  • The next stage in the RfC is to actually see if this change get’s approval. Hopefully it will, but it may not, in which case we are making noise about something that won’t happen!
  • If it does get approved, it doesn’t mean an instant change. As has been pointed out nobody should be making bulk automated edits without first following the relevant processes (see Automated edits).
  • Deprecating the tag means different things in different regions of the world. In many places it would mean switching out one established tag for another long established tag. But in north America it does mean a relatively new tag (one that was probably inevitable anyway since NACS is now being used at non-tesla sites). Local communities should therefore act appropriately. A slightly longer gap between an ā€œapprovalā€ vote, and implementing tagging changes could be one option.
  • We have a list of some data consumers on taginfo (here). I will notify them all, either via a project address or via an individual that I know is well connected to each project.

If there is anything else you think I should be doing, please let me know. I want this to work and I want this to work well.

5 Likes

Relax @GA_Kevin

I have not been very active on OSM for a few years but things do move slowly move along (glacial speeds at times).
Getting to changing tag things properly can take forever. Sometimes (or the cynic of the process in me what say often) the paperwork and red tape to get thing done gets in the way. There can to be too much to take in. I looked a few years ago at the charging_point tag and it was a complete mess and not fit for any usefulness. I gave up even trying to get it sorted as it was too much work and get the majority to agree on anything here is like herding cats. They can mostly agree something is poorly implemented but cannot agree on the solution.

But things got better, there is still a bunch wrong with that tag that can be improved but it is at much better base than a few years ago.

Things like this socket were obviously wrong (now a more official name is recognised) and the worst of it was the ccs tag for this socket:tesla_supercharger_ccs monstrosity which hopefully this will address. Realistically these could have been changed by hand in the tags in the background and few would object but to change it properly to need to go this long process @RobJN is going through.

Progress does happen even a slow speeds we even have swimming pool tags I’ve noticed in one place now and that only took 15 years! The NSI has done wonders since it was introduced. It’s less of the wild west than it used to be.

And finally regrading this proposal it looks good the only real question for me was around J3400 and nacs naming. If it was just north America markets I can see it making complete sense it is unclear in the other markets Japan, South Korea (and there are some in Taiwan and Hong Kong too) how they refer to them if they get mainstream/government backed adaptation (Japan and South Korea will move to a new standard soon as there are outdated) what will they call in. But happy with nacs as it is the most common term and noone like or really calls it J3400

Thanks all. The voting stage is now open! Please add your vote to Proposal:Deprecate socket:tesla supercharger and socket:tesla destination - OpenStreetMap Wiki

2 Likes

I have contacted Pieter at MapComplete and opened tickets on the issue trackers for Vespucci and OSMAnd. It could result in some voting against the change as it will cause work for them but hopefully not.

Anyone know how best to contact Flosm POI and the JOSM team?

I have also submitted an article for the upcoming WeeklyOSM.

The voting period has now come to an end and this proposal was successful. I will update the wiki page when I have time this week. Many thanks for all your support.

2 Likes

I have now messaged all those who are listed on TagInfo as users of the deprecated tags with the exception of Vespucci. @SimonPoole you closed my GitHub ticket for Vespucci with this comment:

This belongs in the preset repo, not here.

But did not link to the ā€œpreset repoā€. I don’t know where it is. Can you either open a ticket for me there or share a link so I can.

Many thanks
Rob