Hi roadgeek99,
Thank you for bringing this to our attention. I apologize for breaking the relations on NW Flanders St. Reemal_lyft was adding some tags to several ways, and a boundary was attached, to a small section of a way, so when he merged the ways, the boundary stretched itself which caused it to look the way it did. We have since fixed the issue, see changeset changeset/85166349#map=17/45.52566/-122.69085. We will make sure to take our time double checking possible boundaries in the future. Sorry for any inconvenience this may have caused.
Thank you,
Lisa

Hello oba510,
Thanks for letting us know that there have been recent changes in this area. We apologize for making this change without first checking on city resources. Sorry for any inconvenience this may have caused.
Thank you,
Lisa

Hi Ob510,
Thank you for bringing this to our attention. It looks like our editor clicked the wrong turn restriction in error. This changeset has since been fixed please see here: changeset/80861177. We will be sure to be more careful in the future.
Thank you,
Lisa

Hi skquinn,
To clarify, this individual is new to mapping turn restrictions. Mapping for Lyft, we hold ourselves to very high standards for OSM mapping.
Thanks again,
Lisa

Hi skquinn,
Thank you for bringing this to our attention. Upon looking at this area, it seems you are correct. Thanks for making the appropriate changes in the meantime. We are mapping turn restrictions in the area, and rserezo_lyft is still new to our mapping team, so he mapped a turn restriction in error due to the way OSM was modeled. Unfortunately we didn't get a chance to QC this, and make the change before you came across it. I appreciate you making the changes and correcting the map. Sorry for any inconvenience this may have caused you.
Thank you,
Lisa

Hi user_5389,
Thank you for your concern in this matter. After diving deeper into her history, she did not add that key, rather, she added a turn restriction to the node here. As a courtesy, xiuxialiu has made the correction per your request. Please see changeset ID 79432081. Sorry for any confusion this may have caused.

Thank you,
Lisa

Hi TheBestIdea,
Thank you for identifying the error made by abaker_lyft. We appreciate you reverting our previous changeset. Sorry for any inconvenience this may have caused.
Thank you,
Lisa

Hi clay_c,
We apologize for any work that was undone previously. OttoBisno split the way to add parking tag data. It was not our intention to delete any trolleybus route relations. I have updated the parking tags per changeset #76123559. Feel free to look over it. Thank you for reverting our past changeset.
Thank you,
Lisa

No worries. I appreciate the quick response. I will take care of these for you.

Thank you!
lrw2

Hi Mapman44,
I came across the 'barrier=kerb' tags you added at the intersection of Oregon Exway and Louis Road, but it also had the 'kerb=lowered' tag. node/2318681460
In OSM wiki, it is the opposite of kerb=lowered and both should not be used together. It should be either or in this case. We understand that this has been a proposed tag push by idEditor, but it is not standard. I will be happy to remove these 'barrier=kerb' tags unless you have another source that disproves our current source.
barrier=*
Happy Mapping,
lrw2