Home
United States Feeds
lbt-water-taxi
Source Data Validation Report

lbt-water-taxi — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-22T02:55:19Z,
for the dataset file:///shared/lbt-water-taxi_b7654c66.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Long Beach Transit
- website: https://ridelbt.com
- phone number: (562) 591-2301
- email: Not provided

Feed Info

Publisher Name:
Long Beach Transit: Publisher URL:
https://www.ridelbt.com: Feed Email:
N/A: Feed Language:
English: Feed Start Date:
2026-05-22: Feed End Date:
2026-09-07: Service Window:
2026-05-22 to 2026-09-07 (?) The range of service dates covered by the feed, based on trips with an associated service_id in calendar.txt and/or calendar_dates.txt

Files included

agency.txt
calendar.txt
calendar_dates.txt
fare_attributes.txt
fare_leg_rules.txt
fare_media.txt
fare_products.txt
fare_rules.txt
feed_info.txt
networks.txt
rider_categories.txt
route_networks.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 5
Routes: 2
Shapes: 4
Stops: 4
Trips: 70

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

ShapesFeed InformationFares V1Fare ProductsRoute ColorsHeadsignsLocation TypesRoute-Based FaresFare MediaRider Categories

Specification Compliance report

82 notices reported (4 errors, 78 warnings, 0 infos)

Notice Code Severity Total

foreign_key_violation ERROR 4

foreign_key_violation

Wrong foreign key.

A foreign key references the primary key of another file. A foreign key violation means that the foreign key referenced from a given row (the child file) cannot be found in the corresponding file (the parent file). The Foreign keys are defined in the specification under "Type" for each file.

You can see more about this notice here.

childFilename (?) The name of the file from which reference is made.	childFieldName (?) The name of the field that makes reference.	parentFilename (?) The name of the file that is referred to.	parentFieldName (?) The name of the field that is referred to.	fieldValue (?) The faulty record's value.	csvRowNumber (?) The row of the faulty record.
"fare_products.txt"	"fare_media_id"	"fare_media.txt"	"fare_media_id"	"0"	2
"fare_products.txt"	"fare_media_id"	"fare_media.txt"	"fare_media_id"	"0"	3
"fare_products.txt"	"fare_media_id"	"fare_media.txt"	"fare_media_id"	"3"	4
"fare_products.txt"	"fare_media_id"	"fare_media.txt"	"fare_media_id"	"3"	5

equal_shape_distance_same_coordinates WARNING 3

equal_shape_distance_same_coordinates

Two consecutive points have equal shape_dist_traveled and the same lat/lon coordinates in shapes.txt.

When sorted by shape.shape_pt_sequence, the values for shape_dist_traveled must increase along a shape. Two consecutive points with equal values for shape_dist_traveled and the same coordinates indicate a duplicative shape point.

You can see more about this notice here.

shapeId (?) The id of the faulty shape.	csvRowNumber (?) The row number from `shapes.txt`.	shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record.	shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`.	prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point.	prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous shape point.	prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`.
"AB0003"	18	0.249	20001	17	0.249	10016
"AL0003"	95	0.214	10018	94	0.214	10017
"AL0003"	110	0.7	20001	109	0.7	10032

feed_expiration_date30_days WARNING 1

feed_expiration_date30_days

Dataset should cover at least the next 30 days of service.

At any time, the GTFS dataset should cover at least the next 30 days of service, and ideally for as long as the operator is confident that the schedule will continue to be operated.

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	"20260822"	"20260907"	"20260921"

missing_bike_allowance WARNING 70

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 70 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	"AB-188"	"10673096"
3	"AB-188"	"10673097"
4	"AB-188"	"10673098"
5	"AB-188"	"10673099"
6	"AB-188"	"10673100"
7	"AB-188"	"10673101"
8	"AB-188"	"10673102"
11	"AB-188"	"10673105"
12	"AB-188"	"10673106"
15	"AB-188"	"10673109"
16	"AB-188"	"10673110"
17	"AB-188"	"10673111"
18	"AB-188"	"10673112"
19	"AB-188"	"10673113"
20	"AB-188"	"10673114"
21	"AB-188"	"10673115"
22	"AB-188"	"10673116"
23	"AB-188"	"10673117"
24	"AB-188"	"10673118"
25	"AB-188"	"10673119"
26	"AB-188"	"10673120"
27	"AB-188"	"10673121"
33	"AB-188"	"10673057"
34	"AB-188"	"10673058"
35	"AB-188"	"10673059"
36	"AB-188"	"10673060"
37	"AB-188"	"10673061"
38	"AB-188"	"10673062"
39	"AB-188"	"10673063"
40	"AB-188"	"10673064"
41	"AB-188"	"10673065"
42	"AB-188"	"10673066"
43	"AB-188"	"10673067"
44	"AB-188"	"10673068"
45	"AB-188"	"10673069"
46	"AB-188"	"10673070"
47	"AB-188"	"10673071"
48	"AB-188"	"10673072"
49	"AB-188"	"10673073"
50	"AB-188"	"10673074"
51	"AB-188"	"10673075"
52	"AB-188"	"10673076"
53	"AB-188"	"10673077"
54	"AB-188"	"10673078"
9	"AL-188"	"10673103"
10	"AL-188"	"10673104"
13	"AL-188"	"10673107"
14	"AL-188"	"10673108"
28	"AL-188"	"10673122"
29	"AL-188"	"10673123"

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 1

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.
"feed_info.txt"	2	"feed_version"

route_long_name_contains_short_name WARNING 2

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`.
"AB-188"	2	"AquaBus"	"AquaBus"
"AL-188"	3	"AquaLink"	"AquaLink"