Thanks for the replies.
I've updated the patch to introduce a srsInBBOX property.
http://trac.osgeo.org/openlayers/ticket/3006
Tim
On 1/5/11 1:02 PM, Eric Lemoine wrote:
On Wed, Jan 5, 2011 at 8:57 PM,<[email protected]> wrote:
On Jan 5, 2011, at 2:42 PM, ext Tim Schaub wrote:
Hey-
Are there people that use the HTTP protocol against services that would break
if the BBOX query string parameter included the SRS identifier?
E.g.
http://example.com/features?bbox=1,2,3,4,foo
The WFS 1.1 spec allows clients to specify the SRS for a bounding box by
including the SRS identifier as the fifth item in the array. I'd like to add
this functionality to the HTTP protocol if it wouldn't make existing
applications break.
FeatureServer would break; "action.bbox = map(float, value.split(","))" would
barf on
it if the value were not a float-able number, I believe.
Same for MapFish.
bbox = map(float, "1,2,3,4,foo".split(","))
Traceback (most recent call last):
File "<stdin>", line 1, in<module>
ValueError: invalid literal for float(): foo
--
Tim Schaub
OpenGeo - http://opengeo.org
Expert service straight from the developers.
_______________________________________________
Dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/openlayers-dev
