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.

Sign up for GitHub

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

Jump to bottom

Rationalise rasterize usages #191

Open
remi-braun opened this issue Dec 11, 2024 · 0 comments
Open

Rationalise rasterize usages #191

remi-braun opened this issue Dec 11, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@remi-braun
Copy link
Member

For now, multiple rasterize function are coexisting:

  • rasterio.features.rasterize: Low-level not dask-compatible
  • rasters_rio.rasterize: Higher-level but dependent of rasterio, therefore not dask-compatible
  • rasters.rasterize: Higher-level and dask-compatible in a near future
  • Product defined _rasterize: Is it useful? Or at least abstract it at the Product level (using rasters.rasterize)

Convert all of these functions to the latest.
@remi-braun remi-braun added the enhancement New feature or request label Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@remi-braun