Call-prep brief · checked 2026-10-17
Trentino Trasporti (urban networks)
Grade B · 86.9 / 100
Unchanged since 2026-10-16.
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the rider information is complete. Each fix is framed as a next step, not a failure.
What changed since the last check
- Correctness no change
- Freshness no change
- Rider experience no change
Top three things to fix
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
This one is about the feed as a whole, so there is no share of it to count.
Effort: A small file for most flat-fare systems.
Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced.
Some stops sit far from the route line they belong to. Trip planners may draw the transit vehicle route through the wrong path or point riders to the wrong boarding location.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Effort: A few minutes per flagged stop.
Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards.
On some trips the stops fall along the route line in a different order than the schedule lists. Trip planners can draw the transit vehicle doubling back or skipping ahead, which confuses riders reading the map.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Effort: A few minutes per flagged trip.
Riders and need behind these fixes
- Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
- The served-area need overlays cover the United States and Canada, so none of them applies to this feed.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- The feed contains no fare information.
- Next action
- Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Some stops sit far from the route line they belong to.
- Next action
- Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- On some trips the stops fall along the route line in a different order than the schedule lists.
- Next action
- Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
Key facts
- Feed URL
- https://www.trentinotrasporti.it/opendata/google_transit_urbano_tte.zip
- Last checked
- 2026-10-17
- Service window
- 234 days of service data remain. Last service date 2027-06-08.
- Feed version
- 20260930190904.696
- Location
- Trentino-Alto Adige, Italy
Part of the Italy portfolio: see where this agency sits among the other feeds in that group before the call.
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.4, validator 8.0.1.