[Geoserver-users] bounding box

GeoServer GeoServer User
1

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

2

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:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; 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

3

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<mailto: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:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net<mailto:Geoserver-users@anonymised.comrge.net>
https://lists.sourceforge.net/lists/listinfo/geoserver-users

4

If you have not yet done VACUUM ANALYZE, do not do it yet. Do:

  1. Select accurate extents with ST_Extent http://postgis.net/docs/ST_Extent.html

  2. Check what ST_Estimated_Extent shows http://postgis.net/docs/manual-2.0/ST_Estimated_Extent.html

  3. Do VACUUM ANALYZE

  4. 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 count 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

5

See Jukka response,
if you are using the default settings in the postgis store it will compute the bbox using the estimated
extents function, if you want precise and up to date values you can disable it.
Mind, it will come at a cost, computing the bbox that way may take a while if you have many data
(e.g., millions of rows) and the cost will not just be paid on the user interface, but also for every
WFS request if you have the feature bounding options enabled in the WFS settings

Cheers
Andrea

···

On Wed, May 7, 2014 at 12:40 PM, Jonatan Malaver <jon.malaver@anonymised.com> 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@anonymised.comceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

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@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

==
Meet us at GEO Business 2014! in London! Visit http://goo.gl/fES3aK
for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it