specify additional properties in an application schema. A feature must possess an identifying attribute ('id' -
<annotation>
'fid' has been deprecated).</documentation>
<documentation>An abstract feature provides a set of common properties, including id, metaDataProperty, name and description inherited from AbstractGMLType, plus boundedBy. A concrete feature type must derive from this type and specify additional properties in an application schema. A feature must possess an identifying attribute ('id' - 'fid' has been deprecated).</documentation>
</annotation>
</annotation>
<complexContent>
<complexContent>
<extensionbase="gml:AbstractGMLType">
<extensionbase="gml:AbstractGMLType">
<sequence>
<sequence>
<elementref="gml:boundedBy"minOccurs="0"/>
<elementref="gml:boundedBy"minOccurs="0"/>
<elementref="gml:location"minOccurs="0">
<elementref="gml:location"minOccurs="0">
<annotation>
<annotation>
<appinfo>deprecated</appinfo>
<appinfo>deprecated</appinfo>
<documentation>deprecated in GML version 3.1</documentation>
<documentation>deprecated in GML version 3.1</documentation>
<!-- ===== Global element at the head of the "Object" substitution group ======== -->
<!-- =========== Abstract "Object" is "anyType" ============= -->
<elementname="_Object"abstract="true">
<!-- ===== Global element at the head of the "Object" substitution group ======== -->
<annotation>
<elementname="_Object"abstract="true">
<documentation>This abstract element is the head of a substitutionGroup hierararchy which may contain either
<annotation>
simpleContent or complexContent elements. It is used to assert the model position of "class" elements declared in
<documentation>This abstract element is the head of a substitutionGroup hierararchy which may contain either simpleContent or complexContent elements. It is used to assert the model position of "class" elements declared in other GML schemas.</documentation>
<documentation>Global element which acts as the head of a substitution group that may include any element which is a GML feature, object, geometry or complex value</documentation>
<documentation>Global element which acts as the head of a substitution group that may include any element which is a
</annotation>
GML feature, object, geometry or complex value</documentation>
<documentation>Multiple names may be provided. These will often be distinguished by being assigned by different authorities, as indicated by the value of the codeSpace attribute. In an instance document there will usually only be one name per authority.</documentation>
<annotation>
</annotation>
<documentation>Multiple names may be provided. These will often be distinguished by being assigned by
</element>
different authorities, as indicated by the value of the codeSpace attribute. In an instance document there
</sequence>
will usually only be one name per authority.</documentation>
<documentation>Generic GML element to contain a heterogeneous collection of GML _Objects</documentation>
<complexTypename="BagType">
</annotation>
<annotation>
</element>
<documentation>A non-abstract generic collection type that can be used as a document element for a collection of any GML types - Geometries, Topologies, Features ...
FeatureCollections may only contain Features. GeometryCollections may only contain Geometrys. Bags are less constrained they must contain objects that are substitutable for gml:_Object. This may mix several levels, including Features, Definitions, Dictionaries, Geometries etc.
<annotation>
<documentation>A non-abstract generic collection type that can be used as a document element for a collection of any
The content model would ideally be
GML types - Geometries, Topologies, Features ... FeatureCollections may only contain Features. GeometryCollections
member 0..*
may only contain Geometrys. Bags are less constrained they must contain objects that are substitutable for
members 0..1
gml:_Object. This may mix several levels, including Features, Definitions, Dictionaries, Geometries etc. The
member 0..*
content model would ideally be member 0..* members 0..1 member 0..* for maximum flexibility in building a
for maximum flexibility in building a collection from both homogeneous and distinct components:
collection from both homogeneous and distinct components: included "member" elements each contain a single Object
included "member" elements each contain a single Object
an included "members" element contains a set of Objects However, this is non-deterministic, thus prohibited by
an included "members" element contains a set of Objects
XSD.</documentation>
</annotation>
However, this is non-deterministic, thus prohibited by XSD.</documentation>
<documentation>A non-abstract generic collection type that can be used as a document element for a homogeneous
<annotation>
collection of any GML types - Geometries, Topologies, Features ...</documentation>
<documentation>A non-abstract generic collection type that can be used as a document element for a homogeneous collection of any GML types - Geometries, Topologies, Features ...</documentation>
<documentation>Concrete element in the _MetaData substitution group, which permits any well-formed XML content. Intended to act as a container for metadata defined in external schemas, for which it is not possible to add the concrete components to the GML _MetaData substitution group directly. Deprecated with GML version 3.1.0.</documentation>
<documentation>Concrete element in the _MetaData substitution group, which permits any well-formed XML content.
</annotation>
Intended to act as a container for metadata defined in external schemas, for which it is not possible to add the
</element>
concrete components to the GML _MetaData substitution group directly. Deprecated with GML version
<documentation>A pattern or base for derived types used to specify complex types corresponding to an unspecified UML association - either composition or aggregation. Restricts the cardinality of Objects contained in the association to a maximum of one. An instance of this type can contain an element representing an Object, or serve as a pointer to a remote Object.
Descendents of this type can be restricted in an application schema to
<annotation>
* allow only specified classes as valid participants in the aggregation
<documentation>A pattern or base for derived types used to specify complex types corresponding to an unspecified UML
* allow only association by reference (i.e. empty the content model) or by value (i.e. remove the xlinks).
association - either composition or aggregation. Restricts the cardinality of Objects contained in the association
to a maximum of one. An instance of this type can contain an element representing an Object, or serve as a pointer
When used for association by reference, the value of the gml:remoteSchema attribute can be used to locate a schema fragment that constrains the target instance.
to a remote Object. Descendents of this type can be restricted in an application schema to * allow only specified
classes as valid participants in the aggregation * allow only association by reference (i.e. empty the content
In many cases it is desirable to impose the constraint prohibiting the occurence of both reference and value in the same instance, as that would be ambiguous. This is accomplished by adding a directive in the annotation element of the element declaration. This directive can be in the form of normative prose, or can use a Schematron pattern to automatically constrain co-occurrence - see the declaration for _strictAssociation below.
model) or by value (i.e. remove the xlinks). When used for association by reference, the value of the
gml:remoteSchema attribute can be used to locate a schema fragment that constrains the target instance. In many
If co-occurence is not prohibited, then both a link and content may be present. If this occurs in an instance, then the rule for interpretation is that the instance found by traversing the href provides the normative value of the property, and should be used when possible. The value(s) included as content may be used if the remote instance cannot be resolved. This may be considered to be a "cached" version of the value(s).</documentation>
cases it is desirable to impose the constraint prohibiting the occurence of both reference and value in the same
</annotation>
instance, as that would be ambiguous. This is accomplished by adding a directive in the annotation element of the
<sequenceminOccurs="0">
element declaration. This directive can be in the form of normative prose, or can use a Schematron pattern to
<elementref="gml:_Object"/>
automatically constrain co-occurrence - see the declaration for _strictAssociation below. If co-occurence is not
<elementref="gml:_ADEComponent"minOccurs="0"/>
prohibited, then both a link and content may be present. If this occurs in an instance, then the rule for
</sequence>
interpretation is that the instance found by traversing the href provides the normative value of the property, and
<documentation>A pattern or base for derived types used to specify complex types corresponding to a UML aggregation association. An instance of this type serves as a pointer to a remote Object.</documentation>
association. An instance of this type serves as a pointer to a remote Object.</documentation>
<complexTypename="ArrayAssociationType">
</annotation>
<annotation>
<sequence/>
<documentation>A base for derived types used to specify complex types containing an array of objects, by unspecified UML association - either composition or aggregation. An instance of this type contains elements representing Objects.
However, this leads to a non-deterministic content model, since both the base and the extension have minOccurs="0", and is thus prohibited in XML Schema.</documentation>
<!-- ========= multiple objects - by Value or by Reference ================== -->
<documentation>Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML
<documentation>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.</documentation>
document within which it occurs. An external identifier for the object in the form of a URI may be constructed
</annotation>
using standard XML and XPointer methods. This is done by concatenating the URI for the document, a fragment
</attribute>
separator, and the value of the id attribute.</documentation>
<documentation>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.</documentation>
<attributename="remoteSchema"type="anyURI">
</annotation>
<annotation>
</attribute>
<documentation>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.</documentation>
<attributeGroupname="AssociationAttributeGroup">
</annotation>
<annotation>
</attribute>
<documentation>Attribute group used to enable property elements to refer to their value remotely. It contains the simple link components from xlinks.xsd, with all members optional, and the remoteSchema attribute, which is also optional. These attributes can be attached to any element, thus allowing it to act as a pointer. The 'remoteSchema' attribute allows an element that carries link attributes to indicate that the element is declared in a remote schema rather than by the schema that constrains the current document instance.</documentation>
optional. These attributes can be attached to any element, thus allowing it to act as a pointer. The
<elementname="name"type="gml:CodeType">
'remoteSchema' attribute allows an element that carries link attributes to indicate that the element is declared
<annotation>
in a remote schema rather than by the schema that constrains the current document instance.</documentation>
<documentation>Label for the object, normally a descriptive name. An object may have several names, typically assigned by different authorities. The authority for a name is indicated by the value of its (optional) codeSpace attribute. The name may or may not be unique, as determined by the rules of the organization responsible for the codeSpace.</documentation>
attribute. The name may or may not be unique, as determined by the rules of the organization responsible for the
<complexTypename="StringOrRefType">
codeSpace.</documentation>
<annotation>
</annotation>
<documentation>This type is available wherever there is a need for a "text" type property. It is of string type, so the text can be included inline, but the value can also be referenced remotely via xlinks from the AssociationAttributeGroup. If the remote reference is present, then the value obtained by traversing the link should be used, and the string content of the element can be used for an annotation.</documentation>
<documentation>Extends the units.xsd and basicTypes.xsd schemas with types for recording measures using specific types of units, especially the measures and units needed for coordinate reference systems and coordinate operations. The specific unit types encoded are length, angle, scale factor, time, area, volume, speed, and grid length. This schema allows angle values to be recorded as single numbers or in degree-minute-second format.
<documentation>Extends the units.xsd and basicTypes.xsd schemas with types for recording measures using specific types of units, especially the measures and units needed for coordinate reference systems and coordinate operations. The specific unit types encoded are length, angle, scale factor, time, area, volume, speed, and grid length. This schema allows angle values to be recorded as single numbers or in degree-minute-second format.
Copyright (c) 2002-2005 OGC, All Rights Reserved. For conditions, see OGC Software Notice http://www.opengeospatial.org/about/?page=ipr
Parts of this schema are based on Subclause 6.5.7 of ISO/CD 19103 Geographic information - Conceptual schema language, on Subclause A.5.2.2.3 of ISO/CD 19118 Geographic information - Encoding, and on Subclause 4.7 of OpenGIS Recommendation Paper OGC 02-007r4 Units of Measure Use and Definition Recommendations.
Parts of this schema are based on Subclause 6.5.7 of ISO/CD 19103 Geographic information - Conceptual schema language, on Subclause A.5.2.2.3 of ISO/CD 19118 Geographic information - Encoding, and on Subclause 4.7 of OpenGIS Recommendation Paper OGC 02-007r4 Units of Measure Use and Definition Recommendations.</documentation>
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/ .
<documentation>How to encode reference system definitions. Builds on several other parts of GML 3 to encode the data needed to define reference systems.
<documentation>How to encode reference system definitions. Builds on several other parts of GML 3 to encode the data needed to define reference systems.
Copyright (c) 2002-2005 OGC, All Rights Reserved. For conditions, see OGC Software Notice http://www.opengeospatial.org/about/?page=ipr
This schema encodes the Reference System (RS_) package of the extended UML Model for OGC Abstract Specification Topic 2: Spatial Referencing by Coordinates. That UML model is adapted from ISO 19111 - Spatial referencing by coordinates, as described in Annex C of Topic 2. The SC_CRS class is also encoded here, to eliminate the (circular) references from coordinateOperations.xsd to coordinateReferenceSystems.xsd. The RS_SpatialReferenceSystemUsingGeographicIdentifier class is not encoded, since it is not applicable to coordinate positions. The CI_Citation class is not directly encoded, since such information can be included as metaDataProperty elements which are optionally allowed. A modified version of the EX_Extent (DataType) class from ISO 19115 is currently encoded here, using GML 3 schema types. (A more extensive version of the EX_Extent package might be XML encoded in the future, probably in a separate extent.xsd schema.)
This schema encodes the Reference System (RS_) package of the extended UML Model for OGC Abstract Specification Topic 2: Spatial Referencing by Coordinates. That UML model is adapted from ISO 19111 - Spatial referencing by coordinates, as described in Annex C of Topic 2. The SC_CRS class is also encoded here, to eliminate the (circular) references from coordinateOperations.xsd to coordinateReferenceSystems.xsd. The RS_SpatialReferenceSystemUsingGeographicIdentifier class is not encoded, since it is not applicable to coordinate positions. The CI_Citation class is not directly encoded, since such information can be included as metaDataProperty elements which are optionally allowed. A modified version of the EX_Extent (DataType) class from ISO 19115 is currently encoded here, using GML 3 schema types. (A more extensive version of the EX_Extent package might be XML encoded in the future, probably in a separate extent.xsd schema.)
Caution: The CRS package in GML 3.1 and GML 3.1.1 is preliminary, and is expected to undergo some modifications that are not backward compatible during the development of GML 3.2 (ISO 19136). The GML 3.2 package will implement the model described in the revised version of ISO 19111.</documentation>
Caution: The CRS package in GML 3.1 and GML 3.1.1 is preliminary, and is expected to undergo some modifications that are not backward compatible during the development of GML 3.2 (ISO 19136). The GML 3.2 package will implement the model described in the revised version of ISO 19111.
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/ .
<documentationxml:lang="en">The Temporal Reference Systems schema for GML 3.1 provides constructs for handling various styles of temporal reference system.
<documentationxml:lang="en">The Temporal Reference Systems schema for GML 3.1 provides constructs for handling various styles of temporal reference system.
This schema reflects a partial implementation of the model described in ISO 19108:2002.
This schema reflects a partial implementation of the model described in ISO 19108:2002.
Copyright (c) 2002-2005 OGC, All Rights Reserved.
For conditions, see OGC Software Notice http://www.opengeospatial.org/about/?page=ipr</documentation>
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/ .
<documentation>Builds on gmlBase.xsd to encode units of measure (or uom), including definitions of units of measure and dictionaries of such definitions. GML 3.0 candidate schema, primary editor: Arliss Whiteside. Last updated 2005-06-22.
<documentation>Builds on gmlBase.xsd to encode units of measure (or uom), including definitions of units of measure and dictionaries of such definitions. GML 3.0 candidate schema, primary editor: Arliss Whiteside.
Copyright (c) 2002-2005 OGC, All Rights Reserved.
Parts of this schema are based on Subclause 6.5.7 of ISO/CD 19103 Geographic information - Conceptual schema language, on Subclause A.5.2.2.3 of ISO/CD 19118 Geographic information - Encoding, and on most of OpenGIS Recommendation Paper OGC 02-007r4 Units of Measure Use and Definition Recommendations.
For conditions, see OGC Software Notice http://www.opengeospatial.org/about/?page=ipr
Parts of this schema are based on Subclause 6.5.7 of ISO/CD 19103 Geographic information - Conceptual schema language, on Subclause A.5.2.2.3 of ISO/CD 19118 Geographic information - Encoding, and on most of OpenGIS Recommendation Paper OGC 02-007r4 Units of Measure Use and Definition Recommendations.</documentation>
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/ .
