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

try split lidar and clipping #240

Merged
merged 10 commits into from
Jan 27, 2024

Conversation

rosepearson
Copy link
Owner

@rosepearson rosepearson commented Jan 26, 2024

In raw DEM stage split the LiDAR rasterisation and clipping of the raster stages to try reduce instances of 'large memory view errors':

  • Make code change
  • Update tests
    • Update / create new tests
    • Ensure these tests have the expected behavour
    • Test locally and ensure tests are passing
  • Ensure tests passing on GH Actions
  • Update documentation
    • Doc strings
    • Wiki
  • Update package (version.py & pyproject.toml) version (if needed)

@rosepearson rosepearson linked an issue Jan 26, 2024 that may be closed by this pull request
github-actions and others added 9 commits January 26, 2024 06:57
…d proerly during file caching. Also added code to support encoding/compressing the final output files - not yet turned on
…ithub.com:rosepearson/GeoFabrics into 239-dask-valueerror-memoryview-is-too-large-error
Merge branch '239-dask-valueerror-memoryview-is-too-large-error' of github.com:rosepearson/GeoFabrics into 239-dask-valueerror-memoryview-is-too-large-error
@rosepearson rosepearson merged commit 15af8ce into main Jan 27, 2024
2 checks passed
@rosepearson rosepearson deleted the 239-dask-valueerror-memoryview-is-too-large-error branch January 27, 2024 22:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Dask ValueError: memoryview is too large error
1 participant