Hi,
Thank you for your suggestion, on checking way/5783065, private access has been given by some other OSM user, and based on the resources available to us ,street view and aerial images, we don't find any changes. Would be happy to learn and make the changes if you find any. Going forward, I will keep that in mind for my future edits. Looking forward to learn more from you.
Best Regards,
Amanura

Hi,

As rightly pointed out, the Amazon delivery agents will not be allowed to pass through the gates tagged with "access:delivery=no".
Please let us know if there are any concerns, we will be happy to help. Delighted to have this conversation with you.

Regards,
Amanura

Hi,
Apologies for the miss from my end. I have now added access = private to the service road based on your feedback as a part of change set (123525100). Happy to learn from you.
Best Regards,
Amanura

Hi,

Please accept my apologies for the delay in responding. Thank you for looking into the change set. We have added access:delivery=no tag based on the driver feedback.We have started adding this tag based on OSM community suggestion. If you are local or going to survey this location please make the appropriate changes or let us know, we would be happy to update the map. For further information, kindly go through this diary post: @jguthula/diary/392437.

Thanks and Regards,
Amanura

Hi MacLondon,

Thanks for pointing this out to me. I happened to miss checking the Turn restrictions and hence I have turned the street to a one-way. Apologies for the miss and thanks for making the necessary corrections. Always happy to learn from the community.

Best Regards,
amanura.

Hi Tomhukins,
Apologies for the misinterpretation of the access tag. I have added access=private based on the presence of a gate at the beginning of the entity. I might have missed designation=public_footpath tag which made my edits contradictory. I have now deleted the access= private tag as per your suggestion. Please find the changeset (109443984) with modifications. Happy to learn this from you.
Regards,
Amanura

Hi Trigpoint,
Sorry for the delay in response as i was in long leave.
Thanks for looking into my edits. As the history dated 2012. I misjudged it to be an outdated edit. However, as I was unaware I have digitized a new service road as per Bing aerial imagery. Apologies for the genuine miss. I agree that aligning the segment as per the latest imagery would be more apt in this scenario. Please find the changeset (104628953) with suggested modifications.
Thanks for the constructive feedback.
Good Day!
amanura

Hi ,
Thankyou for looking into our edit and explaining us the actual ground scenario.
Regards,
Amanura

Thanks for looking into our edits. Apologies for the misalignment. It is good to see the community improvising our edits. Going forward, I will make sure to prioritize the vicinity over the clear imagery. Thanks for your suggestions. Always happy to learn from the community.

Thanks for checking into our edits. Apologies for the wrong connectivity. It is good to see the community improvising our edit quality. Thanks for the correction. Always happy to learn from the community

Hi MxxCon,
Thanks for looking into my edit and the feedback on the right way of mapping this feature. I have reverted my edit as per your suggestion, I will consider this learning in my future edits.
Regards,
Amanura

Thanks for checking into our edits. We have reverted the changeset and made the necessary changes. Thanks for the heads up. I will make sure to check the entire vicinity for the offset before making the edits. Always happy to learn from the community
Regards
Amanura

Thanks of checking our edits. I have enabled all the imagery to check its availability in the OSM and make necessary changes. All the enabled sources are auto populated while saving the edits. Apologies, I have not modified the sources before saving the edits. Thanks for the suggestions. Going forward, I will be modifying the sources used accordingly. Always happy to learn from the community.
Amanura

Thanks for your inputs. I have missed checking the latest imagery, post your inputs I have verified this location with our 2019 private imagery where the location is under construction. So please do suggest me what to do in this case as reverting the changes also might not correct the accurate data in this location. Do suggest the necessary changes required. Always happy to learn from the community

Thanks for checking our edits. This edit is partially based on our driver feedback and available resources. I had cross verified my edits and made the necessary corrections. please find the changeset(83470001) for the suggested modifications. always happy to learn from the community.

Thanks for your time for checking our edits. It was a mistake from our end. Reverting the changes as per the suggestion. Please find the changeset (82428040) for modifications. Always happy to learn from the community