← NTD readiness

Does your GTFS feed need shapes.txt?

If your agency reports fixed-route or deviated-fixed-route service to the FTA's National Transit Database, yes: the GTFS feed you publish needs to include shapes.txt. Full Reporters have needed it since Report Year 2025, and Reduced, Rural, and Tribal Reporters join in Report Year 2026.

What shapes.txt is

shapes.txt is the file in a GTFS feed that traces each trip's path along the street or rail line, point by point. Trip planners use it to draw your routes on the map. A feed without it still lists stops and times, but an app can only connect the stops with straight lines, so the map shows vehicles cutting across blocks they never travel.

Each row in trips.txt points at a path through its shape_id column. Full coverage means every trip carries a shape_id that matches a path in shapes.txt.

Who needs it, and when

FTA's July 2025 final rule added shapes.txt to the GTFS that NTD reporters with fixed-route or deviated-fixed-route service publish and certify each year on the D-10 form. The requirement phases in by reporter type:

NTD reporter type shapes.txt required from
Full ReportersReport Year 2025
Reduced, Rural, and Tribal ReportersReport Year 2026

Report Year 2026 is the step that reaches most small agencies, many of them publishing GTFS under the NTD requirement for the first time. In 2022 FTA proposed that a reporter without a GTFS feed could request a one-year waiver by documenting that it is seeking technical assistance (the 2022 proposal). We have not confirmed how that waiver works under the current rule, so ask your NTD validation analyst. Your reporter type and any waiver live in your own NTD filing, not on this site.

Source: FTA's NTD reporting changes for report years 2025 and 2026. Reporters with no fixed-route or deviated-fixed-route service are outside the GTFS requirement.

Check whether your feed has it

The shapes.txt check already runs on every US feed this site tracks: open your agency's scorecard page and look for “shapes.txt covers your trips” in the NTD GTFS readiness section. If your agency is not tracked here, paste your feed's URL to grade it in about a minute, or run the pre-publish check on an export you have not published yet; that one reads the zip in your browser and uploads nothing.

FTA's final notice says it is making “the shapes.txt file mandatory” and adopting the change “as proposed.” It does not say how many routes or trips the file must cover, and it does not mention GTFS-Flex or other demand-response service. This site counts something simpler and stricter: whether every trip in trips.txt carries a shape_id that matches a path in shapes.txt.

How to add it

Shape data usually comes from the software that builds your feed, not from hand-drawn maps. If a vendor or scheduling tool produces your GTFS export, ask for shapes.txt in the export, with trips.shape_id set to match. If some trips already have shapes, the remaining work is to fill in the rest so every trip has a path.

After you republish, the next completed scoring run re-checks your feed and the readiness line on your agency's page updates on its own.

Where tracked feeds stand

Across the 957 US feeds this site tracks and checks, 94.5% carry a shape for every trip. The rest have the file to add or finish before their report year. A further 59 Flex-only feeds are reported separately below.

A feed in which every trip is GTFS-Flex demand-response service (riders are picked up in zones or time windows, not along a fixed path) is reported on its own row as a Flex-only feed and is not counted in the headline totals. The notice does not say whether such a feed is expected to include shapes.txt. A feed that also runs fixed-route trips stays in the count, even if it publishes Flex as well.

CoverageFeeds
Every trip has a shape904
Some trips are missing one41
No shapes yet12
Flex-only feed (not counted above)59

By state

StateFullPartialNoneCheckedFlex-only
Alabama30360
Alaska70070
Arizona1910200
Arkansas20020
California186411917
Colorado47715531
Connecticut80190
Delaware10010
District of Columbia40040
Florida3900390
Georgia1400140
Hawaii30030
Idaho30030
Illinois1201130
Indiana1000100
Iowa1810190
Kansas50050
Kentucky40040
Louisiana40040
Maine60060
Maryland2610270
Massachusetts3511370
Michigan1300130
Minnesota81091
Mississippi30030
Missouri51060
Montana80080
Nebraska30030
Nevada60060
New Hampshire20021
New Jersey40040
New Mexico1400140
New York7620780
North Carolina1600160
North Dakota30030
Ohio1410150
Oklahoma30030
Oregon6710680
Pennsylvania2810290
Rhode Island21030
South Carolina60060
South Dakota10010
Tennessee80190
Texas2010210
Unlocated1233181
Utah60060
Vermont1140150
Virginia3890476
Washington57105812
West Virginia20020
Wisconsin1100110
Wyoming10010

A state name that is a link opens that state's list of tracked feeds. A state appears there once at least 5 of its feeds have been checked for shapes.txt.

For reporters: the Report Year 2026 story

The story here is population-level: a federal data requirement reaches the smallest transit agencies in Report Year 2026, and a measurable share of published feeds do not carry the file yet. When FTA proposed the requirement in October 2024, it estimated that over one-third of all reporters already maintained the file (the proposal); the final notice does not repeat the estimate.

“Of 957 tracked US transit feeds checked, 94.5% include a shape for every trip.” The per-state counts above support a local cut, counted over the covered set with the state named. The same numbers are machine-readable in ntd.json.

Two claims these numbers do not support. First, “Agency X is out of compliance”: reporter type and waiver status live in an agency's own NTD filing, and this site reads published feeds, not filings; it states what a feed contains and certifies nothing. Second, a worst-agencies ranking: the site covers the feeds it tracks, so absence means not covered, never failing, and these denominators differ from FTA's (tracked feeds, not all NTD reporters). Attribution and more guidance: writing about this data.

This page is a data-quality heads-up, not an official compliance determination or legal advice. The official record is each agency's own NTD filing and annual D-10 certification.