Issue #1775 improve target grid

[JoerivanEngelen]

Fixes #1775

Description

Add option to regrid to target_grid and default to iMOD5 target grid if not provided.

• Add option to specify target_grid upon importing, this saves unnecessary regridding for iMOD5 databases with inconsistent grids
• When no target_grid is provided, choose the first BND grid, like iMOD5 did. Instead of trying to estimate the grid with the smallest extent and finest resolution from the TOP, BOT, BND. This could result in very poor performance when iMOD5 databases had grids for TOP or BOT on a very fine resolution.
• Remove smallest targest grid utility

Checklist

• Links to correct issue
• Update changelog, if changes affect users
• PR title starts with Issue #nr, e.g. Issue #737
• Unit tests were added
• If feature added: Added/extended example
• If feature added: Added feature to API documentation
• If pixi.lock was changed: Ran pixi run generate-sbom and committed changes

[Manangka]

Can you elaborate? What is different about this? When do you use it?

[JoerivanEngelen]

I have elaborated further on this and linked to the user guide on allocation of topsystems.

[Manangka]

In the description you say "iMOD5 databases with inconsistent grids". What are inconsistent grids and are those kind of grids common?

[JoerivanEngelen]

In the description you say "iMOD5 databases with inconsistent grids". What are inconsistent grids and are those kind of grids common?

Good question, pardon my vagueness: iMOD5 only supports structured grids, but in an iMOD5 database, the grid for hydraulic conductivity can be on a 100m resolution, whereas the grid for a bottom in a database can be 25 m. iMOD5 (and iMOD Python when calling from_imod5_data) rescales all these parameters to one consistent model grid behind-the-scenes.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud