Encoded GML 3.2 MultiSurface is schema-invalid because contained Polygon lacks
gml:id
-------------------------------------------------------------------------------------
Key: GEOT-3824
URL: https://jira.codehaus.org/browse/GEOT-3824
Project: GeoTools
Issue Type: Bug
Components: xsd-gml
Affects Versions: 2.7.3, 8.0-M2
Reporter: Ben Caradoc-Davies
Assignee: Justin Deoliveira
GML 3.2 geometries have a mandatory gml:id attribute. When MultiSurface is
encoded, even if the top-level geometry has a gml:id, the encoded GML is
schema-invalid because contained geometries go not have gml:id. This will
likely affect all multi-geometries.
{noformat}
<gml:MultiSurface gml:id="shape.mf.1">
<gml:surfaceMember>
<gml:Polygon> <!-- this is schema-invalid because gml:id is required -->
<gml:exterior>
<gml:LinearRing>
<gml:posList>268926.0 4810180.0 268926.0 4829560.0 296474.0 4829560.0 296474.0
4810180.0 268926.0 4810180.0</gml:posList>
</gml:LinearRing>
</gml:exterior>
</gml:Polygon>
</gml:surfaceMember>
</gml:MultiSurface>
{noformat}
it
app-schema can put a gml:id on the top-level feature (as in this case), but
knows nothing about the structure of contained geometries.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management
Up to 160% more powerful than alternatives and 25% more efficient.
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
