Hello Oba510,

Thanks for bringing this to my attention. I mistakenly made the edit without checking the way history first. I will make sure to do so in the future. Thank you for correcting my previous changeset. I apologize for any inconvenience this may have caused on your part.

Thank You,
Clayton

Hello Roadsguy,

My name is Clayton and I work on the OSM editing team for Lyft. While working in this area I came across this way: way/540346294 that was tagged with destination:ref:DE 1 South as well as other onramp tags. Way segments between on and off ramps should not have the destination:ref tags of the onramp as it affects routing. For example, following the destination tags, the exit would not be able to route to the other side of Pulaski Highway. If you would be so kind as to provide a source of evidence for this change or remove the onramp tags on the way you edited on your previous changeset changeset/63714599 it would be greatly appreciated.

Thank You!
Clayton

Hello TeresaPeteti,

My name is Clayton and I work on the OSM editing team for Lyft. While working in this area I came across this way: way/538669651 that was tagged with destination:ref: I 80 West;I 580 East. Way segments between on and off ramps should not have the destination:ref tags of the onramp as it affects routing. For example, following the destination tags, the exit would not be able to route to the other side of University Avenue. If you would be so kind as to provide a source of evidence for this change or remove this tag on the way you edited on your previous changeset changeset/53546350 it would be greatly appreciated.

Thank You!
Clayton

Hello ranjithjoy,

My name is Clayton and I work on the OSM editing team for Lyft. While working in this area I came across this way: way/436414404 that was tagged with destination:ref:I 805 North. Way segments between on and off ramps should not have the destination:ref tags of the onramp as it affects routing. For example, following the destination tags, the exit would not be able to route to the other side of El Cajon Boulevard. If you would be so kind as to provide a source of evidence for this change or remove this tag on the way you edited on your previous changeset changeset/53942466 it would be greatly appreciated.

Thank You!
Clayton

Hello LocalTrailgeek,

My name is Clayton and I work on the OSM editing team for Lyft. While working in this area I came across this node: node/374086798 that was tagged ref:12A. Using the latest Mapillary street imagery, the exit for this particular junction is 12B instead of 12A. Exit 12A is found further ahead at this node:node/374090903. Would you be so kind as to swap the ref tags for these two nodes edited on your previous changeset changeset/34870821? This would be greatly appreciated.

Thank You!
Clayton

Hello marthaleena,

My name is Clayton and I work on the OSM editing team for Lyft. While working in this area I came across this way: way/274715822 that was tagged with destination:ref:I 75 North. Way segments between on and off ramps should not have the destination:ref tags of the onramp as it affects routing in a negative way. For example, following the destination tags, the exit would not be able to route to the other side of North Marietta Parkway. If you would be so kind as to provide a source of evidence for this change or split the way and remove this tag on the way you edited on your previous changeset changeset/53362466 it would be greatly appreciated.

Thank You!
Clayton

Hello Freedom Editor,

My name is Clayton and I work on the OSM editing team for Lyft. While working in this area, I came across this way way/604642464 that was tagged with destination:street:Veterans Memorial Highway. According to the OSM wiki for destination subkeys: (osm.wiki/Proposed_features/Destination_details), the destination:street tag should be used for named streets instead of names assigned to highways. In addition, I was unable to locate signage indicating that the Veterans Memorial Highway was one of the named destinations. If you would be so kind as to remove this tag from the ways you edited on your previous changeset changeset/71782334 or otherwise change the tag to destination: Veterans Memorial Highway to better reflect the road type it would be greatly appreciated.

Thank You!
Clayton

Hello SSR_317,
My name is Clayton and I work on the OSM editing team for Lyft. While working in this area, I came across this way way/590629983 that was tagged with junction:ref:2. According to the OSM wiki for the junction:ref tag: (junction:ref=*), the junction:ref tag should only be used to indicate exit numbers according to signage along a road. Since this way is an onramp, it is unlikely to have an exit number associated with it. Furthermore, I was unable to locate any signage corresponding to an exit number for this way using street imagery. If you would be so kind as to provide a source for your change or revert your previous changeset changeset/76565263 to reflect this change it would be greatly appreciated.

Thank You!
Clayton

Hello Iowa Kid,

My name is Clayton and I work on the OSM editing team for Lyft. While working in this area, I came across this way way/15375585#map=19/30.33508/-97.75416 that was tagged as destination: Loop 1 North. according to the OSM wiki: (osm.wiki/United_States_roads_tagging#County_Highways) under Texas state highways, loop roads should instead be classified with ref tags as they are considered highways. Therefore, the correct tag to use would be destination:ref:Loop 1 North. Can you please revert your previous changeset changeset/27145704#map=19/30.33508/-97.75416 to reflect this change it would be greatly appreciated.

Thank You
Clayton!