Hi there,
i've run into a problem with GET requests going to geoserver, oracle
is the datasource, openlayers is the client.
In this case i'm overlaying a google map, but the problem also exists
even when its a straight epsg:4326 map.
It seems that openlayers asks this of the WFS to render a WFS layer:
easier to read version:
http://localhost/geoserver/wfs
?typename=acted%3ALOCATION_PROFILES
&VERSION=1.1.0
&SERVICE=WFS
&REQUEST=GetFeature
&SRS=EPSG%23900913
&BBOX=31.327875542134397,17.681011813612997,101.64037553932717,46.82662679640924
that results in a null SRID going to oracle, and the stack trace shows
oracle bitching about that.
if however you fix the above url so the hash (#) is not url encoded,
the request works fine.. but strangely the value of the epsg code
given makes no difference to the coordinates or features returned. In
fact as long as the SRS parameter contains the hash it works, if not
it never does. No use of URN_blah or the EPSG:xxxx method works.
(grumbles bout how many ways to define a srs there needs to be).
Looking closer, geoserver isn't applying a spatial filter to the query
unless there is a hash in the url, in which case it never matches the
epsg to the SRID.
geoserver is 1.7.0RC2, running on tomcat 5.5.
WMS is working fine with reprojections in 1.7.0rc2.
To fix this i downloaded 1.6.4b, and here it seems the SRS parameter
is completely ignored (can be missing or wrong) so the problem goes
away.
keeping track of which geoserver version uses what srs descriptor for
each wfs version and which ones are optional and which ones make a
difference to what service is a challenge.. is there a table/doco
somewhere ?
incidentally after downloading 'stable' 1.6.4b i find it doesn't work
with WMS coz of this bug:
http://www.nabble.com/Problem-Geoserver-1.6.4-and-Oracle-Spatial-(10.2)-td19182679.html
shouldn't these fixes be moved to the 'stable production' download ?
so i'm all fixed but i just wanted to report this possible problem
with the WFS requests for the latest RC
thanks peoples,
-i
