sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Desruisseaux (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SIS-204) Verify CompoundCRS restrictions at format time
Date Mon, 06 Jul 2015 14:44:04 GMT

     [ https://issues.apache.org/jira/browse/SIS-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Martin Desruisseaux resolved SIS-204.
-------------------------------------
       Resolution: Fixed
         Assignee: Martin Desruisseaux
    Fix Version/s: 0.6

Added a {{isStandardCompliant()}} method in {{CompoundCRS}}. This method is not yet public
because we relax the ISO 19162 restrictions with the following:

* Accept three-dimensional Geodetic CRS followed by a Time CRS.


> Verify CompoundCRS restrictions at format time
> ----------------------------------------------
>
>                 Key: SIS-204
>                 URL: https://issues.apache.org/jira/browse/SIS-204
>             Project: Spatial Information Systems
>          Issue Type: Sub-task
>          Components: Referencing
>    Affects Versions: 0.4, 0.5
>            Reporter: Martin Desruisseaux
>            Assignee: Martin Desruisseaux
>            Priority: Minor
>             Fix For: 0.6
>
>
> ISO 19162 restricts compound CRS to the following components in that order:
> * A mandatory horizontal CRS (only one of two-dimensional {{GeographicCRS}} or {{ProjectedCRS}}
or {{EngineeringCRS}})
> * Optionally followed by a {{VerticalCRS}} or a {{ParametricCRS}} (but not both).
> * Optionally followed by a {{TemporalCRS}}.
> SIS currently does not enforce those restrictions. In particular:
> * Components may appear in different order.
> * {{VerticalCRS}} + {{TemporalCRS}} (without horizontal component) is accepted.
> * {{GeocentricCRS}} or three-dimensional {{GeographicCRS}} can be combined with {{TemporalCRS}}.
> We should nevertheless perform a check and raise a flag if the CRS does not meet WKT
restrictions, even if we still format it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message