GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-10-16

AMT Genova

Grade F · 57.0 / 100

Up 29.7 points since 2026-10-15 (F to F).

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 up 62.0
  • Freshness up 10.0
  • Rider experience no change

No longer reported since the last check (4 findings):

  • Missing required field (flagged by the MobilityData validator). (missing_required_field)
  • Block trips with overlapping stop times (flagged by the MobilityData validator). (block_trips_with_overlapping_stop_times)
  • Foreign key violation (flagged by the MobilityData validator). (foreign_key_violation)
  • Some files leave out fields that GTFS asks for but does not require. (missing_recommended_field)

This compares feed state. It does not identify who made a change or why.

Top three things to fix

  1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

    2755 of 2755 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

    Fixing this covers all 2,755 stops in the feed.

    Effort: A column in stops.txt; your scheduling software likely has it.

  2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

    47557 of 47557 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle itself can take them.

    Fixing this covers all 47,557 trips in the feed.

    Effort: A default or per-trip field in your export.

  3. Add feed_info.txt with feed_start_date and feed_end_date to your export.

    feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

    This one is about the feed as a whole, so there is no share of it to count.

    Effort: Two fields, set once in export settings.

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
2755 of 2755 stops don't say whether a wheelchair user can board there.
Next action
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
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
http://opendatagoogletransit.comune.genova.it/downloads/google_transit.zip
Last checked
2026-10-16
Service window
49 days of service data remain. Last service date 2026-12-04.
Location
Liguria, 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.