sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Desruisseaux (Jira)" <>
Subject [jira] [Commented] (SIS-431) Need MD_ReferenceSystem adapter
Date Wed, 11 Sep 2019 09:29:00 GMT


Martin Desruisseaux commented on SIS-431:

Close this issue since the part consisting in replacing the full CRS by an identifier is done.
The task is not fully completed however since we do not yet marshal the {{mrs:referenceSystemType}}
property and we do not perform the reverse operation (creating a full CRS at unmarshalling
time). Those two tasks the the subject of separated issues, SIS-470 and SIS-471 respectively.

> Need MD_ReferenceSystem adapter
> -------------------------------
>                 Key: SIS-431
>                 URL:
>             Project: Spatial Information Systems
>          Issue Type: Task
>          Components: Metadata
>            Reporter: Martin Desruisseaux
>            Assignee: Martin Desruisseaux
>            Priority: Major
>             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}}
> However current Apache SIS implementation of {{RS_ReferenceSystem}} JAXB adapter marshalls
the full CRS, which is not the expected behavior except in the {{verticalCRS}} case. We need
a new adapter - {{MD_ReferenceSystem}} - for marshalling only the identifier and the {{MD_ReferenceSystemTypeCode}}
> 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

View raw message