[
https://issues.apache.org/jira/browse/SIS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Desruisseaux resolved SIS-163.
-------------------------------------
Assignee: Martin Desruisseaux
Resolution: Fixed
The missing tasks that could be done easily are done. For the missing tasks, it
is unclear how to process. For example, the WKT 2 "bearing" element has no
equivalent structure in ISO 19111, therefore it is unclear what to map this
element to. Likewise, the time extent with geological era has no obvious
mapping to {{java.time}}. The maximal length is only a recommendation. The
precedence of EPSG codes is an issue wider than WKT parsing (e.g., it applies
also to GML parsing). Finally, {{BoundCRS}} is a topic on its own.
> 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
> Assignee: 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)
> {color:green}(edit: fixed){color}.
> * {{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_. {color:green}(edit: fixed){color}
> * ISO 19162 restrictions on axis name, abbreviation and directions (e.g.
> geographic CRS shall be ‘_latitude_’, ‘_longitude_’) {color:green}(edit:
> fixed){color}.
> * 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).
> {color:green}(edit: fixed){color}
> * 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
(v8.20.10#820010)
