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] [Created] (SIS-442) Cache CRS.findOperation(…, areaOfInteret) when area of interest is non null
Date Fri, 14 Dec 2018 18:33:00 GMT
Martin Desruisseaux created SIS-442:
---------------------------------------

             Summary: Cache CRS.findOperation(…, areaOfInteret) when area of interest is
non null
                 Key: SIS-442
                 URL: https://issues.apache.org/jira/browse/SIS-442
             Project: Spatial Information Systems
          Issue Type: Task
          Components: Referencing
    Affects Versions: 0.8, 0.7
            Reporter: Martin Desruisseaux


Calls to {{CRS.findOperation(sourceCRS, targetCRS, areaOfInterest)}} currently cache the {{CoordinateOperation}}
only when {{areaOfInterest}} is null. It is hard to implement a general cache mechanism for
all non-null area of interest, but we can implement an intermediate solution:

1. When {{EPSGFactory}} or {{CoordinateOperationRegistry}} detects that there is only one
{{CoordinateOperation}} for given source and target CRS, it automatically adds some sentinel
value in {{PositionalAccuracy}} metadata. It could be some internal sub-class.
2. When {{DefaultCoordinateOperationFactory}} sees above sentinel values, it allows caching
even if {{areaOfInterest}} is non-null. Otherwise caching is enabled only if {{areaOfInterest}}
is null, as today.

We could also take this opportunity for adding an information message if we detected may transformations
for the same pair of CRS. Something like _"Note: many transformations are defined for this
pair of referencing systems in different domains of validity."_




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message