OpenStreetMap
Argh! After putting this junction right twice I've had to take desperate measures. (see map location and click edit)
I wish yahoo tracers wouldn't assume that other mappers are wrong when they haven't been to a location recently themselves. This roundabout was changed to a big crossroads more than a year ago!
Grrrr!
토론
2009년 5월 23일 09:51에 Minh Nguyen님의 의견
Perhaps you could try adding
note=Yahoo! is out of date here.or something like that.2009년 5월 23일 10:36에 c2r님의 의견
Have you let the users know? h in potlatch to find who did it!
2009년 5월 23일 11:47에 RichardB님의 의견
I guess you'd have to be blind to change it back again now! But there must be plenty of places where Yahoo is now out of date. I can think of several. In addition, I can also think of areas where GPX traces are now out of date.
Some way of removing out of date GPX points would be good. Could be tricky to implement though.
2009년 5월 23일 11:50에 RichardB님의 의견
I've also noticed that your junction has a set of unconnected nodes at the northernmost highway=traffic_signals node. Can I assume that these should be merged?
2009년 5월 23일 12:44에 daveemtb님의 의견
I had put an explanatory note on all the nodes the first time I mapped it correctly! Hence the rather silly writing all over it now!
I think the uncorrected nodes were an error in Potlatch when I reverted the ways. They need deleting.
2009년 5월 26일 15:30에 Andrew Chadwick님의 의견
Perhaps it would be cleaner to draw a small bounding box with a note explaining that Yahoo!'s imagery is out-of-date here. Much like osm.org/browse/way/32737099 only in reverse...
2009년 5월 26일 18:31에 daveemtb님의 의견
I'm sure it would be neater, but people weren't reading the annotations on the nodes of the junction. I'll clean it up eventually, but thought more unmissable "hint" would be useful effective the short term to discourage reversion.
2009년 5월 26일 18:32에 daveemtb님의 의견
I should add that my initial exasperated diary post was not a complaint at anyone who does Yahoo tracing - I do quite a lot myself. It's just important that people don't assume it's right and the existing mapping is wrong.