[
https://issues.apache.org/jira/browse/SIS-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Desruisseaux resolved SIS-594.
-------------------------------------
Resolution: Fixed
> Accept transform steps with swapped (source, target) CRS
> --------------------------------------------------------
>
> Key: SIS-594
> URL: https://issues.apache.org/jira/browse/SIS-594
> Project: Spatial Information Systems
> Issue Type: Improvement
> Components: Referencing
> Affects Versions: 0.6, 0.7, 0.8, 1.0, 1.1, 1.2, 1.3, 1.4
> Reporter: Martin Desruisseaux
> Assignee: Martin Desruisseaux
> Priority: Major
> Fix For: 1.5
>
>
> In a {{ConcatenatedOperation}}, usually the {{targetCRS}} of a step should be
> the {{sourceCRS}} of the next step. But {{ConcatenatedOperation}} instances
> are sometime provided with steps that need to have their source and target
> CRS swapped in order to met above-cited consistency. Such cases should be
> interpreted as defining the inverse transform of a step. This practice avoids
> the problem of {{OperationMethod}} defined in only one direction, for example
> map projections (the inverse projection is defined in the text, but no
> {{OperationMethod}} instance is provided for them). Some
> {{ConcatenatedOperation}} in the EPSG geodetic dataset use that pattern.
> The changes need to be applied in {{DefaultConcatenatedOperation}} class. We
> also need to search all usages of {{ConcatenatedOperation.getOperations()}}
> for verifying if the code is robust to step with (source, target) CRS swapped.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
