DirkEilander

For the raster driver the variable name should also be updated based on the variables argument in `DataCatalog.get_rasterdataset`, see #883. This is important to make sure we can still read...

@hboisgon @JoostBuitink @verseve Do you remember what the status of using soilgrids_v2 in wflow is? If I remember correctly, @laurenebouaziz worked on this, but I think that because of this...

# More context - all methods that add information to a Model currently start with `setup_`, e.g. `setup_grid` creates the model grid and `setup_grid_from_raster` adds a new data layer by...

Good suggestion! And thanks for providing a catalog entry! Could you copy this dataset to p:\wflow_global\hydromt_staging\ ? Do you also happen to know how it compares to the PXR dataset...

In addition to @hboisgon. The placeholders are solved when parsing the data catalog, The path format arguments are checked in the resolve path and should be part of the new...

> So far I intend to place a generic solution with hydromt keywords year, month, variable, zoom_level, at the DataSource level. Drivers can then fill in any {{key}} themselves, as...

> One thing I think is definitely something we want is to make a distinction between the kinds of place holders since they need to be handled at different times....

I see your point @hboisgon. We now allow for a region to be shared by one or more components, But a component can only have one region. You want multiple...

Or, since `ModelRegionComponent.data` is a `GeoDataFrame` object. we could also add multiple geometries to it. With e.g., a `ModelRegionComponent.add_subregion` method we could add the mesh1d, rivers etc subgregions. The total...

> The one I care about is the `mesh1dregion` that I need to add new objects like bridges structures. And this `mesh1dregion` I cannot create from a region dict but...