On Fri, 2008-10-31 at 17:34 +0200, Rahkonen Jukka wrote:
> Hi,
>
> I noticed earlier that nik2img.py was missing some coastline elements
> while generate_image.py brings them all to the resulting map.
>
> I believe now that I have isolated the reason for different behaviour
> from PostGIS statement logs.
>
> This seems to be how the database will be queried when nik2img.py is
> used.
> select asbinary(way) as way FROM shoreline_a where way &&
> setSRID('BOX3D(2796623.487632482 8414856.658170387,3648235.036730606
> 8450106.434262134)'::box3d,900913)
>
> Using generate_image.py leads to a bit different query
>
> select asbinary(way) as geom from (select way from shoreline_a) as
> "coast-poly" where way && setSRID('BOX3D(2760723.371673184
> 8425528.555575622,2805251.167990494 8470056.351892933)'::box3d,900913)
>
> I do not quite understand why these queries are giving different
> results, but they really do. I verified that be sending those
> directly with OpenJUMP GIS and indeed, the nik2img query is giving a
> map that is missing lots of islands. Not all islands, though.
I don't want to state the obvious but the bounding boxes are different.
Perhaps try updating the BOX3D in one and see if the data matches?
Jon
_______________________________________________
Mapnik-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/mapnik-users
