[TinyOWS-users] Using BBOX and srsName together with http GET

Olivier Courtin olivier.courtin at gmail.com
Fri Aug 5 07:38:13 EST 2011

On Fri, Aug 5, 2011 at 9:21 AM, Rahkonen Jukka
<Jukka.Rahkonen at mmmtike.fi> wrote:

> Running r586 now and behaves perhaps a bit better.  But perhaps before you continue it should be thought how is should behave.

Yeap could be helpfull ^^

> If some other srsName is given then the BBOX must use the same SRS than the output. Sounds reasonable, but should be documented.

13.3.3 in WFS 1.0.0
"The SRS of the bounding box must be the same of the feature type(s)
in a request. [...]"

> WFS 1.1.0 does not seem to work yet. TinyOWS takes now BBOX with the crsuri parameter
> However, result is empty with the srsname parameter.  I tried with both EPSG:2393 and urn:ogc:def:crs:EPSG::2393

r588 should fixed that.

> Perhaps before you continue it should be thought how is should behave. I would say that WFS 1.0.0 with BBOX using the same srsName that is defined for output.  With 1.1.0 it would be best if the user gives BBOX with five parameters to make sure what is the meaning.

Yes that's the spec said

> Otherwise BBOX shoud default to layer SRS. Or should it?  This would yield different results with 1.0.0 and 1.1.0 with the same BBOX.  Absolutely most safe to use five parameters with 1.1.0.

That's a point indeed !
After more time to think about it, i'd like to keep the strict spec
implementation way,

WFS 1.0.0
- no srsName : we use the storage layer srs
- srsName provided: same than the bbox

WFS 1.1.0
 - no crsuri in the bbox: 4326
 - crsuri provided: obvious

r589 should behave like that,


More information about the TinyOWS-users mailing list