Ordered by payoff-per-effort; ✔ = you’ve effectively built it — formalize + verify + share:
- ✔ Traffic volume chart generator (counts → per-intersection hourly charts) — generalize beyond the one workbook; team-ready CLI.
- TMC sheet cleaner/balancer: vendor CSVs → standard tab + node-balance checks flagged.
- ✔ Crash summary generator: S4A CSV → year/severity/type tables + charts + top-locations map (folium).
- PDF table extractor: old studies/agency PDFs → dataframes (pdfplumber; QC prints).
- Project folder + file-namer: one command scaffolds File Naming and Project Folders structure.
- Trip-gen calculator: rates table + IC/pass-by stages → report-ready table (mirrors Trip Generation - Internal Capture and Pass-By).
- Parking study workbook builder + ULI QA/QC script: re-derives ULI matrix independently and diffs vs the analyst workbook — the definition of a second-method check.
- ✔ KML/KMZ ↔ GIS converter (your parser, packaged).
- Agency reference DB: scrape/refresh your
03 Agencieslink lists, flag dead URLs monthly (feeds Standards Update Tracker). - Comp-sites database: comp-site note frontmatter → searchable table (Dataview does v1 free).
- Countermeasure/CMF lookup: local CSV of your vetted CMFs with star/context fields.
- Excel QC bot: opens workbook, checks sum-ties/broken links/hidden errors, prints report.
Shipped: FTO AADT puller
First one actually in the repo: tools/fto_aadt.py. Stdlib-only Python — hits FDOT’s Open Data Hub AADT feature service (the TDA “Annual Average Daily Traffic” layer on services1.arcgis.com) and pulls every segment for a county: station (COSITE), roadway ID, from/to descriptions, AADT, year, and K/K100/D/T factors. Writes a CSV and prints a quick summary table so you can eyeball ranges before opening anything.
Usage: python tools/fto_aadt.py --county Hillsborough (county name or 2-digit FDOT code; add --route "I-275" to filter, --limit N to cap, --out file.csv to name the output).
Caveat that goes on everything downstream: this is screening-level — the current-year GIS event layer, great for scoping and sanity checks; official published AADT and historical counts come from Florida Traffic Online. Extending it is mostly swapping the layer URL — the same query/paginate skeleton works for any FDOT hosted layer (historical AADT, TMSCOUNT stations, RCI), so this doubles as the template for #9’s agency-data refreshers.