[Tagging] Follow up on destination= and destination:ref=
Hi, (I am sorry if this message appears twice - I wasn't yet subscribed to this list with my Telenav account.) I posted about destination= and destination:ref= a few days ago, linking to my diary entry. I have since received a lot of useful comments. I just wanted to bump this topic because all the discussion has been going on there and not on the list: http://www.openstreetmap.org/user/mvexel/diary/22419#comment27109 Here at Telenav, we have now adopted destination= and destination:ref= for signpost information. We have two people adding information about signposts where they don't exist, prioritizing corridors that are of particular importance to us. You can follow their work here: http://www.openstreetmap.org/user/Dami_D/history http://www.openstreetmap.org/user/ChrisZontine/history We are not removing or replacing existing exit_to tagging. We are focusing on exits that don't have signpost information at all yet. We are also building support for this convention into our OSM model, retaining the existing support for exit_to for now. From the comment thread on my diary entry I get the feeling that there is some sense of agreement that we can move towards finally deprecating exit_to. As much as I would love to, that would require more discussion around what we will do with the existing exit_to tags, support in editors, etc. I would like to start talking about these things, but not before I am comfortable that we want this as a community. -- Martijn van Exel http://oegeo.wordpress.com/ http://openstreetmap.us/ ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Follow up on destination= and destination:ref=
Hi! 2014-07-10 15:43 GMT+02:00 Martijn van Exel m...@rtijn.org: Here at Telenav, we have now adopted destination= and destination:ref= for signpost information. Great news! I just came back from my holidays where we used Skobbler (I guess you know it ;-) ) for navigation and it was hell. Skobbler desperately needs that kind of information. Just a brief summary for everyone who's never used the key destination and its sub-keys: * The key destination=* describes the direction of the highway by using the name of the city the highway is heading to. [1] * There are some proposed sub-keys to provide further information, e.g. destination:ref to provide the reference of the highway this highway is heading to. [2] * The JOSM style Land and road attributes [3] has rudimentary support for destination, destination:ref, destination:int_ref and destination:country, so you are able to see that kind of information while editing in JOSM. Best regards, Martin [1] http://wiki.openstreetmap.org/wiki/Proposed_features/Destination_details [2] http://wiki.openstreetmap.org/wiki/Proposed_features/Destination_details [3] http://josm.openstreetmap.de/wiki/Styles/Lane_and_Road_Attributes ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Follow up on destination= and destination:ref=
Hi Martin, and others, I need to clarify that for the time being the Skobbler apps use a different engine than the Scout U.S. apps. My work is focused mostly on the Scout U.S. apps for now, and the improvements I am working on will only benefit Scout U.S. for now. That said, we are working on tighter integration of the products, so that all the work we do on OpenStreetMap benefits all our apps. In the mean time, let me ask the Skobbler team what their usage of destination* is. -- Martijn From: Martin Vonwald imagic@gmail.commailto:imagic@gmail.com Reply-To: Tag discussion, strategy and related tools tagging@openstreetmap.orgmailto:tagging@openstreetmap.org Date: Thursday, July 10, 2014 at 8:20 AM To: Tag discussion, strategy and related tools tagging@openstreetmap.orgmailto:tagging@openstreetmap.org Subject: Re: [Tagging] Follow up on destination= and destination:ref= Hi! 2014-07-10 15:43 GMT+02:00 Martijn van Exel m...@rtijn.orgmailto:m...@rtijn.org: Here at Telenav, we have now adopted destination= and destination:ref= for signpost information. Great news! I just came back from my holidays where we used Skobbler (I guess you know it ;-) ) for navigation and it was hell. Skobbler desperately needs that kind of information. Just a brief summary for everyone who's never used the key destination and its sub-keys: * The key destination=* describes the direction of the highway by using the name of the city the highway is heading to. [1] * There are some proposed sub-keys to provide further information, e.g. destination:ref to provide the reference of the highway this highway is heading to. [2] * The JOSM style Land and road attributes [3] has rudimentary support for destination, destination:ref, destination:int_ref and destination:country, so you are able to see that kind of information while editing in JOSM. Best regards, Martin [1] http://wiki.openstreetmap.org/wiki/Proposed_features/Destination_details [2] http://wiki.openstreetmap.org/wiki/Proposed_features/Destination_details [3] http://josm.openstreetmap.de/wiki/Styles/Lane_and_Road_Attributes ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Follow up on destination= and destination:ref=
Am 10.07.2014 15:43, schrieb Martijn van Exel: Hi, (I am sorry if this message appears twice - I wasn't yet subscribed to this list with my Telenav account.) I posted about destination= and destination:ref= a few days ago, linking to my diary entry. I have since received a lot of useful comments. I just wanted to bump this topic because all the discussion has been going on there and not on the list: http://www.openstreetmap.org/user/mvexel/diary/22419#comment27109 Here at Telenav, we have now adopted destination= and destination:ref= for signpost information. We have two people adding information about signposts where they don't exist, prioritizing corridors that are of particular importance to us. You can follow their work here: http://www.openstreetmap.org/user/Dami_D/history http://www.openstreetmap.org/user/ChrisZontine/history We are not removing or replacing existing exit_to tagging. We are focusing on exits that don't have signpost information at all yet. We are also building support for this convention into our OSM model, retaining the existing support for exit_to for now. From the comment thread on my diary entry I get the feeling that there is some sense of agreement that we can move towards finally deprecating exit_to. As much as I would love to, that would require more discussion around what we will do with the existing exit_to tags, support in editors, etc. I would like to start talking about these things, but not before I am comfortable that we want this as a community. I did follow the comments on your diary but did not comment so far. * as there is still a traffic sign at the junction you might keep the information on the node. * if we want to keep the separation in the destination:ref, I would prefer destination:ref_to over ref:to. Though there is no problem with semi-colon separated values of destination:ref. * if we need information about the junction on ways, we already have junction=* and junction:ref=* or even junction:ref:lanes:forward=* might work. Just my 2ct fly ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Follow up on destination= and destination:ref=
Martijn, great to hear that Telenav will be using the destination keys. Since this tagging will only be used for informational purposes to the motorist (routing won't be affected) I recommend to tag all info on the signposts, like the signs, and not only the destination and destination:ref. Examples can be found here: http://wiki.openstreetmap.org/wiki/Proposed_features/Destination_details Also I would recommend to tag the lane information at the same time, since this also gives extra info to the motorist. Cheers, Johan p.s. you can use the Netherlands as a European test bed: 85% of the motorways has been tagged with signpost and lane info :-) 2014-07-10 17:21 GMT+02:00 fly lowfligh...@googlemail.com: Am 10.07.2014 15:43, schrieb Martijn van Exel: Hi, (I am sorry if this message appears twice - I wasn't yet subscribed to this list with my Telenav account.) I posted about destination= and destination:ref= a few days ago, linking to my diary entry. I have since received a lot of useful comments. I just wanted to bump this topic because all the discussion has been going on there and not on the list: http://www.openstreetmap.org/user/mvexel/diary/22419#comment27109 Here at Telenav, we have now adopted destination= and destination:ref= for signpost information. We have two people adding information about signposts where they don't exist, prioritizing corridors that are of particular importance to us. You can follow their work here: http://www.openstreetmap.org/user/Dami_D/history http://www.openstreetmap.org/user/ChrisZontine/history We are not removing or replacing existing exit_to tagging. We are focusing on exits that don't have signpost information at all yet. We are also building support for this convention into our OSM model, retaining the existing support for exit_to for now. From the comment thread on my diary entry I get the feeling that there is some sense of agreement that we can move towards finally deprecating exit_to. As much as I would love to, that would require more discussion around what we will do with the existing exit_to tags, support in editors, etc. I would like to start talking about these things, but not before I am comfortable that we want this as a community. I did follow the comments on your diary but did not comment so far. * as there is still a traffic sign at the junction you might keep the information on the node. * if we want to keep the separation in the destination:ref, I would prefer destination:ref_to over ref:to. Though there is no problem with semi-colon separated values of destination:ref. * if we need information about the junction on ways, we already have junction=* and junction:ref=* or even junction:ref:lanes:forward=* might work. Just my 2ct fly ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
