Hello SafetyIng,
Thanks for bringing this up to me. I have rechecked the wiki page for highway=track. I have modified the road classifications as per wiki and your suggestions(changeset :- 111200043). Thanks again for reminding this to me. Happy day! Regards,
bathines

Hi,
As per bing aerial imagery, the road condition seems to be not very ideal for vehicles, as there are track marks and vegetation. Also, there is no vehicle presence proof as per the available resources in OSM. Hence, I have tagged it as highway= track. I assumed the single entity to be a farm house or warehouse for farm utility. I have now modified the tags as per your suggestion.
Thanks for your valuable feedback.
Regards,
bathines

Hi,
Thanks for the feedback. I have now converted the segment to driveway based on you feedback (changeset: 106971168). Apologies for the inconvenience.
Regards,
bathines

Hi,
Thanks for the Quick turn around. I have made the changes as per your suggestions (Changeset:104387240 ).
Good Day!

Hi,
Thanks for looking into my edit. I have added segment as per available OSM resources. As I was unaware of the type of entity. I have not added service = driveway. Kindly, confirm the same so that we can add the appropriate tag.

Hi,
Thanks for looking into my edit. I have added segment as per available OSM resources. As I was unaware of the type of entity. I have not added service = driveway. Kindly, confirm the same so that we can add the appropriate tag.

Hi,
Thanks for checking my edits. I have added the missing segment as per available OSM resources as I was unaware of the building type I have added highway = service. But, As it is a residential area, in this scenario it would be more apt to tag it as a driveway. Please find the changeset (104258361 )with suggested modifications. Apologies for the miss.
Regards.

Hi,
I have added the missing segment as per the available OSM resources. As there was no information regarding the entity , I was unaware that it was a depot. Thanks for correcting my edit. Always happy to learn from the community.

Hi,
I have turned on mappilary overlay to check if they are present, but id editor has auto captured it in the imagery used column. As it is already saved we would not be able to change the captured data. Will keep a check in our future edits.
Thanks

Hi,
Thanks for the quick turn around. As mentioned above the media source got auto captured into the changeset. I am unsure on how to remove it. Kindly, help me out incase you have any idea on editing these before saving the edits. Always happy to learn from community.

Hi,
Thanks for looking into our edits. I have added the segments based on Maxar imagery and esri world imagery available in OSM as bing aerial imagery does not have vintage displayed. I have also verified all the available resources in OSM to make the edit which is why all the resources are auto captured in the id editor for my changeset. I am unsure of why is it populating as imagery used when i havent used the mappilary in this area. However, As per bing the path seems to be blocked for vehicles, Hence, I have modified the segment as per your suggestion (changeset/104117523). Please let me know in case of any other modifications. Thanks for your constructive feedback.

Thanks for checking into our edits. I have added the turn restriction based on the mapillary street level imagery. I have not modified the bicycle access as there is no valid evidence to add the restriction. It can be helpful if your local knowledge can improvise our edit quality. Please let me know if anything else needs to be modified. Always happy to learn from the community.

Thanks for checking into our edits. I have not changed the existing road as I don't have enough resources to make the change. please find the suggested modifications in the changeset 98357482. It is good to see the community improvising our edit quality. Always happy to learn from the community.

Thanks for checking into our edits. My sincere apologies for the missed attributes. Going forward, I will make sure to add all the features before saving my edits. Once again, Thanks for the correction. I will take this as a learning from the community and make sure to implement it in my future edits. Always happy to learn from the community.

Thanks for checking into our edits. I have misinterpreted the road as parking aisle. Thanks for improvising my edits. I will take this as a learning from the community and make sure to implement in this future edits. Always happy to learn from the community.

Hi, thanks for checking into our edits. I have added the barrier based on the internal driver feedback and OS open data. I have added the note so that the community would validate it with the ground reality. Thanks for the modification, it is good to see the community improvising our edits. Always happy to learn from the community.

Thanks for your valuable suggestions. it is good to see the community improvising our edits. Going forward, I will make sure to consider the access tags of the adjoining paths before making the edits. I will take this as a learning from the community and make sure to implement in my future edits.

Hi Chris Fleming,
Thanks for looking into our edits. I have made this edit based on the aerial imagery, it is little ambiguous as it is partially covered by vegetation. Apologies, if it is contradicting with the ground reality. Please find the changeset (86114229) for the suggested modifications. Always happy to learn from the community
Thanks
bathines

Hi messpert
Thanks for looking into our edits. We have made the edits based on our driver feedback and available resources. Please go ahead and make the necessary changes or do suggest me with the changes required to improve the map quality. we acknowledge that the ground knowledge always improves our edit quality. Always happy to learn from the community.
thanks
bathines

Hi OSM_RogerWilco,
Appreciating your time for checking my edits. After further deep dive, we realized that it is an error from our end and rectified it. Please find the changeset (81175723) for the suggested modifications. Always happy to learn from the community.
regards
bathines