Hi, I had a look at the document http://schemas.opengis.net/gml/3.1.1/base/geometryBasic0d1d.xsd and I fear I start to understand. Envelope can be defined in four different ways, "lowerCorner+upperCorner", "coord", "pos", and "coordinates". The first choise "lowerCorner+upperCorner" is the one to use and the three others are deprecated , but they are not denied. That must mean that all four should be supported. Thank god I am not a developer but this mess makes living hard also for a user who wants to understand what is happening under the roof.
<complexType name="EnvelopeType"> ... <choice> <sequence> <element name="lowerCorner" type="gml:DirectPositionType"/> <element name="upperCorner" type="gml:DirectPositionType"/> </sequence> <element ref="gml:coord" minOccurs="2" maxOccurs="2"> <annotation> <appinfo>deprecated</appinfo> <documentation>deprecated with GML version 3.0</documentation> </annotation> </element> <element ref="gml:pos" minOccurs="2" maxOccurs="2"> <annotation> <appinfo>deprecated</appinfo> <documentation>Deprecated with GML version 3.1. Use the explicit properties "lowerCorner" and "upperCorner" instead.</documentation> </annotation> </element> <element ref="gml:coordinates"> <annotation> <documentation>Deprecated with GML version 3.1.0. Use the explicit properties "lowerCorner" and "upperCorner" instead.</documentation> </annotation> </element> </choice> -Jukka Rahkonen- > -----Alkuperäinen viesti----- > Lähettäjä: Rahkonen Jukka [mailto:[email protected]] > Lähetetty: 23. toukokuuta 2011 13:25 > Vastaanottaja: [email protected] > Aihe: [Geoserver-users] WFS 1.1.0 and GML version in filters > > Hi, > > I know that WFS 1.0.0 is having GML2 as a default > outputformat and 1.1.0 > is using text/xml; subtype=gml/3.1.1. But how it is with the input, > should the gml used if filters use the same versions? I thought I can > find it by studying the Geoserver demo requests but they are > ambiguous. > > WFS_getFeatureBBOX-1.0.xml is using > <ogc:BBOX> > <ogc:PropertyName>the_geom</ogc:PropertyName> > <gml:Box > srsName="http://www.opengis.net/gml/srs/epsg.xml#4326"> > <gml:coordinates>-75.102613,40.212597 > -72.361859,41.512517</gml:coordinates> > </gml:Box> > </ogc:BBOX> > > WFS_getFeatureBBOX-1.1.xml is using > <ogc:BBOX> > <ogc:PropertyName>the_geom</ogc:PropertyName> > <gml:Envelope > srsName="http://www.opengis.net/gml/srs/epsg.xml#4326"> > <gml:lowerCorner>-75.102613 40.212597</gml:lowerCorner> > <gml:upperCorner>-72.361859 41.512517</gml:upperCorner> > </gml:Envelope> > </ogc:BBOX> > > This looks logical, WFS 1.0.0=GML2, WFS 1.1.0=GML3. But then > > WFS_getFeatureIntersects-1.0.xml > <Intersects> > <PropertyName>the_geom</PropertyName> > <gml:Point > srsName="http://www.opengis.net/gml/srs/epsg.xml#4326"> > <gml:coordinates>-74.817265,40.5296504</gml:coordinates> > </gml:Point> > </Intersects> > > WFS_getFeatureIntersects-1.1.xml > <Intersects> > <PropertyName>the_geom</PropertyName> > <gml:Point > srsName="http://www.opengis.net/gml/srs/epsg.xml#4326"> > <gml:coordinates>-74.817265,40.5296504</gml:coordinates> > </gml:Point> > </Intersects> > > Both the 1.0.0 and 1.1.0 demo requests are giving the_geom as > GML2. Does > it mean that both GML2 and GML3 are equally acceptable in the WFS > filters? However, I am pretty sure that using gml:Box in WFS 1.1.0 has > been doomed forbidden because GML3 does not define Box. Then why > gml:coordinates are still accepted? > > -Jukka Rahkonen- > > -------------------------------------------------------------- > ---------------- > What Every C/C++ and Fortran developer Should Know! > Read this article and learn how Intel has extended the reach of its > next-generation tools to help Windows* and Linux* C/C++ and Fortran > developers boost performance applications - including clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > Geoserver-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users > ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
