+ USGS gauges · FHWA NBI bridges · USACE NID dams · SIR 2024-5130 envelope · state + county auto-detect
Preliminary screening only. Verify every value against its authoritative source before acting on it. Not for design, permits, insurance, or regulatory filings. The two drainage areas shown are different on purpose: the SnapBasin value (top) is NHDPlus HR’s per-reach published total — constant within a reach segment; the StreamStats value (below) is an independent modern flow-accumulation delineation at the click point. Where they disagree, the modern DEM does not confirm the legacy NHD basin definition.
⊕
Click any point on the map. First SnapBasin tries to snap to a nearby NHD flowline (green). If NHD doesn't have it, SnapBasin pulls a 10m 3DEP elevation tile and walks steepest-descent downhill through the terrain (purple dashed) until it finds a drainage — the same physics StreamStats uses server-side. Then it delineates from there.
Zoom in to tighten the NHD snap. FEMA + gauges always run from your original click. Toggle FEMA Flood Map (FIRM) in the layers panel to see cross-section letters and BFE elevations rendered directly on the map (visible at z15+). Toggle USA Structures to overlay building footprints (occupancy / height / address) from the FEMA + Oak Ridge dataset (visible at z14+). Click any building for details.
⟁ SnapBasin — before you start
SnapBasin is a hobby project I built to speed up my own preliminary work. It pulls hydrologic, hydraulic, and flood-risk data from public federal sources and shows it in one click instead of five websites.
This is not an engineering deliverable
Do not use SnapBasin output for:
Insurance or real estate decisions
Design of any drainage structure, bridge, building, or road
Permit applications, certifications, or regulatory filings
Floodplain determinations or elevation certificates
For any decision that matters, go to the authoritative source
Values shown here may be wrong, stale, or misapplied. The snap-to-stream may land on the wrong reach. Regression equations may be extrapolated outside their validity range. Parsed NBI fields may not match the latest inspection. LOMR data may be incomplete. Verify everything.
SnapBasin is a personal project by Travis Jenkins, built on personal time with personal resources. It is not affiliated with, endorsed by, or representative of any employer, agency, or licensing board. Data sources belong to their respective federal agencies and are used under public-domain access. No warranty, express or implied.
About SnapBasin
SnapBasin is a personal hobby project by Travis Jenkins, a hydraulic engineer (EIT) who wanted to click one point on a map and see everything at once instead of loading five different websites.
What it is
A click-the-map preliminary screening tool. Given a point, it snaps to the nearest stream (NHDPlus HR vector snap, or 3DEP terrain walk-down when there's no vector match), delineates the basin via USGS StreamStats, pulls basin characteristics, runs the applicable NSS regression equations, cross-references FEMA published discharges, checks for active LOMRs on the reach, queries FEMA flood zone at both click and stream points, lists nearby USGS gauges, finds NID dams upstream with distance-from-click, and enumerates NBI bridges on the reach with full geometry.
What it is not
It is not a substitute for engineering judgment, certified studies, sealed work products, or the authoritative source for any of the data it displays. It is not affiliated with, endorsed by, or representative of TDOT, FHWA, USGS, FEMA, USACE, or any employer, agency, or licensing board.
All development — code, AI assistance, data curation, and testing — was performed on personal equipment during personal time. The tool consumes public federal data and adds nothing proprietary to any employer's work product. Use of real project data during development was limited to validation of public methods against public sources; no internal engineering files, deliverables, or employer IP are contained in or exposed by SnapBasin.
Data sources
Everything here is public federal data, redisplayed. Source links are in the footer. If something looks wrong, the authoritative portal is always the tiebreaker.
Built in
~20 hours across a long weekend, on a home computer, with a lot of help from an AI pair programmer. $13/year domain + free Netlify hosting. No analytics, no tracking, no accounts, no cookies beyond the one that remembers you've read this disclaimer.
Bug reports, feature requests, and "hey this number looks weird" feedback welcome. Nothing here is monetized and nothing here is warranted.
Export Bridge Metadata for Scour Calc
⚠ VERIFICATION REQUIRED — GO LOOK FOR YOURSELF
The values below are extracted from the FHWA National Bridge Inventory (NBI) 2025 snapshot.
NBI data can be stale, contain parser artifacts, or reflect pre-reconstruction geometry.
Before using any of these values in a scour analysis:
Verify the bridge number matches the actual structure you are analyzing
Verify OtoO width, skew, and pier geometry against project drawings or current TDOT inspection
Cross-check the feature/stream name against the correct NHD reach
NBI data is not a substitute for engineering inspection, plan review, or as-built verification
The tool author is not responsible for errors from blind use of exported values
Bridge metadata preview
Export as:
Paste into the SCOUR CALC v3.3+ SUMMARY tab. The text format lists each field as "Label: value" —
you type the values into the corresponding yellow cells on the SUMMARY tab manually. This keeps the
verification step in your hands — no auto-fill, no silent overwrites.
A note from the builder
Single developer. About to be a 49‑year‑old father of four — three teenagers at home.
If you see something wrong, please let me know — I’ll change it as soon as I can. I’ll credit you if you want the credit.
Some labs are better than others; a few have obvious broken bits I’m still working through. Some were built early, some late — they don’t all look the same, but they share a feel.