OpenStreetMap logo OpenStreetMap

Changeset When Comment
149434684 almost 2 years ago

Hi, Kovoschiz
Many thanks for reaching us.
You can find Lyft's dedicated page at osm.wiki/Lyft, which is also referenced in the Organized Editing/Activities section at osm.wiki/Organised_Editing/Activities, as per the guidelines.

For a comprehensive overview of our projects, we've provided a direct link to our GitHub repository on our wiki page.
Best,
Marina

149434684 almost 2 years ago

Hi, Friendly_Ghost
My name is Marina, and I’m a mapper on the OSM team at Lyft.
The barrier:keypad tag was recommended for use in a slack discussion with the OSM community: https://osmus.slack.com/archives/C2VJAJCS0/p1681734702769439
Additionally, we are following this proposal - osm.wiki/w/index.php?oldid=840159#Combinations_/_Subtags
The usage of this tag has increased because we have initiated a new project to incorporate it; more details are available here - https://github.com/Test-DCT/OSM-LYFT-DCT/issues/29
Thank you for your interest in our edits. I am happy to answer any questions you may have.
Best regards,
Marina

146670668 almost 2 years ago

Hi, emersonveenstra
My name is Marina, and I am a mapper on the OSM team at Lyft.
Thank you for paying attention to this issue. You are right, I made a mistake when I added roads in this area. Thank you so much for correcting the error, I’m so sorry for it. I will make sure to double check my mapping before I upload it in the future.

Best regards,
Marina

133934124 almost 2 years ago

Hi, Mateusz
My name is Marina, and I am a mapper on the OSM team at Lyft.
Thank you for your message, and for catching this error! You are right, I made a typo when adding the tag, I have updated the inaccuracies per changeset https://pewu.github.io/osm-history/#/node/10750433566, I will be more attentive next time.
Best regards,
Marina

126978406 almost 2 years ago

Hi, Mateusz
Thank you for bringing this to my attention and for correcting the error, I will be more attentive next time.
Best regards,
Marina

126994087 almost 2 years ago

Hi, Mateusz
My name is Marina, and I am a mapper on the OSM team at Lyft.
Thank you for paying attention to this issue. You are right, I made a mistake when adding the tag. Thank you so much for correcting the error, I will be more attentive next time.
Best regards,
Marina

145433979 about 2 years ago

Thanks for sharing your thoughts on this. It seems that at the moment the info in the video does not correspond to the actual traffic situation. According to Lyft-owned sources the ways you mentioned were driven this week: on average 920 passes per day by Lyft drivers. Probably it is a phased road closure: at first one motorway link was open and another closed, and in the near future the part of the I 395 shown in red in the video will also be closed. In accordance with our rules, we shouldn’t tag ways with construction if there is evidence that the road is driveable. As soon as the situation changes, most likely we will be able to notice it promptly and correct it.

Best regards,
Marina

145433979 about 2 years ago

Hi, Udarian
My name is Marina, and I am a mapper on the OSM team at Lyft.
Thank you for bringing this to my attention. After I took a detailed look at all the ways connected to the link I edited, I added a construction tag only to I 395 exit based on the reconstruction project and Lyft-owned sources - the changeset changeset/145534625. According to our data, there have been no drivers passing on this motorway link since December, 21.
However, I'm assuming the I 395 is still accessible for drivers since there are passes along it. If you have more recent data, we would appreciate it if you could make changes based on it.
Best regards,
Marina

140833763 over 2 years ago

Hi, oba510
My name is Marina, and I am a mapper on the OSM team at Lyft. Thank you so much for paying attention to this.
When removing the barrier, we used Lyft-owned sources: Nearmap background, telemetry data, and street-level images. The road is drivable according to our telemetry data - https://drive.google.com/file/d/1uJFvXWHiiuFXwfZFJyGceWvKipUKCnmt/view?usp=drive_link. According to the image (photo taken from Ellsworth Street, 37.867828, -122.263685) - https://drive.google.com/file/d/1oyMZGIQupiaP0e7gAhj8yNbN1n3Ck7yh/view?usp=drive_link,
there is a barrier only on one lane and not on the entire road, and it doesn’t interfere with the traffic of cars. According to the OSM wiki, a barrier is a physical structure that blocks or impedes movement - barrier=*#:~:text=A-,barrier%20is%20a%20physical%20structure%20which%20blocks%20or%20impedes%20movement,-.%20The%20barrier%20tag. It seems that it’s better not to add a barrier on this section of the road, since one of the lanes is entirely accessible to traffic and the presence of a barrier may prevent navigation through this section of the road.
Best regards,
Marina

139022474 over 2 years ago

Hi, Baloo Uriza
My name is Marina, and I am a mapper on the OSM team at Lyft. Thank you so much for paying attention to this.
The OSM wiki has two approaches to tagging lanes count. We use both of them.
In this case, we use information from the article on the OSM wiki and added lanes=3: “If the number of lanes changes, it is necessary to split the OSM way. This should be done as soon as a new lane has started (regardless of width)...” (lanes=*#:~:text=for%20further%20details.-,If%20the%20number,-of%20lanes%20changes ).
According to another article in OSM Wiki (osm.wiki/Lanes#:~:text=is%20an%20intersection.-,Street,-Here%2C%20a%20residential ), only a fully formed turn lane can be included into the lane count (i.e. a turn lane transition area marked with dashes where the lane begins to form do not include into the lane count since it is not fully formed).
In our opinion, these 2 articles contradict each other and become a source of confusion. We assume that both methods can be correct. If you know any other details that can clarify the current state of this area, we'll be happy to work on this further. Thank you so much for your contribution!
Best regards,
Marina

136788657 over 2 years ago

Hi, Horza
My name is Marina, and I am a mapper on the OSM team at Lyft.
Thank you for your attention to this case. According to Lyft-owned images from 03/24/23 (https://drive.google.com/file/d/1r-tNv3AyTRYRPRKspZeQhV5p4TSLhZML/view?usp=drive_link, https://drive.google.com/file/d/1BoEQh0j0oNvUGleZBzKFtO6iTNQUYXg3/view?usp=drive_link - 30.448911, -81.579149) the left two lanes are closed due to construction work and traffic is organized along the right two lanes as bidirectional. We have shifted the road according to these photos and GPS tracks of drivers. However, we see that, according to official resources https://mobilityworks.jtafla.com/projects/alta-drive-south-of-faye-road-north-to-burkit-lane/ and https://mobilityworks.jtafla.com/, this road is closed and traffic is detoured (this is also evidenced by the GPS tracks of our drivers - https://drive.google.com/file/d/1j2TpxfxglyWAYc-L4vFtt0eWoDcX3QHw/view?usp=drive_link ). The changes were made based on the data at the time of publication of the changeset. We usually don't make edits for short-term builds, but since we've edited the road in this case, we'll be monitoring the progress of the construction works. And we will be able to make the necessary changes after the construction is completed and when new sources of data appear for editing.
Best regards,
Marina

131053026 almost 3 years ago

Hi, Baloo Uriza
My name is Marina, and I am a mapper on the OSM team at Lyft. Thanks for bringing this to your attention. At this point in the OSM wiki, there isn’t any definition of when the destination:street tag is used (osm.wiki/Item:Q1221). At the same time, there are several discussions about the tag usage:
Talk:Proposed features/Destination details (osm.wiki/Talk:Proposed_features/Destination_details#destination:street?:~:text=(talk)-,destination%3Astreet%3F,-I%27ve%20seen%20the);
Proposed features (osm.wiki/Proposed_features/Destination_details#destination:street:~:text=language%20code%3A%20en);
Discuss destination:street (https://github.com/osmandapp/OsmAnd/issues/3592).
We adhere to the logic according to a proposal from Minh Nguen: osm.wiki/User:Minh_Nguyen/destination:street. There are some examples of the same opinion: the comment (changeset/132993570) to the changeset, or discuss in Slack (https://app.slack.com/client/T029HV94T/C2VJAJCS0/thread/C2VJAJCS0-1655772384.310139), where mappers refer to this proposal.
If you have more information about this tag, we would be very grateful to you for sharing it. We would really like to learn more about the use of ‘destination:street’ in order to apply it in the most correct way.
Best regards,
Marina

128723019 about 3 years ago

Hi, pretzel_raccoon.
My name is Marina, and I am a mapper on the OSM team at Lyft. Unfortunately, it's not entirely clear to me what kind of edits you mean. There is some pretty complex road geometry in this area, but I have added only two gates based on Bing Streetside view images in the changeset https://osmcha.org/changesets/128723019/. Anyway, thank you for your comment.
Best regards,
Marina

124623287 over 3 years ago

Hi, impiaaa!
My name is Marina and I am a mapper on the OSM team at Lyft. Thank you for paying attention to this. Indeed, all *:lanes tags should match each other. I'm so sorry for missing the 'hov:lanes' tag here. I have already removed it in the changeset changeset/127029210.
Thank you for your contribution!

Best regards,
Marina