jDeters-USACE / Antecedent-Precipitation-Tool

Created to automate the climatological analysis workflows USACE Regulatory Project Managers are required to perform to comply with long-standing agency guidance as well as the new Navigable Waters Protection Rule, effective June 22, 2020..
https://github.com/jDeters-USACE/Antecedent-Precipitation-Tool
Other
10 stars 8 forks source link
climatology cwa regulatory usace

Antecedent Precipitation Tool (APT)

Where can I get it?

USACE has now migrated the current USACE version of the APT to ERDC's Github page.

What is it?

An automation tool that evaluates three climatological parameters to assist in the making and documenting of various determinations required by policy for the execution of USACE's Regulatory Program.

Scale

The tool can perform its analyses at a single point, for the consideration of wetland hydrology, or it can be configured to run on a watershed scale to help support a typical year analysis.

Usage

Rapidly, accurately, and effortlessly determine whether any of the following problematic circumstances exist for a given Latitude, Longitude, and Date:

Utility

Basic Methodology for each determination

Station Selection

Manual Procedure

- The original method required a PM to manually locate weather station data that they deemed most appropriate to use for their site, with a note that it should be relatively close and at a similar elevation.
- No real parameters were provided for when a station is too far, or how you can be sure there is not a closer station that you have overlooked.
- Most PMs were using only the stations used to create the WETS tables, which are limited to approximately 1 or 2 per county in California.
- If any dates were missing from the record, PMs were having to backfill from the other WETS station in the county, which might be drastically further away.

Problems with the manual method

- Weather patterns vary greatly over relatively small lateral distances, especially if those distances are accompanied with large changes in elevation.
- There are typically quite a few stations closer in distance and elevation, but PMs don't know how to find them all, and most people don't know how to calculate distance using geographic coordinates. Even if they did, sorting through all of the available stations based on distance and elevation difference would be extremely time-consuming.
- The completeness of the record needs to be considered, as you can't create a 30-year normal from disparate data sources.
- This would require PMs to download a large number of complete records from every available weather station, do the math on how many of dates from the pertinent range are missing from each dataset, and factor this information into the selection of their primary weather station.

Solution - Automated Querying of NOAA's data by programmatically

- Acquiring a list of every weather station in the U.S.
- Locating those within a specific distance from the observation point
- Sorting the selected stations by a weighted difference value

  - Incorporates both distance and difference in elevation
  - Created experimentally by matching the result to the best professional judgment of contributing PMs around the country.

Forthcoming improvements in the newest version