[OSM-talk] High Road - pre-cooked Postgres views for rendering OSM roads

[Peter Wendorff]

Am 07.09.2011 14:51, schrieb Ilya Zverev:
> Hi!
>
> Did you consider (or are you planning to) joining named ways, so 
> segmenting roads won't have any effect on rendering labels? komap.py 
> of Kothic library does that, for example. This is also a task for 
> PostGIS, so it could be included in HighRoad.
I'm not speaking for Stamen, but keep in mind, that the joining you 
propose restricts the usage, if it's not possible to define a set of 
separating tags.

Consider a primary road that switches to a secondary or tertiary while 
keeping the same name.
(e.g. in Germany) that could happen in cases where a old, named street 
crosses a town and there is a new bypass road build to circumvent too 
much traffic in the town.
In this case the street could keep the same name crossing the town, but 
collapsing it would lead to wrong rendering results, as the tags would 
have to be unified.

Similar issues could happen if you consider special renderings, e.g. 
with focus on
- parking lanes
- sidewalks
- oneways (!)
- surface
- maxspeed
and much much more.

So if supported, this should be 1) optional and 2) the set of separating 
tag (dependent on the usage of the result) should be defineable.

regards

Peter