| Changeset | # | Tmstmp UTC | Contributor | Comment |
|---|---|---|---|---|
| 78531587 by kanleela @ 2019-12-17 14:08 | 1 | 2021-02-18 16:52 | skquinn ♦805 | In the future, please do not loop service roads back onto themselves as you did with way 756263924 (may be changed by the time you see this). This throws warnings and errors in many validation tools. |
| 2 | 2021-02-19 08:48 | kanleela | Hi Skquinn, Thanks for your feedback. I will make sure not to make such closed loops in future. Looking forward to learn more from you.Regards,kanleela. | |
| 82429691 by kanleela @ 2020-03-20 11:33 | 1 | 2021-02-13 03:34 | DUGA ♦549 | You caused more trouble because an illegal turn was added. |
| 2 | 2021-02-15 09:10 | kanleela | Hi,Thank you for reviewing and correcting the edit. Apologies for the incorrect addition of road, will ensure not to repeat such errors. Looking forward to learn more from you. Happy mapping!Regards,kanleela. | |
| 75987879 by kanleela @ 2019-10-21 10:18 | 1 | 2019-12-28 09:21 | gpserror ♦222 | Not sure who caused this issue, but there is an overlapping road here and you were a recent editor of this road, if you could fix it that would be great. The problem area is at (39.50248,-74.99426) near the service road. If you don't understand the problem, feel free to please contact me. |
| 2 | 2019-12-29 03:51 | freebeer ♦1,598 | salve, gpserror...is your detection of these overlaps able to spit out the id of the two (or more) ways of concern?i know my editor will make them obvious, but due to multiple catastropic equipment failure i'm reduced to viewing osm data on a castrated device where tracking the history ... | |
| 3 | 2019-12-29 19:07 | gpserror ♦222 | I was trying to fix some turn restrictions here but noticed the overlap so I stopped and tried looking for who caused it. Still tough to tell. Anyway the two broken ways can be determined without an editor through OSM main web browser, just "Query Features" on the point and it will show ... | |
| 4 | 2019-12-30 07:49 | gpserror ♦222 | OKAY: The person who created the overlap is https://www.openstreetmap.org/user/yerramg who had version 1, not this last changeset. It's scary that people are editing on top of this before noticing a duplicate. This is kind of dangerous. | |
| 5 | 2019-12-30 15:35 | gpserror ♦222 | I was able to fix another overlap at https://www.openstreetmap.org/note/2038869 -- luckily that one wasn't too hard to fix, just tedious. Used iD to fix(!) | |
| 6 | 2019-12-31 02:57 | gpserror ♦222 | OK I fixed this overlap: changeset is at https://www.openstreetmap.org/changeset/79037833 | |
| 7 | 2020-01-03 10:42 | kanleela | Hi,Apologies for the delay in response. I was unaware that my edit was being duplicated at the node. As freebeer mentioned, this could have happened because of the bug with tool. However, we are putting efforts to proactively identify and resolve such errors if committed by our editor. We are al... | |
| 8 | 2020-01-04 17:40 | freebeer ♦1,598 | salut, gps-systematic-offset,thanks for the tip. normally one is never too old to learn something new, but there's always an exception to every rule.i agree, not detecting these promptly is an issue as errors that take more effort to correct get compunded. in the case of the two ways ... | |
| 9 | 2020-01-05 16:46 | gpserror ♦222 | Oops, I think I misunderstood your question, sorry for answering incorrectly. When I edit things now in iD, most of the times I end up zooming into the intersection very closely and randomly click on the items in the vicinity. For each intersection I should see specific items highlight as one wou... | |
| 10 | 2020-01-06 02:44 | freebeer ♦1,598 | by the way, all, i think i was mistaken in my claim that potlatch2 would highlight this sort of overlap, haven given meself time to digest the random drivel i wrote.i likely confused my investigative work on this error with that performed earlier, several months ago, on a different iD irregular ... | |
| 74634111 by kanleela @ 2019-09-18 15:30 | 1 | 2019-09-18 16:26 | user_5359 ♦19,606 | Hello! Please the restriction relation https://www.osm.org/relation/10031611. |
| 2 | 2019-09-19 09:32 | kanleela | Hi,Thanks for your suggestion.I have fixed this changeset #74662087.Let me know if you have any other suggestions.Regards,kanleela. | |
| 74530833 by kanleela @ 2019-09-16 12:51 | 1 | 2019-09-16 16:29 | user_5359 ♦19,606 | Hello! A restriction relation must have three members (from, to, via), see relation https://www.openstreetmap.org/relation/10031611 |
| 2 | 2019-09-18 15:31 | kanleela | Hi,Thanks for your suggestion.I have fixed this changeset #74634111.Let me know if you have any other suggestions.Regards,kanleela. |