Am 14.10.2010 08:39, schrieb Jochen Topf:
And one problem they have is that maps are hard to use if you
can't read half the country names.
This is one of those problems that will not be solved until the renderers
get more clever and, for instance, take the "name" tag and the "name:en" tag
and
Hi all,
I now have the JOSM map features list organized into a nice GoogleDocs
spreadsheet.
https://spreadsheets.google.com/ccc?key=0Am70fsptsPF2dFB6bl9IMmMzV1hSRWdFaGE0NHBvQUE&hl=en
I basically just manually converted/copied the .xml file into columns
and rows for each tag.
It's an Open Access c
> I could set up such a style on the toolserver if it would be helpful,
> but I'd like to point to the localized maps we currently have in >30
> languages: http://toolserver.org/~osm/locale/ (use the layer switcher).
This is great!
...but it's not quite right (or I'm doing something wrong).
Here
Am 14.10.2010 12:41, schrieb Andrew Errington:
This generalises to "if language "lang" is requested then use name:lang=* if
such a tag is present. If it's not present then use name=*"
That's exactly what we do on the locale maps on the toolserver for the
30+ languages listed there.
Anyway,
On Thu, Oct 14, 2010 at 12:41 PM, Andrew Errington <
a.erring...@lancaster.ac.uk> wrote:
> Furthermore, the convention that has been adopted is that
> name=* should be the name in Hangul, followed by a space, followed by the
> name in English in parentheses.
>
:
> So, as I see it, names should be
On Thu, 14 Oct 2010 20:08:16 Peter Körner wrote:
> Am 14.10.2010 12:41, schrieb Andrew Errington:
> > This generalises to "if language "lang" is requested then use name:lang=*
> > if such a tag is present. If it's not present then use name=*"
>
> That's exactly what we do on the locale maps on the
On Thu, 14 Oct 2010 20:07:57 Pieren wrote:
> On Thu, Oct 14, 2010 at 12:41 PM, Andrew Errington <
>
> a.erring...@lancaster.ac.uk> wrote:
> > Furthermore, the convention that has been adopted is that
> > name=* should be the name in Hangul, followed by a space, followed by the
> > name in English i
On 10/14/10 7:57 AM, Andrew Errington wrote:
On Thu, 14 Oct 2010 20:07:57 Pieren wrote:
This is exactly a good example of "tagging for the renderers". What OSM
needs is a lot of local contributors. And for them, it is much easier to
enter only one tag for the name and this in the local language
I'm not sure, if that's a good solution...
It's relatively simple and can be done automatically, but do it hit the
target?
For most Asian and Arabian countries that would help perhaps: the native
language uses other character (sub)sets and therefore the rest of the
world probably don't know
On Thu, 14 Oct 2010 21:53:19 Richard Welty wrote:
> On 10/14/10 7:57 AM, Andrew Errington wrote:
>
> it's a hack, it happens to work for you, and that's ok.
>
> but it's not good practice in terms of making a generally usable
> database. it causes some existing renderers to do something you
> like,
On 14/10/2010 14:36, Andrew Errington wrote:
So, when we get a renderer that can render "name:ko + (name:en)" we can delete
all name=* which have been typed in that form and then rename name:ko=* to
name=*
No, this would not be helpful. Because then how do you know what
language the "name" ta
Am 14.10.2010 15:47, schrieb Craig Wallace:
On 14/10/2010 14:36, Andrew Errington wrote:
So, when we get a renderer that can render "name:ko + (name:en)" we
can delete
all name=* which have been typed in that form and then rename
name:ko=* to
name=*
No, this would not be helpful. Because then
You can also test for the presence of "name:de" in "name", rather than
just equality, so that if name contains (say) French/German/Flemish
components, then you use that rather than making your own name
(name:de) combination.
Richard
On Thu, Oct 14, 2010 at 2:51 PM, Peter Körner wrote:
> Am 14.10
Am 14.10.2010 15:56, schrieb Richard Mann:
You can also test for the presence of "name:de" in "name", rather than
just equality, so that if name contains (say) French/German/Flemish
components, then you use that rather than making your own name
(name:de) combination.
That would be:
SELECT name
Hi.
Tweaking the renderer this way is the wrong decision, I would say.
For me the problem is the mixed name stored in some name tags, e.g.
local-name (english name) as mentioned before.
Your idea here is to make the renderers better to avoid the NEED of that
crap (to be clear: as a workaround i
On 14. Oktober 2010 18:57 Andrew Errington [a.erring...@lancaster.ac.uk]
wrote:
> Not really. Street signs, roadsigns and other public signage is
increasingly
> being printed in Hangul and English. However, when we get a renderer that
> can render "name:ko + (name:en)" we can delete all nam
On 14/10/2010 14:51, Peter Körner wrote:
To render a German map there are two possibilities:
1. render "name:de" if it exists, "name" otherwise
2. render "name" if its identical to "name:de", "name (name:de)" otherwise
"name" does hereby refer to the local name ((how do the people that live
the
Am 14.10.2010 16:42, schrieb Craig Wallace:
On 14/10/2010 14:51, Peter Körner wrote:
To render a German map there are two possibilities:
1. render "name:de" if it exists, "name" otherwise
2. render "name" if its identical to "name:de", "name (name:de)"
otherwise
"name" does hereby refer to the
On Jueves 14 Octubre 2010 16:05:58 Peter Körner escribió:
> Am 14.10.2010 16:42, schrieb Craig Wallace:
> > On 14/10/2010 14:51, Peter Körner wrote:
> >> To render a German map there are two possibilities:
> >> 1. render "name:de" if it exists, "name" otherwise
> >> 2. render "name" if its identica
On Thu, Oct 14, 2010 at 4:42 PM, Craig Wallace wrote:
>
> You could assume what language "name" is in, based on country boundaries,
> but that makes things much more complicated.
>
Not for a GIS application.
Pieren
___
Tagging mailing list
Tagging@ope
Noel David Torres Taño writes:
> That all is quite good for places with only one roman-script name. But I'm
> thinking in this case:
>
> name:es=Cataluña (This is the name in Spain's official language, which is
> official there since Catalonia is part of Spain)
> name:ca=Catalunya (This is the
However, in countries that have more than one official language, or in areas
that expect to have a lot of foreign visitors, you are likely to see more than
one language on at least some of the signs. In this case, what would you
recommend, particularly if the signs are labeled in more than one
On 15 October 2010 02:29, wrote:
> However, in countries that have more than one official language, or in areas
> that expect to have a lot of foreign visitors, you are likely to see more
> than one language on at least some of the signs. In this case, what would
> you recommend, particularly
Am 15.10.2010 08:21, schrieb Stephen Hope:
So the sign "Rue Bouganville St" would be name:en=Bouganville Street,
name:fr=Rue Bouganville, but what would you put in name=?
Exactly what's on the sign: "Rue Bouganville St"
Peter
___
Tagging mailing lis
24 matches
Mail list logo
