Maybe a possible solution to get rid of name=* tags containing names
in multiple languages would be to add the information about which
languages are spoken in a particular region to its boundary relation
(e.g. spoken_languages=de;fr to the municipality boundary of
Biel/Bienne). However, the rendere
The renderers and ALL data consumers would then have to take that into
account.
Tagging for the renderer means: Using a inappropriate tag on an object such
that it renders in a colour or style the mapper prefers over correctly
tagging an object.
Putting 2 names in a name field where those 2 names
1 up.
- - - - -
Well,
* can anyone (as I) to vote? I am a database OSM user/developer (PostGIS
etc), not an experienced mapper.
* there are here an "e-mail-vote protocol" to say +1 / -1 /
abstention... ?
Em 2018-08-09 12:57, Eric H. Christensen escreveu:
-BEGIN PGP SIGNED MESSAGE--
On Fri, Aug 10, 2018 at 2:01 PM, peterkrauss
wrote:
>
> * can anyone (as I) to vote?
Have you registered as a user of the OSM Wiki? Voting is a matter of
editing the proposal page to add your vote.
> I am a database OSM user/developer (PostGIS etc), not an experienced
> mapper.
If you don'
On Fri, Aug 10, 2018 at 12:25 AM, Martin Koppenhoefer <
dieterdre...@gmail.com> wrote:
>
> > On 10. Aug 2018, at 00:42, Daniel McCormick
> wrote:
> >
> > While the default renderer favors name=* over name:nl or name:fr that is
> not the case for other renderers. We as contributors might think tha
sent from a phone
> On 10. Aug 2018, at 15:29, Paul Allen wrote:
>
> 1) It is said to be standard practice to render what is observable on the
> ground.
everybody can render what she deems most useful, there is not an absolute rule
to render what is on the ground (e.g. if there is a typo
sent from a phone
> On 10. Aug 2018, at 15:01, peterkrauss wrote:
>
> * can anyone (as I) to vote? I am a database OSM user/developer (PostGIS
> etc), not an experienced mapper.
you have to register to the osm wiki (if you haven’t yet) and vote on the
proposal page with {{vote|yes}}— o
On Fri, Aug 10, 2018 at 4:23 PM, Martin Koppenhoefer wrote:
>
> > On 10. Aug 2018, at 15:29, Paul Allen wrote:
> >
> > 1) It is said to be standard practice to render what is observable on
> the ground.
>
>
> everybody can render what she deems most useful, there is not an absolute
> rule to ren
sent from a phone
> On 10. Aug 2018, at 18:24, Paul Allen wrote:
>
> You appear to be saying that the name of the street (as on the sign) is not
> the name of the street (as in the name=*
> tag applying to the street). This appears to be a post-modernist
> interpretation of "name."
>
> Wha
If the sign shows one string, name= should always be right.
If you know the string contains two language variants and a separator, sep
string, brackets or whatever, you can interpret the string and extract name:xx
substrings. I would still keep the name= tag, to serve both rendering
and other da
of objects just because
>>> someone does not like the rendering on the default osm.org map.
>>>
>>> m.
>>>
>>> ___
>>> Tagging mailing list
>>> Tagging@openstreetmap.org
>>> https://
On Fri, Aug 10, 2018 at 6:06 PM, Martin Koppenhoefer wrote:
>
> I am saying that street signs are just indications of names. Names for
> streets are usually (at least in Italy and Germany) assigned by the city
> council,
Assigned by the county council here in the UK (I'm simplifying a little
be
> If there's a street sign, that's what should be mapped in name=* even if it's
> "wrong." Not temporarily wrong, but
> permanently "the council has decreed that's what it is, and that's how it's
> going to stay" wrong. Because if I'm in
> a strange location, looking at a map that labels a stre
On Fri, Aug 10, 2018 at 6:38 PM, Daniel McCormick
wrote:
>
> The goal of OSM is not to create a map that renders great on the default
> renderer. The goal is to create repository that can be rendered quickly and
> easily by anyone. The default map is what we primarily interact with and
> just lik
On Fri, Aug 10, 2018 at 7:35 PM, Marc Gemis wrote:
>
> what if there are different street signs on the left and the right
> side because the street is on the boundary between 2 villages ?
>
name:left=* and name:right=* are what the wiki recommends. Local mapping
conventions might well decide to
Am 10.08.2018 um 20:19 schrieb Paul Allen:
> Because if I'm in
> a strange location, looking at a map that labels a street "Foo Lane"
> that's what I expect to see on the sign. Anything
> else is misleading and unhelpful.
Couldn't agree more.
Note: we do have "official_name" for identifyin
Le 10. 08. 18 à 20:35, Marc Gemis a écrit :
>> If there's a street sign, that's what should be mapped in name=* even if
>> it's "wrong."
> What if there are 2 streets signs on either end of the street with
> different spelling ?
I agree with you
the name of a highway, is the name of... the highw
Le 10. 08. 18 à 19:28, Peter Elderson a écrit :
> If the sign shows two strings one line each, you will need
> interpretation and/or a glue character or glue string.
in fact, what's the better glue character IS the question
at the begging of this thread.
Currently, a Brussels resident reading a
On Fri, 10 Aug 2018 at 21:42, marc marc wrote:
> In the same way as in osm we defined ";" as being the separator between
> several values of the same key (with several exceptions), it would be
> useful to define a separator between several lines of the same key.
Then why not also use the semicolo
if I were a renderer I would not try to parse/interpret a free format string. I
would parse only clearly defined sections, where the separator is very very
unlikely to occur in text strings. Space slash space might be suitable, but not
if any context is required, context such as that it’s about
Fortunately all streets in Brussels are already mapped, based on official
data from Urbis. So the person from Biel who would prefer to put / in those
names doesn't need to to so anymore.
There are definitely street name signs which are wrong. It would be absurd
to copy that wrong text into the nam
On Fri, Aug 10, 2018 at 10:47 PM, Peter Elderson
wrote:
if I were a renderer I would not try to parse/interpret a free format
> string. I would parse only clearly defined sections, where the separator is
> very very unlikely to occur in text strings. Space slash space might be
> suitable, but not
On Fri, Aug 10, 2018 at 11:38 PM, Jo wrote:
> Fortunately all streets in Brussels are already mapped, based on official
> data from Urbis. So the person from Biel who would prefer to put / in those
> names doesn't need to to so anymore.
>
> There are definitely street name signs which are wrong.
What if the street sign said:
St Francis St.
would you be putting that exactly as is in the name tag?
I would put
Saint Francis Street
in it.
What if there are 3 signs, one with
St Francis St.
Saintt Francis St.
St Francis Street
It may be a longer street, it may be that time passed by betwe
On 11 August 2018 at 09:14, Jo wrote:
> What if the street sign said:
>
> St Francis St.
>
> would you be putting that exactly as is in the name tag?
>
> I would put
>
> Saint Francis Street
>
> in it.
>
> What if there are 3 signs, one with
> St Francis St.
> Saintt Francis St.
> St Francis Stre
> I find it hard to understand why some mappers do not want to map reality.
> Unless it's because they wish the street
> signs were really monolingual. There are people where I live who object to
> any use of English, should I cater to
> their whims by amending all names around here to remove t
If I knew about usual abbrevs I would probably expand those. If I was not sure,
I would not. Usually, looking at existing names in the area tells me what to
do. If there are variants on different signs in an area/language I don’t know,
I tend to do nothing at all, but if I had to I would either
I am not trying to change any accepted local rule.
Mvg Peter Elderson
Op 11 aug. 2018 om 06:13 heeft Marc Gemis het volgende
geschreven:
>> I find it hard to understand why some mappers do not want to map reality.
>> Unless it's because they wish the street
>> signs were really monolingual.
28 matches
Mail list logo
