Feed status · checked 2026-09-01
ASPO (Olbia urban bus)
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-08-31
Catalogued in Sardegna, Italy.
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.
Checked for changes 4 hours ago; last changed 4 days ago.
Measured 3 of 4 score categories from the feed URL on file (publisher not verified).
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 configured feed URL. Publisher ownership of that URL is not verified.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
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
423 of 423 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
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
496 of 496 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
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
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
- 423 of 423 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
- Feed evidence
- 496 of 496 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
- 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
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.
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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.
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 121 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
The MobilityData validator flagged 8 kinds of issue across 19111 instances (0 error, 19111 warning, 0 informational).
Service data covers the next 121 days.
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.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
13 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.
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 423 stops.
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.
- 01 (red)
- 02 (pink)
- 03 (teal)
- 04 (white)
- 05 (green)
- 05PI (green)
- 05PR (white)
- 06 (gray)
- 07 (brown)
- 08 (orange)
- 09 (pink)
- 10 (purple)
- 11 (gray)
- 12 (gray)
- 1S (red)
- 2S (pink)
- 4S (white)
| Route | Type | Line color |
|---|---|---|
| 01 Sa Marinedda - Basa | Bus | red |
| 02 Mater - Via Nicosia | Bus | pink |
| 03 Caresi - Centro (Ponte di Ferro - Via Roma) - Caresi | Bus | teal |
| 04 Via G. Vico (Ex Tribunale) - Bados | Bus | white |
| 05 Porto Istana - Porto Rotondo | Bus | green |
| 05PI Porto Istana - Olbia | Bus | green |
| 05PR Porto Rotondo - Olbia | Bus | white |
| 06 Santa Mariedda - San Vittore | Bus | gray |
| 07 Ospedale Nuovo - Ospedale Vecchio - Ospedale Nuovo | Bus | brown |
| 08 Poltu Cuadu - San Nicola | Bus | orange |
| 09 Porto Isola Bianca - Centro Citta' (Centro Martini) - Porto Isola Bianca | Bus | pink |
| 10 Aeroporto - Centro Citta' - Aeroporto | Bus | purple |
| 11 Geovillage - Centro Citta' - Geovillage | Bus | gray |
| 12 Via Mameli - Piazzale Cimitero Berchiddeddu | Bus | gray |
| 1S Sa Marinedda - Basa (servizio scolastico) | Bus | red |
| 2S Sa Minda Noa- Via Vicenza- Sa Marinedda- Delta Center (servizio scolastico) | Bus | pink |
| 4S RINFORZO SCOLASTICO LINEA 4 | Bus | white |
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
- Via San Severino
- 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
- Cala Saccaia
- V.Forteleoni fr7
- Pozzo Sacro
- SP82 Pozzo sacro
- SP82 Olbia G.Aranci
- Via Viterbo, 9
- Olbia, Via Imperia, 1
- Via Loiri, Istituto I.P.A.A.
- S.Vitt. fr Plebi
- 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
- V.Seychelles
- 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
- Cala Saccaia
- Pozzo Sacro
- 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
- 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
- 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
- Veronese fr.Gramsci
- Veronese fr. Pisano
- Veronese fr.Vignola
- Veronese fr.Lamberti
- Veronese fr. Dei Pini
- Veronese via dei Fiori
- Plebi Via Abba Fritta
- Plebi fr. Santa Lucia
- San Vittore Chidonza
- Via San Vittore 2a fer.
- Via San Vittore
- Via San Vittore 4a fer.
- V.S.Vittore fr.Chinzana
- San Vittore Sa Istrana
- Via Plebi Culatolzu
- 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
- and 173 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-08-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 46.5 | first check |
| 2026-08-07 | 46.1 | down 0.4 |
| 2026-08-31 | 61.8 | up 15.7 |
| 2026-09-01 | 61.8 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-08-31.
Same feed file as 2026-08-31; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
What changed over time
On 2026-08-06 this feed started at grade F. On 2026-08-31 the grade moved from F to D. On 2026-08-31 the check no longer reported: some service calendars in the feed have already ended; trip distance exceeds shape distance (flagged by the MobilityData validator). As of 2026-09-01 it holds grade D.
A plain-language history of this feed, newest first.
- 2026-08-31 Grade went F to D, freshness rose 35 points.
Everything we checked
11 findings, ordered by severity.
Show every finding
- Warning18461 instances
Some rows in stop_times.txt leave the timepoint column blank.
That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises.
Fix: Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1. (Usually one export setting.)
Finding code: missing_timepoint_value · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning496 instances
496 of 496 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.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning423 instances
423 of 423 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 (opens the GTFS Schedule reference on an external site)
- Warning374 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.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning244 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 (opens the validator rules on an external site)
- Warning15 instances
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning10 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 streets or point riders to the wrong corner.
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 (opens the validator rules on an external site)
- 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.)
Finding code: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some values have extra spaces at the start or end.
A stray space can break a match, so a stop or route may fail to link across files.
Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)
Finding code: leading_or_trailing_whitespaces · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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 (opens GTFS Best Practices on an external site)
Conformance mark Not yet
One requirement remains for this feed to earn the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 121 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 121 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
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 52 / 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 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.
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-09-01.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-01. 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.