[mapguide-trac] #1421: OGC WFS 1.1.0 Support
MapGuide Open Source
trac_mapguide at osgeo.org
Wed Sep 29 04:10:48 EDT 2010
#1421: OGC WFS 1.1.0 Support
-----------------------------+----------------------------------------------
Reporter: liuar | Owner: liuar
Type: enhancement | Status: new
Priority: medium | Milestone:
Component: WFS Interface | Version:
Severity: minor | Keywords: WFS
External_id: |
-----------------------------+----------------------------------------------
Comment(by liuar):
13 Test wfs:wfs-1.1.0-Basic-GetFeature-tc8.1
(s0001/d1e35137_1/d1e740_1/d1e25217_1/d1e6162_1)
Assertion: A KVP parameter value that denotes a bounding box shall conform
to the general syntax specified in subclause 10.2.3. If no CRS reference
is provided, a service-defined default value must be assumed.
The API GetWfsFeature which response to the GetFeature request doesn't
support mutilple spatial query like:
{{{
(surfaceProperty ENVELOPEINTERSECTS GeomFromText('POLYGON((-180 -90,180
-90,180 90,-180 90,-180 -90))')) OR (pointProperty ENVELOPEINTERSECTS
GeomFromText('POLYGON((-180 -90,180 -90,180 90,-180 90,-180 -90))')) OR
(curveProperty ENVELOPEINTERSECTS GeomFromText('POLYGON((-180 -90,180
-90,180 90,-180 90,-180 -90))'))
}}}
It just do query on the default geometry property, and features responsed
to the client is less then expected. I extended the GetWfsFeature API to
make sure MapGuide could process the spatial query on multiple geometry
properties.
NOTE: Some FDO providers don't support OR with spatial query like
Postgis/Posstgres Provider.
Another problem is that WFS 1.1.0 support URN SRS like
(urn:ogc:def:crs:EPSG::4326) which is not supported by MapGuide. In order
to support the URN SRS, I did a work around to replace the text
"urn:ogc:def:crs:EPSG:" with "EPSG".
Changeset [5209] by liuar
--
Ticket URL: <http://trac.osgeo.org/mapguide/ticket/1421#comment:10>
MapGuide Open Source <http://mapguide.osgeo.org/>
MapGuide Open Source Internals
More information about the mapguide-trac
mailing list