You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sis.apache.org by "Martin Desruisseaux (Jira)" <ji...@apache.org> on 2026/01/27 15:44:00 UTC
[jira] [Updated] (SIS-591) Parse CRS from GML like published by EPSG
[ https://issues.apache.org/jira/browse/SIS-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Desruisseaux updated SIS-591:
------------------------------------
Fix Version/s: 1.7
(was: 1.6)
> Parse CRS from GML like published by EPSG
> -----------------------------------------
>
> Key: SIS-591
> URL: https://issues.apache.org/jira/browse/SIS-591
> Project: Spatial Information Systems
> Issue Type: Improvement
> Components: Referencing
> Reporter: Martin Desruisseaux
> Assignee: Martin Desruisseaux
> Priority: Major
> Fix For: 1.7
>
>
> Apache SIS 0.7 and later can read a CRS definition in GML, but all components have to be in a single file. But the CRS definitions provided by EPSG use {{xlink:href}} instead for referring to definitions in external documents. SIS automatically follows {{xlink:href}} when they are in the same document (except for forward references, which are not yet supported), but this is not sufficient for parsing an EPSG definition.
> We need to follow {{xlink:href}} to external files. This task is described by SIS-387 for the metadata part, but the same issue applies to CRS definitions. This task is needed for OGC Testbed-19 for the definitions of CRS in space, but should have the side-effect of allowing parsing CRS definition provided online by the EPSG registry in GML. So it should not be necessary anymore for users to install the EPSG database if fetching the definition online is acceptable, and they would always get the latest definition from EPSG.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)