Upload the EPMPO submittal: the network shapefile (one shapefile carrying all six network years — raw wide layout or the merged-long layout are both auto-detected; include all sidecar files) and the project listing (CSV). Then click Process Data.
Runs on EVERY listing row before any filtering: checks each project's Project Element / Mode classification against the 40 CFR exemption categories and regional-significance signals (EPMPO functional class is used directly for the RS test). Nothing is dropped here.
Each row is ONE inconsistency on one link in one year — a single project appears once per inconsistency, so a project with several rows has several separate things to look at.
Every listing row whose Network year says it should be in the travel model but that no link carries as P1 or P2. 'Expected' rows are programmatic or transit projects that never tag roadway links.
All findings + per-check sheets in one Excel file.
⬇ Download Complete Summary (Excel)Python Shiny implementation of the EPMPO TDM QA workflow (FY26). One network shapefile carries all six network years (2017–2052); the QA is year-based: network-year anomalies, unexplained lane drops, presence checks, and description-decoded lane comparison — plus the Section-3 / 40 CFR exemption QA check on the full listing.
Maintained by the TTI Environmental Modeling Program under IAC-A Subtask 4.1.