Define a max area for AOI and/or limits on output grid dimensions · Issue #16 · uw-cryo/lidar_tools · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most people will submit a small site polygon, and we can provide examples with expected runtimes.
But inevitably, someone will try to run with a huge polygon - say all of CONUS, or Washington state. We should probably check for this, warn, and potentially require confirmation.
Similar question about output grid dimensions - what if they want all of CONUS and 0.01 m grid cells? :)
The text was updated successfully, but these errors were encountered:
100% I will be running some memory usage profiling test for parallelization component, and will also use that exercise to caution users about specific memory requirements based on size of point cloud data and output DEM GSD.
Most people will submit a small site polygon, and we can provide examples with expected runtimes.
But inevitably, someone will try to run with a huge polygon - say all of CONUS, or Washington state. We should probably check for this, warn, and potentially require confirmation.
Similar question about output grid dimensions - what if they want all of CONUS and 0.01 m grid cells? :)
The text was updated successfully, but these errors were encountered: