On Mon, 2008-10-27 at 21:39 +0200, Rahkonen Jukka wrote:
> This is what happened after reprojecting all OSM data in Postgis by
>
> update gosm_point set way=transform(way,32635);
> update gosm_line set way=transform(way,32635);
> update gosm_polygon set way=transform(way,32635);
> update geometry_columns set srid=32635 where
> f_table_name='gosm_point';
> update geometry_columns set srid=32635 where f_table_name='gosm_line';
> update geometry_columns set srid=32635 where
> f_table_name='gosm_polygon';
>
> and editing osm.xml to suit the new epsg:32635 projection by having in
> all places
> srs="+proj=utm +zone=35 +ellps=WGS84 +datum=WGS84 +units=m +no_defs"
Have you adjusted the 'extent' parameters for your layers in the osm.xml
file:
<Parameter name="extent">-20037508,-19929239,20037508,19929239</Parameter>
You could simply try removing all those lines. This will cause Mapnik to
query the DB to work out the extents. This will be slow since it has to
scan all the data.
The default extent represents the whole Earth in spherical mercator. I
have not tried any UTM projections but we've seen issues previously when
wrapping occurs during reprojection. It can lead to the sorts of odd
bounding boxes like you are seeing where a 'minimum' co-oridinate in one
co-ordincate system wraps and becomes a maximum when projected.
The default extent numbers will be completely bogus if you've
reprojected all the source data.
Jon
_______________________________________________
Mapnik-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/mapnik-users
