You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could first restrict .proj.merge_crs("coord_name") to checking that all CRS indexes found in the dataset are equal and if yes merge all CRS coordinates into one (with the name given as argument). Later on we could expand the functionality with optional arguments (e.g., trigger re-projection).
The text was updated successfully, but these errors were encountered:
A useful feature (regardless of the single vs. multi CRS model discussed in #2) would be to merge all the CRSs found in a dataset or dataarray.
Let's take the example below where two datasets differ only by the name of the CRS-indexed coordinate:
Merging these two datasets with
xarray.merge()
will keep both CRS coordinates:Getting the unique CRS from the merged dataset won't work despite all CRS are the same:
For convenience we could provide a
proj.merge_crs()
method such that:We could first restrict
.proj.merge_crs("coord_name")
to checking that all CRS indexes found in the dataset are equal and if yes merge all CRS coordinates into one (with the name given as argument). Later on we could expand the functionality with optional arguments (e.g., trigger re-projection).The text was updated successfully, but these errors were encountered: