On Tue, 2009-12-22 at 16:16 -0700, Dane Springmeyer wrote:
> > The only solution to get a correct map ist to set the parameter
> > ="estimate_extent" to false, but then the whole table will be
> > scanned and
> > the rendering time is much too long. I also tried to reduce the
> > extent of
> > the layer for rendering smaller areas:
> >
> > <Parameter name="estimate_extent">false</Parameter>
> > <Parameter name="extent">9.2,47.0,13.7,48.8</Parameter>
> >
> > But when I want to render the whole country, then this is no
> > solution. See
The estimated_extent feature in postgres was never intended to be relied
upon to provide accurate information in all cases.
The general solution is to set estimated_extent to false and set the
extent to include all your data, or -180,-90,180,90 if you have the
whole world.
Mapnik uses this extent when deciding whether the layer contains data
which might be visible in a given tile. If you set it too large but
never render tiles for the larger area then this should generally avoid
any problems.
The one exception to this occurs if your rendering your map to some
projection where the extent is either invalid or wraps. This can also
cause odd effects. In this case you should restrict the extent to
something which is within the valid bounds of your map projection.
Jon
_______________________________________________
Mapnik-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/mapnik-users
