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
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,
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)
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
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
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
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
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...
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
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
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
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
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
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
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
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
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
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
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
Steve Bennett wrote:
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.
Not quite. Where a dual carriageway becomes a single carriageway, this
would wrap the name around
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
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
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
Hi.
Take a look at Saint-Petersburg map at zoom 13:
http://www.openstreetmap.org/?lat=59.9496lon=30.2774zoom=13layers=B000FTF
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,
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
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
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
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
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,
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
30 matches
Mail list logo