Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make use of an OverviewStrategy in the DEMRasterSources implementation #62

Closed
pomadchin opened this issue Mar 26, 2020 · 1 comment · Fixed by #79
Closed

Make use of an OverviewStrategy in the DEMRasterSources implementation #62

pomadchin opened this issue Mar 26, 2020 · 1 comment · Fixed by #79
Assignees

Comments

@pomadchin
Copy link
Member

pomadchin commented Mar 26, 2020

At this point DEMRasterSources don't use OverviewStrategy and rely only on the PDAL EPTReader capabilities https://github.com/PDAL/PDAL/blob/2.1.0/io/EptReader.cpp#L293-L318.

This task is to improve control over it to improve real time performance.

The core use case is to be able to select the actual resolution we're querying from the EPT tree.

  • Use OverviewStrategy to select the PDAL resolution
  • Treat the RasterSource cellSize as request into GT OverviewStrategy given resolutions computed from metadata
  • Use returned resolution as query parameter to PDAL Pipeline

Requires: #69

@echeipesh
Copy link
Collaborator

Change in EPTRasterSourceProvider

Use case:
We get a WCS request is for 30x30m resolution, we want to query the EPT through PDAL pipeline at at 60x60m resolution:

ept://path/to/catalog?overviewStrategy=auto-2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants