> -----Original Message----- > From: andrea.a...@gmail.com [mailto:andrea.a...@gmail.com] On Behalf Of > Andrea Aime > Sent: 15 October 2013 18:24
> it's pretty simple, Doesn't seem so simple in my case ... :-( > See also: > http://docs.geoserver.org/latest/en/user/services/wfs/basics.html#axis- > ordering I hadn't read that documentation page (sorry) but I had guessed it might be worth experimenting with the style of specifying the EPSG code between short form and URN (and HTTP-URI) and it didn't change the result. However, knowing that it _should_ work I did some more experiments setting up a simple feature WFS based on the same spatial table that I'm using with my app-schema complex WFS. It seems that changing the EPSG URI style does work with the simple WFS but not the app-schema complex one. I edited the manually created featuretype.xml file in my app-schema configuration so that the srs, crs and bounding box information were the same as those in the featuretype.xml created by the web UI for my corresponding simple WFS as I thought that might be important but it didn't help either. Maybe an app-schema person can comment? Marcus For reference I have experimented with sending the basic example query below in a number of variations: 1 - Set typenames attribute to gsml:MappedFeature and fes:ValueReference for querying the app-schema complex feature or - set typenames to test:UK_625K_BEDROCK_WGS84 and fes:ValueReference to test:the_geom for querying the simple feature based on the same geometry table. 2 - Set srsName attribute (on both the Query element and gml:Envelope just to be safe) to EPSG:4326 or urn:ogc:def:crs:EPSG::4326 3 - Specify the envelope coordinates in lat-lon: <gml:lowerCorner>56.08643859340388 -4.0004826736994445</gml:lowerCorner> <gml:upperCorner>56.165510496146474 -3.8381055732299343</gml:upperCorner> or lon-lat: <gml:lowerCorner>-4.0004826736994445 56.08643859340388</gml:lowerCorner> <gml:upperCorner>-3.8381055732299343 56.165510496146474</gml:upperCorner> Example query: <?xml version="1.0" encoding="UTF-8"?> <GetFeature xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://www.opengis.net/wfs/2.0 http://schemas.opengis.net/wfs/2.0/wfs.xsd http://www.opengis.net/gml/3.2 http://schemas.opengis.net/gml/3.2.1/gml.xsd"; xmlns="http://www.opengis.net/wfs/2.0"; xmlns:gsml="http://xmlns.geosciml.org/GeoSciML-Core/3.2"; 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"; version="2.0.0" service="WFS" count="100"> <Query typeNames="gsml:MappedFeature" srsName="urn:ogc:def:crs:EPSG::4326"> <fes:Filter> <fes:BBOX> <fes:ValueReference>gsml:shape</fes:ValueReference> <gml:Envelope srsName="urn:ogc:def:crs:EPSG::4326"> <gml:lowerCorner>56.08643859340388 -4.0004826736994445</gml:lowerCorner> <gml:upperCorner>56.165510496146474 -3.8381055732299343</gml:upperCorner> </gml:Envelope> </fes:BBOX> </fes:Filter> </Query> </GetFeature> Querying the simple feature behaves as documented expecting coordinates in lon-lat if I use EPSG:4326 and lat-lon if I use urn:ogc:def:crs:EPSG::4326. Querying the app-schema feature, however, always expects lon-lat whethere I specify EPSG:4326 or urn:ogc:def:crs:EPSG::4326 This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system. ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
