Hi all,
I’m developing an application which connects to a PostGIS datastore and
has line and polygon featuretypes using GS1.5.3.
The problem is that in my migration to Geoserver 1.6.0 release, the
behaviour of WFS GetFeature differs with GS1.5.3.
Request on Geoserver 1.5.3 is more restrictive and accurate than in GS
1.6.0.
They are in separate tomcats each.
Watching the tomcat output I can see the request made is different (I’m
not sure of what it’s doing really).
For GS 1.5.3 it returns one entity and the tomcat output for the request is:
[INFO] org.vfny.geoserver.servlets
.AbstractSErvice - handling request:
Request: null
output format: GML2
max features:2147483647
version: 1.0.0
Query
feature type: topp:buildings
filter: [ the_geom intersects POLYGON ((260405 4143267, 260405
4143381, 260519 4143381, 260519 4143267, 260405 4143267)) ]
[properties: ALL]
For GS 1.6.0 it returns two entities, and the tomcat output describing
the request is:
21 feb 16:36:29 INFO [geoserver.wfs] -
Request: getFeature
handle = null
service = WFS
version = 1.0.0
baseUrl =http://localhost:8080/geoserver/
query = [net.opengis.wfs.impl.QueryTipyeImpl@anonymised.com
(group: null, propertyName: null, funcion: null, filter: [ the_geom bbox
POLYGON ((260405 4143267, 260405 4143381, 260519 4143381, 260519
4143267, 260405 4143267)) ], sortBy: null, featureVersion: null, handle:
null, srsName: null, typeName: [{http://www.openplans.org/topp}buildings]
maxFeatures = null
output format: GML2
resultType = results
traverseXlinkDepth = null
traverseXlinkExpiry = null
Has changed the meaning of the request to the PostGIS database?
With roads also happens something similar. GS160 seems to return all roads
whose bbox surrounds the request’s bbox (although the road surrounds and
not intersects the request’s bbox) and also the roads which intersects the
request’s bbox.
Thank you in advance.
Regards,
paddy
Patrick O'Brian wrote:
Hi all,
I'm developing an application which connects to a PostGIS datastore and
has line and polygon featuretypes using GS1.5.3.
The problem is that in my migration to Geoserver 1.6.0 release, the
behaviour of WFS GetFeature differs with GS1.5.3.
Request on Geoserver 1.5.3 is more restrictive and accurate than in GS
1.6.0.
They are in separate tomcats each.
Watching the tomcat output I can see the request made is different (I'm
not sure of what it's doing really).
For GS 1.5.3 it returns one entity and the tomcat output for the request
is:
[INFO] org.vfny.geoserver.servlets.AbstractSErvice - handling request:
Request: null
output format: GML2
max features:2147483647
version: 1.0.0
Query
feature type: topp:buildings
filter: [ the_geom intersects POLYGON ((260405 4143267, 260405
4143381, 260519 4143381, 260519 4143267, 260405 4143267)) ]
[properties: ALL]
For GS 1.6.0 it returns two entities, and the tomcat output describing
the request is:
21 feb 16:36:29 INFO [geoserver.wfs] -
Request: getFeature
handle = null
service = WFS
version = 1.0.0
baseUrl =http://localhost:8080/geoserver/
query = [net.opengis.wfs.impl.QueryTipyeImpl@anonymised.com
(group: null, propertyName: null, funcion: null, filter: [ the_geom bbox
POLYGON ((260405 4143267, 260405 4143381, 260519 4143381, 260519
4143267, 260405 4143267)) ], sortBy: null, featureVersion: null, handle:
null, srsName: null, typeName:
[{http://www.openplans.org/topp\}buildings<http://www.openplans.org/topp}buildings>
]
maxFeatures = null
output format: GML2
resultType = results
traverseXlinkDepth = null
traverseXlinkExpiry = null
Has changed the meaning of the request to the PostGIS database?
With roads also happens something similar. GS160 seems to return all roads
whose bbox surrounds the request's bbox (although the road surrounds and
not intersects the request's bbox) and also the roads which intersects the
request's bbox.
Hum, I have a hunch on what's going on but I'll have to check.
If you are using Postgis the datastore is configured by default to use
"fast bbox" opeartion that do compare only the bbox of geometries
instead of doing bbox to pre-filter and intersects to fine tune:
this setting allows for faster WMS rendering but makes bbox in
GetFeature less accurate.
The setting is available on both versions of geoserver and it
has not changed between 1.5.3 and 1.6.0, but it may be that the
datastore is configured in a different way in the two geoserver installs?
Can you double check and see how "fast bbox" is configured in the
datastores of your two geoserver installs?
Cheers
Andrea
--
View this message in context: http://www.nabble.com/WFS-getFeature-in-GS1.6.0-tp15615304p15629440.html
Sent from the GeoServer - User mailing list archive at Nabble.com.