Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Optimize Raster Reader Memory Usage for Hazard Module

Abierto
  • ¿Algo no está bien?
#1,262 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
python
Área
data

Línea de trabajo

Start with the HazardXarrayReader class and its get_hazard_kwargs() method, where the raster data is turned into centroid coordinates for the hazard module. The issue leaves open whether the new options should default to filtering out no-data and zero-intensity points, so settle that with the maintainers first. Done means that centroids are built only for the selected coordinates, with the options exposed on the reader and covered by tests.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

The current raster readers for the hazard module require building centroids for every point across the total extent of the raster. For high-resolution rasters, this leads to excessive memory requirements.

The construction requires building a Centroid grid for every point of the raster (even for no-data points)

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
(Add an option to?) Sub-select the dataset to coordinates which are not always NaN (also 0?)
This approach would save substantial RAM and computation time.

Specifically:

  1. add optional attributes to HazardXarrayReader (e.g. ignore_novalue_coords (default True) and ignore_zero_intensity_coords (default False)
  2. based on these attributes, sub-select the data in the get_hazard_kwargs() method, to generate Centroids only for the corresponding coordinates.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context

  • This is related to the refactoring of the centroids (GeoDataFrame)
  • This issue affects both read raster and potentially write raster methods? (a priori not)
Lenguaje dominante
Jupyter Notebook
Estrellas
478
Forks
166
Merge medio
2 d 31 min
PR fusionados (30 d)
4

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CLIMADA-project/climada_python

Todos los issues de CLIMADA-project/climada_python

Issues similares

Más issues de Data Engineering

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.