I could imagine some sort of duplicate/concatenate function that created additional ways based on matching certain tag values (eg highway=primary), and grouping based on a specified set of keys (eg highway & name), and simple end-on-end geometry. You'd then render names (with repeats if required) based on these new ways and not render names using the original ways.
The main point of this would be that concatenation probably ought to be directed/controlled by the user. If it's done automatically (eg for name/ref tags on highways) in data-massaging/rendering software then the user will end up having to fix the source data to control the behaviour of the software. Richard On Fri, Jul 2, 2010 at 10:00 AM, Andy Allan <[email protected]> wrote: > Yes, this is the issue at hand. For some properties (most often names, > but also things like shields) you want to join just that property into > a longer linestring. I would suggest this is done in osm2pgsql, but as > yet I haven't figured out a good approach. I think it might involve a > bit of rethinking the way that osm2pgsql works. _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
