[Tagging] [RFC] Feature Proposal - EV Charging Station Mapping

[NKA mapper]

fre. 31. mar. 2023 kl. 01:54 skrev Andy Townsend <ajt1047 at gmail.com>:

> If the same tag must be used for both, the only way to tell "single charge
> point" from "group of chargers" is to have a tag that is set to indicate
> which is which.  If "newtag=single" it means it's a single charge point, if
> "newtag=group" it's a group, and if "newtag" is not set, we don't yet know,
> and need to encourage local mappers to add the tag.
>

Why would you want to tell the difference between single-charger stations
and a multi-charger stations? What is the use case? Would you like to
render a group of charge points differently from single charge points?

If you would like to render them differently, then why is a group of 4
charge points of 3.6 kW more important than a single high capacity CCS
charger? If you want to have a new feature or another tag for a "large and
important charging site" similar to a recycling center, then how do you
even define what that is?

I understand that a single bin is different from a full recycling center,
but it is a little more complicated with chargers. For fuel stations, I
would not care if there is one pump or three. For charging stations, I look
for a high capacity charger while on the road (availability is provided by
an app), and for lower capacity chargers for a stay overnight. I think
there is no way around using capacity and socket information if you want to
render certain charging stations differently. Asking users to add another
new tag will not help as it would be incomplete.

With the proposal, at least you would not need to render 36 identical
charge points at a location, and it will be clear that one
amenity=charging_station element should carry capacity and socket
information for the whole location, making it easier than currently for
data consumers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20230331/6c40c139/attachment-0001.htm>