sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Desruisseaux (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (SIS-335) CRS.findOperation(…) sometime slow
Date Tue, 02 May 2017 12:28:04 GMT

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

Martin Desruisseaux closed SIS-335.
-----------------------------------

> CRS.findOperation(…) sometime slow
> ----------------------------------
>
>                 Key: SIS-335
>                 URL: https://issues.apache.org/jira/browse/SIS-335
>             Project: Spatial Information Systems
>          Issue Type: Bug
>          Components: Referencing
>    Affects Versions: 0.7
>            Reporter: Martin Desruisseaux
>            Assignee: Martin Desruisseaux
>             Fix For: 0.8
>
>
> Execution of {{CRS.findOperation(sourceCRS, targetCRS, areaOfInterest)}} is slow when:
> * A connection to the EPSG geodetic dataset is available (which is recommended)
> * the given CRS have no EPSG identifiers, or their identifiers are wrong
> In such case, {{IdentifiedObjectFinder}} search the right EPSG code for the given CRS
by scanning the EPSG database. Some conditions are put in the SQL {{WHERE}} clause for reducing
the amount of CRS to scan, but in Apache SIS 0.7 those conditions are not restrictive enough,
resulting in way too many CRS being scanned.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message