The open_projectfile_data creates separate CHD packages per layer.
The context for this is that iMOD5 supports specifying multiple systems for a single package. This means you can specify multiple river stages and conductances to a single cell, which is useful for example in Dutch polder systems, where there are a lot of small surface water networks set to different stages in a single model cell. The projectfile doesn't have a way to discern which layer data belongs to which system for boundary condition entries. It is hard to figure out programmatically which layers form 1 system. Users do this by manually inspecting the paths to their IDFs which they hopefully provided with a good naming. As there is no strict naming convention for these systems in the paths, we should make separate packages for each layer. Users can manually merge systems together in a script if they want to.
The CHD package, however, is an exception, as it sets heads directly in the groundwater model (so a Dirichlet instead of Robin boundary condition). This means it doesn't make sense to specify multiple heads in a single cell, rendering separate CHD systems useless. We can therefore safely assume that the different CHD entries are different layers in a single system, and combine them into one single CHD package.
The
open_projectfile_datacreates separate CHD packages per layer.The context for this is that iMOD5 supports specifying multiple systems for a single package. This means you can specify multiple river stages and conductances to a single cell, which is useful for example in Dutch polder systems, where there are a lot of small surface water networks set to different stages in a single model cell. The projectfile doesn't have a way to discern which layer data belongs to which system for boundary condition entries. It is hard to figure out programmatically which layers form 1 system. Users do this by manually inspecting the paths to their IDFs which they hopefully provided with a good naming. As there is no strict naming convention for these systems in the paths, we should make separate packages for each layer. Users can manually merge systems together in a script if they want to.
The CHD package, however, is an exception, as it sets heads directly in the groundwater model (so a Dirichlet instead of Robin boundary condition). This means it doesn't make sense to specify multiple heads in a single cell, rendering separate CHD systems useless. We can therefore safely assume that the different CHD entries are different layers in a single system, and combine them into one single CHD package.