Hey Rene78,

The context here is since this way way/449370094/history is marked as access=no, and the remaining are marked as private. The validator flags it as island highways due to the fact private roads are considered routable. Can we mark these roads as access=no or change the first way access=private so that the validator doesn't flag it as island highways?

Retaining a correct no right turn restriction from Tuas Crescent to Pioneer Road.

Oh? I checked multiple imageries before I changed it. May be the ones I checked are old. Thank you for bringing this ti my notice, will rectify it immediately. Apologies for the delay in response.
Poorni

Clicked this by mistake: review_requested yes
No need of a review

*on

Hi,
Thank you so much for letting us know about this. We will work in fixing these. We have deleted most of them already. But I guess we missed a couple of the pointers. Will rectify it soon. Thanks again!

Data fixes in Boston

F Street

Los Angeles street closure

source: http://campaign.r20.constantcontact.com/render?m=1101388121947&ca=c71c41c0-caf9-4f9c-b3cf-0af962e6a14b

Juliane Street

http://nypdnews.com/2017/11/enhanced-security-measures-significant-changes-thanksgiving-day-parade-festivities/

College Point Boulevard closure

The actual changeset for the road closure details is here: changeset/53424372

I was aligning the road to the imagery in this particular changeset. Had a minor snafu with the upload.

Closure of Terry Francois Blvd

Hi Akash,
I noticed you have added Kolar place label, in Kannada, over water, when there is already a place label for Kolar present on OSM with the kannada translation already added: node/245618507/history. If you want to add the Kannada translations for an place, you can update the same node with name:kn tag, instead of creating a duplicate place label. I am going to delete the duplicate. Please be careful while adding/editing data and make sure you are not adding any duplicates.
Thank you,
Poornima

Hi Elvind,
I know that I have changed parts of the official import for coastlines. But not having that part as a riverbank is breaking OpenStreetMap itself. It's rendering water as land. I have not done any changes to the actual coastline. Unless the coastline doesnt break the river relation and render it as land, you can change my edits back to being coastline. Thanks!
Poornima

Alright, sounds good. Thanks again

Right. Would having that entire stretch of coastline in a relation solved the problem? Because, as far as I know, why this river looks like the way it does now was because the coastline was not in a relation connected to the end part of the river. The river continued until the end, according to one local mapper, and it was rendering completely until sometime in end May or June beginning, when the render broke. So I would say the actual issue was adding the coastline and not linking it to the river. So if the coastline would have been put in a relation, would the problem be solved?

Hi EivindWAA_import,
First of all, apologies that I didnt comment on your changeset before I made the repairs. I have not done any major changes to the actual coastline but just changed the tags of the upper part to riverbank, because not having the coastline made it break on osm and make the river mandalseva appear as a thin line. This was the reason why this edit was changed. I agree the import mentioned may the coastline extended but not having that in a relation caused that entire zone to appear as land with a thin stream of river flowing. If any issues, please let me know.
Thanks
Poornima Badrinath

Oh okay. Got it. Thanks! But changing it to a riverbank makes sense right?