Opened 10 years ago

Closed 8 years ago

#2392 closed enhancement (invalid)

named relations for streets consists of several ways

Reported by: woidrick Owned by: mapnik-team@…
Priority: minor Milestone:
Component: mapnik Version:
Keywords: Cc:

Description

for now, many streets consists of several ways bacause of routing rules etc.

when name applied to each part the rendering of this looks bad

i propose to add all parts of street to some relation which will be named as name of street.

the renderer should use the name in relation to render street name in proper part of street and if the street is long - several times repeated street name with proper spacing

Change History (2)

comment:1 Changed 10 years ago by Mikado

I believe that the accepted relation for that is associatedStreet. It is used on 4000 to 6500 relations already (osmdoc, tagwatch). FWIW, it's already supported by some robot in the Moscow city.

comment:2 Changed 8 years ago by Ldp

Resolution: invalid
Status: newclosed

We're building a database with a spatial component. Collating connected and similarly named roads into larger features is a task well suited to such a database. Attacking this problem with a relation is just the wrong approach.

Note: See TracTickets for help on using tickets.