ARM Logo

Py-ART Gridding


Overview

Within this notebook, we will cover:

  1. What is gridding and why is it important?

  2. An overview of gridding with Py-ART

  3. Test out a different gridding routine

  4. Apply Gridding to a Selection of Files

Prerequisites

Concepts

Importance

Notes

Py-ART Basics

Helpful

Basic features

Intro to Cartopy

Helpful

Basic features

Matplotlib Basics

Helpful

Basic plotting

NumPy Basics

Helpful

Basic arrays

  • Time to learn: 15 minutes


Imports

import os
from pathlib import Path
import glob
import warnings

import cartopy.crs as ccrs
import matplotlib.pyplot as plt


import pyart
import xarray as xr

warnings.filterwarnings('ignore')
## You are using the Python ARM Radar Toolkit (Py-ART), an open source
## library for working with weather radar data. Py-ART is partly
## supported by the U.S. Department of Energy as part of the Atmospheric
## Radiation Measurement (ARM) Climate Research Facility, an Office of
## Science user facility.
##
## If you use this software to prepare a publication, please cite:
##
##     JJ Helmus and SM Collis, JORS 2016, doi: 10.5334/jors.119

What is gridding and why is it important?

Antenna vs. Cartesian Coordinates

Radar data, by default, is stored in a polar (or antenna) coordinate system, with the data coordinates stored as an angle (ranging from 0 to 360 degrees with 0 == North), and a radius from the radar, and an elevation which is the angle between the ground and the ground.

This format can be challenging to plot, since it is scan/radar specific. Also, it can make comparing with model data, which is on a lat/lon grid, challenging since one would need to transform the model daa cartesian coordinates to polar/antenna coordiantes.

Fortunately, PyART has a variety of gridding routines, which can be used to grid your data to a Cartesian grid. Once it is in this new grid, one can easily slice/dice the dataset, and compare to other data sources.

Why is Gridding Important?

Gridding is essential to combining multiple data sources (ex. multiple radars), and comparing to other data sources (ex. model data). There are also decisions that are made during the gridding process that have a large impact on the regridded data - for example:

  • What resolution should my grid be?

  • Which interpolation routine should I use?

  • How smooth should my interpolated data be?

While there is not always a right or wrong answer, it is important to understand the options available, and document which routine you used with your data! Also - experiment with different options and choose the best for your use case!

An overview of gridding with Py-ART

Let’s dig into the regridding process with PyART!

Read in and Visualize a Test Dataset

Let’s start with the same file used in the previous notebook (PyART Basics), which is a radar file from Northern Oklahoma.

file = "../data/cacti/radar/corcsapr2cmacppiM1.c1.20190125.200003.nc"
radar = pyart.io.read(file)

Let’s plot up quick look of reflectivity, at the lowest elevation scan (closest to the ground)

fig = plt.figure(figsize=[8, 6])
display = pyart.graph.RadarDisplay(radar)
display.plot_ppi('attenuation_corrected_reflectivity_h',
                 cmap='pyart_HomeyerRainbow')
../../_images/9e73f2c52d98ce7c82804e37c312cbf2144fddba7ba4aa875b49c60d1f58aed0.png

As mentioned before, the dataset is currently in the antenna coordinate system measured as distance from the radar

Setup our Gridding Routine with pyart.map.grid_from_radars()

Py-ART has the Grid object which has characteristics similar to that of the Radar object, except that the data are stored in Cartesian coordinates instead of the radar’s antenna coordinates.

pyart.core.Grid?
Init signature:
pyart.core.Grid(
    time,
    fields,
    metadata,
    origin_latitude,
    origin_longitude,
    origin_altitude,
    x,
    y,
    z,
    projection=None,
    radar_latitude=None,
    radar_longitude=None,
    radar_altitude=None,
    radar_time=None,
    radar_name=None,
)
Docstring:     
A class for storing rectilinear gridded radar data in Cartesian coordinate.

Refer to the attribute section for information on the parameters.

To create a Grid object using legacy parameters present in Py-ART version
1.5 and before, use :py:func:`from_legacy_parameters`,
grid = Grid.from_legacy_parameters(fields, axes, metadata).

Attributes
----------
time : dict
    Time of the grid.
fields : dict of dicts
    Moments from radars or other variables.
metadata : dict
    Metadata describing the grid.
origin_longitude, origin_latitude, origin_altitude : dict
    Geographic coordinate of the origin of the grid.
x, y, z : dict, 1D
    Distance from the grid origin for each Cartesian coordinate axis in a
    one dimensional array. Defines the spacing along the three grid axes
    which is repeated throughout the grid, making a rectilinear grid.
nx, ny, nz : int
    Number of grid points along the given Cartesian dimension.
projection : dic or str
    Projection parameters defining the map projection used to transform
    from Cartesian to geographic coordinates. None will use the default
    dictionary with the 'proj' key set to 'pyart_aeqd' indicating that
    the native Py-ART azimuthal equidistant projection is used. Other
    values should specify a valid pyproj.Proj projparams dictionary or
    string. The special key '_include_lon_0_lat_0' is removed when
    interpreting this dictionary. If this key is present and set to True,
    which is required when proj='pyart_aeqd', then the radar longitude and
    latitude will be added to the dictionary as 'lon_0' and 'lat_0'.
    Use the :py:func:`get_projparams` method to retrieve a copy of this
    attribute dictionary with this special key evaluated.
radar_longitude, radar_latitude, radar_altitude : dict or None, optional
    Geographic location of the radars which make up the grid.
radar_time : dict or None, optional
    Start of collection for the radar which make up the grid.
radar_name : dict or None, optional
    Names of the radars which make up the grid.
nradar : int
    Number of radars whose data was used to make the grid.
projection_proj : Proj
    pyproj.Proj instance for the projection specified by the projection
    attribute. If the 'pyart_aeqd' projection is specified accessing this
    attribute will raise a ValueError.
point_x, point_y, point_z : LazyLoadDict
    The Cartesian locations of all grid points from the origin in the
    three Cartesian coordinates. The three dimensional data arrays
    contained these attributes are calculated from the x, y, and z
    attributes. If these attributes are changed use :py:func:
    `init_point_x_y_z` to reset the attributes.
point_longitude, point_latitude : LazyLoadDict
    Geographic location of each grid point. The projection parameter(s)
    defined in the `projection` attribute are used to perform an inverse
    map projection from the Cartesian grid point locations relative to
    the grid origin. If these attributes are changed use
    :py:func:`init_point_longitude_latitude` to reset the attributes.
point_altitude : LazyLoadDict
    The altitude of each grid point as calculated from the altitude of the
    grid origin and the Cartesian z location of each grid point.  If this
    attribute is changed use :py:func:`init_point_altitude` to reset the
    attribute.
Init docstring: Initalize object.
File:           ~/mambaforge/envs/arm-summer-school-2024-dev/lib/python3.11/site-packages/pyart/core/grid.py
Type:           type
Subclasses:     

We can transform our data into this grid object, from the radars, using pyart.map.grid_from_radars().

Beforing gridding our data, we need to make a decision about the desired grid resolution and extent. For example, one might imagine a grid configuration of:

  • Grid extent/limits

    • 20 km in the x-direction (north/south)

    • 20 km in the y-direction (west/east)

    • 15 km in the z-direction (vertical)

  • 500 m spatial resolution

The pyart.map.grid_from_radars() function takes the grid shape and grid limits as input, with the order (z, y, x).

Let’s setup our configuration, setting our grid extent first, with the distance measured in meters

z_grid_limits = (0.,20_000.)
y_grid_limits = (-150_000.,150_000.)
x_grid_limits = (-150_000.,150_000.)

Now that we have our grid limits, we can set our desired resolution (again, in meters)

grid_resolution = 500

Let’s compute our grid shape - using the extent and resolution to compute the number of grid points in each direction.

def compute_number_of_points(extent, resolution):
    return int((extent[1] - extent[0])/resolution) + 1

Now that we have a helper function to compute this, let’s apply it to our vertical dimension

z_grid_points = compute_number_of_points(z_grid_limits, grid_resolution)
z_grid_points
41

We can apply this to the horizontal (x, y) dimensions as well.

x_grid_points = compute_number_of_points(x_grid_limits, grid_resolution)
y_grid_points = compute_number_of_points(y_grid_limits, grid_resolution)

print(z_grid_points,
      y_grid_points,
      x_grid_points)
41 601 601

Use our configuration to grid the data!

Now that we have the grid shape and grid limits, let’s grid up our radar!

grid = pyart.map.grid_from_radars(radar,
                                  grid_shape=(z_grid_points,
                                              y_grid_points,
                                              x_grid_points),
                                  grid_limits=(z_grid_limits,
                                               y_grid_limits,
                                               x_grid_limits),
                                  gridding_algo='map_gates_to_grid',
                                  min_radius=200.
                                 )
grid
<pyart.core.grid.Grid at 0x307a47b50>

We now have a pyart.core.Grid object!

Plot up the Grid Object

Plot a horizontal view of the data

We can use the GridMapDisplay from pyart.graph to visualize our regridded data, starting with a horizontal view (slice along a single vertical level)

display = pyart.graph.GridMapDisplay(grid)
display.plot_grid('attenuation_corrected_reflectivity_h',
                  level=2,
                  vmin=-20,
                  vmax=60,
                  cmap='pyart_HomeyerRainbow')
../../_images/61fda3f5102da5901e7f629e3ab088b762fff00ace345910633c6115a14469db.png

Plot a Latitudinal Slice

We can also slice through a single latitude or longitude!

display.plot_latitude_slice('attenuation_corrected_reflectivity_h',
                            lat=-31.8,
                            vmin=-20,
                            vmax=80,
                            cmap='pyart_HomeyerRainbow')
plt.xlim([0, 40]);
../../_images/f0125a204825726bfb36a3ce1420c0767ae44893cf54fa8b8bbc55467a2c9445.png

Plot with Xarray

Another neat feature of the Grid object is that we can transform it to an xarray.Dataset!

ds = grid.to_xarray()
ds
<xarray.Dataset> Size: 184MB
Dimensions:                               (time: 1, z: 41, y: 601, x: 601)
Coordinates:
  * time                                  (time) object 8B 2019-01-25 20:00:03
  * z                                     (z) float64 328B 0.0 500.0 ... 2e+04
    lat                                   (y, x) float64 3MB -33.47 ... -30.77
    lon                                   (y, x) float64 3MB -66.35 ... -63.16
  * y                                     (y) float64 5kB -1.5e+05 ... 1.5e+05
  * x                                     (x) float64 5kB -1.5e+05 ... 1.5e+05
Data variables:
    corrected_velocity                    (time, z, y, x) float32 59MB nan .....
    attenuation_corrected_reflectivity_h  (time, z, y, x) float32 59MB nan .....
    ROI                                   (time, z, y, x) float32 59MB 3.703e...

Now, our plotting routine is a one-liner, starting with the horizontal slice:

ds.isel(z=2).attenuation_corrected_reflectivity_h.plot(cmap='pyart_HomeyerRainbow',
                                                       vmin=-20,
                                                       vmax=80);
../../_images/6574d78a531313de9e86328d6c79d2e0d299b880bf2c22e06b4d3bbd70074e3e.png

And a vertical slice at a given y dimension (latitude)

ds.sel(y=40_000,
       method='nearest').attenuation_corrected_reflectivity_h.plot(cmap='pyart_HomeyerRainbow',
                                           vmin=-20,
                                           vmax=80);
plt.xlim(0, 50_000)
(0.0, 50000.0)
../../_images/6c40b77977bc0a4637cd28dceb34dd247dd7a9fc9fa37b56be15ba9a3b639604.png

Try a Different Gridding Technique

nearest_grid = pyart.map.grid_from_radars(radar,
                                  grid_shape=(z_grid_points,
                                              y_grid_points,
                                              x_grid_points),
                                  grid_limits=(z_grid_limits,
                                               y_grid_limits,
                                               x_grid_limits),
                                  weighting_function='Nearest',
                                  min_radius=200.
                                 )
display.plot_latitude_slice('attenuation_corrected_reflectivity_h',
                            lat=-31.8,
                            vmin=-20,
                            vmax=80,
                            cmap='pyart_HomeyerRainbow')
plt.xlim([0, 40]);
../../_images/f0125a204825726bfb36a3ce1420c0767ae44893cf54fa8b8bbc55467a2c9445.png
display = pyart.graph.GridMapDisplay(nearest_grid)
display.plot_latitude_slice('attenuation_corrected_reflectivity_h',
                            lat=-31.8,
                            vmin=-20,
                            vmax=80,
                            cmap='pyart_HomeyerRainbow')
plt.xlim([0, 40]);
../../_images/44fdea3cbf8ccc8cd953ac369798bb2c9462d3db3b8ead2bf82e2de3c5e5770d.png

Summary

Within this notebook, we covered the basics of gridding radar data using pyart, including:

  • What we mean by gridding and why is it matters

  • Configuring your gridding routine

  • Visualize gridded radar data

What’s Next

In the next few notebooks, we walk through applying data cleaning methods, and advanced visualization methods!

Resources and References

Py-ART essentials links: