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] [Updated] (SIS-163) Unsupported WKT 2 features
Date Mon, 06 Jul 2015 10:28:04 GMT

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

Martin Desruisseaux updated SIS-163:
------------------------------------
    Affects Version/s: 0.6

> Unsupported WKT 2 features
> --------------------------
>
>                 Key: SIS-163
>                 URL: https://issues.apache.org/jira/browse/SIS-163
>             Project: Spatial Information Systems
>          Issue Type: Task
>          Components: Referencing
>    Affects Versions: 0.4, 0.5, 0.6
>            Reporter: Martin Desruisseaux
>            Priority: Minor
>
> This page summarizes the WKT 2 features which are currently not supported in Apache SIS.
More details are provided in the sub-tasks for unsupported elements and restrictions. The
third sections is about recommendations that are not mandatory, but that we do not yet follow.
> h3. Unsupported WKT elements
> * {{ParametricCRS}} (we need an implementation in the rest of SIS first).
> * {{Bearing}} element for polar coordinate systems having a "clockwise" or "counterClockwise"
axis direction.
> * {{BoundCRS}} element as the successor of the WKT 1 {{TOWGS84}} element.
> * Time extent with named eras (e.g.{{TIMEEXTENT\["Jurassic", "Quaternary"\]}})
> h3. Restrictions that we do not verify
> * ISO 19162 restrictions on {{CompoundCRS}}: (_geographic_ or _projected_ or _engineering_)
followed by (_vertical_ or _parametric_) followed by _temporal_.
> * ISO 19162 restrictions on axis name, abbreviation and directions (e.g. geographic CRS
shall be ‘_latitude_’, ‘_longitude_’).
> * Precedence of EPSG codes over names for {{Conversion}} objects.
> h3. Recommendations that we do not yet follow
> * Formatter should be able to write the short WKT 2 keywords (currently we format only
the long ones, because they match the type names).
> * We do not check the recommended maximum string lengths (80 characters in names, 255
characters in other quoted texts, 4096 in total).



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

Mime
View raw message