GTFS Scorecard
← All agencies

Feed status · checked 2026-07-18

ASPO (Olbia urban bus)

Based on the feed this agency publishes

Service mode Bus

54.4 / 100

First scorecard for this agency

Catalogued in Sardegna, Italy.

Covers 59 daysAccessibility gapsRealtime not yet published

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.2, validator 8.0.1.

Measured 3 of 4 score categories from the agency's own feed.

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 agency's own URL.

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 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

Trip distance exceeds shape distance (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +12 points in its category

Fix 02

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

403 of 403 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 +25 points in its category

Fix 03

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

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

⏱ A default or per-trip field in your export.worth about +15 points in its category

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 'trip_distance_exceeds_shape_distance' 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. 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.

  3. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · 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 59 days.
Published accessibility data
Accessibility information is stated for 0% of stops and 0% 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

Correctness36.0 / 100

The MobilityData validator flagged 10 kinds of issue across 15649 instances (3 error, 15646 warning, 0 informational).

Freshness98.3 / 100

Service data covers the next 59 days.

Rider experience45.0 / 100

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

Accessibility0 / 100

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

2 accessibility depth signals

  • 11 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (01, 02, 03, 04, 05PR, and more).

    Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.

  • 4 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Monte Ladu fr.St.Bide", "V.Monte Ladu St. Bide", "Putzolu St.zo Caprolu", and more).

    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.

Skip to route and stop data

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

  • 01 (red)
  • 02 (pink)
  • 03 (teal)
  • 04 (white)
  • 05PI (green)
  • 05PR (white)
  • 06 (gray)
  • 07 (brown)
  • 08 (orange)
  • 09 (pink)
  • 10 (purple)
  • 11 (gray)
  • 12 (gray)
Routes in ASPO (Olbia urban bus)'s feed
RouteTypeLine color
01 Sa Marinedda - BasaBusred
02 Mater - Via NicosiaBuspink
03 Caresi - Centro (Ponte di Ferro - Via Roma) - CaresiBusteal
04 Via G. Vico (Ex Tribunale) - BadosBuswhite
05PI Porto Istana - OlbiaBusgreen
05PR Porto Rotondo - OlbiaBuswhite
06 Santa Mariedda - San VittoreBusgray
07 Ospedale Nuovo - Ospedale Vecchio - Ospedale NuovoBusbrown
08 Poltu Cuadu - San NicolaBusorange
09 Porto Isola Bianca - Centro Citta' (Centro Martini) - Porto Isola BiancaBuspink
10 Aeroporto - Centro Citta' - AeroportoBuspurple
11 Geovillage - Centro Citta' - GeovillageBusgray
12 Via Mameli - Piazzale Cimitero BerchiddedduBusgray

This feed has 403 stops.

List every stop
  • Colcò
  • Padrongianus
  • Castello di Pedres
  • V. Fiorita Eliporto
  • Loiri
  • Zappalli
  • Via Nazionale 1
  • Via Nazionale 70
  • BASA-PARK
  • Centro Martini Parco
  • V.le Pittulongu
  • D'Annunzio caserma
  • Via D'Annunzio fronte stazione FS
  • Necropoli S.Simplicio
  • Via San Simplicio,11
  • Colcò agraria
  • Padrongianus
  • Castello di Pedres
  • Vena Fiorita
  • Loiri
  • Zappalli
  • Via Nazionale fr.1
  • Via Nazionale fr.70
  • V.le Italia-Ind
  • Mameli 6
  • V.le Pittulongu
  • Mameli Casermette
  • int. via Campidano
  • Cimitero Berchiddeddu
  • Via Ferrara civ.46
  • Via Ferrara civico 98
  • Via Ferrara fronte civico 98
  • Via Ferrara civ. 55
  • Centro Martini
  • Via D'Annunzio fronte Carabinieri
  • Via D'Annunzio stazione FS
  • Necropoli S.Simplicio
  • Via San Simplicio 6
  • Via Mameli 1
  • Mameli fr.Casermette
  • Roma fr. Campidano
  • Sa Castanza dir. Mamusi
  • Via Trainu Moltu dir. Mamusi
  • Mamusi Via Omodeo
  • Trainu Moltu dir. Olbia
  • Sa Castanza dir. Olbia
  • Via Dei Lidi fr.5
  • SP n°79 fronte civico 10
  • Via Rio sos Campitos dir. Mamusi
  • Via Rio sos Campitos dir. Olbia
  • Via Gianni Rodari
  • Battista dir.Mamusi
  • Olbia, Via Monte Aspru
  • Sos Coddos Dir. Mamusi
  • Sos Coddos dir. Olbia
  • Via Olivà Dir. Mamusi
  • Via Dei Lidi fr.69
  • Via Olivà dir. Olbia
  • Via San Vittore fronte via Faggio
  • Olbia, Via San Vittore
  • Santa Mariedda SP 38bis Civico 50
  • S. Mariedda S.P. 38 bis Civ 62
  • S.P. 38bis Bivio Campo di Pino
  • Via della Cantoniera Putzolu
  • Via della Cantoniera Putzolu
  • Via della Cantoniera int.38 bis
  • SP38 bis Inters. Via Del Nuraghe
  • Stazione Terranova
  • Olbia, Via Viterbo - Fronte Campi
  • Via San Vittore Lato Via Plebi
  • V.le Italia ZI
  • V.Forteleoni fr7
  • SP82 Pozzo sacro
  • SP82 Olbia G.Aranci
  • Via Viterbo, 9
  • Olbia, Via Imperia, 1
  • Via Loiri, Istituto I.P.A.A.
  • Mater
  • Via della Cantoniera Putzolu
  • Via Mestre 27, angolo Via Perugia
  • Nicosia
  • sp 125 lato ristorante
  • Strada Statale Orientale Sarda
  • Strada Statale Orientale Sarda 14
  • OlbiaVia Picciaredda
  • Olbia, fronte Via Picciaredda
  • SS 125, civ. 20
  • Via Monte Rosa 5
  • 2096 - Via Mosca
  • Forteleoni 17
  • Spiaggia Lo Squalo
  • Spiaggia Pellicano
  • Spiaggia Mare Rocce
  • Molo Brin
  • Capitaneria di Porto
  • V. Indonesia fr Mc
  • Fronte ASPO
  • V. Indonesia Fronte CFadda
  • Delta Center
  • Via Capo Verde 2a Ferm Direz Geov.
  • Via Corea 1a ferm. direz Geov.
  • Via Sierra Leone
  • Via Dei Lidi 5
  • Via Dei Lidi 67
  • Blumarine
  • V.le Italia Zona Ind.le
  • SP82 Pozzo Sacro
  • SP82 Olbia G. Aranci
  • Lo squalo
  • Pellicano
  • Mare Rocce
  • Comune di Olbia
  • V.le I.Bianca fronte capitaneria
  • V. Indonesia
  • Deposito ASPO
  • V. Indonesia Fronte Trony
  • V.Seychelles
  • Capo Verde dirCentro
  • V.Capo Verde 1a ferm. Direz Centro
  • Via Corea 2a fermata
  • Via Sierra Leone 1
  • Bados
  • Porto
  • Geovillage
  • A.Moro Ospedale
  • V.le A.Moro 42
  • V.le A.Moro 78 poste
  • V.le A.Moro fr.bartolo
  • V.le A.Moro ex enel
  • A.Moro 206 tropical
  • V.le A.Moro 252
  • A.Moro Romagnolo
  • V.le A.Moro ENI
  • A.Moro Case Popolari
  • V.le A.Moro fr.417
  • A.Moro fr. V.Bonn
  • V.le A.Moro V.Cairo
  • V.le A.Moro fr. 511
  • V.le Basa Terranova
  • V.le Basa Eurospin
  • V.le Basa Piscina
  • V.Leonardo Da Vinci
  • A.Moro fr.Ospedale
  • V.le A.Moro 87
  • V.le A.Moro 137
  • A.Moro 181 bartolo
  • V.le A.Moro 227
  • V.le A.Moro 245
  • V.le A.Moro fr.252
  • A.Moro Romagnolo
  • V.le A.Moro fr.ENI
  • A.Moro fr.popolari
  • V.le A.Moro 409
  • A.Moro Minda Noa
  • A.Moro fr. V.Cairo
  • V.le A.Moro 511
  • V.le Basa fr.Eurospin
  • Via Londra
  • Basa
  • SS125 Li Puntitti
  • SP73
  • SP73 Riv. Legnami
  • SP73 Vivaio
  • V.le Rudalza
  • Rudalza Pazzolu
  • Rudalza fr.rist.
  • Rudalza
  • Monte Ladu
  • Monte Ladu ristorante
  • Monte Ladu I.Piumica
  • Monte Ladu fr.St.Bide
  • Monte Ladu I Valentini
  • Monte Ladu Maiore
  • Porto Rotondo CC
  • P.Rotondo P.zza Krizia
  • SS125 ex SAFA
  • SP73 fr. Agriturismo
  • SP73 Tecnoverde
  • SP73
  • Rudalza int.SP73
  • Rudalza fr. Pazzolu
  • V.le Rudalza rist.
  • Rudalza
  • Monte Ladu edicola
  • Monte Ladu rist.
  • V.M.Ladu fr. I.Piumica
  • V.Monte Ladu St. Bide
  • Monte Ladu Valentini
  • V.Monte Ladu
  • P.Rotondo Farmacia
  • P.Rotondo Tartarughino
  • Porto Rotondo
  • Via Galvani 12A
  • Via Galvani 78
  • Via Petta incrocio Piro
  • Via Petta 60
  • Via Petta 51
  • Via Euclide fr. 12
  • Veronese Gramsci
  • Veronese V.Pisano
  • Via Veronese Vignola
  • Via Veronese Lamberti
  • Via Veronese Dei Pini
  • Veronese fr.Dei Fiori
  • Plebi fr.V.Abba Fritta
  • Via Plebi Santa Lucia
  • V.Plebi S.Lucia
  • V.S.Vittore fr.Chidonza
  • S.Vittore 2a fermata
  • S.Vittore 3a fermata
  • S.Vittore 4a fermata
  • S.Vittore Chinzana
  • S.Vittore fr.Sa Istrana
  • Via Plebi Culatolzu
  • Via Galvani fr. 14
  • Via Galvani fr. 78
  • Petta Croce Bianca
  • Via Petta fr. 60
  • Plebi Via Abba Fritta
  • Plebi fr. Santa Lucia
  • San Nicola
  • San Vittore
  • Via Brigata Sassari
  • Barcellona V.Rossini
  • Barcellona Porpora
  • Barcellona fr.Nassiria
  • Via Barc. fr. 157
  • Via De Sanctis
  • Via Correggio V.Corelli
  • Via Correggio Gregorio
  • Via Vesuvio
  • Corso Vittorio Veneto fr.ENI
  • Corso Vittorio Veneto V.Emilia
  • Corso Vittorio Veneto A.Adige
  • Corso Vittorio Veneto Campania
  • Veneto fr.Toti
  • C.so V. Veneto Diaz
  • Via Cesti
  • Via Tre Venezie LD
  • Tre Venezie 2a fer.
  • Via Bazzoni ASL
  • Via Bazzoni
  • via Bazzoni (Chiesa)
  • S.Lucia San Vittore
  • Santa Lucia V.Pegaso
  • V.S.Lucia 3a fermata
  • V.S.Lucia fr.V.Lattea
  • V.S.Lucia V.Del Grano
  • V.Santa Lucia
  • V.F.Noce S.Simplicio
  • and 153 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

13 findings, ordered by severity.

Show every finding
  • Error3 instances

    Trip distance exceeds shape distance (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: trip_distance_exceeds_shape_distance · See MobilityData GTFS Validator rules

  • Warning15102 instances

    Missing timepoint value (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: missing_timepoint_value · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning403 instances

    403 of 403 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.)

    Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning395 instances

    395 of 395 trips don't say whether the vehicle is wheelchair accessible.

    Even with accessible stops, riders need to know the bus 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.)

    Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning353 instances

    Some scheduled trips move faster between stops than a bus can.

    Usually a typo'd stop time; riders get arrival times no bus can meet.

    Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)

    Validator rule: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning161 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.)

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

  • Warning11 instances

    Stop too far from shape using user distance (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

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

  • Warning11 instances

    Trip distance exceeds shape distance below threshold (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning4 instances

    Some route colors don't contrast with their text color.

    Route badges get hard to read, most of all for riders with low vision.

    Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)

    Validator rule: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning2 instances

    Stops match shape out of order (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules

  • Warning1 instance

    Some service calendars in the feed have already ended.

    Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.

    Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)

    Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    Leading or trailing whitespaces (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: leading_or_trailing_whitespaces · 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.)

    Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices

Conformance mark Not yet

This feed is close to the conformance mark. 1 validator error to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Not yet
1 validator error to resolve.
Current Met
Service data covers the next 59 days.
Accessible Not yet
States wheelchair access on 0% of stops and 0% 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 59 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 3 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 36 / 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 98 / 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 45 / 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.

ASPO (Olbia urban bus) 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/aspo-olbia/2026-07-18.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-07-18. 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.