Hi,
Clearly EPSG:4258 should use lat-lon (north-east) order in all places if it is
GML3. Thus your filter is right and the response wrong.
http://epsg-registry.org/report.htm?type=selection&entity=urn:ogc:def:crs:EPSG::4258&reportDetail=short&style=urn:uuid:report-style:default-with-code&style_name=OGP%20Default%20With%20Code&title=4258
I wonder the first wfs:boundedBy. How can we know that it is using EPSG:4258
if it comes without srsName?
<wfs:boundedBy>
<gml:Envelope>
<gml:lowerCorner>46.34715 0.05296</gml:lowerCorner>
<gml:upperCorner>48.94105 3.12903</gml:upperCorner>
</gml:Envelope>
</wfs:boundedBy>
-Jukka Rahkonen-
Florent Gravin wrote:
Hi,
I've read the geoserver topic, maybe XY has to be inverted, but whatever it
should be inverted in all situation ? i mean in the GetFeatureResponse, and in
my filterRequest.
For exemple :
<?xml version="1.0" encoding="UTF-8"?>
<GetFeature
version="2.0.0"
service="WFS"
xmlns="http://www.opengis.net/wfs/2.0"
xmlns:fes="http://www.opengis.net/fes/2.0"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:gml="http://www.opengis.net/gml/3.2"
xmlns:au="urn:x-inspire:specification:gmlas:AdministrativeUnits:3.0"
xmlns:base="urn:x-inspire:specification:gmlas:BaseTypes:3.2"
xmlns:gmd="http://www.isotc211.org/2005/gmd">
<Query typeNames="au:AdministrativeUnit">
<fes:Filter>
<fes:BBOX>
<fes:ValueReference>au:geometry</fes:ValueReference>
<gml:Envelope srsName="EPSG::4258">
<gml:lowerCorner>1.32709 48.49261</gml:lowerCorner>
<gml:upperCorner>1.37412 48.52348</gml:upperCorner>
</gml:Envelope>
</fes:BBOX>
</fes:Filter>
</Query>
</GetFeature>
will give the response :
<wfs:FeatureCollection numberMatched="unknown" numberReturned="1"
timeStamp="2012-11-23T09:32:22.726Z"
xsi:schemaLocation="http://www.opengis.net/gml/3.2
http://schemas.opengis.net/gml/3.2.1/gml.xsd http://www.opengis.net/wfs/2.0
http://schemas.opengis.net/wfs/2.0/wfs.xsd
urn:x-inspire:specification:gmlas:AdministrativeUnits:3.0
file:/home/fgravin/dev/ign/igngeoserver/data/nuts/workspaces/au/au_AdministrativeUnits/AdministrativeUnits.xsd">
<wfs:boundedBy>
<gml:Envelope>
<gml:lowerCorner>46.34715 0.05296</gml:lowerCorner>
<gml:upperCorner>48.94105 3.12903</gml:upperCorner>
</gml:Envelope>
</wfs:boundedBy>
<wfs:member>
<au:AdministrativeUnit gml:id="FR2400000000">
<gml:boundedBy>
<gml:Envelope srsDimension="2" srsName="EPSG:4258">
<gml:lowerCorner>46.34715 0.05296</gml:lowerCorner>
<gml:upperCorner>48.94105 3.12903</gml:upperCorner>
</gml:Envelope>
</gml:boundedBy>
<au:geometry>
XY are not in the same order in the request and in the response.
My investigations lead me further :
It is in Object visit(BBOX filter, Object extraData) {
This is where it try to retrieve the targetCrs, from the propertyName,
considering the featureType.
Seems it works well with Tasmania simpleFeatureType and topp:the_geom.
But in my case, i am using complexFeatureType and maybe the AttributeDescriptor
at = (AttributeDescriptor) propertyName.evaluate(featureType); cannot retrieve
properly the CRS from complexFeature.
Either it is a bug from app-schema, or i have something to specify in my schema
to match the propertyName and the CRS somewhere i don't know
do you have any idea ?
thanks
On Thu, Nov 22, 2012 at 6:30 PM, Andrea Aime
<andrea.a...@geo-solutions.it<mailto:andrea.a...@geo-solutions.it>> wrote:
On Thu, Nov 22, 2012 at 5:50 PM, Florent Gravin
<florent.gra...@camptocamp.com<mailto:florent.gra...@camptocamp.com>> wrote:
Hi,
My GetFeature response gives me :
<gml:boundedBy>
<gml:Envelope srsDimension="2" srsName="EPSG:4258">
<gml:lowerCorner>47.57657 3.38328</gml:lowerCorner>
<gml:upperCorner>50.1692 5.89086</gml:upperCorner>
</gml:Envelope>
</gml:boundedBy>
If i want to make a WFS request with filter BBOX, i have to switch long lat to
make it work :
<gml:Envelope srsDimension="2" srsName="EPSG:4258">
<gml:lowerCorner>3.38328 47.57657</gml:lowerCorner>
<gml:upperCorner>5.89086 50.1692</gml:upperCorner>
</gml:Envelope>
I debug into WFSReprojectionUtil.normalizeFilterCRS(filter, source.getSchema(),
declaredCRS);
where the convertion could be done
I've tested for Tasmania default layer that is in EPSG:4326, i used the same
order to make the BBOX filter work ... anyway i've heard 4326 has inverted XY ..
Any way my question is :
Whatever the projection is, should the reponse and the filter envelope XY order
HAVE TO be the same ?
Is there a bug somewhere ?
It's difficult to tell, you're not giving us enough information.
Please have a look here:
http://docs.geoserver.org/latest/en/user/services/wfs/basics.html#axis-ordering
And then report again with the full request and enough of each response so that
we can
look into it
Cheers
Andrea
--
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313<tel:%2B39%200584%20962313>
fax: +39 0584 1660272<tel:%2B39%200584%201660272>
mob: +39 339 8844549<tel:%2B39%20%C2%A0339%208844549>
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
--
Florent Gravin
Camptocamp - Chambéry
0479444492
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users