A profile of OpenGeospatialConsortium (OpenGIS, OGC) Geography Markup Language (GML) version 3.1.1 schemas for niem version 1.0. Deprecated GML3.1.1 types like gid are eliminated because they will not be included in the ISO TC/211 19136 version of the GML standard.
This GML profile includes AssociationAttributeGroup even though niem version 0.2 uses IDREF and IDREFS instead of xlink:href.
GML Simple Features does not allow XLinks, and OpenLS does not use them. But they are used for the GML definitions for
Coverages, Moving Objects, and throughout the schemas for Observations and Measurements. The attributes in the xlink:simpleLink
attributeGroup referenced by gml:AssociationAttributeGroup are optional. So their use in instance documents may be avoided
where not allowed or customary.
2006-09-28 Changed namespaces and schema location
ns old http://niem.gov/niem/external/gml/3.1.1/dhs-gmo/1.0.0
ns new http://niem.gov/niem/external/ogc-gml/3.1.1/dhs-gmo/1.0.0
ns old http://niem.gov/niem/external/xlink/1.0.0/dhs-gmo/1.0.0
ns new http://niem.gov/niem/external/w3c-xlink/1.0/dhs-gmo/1.0.0
from ../../../../xlink/1.0.0/dhs-gmo/1.0.0/xlinks.xsd
to ../../../../w3c-xlink/1.0/dhs-gmo/1.0.0/xlinks.xsd
2006-09-21 Changes
1. Change namespaces following NIEM conventions
a) targetNamespace http://niem.gov/niem/external/gml/3.1.1/dhs-gmo/1.0.0
b) xlink namespace http://niem.gov/niem/external/xlink/1.0.0/dhs-gmo/1.0.0
2006-09-19 Changes
add definitions used by ISO 19139 Metadata
put metadataProperty back in StandardObjectProperties and DefinitionType to support referenceSystems definitions that use it
2006-09-04 Changes
1. Change namespaces following conventions proposed in OGC 05-065r3 to include version and profile information,
except that complete version is used instead of BNF "principle version".
a) targetNamespace was http://www.opengis.net/gml; changed to http://www.opengis.net/gml/3.1.1/DHS-GMO/1.0.0
b) xlink namespace was http://www.w3.org/1999/xlink; changed to http://www.w3.org/1999/xlink/1.0.0/OGC-DHS-GMO/1.0.0
2. Change xlink import to point to xlink schema in its own versioned directory instead of deprecated schema that references it.
3. Include complete OGC copyright notice from http://www.opengeospatial.org/ogc/software
2006-04-14 Changes
move to proposed external directory structure
change path to xlinks.xsd
2006-01-02 Changes
include appinfo source="" to document source of definitions
include base, units, measures, values, temporal, coverage
2006-01-03
include observations
2006-01-05
add documentation
2006-01-09
add back in empty AssociationAttributeGroup
Copyright Notices:
Copyright (c) 2001-2004 OGC, All Rights Reserved.
This OGC work (including software, documents, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions:
Permission to use, copy, and modify this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including modifications, that you make:
1. The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.
2. Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, a short notice of the following form (hypertext is preferred, text is permitted) should be used within the body of any redistributed or derivative code: "Copyright © [$date-of-document] Open Geospatial Consortium, Inc. All Rights Reserved. http://www.opengeospatial.org/ogc/legal (Hypertext is preferred, but a textual representation is permitted.)
3. Notice of any changes or modifications to the OGC files, including the date changes were made. (We recommend you provide URIs to the location from which the code is derived.)
THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific, written prior permission. Title to copyright in this software and any associated documentation will at all times remain with copyright holders.
This content model group makes it easier to construct types that
derive from AbstractGMLType and its descendents "by restriction".
A reference to the group saves having to enumerate the standard object properties.
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.
basicTypes.xsd
Utility type for null elements. The value may be selected from one of the enumerated tokens, or may be a URI in which case this should identify a resource which describes the reason for the null.
basicTypes.xsd
Some common reasons for a null value:
innapplicable - the object does not have a value
missing - The correct value is not readily available to the sender of this data.
Furthermore, a correct value may not exist.
template - the value will be available later
unknown - The correct value is not known to, and not computable by, the sender of this data.
However, a correct value probably exists.
withheld - the value is not divulged
other:reason - as indicated by "reason" string
Specific communities may agree to assign more strict semantics when these terms are used in a particular context.
Union of the XML Schema boolean type and the GML Nulltype. An element which uses this type may have content which is either a boolean {0,1,true,false} or a value from Nulltype
XML List based on the union type defined above. An element declared with this type contains a space-separated list of boolean values {0,1,true,false} with null values interspersed as needed

XML List based on XML Schema boolean type. An element of this type contains a space-separated list of boolean values {0,1,true,false}

Union of the XML Schema string type and the GML Nulltype. An element which uses this type may have content which is either a string or a value from Nulltype. Note that a "string" may contain whitespace.
Union of the XML Schema Name type and the GML Nulltype. An element which uses this type may have content which is either a Name or a value from Nulltype. Note that a "Name" may not contain whitespace.
XML List based on the union type defined above. An element declared with this type contains a space-separated list of Name values with null values interspersed as needed

XML List based on XML Schema Name type. An element of this type contains a space-separated list of Name values

basicTypes.xsd
Union of the XML Schema double type and the GML Nulltype. An element which uses this type may have content which is either a double or a value from Nulltype
basicTypes.xsd
XML List based on the union type defined above. An element declared with this type contains a space-separated list of double values with null values interspersed as needed

basicTypes.xsd
XML List based on XML Schema double type. An element of this type contains a space-separated list of double values

basicTypes.xsd
Union of the XML Schema integer type and the GML Nulltype. An element which uses this type may have content which is either an integer or a value from Nulltype
basicTypes.xsd
XML List based on the union type defined above. An element declared with this type contains a space-separated list of integer values with null values interspersed as needed

basicTypes.xsd
XML List based on XML Schema integer type. An element of this type contains a space-separated list of integer values

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.
basicTypes.xsd
Name or code with an (optional) authority. Text token.
If the codeSpace attribute is present, then its value should identify a dictionary, thesaurus
or authority for the term, such as the organisation who assigned the value,
or the dictionary from which it is taken.
A text string with an optional codeSpace attribute.
List of values on a uniform nominal scale. List of text tokens.
In a list context a token should not include any spaces, so xsd:Name is used instead of xsd:string.
If a codeSpace attribute is present, then its value is a reference to
a Reference System for the value, a dictionary or code list.
List of values on a uniform nominal scale. List of text tokens.
In a list context a token should not include any spaces, so xsd:Name is used instead of xsd:string.
A member of the list may be a typed null.
If a codeSpace attribute is present, then its value is a reference to
a Reference System for the value, a dictionary or code list.
Number with a scale.
The value of uom (Units Of Measure) attribute is a reference to a Reference System for the amount, either a ratio or position scale.
List of numbers with a uniform scale.
The value of uom (Units Of Measure) attribute is a reference to
a Reference System for the amount, either a ratio or position scale.
List of numbers with a uniform scale.
A member of the list may be a typed null.
The value of uom (Units Of Measure) attribute is a reference to
a Reference System for the amount, either a ratio or position scale.
measures.xsd
Value of a length (or distance) quantity, with its units. Uses the MeasureType with the restriction that the unit of measure referenced by uom must be suitable for a length, such as metres or feet.
measures.xsd
Value of an angle quantity recorded as a single number, with its units. Uses the MeasureType with the restriction that the unit of measure referenced by uom must be suitable for an angle, such as degrees or radians.
Reference to a unit of measure definition that applies to all the numerical values described by the element containing this element. Notice that a complexType which needs to include the uom attribute can do so by extending this complexType. Alternately, this complexType can be used as a pattern for a new complexType.
Reference to a unit of measure definition, usually within the same XML document but possibly outside the XML document which contains this reference. For a reference within the same XML document, the "#" symbol should be used, followed by a text abbreviation of the unit name. However, the "#" symbol may be optional, and still may be interpreted as a reference.
Contains a simple text description of the object, or refers to an external description.
basicTypes.xsd
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.
As a profile of the GML StringOrRefType, this definition has no capability for remote references, because niem does not currently use xlinks, no uses of xlinks are
included in the first version of this schema for niem.
gmlBase.xsd
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.
gmlBase.xsd
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.
gmlBase.xsd
All complexContent GML elements are directly or indirectly derived from this abstract supertype
to establish a hierarchy of GML types that may be distinguished from other XML types by their ancestry.
Elements in this hierarchy may have an ID and are thus referenceable.
gmlBase.xsd
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
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.
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.
gmlBase.xsd
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 reference one remotely via an xlink:href, but may not do both.
Descendents of this type can be restricted in an application schema to allow only specified classes as valid participants in the aggregation
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.
This content model group makes it easier to construct types that
derive from DefinitionType and its descendents "by restriction".
A reference to the group saves having to enumerate the standard definition properties.
See definition of StandardObjectProperties for more documentation
A definition, which can be included in or referenced by a dictionary. In this extended type, the inherited "description" optional element can hold the definition whenever only text is needed. The inherited "name" elements can provide one or more brief terms for which this is the definition.
The gml:id attribute is required - it must be possible to reference this definition using this handle.
A non-abstract bag that is specialized for use as a dictionary which contains a set of definitions. These definitions are referenced from other places, in the same and different XML documents. In this restricted type, the inherited optional "description" element can be used for a description of this dictionary. The inherited optional "name" element can be used for the name(s) of this dictionary. The inherited "metaDataProperty" elements can be used to reference or contain more information about this dictionary. The inherited required gml:id attribute allows the dictionary to be referenced using this handle.
An entry in this dictionary. The content of an entry can itself be a lower level dictionary or definition collection. This element follows the standard GML property model, so the value may be provided directly or by reference. Note that if the value is provided by reference, this definition does not carry a handle (gml:id) in this context, so does not allow external references to this specific entry in this context. When used in this way the referenced definition will usually be in a dictionary in the same XML document.
An entry in a dictionary of definitions. An instance of this type contains or refers to a definition object.
The number of definitions contained in this dictionaryEntry is restricted to one, but a DefinitionCollection or Dictionary that contains multiple definitions can be substituted if needed. Specialized descendents of this dictionaryEntry might be restricted in an application schema to allow only including specified types of definitions as valid entries in a dictionary.
This element in a dictionary entry contains the actual definition.
geometryBasic0d1d.xsd
This is the abstract root type of the geometric primitives. A geometric primitive is a geometric object that is not
decomposed further into other primitives in the system. All primitives are oriented in the direction implied by the sequence of their
coordinate tuples.
geometryBasic0d1d.xsd
The "_GeometricPrimitive" element is the abstract head of the substituition group for all (pre- and user-defined)
geometric primitives.
geometryBasic0d1d.xsd
All geometry elements are derived directly or indirectly from this abstract supertype. A geometry element may
have an identifying attribute ("gml:id"), a name (attribute "name") and a description (attribute "description"). It may be associated
with a spatial reference system (attribute "srsName"). The following rules shall be adhered: - Every geometry type shall derive
from this abstract type. - Every geometry element (i.e. an element of a geometry type) shall be directly or indirectly in the
substitution group of _Geometry.
geometryBasic0d1d.xsd
Optional reference to the CRS used by this geometry, with optional additional information to simplify use when
a more complete definition of the CRS is not needed.
In general this reference points to a CRS instance of gml:CoordinateReferenceSystemType
(see coordinateReferenceSystems.xsd). For well known references it is not required that the CRS description exists at the
location the URI points to. If no srsName attribute is given, the CRS must be specified as part of the larger context this
geometry element is part of, e.g. a geometric element like point, curve, etc. It is expected that this attribute will be specified
at the direct position level only in rare cases.
The "srsDimension" is the length of coordinate sequence (the number of entries in the list). This dimension is
specified by the coordinate reference system. When the srsName attribute is omitted, this attribute shall be omitted.
geometryBasic0d1d.xsd
The "_Geometry" element is the abstract head of the substituition group for all geometry elements of GML 3. This
includes pre-defined and user-defined geometry elements. Any geometry element must be a direct or indirect extension/restriction
of AbstractGeometryType and must be directly or indirectly in the substitution group of "_Geometry".
geometryBasic0d1d.xsd
A geometric property is any geometry element encapsulated in an element of this type.
2006-01-07 PwD derive from AssociationType to fix om:geometryResult membership in gml:resultOf substituion group
geometryBasic0d1d.xsd
DirectPosition instances hold the coordinates for a position within some coordinate reference system (CRS). Since
DirectPositions, as data types, will often be included in larger objects (such as geometry elements) that have references to CRS, the
"srsName" attribute will in general be missing, if this particular DirectPosition is included in a larger element with such a reference to a
CRS. In this case, the CRS is implicitly assumed to take on the value of the containing object's CRS.
geometryBasic0d1d.xsd
DirectPositionList instances hold the coordinates for a sequence of direct positions within the same coordinate
reference system (CRS).
geometryBasic0d1d.xsd
geometryBasic0d1d.xsd
Vector instances hold the compoents for a (usually spatial) vector within some coordinate reference system (CRS).
Since Vectors will often be included in larger objects that have references to CRS, the "srsName" attribute may be missing.
In this case, the CRS is implicitly assumed to take on the value of the containing object's CRS.
Note that this content model is the same as DirectPositionType, but is defined separately to reflect the distinct semantics, and to avoid validation problems. SJDC 2004-12-02
geometryBasic0d1d.xsd
A Point is defined by a single coordinate tuple.
geometryBasic0d1d.xsd
A property that has a point as its value domain can be an appropriate geometry element encapsulated in an
element of this type
geometryBasic0d1d.xsd
The "_Curve" element is the abstract head of the substituition group for all (continuous) curve elements.
geometryBasic0d1d.xsd
An abstraction of a curve to support the different levels of complexity. The curve can always be viewed as a geometric
primitive, i.e. is continuous.
geometryBasic0d1d.xsd
A property that has a curve as its value domain as an appropriate geometry element encapsulated in an
element of this type.
geometryBasic0d1d.xsd
A LineString is a special curve that consists of a single segment with linear interpolation. It is defined by two or more coordinate
tuples, with linear interpolation between them. It is backwards compatible with the LineString of GML 2, GM_LineString of ISO 19107 is
implemented by LineStringSegment.
GML supports two different ways to specify the control points of a line string. 1. A sequence of "pos"
(DirectPositionType) or "pointProperty" (PointPropertyType) elements. "pos" elements are control points that are only part
of this curve, "pointProperty" elements contain a point that may be referenced from other geometry elements or reference
another point defined outside of this curve (reuse of existing points). 2. The "posList" element allows for a compact way to
specifiy the coordinates of the control points, if all control points are in the same coordinate reference systems and belong
to this curve only. The number of direct positions in the list must be at least two.
geometryBasic2d.xsd
An abstraction of a ring to support surface boundaries of different complexity.
geometryBasic2d.xsd
The "_Ring" element is the abstract head of the substituition group for all closed boundaries of a surface patch.
geometryBasic2d.xsd
A boundary of a surface consists of a number of rings. In the normal 2D case, one of these rings is distinguished as being the exterior boundary. In a general manifold this is not always possible, in which case all boundaries shall be listed as interior boundaries, and the exterior will be empty.
geometryBasic2d.xsd
A boundary of a surface consists of a number of rings. The "interior" rings seperate the surface / surface patch from the area enclosed by the rings.
geometryBasic2d.xsd
Encapsulates a ring to represent the surface boundary property of a surface.
geometryBasic2d.xsd
A LinearRing is defined by four or more coordinate tuples, with linear interpolation between them; the first and last coordinates must be coincident.
GML supports two different ways to specify the control points of a linear ring.
1. A sequence of "pos" (DirectPositionType) or "pointProperty" (PointPropertyType) elements. "pos" elements are control points that are only part of this ring, "pointProperty" elements contain a point that may be referenced from other geometry elements or reference another point defined outside of this ring (reuse of existing points).
2. The "posList" element allows for a compact way to specifiy the coordinates of the control points, if all control points are in the same coordinate reference systems and belong to this ring only. The number of direct positions in the list must be at least four.
geometryBasic2d.xsd
An abstraction of a surface to support the different levels of complexity. A surface is always a continuous region of a plane.
geometryBasic2d.xsd
The "_Surface" element is the abstract head of the substituition group for all (continuous) surface elements.
geometryBasic2d.xsd
A property that has a surface as its value domain as an appropriate geometry element encapsulated in an element of this type.
geometryBasic2d.xsd
A Polygon is a special surface that is defined by a single surface patch. The boundary of this patch is coplanar and the polygon uses planar interpolation in its interior. It is backwards compatible with the Polygon of GML 2, GM_Polygon of ISO 19107 is implemented by PolygonPatch.
geometryAggregates.xsd
This is the abstract root type of the geometric aggregates.
geometryAggregates.xsd
The "_GeometricAggregate" element is the abstract head of the substituition group for all geometric aggremates.
geometryAggregates.xsd
A geometry collection must include one or more geometries, referenced through geometryMember elements.
The members of the geometric aggregate can be specified using the "standard" property.
geometryAggregates.xsd
A property that has a geometric aggregate as its value domain an appropriate geometry element encapsulated in an element of this type.
geometryAggregates.xsd
A MultiPoint is defined by one or more Points, referenced through pointMember elements.
The members of the geometric aggregate can be specified using the "standard" property.
geometryAggregates.xsd
A property that has a collection of points as its value domain an appropriate geometry element encapsulated in an element of this type.
geometryAggregates.xsd
A MultiCurve is defined by one or more Curves, referenced through curveMember elements.
The members of the geometric aggregate can be specified using the "standard" property.
geometryAggregates.xsd
A property that has a collection of curves as its value domain as an appropriate geometry element encapsulated in an element of this type.
geometryAggregates.xsd
A MultiSurface is defined by one or more Surfaces, referenced through surfaceMember elements.
The members of the geometric aggregate can be specified either using the "standard" property or the array property style. It is also valid to use both the "standard" and the array property style in the same collection.
NOTE: Array properties cannot reference remote geometry elements.
geometryAggregates.xsd
This property element contains the "multi surface" element. multiSurfaceProperty is the predefined property which can be used by GML Application Schemas whenever a GML Feature has a property with a value that is substitutable for MultiSurface.
geometryAggregates.xsd
A property that has a collection of surfaces as its value domain as an appropriate geometry element encapsulated in an element of this type.
geometryPrimitives.xsd
SurfaceInterpolationType is a list of codes that may be used to identify the interpolation mechanisms specified by an
application schema.
geometryBasic0d1d.xsd
Envelope defines an extent using a pair of positions defining opposite corners in arbitrary dimensions. The first direct
position is the "lower corner" (a coordinate position consisting of all the minimal ordinates for each dimension for all points within the envelope),
the second one the "upper corner" (a coordinate position consisting of all the maximal ordinates for each dimension for all points within the
envelope).
geometryPrimitives.xsd
A CircleByCenterPoint is an ArcByCenterPoint with identical start and end angle to form a full circle. Again, this represenation can be used only in 2D.
geometryPrimitives.xsd
This variant of the arc requires that the points on the arc have to be computed instead of storing the coordinates directly. The control point is the center point of the arc plus the radius and the bearing at start and end. This represenation can be used only in 2D.
GML supports two different ways to specify the control points of a curve segment.
1. A "pos" (DirectPositionType) or "pointProperty" (PointPropertyType) element. The "pos" element contains a center point that is only part of this curve segment, a "pointProperty" element contains a point that may be referenced from other geometry elements or reference another point defined outside of this curve segment (reuse of existing points).
2. The "posList" element can be used to specifiy the coordinates of the center point, too. The number of direct positions in the list must be one.
The radius of the arc.
The bearing of the arc at the start.
The bearing of the arc at the end.
The attribute "interpolation" specifies the curve interpolation mechanism used for this segment. This mechanism
uses the control points and control parameters to determine the position of this curve segment. For an ArcByCenterPoint the interpolation is fixed as "circularArcCenterPointWithRadius".
Since this type describes always a single arc, the attribute is fixed to "1".
geometryPrimitives.xsd
Curve segment defines a homogeneous segment of a curve.
geometryPrimitives.xsd
CurveInterpolationType is a list of codes that may be used to identify the interpolation mechanisms specified by an
application schema. "linear" and "geodesic" were the only enumerations in the origial geometry.xsd for XLS. But this was insufficient to pass Xerces schema validation because ArcByCenterPointType uses circularArcCenterPointWithRadius as a fixed interpolation type. So it has been added here.
geometryPrimitives.xsd
The "_CurveSegment" element is the abstract head of the substituition group for all curve segment elements, i.e. continuous segments of the same interpolation mechanism.
feature.xsd
Bounding shape.
feature.xsd
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).
feature.xsd
Container for a feature - follow gml:AssociationType pattern.
feature.xsd
A feature collection contains zero or more features.
feature.xsd
Concrete generic feature collection.
temporal.xsd
This abstract element acts as the head of the substitution group for temporal primitives and complexes.
temporal.xsd
The abstract supertype for temporal objects.
This abstract element acts as the head of the substitution group for temporal complexes.
Temporal complex is an aggregation of temporal primitives as its components,
represents a temporal geometric complex and a temporal topology complex.
N.B. Temporal geometric complex is not defined in this schema.
The abstract supertype for temporal complexes.
temporal.xsd
This abstract element acts as the head of the substitution group for temporal primitives.
temporal.xsd
The abstract supertype for temporal primitives.
2006-01-07 PwD derive from AssociationType to allow
om:temporalResult as member of gml:resultOf substitutionGroup
temporal.xsd
This abstract element acts as the head of the substitution group for temporal geometric primitives.
temporal.xsd
The abstract supertype for temporal geometric primitives.
A temporal geometry must be associated with a temporal reference system via URI.
The Gregorian calendar with UTC is the default reference system, following ISO
8601. Other reference systems in common use include the GPS calendar and the
Julian calendar.
temporal.xsd
Omit back-pointers begunBy, endedBy.
temporal.xsd
temporal.xsd
This model group is provided as an alternative to the abstract susbstitutionGroup head _timeLength.
ISO 19136 comment 411
temporal.xsd
This element is an instance of the primitive xsd:duration simple type to
enable use of the ISO 8601 syntax for temporal length (e.g. P5DT4H30M).
It is a valid subtype of TimeDurationType according to section 3.14.6,
rule 2.2.4 in XML Schema, Part 1.
temporal.xsd
This element is a valid subtype of TimeDurationType
according to section 3.14.6, rule 2.2.4 in XML Schema, Part 1.
temporal.xsd
This type extends the built-in xsd:decimal simple type to allow floating-point
values for temporal length. According to the ISO 11404 model you have to use
positiveInteger together with appropriate values for radix and factor. The
resolution of the time interval is to one radix ^(-factor) of the specified
time unit (e.g. unit="second", radix="10", factor="3" specifies a resolution
of milliseconds). It is a subtype of TimeDurationType.
temporal.xsd
Standard units for measuring time intervals (see ISO 31-1).
Direct representation of a temporal position
temporal.xsd
Direct representation of a temporal position.
Indeterminate time values are also allowed, as described in ISO 19108. The indeterminatePosition
attribute can be used alone or it can qualify a specific value for temporal position (e.g. before
2002-12, after 1019624400).
For time values that identify position within a calendar, the calendarEraName attribute provides
the name of the calendar era to which the date is referenced (e.g. the Meiji era of the Japanese calendar).
temporal.xsd
The ISO 19108:2002 hierarchy of subtypes for temporal position are collapsed
by defining a union of XML Schema simple types for indicating temporal position relative
to a specific reference system.
Dates and dateTime may be indicated with varying degrees of precision.
dateTime by itself does not allow right-truncation, except for fractions of seconds.
When used with non-Gregorian calendars based on years, months, days,
the same lexical representation should still be used, with leading zeros added if the
year value would otherwise have fewer than four digits.
An ordinal position may be referenced via URI identifying the definition of an ordinal era.
A time coordinate value is indicated as a decimal (e.g. UNIX time, GPS calendar).
temporal.xsd
Calendar dates may be indicated with varying degrees of precision,
using year, year-month, date.
When used with non-Gregorian calendars based on years, months, days,
the same lexical representation should still be used, with leading zeros added if the
year value would otherwise have fewer than four digits.
time is used for a position that recurs daily (see clause 5.4.4.2 of ISO 19108:2002).
temporal.xsd
This enumerated data type specifies values for indeterminate positions.
valueObjects.xsd
Utility choice group which unifies generic Values defined in this schema document with
Geometry and Temporal objects and the Measures described above,
so that any of these may be used within aggregate Values.
valueObjects.xsd
A value from two-valued logic, using the XML Schema boolean type. An instance may take the values {true, false, 1, 0}.
valueObjects.xsd
XML List based on XML Schema boolean type. An element of this type contains a space-separated list of boolean values {0,1,true,false}
valueObjects.xsd
A term representing a classification. It has an optional XML attribute codeSpace, whose value is a URI which identifies a dictionary, codelist or authority for the term.
valueObjects.xsd
A space-separated list of terms or nulls. A single XML attribute codeSpace may be provided, which authorises all the terms in the list.
valueObjects.xsd
A numeric value with a scale. The content of the element is an amount using the XML Schema type double which permits decimal or scientific notation. An XML attribute uom (unit of measure) is required, whose value is a URI which identifies the definition of the scale or units by which the numeric value must be multiplied.
valueObjects.xsd
A space separated list of amounts or nulls. The amounts use the XML Schema type double. A single XML attribute uom (unit of measure) is required, whose value is a URI which identifies the definition of the scale or units by which all the amounts in the list must be multiplied.
valueObjects.xsd
An integer representing a frequency of occurrence.
valueObjects.xsd
A space-separated list of integers or nulls.
valueObjects.xsd
Aggregate value built from other Values using the Composite pattern. It contains zero or an arbitrary number of valueComponent elements, and zero or one valueComponents elements. It may be used for strongly coupled aggregates (vectors, tensors) or for arbitrary collections of values.
Aggregate value built using the Composite pattern.
valueObjects.xsd
A Value Array is used for homogeneous arrays of primitive and aggregate values. The member values may be scalars, composites, arrays or lists. ValueArray has the same content model as CompositeValue, but the member values must be homogeneous. The element declaration contains a Schematron constraint which expresses this restriction precisely. Since the members are homogeneous, the referenceSystem (uom, codeSpace) may be specified on the ValueArray itself and implicitly inherited by all the members if desired. Note that a_ScalarValueList is preferred for arrays of Scalar Values since this is a more efficient encoding.
valueObjects.xsd
A Value Array is used for homogeneous arrays of primitive and aggregate values. _ScalarValueList is preferred for arrays of Scalar Values since this is more efficient. Since "choice" is not available for attribute groups, an external constraint (e.g. Schematron) would be required to enforce the selection of only one of these through schema validation
valueObjects.xsd
Element which refers to, or contains, a set of homogeneously typed Values.
valueObjects.xsd
GML property which refers to, or contains, a set of homogeneously typed Values.
PwD 2006-01-07 derive from gml:AssociationType
valueObjects.xsd
Property whose content is a scalar value.
valueObjects.xsd
Property whose content is a Boolean value.
valueObjects.xsd
Property whose content is a Category.
valueObjects.xsd
Property whose content is a Quantity.
valueObjects.xsd
Property whose content is a Count.
valueObjects.xsd
Utility element to store a 2-point range of numeric values. If one member is a null, then this is a single ended interval.
valueObjects.xsd
Restriction of list type to store a 2-point range of numeric values. If one member is a null, then this is a single ended interval.
valueObjects.xsd
Utility element to store a 2-point range of ordinal values. If one member is a null, then this is a single ended interval.
valueObjects.xsd
Restriction of list type to store a 2-point range of ordinal values. If one member is a null, then this is a single ended interval.
valueObjects.xsd
Utility element to store a 2-point range of frequency values. If one member is a null, then this is a single ended interval.
valueObjects.xsd
Restriction of list type to store a 2-point range of frequency values. If one member is a null, then this is a single ended interval.
valueObjects.xsd
Element which refers to, or contains, a Value
valueObjects.xsd
Element which refers to, or contains, a Value. This version is used in CompositeValues.
valueObjects.xsd
GML property which refers to, or contains, a Value
grids.xsd
An unrectified grid, which is a network composed of two or more sets of equally spaced parallel lines in which the members of each set intersect the members of the other sets at right angles.
grids.xsd
Provides grid coordinate values for the diametrically opposed corners of an envelope that bounds a section of grid. The value of a single coordinate is the number of offsets from the origin of the grid in the direction of a specific axis.
Should be substitutionGroup="gml:Grid" but changed in order to accomplish Xerces-J schema validation
grids.xsd
A rectified grid has an origin and vectors that define its post locations.
coverage.xsd
Abstract element which acts as the head of a substitution group for coverages. Note that a coverage is a GML feature.
coverage.xsd
A continuous coverage as defined in ISO 19123 is a coverage that can return different values for the same feature attribute at different direct positions within a single spatiotemporal object in its spatiotemporal domain
coverage.xsd
A discrete coverage consists of a domain set, range set and optionally a coverage function. The domain set consists of either geometry or temporal objects, finite in number. The range set is comprised of a finite number of attribute values each of which is associated to every direct position within any single spatiotemporal object in the domain. In other words, the range values are constant on each spatiotemporal object in the domain. This coverage function maps each element from the coverage domain to an element in its range. This definition conforms to ISO 19123.
coverage.xsd
The spatiotemporal domain of a coverage.
Typically
* a geometry collection,
* an implicit geometry (e.g. a grid),
* an explicit or implicit collection of time instances or periods has been removed as an option here
N.B. Temporal geometric complexes and temporal grids are not yet implemented in GML.
coverage.xsd
each member _Value holds a tuple or "row" from the equivalent table
each list holds the complete set of one scalar component from the values - i.e. a "column" from the equivalent table
Its tuple list holds the values as space-separated tuples each of which contains comma-separated components, and the tuple structure is specified using the rangeParameters property.
coverage.xsd
The function or rule which defines the map from members of the domainSet to the range.
More functions will be added to this list
coverage.xsd
coverage.xsd
Metadata about the rangeSet. Definition of record structure.
This is required if the rangeSet is encoded in a DataBlock.
We use a gml:_Value with empty values as a map of the composite value structure.
coverage.xsd
Description of a rule for associating members from the domainSet with members of the rangeSet.
coverage.xsd
Defines how values in the domain are mapped to the range set. The start point and the sequencing rule are specified here.
If absent, the implied value is "Linear".
Index position of the first grid post, which must lie somwhere in the GridEnvelope. If absent, the startPoint is equal to the value of gridEnvelope::low from the grid definition.
coverage.xsd
Exends GridFunctionType with a lookUpTable. This contains a list of indexes of members within the rangeSet corresponding with the members of the domainSet. The domainSet is traversed in list order if it is enumerated explicitly, or in the order specified by a SequenceRule if the domain is an implicit set. The length of the lookUpTable corresponds with the length of the subset of the domainSet for which the coverage is defined.
coverage.xsd
List of codes (adopted from ISO 19123 Annex C) that identifies the rule for traversing a grid to correspond with the sequence of members of the rangeSet.
coverage.xsd
The enumeration value here indicates the incrementation order to be used on the first 2 axes, i.e. "+x-y" means that the points on the first axis are to be traversed from lowest to highest and the points on the second axis are to be traversed from highest to lowest. The points on all other axes (if any) beyond the first 2 are assumed to increment from lowest to highest.
coverage.xsd
A discrete coverage type whose domain is defined by a collection of point
coverage.xsd
coverage.xsd
A discrete coverage type whose domain is defined by a collection of curves.
coverage.xsd
A discrete coverage type whose domain is defined by a collection of surface patches (includes polygons, triangles, rectangles, etc).
coverage.xsd
coverage.xsd
coverage.xsd
coverage.xsd
direction.xsd
direction.xsd
Direction expressed as a vector, either using components, or using angles.
observation.xsd
This element contains or points to a description of a sensor, instrument or procedure used for the observation
observation.xsd
This element contains or points to the specimen, region or station which is the object of the observation
observation.xsd
Synonym for target - common word used for photographs
observation.xsd
Container for an object representing the target or subject of an observation.
A timeslice encapsulates the time-varying properties of a dynamic feature--it
must be extended to represent a timestamped projection of a feature. The dataSource
property describes how the temporal data was acquired.
The history relationship associates a feature with a sequence of TimeSlice instances.
A coordinate reference system consists of an ordered sequence of coordinate system axes that are related to the earth through a datum. A coordinate reference system is defined by one datum and by one coordinate system. Most coordinate reference system do not move relative to the earth, except for engineering coordinate reference systems defined on moving platforms such as cars, ships, aircraft, and spacecraft. For further information, see OGC Abstract Specification Topic 2.
Coordinate reference systems are commonly divided into sub-types. The common classification criterion for sub-typing of coordinate reference systems is the way in which they deal with earth curvature. This has a direct effect on the portion of the earth's surface that can be covered by that type of CRS with an acceptable degree of error. The exception to the rule is the subtype "Temporal" which has been added by analogy.
Association to a coordinate reference system, either referencing or containing the definition of that reference system.
A coordinate reference system describing the position of points through two or more independent coordinate reference systems.
Ordered sequence of associations to all the component coordinate reference systems included in this compound coordinate reference system.
An association to a component coordinate reference system included in this compound coordinate reference system.
Association to a compound coordinate reference system, either referencing or containing the definition of that reference system.
A coordinate reference system based on an ellipsoidal approximation of the geoid; this provides an accurate representation of the geometry of geographic features for a large portion of the earth's surface.
Association to the ellipsoidal coordinate system used by this CRS.
Association to the geodetic datum used by this CRS.
Association to a geographic coordinate reference system, either referencing or containing the definition of that reference system.
A 1D coordinate reference system used for recording heights or depths. Vertical CRSs make use of the direction of gravity to define the concept of height or depth, but the relationship with gravity may not be straightforward. By implication, ellipsoidal heights (h) cannot be captured in a vertical coordinate reference system. Ellipsoidal heights cannot exist independently, but only as an inseparable part of a 3D coordinate tuple defined in a geographic 3D coordinate reference system.
Association to the vertical coordinate system used by this CRS.
Association to the vertical datum used by this CRS.
Association to a vertical coordinate reference system, either referencing or containing the definition of that reference system.
A 3D coordinate reference system with the origin at the approximate centre of mass of the earth. A geocentric CRS deals with the earth's curvature by taking a 3D spatial view, which obviates the need to model the earth's curvature.
Association to the Cartesian coordinate system used by this CRS.
Association to the spherical coordinate system used by this CRS.
Association to a geocentric coordinate reference system, either referencing or containing the definition of that reference system.
A coordinate reference system that is defined by its coordinate conversion from another coordinate reference system (not by a datum). This abstract complexType shall not be used, extended, or restricted, in an Application Schema, to define a concrete subtype with a meaning equivalent to a concrete subtype specified in this document.
Association to the coordinate reference system used by this derived CRS.
Association to the coordinate conversion used to define this derived CRS.
A 2D coordinate reference system used to approximate the shape of the earth on a planar surface, but in such a way that the distortion that is inherent to the approximation is carefully controlled and known. Distortion correction is commonly applied to calculated bearings and distances to produce values that are a close match to actual field values.
Association to a projected coordinate reference system, either referencing or containing the definition of that reference system.
A coordinate reference system that is defined by its coordinate conversion from another coordinate reference system but is not a projected coordinate reference system. This category includes coordinate reference systems derived from a projected coordinate reference system.
Type of a derived coordinate reference system.
Reference to a source of information specifying the values and meanings of all the allowed string values for this DerivedCRSTypeType.
Association to the coordinate system used by this CRS.
Association to a non-projected derived coordinate reference system, either referencing or containing the definition of that reference system.
A contextually local coordinate reference system; which can be divided into two broad categories:
- earth-fixed systems applied to engineering activities on or near the surface of the earth;
- CRSs on moving platforms such as road vehicles, vessels, aircraft, or spacecraft.
For further information, see OGC Abstract Specification Topic 2.
Association to the engineering datum used by this CRS.
Association to an engineering coordinate reference system, either referencing or containing the definition of that reference system.
An engineering coordinate reference system applied to locations in images. Image coordinate reference systems are treated as a separate sub-type because a separate user community exists for images with its own terms of reference.
Association to the oblique Cartesian coordinate system used by this CRS.
Association to the image datum used by this CRS.
Association to an image coordinate reference system, either referencing or containing the definition of that reference system.
A 1D coordinate reference system used for the recording of time.
Association to the temporal coordinate system used by this CRS.
Association to the temporal datum used by this CRS.
Association to a temporal coordinate reference system, either referencing or containing the definition of that reference system.
Basic encoding for coordinate system axis objects, simplifying and restricting the DefinitionType as needed.
The name by which this coordinate system axis is identified.
Definition of a coordinate system axis.
Set of alternative identifications of this coordinate system axis. The first axisID, if any, is normally the primary identification code, and any others are aliases.
Comments on or information about this coordinate system axis, including data source information.
An identification of a coordinate system axis.
The abbreviation used for this coordinate system axis. This abbreviation can be used to identify the ordinates in a coordinate tuple. Examples are X and Y. The codeSpace attribute can reference a source of more information on a set of standardized abbreviations, or on this abbreviation.
Direction of this coordinate system axis (or in the case of Cartesian projected coordinates, the direction of this coordinate system axis at the origin). Examples: north or south, east or west, up or down. Within any set of coordinate system axes, only one of each pair of terms can be used. For earth-fixed CRSs, this direction is often approximate and intended to provide a human interpretable meaning to the axis. When a geodetic datum is used, the precise directions of the axes may therefore vary slightly from this approximate direction. Note that an EngineeringCRS can include specific descriptions of the directions of its coordinate system axes. For example, the path of a linear CRS axis can be referenced in another document, such as referencing a GML feature that references or includes a curve geometry. The codeSpace attribute can reference a source of more information on a set of standardized directions, or on this direction.
Identifier of the unit of measure used for this coordinate system axis. The value of this coordinate in a coordinate tuple shall be recorded using this unit of measure, whenever those coordinates use a coordinate reference system that uses a coordinate system that uses this axis.
Association to a coordinate system axis, either referencing or containing the definition of that axis.
Basic encoding for coordinate system objects, simplifying and restricting the DefinitionType as needed.
The name by which this coordinate system is identified.
A coordinate system (CS) is the set of coordinate system axes that spans a given coordinate space. A CS is derived from a set of (mathematical) rules for specifying how coordinates in a given space are to be assigned to points. The coordinate values in a coordinate tuple shall be recorded in the order in which the coordinate system axes associations are recorded, whenever those coordinates use a coordinate reference system that uses this coordinate system. This abstract complexType shall not be used, extended, or restricted, in an Application Schema, to define a concrete subtype with a meaning equivalent to a concrete subtype specified in this document.
Set of alternative identifications of this coordinate system. The first csID, if any, is normally the primary identification code, and any others are aliases.
Comments on or information about this coordinate system, including data source information.
Ordered sequence of associations to the coordinate system axes included in this coordinate system.
An identification of a coordinate system.
Association to a coordinate system axis.
Association to a coordinate system, either referencing or containing the definition of that coordinate system.
A two- or three-dimensional coordinate system in which position is specified by geodetic latitude, geodetic longitude, and (in the three-dimensional case) ellipsoidal height. An EllipsoidalCS shall have two or three usesAxis associations.
Association to an ellipsoidal coordinate system, either referencing or containing the definition of that coordinate system.
A 1-, 2-, or 3-dimensional coordinate system. Gives the position of points relative to orthogonal straight axes in the 2- and 3-dimensional cases. In the 1-dimensional case, it contains a single straight coordinate axis. In the multi-dimensional case, all axes shall have the same length unit of measure. A CartesianCS shall have one, two, or three usesAxis associations.
Association to a Cartesian coordinate system, either referencing or containing the definition of that coordinate system.
A one-dimensional coordinate system used to record the heights (or depths) of points. Such a coordinate system is usually dependent on the Earth's gravity field, perhaps loosely as when atmospheric pressure is the basis for the vertical coordinate system axis. A VerticalCS shall have one usesAxis association.
Association to a vertical coordinate system, either referencing or containing the definition of that coordinate system.
A one-dimensional coordinate system containing a single time axis, used to describe the temporal position of a point in the specified time units from a specified time origin. A TemporalCS shall have one usesAxis association.
Association to a temporal coordinate system, either referencing or containing the definition of that coordinate system.
A one-dimensional coordinate system that consists of the points that lie on the single axis described. The associated ordinate is the distance from the specified origin to the point along the axis. Example: usage of the line feature representing a road to describe points on or along that road. A LinearCS shall have one usesAxis association.
Association to a linear coordinate system, either referencing or containing the definition of that coordinate system.
A two- or three-dimensional coordinate system that consists of any combination of coordinate axes not covered by any other coordinate system type. An example is a multilinear coordinate system which contains one coordinate axis that may have any 1-D shape which has no intersections with itself. This non-straight axis is supplemented by one or two straight axes to complete a 2 or 3 dimensional coordinate system. The non-straight axis is typically incrementally straight or curved. A UserDefinedCS shall have two or three usesAxis associations.
Association to a user-defined coordinate system, either referencing or containing the definition of that coordinate system.
A three-dimensional coordinate system with one distance measured from the origin and two angular coordinates. Not to be confused with an ellipsoidal coordinate system based on an ellipsoid "degenerated" into a sphere. A SphericalCS shall have three usesAxis associations.
Association to a spherical coordinate system, either referencing or containing the definition of that coordinate system.
A two-dimensional coordinate system in which position is specified by the distance from the origin and the angle between the line from the origin to a point and a reference direction. A PolarCS shall have two usesAxis associations.
Association to a polar coordinate system, either referencing or containing the definition of that coordinate system.
A three-dimensional coordinate system consisting of a polar coordinate system extended by a straight coordinate axis perpendicular to the plane spanned by the polar coordinate system. A CylindricalCS shall have three usesAxis associations.
Association to a cylindrical coordinate system, either referencing or containing the definition of that coordinate system.
A two- or three-dimensional coordinate system with straight axes that are not necessarily orthogonal. An ObliqueCartesianCS shall have two or three usesAxis associations.
Association to an oblique-Cartesian coordinate system, either referencing or containing the definition of that coordinate system.
Basic encoding for coordinate operation objects, simplifying and restricting the DefinitionType as needed.
The name by which this coordinate operation is identified.
A mathematical operation on coordinates that transforms or converts coordinates to another coordinate reference system. Many but not all coordinate operations (from CRS A to CRS B) also uniquely define the inverse operation (from CRS B to CRS A). In some cases, the operation method algorithm for the inverse operation is the same as for the forward algorithm, but the signs of some operation parameter values must be reversed. In other cases, different algorithms are required for the forward and inverse operations, but the same operation parameter values are used. If (some) entirely different parameter values are needed, a different coordinate operation shall be defined.
Set of alternative identifications of this coordinate operation. The first coordinateOperationID, if any, is normally the primary identification code, and any others are aliases.
Comments on or information about this coordinate operation, including source information.
Unordered set of estimates of the impact of this coordinate operation on point position accuracy. Gives position error estimates for target coordinates of this coordinate operation, assuming no errors in source coordinates.
An identification of a coordinate operation.
Version of the coordinate transformation (i.e., instantiation due to the stochastic nature of the parameters). Mandatory when describing a transformation, and should not be supplied for a conversion.
Association to the source CRS (coordinate reference system) of this coordinate operation.
Association to the target CRS (coordinate reference system) of this coordinate operation. For constraints on multiplicity of "sourceCRS" and "targetCRS", see UML model of Coordinate Operation package in OGC Abstract Specification topic 2.
Association to a coordinate operation, either referencing or containing the definition of that coordinate operation.
An ordered sequence of two or more single coordinate operations. The sequence of operations is constrained by the requirement that the source coordinate reference system of step (n+1) must be the same as the target coordinate reference system of step (n). The source coordinate reference system of the first step and the target coordinate reference system of the last step are the source and target coordinate reference system associated with the concatenated operation. Instead of a forward operation, an inverse operation may be used for one or more of the operation steps mentioned above, if the inverse operation is uniquely defined by the forward operation.
Ordered sequence of associations to the two or more single operations used by this concatenated operation.
Association to a single operation.
Association to a concatenated operation, either referencing or containing the definition of that concatenated operation.
A single (not concatenated) coordinate operation.
Association to a single operation, either referencing or containing the definition of that single operation.
A pass-through operation specifies that a subset of a coordinate tuple is subject to a specific coordinate operation.
Ordered sequence of positive integers defining the positions in a coordinate tuple of the coordinates affected by this pass-through operation.
A positive integer defining a position in a coordinate tuple.
Association to the operation applied to the specified ordinates.
Association to a pass through operation, either referencing or containing the definition of that pass through operation.
A parameterized mathematical operation on coordinates that transforms or converts coordinates to another coordinate reference system. This coordinate operation uses an operation method, usually with associated parameter values. However, operation methods and parameter values are directly associated with concrete subtypes, not with this abstract type.
This abstract complexType shall not be directly used, extended, or restricted in a compliant Application Schema.
Association to an abstract operation, either referencing or containing the definition of that operation.
An abstract operation on coordinates that does not include any change of datum. The best-known example of a coordinate conversion is a map projection. The parameters describing coordinate conversions are defined rather than empirically derived. Note that some conversions have no parameters.
This abstract complexType is expected to be extended for well-known operation methods with many Conversion instances, in Application Schemas that define operation-method-specialized element names and contents. This conversion uses an operation method, usually with associated parameter values. However, operation methods and parameter values are directly associated with concrete subtypes, not with this abstract type. All concrete types derived from this type shall extend this type to include a "usesMethod" element that references the "OperationMethod" element. Similarly, all concrete types derived from this type shall extend this type to include zero or more elements each named "uses...Value" that each use the type of an element substitutable for the "_generalParameterValue" element.
Association to a general conversion, either referencing or containing the definition of that conversion.
A concrete operation on coordinates that does not include any change of Datum. The best-known example of a coordinate conversion is a map projection. The parameters describing coordinate conversions are defined rather than empirically derived. Note that some conversions have no parameters.
This concrete complexType can be used with all operation methods, without using an Application Schema that defines operation-method-specialized element names and contents, especially for methods with only one Conversion instance.
Unordered list of composition associations to the set of parameter values used by this conversion operation.
Association to the operation method used by this coordinate operation.
Composition association to a parameter value used by this coordinate operation.
Association to a concrete general-purpose conversion, either referencing or containing the definition of that conversion.
An abstract operation on coordinates that usually includes a change of Datum. The parameters of a coordinate transformation are empirically derived from data containing the coordinates of a series of points in both coordinate reference systems. This computational process is usually "over-determined", allowing derivation of error (or accuracy) estimates for the transformation. Also, the stochastic nature of the parameters may result in multiple (different) versions of the same coordinate transformation.
This abstract complexType is expected to be extended for well-known operation methods with many Transformation instances, in Application Schemas that define operation-method-specialized value element names and contents. This transformation uses an operation method with associated parameter values. However, operation methods and parameter values are directly associated with concrete subtypes, not with this abstract type. All concrete types derived from this type shall extend this type to include a "usesMethod" element that references one "OperationMethod" element. Similarly, all concrete types derived from this type shall extend this type to include one or more elements each named "uses...Value" that each use the type of an element substitutable for the "_generalParameterValue" element.
Association to a general transformation, either referencing or containing the definition of that transformation.
A concrete operation on coordinates that usually includes a change of datum. The parameters of a coordinate transformation are empirically derived from data containing the coordinates of a series of points in both coordinate reference systems. This computational process is usually "over-determined", allowing derivation of error (or accuracy) estimates for the transformation. Also, the stochastic nature of the parameters may result in multiple (different) versions of the same coordinate transformation.
This concrete complexType can be used for all operation methods, without using an Application Schema that defines operation-method-specialized element names and contents, especially for methods with only one Transformation instance.
Unordered set of composition associations to the set of parameter values used by this transformation operation.
Association to a transformation, either referencing or containing the definition of that transformation.
Abstract parameter value or group of parameter values.
This abstract complexType is expected to be extended and restricted for well-known operation methods with many instances, in Application Schemas that define operation-method-specialized element names and contents. Specific parameter value elements are directly contained in concrete subtypes, not in this abstract type. All concrete types derived from this type shall extend this type to include one "...Value" element with an appropriate type, which should be one of the element types allowed in the ParameterValueType. In addition, all derived concrete types shall extend this type to include a "valueOfParameter" element that references one element substitutable for the "OperationParameter" element.
A parameter value, ordered sequence of values, or reference to a file of parameter values. This concrete complexType can be used for operation methods without using an Application Schema that defines operation-method-specialized element names and contents, especially for methods with only one instance. This complexType can be used, extended, or restricted for well-known operation methods, especially for methods with many instances.
Numeric value of an operation parameter, with its associated unit of measure.
Value of an angle operation parameter, in either degree-minute-second format or single value format.
String value of an operation parameter. A string value does not have an associated unit of measure.
Positive integer value of an operation parameter, usually used for a count. An integer value does not have an associated unit of measure.
Boolean value of an operation parameter. A Boolean value does not have an associated unit of measure.
Ordered sequence of two or more numeric values of an operation parameter list, where each value has the same associated unit of measure. An element of this type contains a space-separated sequence of double values.
Ordered sequence of two or more integer values of an operation parameter list, usually used for counts. These integer values do not have an associated unit of measure. An element of this type contains a space-separated sequence of integer values.
Reference to a file or a part of a file containing one or more parameter values, each numeric value with its associated unit of measure. When referencing a part of a file, that file must contain multiple identified parts, such as an XML encoded document. Furthermore, the referenced file or part of a file can reference another part of the same or different files, as allowed in XML documents.
Association to the operation parameter that this is a value of.
A group of related parameter values. The same group can be repeated more than once in a Conversion, Transformation, or higher level parameterValueGroup, if those instances contain different values of one or more parameterValues which suitably distinquish among those groups. This concrete complexType can be used for operation methods without using an Application Schema that defines operation-method-specialized element names and contents, especially for methods with only one instance. This complexType can be used, extended, or restricted for well-known operation methods, especially for methods with many instances.
Unordered set of composition associations to the parameter values and groups of values included in this group.
A composition association to a parameter value or group of values included in this group.
Association to the operation parameter group for which this element provides parameter values.
Basic encoding for operation method objects, simplifying and restricting the DefinitionType as needed.
The name by which this operation method is identified.
Definition of an algorithm used to perform a coordinate operation. Most operation methods use a number of operation parameters, although some coordinate conversions use none. Each coordinate operation using the method assigns values to these parameters.
Set of alternative identifications of this operation method. The first methodID, if any, is normally the primary identification code, and any others are aliases.
Comments on or information about this operation method, including source information.
Unordered list of associations to the set of operation parameters and parameter groups used by this operation method.
An identification of an operation method.
Formula(s) used by this operation method. The value may be a reference to a publication. Note that the operation method may not be analytic, in which case this element references or contains the procedure, not an analytic formula.
Number of dimensions in the source CRS of this operation method.
Number of dimensions in the target CRS of this operation method.
Association to an operation parameter or parameter group used by this operation method.
Association to a concrete general-purpose operation method, either referencing or containing the definition of that method.
Abstract definition of a parameter or group of parameters used by an operation method.
The minimum number of times that values for this parameter group or parameter are required. If this attribute is omitted, the minimum number is one.
Association to an operation parameter or group, either referencing or containing the definition of that parameter or group.
Basic encoding for operation parameter objects, simplifying and restricting the DefinitionType as needed.
The name by which this operation parameter is identified.
The definition of a parameter used by an operation method. Most parameter values are numeric, but other types of parameter values are possible. This complexType is expected to be used or extended for all operation methods, without defining operation-method-specialized element names.
Set of alternative identifications of this operation parameter. The first parameterID, if any, is normally the primary identification code, and any others are aliases.
Comments on or information about this operation parameter, including source information.
An identification of an operation parameter.
Association to an operation parameter, either referencing or containing the definition of that parameter.
Basic encoding for operation parameter group objects, simplifying and restricting the DefinitionType as needed.
The name by which this operation parameter group is identified.
The definition of a group of parameters used by an operation method. This complexType is expected to be used or extended for all applicable operation methods, without defining operation-method-specialized element names.
Set of alternative identifications of this operation parameter group. The first groupID, if any, is normally the primary identification code, and any others are aliases.
Comments on or information about this operation parameter group, including source information.
Unordered list of associations to the set of operation parameters that are members of this group.
An identification of an operation parameter group.
The maximum number of times that values for this parameter group can be included. If this attribute is omitted, the maximum number is one.
Association to an operation parameter that is a member of a group.
Association to an operation parameter, either referencing or containing the definition of that parameter.
Basic encoding for datum objects, simplifying and restricting the DefinitionType as needed.
The name by which this datum is identified.
A datum specifies the relationship of a coordinate system to the earth, thus creating a coordinate reference system. A datum uses a parameter or set of parameters that determine the location of the origin of the coordinate reference system. Each datum subtype can be associated with only specific types of coordinate systems. This abstract complexType shall not be used, extended, or restricted, in an Application Schema, to define a concrete subtype with a meaning equivalent to a concrete subtype specified in this document.
Set of alternative identifications of this datum. The first datumID, if any, is normally the primary identification code, and any others are aliases.
Comments on this reference system, including source information.
An identification of a datum.
Description, possibly including coordinates, of the point or points used to anchor the datum to the Earth. Also known as the "origin", especially for engineering and image datums. The codeSpace attribute can be used to reference a source of more detailed on this point or surface, or on a set of such descriptions.
- For a geodetic datum, this point is also known as the fundamental point, which is traditionally the point where the relationship between geoid and ellipsoid is defined. In some cases, the "fundamental point" may consist of a number of points. In those cases, the parameters defining the geoid/ellipsoid relationship have been averaged for these points, and the averages adopted as the datum definition.
- For an engineering datum, the anchor point may be a physical point, or it may be a point with defined coordinates in another CRS. When appropriate, the coordinates of this anchor point can be referenced in another document, such as referencing a GML feature that references or includes a point position.
- For an image datum, the anchor point is usually either the centre of the image or the corner of the image.
- For a temporal datum, this attribute is not defined. Instead of the anchor point, a temporal datum carries a separate time origin of type DateTime.
The time after which this datum definition is valid. This time may be precise (e.g. 1997.0 for IRTF97) or merely a year (e.g. 1983 for NAD83). In the latter case, the epoch usually refers to the year in which a major recalculation of the geodetic control network, underlying the datum, was executed or initiated. An old datum can remain valid after a new datum is defined. Alternatively, a datum may be superseded by a later datum, in which case the realization epoch for the new datum defines the upper limit for the validity of the superseded datum.
Association to a datum, either referencing or containing the definition of that datum.
An engineering datum defines the origin of an engineering coordinate reference system, and is used in a region around that origin. This origin can be fixed with respect to the earth (such as a defined point at a construction site), or be a defined point on a moving vehicle (such as on a ship or satellite).
Association to an engineering datum, either referencing or containing the definition of that datum.
An image datum defines the origin of an image coordinate reference system, and is used in a local context only. For more information, see OGC Abstract Specification Topic 2.
Specification of the way an image grid is associated with the image data attributes.
Reference to a source of information specifying the values and meanings of all the allowed string values for this PixelInCellType.
Association to an image datum, either referencing or containing the definition of that datum.
A textual description and/or a set of parameters identifying a particular reference level surface used as a zero-height surface, including its position with respect to the Earth for any of the height types recognized by this standard. There are several types of Vertical Datums, and each may place constraints on the Coordinate Axis with which it is combined to create a Vertical CRS.
Type of a vertical datum.
Reference to a source of information specifying the values and meanings of all the allowed string values for this VerticalDatumTypeType.
Association to a vertical datum, either referencing or containing the definition of that datum.
Partially defines the origin of a temporal coordinate reference system. This type restricts the AbstractDatumType to remove the "anchorPoint" and "realizationEpoch" elements.
Defines the origin of a temporal coordinate reference system. This type extends the TemporalDatumRestrictionType to add the "origin" element with the dateTime type.
The date and time origin of this temporal datum.
Association to a temporal datum, either referencing or containing the definition of that datum.
A geodetic datum defines the precise location and orientation in 3-dimensional space of a defined ellipsoid (or sphere) that approximates the shape of the earth, or of a Cartesian coordinate system centered in this ellipsoid (or sphere).
Association to the prime meridian used by this geodetic datum.
Association to the ellipsoid used by this geodetic datum.
Association to a geodetic datum, either referencing or containing the definition of that datum.
Basic encoding for prime meridian objects, simplifying and restricting the DefinitionType as needed.
The name by which this prime meridian is identified. The meridianName most common value is Greenwich, and that value shall be used when the greenwichLongitude value is zero.
A prime meridian defines the origin from which longitude values are determined.
Set of alternative identifications of this prime meridian. The first meridianID, if any, is normally the primary identification code, and any others are aliases.
Comments on or information about this prime meridian, including source information.
An identification of a prime meridian.
Longitude of the prime meridian measured from the Greenwich meridian, positive eastward. The greenwichLongitude most common value is zero, and that value shall be used when the meridianName value is Greenwich.
Association to a prime meridian, either referencing or containing the definition of that meridian.
Basic encoding for ellipsoid objects, simplifying and restricting the DefinitionType as needed.
The name by which this ellipsoid is identified.
An ellipsoid is a geometric figure that can be used to describe the approximate shape of the earth. In mathematical terms, it is a surface formed by the rotation of an ellipse about its minor axis.
Set of alternative identifications of this ellipsoid. The first ellipsoidID, if any, is normally the primary identification code, and any others are aliases.
Comments on or information about this ellipsoid, including source information.
An identification of an ellipsoid.
Length of the semi-major axis of the ellipsoid, with its units. Uses the MeasureType with the restriction that the unit of measure referenced by uom must be suitable for a length, such as metres or feet.
Association to an ellipsoid, either referencing or containing the definition of that ellipsoid.
Definition of the second parameter that defines the shape of an ellipsoid. An ellipsoid requires two defining parameters: semi-major axis and inverse flattening or semi-major axis and semi-minor axis. When the reference body is a sphere rather than an ellipsoid, only a single defining parameter is required, namely the radius of the sphere; in that case, the semi-major axis "degenerates" into the radius of the sphere.
Inverse flattening value of the ellipsoid. Value is a scale factor (or ratio) that has no physical unit. Uses the MeasureType with the restriction that the unit of measure referenced by uom must be suitable for a scale factor, such as percent, permil, or parts-per-million.
Length of the semi-minor axis of the ellipsoid. Uses the MeasureType with the restriction that the unit of measure referenced by uom must be suitable for a length, such as metres or feet.
The ellipsoid is degenerate and is actually a sphere. The sphere is completely defined by the semi-major axis, which is the radius of the sphere.
Basic encoding for reference system objects, simplifying and restricting the DefinitionType as needed.
The name by which this reference system is identified.
Description of a spatial and/or temporal reference system used by a dataset.
Set of alterative identifications of this reference system. The first srsID, if any, is normally the primary identification code, and any others are aliases.
Comments on or information about this reference system, including source information.
An identification of a reference system.
Association to a reference system, either referencing or containing the definition of that reference system.
Abstract coordinate reference system, usually defined by a coordinate system and a datum. This abstract complexType shall not be used, extended, or restricted, in an Application Schema, to define a concrete subtype with a meaning equivalent to a concrete subtype specified in this document.
Association to a CRS abstract coordinate reference system, either referencing or containing the definition of that CRS.
An identification of a CRS object. The first use of the IdentifierType for an object, if any, is normally the primary identification code, and any others are aliases.
The code or name for this Identifier, often from a controlled list or pattern defined by a code space. The optional codeSpace attribute is normally included to identify or reference a code space within which one or more codes are defined. This code space is often defined by some authority organization, where one organization may define multiple code spaces. The range and format of each Code Space identifier is defined by that code space authority. Information about that code space authority can be included as metaDataProperty elements which are optionally allowed in all CRS objects.
Remarks about this code or alias.
Identifier of the version of the associated codeSpace or code, as specified by the codeSpace or code authority. This version is included only when the "code" or "codeSpace" uses versions. When appropriate, the version is identified by the effective date, coded using ISO 8601 date format.
Information about this object or code. Contains text or refers to external text.
Description of domain of usage, or limitations of usage, for which this CRS object is valid.
Area or region in which this CRS object is valid.
Information about the spatial, vertical, and/or temporal extent of a reference system object. Constraints: At least one of the elements "description", "boundingBox", "boundingPolygon", "verticalExtent", and temporalExtent" must be included, but more that one can be included when appropriate. Furthermore, more than one "boundingBox", "boundingPolygon", "verticalExtent", and/or temporalExtent" element can be included, with more than one meaning the union of the individual domains.
Description of spatial and/or temporal extent of this object.
Geographic domain of this reference system object.
Unordered list of bounding boxes (or envelopes) whose union describes the spatial domain of this object.
Unordered list of bounding polygons whose union describes the spatial domain of this object.
Unordered list of vertical intervals whose union describes the spatial domain of this object.
Unordered list of time periods whose union describes the spatial domain of this object.
A bounding box (or envelope) defining the spatial domain of this object.
A bounding polygon defining the horizontal spatial domain of this object.
An interval defining the vertical spatial domain of this object.
A time period defining the temporal domain of this object.
Definition of a unit of measure (or uom). The definition includes a quantityType property, which indicates the phenomenon to which the units apply, and a catalogSymbol, which gives the short symbol used for this unit. This element is used when the relationship of this unit to other units or units systems is unknown.
Definition of a unit of measure which is a base unit from the system of units. A base unit cannot be derived by combination of other base units within this system. Sometimes known as "fundamental unit".
Definition of a unit of measure which is defined through algebraic combination of more primitive units, which are usually base units from a particular system of units. Derived units based directly on base units are usually preferred for quantities other than the base units or fundamental quantities within a system. If a derived unit is not the preferred unit, the ConventionalUnit element should be used instead.
Definition of a unit of measure which is related to a preferred unit for this quantity type through a conversion formula. A method for deriving this unit by algebraic combination of more primitive units, may also be provided.
Informal description of the phenomenon or type of quantity that is measured or observed. For example, "length", "angle", "time", "pressure", or "temperature". When the quantity is the result of an observation or measurement, this term is known as Observable Type or Measurand.
For global understanding of a unit of measure, it is often possible to reference an item in a catalog of units, using a symbol in that catalog. The "codeSpace" attribute in "CodeType" identifies a namespace for the catalog symbol value, and might reference the catalog. The "string" value in "CodeType" contains the value of a symbol that is unique within this catalog namespace. This symbol often appears explicitly in the catalog, but it could be a combination of symbols using a specified algebra of units. For example, the symbol "cm" might indicate that it is the "m" symbol combined with the "c" prefix.
Definition of one unit term for a derived unit of measure. This unit term references another unit of measure (uom) and provides an integer exponent applied to that unit in defining the compound unit. The exponent can be positive or negative, but not zero.
This element is included when this unit has an accurate conversion to the preferred unit for this quantity type.
This element is included when the correct definition of this unit is unknown, but this unit has a rough or inaccurate conversion to the preferred unit for this quantity type.
Relation of a unit to the preferred unit for this quantity type, specified by an arithmetic conversion (scaling and/or offset). A preferred unit is either a base unit or a derived unit selected for all units of one quantity type. The mandatory attribute "uom" shall reference the preferred unit that this conversion applies to. The conversion is specified by one of two alternative elements: "factor" or "formula".
Specification of the scale factor by which a value using this unit of measure can be multiplied to obtain the corresponding value using the preferred unit of measure.
Specification of the formula by which a value using this unit of measure can be converted to obtain the corresponding value using the preferred unit of measure.
Paremeters of a simple formula by which a value using this unit of measure can be converted to the corresponding value using the preferred unit of measure. The formula element contains elements a, b, c and d, whose values use the XML Schema type "double". These values are used in the formula y = (a + bx) / (c + dx), where x is a value using this unit, and y is the corresponding value using the preferred unit. The elements a and d are optional, and if values are not provided, those parameters are considered to be zero. If values are not provided for both a and d, the formula is equivalent to a fraction with numerator and denominator parameters.
Contains or refers to a metadata package that contains metadata properties.
Base type for complex metadata property types.
Value of a scale factor (or ratio) that has no physical unit. Uses the MeasureType with the restriction that the unit of measure referenced by uom must be suitable for a scale factor, such as percent, permil, or parts-per-million.
Value of an angle quantity provided in either degree-minute-second format or single value format.
Angle value provided in degree-minute-second or degree-minute format.
Integer number of degrees, plus the angle direction. This element can be used for geographic Latitude and Longitude. For Latitude, the XML attribute direction can take the values "N" or "S", meaning North or South of the equator. For Longitude, direction can take the values "E" or "W", meaning East or West of the prime meridian. This element can also be used for other angles. In that case, the direction can take the values "+" or "-" (of SignType), in the specified rotational direction from a specified reference direction.
Integer number of degrees in a degree-minute-second or degree-minute angular value, without indication of direction.
Decimal number of arc-minutes in a degree-minute angular value.
Integer number of arc-minutes in a degree-minute-second angular value.
Number of arc-seconds in a degree-minute-second angular value.
Utility type used in various places
- e.g. to indicate the direction of topological objects;
"+" for forwards, or "-" for backwards.
Position error estimate (or accuracy) data.
A description of the position accuracy parameter(s) provided.