Talk:Tag:amenity=charging station/Tesla Motors

From OpenStreetMap Wiki
Jump to: navigation, search

Tagging

https://www.mail-archive.com/tagging@openstreetmap.org/msg20684.html

operator=Tesla Motors Inc.

...seem to be mostly used. Since OSM discourages abbreviations, should we just sick to "Tesla Motors"? Or how is this usually done with corporations. Not really a fan of adding Incorporated. Also seems to be "Tesla Motors, Inc."


authentication:*=*

... I can't find any tags that fits on amenity=charging_station. I think it's bascially does it over the plug and some data cable. Not every Tesla can actually charge there, for some cars it's an extra upgrade you have to purchase. Not sure authentication:cable/plug/automated/?/=*

Or is authentication:none=no enough?

access=customers

....obviously means for Tesls customers, but what if a station is actually limited to for example hotel guests? Not really that important right now, but if someone has a good idea...

...should this be changed to operator=Tesla instead of Tesla Motors? The motors part could be dropped.

Supercharger Plug Type

It seems that right now there is more than one plug in use for supercharger stations (worldwide).
Example: The EU superchargers do have a Type2 like plug while the US superchargers do have a proprietary plug. If you decide to import a US Tesla to Europe or drive your US Tesla in the EU (or vice versa) you - at least as far as I know - can not use any of the superchargers, because there are no converters for it. Thereby an additional tag that would specify which type of plug is used in the supercharger would be a smart idea.
I thought about something like tesla_supercharger_type or tesla_supercharger:type = NAME
Any ideas or comments about that? --TBKMrt (talk) 17:45, 5 April 2017 (UTC)

Because of the lack of comments - none at all to be precise - I count this discussion as no one cares. So if there is a new key called tesla_supercharger:type no one will complain. --TBKMrt (talk) 19:53, 9 May 2017 (UTC)
New key-tag combinations:
  • tesla_supercharger:type - What type of charging connector is used
    • Type2 like connector: type2
    • US connector: ? (it's name or acronym)
  • tesla_supercharger:version - What version the charging station is at
    • int value of the version number (currently gen is 2, version 3 said to be published this summer)
Existing key-tag combinations:
  • socket:tesla_supercharger:output - the electric power output of the respective plug (watts)
  • socket:tesla_supercharger:current - the current of the respective plug (ampere)
no comment for over a year, can we do better than that and get 1.5 or 2 years?
--TBKMrt (talk) 23:34, 22 May 2018 (UTC)

Destination Charging

I was wonderding: what's about Tesla's destination chargers? Is there a pattern how to map them properly? Nothing is mentioned in this article.

Some questions regarding destination charging which comes into my mind:

  • is Tesla the operator or is it the "Charging Partner"?
  • as the destination chargers are one stall per car, create a node for every stalls or just one for all?
  • how to make clear that some of the stalls are available only for tesla and some of them for everyone?
  • which socket to map, type2?
  • how to map that the destination charger is only for customers of the shop how installed the chargers (typically access=customer but it maybe collides with "only for tesla customers")

--Nickel715 (talk) 21:05, 13 June 2018 (UTC)

I would have to check a destination charger to see how they are configured. Regards your questions:
  • operator: I think the operator is the partner at the destination location
  • one stall per car: No, just tag them like other charging stations with multiple stalls
  • tesla only stalls: if they are separated they could be taged as two different nodes. If not I don't think that there really is a standard way of doing it. You can place a note key, but that wouldn't solve the problem
  • socket type: add te socket that will be found there no matter what it is. If you can charge an EU Tesla it's more than likely Type2, not sure how it is in the US.
  • shop vs tesla only: like above. if the shop is the operator then access=customers is not a problem even if it's tesla only since even as tesla person you can only charge your EV there if you go into the shop
Maybe it's best for now to leave them as separate points when you have tesla only and customer only charging ports since it's not really commons to have such a restriction. usually the charging station is private OR public
--TBKMrt (talk) 18:03, 14 June 2018 (UTC)

Thanks for your reply.

  • operator: I checked the documentation for operator and it correspond with your suggestion. The operator tag is described: "who is directly in charge of the current operation of a map object" this applies to the charging partner. In addition (as the chargers are Tesla branded) I would use brand=Tesla.
  • tesla only stalls: As the destination chargers usually always only for customers of the operator access=customer definitely makes sense. But I also have no idea how to map the difference for tesla only. So the best solution would be the note I think.

Finally I came up with the following tagging suggestion, what do you think guys?

Destination Chargers

There are two types of destination charger. The one for Tesla only and the charger for all EV's. If there are charger for non teslas there are also tesla chargers. So you need to create two nodes, one for Tesla only and one for all EV's like in the following example.

For Tesla only stalls

The boxes with the red "Tesla vehicles" sign.

For "All EV" stalls

The boxes with the white "Electric vehicles" sign.

Discuss: Talk:Tesla_Motors#Destination_Charging

--Nickel715 (talk) 21:53, 3 July 2018 (UTC)

I would like to suggest the following for destination and superchargers.

The reason for this is that there are two types of Tesla chargers. I have three destination chargers at my office but currently there isn't a clear way to tag them, only supercharger which is incorrect. https://www.tesla.com/findus/list/chargers

--vespax 13:32, 27 September 2018 (UTC)