stillhart's Comments
| Changeset | When | Comment |
|---|---|---|
| 179463207 | hi. I think here you mapped the whole supercharger into many charging station but that is wrong. a charging station can be an area for the whole set of chargers too. each individual station is then a man_made=charge_point see also
you mind if I fix it? |
|
| 179429906 | (mapping chargers in general is a mess) |
|
| 179429906 | thank you for the supercharger, I updated it slightly. There are some good presets on iD too :-) In case you want to learn how to map charging stations very accurately (and usefully for electric car drivers), here's the wiki
Further in case you are local, you may convert the charging_station to an area and add each charging point too.
no critic, just a hint :-) |
|
| 179512738 | Thank you for fixing my mistake and adding back the (less accurate) summaries. For me it's just very important to get to charging infrastructure mapped right and also more or less easy readable. For electric car drivers it often matters a lot how big and fast a charging station is. And there are a 1000 proprietary apps having localized data, but it sucks as tourist. So really wish for osm to be the leader here :-) |
|
| 179512738 | The wiki article contradicts that. Same as a map consumer, I really think it‘s useful and practical to have the summary of chargers on a node/area. I suggest do discus this there or on the community website ( 1 of 1000 charger discussions :-) ) My analogy would be parking spaces, which belong to a parking. We do not expect the map consumers to count spaces inside the parking, instead we use the capacity. I consider the sockets as capacity. |
|
| 179497134 | Oh shit, I thought the use the Tesla ID?!? 🗿 I will verify and cleanup. |
|
| 179325263 | (soll heissen, mir sollen alles recht ein, hauptsache konstistent durchgezogen) |
|
| 179325263 | Bei OSM ist es immer schwierig herauszufinden wer wo wie die Daten braucht :-) Generell ist das Chargerthema ein leidiges. Tesla war früh und zuerst, d.h. socket:tesla_supercharger_css aber heutzutage ist es halt generisch. aber je nach Kontinent ist es dann wieder etwas anderes. Aber so sind und waren halt viele Supercharger getaggt. dann kommt noch socket:, die dinger sind alle kabel, keine Sockets. sockets gibt es wenn überhaupt bei typ2, aber nicht beim combo. Ergänzt wird das durch die fehlenden Felder in iD. Die Stecken da auch in zig diskussionen fest... |
|
| 179325263 | Verständlich. Problem ist etwas, dass die Equivalent sind die Ankündigung zur Umstellung etwas kurzfristig war. D.h. kann man vorerst beides lassen. Zumindest so gelesen. |
|
| 177113688 | Wusste nicht dass das irgend ein Tesla supercharger kann😳 |
|
| 152551387 |
is that really a destination charger? |
|
| 178220510 | btw, no critique. mapping charging stations is hell and has change often recently... |
|
| 178220510 | according to the tesla website, there should be 14 charging points. if you are local, you may add all of them exactly :-) |
|
| 178220510 | hi :-) for your information. for charging stations, the whole station is an amenity
and each machine then is a man_made charge_point the naming is pretty confusing :-(
For tesla it's more special, since each station is for 1 car. in some brands the charging_station and charge_point are basically the same. |
|
| 136916790 | lovely supercharger micro mapping you did here :-) fyi, chargers can be areas, even relations, these days. the charge points can have now tesla tagging too :-) |
|
| 178809665 | is there really a destination charger right next, even in, this supercharger??? |
|
| 178203920 | Very nicely mapped supercharger 😍
|
|
| 177113688 | der Supercharger hat doch niemals 500 kW???? |
|
| 176681106 | is here really also a destination charger? maybe add a note then |
|
| 174925755 | perfekter supercharger 😍 |