Dear Oba510,
Thank you for your comment. I appreciate your context in this matter, and I agree with what you said. This tag was added previously by wvdp (https://osmlab.github.io/osm-deep-history/#/node/5674203236) on June 14, 2019. I removed this tag per OSM wiki barrier=* which states how to use this tag. In this case it doesn’t make sense to add barrier=kerb, since as you stated it would imply that there is a curb on the street that had to be driven/walked over.
Thank you,
Anu_lyft

Hi Glassman,
My name is Anu and I am a mapper on the OSM team at Lyft. Thank you for bringing this to our attention. Per OSMwiki barrier=* it doesn’t make sense to add barrier=kerb, as it would imply that there is a curb on the street that had to be driven/walked over. Please let me know if you have any further questions. Sorry for any inconvenience this may have caused.
Thank you,
Anu_lyft

Hello arkdatta,

My name is Anu and I work as a mapper on the OSM team at Lyft. While mapping in this area, I found 4 ways tagged incorrectly on 3rd Avenue way/391198727, way/634155259, way/634155255 and way/634155254, each of these has been modeled as oneway=yes. These 4 ways should be labeled as bi-directional. Looking at the history of these ways you added directionality on 29 December 2019 for this changeset/78975414. On 3rd Avenue connecting to Jefferson street intersection at this (node/202257186) starting from Harrison street should be bi-directional. It has been tagged as a bi-directional since May 8, 2018 modified by mapper ionutr_telenav which was correct.

The split starts at Jo Johnston Avenue and goes Northwest to Harrison Street for way/633979659 however, this is the only way on 3rd Avenue in the area that should be tagged as oneway=yes.
Can you please revert the changes to reflect the current state of imagery? If you have more current information on this area that discounts this information, any help would be greatly appreciated.

Thank you,
Anu_lyft

Hello dufekin,

My name is Anu and I work as a mapper on the OSM team at Lyft. While mapping in this area, I found some discrepancies regarding St Ferdinand St way/12633005, way/181653702 and way/181653709. Each of these has been modeled as oneway =yes. Looking at the history of these ways you added directionality on 12 July 2012 for this changeset/12193906. St Ferdinand St starts from the intersection of North Boulevard (node/115263476) until South Boulevard intersection (node/1821126612). According to Mapillary street side Imagery 2018, presently the street is bi-directional. Along with this change, we need to change directionality for Saint Louis Street which needs to be updated from a oneway to a bi-directional way as it runs parallel to St Ferdinand St from South Boulevard until North Boulevard. Again, directionality was added on 15 July 2012 for this changeset/12182556. Can you please revert both changesets, and correct the changes to reflect the current state of imagery? Or if you have another recent source that discounts this change, could you please provide further information on this?

Thank you,
Anu_lyft

Hello anurasi,
My name is Anu and I work on the OSM Editing team at Lyft.
While mapping in this area, I noticed a way mapped as a oneway=yes near 2nd and 3rd street.
Here is the link way/103020635 and the changeset/60780756.
It is my understanding that the way is bi-directional and should not be tagged as a oneway.
I was wondering if you had a recent resource that denoted this road segment as a oneway?
If I do not hear from you by Friday January 24th, 2020, I will go ahead and make the changes.
Thank you,
Anu_Lyft

Hello Muziriana,
I am currently mapping freeway I-880 South area and noticed that you added junction:ref=26 on this way from this node node/1684055215 on ward until way way/516003135 meets the motorway.
I believe that junction:ref=26 is not needed on this portion of way. Can you please revert changeset? Additionally if you have more recent information regarding this area, please let me know.
Thank you,
Anu_Lyft

Hello G1asshouse,
Thank you for bringing this to my attention. It was not my intention to remove the turn restriction here. Here is the link to the node node/53162660 and the changeset/78168027. Please feel free to take a look. I appreciate your help and will make sure to avoid these situations in the future by double checking my work before uploading.
Thank you,
Anu_lyft

Hello G1asshouse,
Thank you for bringing this to my attention. It was not my intention to add the turn restriction here. Here is the link to the node node/59713094 and the changeset/76177138. Please feel free to take a look. I appreciate your help and will make sure to avoid these situations in the future.
Thank you,
Anu_lyft

Hi StellanL,
I was working on editing way/392620051 and saw that it intersected this building way/27132458. After further review it looks like in this change-set the building (way/27132458) was created with (way/27132423). These seem like duplicates, with one having more detail than the other. After asking DannyAiquipa, they said to ask the oldest user how to go about fixing what seems like duplicate buildings with one of them intersecting a road.

I would love to fix these duplicate buildings, but wanted to confirm these errors with you.

Happy Mapping,
Anu