Skip to content

README.md

Latest commit

 

History

History
89 lines (64 loc) · 4.04 KB

README.md

File metadata and controls

89 lines (64 loc) · 4.04 KB
Raw

nr-wrf

Air quality dispersion data publication app

Overview

This application provides air quality dispersion data through two separate search interfaces:

CALPUF Search (index.html)

  • Domain File: Uses domaininfo_bcwrf.csv which contains grid coordinates mapping I, J values to LAT, LONG positions
    • Format: I,J,LAT,LON (e.g., 2,2,46.4292,-137.674)
    • Grid dimensions: MAX_I = 476, MAX_J = 425
  • Object Store: Files are fetched from https://nrs.objectstore.gov.bc.ca/kadkvt/
  • Search Functionality:
    • Users can search by drawing rectangles on a map or entering coordinates and date ranges
    • The application converts lat/long selections to I/J grid coordinates
    • Constructs URLs to fetch 10x10km tile files from object storage based on year, month, and grid position
    • File format: x{I1}y{J1}x{I2}y{J2}.{YYYY}{MM}.10x10.m3d.7z
  • Output: Packages selected files into a nr-wrf.zip file with processing utilities (7z.exe, m3d_bild.exe, start.bat, readme.txt, and generated config file)

AERMOD Search (aermod.html)

  • Domain File: Uses tile-based domain information accessed via backend API (/mapping/findClosestPoint)
  • Object Store: Files are fetched from https://nrs.objectstore.gov.bc.ca/qfncae/support_files/
  • Search Functionality:
    • Users search by clicking on the map or entering specific lat/long coordinates with date ranges
    • The backend finds the closest I, J grid point and tile ID for the selected coordinates
    • Fetches files from object storage based on the tile information and date range
  • Output: Packages selected files into a nr-wrf_aermod.zip file with processing utilities (start.bat, readme.txt, mmif.inp)

Both search screens use the mapping service (geomapping.js and geomapping_aermod.js) to construct object store URLs, which are then processed by the backend zip-file service to package all searched files into downloadable archives.

Data Index Update (High-Resolution Support)

The application has been updated to support a new data index structure with multiple resolution domains and organized sub-folders in object storage.

New Object Store Structure

Data files are now organized by type (AERMOD/CALPUFF), resolution domain, and year/month:

AERMOD Data Locations

  • 4km resolution (d02) - Currently used by WRF:
    • https://nrs.objectstore.gov.bc.ca/wrfdel/aermod/d02/
  • High resolution domains:
    • https://nrs.objectstore.gov.bc.ca/wrfdel/aermod/d03/
    • https://nrs.objectstore.gov.bc.ca/wrfdel/aermod/d04/
    • https://nrs.objectstore.gov.bc.ca/wrfdel/aermod/d05/
    • https://nrs.objectstore.gov.bc.ca/wrfdel/aermod/d06/

CALPUFF Data Locations

  • 4km resolution (d02):
    • https://nrs.objectstore.gov.bc.ca/wrfdel/calpuff/3ddat/YYYYMM/d02/
  • High resolution domains:
    • https://nrs.objectstore.gov.bc.ca/wrfdel/calpuff/3ddat/YYYYMM/d03/
    • https://nrs.objectstore.gov.bc.ca/wrfdel/calpuff/3ddat/YYYYMM/d04/
    • https://nrs.objectstore.gov.bc.ca/wrfdel/calpuff/3ddat/YYYYMM/d05/
    • https://nrs.objectstore.gov.bc.ca/wrfdel/calpuff/3ddat/YYYYMM/d06/

Where YYYYMM represents the year and month (e.g., 201901 for January 2019).

Resolution Priority

The application uses a resolution priority strategy:

  • If high-resolution data is available for a search area, the application will preferentially use that data
  • Otherwise, it falls back to the 4km resolution (d02) data
  • This ensures users get the most detailed data available for their area of interest

Index File Format

The new index uses a CSV format with the following columns:

  • filename: Name of the data file
  • tile: Unique tile identifier
  • domain: Resolution domain (d02, d03, d04, d05, d06)
  • year: Data year
  • I0, J0, I1, J1: Grid coordinate bounds
  • lat0, lon0, lat1, lon1: Geographic coordinate bounds
  • url: Direct URL to the file in object storage

This structured index allows for:

  • Direct URL lookup without dynamic construction
  • Support for multiple resolution domains
  • Explicit inventory of available data files
  • Easier maintenance and updates