You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sis.apache.org by "Martin Desruisseaux (Jira)" <ji...@apache.org> on 2020/06/09 17:52:00 UTC

[jira] [Resolved] (SIS-485) Replace GridCoverage.evaluate(DirectPosition, …) method

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

Martin Desruisseaux resolved SIS-485.
-------------------------------------
    Resolution: Fixed

> Replace GridCoverage.evaluate(DirectPosition, …) method
> -------------------------------------------------------
>
>                 Key: SIS-485
>                 URL: https://issues.apache.org/jira/browse/SIS-485
>             Project: Spatial Information Systems
>          Issue Type: Task
>          Components: Features
>            Reporter: Martin Desruisseaux
>            Assignee: Martin Desruisseaux
>            Priority: Major
>             Fix For: 1.1
>
>
> The following method has been added in the {{GridCoverage}} class in the development branch:
> {code:java}
> public double[] evaluate(final DirectPosition point, double[] buffer) throws CannotEvaluateException;
> {code}
> However this method is inefficient if invoked for more than one point (which is a typical scenario). It may trig many readings of small areas, construct many times the same {{CoordinateOperation}}, _etc._ Furthermore it does not allow users to control the interpolatipn method.
> An alternative approach could be to define a separated {{Evaluator}} class with methods for setting the interpolation types among other. All coordinates to evaluate could be specified in advance, allowing {{Evaluator}} to perform only one larger read operation instead than many small operations.
> We may keep {{GridCoverage.evaluate}} as a convenience method when there is really only one point to evaluate. But we would need to clarify at least the policy regarding interpolation method.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)