If you have not yet done VACUUM ANALYZE, do not do it yet. Do:
-
Select accurate extents with ST_Extent http://postgis.net/docs/ST_Extent.html
-
Check what ST_Estimated_Extent shows http://postgis.net/docs/manual-2.0/ST_Estimated_Extent.html
-
Run VACUUM ANALYZE
-
Repeat 2.
See if 2. and 4. gives different results. If yes, we know that VACUUM ANALYZE is useful. Try then what extents Geoserver gets with compute from data.
-Jukka Rahkonen-
···
Jonatan Malaver wrote:
It changed but not to the correct bounding box.
-------- Original message --------
From: Russell Hore
Date:05/07/2014 3:04 AM (GMT-05:00)
To: Jonatan Malaver
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] bounding box
Go to the layer in the Administration interface.
"Under Bounding Box” click on ‘Compute from Data’ (and ‘Compute from native bounds’ ?). See if the coords change.
Save the layer
Russ
On 6 May 2014, at 19:26, Jonatan Malaver <jon.malaver@anonymised.com> 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
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users