Choosing not to render a point because there's something else more important
close by is relatively easy. Aggregating adjacent lines is much (much)
harder. Identifying the number of lines that are adjacent is much
(much) easier for the tagger than for the renderer.
But I seem to be repeating
On Wed, Jun 24, 2009 at 1:31 PM, Richard Mann
richard.mann.westoxf...@googlemail.com wrote:
Choosing not to render a point because there's something else more important
close by is relatively easy. Aggregating adjacent lines is much (much)
harder. Identifying the number of lines that are
Hi all,
It's about time to push on the import to the rest of the UK, however,
we must first consider what we do with the new Public Transport
tagging schema.
It would make a lot of sense to use this now that a detailed proposal
has been put together.
The only real differences it would make for us
On Wed, Jun 24, 2009 at 2:45 PM, Richard Mann
richard.mann.westoxf...@googlemail.com wrote:
Do relations solve the problem at all? If a track is part of a route
relation, then could a renderer use that as a means of aggregating the
tracks together?
My hunch is that relations probably
