On Thu, 2009-11-26 at 00:58 +0100, Nop wrote:
> Hi!
>
> Lennard schrieb:
> > It seems osm2pgsql decided that your roundabout was an area, for it to
> > put it into the polygon table. Do they show up if you hack an area=no on
> > them?
>
> It will take a while to try that, but I think you are right. It probabyl
> assumed that the closed shape must be an area, though there is no area tag.
>
> I did not have this problem originally, but I am not sure when it first
> occurred. Was there a change to this effect in osm2pgsql? I am using
> 0.66-16423. Is there a way to globally force osm2pgsql not to make this
> assumption?
Can you provide a copy of your style file?
> What are the exact rules osm2pgsql uses in this case?
Generally it will convert a closed way into a polygon if it has a tag
which is marked as "polygon" in the style file. This does not appear to
be the case for any of the current tags, these are the entries in the
default.style:
node,way highway text linear
node,way name text linear
node,way ref text linear
node,way junction text linear
if your style has any of those as polygon instead of linear then this
would trigger it.
There is another possibility that it is triggered by the route relation
containing this way (153309). It looks like this route is also a
completely closed ring and it might just be trying to interpret this
route as a multipolygon. I think this might have a side-effect of
converting the closed roundabout way into a polygon too.
The odd thing is that the main OSM site interprets the same data
correctly so I believe there must either be a difference in the style or
newer osm2pgsql version.
Jon
_______________________________________________
Mapnik-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/mapnik-users
