[
https://issues.apache.org/jira/browse/SIS-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Desruisseaux updated SIS-210:
------------------------------------
Affects Version/s: 0.8
0.7
Fix Version/s: 1.0
> Enforce precedence of EPSG codes over names at parsing time
> -----------------------------------------------------------
>
> Key: SIS-210
> URL: https://issues.apache.org/jira/browse/SIS-210
> Project: Spatial Information Systems
> Issue Type: Sub-task
> Components: Referencing
> Affects Versions: 0.6, 0.7, 0.8
> Reporter: Martin Desruisseaux
> Priority: Minor
> Fix For: 1.0
>
>
> The specification ยง9.3.2 said:
> {quote}
> If an identifier is provided as an attribute within the <map projection
> conversion> object, because it is expected to describe a complete collection
> of zone name, method, parameters and parameter values, it shall override any
> identifiers given within the map projection method and map projection
> parameter objects.
> {quote}
> However this would require the {{GeodeticObjectParser}} to hold a
> {{CoordinateOperationAuthorityFactory}}, which we do not yet implement.
> Likewise, EPSG code in {{Parameter}} elements are also supposed to have
> precedence over the parameter name. This is not yet implemented in SIS, but
> may be less critical since SIS implementation is quite lenient (without
> introducing ambiguities) regarding parameter names.
> For now, the only place where EPSG codes take precedence over names is when
> fetching the {{OperationMethod}} objects, which is the most critical place
> where we observed ambiguities in our experience.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
