sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Desruisseaux (JIRA)" <>
Subject [jira] [Created] (SIS-206) Enforce axis name, abbreviation and direction constraints
Date Thu, 02 Jul 2015 17:31:05 GMT
Martin Desruisseaux created SIS-206:

             Summary: Enforce axis name, abbreviation and direction constraints
                 Key: SIS-206
             Project: Spatial Information Systems
          Issue Type: Sub-task
          Components: Referencing
    Affects Versions: 0.5, 0.4
            Reporter: Martin Desruisseaux
            Priority: Minor
             Fix For: 0.6

ISO 19162 puts many constraints on axis names, abbreviations and directions. Some of those
constraints are inherited from ISO 19111, and some others are specific to ISO 19162. Apache
SIS verifies some of those constraints at {{CoordinateSystem}} construction time, but not
all. Constraints *not* verified by Apache SIS includes:

* Axis names of geographic CRS shall be ‘_latitude_’, ‘_longitude_’ and (in 3D case)
‘_ellipsoidal height_’.
* For other kind of CRS axis names shall be as documented in ISO 19111.
* Abbreviation of ellipsoidal height shall be _h_.
* Abbreviations of geocentric CRS axes shall be _X_, _Y_, _Z_.
* Axis directions are restricted to _north_, _east_ and _up_ for geographic CRS (no _south_,
_west_ or _down_).

Apache SIS does not verify those constraints at formatting time. We may argue that this is
not formatter job.
{color:red}Update (May 2015):{color} on-the-fly renaming of "Geodetic longitude/latitude"
into "longitude/latitude" now supported.

This message was sent by Atlassian JIRA

View raw message