Changeset When Comment
180012656

Hi,
I acknowledge and thank you for the feedback.

185712767

Hi pnorman,
The missing segments have been added based on available evidence. The existing one was not verified, as the primary intention was to add the missing segments rather than to review what was already in place. Please note we have paused the edits and will resume once community consultation is completed

185713586

Hi pnorman,
The new road segment was added based on clear alignment between GPS traces and aerial imagery. To maintain map accuracy, features are only added when they can be fully verified. Since the available data does not provide clear evidence of a U-turn restriction, it was left out of this edit.

185713794

Hi pnorman,
Thank you for looking into this area. The new road segment was added based on clear alignment between GPS traces and aerial imagery. Regarding your observations about the construction zone status, the alternate entrance, and the bridge connectivity, these features fall outside the immediate scope of this specific edit. The focus of this changeset was solely on adding the missing road segment verified by our data sources, rather than updating the surrounding basemap connectivity or construction tags.

181302551

Hi pnorman ,
Thank you for flagging this. You are absolutely right, and we apologize for the oversight.
We have now updated the wiki pages for both the London Sidewalks organized edit (Uber Pedestrian Data Improvements in London) and our other global edit pages (Uber Road Geometry, Turn Restrictions, Directionality & Lane Connectivity Improvements) to accurately reflect the current status.
We also confirm that all edits under this organized edit in London were stopped in June 2026, and we are not currently making any edits.
Additionally, we are currently in the process of reviewing the edits we made in London to ensure they meet the expected quality and community standards.

Based on the updated wiki page status, could you please advise whether we may proceed with resuming edits?

Thank you again for your patience and guidance.

181302551

Please find the page with the organized edits.osm.wiki/Uber_Pedestrian_Data_Improvements_in_London

185717624

Hi norman,
Thank you for your feedback. I sincerely apologize for my mistake. I initially marked the road as two-way based on our internal GPS data. However, after verifying the road alignment, I realized it is actually one-way, and I have reverted the edit.

I truly appreciate your feedback, and I will be much more careful in the future before uploading any edits. Please also find the relevant OSM wiki for reference. Link:osm.wiki/Uber_Road_Geometry,_Turn_restrictions,_Directionality_%26_Lane_connectivity_Improvements

181302551

Hi rskedgell ,
Thanks for performing the edits. Thank you for catching these errors and for taking the time to correct the changesets. We are not currently editing in London, UK, and we stopped editing there on 26 May 2026.

Regards,
Vandana N

182534470

Hello Andy,
Thank you for reaching out and for taking the time to flag this issue with the "Jubilee_Walkway_City_Loop" (relation/12890344). We sincerely apologize for the inconvenience caused by our edit.
And thanks for fixing the relations from your end.
We will check on possibilities to use JOSM validator for upcoming edits on relations.

182534470

Hi Andy,

Thank you for the helpful feedback and for pointing this out. You are completely right.
We reverted the changes and we didn't get notified about relation breakage at the location in OSM ID editor.
Deleted our standalone kerb node since the existing kerb already covers this location.
Thanks for the suggestion to use JOSM editor we will look into this.
Best regards,
Vandana

182493502

The river location was not within our working area. However, thank you for bringing it to our attention

181436621

Three months ago, we created the barrier based on internal evidence. However, following user feedback, we reviewed OpenStreetMap (OSM) various aerial imagery data. Since the imagery confirms the barrier is no longer there, we have reverted the change and removed it

169340203

Apologies for the mistake and Thank you for your valuable feedback. I will make sure to be more cautious in future. Thank you.

176729443

Apologies for the mistake I committed. Going forward will take care. Thank you for the valuable feedback. Thank you.

176726859

Apologies for the mistake and Thank you for your valuable feedback. I will make sure to be more cautious in future. Thank you.

179953702

acknowledge. going forward will take care

178991673

Thank you for the valuable feedback. Please feel free to point out similar suggestions in future as well. Regards, Vandana N.