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

Vary relationship between requested raster CellSize and PDAL pipeline resolution #65

Open
2 tasks
echeipesh opened this issue Mar 31, 2020 · 0 comments
Open
2 tasks

Comments

@echeipesh
Copy link
Collaborator

Currently the DEMRasterSource translated the requested cell size is translated directly to PDAL pipeline resolution:

val expression = ReadEpt(
filename = path.value,
resolution = gridExtent.cellSize.resolution.some,
bounds = s"([$exmin, $eymin], [$exmax, $eymax])".some,
threads = threads
) ~ FilterDelaunay()

We have observed that response latency is very sensitive to the query resolution: https://github.com/geotrellis/geotrellis-pointcloud/tree/master/benchmark

Because DEMRasterSource performs a Delaunay it can be expected to produce a sufficiently good result with sparser input and consequently in less time.

This issue is to take first steps:

  • provide a fixed ratio between request and query resolution
  • test and record the resulting performance and behavior

Note: This parameter should probably be parsed from the URI used to construct the DEMRasterSource so it can be easily threaded through.

Future work can incorporate more sophisticated logic for pipeline resolution selection based on the EPT metadata as mentioned in #62

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

No branches or pull requests

2 participants