Hi all (-tagging and talk-ca as this just relates to mapping locally here in the US),
Just to follow up on this, our team is starting to do some freeway exit tagging updates in the Detroit area and they are using destination:street — and the ‘destination’ tagging schema in general — as discussed back in February on this thread. This is the start of some US editing projects that our team is going to be working on in the near future. We will be back with more detail on that soon. In the mean time, you can recognize any of our team members by their OSM usernames ending in _telenav. They are a friendly bunch[1] and eager to hear your comments on their work. You can also always reach out directly to me with questions or concerns. Martijn [1] here’s some of them: http://blog.improve-osm.org/wp-content/uploads/2016/11/Map-2.jpg <http://blog.improve-osm.org/wp-content/uploads/2016/11/Map-2.jpg> > On Feb 2, 2017, at 8:14 AM, Duane Gearhart <du...@mapzen.com> wrote: > > Hey Martijn, > > Apologies for my delay getting back to you. > > As suggested - I added a link on the destination page [1] > > For this location [2] the interchange information would look like this: > destination=West Valley > destination:ref=UT 201 West > destination:street=1300 South;2100 South > as updated here [3] > Note how the destination:street values follow the OSM pattern of spelling out > street names. Also, the semicolon separated names are easily read into a a > list of exit branch street names. > > If user would would continue and take exit 305C onto 1300 South [4] as > captured here [5] > then the software can rank, sort, and collapse the consecutive exit > information - therefore, "1300 South" would take precedence over "2100 South" > I briefly discussed this at SotM US 2015 [6] at 12:23 into the video. > > I can follow-up with you after the OSM data has been processed with recent > edits. > > Regards, > Duane > > [1] http://wiki.openstreetmap.org/wiki/Key:destination#See_also > <http://wiki.openstreetmap.org/wiki/Key:destination#See_also> > [2] http://openstreetcam.org/details/8230/168 > <http://openstreetcam.org/details/8230/168> > [3] http://www.openstreetmap.org/way/37192513 > <http://www.openstreetmap.org/way/37192513> > [4] http://openstreetcam.org/details/8230/181 > <http://openstreetcam.org/details/8230/181> > [5] http://www.openstreetmap.org/way/32028378 > <http://www.openstreetmap.org/way/32028378> > [6] https://www.youtube.com/watch?v=hwglqOV6I9M > <https://www.youtube.com/watch?v=hwglqOV6I9M> > > > > On Fri, Jan 20, 2017 at 3:02 PM, Martijn van Exel <m...@rtijn.org > <mailto:m...@rtijn.org>> wrote: > Hi Duane, > > Thanks. I had overlooked the examples page (even though I searched the OSM > wiki for the exact term!) > I do appreciate the granularity of the destination:street tagging and would > encourage the Telenav mappers to use it as well then, but we like to stick to > conventions that are properly documented (not only in an example page). Since > there is significant usage in N-America and some other regions [1], we could > add it to the destination tag page [2]? > > My only issue with destination:street is that there’s still ambiguity when > more than one street is on the sign, like here [3]. Would that then be > destination:street=1300 So.;2100 So. and destination:ref=201 and > destination:West Valley? The advantage of having a separate tag partly > vanishes when you still need the semicolon separator? > > Martijn van Exel > > [1] http://taginfo.osm.org/keys/destination%3Astreet#map > <http://taginfo.osm.org/keys/destination:street#map> > [ <http://taginfo.osm.org/keys/destination:street#map>2] > http://wiki.openstreetmap.org/wiki/Key:destination > <http://wiki.openstreetmap.org/wiki/Key:destination> > [3] http://openstreetcam.org/details/8230/168 > <http://openstreetcam.org/details/8230/168> > > <http://taginfo.osm.org/keys/destination%3Astreet#map> > > <http://taginfo.osm.org/keys/destination%3Astreet#map> >> On Jan 19, 2017, at 5:44 PM, Duane Gearhart <du...@mapzen.com >> <mailto:du...@mapzen.com>> wrote: >> >> Hey Martijn, >> >> It looks correct to me - using the destination:street allows users to know >> if the ramp is branching onto the specified street name vs. heading toward a >> street name - examples are located here: >> http://wiki.openstreetmap.org/wiki/Exit_Info#Road_name_Example >> <http://wiki.openstreetmap.org/wiki/Exit_Info#Road_name_Example> >> >> Mappers have been using in the US too: >> http://overpass-turbo.eu/s/ln4 <http://overpass-turbo.eu/s/ln4> >> >> Here is an example way: >> https://www.openstreetmap.org/way/11502773#map=19/39.21853/-76.65894 >> <https://www.openstreetmap.org/way/11502773#map=19/39.21853/-76.65894> >> >> You can see how it is used in the directions: >> https://www.openstreetmap.org/directions?engine=mapzen_car&route=39.22079%2C-76.65959%3B39.22139%2C-76.65428 >> >> <https://www.openstreetmap.org/directions?engine=mapzen_car&route=39.22079%2C-76.65959%3B39.22139%2C-76.65428> >> >> Regards, >> Duane >> >> >> >> >> On Thu, Jan 19, 2017 at 8:00 PM, Martijn van Exel <m...@rtijn.org >> <mailto:m...@rtijn.org>> wrote: >> Hi all, >> >> The Telenav mapping team noticed quite a few destination:street tags on >> (mostly) motorway_link off-ramps in Canada. This is an undocumented sub-tag >> of the destination tag so I am curious how it is being used and if there is >> some sort of consensus that is documented somewhere else than the OSM wiki. >> >> An Overpass query surfaced 1883 cases, http://overpass-turbo.eu/s/ln2 >> <http://overpass-turbo.eu/s/ln2> >> >> Looking at a random one, http://www.openstreetmap.org/way/34154734 >> <http://www.openstreetmap.org/way/34154734> / >> http://openstreetcam.org/details/10767/4194 >> <http://openstreetcam.org/details/10767/4194> — I think in the US we would >> just map this as destination=Carman Road;Iriquois and destination:ref=1 >> >> So my question is whether this is some relic of a past practice, or is this >> actively used and encouraged mapping practice and if so, where should it be >> documented? >> (https://wiki.openstreetmap.org/wiki/Proposed_features/Destination_details >> <https://wiki.openstreetmap.org/wiki/Proposed_features/Destination_details> >> seems to be a good candidate.) >> >> We’re happy to help improve these tags based on OSC / Mapillary data but I >> wanted to make sure first that this is the way you all want to go. >> >> Happy mapping, >> >> Martijn van Exel >> >> >> _______________________________________________ >> Tagging mailing list >> tagg...@openstreetmap.org <mailto:tagg...@openstreetmap.org> >> https://lists.openstreetmap.org/listinfo/tagging >> <https://lists.openstreetmap.org/listinfo/tagging> >> >> >> _______________________________________________ >> Talk-us mailing list >> Talk-us@openstreetmap.org <mailto:Talk-us@openstreetmap.org> >> https://lists.openstreetmap.org/listinfo/talk-us >> <https://lists.openstreetmap.org/listinfo/talk-us> > >
_______________________________________________ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
