karussell's Comments
| Changeset | When | Comment |
|---|---|---|
| 40988423 | ||
| 49637026 | Cool, danke! |
|
| 49637026 | Durch access=no wird der Zugang zur Brücke auch mit dem Fahrrad blockiert. Ist das gewünscht :) ? |
|
| 47141205 | No. Will contact the Data working group first ... |
|
| 47141205 | Ok, 10 days is enough to respond. Will revert. |
|
| 47141205 | It is not allowed to copy from other map providers! Please revert this change and then submit a new one if you can see this road via aerial view in the editor. |
|
| 41567412 | Kleine Frage, routet der hier korrekt? Oder kann man da nicht durch? https://github.com/graphhopper/graphhopper/issues/337#issuecomment-230723525 Und muss in einem Sperrgebiet nur der Zugang gesperrt werden oder müssen alle Straßen darin z.B. das military tag haben? |
|
| 36574712 | War vor Ort und hier nen 'Nachweis'
|
|
| 35009662 | This language ambiguity should not infiltrate OSM tagging. So I would either define max. one unit per country or just one unit world wide and move the conversion towards the editor |
|
| 35008212 | Sorry, I've reverted and put the hgv:no on the list. That is indeed an ugly sign :) Please see my steps which leads to the removal action here:
|
|
| 35009662 | Furthermore the usage of 'US tons' was 5 world wide. And that before my edit ... |
|
| 35009662 | My argument is that OpenStreetMap is a database and should try to get more concise over time. Also there are so many units and possible combinations why not just stick to lbs or tons? Please see my blog post why I think it is necessary to move at least parts of the unit conversion step to the editor:
|
|
| 35009662 | This wasn't an automated edit. And I disagree about the tagging here. Because messing in every unit is not only ugly but is just a lot simpler if done on the editing side. OSM is a database AND not necessarily 'readable' by humans (although partly important I of course agree) A good editor would read the value and convert to the readers preferences. The same for writing the value. |
|
| 35009662 | And I agree with you that the mapper is very important (I do not agree on the term 'resource' ;)). And so we should fix the mapping software making converting US short and long tons etc into tons. Also I do intend to change 'lbs' values because they are a lot more frequent and kind of 'unwikied' standard, so I also do not think 100% that the wiki is OSM.
|
|
| 35009662 | Why is this harder to use? In fact consuming values like this is very confusing. The mapping software should make it easier with conversion, so I my counter argument is: your mapping software should be improved to make consuming the data easier. And an important btw: such a value '15 us tons' is used VERY rarely world wide (and therefor for US too) Just have a look here: http://taginfo.openstreetmap.org/keys/maxweight |
|
| 35009662 | It has nothing to do with software. The wiki is very explicit when it comes to weight:
|
|
| 35008444 | Okay, so please undo. |
|
| 35008444 | Sorry, I've placed a note to avoid loosing information, I'm not unsure how to map it. Would you help? |
|
| 34326155 | I get:
|
|
| 34326155 | Please review as this road is clearly too long! |