Package org.opengis.referencing.cs
One CoordinateSystem
instance may be used by multiple
CoordinateReferenceSystem
(CRS) instances.
The number of coordinates in a coordinate tuple
shall be equal to the number of coordinate axes
in the coordinate system.
Coordinates in coordinate tuples shall be supplied in the order in which the coordinate system's axes are defined.
Coordinate system types
A coordinate system implies how coordinates are calculated from geometric elements such as distances and angles and vice versa. These rules are not specified in details, but are implied by the coordinate system interface. Certain subinterfaces of coordinate system shall be used only with specific subinterfaces of CRS. The restrictions are documented in the javadoc of each CRS subtype.Coordinate system interfaces should not be confused with coordinate system unions. The latter look similar to CS interfaces, but do not imply a specific set of mathematical rules. A CS union is only an enumeration of the CS interfaces that can be associated to a given CRS interface. Because the Java language has no direct support for unions, the CS unions defined by ISO 19111 are not part of GeoAPI. They are replaced by Javadoc documenting the constraints.
 Since:
 1.0
Departure from OGC/ISO standard due to constraint of the Java language
TheGeodeticCS
, EngineeringCS
and DerivedProjectedCS
unions are omitted because unions
are not directly supported in the Java language (they are supported in some other languages such as C/C++).
Unions could be simulated, for example, by defining GeodeticCS
as a parent interface of
org.opengis.referencing.cs.CartesianCS
, org.opengis.referencing.cs.SphericalCS
and
org.opengis.referencing.cs.EllipsoidalCS
(the members of the GeodeticCS
union).
However, it would blur the semantics of subtyping as an “is type of” hierarchy.
For example, a CartesianCS
can be used in nongeodetic contexts.
Departure from OGC/ISO standard for harmonization between different specifications
TheOrdinalCS
and TemporalCountCS
interfaces are omitted because they are about a type
of coordinate values (integers) rather than the mathematical rules implied by the coordinate system.
The DateTimeTemporalCS
interface is omitted for similar reason.
The TemporalMeasureCS
interface is omitted because it behaves like most other axes,
and therefor is adequately covered by the TimeCS
parent interface.

ClassDescriptionA 2 or 3dimensional coordinate system in Euclidean space with straight axes that are not necessarily orthogonal.The direction of positive increase in the coordinate value for a coordinate system axis.A 2 or 3dimensional coordinate system in Euclidean space with orthogonal straight axes.Type (measure, integer or date) of coordinate values.Sequence of nonrepeating coordinate system axes that spans a given coordinate space.Definition of a coordinate system axis.Creates coordinate systems using authority codes.Builds up complex coordinate systems from simpler objects or values.A 3dimensional cylindrical coordinate system.A 2 or 3dimensional coordinate system for use with geodetic CRS.A 1dimensional coordinate system that consists of the points that lie on the single axis described.A 1dimensional coordinate system in which a physical property or function is used as the dimension.A 2dimensional polar coordinate system.Meaning of the axis value range specified through minimum value and maximum value.A 2 or 3dimensional coordinate system with one distance measured from the origin and two angular coordinates.A 1dimensional coordinate system containing a single time axis.Deprecated.A 1dimensional coordinate system used to record the heights or depths of points.
CoordinateSystem
directly.