Hi,
Quick fix would be to feed the bounding box coordinates manually. That
automatic computing does not take into account the newly added features must
mean that something on the PostGIS side has not updated as supposed. Perhaps
Geoserver is doing query with ST_Estimated_Extent and you should run VACUUM
ANALYZE in your database
http://postgis.net/docs/manual-2.0/ST_Estimated_Extent.html.
-Jukka Rahkonen-
Jonatan Malaver wrote:
Hello,
I have a PostGIS store in Geoserver 2.4, where the computed native bounding
box x,y and lat/long are incorrect. When I try to preview the layer, the layer
is cut on the map. Could anyone help me resolve this problem? The postgis table
was recently updated (more geometry added). I'm having problems with the new
geometry added to the table. I have tried deleting the layer and adding it
again and problem persists.
Thanks,
Jon
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
