GML is an OGC Standard.
Copyright (c) 2001,2005,2010 Open Geospatial Consortium.
To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ .
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Source
<element name="_TopoPrimitive" type="gml:AbstractTopoPrimitiveType" abstract="true" substitutionGroup="gml:_Topology"><annotation><documentation>Substitution group branch for Topo Primitives, used by TopoPrimitiveArrayAssociationType</documentation></annotation></element>
Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the
XML Schema Section 4.14 Referencing Schemas from Elsewhere.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the
XML Schema Section 4.14 Referencing Schemas from Elsewhere.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the
XML Schema Section 4.14 Referencing Schemas from Elsewhere.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the
XML Schema Section 4.14 Referencing Schemas from Elsewhere.
Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the
XML Schema Section 4.14 Referencing Schemas from Elsewhere.
Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the
XML Schema Section 4.14 Referencing Schemas from Elsewhere.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the
XML Schema Section 4.14 Referencing Schemas from Elsewhere.
<element name="maximalComplex" type="gml:TopoComplexMemberType"><annotation><appinfo><sch:pattern name="refAndContent co-occurence prohibited"><sch:rule context="gml:subComplex"><sch:extends rule="hrefOrContent"/></sch:rule></sch:pattern></appinfo><documentation>Need schamatron test here that isMaximal attribute value is true</documentation></annotation></element>
Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the
XML Schema Section 4.14 Referencing Schemas from Elsewhere.
Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the
XML Schema Section 4.14 Referencing Schemas from Elsewhere.
Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the
XML Schema Section 4.14 Referencing Schemas from Elsewhere.
Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the
XML Schema Section 4.14 Referencing Schemas from Elsewhere.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the
XML Schema Section 4.14 Referencing Schemas from Elsewhere.
Its optional co-boundary is a set of connected directedEdges. The orientation of one of these dirEdges is "+" if the Node
is the "to" node of the Edge, and "-" if it is the "from" node.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Source
<complexType name="NodeType"><annotation><documentation>Its optional co-boundary is a set of connected directedEdges. The orientation of one of these dirEdges is "+" if the Node is the "to" node of the Edge, and "-" if it is the "from" node.</documentation></annotation><complexContent><extension base="gml:AbstractTopoPrimitiveType"><sequence><element ref="gml:directedEdge" minOccurs="0" maxOccurs="unbounded"/><element ref="gml:pointProperty" minOccurs="0"/><!-- <element name="geometry" type="gml:PointPropertyType" minOccurs="0"/> --></sequence></extension></complexContent></complexType>
Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the
XML Schema Section 4.14 Referencing Schemas from Elsewhere.
. The topological boundary of a face consists of a set of directed edges. Note that all edges associated with a Face, including
dangling and interior edges, appear in the boundary. Dangling and interior edges are each referenced by pairs of directedEdges
with opposing orientations. The optional coboundary of a face is a pair of directed solids which are bounded by this face.
If present, there is precisely one positively directed and one negatively directed solid in the coboundary of every face.
The positively directed solid corresponds to the solid which lies in the direction of the positively directed normal to the
face in any geometric realisation. A face may optionally be realised by a 2-dimensional (surface) geometric primitive.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Source
<complexType name="FaceType"><annotation><documentation>. The topological boundary of a face consists of a set of directed edges. Note that all edges associated with a Face, including dangling and interior edges, appear in the boundary. Dangling and interior edges are each referenced by pairs of directedEdges with opposing orientations. The optional coboundary of a face is a pair of directed solids which are bounded by this face. If present, there is precisely one positively directed and one negatively directed solid in the coboundary of every face. The positively directed solid corresponds to the solid which lies in the direction of the positively directed normal to the face in any geometric realisation. A face may optionally be realised by a 2-dimensional (surface) geometric primitive.</documentation></annotation><complexContent><extension base="gml:AbstractTopoPrimitiveType"><sequence><element ref="gml:directedEdge" maxOccurs="unbounded"/><element ref="gml:directedTopoSolid" minOccurs="0" maxOccurs="2"/><element ref="gml:surfaceProperty" minOccurs="0"/></sequence></extension></complexContent></complexType>
Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the
XML Schema Section 4.14 Referencing Schemas from Elsewhere.
There is precisely one positively directed and one negatively directed node in the boundary of every edge. The negatively
and positively directed nodes correspond to the start and end nodes respectively. The optional coboundary of an edge is a
circular sequence of directed faces which are incident on this edge in document order. Faces which use a particular boundary
edge in its positive orientation appear with positive orientation on the coboundary of the same edge. In the 2D case, the
orientation of the face on the left of the edge is "+"; the orientation of the face on the right on its right is "-". An edge
may optionally be realised by a 1-dimensional (curve) geometric primitive.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Source
<complexType name="EdgeType"><annotation><documentation>There is precisely one positively directed and one negatively directed node in the boundary of every edge. The negatively and positively directed nodes correspond to the start and end nodes respectively. The optional coboundary of an edge is a circular sequence of directed faces which are incident on this edge in document order. Faces which use a particular boundary edge in its positive orientation appear with positive orientation on the coboundary of the same edge. In the 2D case, the orientation of the face on the left of the edge is "+"; the orientation of the face on the right on its right is "-". An edge may optionally be realised by a 1-dimensional (curve) geometric primitive.</documentation></annotation><complexContent><extension base="gml:AbstractTopoPrimitiveType"><sequence><element ref="gml:directedNode" minOccurs="2" maxOccurs="2"/><element ref="gml:directedFace" minOccurs="0" maxOccurs="unbounded"/><element ref="gml:curveProperty" minOccurs="0"/></sequence></extension></complexContent></complexType>
Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the
XML Schema Section 4.14 Referencing Schemas from Elsewhere.
Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the
XML Schema Section 4.14 Referencing Schemas from Elsewhere.
Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the
XML Schema Section 4.14 Referencing Schemas from Elsewhere.
The topological boundary of a TopoSolid consists of a set of directed faces. Note that all faces associated with the TopoSolid,
including dangling faces, appear in the boundary. The coboundary of a TopoSolid is empty and hence requires no representation.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Source
<complexType name="TopoSolidType"><annotation><documentation>The topological boundary of a TopoSolid consists of a set of directed faces. Note that all faces associated with the TopoSolid, including dangling faces, appear in the boundary. The coboundary of a TopoSolid is empty and hence requires no representation.</documentation></annotation><complexContent><extension base="gml:AbstractTopoPrimitiveType"><sequence><element ref="gml:directedFace" maxOccurs="unbounded"/></sequence></extension></complexContent></complexType>
Complex Type gml:TopoPointType
Namespace
http://www.opengis.net/gml
Annotations
The intended use of TopoPoint is to appear within a point feature to express the structural and possibly geometric relationships
of this point to other features via shared node definitions. Note the orientation assigned to the directedNode has no meaning
in this context. It is preserved for symmetry with the types and elements which follow.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Source
<complexType name="TopoPointType"><annotation><documentation>The intended use of TopoPoint is to appear within a point feature to express the structural and possibly geometric relationships of this point to other features via shared node definitions. Note the orientation assigned to the directedNode has no meaning in this context. It is preserved for symmetry with the types and elements which follow.</documentation></annotation><complexContent><extension base="gml:AbstractTopologyType"><sequence><element ref="gml:directedNode"/></sequence></extension></complexContent></complexType>
The end Node of each directedEdge of a TopoCurveType
is the start Node of the next directedEdge of the TopoCurveType in document order. The TopoCurve type and element represent
a homogeneous topological expression, a list of directed edges, which if realised are isomorphic to a geometric curve primitive.
The intended use of TopoCurve is to appear within a line feature instance to express the structural and geometric relationships
of this line to other features via the shared edge definitions.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Source
<complexType name="TopoCurveType"><annotation><documentation>The end Node of each directedEdge of a TopoCurveType
is the start Node of the next directedEdge of the TopoCurveType in document order. The TopoCurve type and element represent a homogeneous topological expression, a list of directed edges, which if realised are isomorphic to a geometric curve primitive. The intended use of TopoCurve is to appear within a line feature instance to express the structural and geometric relationships of this line to other features via the shared edge definitions.</documentation></annotation><complexContent><extension base="gml:AbstractTopologyType"><sequence><element ref="gml:directedEdge" maxOccurs="unbounded"/></sequence></extension></complexContent></complexType>
The TopoSurface type and element represent a homogeneous topological expression, a set of directed faces, which if realised
are isomorphic to a geometric surface primitive. The intended use of TopoSurface is to appear within a surface feature instance
to express the structural and possibly geometric relationships of this surface to other features via the shared face definitions.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Source
<complexType name="TopoSurfaceType"><annotation><documentation>The TopoSurface type and element represent a homogeneous topological expression, a set of directed faces, which if realised are isomorphic to a geometric surface primitive. The intended use of TopoSurface is to appear within a surface feature instance to express the structural and possibly geometric relationships of this surface to other features via the shared face definitions.</documentation></annotation><complexContent><extension base="gml:AbstractTopologyType"><sequence><element ref="gml:directedFace" maxOccurs="unbounded"/></sequence></extension></complexContent></complexType>
The TopoVolume type and element represent a homogeneous topological expression, a set of directed TopoSolids, which if realised
are isomorphic to a geometric solid primitive. The intended use of TopoVolume is to appear within a 3D solid feature instance
to express the structural and geometric relationships of this solid to other features via the shared TopoSolid definitions.
. Note the orientation assigned to the directedSolid has no meaning in three dimensions. It is preserved for symmetry with
the preceding types and elements.
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Source
<complexType name="TopoVolumeType"><annotation><documentation>The TopoVolume type and element represent a homogeneous topological expression, a set of directed TopoSolids, which if realised are isomorphic to a geometric solid primitive. The intended use of TopoVolume is to appear within a 3D solid feature instance to express the structural and geometric relationships of this solid to other features via the shared TopoSolid definitions. . Note the orientation assigned to the directedSolid has no meaning in three dimensions. It is preserved for symmetry with the preceding types and elements.</documentation></annotation><complexContent><extension base="gml:AbstractTopologyType"><sequence><element ref="gml:directedTopoSolid" maxOccurs="unbounded"/></sequence></extension></complexContent></complexType>
Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it
occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.
This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the
XML Schema Section 4.14 Referencing Schemas from Elsewhere.
<complexType name="TopoComplexMemberType"><annotation><documentation>This Property can be used to embed a TopoComplex in a feature collection.</documentation></annotation><sequence><element ref="gml:TopoComplex" minOccurs="0"/></sequence><attributeGroup ref="gml:AssociationAttributeGroup"/></complexType>
Complex Type gml:TopoPrimitiveMemberType
Namespace
http://www.opengis.net/gml
Annotations
This type supports embedding topological primitives in a TopoComplex.
Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the
XML Schema Section 4.14 Referencing Schemas from Elsewhere.
<complexType name="TopoPrimitiveMemberType"><annotation><documentation>This type supports embedding topological primitives in a TopoComplex.</documentation></annotation><sequence><element ref="gml:_TopoPrimitive" minOccurs="0"/></sequence><attributeGroup ref="gml:AssociationAttributeGroup"/></complexType>
Complex Type gml:TopoPrimitiveArrayAssociationType
Namespace
http://www.opengis.net/gml
Annotations
This type supports embedding an array of topological primitives in a TopoComplex
<complexType name="TopoPrimitiveArrayAssociationType"><annotation><documentation>This type supports embedding an array of topological primitives in a TopoComplex</documentation></annotation><!-- <complexContent>
<restriction base="gml:ArrayAssociationType"> --><sequence><choice minOccurs="0" maxOccurs="unbounded"><element ref="gml:_TopoPrimitive"/></choice></sequence><!-- </restriction>
</complexContent> --></complexType>
