GTFS Scorecard
← All agencies

Feed status · checked 2026-09-05

Trenitalia regional rail in Liguria

Based on the official feed source on file

Service mode Rail + Bus

59.4 / 100

First scorecard for this agency

Catalogued in Liguria, Italy.

Covers 98 daysAccessibility gapsRealtime not yet published

Trenitalia's regional rail service in Liguria, one operator dataset of the region's planned-service publication. Regione Liguria names each archive after its validity window, so the download is version-pinned and a curator refreshes it when the region publishes the next period.

A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.

Measured 3 of 4 score categories from the official feed URL on file.

How we measured this

Confidence in this measurement: medium.

  • Realtime quality was not measured this run. It does not count against the grade.
  • The feed was downloaded from the official feed URL on file.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

Top things to fix

Fix 01

Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

Duplicate key (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +24 points in its category

Fix 02

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.

⏱ A small file for most flat-fare systems.worth about +15 points in its category

Fix 03

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

194 of 357 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.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +14 points in its category

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
Duplicate key (flagged by the MobilityData validator).
Next action
Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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
How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

  1. Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  2. 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. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

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

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility
The feed's last published service date is in 98 days.
Published accessibility data
Accessibility information is stated for 45.7% of stops and 58% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
No fare information is published in the feed.
Realtime information
Realtime-feed availability and live-arrival coverage are not known from this scorecard.

Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.

Send your vendor a fix request

You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.

Score by category

Correctness48.0 / 100

The MobilityData validator flagged 5 kinds of issue across 2469 instances (547 error, 1922 warning, 0 informational).

Freshness100.0 / 100

Service data covers the next 98 days.

Rider experience42.9 / 100

46% of stops state wheelchair accessibility (46% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.

Accessibility50.3 / 100

46% of stops state accessibility (46% marked accessible). Reflects what the feed states, not verified physical usability.

1 accessibility depth signal

  • 1 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("ST.DALMAS DE TENDE (IT)").

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.

Realtime qualityNot yet measured

Not scored yet. Nothing here counts against the grade.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 357 stops.

Skip to route and stop data

The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

  • REG (red)
  • REG (red)
  • EXP (red)
  • ICN (red)
  • IC (red)
  • EC (red)
  • RV (red)
  • FB (red)
  • FR (red)
  • FA (red)
  • BUS (red)
Routes in Trenitalia regional rail in Liguria's feed
RouteTypeLine color
REG RegionaleRailred
REG RegionaleRailred
EXP EspressoRailred
ICN InterCityNotteRailred
IC IntercityRailred
EC EurocityRailred
RV Regionale VeloceRailred
FB FrecciabiancaRailred
FR FrecciarossaRailred
FA FrecciargentoRailred
BUS AutobusBusred
TS Treno StoricoRailred (no shape in feed)
List every stop
  • MORTARA
  • TORINO PORTA NUOVA
  • TORINO PORTA SUSA
  • VERCELLI
  • NOVARA
  • TORINO LINGOTTO
  • TROFARELLO
  • VILLANOVA D'ASTI
  • VILLAFRANCA-CANTARANA
  • ASTI
  • ALESSANDRIA
  • CARMAGNOLA
  • RACCONIGI
  • CAVALLERMAGGIORE
  • SAVIGLIANO
  • FOSSANO
  • CUNEO
  • BORGO S.DALMAZZO
  • ROCCAVIONE
  • ROBILANTE
  • VERNANTE
  • LIMONE
  • CEVA
  • SALE LANGHE
  • SALICETO
  • CENGIO
  • BORGORATTO
  • CASSINE
  • STREVI
  • ACQUI TERME
  • TERZO MONTABONE
  • BISTAGNO
  • PONTI
  • MONTECHIARO DENICE
  • MOMBALDONE-ROCCAVERANO
  • SPIGNO
  • MERANA
  • PIANA
  • DEGO
  • ROCCHETTA CAIRO
  • CAIRO MONTENOTTE
  • TRINITA' BENE VAGIENNA
  • MAGLIANO CRAVA MOROZZO
  • MONDOVI'
  • VICOFORTE S.MICHELE
  • LESEGNO
  • GALLARATE
  • BUSTO ARSIZIO
  • LEGNANO
  • RHO
  • CHIASSO
  • COMO S.GIOVANNI
  • MILANO GRECO PIRELLI
  • Milano Forlanini
  • BERGAMO
  • VERDELLO DALMINE
  • TREVIGLIO OVEST
  • MILANO PORTA GARIBALDI
  • MILANO CENTRALE
  • MILANO LAMBRATE
  • BRESCIA
  • VOGHERA
  • TORTONA
  • MILANO ROGOREDO
  • MELEGNANO
  • LODI
  • CASALPUSTERLENGO
  • CODOGNO
  • PAVIA
  • STRADELLA
  • CASTEL S.GIOVANNI
  • S.NICOLO'
  • DESENZANO
  • PESCHIERA DEL GARDA
  • VERONA PORTA NUOVA
  • VICENZA
  • PADOVA
  • VENEZIA MESTRE
  • VENEZIA S.LUCIA
  • VISONE
  • PRASCO CREMOLINO
  • MOLARE
  • OVADA
  • ROSSIGLIONE
  • CAMPOLIGURE MASONE
  • MELE
  • GENOVA ACQUASANTA
  • GENOVA GRANARA
  • GENOVA BORZOLI
  • GENOVA COSTA DI SESTRI PONENTE
  • FRUGAROLO BOSCOMARENGO
  • NOVI LIGURE
  • SERRAVALLE SCRIVIA
  • ARQUATA SCRIVIA
  • RIGOROSO
  • PIETRABISSARA
  • ISOLA DEL CANTONE
  • RONCO SCRIVIA
  • BORGO FORNARI PER VOLTAGGIO
  • BUSALLA
  • PIANO ORIZZONTALE DEI GIOVI
  • GENOVA PONTEDECIMO
  • GENOVA BOLZANETO
  • GENOVA RIVAROLO
  • GENOVA SAMPIERDARENA
  • GENOVA S.BIAGIO
  • GENOVA VIA DI FRANCIA
  • OLIVETTA S.MICHELE
  • AIROLE
  • BEVERA
  • VENTIMIGLIA
  • VALLECROSIA
  • BORDIGHERA
  • Sanremo
  • TAGGIA ARMA
  • DIANO
  • Andora
  • LAIGUEGLIA
  • ALASSIO
  • ALBENGA
  • CERIALE
  • BORGHETTO S.SPIRITO
  • LOANO
  • PIETRA LIGURE
  • BORGIO VEREZZI
  • FINALE LIGURE MARINA
  • Imperia
  • SPOTORNO NOLI
  • QUILIANO VADO
  • ALBISOLA
  • CELLE
  • VARAZZE
  • COGOLETO
  • ARENZANO
  • GENOVA VOLTRI
  • GENOVA PRA
  • GENOVA PEGLI
  • GENOVA SESTRI PONENTE
  • GENOVA CORNIGLIANO
  • GENOVA VESIMA
  • GENOVA PIAZZA PRINCIPE
  • GENOVA BRIGNOLE
  • GENOVA STURLA
  • GENOVA QUARTO DEI MILLE
  • GENOVA QUINTO AL MARE
  • GENOVA NERVI
  • BOGLIASCO
  • PONTETTO
  • PIEVE LIGURE
  • SORI
  • MULINETTI
  • RECCO
  • CAMOGLI S.FRUTTUOSO
  • S.MARGHERITA LIGURE PORTOFINO
  • RAPALLO
  • ZOAGLI
  • CHIAVARI
  • LAVAGNA
  • CAVI
  • SESTRI LEVANTE
  • RIVA TRIGOSO
  • MONEGLIA
  • DEIVA MARINA
  • FRAMURA
  • BONASSOLA
  • LEVANTO
  • MONTEROSSO
  • VERNAZZA
  • CORNIGLIA
  • MANAROLA
  • RIOMAGGIORE
  • SAVONA
  • SANTUARIO
  • BRAGNO
  • FERRANIA
  • S.GIUSEPPE DI CAIRO
  • ALTARE
  • PIACENZA
  • FIORENZUOLA
  • FIDENZA
  • PARMA
  • S.ILARIO
  • REGGIO EMILIA
  • RUBIERA
  • MODENA
  • CASTELFRANCO EMILIA
  • BOLOGNA C.LE
  • S.LAZZARO DI S.
  • CASTEL S.PIETRO TERME
  • IMOLA
  • CASTELBOLOGNESE
  • FAENZA
  • FORLI'
  • FORLIMPOPOLI
  • CESENA
  • GAMBETTOLA
  • SAVIGNANO SUL RUBICONE
  • S.ARCANGELO DI ROMAGNA
  • RIMINI
  • RAVENNA
  • SOLAROLO
  • LUGO
  • BAGNACAVALLO
  • RUSSI
  • LA SPEZIA CENTRALE
  • LASTRA A SIGNA
  • LA SPEZIA MIGLIARINA
  • CARRARA AVENZA
  • ARCOLA
  • SARZANA
  • LUNI
  • MASSA CENTRO
  • FORTE DEI MARMI-SERAVEZZA-QUERCETA
  • PIETRASANTA
  • AULLA LUNIGIANA
  • TORRE DEL LAGO PUCCINI
  • CECINA
  • CAMPIGLIA MARITTIMA
  • FOLLONICA
  • GROSSETO
  • VIAREGGIO
  • CAMAIORE LIDO CAPEZZANO
  • CA' DI BOSCHETTI
  • MEDESANO
  • VICOFERTILE
  • COLLECCHIO
  • OZZANO TARO
  • FORNOVO
  • SOLIGNANO
  • BERCETO
  • OSTIA PARMENSE
  • BORGO VAL DI TARO
  • PONTREMOLI
  • FILATTIERA
  • VILLAFRANCA-BAGNONE
  • S.STEFANO DI MAGRA
  • VEZZANO LIGURE
  • FIVIZZANO ROMETTA-SOLIERA
  • FIVIZZANO-GASSANO
  • GRAGNOLA
  • MONZONE-MONTE DEI BANCHI-ISOLANO
  • EQUI TERME
  • MINUCCIANO-PIEVE-CASOLA
  • PRATO CENTRALE
  • FIRENZE CASTELLO
  • FIRENZE RIFREDI
  • FIRENZE S.MARIA NOVELLA
  • PISA CENTRALE
  • PISA SAN ROSSORE
  • NAVACCHIO
  • and 107 more (see the full list on the map or in the GeoJSON)

Over time

This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.

Everything we checked

10 findings, ordered by severity.

Show every finding
  • Error547 instances

    Duplicate key (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: duplicate_key · See MobilityData GTFS Validator rules

  • Warning1443 instances

    Some rider-facing names are in ALL CAPS or all lowercase.

    ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

    Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)

    Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning765 instances

    765 of 1823 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.

    Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)

    Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning264 instances

    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.

    Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)

    Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning214 instances

    Some stops sit far from the route line, going by the feed's own distance values.

    Trip planners may draw the route down the wrong path or point riders to the wrong boarding location.

    Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)

    Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning194 instances

    194 of 357 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.

    Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)

    Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning1 instance

    feed_info.txt lists no contact email and no contact URL.

    Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.

    Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)

    Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    The feed contains no fare information.

    Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

    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. (A small file for most flat-fare systems.)

    Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices

  • Info351 instances

    About 351 stop names are written in ALL CAPS.

    Mixed-case names are easier to read in apps and are read more naturally by screen readers.

    Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)

    Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

    App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules

Conformance mark Not yet

Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. States wheelchair access on 46% of stops and 58% of trips; the mark needs 90% of each.

Valid Not yet
1 validator error to resolve.
Current Met
Service data covers the next 98 days.
Accessible Not yet
States wheelchair access on 46% of stops and 58% of trips; the mark needs 90% of each.

In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.

A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.

Clears the Google and Apple Maps four-week coverage bar. This feed has 98 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 547 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.

How this agency maps to the standards

The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance. Read the full standards crosswalk.

Correctness 48 / 100
GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication.
Freshness 100 / 100
GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners.
Rider experience 43 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality Not yet published
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Show your grade

Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.

Trenitalia regional rail in Liguria GTFS data quality grade: F

Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.

Cite this record

This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/trenitalia-liguria/2026-09-05.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-09-05. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.