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.