Re: [OSM-talk] Rendering street names across several ways
andrzej zaborowski wrote: I think the rules for joining segments by osm2pgsql should be something like: * name='s are equal, * highway/railway/waterway/aeroway class is equal (however I wouldn't mind osm2pgsql joining a 3-segment way where the middle segment is shared with a tramway) * only two such ways meet at the common node -- not a Y type of junction where all three ways have identical names classes. * (possibly) not divided by a crossing with a higher class way, * (possibly) not meeting at a narrow angle * oneway='s are equal (or inverse, in case the ways have opposite directions), * unless it's a zoom level where the oneway arrows are invisible. How about http://osm.org/go/WIdREBKcE-- ? Note, the N/S road is split in two parts at this intersection, as it is oneway=yes on both sides in opposite directions. Since the street is so short, it loses both name labels just two zooms out. Of course, rendering the mini-roundabout at lower zooms doesn't help. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
On Fri, Jul 2, 2010 at 2:42 AM, Roy Wallace waldo000...@gmail.com wrote: Say you have two connected ways: name=Foo Street lanes=2 and name=Foo Street lanes=4 You don't want to join these ways with osm2pgsql before rendering, because you want to render them differently. You probably do, however, want them to share a name label. Right? 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. Cheers, Andy ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
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 gravityst...@gmail.com 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 talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
andrzej zaborowski balrogg at gmail.com writes: I think the rules for joining segments by osm2pgsql should be something like: * name='s are equal, * highway/railway/waterway/aeroway class is equal (however I wouldn't mind osm2pgsql joining a 3-segment way where the middle segment is shared with a tramway) * only two such ways meet at the common node -- not a Y type of junction where all three ways have identical names classes. * (possibly) not divided by a crossing with a higher class way, * (possibly) not meeting at a narrow angle * oneway='s are equal (or inverse, in case the ways have opposite directions), * unless it's a zoom level where the oneway arrows are invisible. Hi, I hope that if osm2pgsql will have this kind of Mapnik specific import rules, they would be optional. People are using osm2pgsql also for other purposes than Mapnik rendering. -Jukka Rahkonen- ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
On Fri, Jul 2, 2010 at 11:33 AM, Jukka Rahkonen jukka.rahko...@latuviitta.fi wrote: I hope that if osm2pgsql will have this kind of Mapnik specific import rules, they would be optional. People are using osm2pgsql also for other purposes than Mapnik rendering. Oh, totally. And there are even people using osm2pgsql for processing non-OpenStreetMap data, so one of my projects is to try to remove all the hardcoded tags (from z-order calculations through to the type tag on relation handling or the area tag on ways) and put them into configuration files. Cheers, Andy ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
On 2 July 2010 21:18, Andy Allan gravityst...@gmail.com wrote: Oh, totally. And there are even people using osm2pgsql for processing non-OpenStreetMap data, so one of my projects is to try to remove all the hardcoded tags (from z-order calculations through to the type tag on relation handling or the area tag on ways) and put them into configuration files. How hard would it be to calculate the admin_level of a way from the relation information during import? ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
On Thu, Jul 1, 2010 at 2:18 PM, Ben Last ben.l...@nearmap.com wrote: ... I assumed zverik's comment related to osm2pgsql or the like, where ways (or sets of relations) could be joined. I don't think you want to join ways, because they belong to different relations. (E.g. you might render the segment of street that belongs to a bus route relation differently to the other segment with the same name.) Rather, you want multiple ways to share a name. This does sound like a job for the renderer to me. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
On 1 July 2010 16:17, Roy Wallace waldo000...@gmail.com wrote: Rather, you want multiple ways to share a name. This does sound like a job for the renderer to me. Or you can help things out by putting the name into a relation and adding the segments of way as members... ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
On Thu, Jul 1, 2010 at 9:44 AM, John Smith deltafoxtrot...@gmail.comwrote: On 1 July 2010 16:17, Roy Wallace waldo000...@gmail.com wrote: Rather, you want multiple ways to share a name. This does sound like a job for the renderer to me. Or you can help things out by putting the name into a relation and adding the segments of way as members... This results in even more complicated situation and even more work to maintain such data. And even if do you follow this practice, there will still be huge amounts of legacy data which do not. I think if two streets share the same name and are adjacent to each other, it is reasonable for renderers to assume it's the same street. Igor ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
On 1 July 2010 17:59, Igor Brejc igor.br...@gmail.com wrote: This results in even more complicated situation and even more work to maintain such data. And even if do you follow this practice, there will still be huge amounts of legacy data which do not. I think if two streets share the same name and are adjacent to each other, it is reasonable for renderers to assume it's the same street. Depending on the number of segments it would still make more sense to put this information into a relation, since you are reducing the amount of redundant data. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
On Thu, Jul 1, 2010 at 5:59 PM, Igor Brejc igor.br...@gmail.com wrote: This results in even more complicated situation and even more work to maintain such data. And even if do you follow this practice, there will still be huge amounts of legacy data which do not. I think if two streets share the same name and are adjacent to each other, it is reasonable for renderers to assume it's the same street. Definitely. I would go so far as to say that two connected ways should render identically to if they were a single way, except for the actual differences in tags between them. That is, the mere fact of being two ways or a single way should make no difference to the rendering - that's an error. I can imagine situations where a renderer would want to repeat a street name, or place the street name across the gap (eg, when a street changes category, and hence rendering colour), to make clear that the two share a name, however. But that should be a deliberate business rule. Steve ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
On Thu, 1 Jul 2010 18:41:13 +1000, Steve Bennett stevag...@gmail.com wrote: On Thu, Jul 1, 2010 at 5:59 PM, Igor Brejc igor.br...@gmail.com wrote: This results in even more complicated situation and even more work to maintain such data. And even if do you follow this practice, there will still be huge amounts of legacy data which do not. I think if two streets share the same name and are adjacent to each other, it is reasonable for renderers to assume it's the same street. Definitely. I would go so far as to say that two connected ways should render identically to if they were a single way, except for the actual differences in tags between them. That is, the mere fact of being two ways or a single way should make no difference to the rendering - that's an error. I can imagine situations where a renderer would want to repeat a street name, or place the street name across the gap (eg, when a street changes category, and hence rendering colour), to make clear that the two share a name, however. But that should be a deliberate business rule. The problem is that if you go to a rule one road, name displayed once, you will have to search for the name of the road if the road is very long. This might not be a problem with residential roads on lower zoom levels, but it will with e.g. motorways on higher zoom levels. Look example [1]. There is no name on the motorway (I've got my browser about 1100 pix wide). I have deliberately cut a local stream up to make the name render in more places. [1] http://www.openstreetmap.org/?lat=51.37798lon=5.95429zoom=15layers=B000FTF Regards, Maarten ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
On Thu, Jul 1, 2010 at 10:56 AM, Maarten Deen md...@xs4all.nl wrote: The problem is that if you go to a rule one road, name displayed once, you will have to search for the name of the road if the road is very long. The actual rule is: treat it as a single OSM way and then decide how often to repeat the name for longer ways. This might not be a problem with residential roads on lower zoom levels, but it will with e.g. motorways on higher zoom levels. Look example [1]. There is no name on the motorway (I've got my browser about 1100 pix wide). I have deliberately cut a local stream up to make the name render in more places. It's up to the renderer to decide how often to repeat the name. Cutting up ways just to make it look better for a certain renderer (Mapnik) isn't really a good practice. And anyway, this depends on the zoom level: once you zoom into enough, you will still get ways that will be long and with one label only. And if you zoom out, you won't get _any_ labels, since the split ways will be too short to show anything. Igor ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
I've got situations where a side road name continues across a main road, and it looks distinctly odd (must happen all the time in grid layouts). I solved the problem by breaking the way at the main road. If a renderer wants to be clever and put the sections back together, they need to suppress the behaviour when the shared node is also shared by a higher-class highway. In the St Petersburg example, the root of the problem is long street names. Maybe you need to render it yourself in a smaller/narrower font. Richard On Thu, Jul 1, 2010 at 9:56 AM, Maarten Deen md...@xs4all.nl wrote: On Thu, 1 Jul 2010 18:41:13 +1000, Steve Bennett stevag...@gmail.com wrote: On Thu, Jul 1, 2010 at 5:59 PM, Igor Brejc igor.br...@gmail.com wrote: This results in even more complicated situation and even more work to maintain such data. And even if do you follow this practice, there will still be huge amounts of legacy data which do not. I think if two streets share the same name and are adjacent to each other, it is reasonable for renderers to assume it's the same street. Definitely. I would go so far as to say that two connected ways should render identically to if they were a single way, except for the actual differences in tags between them. That is, the mere fact of being two ways or a single way should make no difference to the rendering - that's an error. I can imagine situations where a renderer would want to repeat a street name, or place the street name across the gap (eg, when a street changes category, and hence rendering colour), to make clear that the two share a name, however. But that should be a deliberate business rule. The problem is that if you go to a rule one road, name displayed once, you will have to search for the name of the road if the road is very long. This might not be a problem with residential roads on lower zoom levels, but it will with e.g. motorways on higher zoom levels. Look example [1]. There is no name on the motorway (I've got my browser about 1100 pix wide). I have deliberately cut a local stream up to make the name render in more places. [1] http://www.openstreetmap.org/?lat=51.37798lon=5.95429zoom=15layers=B000FTF Regards, Maarten ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
On 1 July 2010 19:16, Richard Mann richard.mann.westoxf...@googlemail.com wrote: I've got situations where a side road name continues across a main road, and it looks distinctly odd (must happen all the time in grid You also get the situation where roads are broken by dual carriage way or other natural features like waterways where the name continues but the road doesn't cross the barrier. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
My point is that OSM Mapnik layer (or any other map rendering) is not The Truth and we should try to avoid adjusting the underlying data just in order to fix issues like the ones you mentioned. Renderers will improve with time to be able to better handle such things. And they will behave differently, so data that seems beautified for one would not be so nice for the other. And as you said: if you really want a proffesional-like rendering, you can always render it yourself, produce a vector map and do the manual postprocessing afterwards. Igor -On Thu, Jul 1, 2010 at 11:16 AM, Richard Mann richard.mann.westoxf...@googlemail.com wrote: I've got situations where a side road name continues across a main road, and it looks distinctly odd (must happen all the time in grid layouts). I solved the problem by breaking the way at the main road. If a renderer wants to be clever and put the sections back together, they need to suppress the behaviour when the shared node is also shared by a higher-class highway. In the St Petersburg example, the root of the problem is long street names. Maybe you need to render it yourself in a smaller/narrower font. Richard ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
Hi again! I hope someone with programming skills is reading this discussion :) The problem is that if you go to a rule one road, name displayed once, you will have to search for the name of the road if the road is very long. The actual rule is: treat it as a single OSM way and then decide how often to repeat the name for longer ways. Although Mapnik does not repeat names, it repeats ref for trunks: http://www.openstreetmap.org/?lat=57.69949lon=28.33726zoom=16layers=B000FTF (scroll it north/south) So I don't think repeating names would be a problem. The fact that Mapnik doesn't do this looks like a bug: on long streets it's sometimes hard to find a name. Try this road (Estonia, for a change): http://www.openstreetmap.org/?lat=59.35981lon=24.71644zoom=17layers=B000FTF Cutting it just for the name to appear more often is mapping for rendeders, obviously. In the St Petersburg example, the root of the problem is long street names. Maybe you need to render it yourself in a smaller/narrower font. Well, streets sometimes are long enough to fit a name ten times. But segments are small. I don't consider this a font problem, because I'd better have one good-looking label than ten unreadable and redundant. IZ ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
This could be solved with the proposed relation=segmented_tag (which seems to be abandoned, and I would prefer the name relation=segment) http://wiki.openstreetmap.org/wiki/Relations/Proposed/Segmented_Tag The relation takes one way and two nodes on the way as members. Then this segment can be used as a member in bus route relations etc. The benefit would be that the way could be kept as a single way and not split in more or less every crossing. While this would not solve the problem over night it might be a more stable model for future use. Konrad 2010/7/1 John Smith deltafoxtrot...@gmail.com: On 1 July 2010 17:59, Igor Brejc igor.br...@gmail.com wrote: This results in even more complicated situation and even more work to maintain such data. And even if do you follow this practice, there will still be huge amounts of legacy data which do not. I think if two streets share the same name and are adjacent to each other, it is reasonable for renderers to assume it's the same street. Depending on the number of segments it would still make more sense to put this information into a relation, since you are reducing the amount of redundant data. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
On Jul 1, 2010, at 2:10 AM, Igor Brejc wrote: On Thu, Jul 1, 2010 at 10:56 AM, Maarten Deen md...@xs4all.nl wrote: The problem is that if you go to a rule one road, name displayed once, you will have to search for the name of the road if the road is very long. The actual rule is: treat it as a single OSM way and then decide how often to repeat the name for longer ways. This might not be a problem with residential roads on lower zoom levels, but it will with e.g. motorways on higher zoom levels. Look example [1]. There is no name on the motorway (I've got my browser about 1100 pix wide). I have deliberately cut a local stream up to make the name render in more places. It's up to the renderer to decide how often to repeat the name. In the case of Mapnik, labels are repeated along lines by default, but its up to the stylesheet author to specify the spacing between them. So, it is the rendering rules in question really, not the renderer. Cutting up ways just to make it look better for a certain renderer (Mapnik) isn't really a good practice. And it not needed at all if Mapnik is the renderer. And anyway, this depends on the zoom level: once you zoom into enough, you will still get ways that will be long and with one label only. And if you zoom out, you won't get _any_ labels, since the split ways will be too short to show anything. Igor ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
Hi, On 1 July 2010 12:32, Ilya Zverev zve...@textual.ru wrote: Although Mapnik does not repeat names, it repeats ref for trunks: http://www.openstreetmap.org/?lat=57.69949lon=28.33726zoom=16layers=B000FTF (scroll it north/south) So I don't think repeating names would be a problem. The fact that Mapnik doesn't do this looks like a bug: on long streets it's sometimes hard to find a name. Yeah, it seems cloudmade layers do repeat names (maps.cloudmade.com) and it's a nice feature. They don't join segmented ways though. I think the rules for joining segments by osm2pgsql should be something like: * name='s are equal, * highway/railway/waterway/aeroway class is equal (however I wouldn't mind osm2pgsql joining a 3-segment way where the middle segment is shared with a tramway) * only two such ways meet at the common node -- not a Y type of junction where all three ways have identical names classes. * (possibly) not divided by a crossing with a higher class way, * (possibly) not meeting at a narrow angle * oneway='s are equal (or inverse, in case the ways have opposite directions), * unless it's a zoom level where the oneway arrows are invisible. Cheers ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
On Fri, Jul 2, 2010 at 11:23 AM, andrzej zaborowski balr...@gmail.com wrote: I think the rules for joining segments by osm2pgsql should be something like: ... But hang on. Do we actually want to join segments [ways], or do we want *separate* ways to share a name label? I believe we want the second. Consider a renderer that renders the lanes=* tag with some style. Say you have two connected ways: name=Foo Street lanes=2 and name=Foo Street lanes=4 You don't want to join these ways with osm2pgsql before rendering, because you want to render them differently. You probably do, however, want them to share a name label. Right? ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
On 2 July 2010 03:42, Roy Wallace waldo000...@gmail.com wrote: On Fri, Jul 2, 2010 at 11:23 AM, andrzej zaborowski balr...@gmail.com wrote: I think the rules for joining segments by osm2pgsql should be something like: ... But hang on. Do we actually want to join segments [ways], or do we want *separate* ways to share a name label? I believe we want the second. Consider a renderer that renders the lanes=* tag with some style. Say you have two connected ways: name=Foo Street lanes=2 and name=Foo Street lanes=4 You don't want to join these ways with osm2pgsql before rendering, because you want to render them differently. You probably do, however, want them to share a name label. Right? Well, right, not necessarily join ways and then forget the segments. But at some point the renderer has to create a geometry that includes both ways, even if it's just to render a text along it. Cheers ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
zve...@textual.ru zve...@textual.ru wrote: Those names are not rendered, obviously, because most streets consist of several ways, due to routing and public transport reasons. Hmm, what routing reasons? The only cases where streets need to be split into multiple ways, in my experience, is where the tagging changes or a junction=roundabout intervenes. However, in your example area, many of the streets are divided into what seems like an unnecessarily large number of ways. If the tagging doesn't change between adjacent ways, then shouldn't the ways be merged into a single way? For example, on Малый проспект В.О. (Maliy Avenue of V.I.) the following consecutive ways all have exactly the same tags: http://www.openstreetmap.org/browse/way/31374333 http://www.openstreetmap.org/browse/way/31395443 http://www.openstreetmap.org/browse/way/29043983 http://www.openstreetmap.org/browse/way/31387923 http://www.openstreetmap.org/browse/way/31400577 http://www.openstreetmap.org/browse/way/36738855 http://www.openstreetmap.org/browse/way/31893349 http://www.openstreetmap.org/browse/way/60948948 Can you or someone else explain why the street was mapped using so many ways? The next way along the same street, http://www.openstreetmap.org/browse/way/35497072 has the tag railway:tram added so it's correct to be split at the node, http://www.openstreetmap.org/browse/node/308322656 Regards, Simon. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
On Wed, Jun 30, 2010 at 01:16:41AM -0700, Simon Biber wrote: zve...@textual.ru zve...@textual.ru wrote: Those names are not rendered, obviously, because most streets consist of several ways, due to routing and public transport reasons. Hmm, what routing reasons? Different parts of the street may be part of different public transport relations. However, in your example area, many of the streets are divided into what seems like an unnecessarily large number of ways. If the tagging doesn't change between adjacent ways, then shouldn't the ways be merged into a single way? For example, on Малый проспект В.О. (Maliy Avenue of V.I.) the following consecutive ways all have exactly the same tags: http://www.openstreetmap.org/browse/way/31374333 http://www.openstreetmap.org/browse/way/31395443 These two are parts of different set of relations. I have not checked others. Greets, Jacek ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
I just wrote simonbi...@yahoo.com.au: However, in your example area, many of the streets are divided into what seems like an unnecessarily large number of ways. If the tagging doesn't change between adjacent ways, then shouldn't the ways be merged into a single way? Sorry, please disregard that, I see now that the relation memberships are different. Nobody bothered to map bus routes in my area of the planet yet! I agree with the OP, would be nice to see the rendering improved for this case. Regards, Simon. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
On Wed, Jun 30, 2010 at 5:54 PM, zve...@textual.ru wrote: As you can see, on islands there are nine labels with street names, but plenty of space for such labels on many streets and avenues. Those names are not rendered, obviously, because most streets consist of several ways, due to routing and public transport reasons. Is there any plan, or just a thought, to merge ways on a rendering stage to display more street name labels? If not, why? Is there a renderer which does that? I suggest you file a Mapnik bug in the trac. Steve ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
On 1 July 2010 11:19, Steve Bennett stevag...@gmail.com wrote: On Wed, Jun 30, 2010 at 5:54 PM, zve...@textual.ru wrote: As you can see, on islands there are nine labels with street names, but plenty of space for such labels on many streets and avenues. Those names are not rendered, obviously, because most streets consist of several ways, due to routing and public transport reasons. Is there any plan, or just a thought, to merge ways on a rendering stage to display more street name labels? If not, why? Is there a renderer which does that? I suggest you file a Mapnik bug in the trac. -- But if mapnik is given a set of different ways to render, then presumably its current behaviour is correct and a bug report inappropriate. It's probably not appropriate for mapnik to make decisions about joining ways together; I assumed zverik's comment related to osm2pgsql or the like, where ways (or sets of relations) could be joined. b Ben Last Development Manager (HyperWeb) NearMap Pty Ltd ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Rendering street names across several ways
On Wed, Jun 30, 2010 at 9:54 AM, zve...@textual.ru wrote: Is there any plan, or just a thought, to merge ways on a rendering stage to display more street name labels? If not, why? Is there a renderer which does that? I have been doing some work on this for Maperitive, but it's not finished. You should also consider that after merging such ways (when rendering), the renderer needs to provide a good mechanism for repeating the street label for very long streets. Igor ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
