OpenStreetMap

You connected roads that are not physically connected and added back roads that have been removed because the area has been demolished!

#WhatInGrabsNameIsThis

Hi Mishari,

Thanks for your feedback.

Can you please provide the way id's so that i can investigate further on the edits done.

Thanks,
Sridhar.

Just with random sampling:
628703875
628507844
410269871 is sloppy, look at the trailing node.
183877605 <-- this isn't quite how we do connections
628709422

I'm reverting this changeset Sridhar.

Thanks Mishari for giving more details.

1) 628703875 - Roads in demolished area.
This area was mapped basis Bing, where buildings are available. However Esri doesnt have buildings. As images available in Josm doesnt give the details of imagery date. I was not sure which imagery is latest here. Here we need help from local mappers to guide us and correct us as appropriate . Since you confirmed this area as demolished. I am now going ahead and deleting them.

2)628507844 / 410269871 - Incorrect connectivity
While aligning the segments, nodes seems to be mistakenly extended beyond the intersection . I am correcting now.

3)183877605 / 628709422 - From the navigation perspective of pedestrian mode, connectivity is correct and needed. Please suggest if we are missing anything here.

Thanks,
Sridhar.

#WhatInGrabsNameIsThis

This edit has been reverted further in chageset 65114108 <https://www.openstreetmap.org/changeset/65114108>, on the Petchaburi road, at the east of Petchaburi 30 drive's entrance.

Reason:

The edit introduced a small "dent" in Phetchaburi road: a sharp left turn followed by a sharp right turn in less than 1 meter.

This is *dangerous* when user uses OSM via turn-by-turn satellite navigator; the error will cause navigator to falsely announce turns where user least expects them, leading to motor accidents.

Following is a screenshot of GraphHopper's driver instruction on this supposedly-straight Phetchaburi road. I have highlighted the false turn in yellow:

<https://u.cubeupload.com/xwindows/xUqsXB.png>

Some satellite units got an even more harsh reaction to this kind of mistake: <https://forum.openstreetmap.org/viewtopic.php?pid=721737#p721737>

Be aware that edits like this can cause real-life fatalities.

I have now reverted it even further in changeset 65120342 <https://www.openstreetmap.org/changeset/65120342>, due to a dangling node that appeared out of thin air.

> Here we need help from local mappers to guide us and correct us as appropriate

This is the crux of the problem. I don't think it works this way, try to get someone from your team to map your city using your standard and see how easy it is to correct after the fact. Your workflow may be appropriate for a closed GIS system, but doesn't really work in OSM context.

Way 628709404 surrounds an office building in an urban environment, how can it be residential?

This edit is also adding excessive nodes to a roadway behind The Market Bangkok, despite the real road being straight.

The corresponding part is now reverted via changeset 68883346 <https://www.openstreetmap.org/changeset/68883346>.