rumbrummer's Comments
Changeset | Маца | Коммент |
---|---|---|
167058612 | 2 масех бутт хьалха | Sorry, comment is confusing, should be swing gates, not lift gates. |
159129827 | 4 масех бутт хьалха | Hi, laut Kurviger Forum ist die Straße noch in Bau:
|
161297924 | 7 масех бутт хьалха | tagging with access=cutomers is ok - but it takes a few days until Kurviger takes it over (please see Kurviger forum: https://forum.kurviger.com/t/ferry-crossing-troon-brodick-arran-is-missing/20151/6 |
140946791 | 11 масех бутт хьалха | Thanks for feedback. I put a hint for clarification in OSM:
|
140946791 | 11 масех бутт хьалха | Is that road really one way? I am not sure, but did not see a sign. |
155593158 | 12 масех бутт хьалха | The obsolete restriction I mean is osm.org/relation/17960948 |
155593158 | 12 масех бутт хьалха | From my point of view this restriction is obsolete, because osm.org/way/23221922 is tagged as onway, and turning left would mean driving in wrong direction of oneway |
145579837 | 12 масех бутт хьалха | I removed one of them, please see osm.org/changeset/155620637 |
145579837 | 12 масех бутт хьалха | Thanks for the fast change - the "straight on forbidden" restriction is gone, Kurviger updates OSM changes to its routing machine each 2 days - I will check ASAP. But the buggy restrictions (way instead of node as via) are still there - I am afraid that they will not work properly in routing machines, but I am not an expert. |
145579837 | 12 масех бутт хьалха | Are you sure with
|
138573601 | 2 месех шо хьалха | Hi,
|
133859684 | 2 месех шо хьалха | Thanks for feedback - done! |
133859684 | 2 месех шо хьалха | Ah - got it: In the past there have been 3 nodes: The saddle 10221246496 (20m besides the road), a pass 10598911072 20m away from that saddle (in the road) and an other pass ~200m away in the road (I did not see it).
|
133859684 | 2 месех шо хьалха | Hi, thanks for the hint, but yes, I am aware of that (and was also before ;-) ): As you can see in history osm.org/node/10221246496/history, in this case the old pass position was 20m away from saddle position.
If you open the node in edit mode and use the OpenTopoMap, you can see the old pass position - it is 20m away from the road (can not paste screenshot here) - if you shift it to the road, you reach the saddle position. So I do not understand why this change (shift pass onto road, unify it with saddle node) should be wrong - every hint mentioned above says that pass and saddle are at same position. I unified several pass/saddle pairs which had a very low distance to a single node - it is not useful to have separate pass and saddle close together, because that causes poor readability in some OSM maps. If I did a mistake and unified a pair, which was not close together, please give a feedback, I will revert it. Regards |
135395751 | 2шарал кӀезга хьалха | Ich habe 2 Hinweise angelegt, die kannst Du über das Ebenen-Menu auf der rechten Seite einblenden.
osm.org/changeset/135395751#map=19/48.14567/11.57484&layers=N |
135395751 | 2шарал кӀезга хьалха | Du hast das "lanes" tag und das "oneway" tag entfernt - ich denke, das wird das Problem nicht lösen, sondern verschlimmern (jetzt kann auch in Gegenrichtung über den Weg geroutet werden).
|
133688562 | 2шарал кӀезга хьалха | Der Pass
|
118292982 | 2шарал кӀезга хьалха | Is access=no correct for this lane of N20? |
116196102 | 3 месех шо хьалха | Hi, as mentionede in the comment of the changes, I just put the mountain pass onto the road (the elevation was already there, please see osm.org/node/6333378176/history ). So your information probably is correct. |
116187585 | 3шарал кӀезга хьалха | Thanks for the feedback. I have modified several mountain passes (with iD) - unfortunately many times with lost history.
|