hboisgon
hboisgon
@xldeltares thanks for posting the issue! I edited to add more context to it.
Hi @Jaapel I guess that could work but I don't know enough about it so here are some questions I have: - Is the `NoDataStrategy` global for the whole model...
> > ``` > > * Is the `NoDataStrategy` global for the whole model building or can you set it for each data that you are trying to read? >...
Should be done on main before the next release
In #534 the changes were first implemented by maybe the names should be discussed with users before changing for good to find which names would be more explicit.
Let me try to answer: ``placeholder`` is really different from the others because it helps to define multiple data sources (from the same dataset) that have exactly the same reading...
I was wondering the same if we could replace ``placeholder`` with ``variants``. Maybe worth exploring in a new issue (for v1)? If we do it well, data catalogs would be...
Well let's take again Delft3D 1D2D model. Right now we have one big ``mesh`` object containing 1D and 2D meshes and the ``region`` is derived dynamically from ``mesh.total_bounds``. I guess...
So I don't really care about the subregions for ``rivers`` and ``pipes`` if the ``region.create`` methods becomes a workflow function that can be called without creating a ``ModelRegionComponent``. The one...
I think your suggestion could work @deltamarnix. Compared to now, the user still needs to manually add ``mesh1dregion.create`` in the yml steps which was not necessary before. I think we...