xarray-grass 0.3.0

An Xarray backend for GRASS raster data.

xarray-grass

A GRASS backend for Xarray. Explore all your GRASS rasters with Xarray.

Installation

Install the package using uv or pip:

uv add xarray-grass

You need to install GRASS independently.

Loading GRASS data as an Xarray Dataset

>>> import xarray as xr
>>> test_ds = xr.open_dataset("/home/lc/grassdata/nc_spm_08_grass7/PERMANENT/", raster=["boundary_county_500m", "elevation"])
>>> test_ds
<xarray.Dataset> Size: 244kB
Dimensions:               (y: 150, x: 135)
Coordinates:
  * y                     (y) float32 600B 2.2e+05 2.2e+05 ... 2.207e+05
  * x                     (x) float32 540B 6.383e+05 6.383e+05 ... 6.39e+05
Data variables:
    boundary_county_500m  (y, x) float64 162kB ...
    elevation             (y, x) float32 81kB ...
Attributes:
    crs_wkt:   PROJCRS["NAD83(HARN) / North Carolina",BASEGEOGCRS["NAD83(HARN...

You can choose which maps you want to load with the raster, raster_3d, strds and str3ds parameters to open_dataset. Those accept either a single string or an iterable. If none of those are specified, the whole mapset will be loaded, ignoring single maps that are already registered in either a strds or str3ds; those maps will be loaded into the Xarray Dataset for being part of the GRASS Space Time Dataset. As of version 0.2.0, any time-stamp associated to a single map not registered in a stds is ignored.

The extent and resolution of the resulting Dataset is defined by the region setting of GRASS, set with the g.region GRASS tool. Note that in GRASS the 3D resolution is independent from the 2D resolution. Therefore, 2D and 3D maps loaded in Xarray will not share the same dimensions and coordinates. The coordinates in the Xarray Dataset correspond to the center of the GRASS cell.

If run from outside a GRASS session, xarray-grass will automatically create a session in the requested project and mapset. If run from within GRASS, only maps from accessible mapsets could be loaded. In GRASS, you can list the accessible mapsets with g.mapsets.

CF conventions attributes mapping

DataArray attributes

CF name	Origin in GRASS
long_name	The "title" field from "r.info", "r3.info", or "t.info"
source	Concatenation of "source1" and "source2" from "r.info" or "r3.info". In case of STDS, taken from the first map.
units	The "unit" field from "r.info" or "r3.info". In case of STDS, taken from the first map.
comment	The "comments" field from "r.info" or "r3.info". In case of STDS, taken from the first map.

The attributes of the coordinates are in line with CF Conventions.

Dataset attributes

The only attributes set at the dataset level are crs_wkt and Conventions.

Writing an Xarray Dataset or DataArray to GRASS

TODO.

Roadmap

Goals for version 1.0

• Load a single raster map
• Load a single Space-time Raster Dataset (strds)
• Load a single raster_3d map
• Load a single str3ds
• Load a combination of all the above
• Load a full mapset
• Support for the drop_variables parameter
• Write from xarray to GRASS
  • Write to a 2D raster
  • Write to STRDS
  • Write to 3D raster
  • Write to STR3DS
  • Honour the dims argument: transpose if dimensions are not in the expected order
  • Support time units for relative time
  • Support end_time
  • Accept writing into a specific mapset (GRASS 8.5)
  • Accept non homogeneous 3D resolution in NS and EW dimensions (GRASS 8.5)
• Lazy loading of all raster types
• Properly test with lat-lon location

Stretch goals

• Load all mapsets from a GRASS project (ex location)
• Read CRS definitions from CF compatible fields