Hi,
I'm still fighting a little with the BBOX KVP parsing along with the
AUTO:xywz,unit,lon,lat syntax.
The thing is, the CRS is not going down through the datastores, it's
lost along the way even
if it's properly parsed.
The issue this time is that the AUTO srs do not have an id, and even
if they would, it's
not the EPSG or URN or HTTP form recognized by the standard srs
mangling/guessing
code.
Our code builds first and envelope out of the bbox, and then in the
kvp reader tries
to build a bbox filter out of the envelope, where it has to get back
the original srs code
by doing some magic (and hoping the code is an EPSG one and that it
can be expressed
either in http or urn form).
The fact is, imho, there is a simpler way: BBOX In the WFS context is
not an envelope,
it's a filter. So, the WFS BBOX KVP parser should simply accept that reality and
build a BBOX filter instead (in which we can stick the srs as is,
without any guessing)
So that's what I'd like to do in fact: make a WFS specific bbox parser
that just builds
a filter, which is then used by the kvp reader as is while building the
request object.
Opinions?
Cheers
Andrea
-----------------------------------------------------
Ing. Andrea Aime
Senior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584962313
fax: +39 0584962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-----------------------------------------------------
Makes sense and +1 on the idea. Do you plan this change for trunk, or planning to backport to 2.0.x as well? I would be a bit leery about the latter but I will wait until things are implemented to comment on that.
On Thu, Oct 28, 2010 at 6:54 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:
Hi,
I’m still fighting a little with the BBOX KVP parsing along with the
AUTO:xywz,unit,lon,lat syntax.
The thing is, the CRS is not going down through the datastores, it’s
lost along the way even
if it’s properly parsed.
The issue this time is that the AUTO srs do not have an id, and even
if they would, it’s
not the EPSG or URN or HTTP form recognized by the standard srs
mangling/guessing
code.
Our code builds first and envelope out of the bbox, and then in the
kvp reader tries
to build a bbox filter out of the envelope, where it has to get back
the original srs code
by doing some magic (and hoping the code is an EPSG one and that it
can be expressed
either in http or urn form).
The fact is, imho, there is a simpler way: BBOX In the WFS context is
not an envelope,
it’s a filter. So, the WFS BBOX KVP parser should simply accept that reality and
build a BBOX filter instead (in which we can stick the srs as is,
without any guessing)
So that’s what I’d like to do in fact: make a WFS specific bbox parser
that just builds
a filter, which is then used by the kvp reader as is while building the
request object.
Opinions?
Cheers
Andrea
Ing. Andrea Aime
Senior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584962313
fax: +39 0584962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.