Hello kadiwa,

Thank you for catching that and repairing it. I’ll try to be more careful to catch those before I upload them in the future.

Happy mapping,
VLD317

Thank you for the follow-up and for considering pedestrian routing. Since you've already made the adjustments, we will not edit it further. Happy mapping!

Thank you for bringing this to my attention. We had removed the link due to the presence of designated crosswalks that are separately mapped and which provide parking lot access. Since the link has been restored, we will not edit the feature further. Happy Mapping!

Hello Jarek,

Certainly! Here is the link for the Maproulette Challenge:

Toronto Missing Crossing Ways: https://maproulette.org/browse/challenges/42238

Happy mapping!
VLD317

Hello NE_SwampYankee,

Thank you for bringing this to my attention. Our team was not aware of the local standards for these driveways/alleyways in Cincinnati; Could you please direct us to the relevant discussion threads?

Best regards,
VLD317

Hi willkmis,

I apologize for my mistake. Thank you for catching that and re-adding the crossing! I will make sure to be more cautious going forward.

Thanks, VLD317

Hello OCD_Dakota_Mapper,

I noticed in changeset/177976955 that the classification of ways 117849484 and 117849485 was updated from highway=residential to highway=living_street. Since other similar neighborhoods in the area have streets classified as highway=residential, I wanted to confirm whether this change to highway=living_street was intentional.

Thank you for your work.

Best regards,
VLD317

Hello rskedgell, I appreciate the feedback. Our team has updated our guidelines for this region to account for both of these issues.

In regards to the sidewalk=* vs sidewalk:both/left/right=*, in other areas we have preferred to use the sidewalk:both/left/right=* format because it allows us to be a bit more specific, especially when the sidewalks are mapped separately. It is not a suggestion from rapID editor, just our efforts to be consistent with our tagging schemes. We realize now that the local community here prefers sidewalk=* and the team has been given guidance to avoid changing them going forward.

Thank you for your help with these features, I will keep this feedback in mind. -VLD317

I apologize for my mistake here. I see you have updated the tags already. Thank you for your feedback and insight into this crossing. -VLD317

No problem! Please continue to reach out with any local conventions you may be aware of as this is very helpful
-VLD317

Hello Benoît C MdP ,

I apologize for the oversight and appreciate your assistance in addressing these issues. Thank you.

-VLD317

Thank you for the response on my recent changeset. I reviewed my edits and made adjustments to the curbs where necessary. I apologize for any inconvenience this may have caused.

Thank you for the response on my recent changeset. I reviewed my edits and made adjustments to the curbs where necessary. I apologize for any inconvenience this may have caused.

Hello ChaireMobiliteKaligrafy,

I apologize for disrupting the alignment. Thank you for letting me know.

-VLD317
---

Published using OSMCha: https://osmcha.org/changesets/167274120

Hello Udarian,

I apologize for splitting the crossings. As I am relatively new to the team, I was not aware that this location was a special case.

Our team will take steps to prevent similar modifications to the features here moving forward.

Best regards,
VLD317

Hello Udarian,

I apologize for splitting the crossings. As I am relatively new to the team, I was not aware that this location was a special case.

Our team will take steps to prevent similar modifications to the features here moving forward.

Best regards,
VLD317

Hi willkmis,

I apologize for the incorrect edit here. Thank you for making the correction and letting me know, I will keep this feedback in mind.

VLD317