Conversation
1a183a2 to
53202e2
Compare
53202e2 to
11b912a
Compare
| that can be either a virtual mosaic in the :ref:`Multidimensional VRT (Virtual Dataset) <vrt_multidimensional>` format, | ||
| or in a more conventional multidimensional format such as :ref:`raster.netcdf` or :ref:`raster.zarr`. | ||
|
|
||
| The array to mosaic in the input datasets must: |
There was a problem hiding this comment.
This line is unclear but I am not sure how to make it better.
There was a problem hiding this comment.
rephrased the whole paragraph as
To create a mosaic from an array, certain structural constraints apply to all
contributing arrays from the input datasets:
- All contributing arrays must have the same array name and path (e.g. "/measurements/pressure")
- They must have the same data type and nodata value
- They must share the same number of dimensions, in the same order, and with the same names.
- each dimension of the array must have an associated one-dimensional numeric indexing variable.
|
fwiw this is working nicely on my large use-case https://gist.github.com/mdsumner/94e6697d7896d11e19a6e0328d1f6ead |
dbaston
left a comment
There was a problem hiding this comment.
I recently needed to use the CDO collgrind command to mosaic spatially tiled netCDFs with multiple variables (lon/lat/elevation, lon/lat/ice_thickness, etc). Could mdim mosaic create a new mdim dataset with all of the variables, instead of a single one?
could indeed make sense to be able to specify one or several variable paths, and by default try all of them (with care regarding to avoid duplicating coordintate variables). Unlikely to be addressed in time for 3.12, so ticketed as #13218 |
Fixes #12953