gridmet_raster2polygon

Raster to polygon aggregations of gridMET meteorological data. The spatial aggregation are performed for GridMET from grid/raster (NetCDF) to polygons (shp).

---

GridMET

gridMET combines high-resolution spatial climate data (e.g. temperature, precipitation, humidity) from PRISM with daily temporal attributes and additional meteorological variables from the regional reanalysis dataset NLDAS-2. The resulting product is a dataset of daily meteorological variables at ~4km x 4km resolution across the contiguous U.S.

---

Codebook

Dataset Columns:

• GEOID {string}: Geographic ID of aggregation level (U.S. County, ZCTA, or grid cell).
• year {int}: Dataset year.
• sph {float64}: Specific humidity (kg/kg), representing the mass of water vapor per unit mass of air.
• vpd {float64}: Vapor pressure deficit (hPa), which measures the difference between the amount of moisture in the air and how much moisture the air can hold when saturated.
• tmmn {float64}: Minimum daily temperature (Kelvin).
• tmmx {float64}: Maximum daily temperature (Kelvin).
• pr {float64}: Precipitation (mm), total daily precipitation.
• rmin {float64}: Minimum relative humidity (%), the lowest daily relative humidity recorded.
• rmax {float64}: Maximum relative humidity (%), the highest daily relative humidity recorded.
• srad {float64}: Downward shortwave solar radiation (W/m²), measuring the solar energy received at the surface.
• vs {float64}: Wind speed at 10 meters (m/s), representing the average daily wind speed at 10 meters above ground level.
• th {float64}: Wind direction at 10 meters (degrees from north), indicating the direction from which the wind is blowing.

Run

Conda environment

Clone the repository and create a conda environment.

git clone <https://github.com/<user>/repo>
cd <repo>

conda env create -f requirements.yml
conda activate <env_name> #environment name as found in requirements.yml

It is also possible to use mamba.

mamba env create -f requirements.yml
mamba activate <env_name>

Input and output paths

Determine the configuration file to be used in cfg.datapaths. The input, intermediate, and output arguments are used in utils/create_dir_paths.py to fix the paths or directories from which a step in the pipeline reads/writes its input/output data inside the corresponding /data subfolders.

If cfg.datapaths points to <input_path> or <output_path>, then utils/create_dir_paths.py will automatically create a symlink as in the following example:

export HOME_DIR=$(pwd)

cd $HOME_DIR/data/input/ .
ln -s <input_path> . 

cd $HOME_DIR/data/output/
ln -s <output_path> . 

Using custom shapefiles

It is also possible to run this script to aggregate based on your own custom shapefile. In order to do this, follow the following steps:

1. Create a conf/datapaths/{shapefile_name}.yaml that contains the locations of input, intermediate, and output files. An example is given with county_cannon.yaml.
2. Create a conf/shapefiles/{shapefiles_name}.yaml with important metadata for your shapefile. The following metadata is required:
   • years: Available shapefile years (list)
   • idvar: ID column name
   • shapefile_prefix: Base naming format
3. Modify the datapaths and shapefile entries in conf/config.yaml to match these new config files. For example:

    defaults:
    - _self_
    - datapaths: grid4x4_cannon
    - gridmet
    - shapefiles: grid_4x4km 

NB: this pipeline expects shapefiles to be stored in paths of the form {shapefile_prefix}_{shapefile_year}/{shapefile_prefix}_{shapefile_year}.shp

Pipeline

You can run the snakemake pipeline described in the Snakefile.

run snakemake pipeline or run the pipeline:

export PYTHONPATH="."
snakemake --cores 4 

Dockerized Pipeline

Create the folder where you would like to store the output dataset.

mkdir <path>

Pull and Run:

docker pull nsaph/gridmet_raster2polygon
docker run -v <path>:/app/data/ nsaph/gridmet_raster2polygon

If you want to build your own image use from the Dockerfile int the GitHub repository.

docker build -t <image_name> .