[
https://issues.apache.org/jira/browse/SIS-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Desruisseaux updated SIS-206:
------------------------------------
Fix Version/s: (was: 1.1)
1.2
Affects Version/s: 1.1
1.0
> Verify axis name, abbreviation and direction constraints at format time
> -----------------------------------------------------------------------
>
> Key: SIS-206
> URL: https://issues.apache.org/jira/browse/SIS-206
> Project: Spatial Information Systems
> Issue Type: Sub-task
> Components: Referencing
> Affects Versions: 0.4, 0.5, 0.6, 0.7, 0.8, 1.0, 1.1
> Reporter: Martin Desruisseaux
> Assignee: Martin Desruisseaux
> Priority: Minor
> Fix For: 1.2
>
>
> 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
(v8.3.4#803005)
