@UML(identifier="SC_VerticalCRS", specification=ISO_19111) public interface VerticalCRS extends SingleCRS
By implication, ellipsoidal heights (h) cannot be captured in a vertical coordinate reference system. Ellipsoidal heights cannot exist independently, but only as inseparable part of a 3D coordinate tuple defined in a geographic 3D coordinate reference system. However GeoAPI does not enforce this rule. Some applications may relax this rule and accept ellipsoidal heights in the following context:
As a transient state while parsing Well Known Text, or any other format based on legacy specifications where ellipsoidal heights were allowed as an independant axis.
As short-lived objects to be passed or returned by methods enforcing type safety, for
example VerticalExtent.getVerticalCRS().
Other cases at implementor convenience. However implementors are encouraged to assemble the full 3D CRS as soon as they can.
| Used with CS type(s) |
|---|
Vertical
|
DOMAIN_OF_VALIDITY_KEY, SCOPE_KEYALIAS_KEY, IDENTIFIERS_KEY, NAME_KEY, REMARKS_KEY| Modifier and Type | Method and Description |
|---|---|
VerticalCS |
getCoordinateSystem()
Returns the coordinate system, which must be vertical.
|
VerticalDatum |
getDatum()
Returns the datum, which must be vertical.
|
getDomainOfValidity, getScopegetAlias, getIdentifiers, getName, getRemarks, toWKT@UML(identifier="usesCS", obligation=MANDATORY, specification=ISO_19111) VerticalCS getCoordinateSystem()
getCoordinateSystem in interface CoordinateReferenceSystemgetCoordinateSystem in interface SingleCRS@UML(identifier="usesDatum", obligation=MANDATORY, specification=ISO_19111) VerticalDatum getDatum()
Copyright © 1996–2019 Geotools. All rights reserved.