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 it's okay, but it's crap from the
data point of view).
If changing the renderer - why not change it correctly to use name +
(name:en) (if that's what we want for name containing only the local name).
There will be people fixing the bugs done as workaround yet - I'm sure;
and as a result we will get a better database with maps similar or equal
to the maps we have now, but perhaps with the far view towards real
multi-language rendering using e.g. different language layers.
regards
Peter
On 14.10.2010 16:03, Peter Körner wrote:
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 AS local_name,
CASE WHEN NOT name ~* (tags->'name:en')
THEN name || ' (' || (tags->'name:en') ||')'
ELSE name
END AS display_name
FROM planet_point
WHERE tags @> '"place"=>"country"'
AND NOT name IS NULL
LIMIT 10;
I'ts so simple.
Peter
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
http://lists.openstreetmap.org/listinfo/tagging
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
http://lists.openstreetmap.org/listinfo/tagging
