[OSM-talk] tiles rendering
Jon Burgess
jburgess777 at googlemail.com
Wed Jan 31 23:11:35 GMT 2007
On Wed, 2007-01-31 at 22:36 +0000, Jon Burgess wrote:
> On Wed, 2007-01-31 at 21:43 +0000, Artem Pavlenko wrote:
> > Yes, good idea. We should only output 'closed' polygons
> >
> > if (polygon && start_point == end_point)
> > {
> > ...
> > }
> > else
> > {
> > ..
> > }
> >
> > Artem
>
>
> That didn't seem to make any difference.
>
> It seems the issue is in osm.xml. The PolygonSymbolizer will render any
> data as a polygon, even if the source data is a linestring :-). This
> attached patch makes things look much better in my eyes. The style may
> need more tweaking.
>
> The data I have loaded in postgis currently is from the "open areas are
> not polygons" version of osm2pgsql currently so I can't be 100% certain
> that this style change alone fixed it, but i'm quite confident the
> osm.xml change is sufficient.
>
> Please try it out on your system and see if it fixes the grey
> triangulated coastline.
>
> Jon
>
I found some issues with the last patch, I think this one renders more
cleanly at all zoom levels. It treats all natural= the same as
waterways, i.e draws as a blue line for the coastline.
The only downside I see with this is that natural=water no longer gets
filled, you'll just get a blue outline. This may effect ponds, lakes
etc.
Perhaps natural=water should be rendered as a polygon but I don't
understand the mapnik rule/scale/filter/else model well enough to make
the rendering work reliably at all zooms.
Jon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: natural-coastline2.diff
Type: text/x-patch
Size: 3233 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20070131/b68c2d25/attachment.bin>
More information about the talk
mailing list