Huite
Huite
Hans and Jan had run into a case where the leaky line doublet seemed to give different answers compared to MWELL and a checking model MODFLOW model. I tried to...
Github seems to have stopped rendering the readme nicely. If I recall correctly, I changed it to restructured text because markdown wasn't rendering nicely on pypi before. But pypi seems...
The UGRID conventions describe the `bounds` coordinates. This is somewhat of a hassle to set now: ```python ds = uds.ugrid.to_dataset() grid = uds.ugrid.grid bounds = grid.face_node_coordinates x_bounds = bounds[..., 0]...
The current `burn_vector_geometry` relies on calling earcut to break a polygon down into a triangular mesh, which is then checked for overlap. I don't necessarily see a better way for...
Holoviews and Datashader supports TriMesh/trimesh (resp.): https://datashader.org/user_guide/Trimesh.html This is obviously useful, especially for larger grids. Althought not every 2D grid is triangular, it can be easily triangulated (which is done...
As raised in #200: selection by polygon seems like a common operation, and it should be easily doable. Currently, it requires burning the polygon into the topology followed by a...
Topology objects are currently propagated through operations. This is desirable, since their size can be relatively large, and we would be copying quite a lot of data potentially. However, it...
After discussion with @JoerivanEngelen: To translate data from networks, e.g. the water level output or bed level from 1D hydraulic simulations, to gridded (MODFLOW) input, we need some tooling that's...
There are multiple ways to represent these (grid_mapping, etc, see also OGC conventions). Since the Ugrid topologies contain these, would be nice to use these if possible.
Xugrid has, so far, mostly focused on projected coordinate systems (y, x). It will also read lat-lon data, but: * Computing areas will go awry * The overlap regridding also...