Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance. Project price only 1 $
You can buy this project and download/modify it how often you want.
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.)
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.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.
