[
https://issues.apache.org/jira/browse/SIS-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Desruisseaux resolved SIS-552.
-------------------------------------
Resolution: Fixed
Actually we still do not test unit first as recommended by CF-conventions,
because the "degrees_east" and "degrees_north" units are already checked in
other parts of the code. We want {{AxisType}} to perform a different check for
giving Apache SIS a chance to report a warning is an inconsistency is found.
Instead "X", "Y" and "Z" axis types are considered ambiguous. When such types
are found, SIS continue with the other tests in above list until a
non-ambiguous type is found. The ambiguous type is returned only if no better
type is found.
> Better identification of latitude/longitude axes in netCDF
> ----------------------------------------------------------
>
> Key: SIS-552
> URL: https://issues.apache.org/jira/browse/SIS-552
> Project: Spatial Information Systems
> Issue Type: Improvement
> Components: Storage
> Affects Versions: 1.0, 1.1, 1.2
> Reporter: Martin Desruisseaux
> Assignee: Martin Desruisseaux
> Priority: Major
> Fix For: 1.3
>
>
> The Coordinate Reference System inferred by the parsing of a netCDF file is
> sometime of type {{EngineeringCRS}} when it should be {{GeographicCRS}}. This
> is caused by {{AxisType}} using the following criteria in that order:
> * Value of {{_CoordinateAxisType}} attribute, which may be "GeoX" or "GeoY"
> among others.
> * Value of {{axis}} attribute, which may be "X" or "Y" among others.
> * Value of {{standard_name}} attribute, which may be "longitude" or
> "latitude" among others.
> * Value of {{description}}, {{title}} or {{long_name}} attribute.
> * Unit of measurement, which may be "degrees_east" or "degrees_north" among
> others.
> The problem occurs when we find an {{axis}} attribute with value "X" or "Y",
> which is used in CF convention not only for latitude/longitude, but also for
> other kind of horizontal axes. Apache SIS conservatively assumes an
> engineering CRS as the closest match for CRS of unknown type.
> According CF conventions, the "degrees_east" and "degrees_north" units of
> measurement should be tested first. We should modify {{AxisType}} for using
> that order.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
