mueschel's Comments
| Changeset | When | Comment |
|---|---|---|
| 139527615 | Hi,
|
|
| 139502235 | I agree this tagging is not really nice, and I would recommend to remove it. Why don't you just add a link to the website? It's not really opening_hours, so I wouldn't use opening_hours:url, but maybe a similar tag? |
|
| 139555475 | Hi,
|
|
| 139540783 | Hi,
|
|
| 139312610 | Hi,
|
|
| 139265856 | Hi,
|
|
| 139319457 | Hi,
|
|
| 139361551 | According to the changeset, the data comes from Bing...
E.g. there needs to be a documentation of the import process in the Wiki, a proper source in the changeset and a description of the new tags you create. |
|
| 139364953 | May I suggest to change to change the "electrobus" tags to something that fits better with other tagging schemes? 1. we already use electric_vehicle and electric_bicycle. How about using "electric_bus"? 2. replace "type" by "manufacturer", which is already in use in many contexts. |
|
| 139361551 | Hi,
|
|
| 139139831 | Hi,
|
|
| 139159925 | Hi,
|
|
| 139125430 | Hallo,
|
|
| 139213823 | Hallo,
|
|
| 44325690 | Hallo,
|
|
| 139054857 | Hallo,
destination:ref:forward:to -> destination:ref:to:foward. Das "to" kommt immer vor dem "backward" oder "lanes".
|
|
| 139093992 | Hi,
Could you check & fix this? |
|
| 139181247 | If it's not clear what the correct natural value is, then there should be a 'fixme' tag on the area so that every mapper in the area gets a marker in their editor.
Even the questionable 'hazard' tag seems to be fitting according to the OSM Note that was left here a year ago (there is still a hazard in the area if you try to access it). Contacting that user seems to be a good source for further information... |
|
| 139181328 | Check e.g. osm.wiki/Limitations_on_mapping_private_information Note that this particular case is not mentioned here, but things that are listed there as not allowed are much less problematic according to law. |
|
| 139181328 | The ethnicity of people is considered as private information that needs special protection by law in many places, e.g. by GPDR and CCPA. Having this kind of information in an open database would make use of OSM almost impossible in these areas. I also remember several discussions with the result that a geo-database lime OSM is not the right place for this kind of information. |