Fabian Hofmann

@Ovewh for retrieving features from other sources one has to add the module to the cutout. But: The surface roughness is only used for extrapolating the wind speed to the...

> No, only a few models provide wind speed at 100m, most models provide only the surface wind speed. So the windspeed has to be extrapolated. Okay then the roughness...

Let's also have a look at https://py-cordex.readthedocs.io/en/stable/index.html

I agree, my preference would be to wait for a new `rasterio` release and add a minimum requirement.

Great. For the logging I would suggest to go with e.g. "2013-01", instead of "2013" only. See https://github.com/PyPSA/atlite/blob/3c7b4b8e4fc24f7cad2718abe7ead97d67f16550/atlite/datasets/era5.py#L309 which could be changed into ```python timestr = f"{request["year"])}-{request["month"]}" ``` and changed...

This is the current bounding box for all grid cells (default config) and the offshore area, it seems not right that some of the offshore area remains uncovered. However I...

After a small discussion with @euronion we agreed that it would be better to double check such configuration manners in a dedicated file. Such would be named `check_config.py` and would...

But the Voronoi cells are build on basis of the ENTSOE gridmap, i.e. their nodes. I think the problem remains the same, as the nodes of the ENTOSE maps have...

> * If the initial regions become too large `build_renewable_profiles` will likely get a performance hit because the rasters need to be chunked for calculating the renewable potentials. This should...

thanks for reporting @davide-f, since you seem to have dived into the code a bit, would you mind making a PR on this issue?