Interface ReferenceSystem

All Superinterfaces:
IdentifiedObject
All Known Subinterfaces:
CompoundCRS, CoordinateReferenceSystem, DerivedCRS, EngineeringCRS, GeneralDerivedCRS, GeocentricCRS, GeodeticCRS, GeographicCRS, ImageCRS, ProjectedCRS, SingleCRS, TemporalCRS, VerticalCRS

@UML(identifier="RS_ReferenceSystem", specification=ISO_19115) public interface ReferenceSystem extends IdentifiedObject
Description of a spatial and temporal reference system used by a dataset.
Since:
1.0
See Also:
Departure from OGC/ISO abstract specification:
Departure for historical reason This interface was initially derived from an ISO 19111 specification published in 2003. Later revisions (in 2005) rely on an interface defined in ISO 19115 instead. The annotations were updated accordingly, but this interface is still defined in the referencing package instead of the metadata package for this historical reason.
  • Field Details

  • Method Details

    • getDomainOfValidity

      @UML(identifier="domainOfValidity", obligation=OPTIONAL, specification=ISO_19111) Extent getDomainOfValidity()
      Area or region or timeframe in which this (coordinate) reference system is valid.
      Returns:
      The reference system valid domain, or null if not available.
      Since:
      2.1
      Departure from OGC/ISO abstract specification:
      Departure for historical reason This method has been kept conformant with the specification published in 2003. Later revisions changed the multiplicity, so the return type should now be a collection. The singleton has been preserved in GeoAPI for historical reasons, and also because the Extent attributes already allow collections.
    • getScope

      Description of domain of usage, or limitations of usage, for which this Reference System object is valid.
      Returns:
      The domain of usage, or null if none.
      Departure from OGC/ISO abstract specification:
      Departure for historical reason This method has been kept conformant with the specification published in 2003. A later revision moved this attribute to subclasses, but GeoAPI keeps this method here for historical reasons. The obligation is still optional, as opposed to ISO 19111:2007 which makes this attribute mandatory while mandating the text "not known" if the scope is unknown. In addition, the return value of this method is still a singleton as in the 2003 version, as opposed to the 2007 version which mandates a collection. The proposed change is still under review.