Hello All,
I'm planning to upgrade our production Geoserver from 1.6.5 to the latest
1.7.2. To test things, I have a 1.7.2 instance running on mu local machine;
I pointed it to all the same data stores as the production instance. But in
the course of testing some of our apps, I notice that a WFS GetFeature
request to the 1.7.2 instance does not return a bounding box, whereas the
1.6.5 instance does. The rest of the returned GML are identical. Here is
the request, followed by that 1.7.2 node in question, followed by the
correct 1.6.5 node:
http://localhost:8080/geoserver/wfs?version=1.0.0&request=GetFeature&typeNam
e=cei:farm_catch_09
<gml:boundedBy>
<gml:null>unknown</gml:null>
</gml:boundedBy>
<gml:boundedBy>
<gml:Box srsName="EPSG:102003">
<gml:coordinates decimal="." cs="," ts=" ">-512465.7812,-813417.625
1538194.875,508452.625</gml:coordinates>
</gml:Box>
</gml:boundedBy>
Any ideas as to why this is happening? One thought I have it that the data
store in question is postgreSQL 7.4.19 with postGIS 1.2; is this too old for
the latest Geoserver?
Thanks,
Steve
Stephen Crawford
Center for Environmental Informatics
The Pennsylvania State University
Stephen Crawford wrote:
Hello All,
I'm planning to upgrade our production Geoserver from 1.6.5 to the latest
1.7.2. To test things, I have a 1.7.2 instance running on mu local machine;
I pointed it to all the same data stores as the production instance. But in
the course of testing some of our apps, I notice that a WFS GetFeature
request to the 1.7.2 instance does not return a bounding box, whereas the
1.6.5 instance does. The rest of the returned GML are identical. Here is
the request, followed by that 1.7.2 node in question, followed by the
correct 1.6.5 node:
http://localhost:8080/geoserver/wfs?version=1.0.0&request=GetFeature&typeNam
e=cei:farm_catch_09
<gml:boundedBy>
<gml:null>unknown</gml:null>
</gml:boundedBy>
<gml:boundedBy>
<gml:Box srsName="EPSG:102003">
<gml:coordinates decimal="." cs="," ts=" ">-512465.7812,-813417.625
1538194.875,508452.625</gml:coordinates>
</gml:Box>
</gml:boundedBy>
Any ideas as to why this is happening? One thought I have it that the data
store in question is postgreSQL 7.4.19 with postGIS 1.2; is this too old for
the latest Geoserver?
Hum... going into the geoserver config and enabling "feature bounding" is supposed to return bounds for both features and collections at the
same time.
The collection bounds have been disabled by default to avoid the server
being stuck computing bounds for big collections (millions of features)
for minutes and minutes, but "feature bounding" should turn both back
on (single feature and collection bounds alike).
If this is not happening, it's a bug. I'm going to double check with
my local instance.
Cheers
Andrea
I only got the feature and not the collection bounds when I indicated in
WFS/Contents to "Generate Feature Bounds".
By the way, where in the config tiles does the "Generate Feature Bounds"
checkbox on the UI translate to?
I couldn't find...
I just checked "Generate Feature Bounds" and now I get BOTH the collection
bounds and the feature bounds; in 1.6.5 I was getting only the collection
bounds.
I just checked and this behavior is for wfs 1.0; for wfs 1.1 I now get the
bounds for each feature, not for the collection.
...now to see if my apps still work 
Thanks,
Steve
-----Original Message-----
From: Freeman, Aleda (EEA) [mailto:Aleda.Freeman@anonymised.com]
Sent: Thursday, March 05, 2009 1:30 PM
To: Andrea Aime; Stephen Crawford
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] no bounding box?
I only got the feature and not the collection bounds when I indicated in
WFS/Contents to "Generate Feature Bounds".
By the way, where in the config tiles does the "Generate Feature Bounds"
checkbox on the UI translate to?
I couldn't find...
----------------------------------------------------------------------------
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
OK, let me change the setting for me again, maybe I misremembered from
yesterday.
Yes, Stephen is correct - checking "Generate Feature Bounds" does for
1.0.0 WFS bring both collection and feature bounds back. Sorry for my
misstatement before. For 1.1.0 I only get the feature bounds not the
collection. I see http://jira.codehaus.org/browse/GEOS-2583, thanks!
Stephen Crawford wrote:
I just checked "Generate Feature Bounds" and now I get BOTH the collection
bounds and the feature bounds; in 1.6.5 I was getting only the collection
bounds.
I just checked and this behavior is for wfs 1.0; for wfs 1.1 I now get the
bounds for each feature, not for the collection.
Yeah, known issue, I'm just fixing it: GEOS-2583
Cheers
Andrea