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] [Created] (SIS-431) Need MD_ReferenceSystem adapter
Date Sun, 02 Sep 2018 15:46:00 GMT
Martin Desruisseaux created SIS-431:
---------------------------------------

             Summary: Need MD_ReferenceSystem adapter
                 Key: SIS-431
                 URL: https://issues.apache.org/jira/browse/SIS-431
             Project: Spatial Information Systems
          Issue Type: Task
          Components: Metadata
            Reporter: Martin Desruisseaux
            Assignee: Martin Desruisseaux
             Fix For: 1.0


Coordinate Reference Systems (CRS) are defined in details by the ISO 19111 classes in GeoAPI
{{org.opengis.referencing.*}} packages. But the ISO 19115 metadata standards do not reference
those CRS classes directly (except in one case). Instead the metadata standards reference
CRS by their identifier (for example an EPSG code), optionally accompanied by a code telling
whether the CRS type is geographic, projected, temporal, a compound of the above, _etc_. Those
two information are combined in a {{MD_ReferenceSystem}} class referenced by the following
properties:

||Class||Association to {{MD_ReferenceSystem}}||Association to a {{CRS}} subtype
|{{MD_Metadata}}|{{referenceSystemInfo}}| |
|{{LI_Source}}|{{sourceReferenceSystem}}| |
|{{EX_VerticalExtent}}|{{verticalCRSId}}|{{verticalCRS}}
|{{MI_GCPCollection}}|{{coordinateReferenceSystem}}| |

In order to have a more uniform way to handle reference systems, GeoAPI replaces those (_identifier_,
_type code_) tuples by associations to the actual _Reference System_ objects.
GeoAPI does that by using the {{ReferenceSystem}} interface as the parent of {{CoordinateReferenceSystem}}
interface.

However current Apache SIS implementation of {{MD_ReferenceSystem}} JAXB adapter marshalls
the full CRS, which is not the expected behavior except in the {{verticalCRS}} case. We need
to modify this adapter for marshalling only the identifier and the {{MD_ReferenceSystemTypeCode}}
instead.

In the particular case of {{VerticalExtent}}, the proposal is to marshal the {{verticalCRSId}}
if an EPSG code is available, or {{verticalCRS}} otherwise.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message