GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-22T10:11:17Z,
for the dataset file:///shared/baltimore-water-taxi.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Baltimore Water Taxi
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
N/A
Feed End Date:
N/A

Files included

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

Counts

  • Agencies: 0
  • Blocks: 0
  • Routes: 8
  • Shapes: 18
  • Stops: 13
  • Trips: 362

Specification Compliance report

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

Notice Code Severity Total
expired_calendar WARNING 7

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 "69693"
3 "69694"
4 "69695"
5 "35339"
6 "69750"
7 "35111"
8 "35110"
missing_bike_allowance WARNING 156

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 156 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.
2 "24958" "3368963"
3 "24958" "3368964"
4 "24958" "3368965"
5 "24958" "3368966"
6 "24958" "3368967"
7 "24958" "3368968"
8 "24958" "3368969"
9 "24958" "3368970"
10 "24958" "3368971"
11 "24958" "3368972"
12 "24958" "3368993"
13 "24958" "3368994"
14 "24958" "3368995"
15 "24958" "3368996"
16 "24958" "3368997"
17 "24958" "3368998"
18 "24958" "3368999"
19 "24958" "3369000"
20 "24958" "3369001"
21 "24958" "3369002"
22 "24958" "3369003"
23 "24958" "3369004"
24 "24958" "3369005"
25 "24958" "3369006"
26 "24958" "3369007"
27 "24958" "3369008"
28 "24958" "3369009"
29 "24958" "3369010"
30 "24958" "3369011"
31 "24958" "3369012"
32 "24958" "3467896"
33 "24958" "3467898"
34 "24958" "3467899"
35 "24959" "3369048"
36 "24959" "3369049"
37 "24959" "3369050"
38 "24959" "3369051"
39 "24959" "3369052"
40 "24959" "3369053"
41 "24959" "3369054"
42 "24959" "3369055"
43 "24959" "3369056"
44 "24959" "3369057"
45 "24959" "3369058"
46 "24959" "3369059"
47 "24959" "3369060"
48 "24959" "3369061"
49 "24959" "3369062"
50 "24959" "3369063"
51 "24959" "3369064"
missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2
missing_recommended_field WARNING 12

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"agency.txt" 2 "agency_id"
"feed_info.txt" 2 "feed_start_date"
"feed_info.txt" 2 "feed_end_date"
"feed_info.txt" 2 "feed_version"
"routes.txt" 2 "agency_id"
"routes.txt" 3 "agency_id"
"routes.txt" 4 "agency_id"
"routes.txt" 5 "agency_id"
"routes.txt" 6 "agency_id"
"routes.txt" 7 "agency_id"
"routes.txt" 8 "agency_id"
"routes.txt" 9 "agency_id"
route_long_name_contains_short_name WARNING 5

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name Dataset
"N"/"Judah" Muni San Fransisco
"6"/"ML King Jr Blvd" Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent" STM Montreal
"1"/"Rangiora/Cashmere" Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeShortName (?) The faulty record's `route_short_name`. routeLongName (?) The faulty record's `route_long_name`.
"24958" 2 "Yellow" "Yellow Route"
"24959" 3 "Red" "Red Route"
"24960" 4 "Blue" "Blue Route"
"24961" 5 "Purple" "Purple Route"
"24957" 9 "Green" "Green Route"
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.
"20251222" "20180321" "20180919"
unused_shape WARNING 1

unused_shape

Shape is not used in GTFS file trips.txt.

All records defined by GTFS shapes.txt should be used in trips.txt.

You can see more about this notice here.

shapeId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"80855" 166