Gridded Datasets I ¶
GeoViews is designed to make full use of multidimensional gridded datasets stored in netCDF or other common formats, via the xarray and iris interfaces in HoloViews. This notebook will demonstrate how to load data using both of these data backends, along with some of their individual quirks. The data used in this notebook was originally shipped as part of the
repository, but a smaller netCDF file is included as part of the GeoViews so that it can be used with xarray as well.
import iris import numpy as np import xarray as xr import holoviews as hv import geoviews as gv import geoviews.feature as gf from cartopy import crs from geoviews import opts gv.extension('matplotlib') gv.output(size=150)
In this notebook we will primarily be working with xarray, but we will also load the same data using iris so that we can demonstrate that the two data backends are nearly equivalent.
As a first step we simply load the data using the
method xarray provides and have a look at the repr to get an overview what is in this dataset:
xr_ensemble = xr.open_dataset('../data/ensemble.nc').load() xr_ensemble
<xarray.Dataset> Dimensions: (bnds: 2, latitude: 145, longitude: 192, time: 6) Coordinates: * time (time) datetime64[ns] 2011-08-16T12:00:00 ... 2012-01-16T12:00:00 * latitude (latitude) float32 -90.0 -88.75 ... 88.75 90.0 * longitude (longitude) float32 0.0 1.875 ... 356.25 358.125 forecast_period (time) timedelta64[ns] 29 days 12:00:00 ... 182 days 12:00:00 forecast_reference_time datetime64[ns] 2011-07-18 Dimensions without coordinates: bnds Data variables: surface_temperature (time, latitude, longitude) float32 214.0061 ... 245.59375 latitude_longitude int32 -2147483647 time_bnds (time, bnds) float64 3.645e+05 ... 3.689e+05 forecast_period_bnds (time, bnds) float64 336.0 1.08e+03 ... 4.752e+03 Attributes: source: Data from Met Office Unified Model um_version: 7.6 Conventions: CF-1.5
Similarly we can load the same dataset using Iris'
function and get a similar overview using the
iris.FUTURE.netcdf_promote=True iris_ensemble = iris.load_cube('../data/ensemble.nc') print(iris_ensemble.summary())
surface_temperature / (K) (time: 6; latitude: 145; longitude: 192) Dimension coordinates: time x - - latitude - x - longitude - - x Auxiliary coordinates: forecast_period x - - Scalar coordinates: forecast_reference_time: 2011-07-18 00:00:00 Attributes: Conventions: CF-1.5 STASH: m01s00i024 source: Data from Met Office Unified Model um_version: 7.6 Cell methods: mean: time (1 hour)
Describing the differences between these two libraries is well beyond the scope of this tutorial, but you can see from the summaries that the two libraries deal differently with both the bounds and with the actual data variables. Iris cubes support only a single data variable, while an xarray dataset can have any number of variables. In this case we are only interested in the
dimension, indexed by
We can easily express this interest by wrapping the data in a GeoViews
Element and declaring the key dimensions (
) and value dimensions (
). Note that the Iris interface is much smarter in the way it extracts the dimensions, so usually you will not have to supply them explicitly.
kdims = ['time', 'longitude', 'latitude'] vdims = ['surface_temperature'] xr_dataset = gv.Dataset(xr_ensemble, kdims=kdims, vdims=vdims) iris_dataset = gv.Dataset(iris_ensemble, kdims=kdims, vdims=vdims)
Now we can compare the repr of the two Elements:
:Dataset [time,longitude,latitude] (surface_temperature) :Dataset [time,longitude,latitude] (surface_temperature)
Despite appearing identical, there are some internal differences, such as in the data types. xarray uses NumPy datetime64 types for dates, while iris will use simple floats:
print("XArray time type: %s" % xr_dataset.get_dimension_type('time')) print("Iris time type: %s" % iris_dataset.get_dimension_type('time'))
XArray time type: <class 'numpy.datetime64'> Iris time type: <class 'numpy.float64'>
To improve the formatting of dates on the xarray dataset we can set the formatter for datetime64 types:
hv.Dimension.type_formatters[np.datetime64] = '%Y-%m-%d'
The other major differences in the way iris cubes are handled are in deducing various bits of metadata including the coordinate system, units, and formatters. Otherwise the two Dataset Elements will behave largely the same.
For either data backend, the
object is not yet visualizable, because we have not chosen which dimensions to map onto which axes of a plot.
A Simple example ¶
To visualize the datasets, in a single line of code we can specify that we want to view it as a collection of Images indexed by longitude and latitude (a HoloViews
xr_dataset.to(gv.Image, ['longitude', 'latitude'])
You can see that the
dimension was automatically mapped to a slider, because we did not map it onto one of the other available dimensions (x, y, or color, in this case). You can drag the slider to view the surface temperature at different times. The example would work just the same for the
Now let us load a cube showing the pre-industrial air temperature:
pre_industrial = xr.open_dataset('../data/pre-industrial.nc').load() air_temperature = gv.Dataset(pre_industrial, ['longitude', 'latitude'], 'air_temperature') air_temperature
:Dataset [longitude,latitude] (air_temperature)
Note that we have the
dimensions. As a result, this cube is a single frame (at right below) when visualized as an
The following more complicated example shows how complex interactive plots can be generated with relatively little code, and also demonstrates how different HoloViews elements can be combined together. In the following visualization, the black dot denotes a specific longitude, latitude location
, and the curve is a sample of the
at that location. The curve is unaffected by the
slider because it already lays out time along the x axis:
temp_curve = hv.Curve(xr_dataset.select(longitude=0, latitude=10), kdims=['time']) temp_map = xr_dataset.to(gv.Image,['longitude', 'latitude']) * gv.Points([(0,10)]) (temp_map + temp_curve).opts( opts.Curve(aspect=2, xticks=4, xrotation=15), opts.Points(color='k', global_extent=True))
Let's view the surface temperatures together with the global coastline:
(xr_dataset.to.image(['longitude', 'latitude']) * gf.coastline).opts( opts.Image(projection=crs.Geostationary(), cmap='Greens', xaxis=None, yaxis=None))
Notice that every frame individually uses the full dynamic range of the Greens color map. This is because normalization is set to
at the top of the notebook, which means every frame is normalized independently. This sort of normalization can be computed on an as-needed basis, using whatever values are found in the current data being shown in a given frame, but it won't let you see how different frames compare to each other.
To control normalization, we need to decide on the normalization limits. Let's see the maximum temperature in the cube, and use it to set a normalization range by using the redim method:
max_surface_temp = xr_dataset.range('surface_temperature') print(max_surface_temp) srfc_temps = xr_dataset.redim.range(surface_temperature=(300, max_surface_temp)).to(gv.Image,['longitude', 'latitude']) (srfc_temps * gf.coastline).opts( opts.Image(projection=crs.Geostationary(), cmap='Greens', xaxis=None, yaxis=None))
By specifying the normalization range we can reveal different aspects of the data. In the example above we can see a cooling effect over time as the dark green areas close to the top of the normalization range (317K) vanish. Values outside this range are clipped to the ends of the color map.
Lastly, here is a demo of a conversion from
xr_dataset.to(gv.FilledContours,['longitude', 'latitude']) * gf.coastline
As you can see, it's quite simple to expose any data you like from your Iris cube or xarray, easily and flexibly creating interactive or static visualizations.