DirkEilander

@roeldegoede Is the raster functionality `to_xyz_tiles` and `to_slippy_tiles` used in the FloodAdapt ecosystem to your knowledge? Otherwise we might as well remove these methods.

This sphinx-julia package could be something to look in to: https://bastikr.github.io/sphinx-julia/

We already tried to unify our internal representation of CRS a while back. Before we used by the rasterio and pyproj CRS objects interchangable, now internally all CRS objects are...

Suggested approach: create an `export_model_data` method to write selected model component to default "GIS compliant" files (e.g., gdal compliant netcdf, geotiff, geojson) with a datacatalog. Note that this method cannot...

@hboisgon it would be good to discuss if we want this in Q4. If so can you provide more context to this issue / refine it, potentially together with someone...

this is by design. rasterdatastes need a CRS otherwise a lot of functionality will fail down the line. We could however put a good error message in `_slice_spatial_dimensions` to guide...

I agree this has low priority. However it should also be rely straight forward to implement and I can image it can help to organize your data catalogs (if many)....

> noting this for the discussion when it becomes relevant: this will need a way to deal with conflicting information, especially if aliases will still be there. i.e. if Cat...

@B-Dalmijn I moved this back to the backlog. We should first decide on if and how we can solve this. I see you deleted my earlier suggestion. Would be good...

Another usecase is large rotated grids, for which constructing the 2D coordinates array requires huge memory usage. The solution mentioned above is however not in line with the current `.raster`...