precip-analyze-atlas14-variance
Analyze spatial variability of NOAA Atlas 14 precipitation frequency estimates within HEC-RAS model domains using intelligent extent-based downloading. Helps determine whether uniform rainfall assump
Files2
View on GitHubSKILL.md.claude/skills/precip_analyze_atlas14-variance/SKILL.md
GitHubAtlas 14 Spatial Variance Analysis
Invoke this skill to assess precipitation spatial variability in HEC-RAS models
Primary Sources (Read These First)
Canonical Contract:
ras_commander/precip/AGENTS.md- Method selection for Atlas 14 grid and variance workflows
- Critical precipitation rules and validation expectations
- Reference notebooks for working examples
API Reference:
ras_commander/precip/Atlas14Grid.py(404 lines)get_pfe_from_project()- Main entry point for HEC-RAS integrationget_pfe_for_bounds()- Direct bounding box queryget_point_pfe()- Single point lookup
ras_commander/precip/Atlas14Variance.py(322 lines)analyze()- Full variance analysisanalyze_quick()- Rapid assessment (100-yr, 24-hr)is_uniform_rainfall_appropriate()- Decision supportgenerate_report()- Export with plots
Working Example:
examples/725_atlas14_spatial_variance.ipynb- Direct bounds queries
- Point lookups
- HEC-RAS project integration
- Visualization
Quick Reference:
.claude/rules/hec-ras/precipitation.md
Quick Reference
Typical Workflow (3 Steps)
from ras_commander.precip import Atlas14Variance
# Step 1: Quick check for representative event
stats = Atlas14Variance.analyze_quick("MyProject.g01.hdf")
# Step 2: Interpret results
if stats['range_pct'] > 10:
# High variance - run full analysis
results = Atlas14Variance.analyze(
geom_hdf="MyProject.g01.hdf",
durations=[6, 12, 24],
return_periods=[10, 25, 50, 100]
)
# Step 3: Generate report
Atlas14Variance.generate_report(
results,
output_dir="Atlas14_Report",
project_name="My Project"
)
else:
# Low variance - uniform rainfall OK
print("✓ Uniform rainfall appropriate")
Direct Grid Access
from ras_commander.precip import Atlas14Grid
# Get PFE for project extent
pfe = Atlas14Grid.get_pfe_from_project(
geom_hdf="MyProject.g01.hdf",
extent_source="2d_flow_area", # or "project_extent"
durations=[6, 12, 24],
return_periods=[10, 50, 100],
buffer_percent=10.0
)
# Access data
print(f"Grid size: {pfe['lat'].shape[0]} x {pfe['lon'].shape[0]}")
print(f"100-yr 24-hr max: {pfe['pfe_24hr'][:,:,5].max():.2f} inches")
Point Query (No Project)
# Quick lookup for single location
df = Atlas14Grid.get_point_pfe(
lat=29.76,
lon=-95.37,
durations=[6, 12, 24],
return_periods=[10, 50, 100, 500]
)
print(df)
Common Workflows
Workflow 1: Quick Assessment
Purpose: Rapid check if variance analysis is needed
See: ras_commander/precip/AGENTS.md and the Atlas 14 variance source docstrings.
from ras_commander.precip import Atlas14Variance
stats = Atlas14Variance.analyze_quick("MyProject.g01.hdf")
if stats['range_pct'] > 10:
print("⚠️ Run full analysis - high variance detected")
Workflow 2: Full Analysis
Purpose: Comprehensive variance across multiple events
See: ras_commander/precip/AGENTS.md and Atlas14Variance.analyze() docstrings.
results = Atlas14Variance.analyze(
geom_hdf="MyProject.g01.hdf",
durations=[6, 12, 24, 48],
return_periods=[10, 25, 50, 100, 500],
extent_source="2d_flow_area",
variance_denominator='min', # or 'max', 'mean'
output_dir="Atlas14_Variance_Report"
)
Workflow 3: Report Generation
Purpose: Engineering documentation
See: ras_commander/precip/AGENTS.md and Atlas14Variance.generate_report() docstrings.
report_dir = Atlas14Variance.generate_report(
results_df=results,
output_dir="reports/",
project_name="My Project",
include_plots=True
)
# Files created:
# - variance_statistics.csv
# - variance_summary.csv
# - variance_by_duration.png
# - variance_heatmap.png
Workflow 4: Custom Grid Analysis
Purpose: Export for HEC-RAS import or custom processing
See: ras_commander/precip/AGENTS.md and Atlas14Grid.get_pfe_from_project() docstrings.
from ras_commander.precip import Atlas14Grid
pfe = Atlas14Grid.get_pfe_from_project(
geom_hdf="MyProject.g01.hdf",
extent_source="2d_flow_area",
durations=[24],
return_periods=[100]
)
# Access raw arrays for custom analysis
lat = pfe['lat']
lon = pfe['lon']
data_100yr_24hr = pfe['pfe_24hr'][:, :, 5]
Key Parameters
extent_source
Controls which geometry is used for extent extraction:
"2d_flow_area"(default, recommended)- Uses union of 2D flow area perimeters
- Most relevant for rain-on-grid models
- Can filter to specific areas via
mesh_area_names
"project_extent"- Uses full project bounding extent
- Includes 1D and storage areas
- Larger extent = more data downloaded
use_huc12_boundary
Controls whether to use HUC12 watershed instead of 2D flow area:
False(default)- Uses 2D flow area perimeters or project extent
- Fastest analysis (smaller area)
True- Finds HUC12 watershed containing center of 2D flow area
- Downloads HUC12 boundary from NHDPlus
- Analyzes full contributing watershed
- Typically higher variance (larger extent)
- Requires
pygeohydropackage
Example:
# Analyze using HUC12 watershed
results = Atlas14Variance.analyze(
geom_hdf="MyProject.g01.hdf",
use_huc12_boundary=True
)
variance_denominator
Controls how range percentage is calculated:
'min'(default) -range_pct = (max - min) / min × 100- Shows variance relative to minimum value
- Matches HEC-Commander approach
- More sensitive to variance
'max'-range_pct = (max - min) / max × 100- Shows variance relative to maximum value
- More conservative metric
'mean'-range_pct = (max - min) / mean × 100- Engineering standard
- Balanced perspective
Technical Details
NOAA CONUS NetCDF Structure
URL: https://hdsc.nws.noaa.gov/pub/hdsc/data/tx/NOAA_Atlas_14_CONUS.nc
| Property | Value |
|---|---|
| Coverage | CONUS (24°N-50°N, -125°W to -66°W) |
| Resolution | |
| Format | HDF5-based NetCDF-4 |
| Size | 320 MB (chunked for efficient access) |
| Chunking | (49, 111, 1) - optimized for spatial access |
| HTTP Support | Accept-Ranges: bytes ✓ |
Available Data:
- Durations: 1, 2, 3, 6, 12, 24, 48, 72, 96, 168 hours
- Return Periods: 2, 5, 10, 25, 50, 100, 200, 500, 1000 years
- Scale Factor: 0.01 (raw values × 0.01 = inches)
Data Transfer Efficiency
| Project Size | Grid Cells | Data Transfer | Full Grid | Reduction |
|---|---|---|---|---|
| Small (0.5° × 0.5°) | ~3,600 | ~60 KB | 379 MB | 99.98% |
| Medium (1° × 1°) | ~14,400 | ~250 KB | 379 MB | 99.93% |
| Large (2° × 2°) | ~57,600 | ~1 MB | 379 MB | 99.74% |
Comparison: Traditional approach downloads 50-100 MB per state as ZIP files.
Critical Warnings
CONUS Coverage Only
The NOAA CONUS NetCDF covers Continental US only:
Covered: Lower 48 states (24°N-50°N, -125°W to -66°W)
Not Covered:
- Hawaii (use StormGenerator point API instead)
- Alaska (use StormGenerator point API instead)
- Puerto Rico (use StormGenerator point API instead)
- Offshore areas (no data)
Internet Required
Atlas14Grid requires internet access to NOAA servers:
- No offline mode currently implemented
- Cache coordinates in memory (cleared with
Atlas14Grid.clear_cache()) - Future: Local disk caching planned
Return Period Mapping
The ari dimension uses return periods, not ARI indices:
ari = [2, 5, 10, 25, 50, 100, 200, 500, 1000]
# 100-year event is index 5
pfe_100yr = pfe['pfe_24hr'][:, :, 5] # Correct
# NOT index 100
pfe_100yr = pfe['pfe_24hr'][:, :, 100] # Wrong!
Dependencies
Required (already in ras-commander):
h5py>=3.0.0- HDF5/NetCDF accessnumpy- Array operationspandas- DataFramesgeopandas>=0.12.0- Spatial operationsfsspec>=2023.0.0- Remote file systems (HTTP)
Optional:
matplotlib- Plotting (forgenerate_report())rioxarray- Enhanced raster operations (future)
Installation:
pip install ras-commander # All required deps included
Navigation Map
For package rules: Read ras_commander/precip/AGENTS.md
For API details: Read docstrings in:
ras_commander/precip/Atlas14Grid.pyras_commander/precip/Atlas14Variance.py
For working code: Run examples/725_atlas14_spatial_variance.ipynb
For quick reference: See .claude/rules/hec-ras/precipitation.md
For research background: See .claude/outputs/atlas14-variance-research-summary.md
Common Questions
Q: When should I use this instead of StormGenerator?
Use Atlas14Grid/Variance when:
- You need spatial precipitation grids (not just point values)
- You want to assess uniform rainfall validity
- You have a large model domain where variance matters
Use StormGenerator when:
- You need point precipitation for a single location
- You want hyetograph generation (temporal distribution)
- You're doing design storm analysis (not variance assessment)
Q: How accurate is the spatial subsetting?
The HTTP range request approach downloads exactly the grid cells within the specified extent. Validation shows:
- ✓ Matches NOAA PFDS web interface values
- ✓ Houston, TX 100-yr 24-hr: 17.00 inches (correct)
- ✓ No data loss from subsetting
- ✓ Scale factor properly applied (0.01)
Q: What if my project spans multiple states?
The CONUS NetCDF covers the entire Continental US in a single file, so:
- ✓ Multi-state projects work automatically
- ✓ No manual merging required
- ✓ No need to specify states
This is a major advantage over HEC-Commander's approach, which requires downloading separate state datasets and manually merging them.
Q: Can I export the grid data to HEC-RAS?
Current: Atlas14Grid returns numpy arrays - export to GeoTIFF/NetCDF not yet implemented
Workaround: Use the data for variance analysis, then use StormGenerator or Atlas14Storm to create HEC-RAS precipitation input files
Future: Planned enhancement for direct GeoTIFF/NetCDF export
Skill Invocation
When user asks to:
- "Analyze Atlas 14 spatial variance for my HEC-RAS project"
- "Check if uniform rainfall is appropriate"
- "Get precipitation frequency grids for my 2D flow areas"
- "Assess precipitation spatial variability"
Respond with:
Quick Check First:
from ras_commander.precip import Atlas14Variance stats = Atlas14Variance.analyze_quick("project.g01.hdf") print(f"Range: {stats['range_pct']:.1f}%")Interpret Results:
- Range < 10%: "✓ Uniform rainfall appropriate"
- Range > 10%: "⚠️ Consider full analysis"
Full Analysis if Needed:
results = Atlas14Variance.analyze("project.g01.hdf") ok, msg = Atlas14Variance.is_uniform_rainfall_appropriate(results) print(msg)Generate Report:
Atlas14Variance.generate_report( results, output_dir="Atlas14_Report", include_plots=True )
Examples, Troubleshooting, and Performance
For use case examples, troubleshooting common errors, and performance tips, read references/examples-and-troubleshooting.md.
Cross-References
Rules (follow these):
.claude/rules/hec-ras/precipitation.md-- Precipitation domain overview.claude/rules/testing/precipitation-method-validation.md-- Testing precipitation methods
Agents (delegate when needed):
precipitation-specialist-- Delegate for complex precipitation workflows
Skills (related workflows):
precip_analyze_aorc-- Use for historical AORC precipitation analysisdss_read_boundary-data-- Use when exporting design storms to DSS format
Primary sources:
ras_commander/AGENTS.md-- Precipitation section