GTFS Scorecard
← All agencies

Feed status · checked 2026-07-18

ACTV Venezia (vaporetto navigation)

Based on the feed this agency publishes

Service mode Ferry

56.0 / 100

First scorecard for this agency

Catalogued in Veneto, Italy.

Covers 44 daysAccessibility gapsRealtime not yet published

The waterborne vaporetto network, a distinct published feed from the same organization as the road network record.

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

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

154 of 154 terminals 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 02

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

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

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

Fix 03

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

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. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every terminal. A field survey can start with the busiest terminals. · 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.

  2. 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.

  3. 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.

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 44 days.
Published accessibility data
Accessibility information is stated for 0% of terminals and 0% of trips. This measures published data, not whether terminals or vessels 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.

Ungraded capability read

Ferry data profile

A ferry-specific view of what this GTFS feed publishes. Schedule measurements use ferry routes and trips only; fare and realtime facts are labelled as whole-feed. Unknown values are not treated as no.

Ferry service
25 routes · 14,461 trips
Terminal structure
140 ferry boarding locations; no parent-station hierarchy is published.
Terminal access
Not applicable: no ferry boarding location is linked to a parent station, so stop_access is not permitted here.
Published accessibility
Unknown: none of the 140 ferry boarding locations publish wheelchair_boarding. Unknown: none of the 14,461 ferry trips publish wheelchair_accessible. This reports published values, not verified physical usability.
Bicycles
Unknown: none of the 14,461 ferry trips publish bikes_allowed.
Cars
Unknown: none of the 14,461 ferry trips publish cars_allowed.
Fares
Whole feed: no applied fare data is published. This is not evidence that ferry service is free.
Realtime
Whole feed: no GTFS-Realtime endpoints are configured in this scorecard.

Descriptive only. This profile does not change the grade or verify vessels, terminal facilities, vehicle carriage, fares, or accessibility in the real world. Field meanings follow the GTFS Schedule reference.

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

Correctness59.2 / 100

The MobilityData validator flagged 8 kinds of issue across 169761 instances (0 error, 169732 warning, 29 informational).

Freshness73.3 / 100

Service data covers the next 44 days.

Rider experience37.5 / 100

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

Accessibility0 / 100

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

1 accessibility depth signal

  • 7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (15, 17, 7, 9, 22, 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.

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 terminals

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

Skip to route and terminal data

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

  • 10 (teal)
  • 11 (white)
  • 12 (yellow)
  • 13 (purple)
  • 14 (orange)
  • 15 (orange)
  • 17 (gray)
  • 18 (yellow)
  • 1 (white)
  • 2/ (red)
  • 20 (white)
  • 22 (yellow)
  • 2 (red)
  • 3 (yellow)
  • 4.1 (pink)
  • 4.2 (pink)
  • 5.1 (gray)
  • 5.2 (gray)
  • 6 (teal)
  • 7 (green)
  • 8 (brown)
  • 9 (brown)
  • NLN (blue)
  • NMU (blue)
  • N (blue)
Routes in ACTV Venezia (vaporetto navigation)'s feed
RouteTypeLine color
10 Lido S.M.E. "E" - Zattere "B"Ferryteal
11 Pellestrina Cimitero - ChioggiaFerrywhite
12 Punta Sabbioni "A" - F.te Nove "A"Ferryyellow
13 F.te Nove "D" - TreportiFerrypurple
14 S. Marco-San Zaccaria "A" - Punta Sabbioni "B"Ferryorange
15 S. Marco-San Zaccaria "A" - Punta Sabbioni "A"Ferryorange
17 Punta Sabbioni - Lido S. Nicolo' FerryFerrygray
18 Murano Navagero - Murano NavageroFerryyellow
1 Arsenale "B" - Lido S.M.E. "D"Ferrywhite
2/ P.le Roma "F" - Rialto "D"Ferryred
20 S. Servolo - S. Marco-San Zaccaria "B"Ferrywhite
22 Punta Sabbioni "A" - F.te Nove "C"Ferryyellow
2 S. Marco-San Zaccaria "B" - Lido S.M.E. "E"Ferryred
3 P.le Roma "D" - P.le Roma "E"Ferryyellow
4.1 Giardini Biennale "B" - Murano Museo "A"Ferrypink
4.2 P.le Roma "D" - F.te Nove "B"Ferrypink
5.1 Lido S.M.E. "A" - F.te Nove "C"Ferrygray
5.2 F.te Nove "D" - Lido S.M.E. "A"Ferrygray
6 P.le Roma "B" - Lido S.M.E. "B"Ferryteal
7 S. Marco-San Zaccaria "E" - S. Marco-San Zaccaria "E"Ferrygreen
8 S. Basilio - Lido S. Nicolo'Ferrybrown
9 Burano "A" - TorcelloFerrybrown
NLN F.te Nove "D" - TreportiFerryblue
NMU F.te Nove "B" - F.te Nove "B"Ferryblue
N Punta Sabbioni "B" - Lido S.M.E. "C"Ferryblue

This feed has 154 terminals.

List every terminal
  • Ospedale
  • Punta Sabbioni Ferry
  • Deposito Tronchetto
  • Vignole A RICHIESTA
  • Lido S.M.E. "B"
  • Lido S.M.E. "C"
  • Lido S.M.E. "D"
  • S.Elena-Stadio Penzo "B"
  • S.Elena-Stadio Penzo "C"
  • Giardini Biennale "B"
  • Giardini "B"
  • Arsenale "A"
  • S. Marco-San Zaccaria "A"
  • S. Marco-San Zaccaria "D"
  • S. Marco-San Zaccaria "C"
  • S. Marco-San Zaccaria "F"
  • S. Marco-San Zaccaria "E"
  • S. Marta
  • Caroman
  • Certosa
  • Celestia
  • Ospedale
  • S. Giorgio
  • Giudecca Palanca "B"
  • Sacca Fisola "A"
  • Tronchetto "B"
  • Tronchetto "A"
  • Tronchetto Ferry
  • P.le Roma "C"
  • P.le Roma "E"
  • P.le Roma "D"
  • P.le Roma "F"
  • P.le Roma "G"
  • Ferrovia "B"
  • Ferrovia "A"
  • Riva de Biasio "B"
  • S. Marcuola-Casino' "A"
  • S. Stae
  • Ca' d'Oro
  • Rialto "D"
  • Rialto "C"
  • Rialto "B"
  • S. Silvestro
  • S. Angelo
  • S. Toma' "B"
  • S. Toma' "A"
  • Ca' Rezzonico
  • S. Samuele
  • Accademia "B"
  • Accademia "A"
  • Zattere "B"
  • Zattere "A"
  • S. Maria del Giglio
  • Salute
  • S. Marco Vallaresso "B"
  • S. Marco Vallaresso "A"
  • S. Marco Giardinetti "A"
  • Orto
  • S. Alvise
  • F.te Nove "C"
  • F.te Nove "B"
  • Cimitero San Michele
  • Murano Colonna "A"
  • Murano Navagero
  • Murano Museo "A"
  • Murano Venier
  • Murano Serenella
  • Burano "B"
  • Treporti
  • Punta Sabbioni "B"
  • Ferrovia
  • Chioggia
  • Pellestrina Cimitero
  • Tronchetto Mercato
  • S. Marco-San Zaccaria "B"
  • S. Servolo
  • S. Lazzaro
  • Zitelle "B"
  • Redentore
  • S. Basilio
  • Guglie "A"
  • Tre Archi
  • F.te Nove "A"
  • F.te Nove "D"
  • Ferrovia "C"
  • Ferrovia "D"
  • Vignole
  • S. Erasmo Capannone
  • S. Erasmo Chiesa
  • S. Erasmo Punta Vela
  • Lido S.M.E. "A"
  • Murano Faro "B"
  • Murano Faro "A"
  • Torcello
  • Lido S. Nicolo'
  • Lido S. Nicolo' Ferry
  • Mazzorbo
  • S. Maria del Mare Ferry
  • Alberoni Faro Rocchetta
  • P.le Roma "B"
  • Punta Sabbioni "A"
  • Punta Sabbioni
  • S.Erasmo Forte Mass.
  • P.le Roma "A"
  • Burano "C"
  • Murano Colonna "B"
  • Bacini - Arsenale Nord
  • S. Pietro di Castello
  • Zitelle "A"
  • Murano Museo "B"
  • Murano Colonna "C"
  • Giardini "A"
  • Deposito Arsenale
  • Giardini Biennale "A"
  • Giudecca Palanca "A"
  • S. Marcuola-Casino' "B"
  • Arsenale "B"
  • Crea
  • Riva de Biasio "A"
  • Zattere Gesuati
  • Rialto Mercato
  • Sacca Fisola "B"
  • Deposito Tronchetto
  • S.Elena-Stadio Penzo "D"
  • Deposito F.te Nove
  • Deposito S. Elena
  • Burano "A"
  • Lido S.M.E. "E"
  • Parcheggio Cantiere S.Ele
  • Deposito Chioggia P.tta V
  • Deposito S.Nicolo'
  • Parcheggio Lido
  • Parcheggio P.le Roma
  • Lido S.M.E. "C"
  • Spirito Santo
  • Deposito Pieta'
  • Rialto "A"
  • Guglie "B"
  • Ferrovia "E"
  • S. Marco-San Zaccaria"B1"
  • S. Marco-San Zaccaria "B"
  • Tronchetto Mercato
  • S. Giobbe
  • Lazzaretto N. A RICHIESTA
  • Certosa A RICHIESTA
  • Celestia A RICHIESTA
  • S. Giorgio A RICHIESTA
  • Vignole A RICHIESTA
  • Torcello A RICHIESTA
  • Lido S.Nicolo' A RICHIEST
  • Bacini A RICHIESTA
  • Caroman A RICHIESTA
  • S. Servolo A RICHIESTA
  • Capannone. A RICHIESTA

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

12 findings, ordered by severity.

Show every finding
  • Warning155247 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

  • Warning14461 instances

    Missing bike allowance (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: missing_bike_allowance · See MobilityData GTFS Validator rules

  • Warning14461 instances

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

    Even with accessible terminals, riders need to know the vessel 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

  • Warning154 instances

    154 of 154 terminals 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 terminal. A field survey can start with the busiest terminals. (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

  • Warning14 instances

    Some terminals exist in the feed but no trip serves them.

    Riders may go to a terminal where no vessel is scheduled to arrive.

    Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)

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

  • Warning7 instances

    Equal shape distance same coordinates (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

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

  • Warning1 instance

    Missing feed contact email and url (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

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

  • Warning1 instance

    Some files leave out fields that GTFS asks for but does not require.

    Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.

    Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)

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

  • Warning1 instance

    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

  • 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

  • Info29 instances

    Some files contain columns that are not part of the GTFS spec.

    Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

    Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)

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

  • Info1 instance

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

    Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.

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

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

Conformance mark Not yet

This feed is close to the conformance mark. States wheelchair access on 0% of terminals and 0% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 44 days.
Accessible Not yet
States wheelchair access on 0% of terminals 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 terminal and trip is wheelchair accessible.

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

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

  • 14 of 154 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

Clears the Google and Apple Maps four-week coverage bar. This feed has 44 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 59 / 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 73 / 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 38 / 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.

ACTV Venezia (vaporetto navigation) 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/actv-venezia-navigazione/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.