You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sis.apache.org by "Martin Desruisseaux (Jira)" <ji...@apache.org> on 2022/02/10 13:19:00 UTC

[jira] [Assigned] (SIS-535) Search for coordinate operations create too many CRS

     [ https://issues.apache.org/jira/browse/SIS-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Desruisseaux reassigned SIS-535:
---------------------------------------


> Search for coordinate operations create too many CRS
> ----------------------------------------------------
>
>                 Key: SIS-535
>                 URL: https://issues.apache.org/jira/browse/SIS-535
>             Project: Spatial Information Systems
>          Issue Type: Improvement
>          Components: Referencing
>    Affects Versions: 1.1, 1.0, 0.8
>            Reporter: Martin Desruisseaux
>            Assignee: Martin Desruisseaux
>            Priority: Major
>             Fix For: 1.2
>
>
> A call to {{CRS.findOperation(souceCRS, targetCRS, …)}} sometime cause an excessively large scanning of EPSG database in search for similar CRS. The problem is especially acute when one of the CRS is a Transverse Mercator projection, in which case SIS starts to instantiate all Transverse Mercator projection declared in the EPSG database using the same datum (there is potentially hundreds of them). SIS does that in case better coordinate operations can be found in the EPSG database for CRS that are equivalent but with different axis order (e.g. EPSG::4171 versus EPSG::7084). However this apply mostly to geographic CRS. Applying this search for all kinds of CRS, in particular projected CRS, may be an overfill.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)