Search
  1. Home
  2. Italy Feeds
  3. alilaguna
  4. Source Data Validation Report

alilaguna — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-04T10:44:46Z,
for the dataset file:///shared/alilaguna_8b7d5b8c.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Alilaguna S.p.A.
Feed Email:
transit@alilaguna.it
Feed Language:
Italian
Feed Start Date:
2025-11-04
Feed End Date:
2026-04-30

Files included

  1. agency.txt
  2. calendar.txt
  3. fare_attributes.txt
  4. fare_rules.txt
  5. feed_info.txt
  6. routes.txt
  7. shapes.txt
  8. stop_times.txt
  9. stops.txt
  10. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 2
  • Shapes: 7
  • Stops: 34
  • Trips: 119

Specification Compliance report

122 notices reported (0 errors, 122 warnings, 0 infos)

Notice Code Severity Total
expired_calendar WARNING 1

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
2 "WD"
feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20260504" "20260430" "20260511"
missing_bike_allowance WARNING 119

missing_bike_allowance

Ferry trips should include bike allowance information.

All ferry trips should have a valid value in the bikes_allowed field in trips.txt.

You can see more about this notice here.

Only the first 50 of 119 affected records are displayed below.

csvRowNumber (?) The row number of the faulty record. routeId (?) The faulty record's route id. tripId (?) The faulty record's trip id.
57 "B" "B_AERO_FERR_1"
58 "B" "B_AERO_FERR_2"
59 "B" "B_AERO_FERR_3"
60 "B" "B_AERO_FERR_4"
61 "B" "B_AERO_FERR_5"
62 "B" "B_AERO_FERR_6"
63 "B" "B_AERO_FERR_7"
64 "B" "B_AERO_FERR_8"
65 "B" "B_AERO_FERR_9"
66 "B" "B_AERO_FERR_10"
67 "B" "B_AERO_FERR_11"
68 "B" "B_AERO_FERR_12"
69 "B" "B_AERO_FERR_13"
70 "B" "B_AERO_FERR_14"
71 "B" "B_AERO_FERR_15"
72 "B" "B_AERO_FERR_16"
73 "B" "B_AERO_FERR_17"
74 "B" "B_AERO_FERR_18"
75 "B" "B_AERO_FERR_19"
76 "B" "B_AERO_FERR_20"
77 "B" "B_AERO_FERR_21"
78 "B" "B_AERO_FERR_22"
79 "B" "B_AERO_FERR_23"
80 "B" "B_AERO_FERR_24"
81 "B" "B_AERO_FERR_25"
82 "B" "B_AERO_FERR_26"
83 "B" "B_AERO_FERR_27"
84 "B" "B_AERO_FERR_28"
85 "B" "B_AERO_FERR_29"
86 "B" "B_AERO_FERR_30"
87 "B" "B_AERO_FERR_31"
88 "B" "B_AERO_FERR_32"
89 "B" "B_AERO_FERR_33"
90 "B" "B_FERR_AERO_1"
91 "B" "B_FERR_AERO_2"
92 "B" "B_FERR_AERO_3"
93 "B" "B_FERR_AERO_4"
94 "B" "B_FERR_AERO_5"
95 "B" "B_FERR_AERO_6"
96 "B" "B_FERR_AERO_7"
97 "B" "B_FERR_AERO_8"
98 "B" "B_FERR_AERO_9"
99 "B" "B_FERR_AERO_10"
100 "B" "B_FERR_AERO_11"
101 "B" "B_FERR_AERO_12"
102 "B" "B_FERR_AERO_13"
103 "B" "B_FERR_AERO_14"
104 "B" "B_FERR_AERO_15"
105 "B" "B_FERR_AERO_16"
106 "B" "B_FERR_AERO_17"
trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format). serviceWindowStartDate (?) The start date of the majority service window. serviceWindowEndDate (?) The end date of the majority service window.
"20260504" "20251104" "20260430"