That has been asked on stack exchange as well:
http://gis.stackexchange.com/questions/10049/updating-a-layers-bounding-box-in-geoserver-after-wfs-t-insert
You may be able to set up a WPS process to calculate the bounds (i.e. full
table scan of all content). I am not sure if there is a way to set up the
REST API to allow us to "kick" the layer into recalculating the bounds.
The code to calculate the bounds is attached to a button in the wicket user
interface, since calculating the bounds may take a long time it is not
something you want to do as you add features one at a time.
--
Jody
Jody Garnett
On Wed, Jun 11, 2014 at 7:21 PM, fanxing926 <[email protected]> wrote:
> Recently, I met a problem. My program need the geoserver compute a layer
> bounding box automaticly when I add a new feature to the layer. Could the
> geoserver provide the interface to the public?
> Thank you!
>
>
>
>
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> _______________________________________________
> Geoserver-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
