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
> Op 23 jan. 2017, om 10:42 heeft Colin Smale het
> volgende geschreven:
>
> It's a complete waste of time to have yet another debate about the pro's and
> con's of semicolons vs suffixes and all the other possibilities, without
> having some kind of mechanism in place, and the will, to actua
On 2017-01-23 09:53, Martin Koppenhoefer wrote:
> sent from a phone
>
>> On 22 Jan 2017, at 22:18, Colin Smale wrote:
>>
>> Consumers who are not ready to handle multiple values in their data models
>> can stop reading after the first value
>
> consumers unaware of multiple values in the same
sent from a phone
> On 22 Jan 2017, at 22:18, Colin Smale wrote:
>
> Consumers who are not ready to handle multiple values in their data models
> can stop reading after the first value
consumers unaware of multiple values in the same field will see all those
multiple values together as jus
On Sun, Jan 22, 2017 at 8:41 PM, yo paseopor wrote:
>> I would expect that each value for destination only occurs a small
>> number of times, especially when there are multiple destinations. Why
>> would a certain combination of destinations occurs more than a handful
>> of times ? Hence, you wil
2017-01-22 22:32 GMT+01:00 yo paseopor :
> I need help. How to tag a roundabout destination traffic sign
> https://www.mapillary.com/map/im/6bMYhgICHVBL_H70ZnyPAg ? With
> correspondence it is easy (for me), but I don't know how to do it with
> multiple values.
>
>
Please check it out (in JOSM for
I need help. How to tag a roundabout destination traffic sign
https://www.mapillary.com/map/im/6bMYhgICHVBL_H70ZnyPAg ? With
correspondence it is easy (for me), but I don't know how to do it with
multiple values.
Also I hope OSM people will advise strongly Finnish people as they are
using suffixed
On 2017-01-22 21:51, Hakuch wrote:
> On 22.01.2017 21:20, yo paseopor wrote:
>
>> As you can see order is not random. In Catalonia is the same. How do you
>> make correspondence with the order.
>
> But I agree, when there is really a important sense in order of the
> values, putting them in a m
On 22.01.2017 21:20, yo paseopor wrote:
> As you can see order is not random. In Catalonia is the same. How do you
> make correspondence with the order.
But I agree, when there is really a important sense in order of the
values, putting them in a multiple value could be wrong
___
On 22.01.2017 21:20, yo paseopor wrote:
>>
>> Following this, you could try to find semantic weight for the different
>> destinations and discuss/use them. But when there is none (what I
>> assume),
>
> Spanish ministery responsible of the roads did not think that
>
> http://www.fomento.es/NR/rdo
>
> Following this, you could try to find semantic weight for the different
> destinations and discuss/use them. But when there is none (what I
> assume),
Spanish ministery responsible of the roads did not think that
http://www.fomento.es/NR/rdonlyres/FC57DE0A-72BF-408F-
810E-467894BA8E38/110896/
On 22.01.2017 20:41, yo paseopor wrote:
> So you say each value...(are we talking about multiple values or values
> with semicolon?). What are the most used values: unique or multiple? Why
> don't we use multiple values more often?
Like I said in my other post, the wiki is not very clear here, but
On 22.01.2017 11:09, yo paseopor wrote:
> It's true, but OSM wiki, the tool people like me who tries to learn how to
> do something uses says that:
> https://wiki.openstreetmap.org/wiki/Semi-colon_value_separator#When_NOT_to_use
> .
> Change the wiki please if it is not.
The wiki is correct at thi
> I would expect that each value for destination only occurs a small
> number of times, especially when there are multiple destinations. Why
> would a certain combination of destinations occurs more than a handful
> of times ? Hence, you will not find them in the top values on taginfo.
>
So you s
On Sun, Jan 22, 2017 at 11:09 AM, yo paseopor wrote:
> And if you search top100 list there are only 12 values with semicolon , 2
> with comma . All these values together are only 1792 tagged values...from
> 71665 total values.
I would expect that each value for destination only occurs a small
num
It's not about tastes or individual habilty . It's about " the aim of *keeping
it simple* both for data *contributors* (mappers) and data *users" *
Semicolon works? I don't have any doubt of it but not in ALL the apps and
services as subtags don't do in others...but could be implemented.
Is not av
On Sat, Jan 21, 2017 at 8:21 AM, yo paseopor wrote:
> Other solution
> destination=Main Street
> destination:2=7th Avenue
> destination:3=Downtown Mappersville
> destination:4=Karte County Courthouse
> ... and so on.
>
Is this actually being used by anyone? Semicolons have seperated multiple
va
I don't like your idea yopaseopor.
Why:
1. It's not forbidden to use a semicolon: 'But there are cases where
semicolons work and, anyway, we can’t completely avoid them. Let’s work on
defining our data model better and make it clearer where those semicolons
can and should be used and how they are
It's true, but OSM wiki, the tool people like me who tries to learn how to
do something uses says that:
https://wiki.openstreetmap.org/wiki/Semi-colon_value_separator#When_NOT_to_use
.
Change the wiki please if it is not.
Wiki explains
"In general *avoid ';' separated values whenever possible*. D
tools such as http://osm.mueschelsoft.de/cgi-bin/render.pl support the
semi-column notation, not the number notation. I assume most
destination signs in Germany and neighbouring countries are using the
semi-column notation.
On Sat, Jan 21, 2017 at 11:00 PM, yo paseopor wrote:
> With destination
With destination:x you mark in a easy way the correspondence with other
tags.Destination:2 goes with distance:2 and with destination:symbol:2 for
example. It is an easy way to see the correspondence. For people like me
(we have less idea to program something like a preset or a style in JOSM,
for ex
Why is destination:X better than a list with semi-colons ?
I think that semi-colons in the destination tags are already to
wide-spread to be stopped. Data consumers like OsmAnd have no problem
with the semi-colons.
m
On Sat, Jan 21, 2017 at 3:21 PM, yo paseopor wrote:
> Other solution
> destina
Other solution
destination=Main Street
destination:2=7th Avenue
destination:3=Downtown Mappersville
destination:4=Karte County Courthouse
... and so on.
(for legible reasons a "standard" traffic sign does not show more than 3/4
items by direction at sign).
also this will be "portable" to other cou
On Fri, Jan 20, 2017 at 2:13 PM, yo paseopor wrote:
> Little apreciation:
> Please, no multiple values,no semicolon.Better subtags
>
That doesn't always work. Fictional example, but one that does come up
routinely, particularly around small to moderate sized towns and rural
America (imagine a b
Little apreciation:
Please, no multiple values,no semicolon.Better subtags
yopaseopor
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
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
In the US the prefix would typically be in the network tag, like network=US:US
ref=89 for US highway 89, etc.
We have seen some of this in Canada as well. (CA:ON for Ontario highways etc.)
Martijn van Exel
> On Jan 20, 2017, at 12:57 AM, Paul Norman wrote:
>
> On 1/19/2017 5:00 PM, Martijn van
On 1/19/2017 5:00 PM, Martijn van Exel wrote:
Looking at a random one, http://www.openstreetmap.org/way/34154734 /
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
That is how it would be typically
28 matches
Mail list logo
