Changes between Version 91 and Version 92 of MapServerOGCCITECompliance
- Timestamp:
- Dec 11, 2009, 5:05:07 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MapServerOGCCITECompliance
v91 v92 10 10 || ||1.0.0 ||[http://trac.osgeo.org/mapserver/ticket/2606 2606]||Add multipoint, multipolygon, multilinestring geometries support to define an area in a spatial filter, when a GetFeature request is sent to a WFS 1.0.0 server ||Could be harder || 11 11 ||WFS ||1.1.0 ||[http://trac.osgeo.org/mapserver/ticket/3076 3076] ||DefaultSRS string value is stripped off from the end. ||Fixed by Assefa, Assefa to verify || 12 || ||1.1.0 ||[http://trac.osgeo.org/mapserver/ticket/2445 2445]||Add a mechanism to support gml:_geometryProperty for a WFS 1.0.0 server || || 12 13 || ||1.1.0 ||[http://trac.osgeo.org/mapserver/ticket/2899 2899] ||axis order must be in order lat long for 4326 for 1.1.0 ||Fixed by Assefa. || 13 14 || ||1.1.0 || ||The main issue is that the layer contains multiple geometry types on the same layer ||Could be really harder. Daniel submitted an idea to solve this. || … … 247 248 - The tests suite was run but stopped because the capabilities document does not validate ([http://trac.osgeo.org/mapserver/ticket/3076 3076]). 248 249 - Axis order must be in order lat long for 4326 for 1.1.0 ([http://trac.osgeo.org/mapserver/ticket/2899 2899]). 250 - XML validation failed. We need to make it possible to specify that the geometry is using one of the predefined properties from the GML 2.1.2 feature.xsd schema by referring to the GML schema definition and using the property in the 'gml:...' namespace instead of defining a new property in the namespace of the MapServer WFS service([http://trac.osgeo.org/mapserver/ticket/2445 2445]). 251 249 252 250 253 All bugs are shown with this query: