GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T20:57:23Z,
for the dataset file:///shared/newark-airtrain-nj.zip. No country code was provided.

Summary

Agencies included

Port Authority of New York and New Jersey
- website: https://www.panynj.gov/
- phone number: 1-800-234-7284
- email: Not provided

Feed Info

Publisher Name:
Transitland: Publisher URL:
https://www.transit.land/: Feed Email:
hello@transit.land: Feed Language:
English: Feed Start Date:
2024-01-01: Feed End Date:
2030-12-31: Service Window:
2024-01-01 to 2030-12-31 (?) 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

LICENSE.txt
agency.txt
areas.txt
calendar.txt
fare_leg_rules.txt
fare_products.txt
feed_info.txt
frequencies.txt
rider_categories.txt
routes.txt
shapes.txt
stop_areas.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 1
Shapes: 1
Stops: 5
Trips: 2

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

Shapes Frequencies Feed Information Fare Products Zone-Based Fares Rider Categories Route Colors Headsigns Stops Wheelchair Accessibility Trips Wheelchair Accessibility Bike Allowed Location Types

Specification Compliance report

11 notices reported (0 errors, 4 warnings, 7 infos)

Notice Code

Severity

Total

route_long_name_contains_short_name

WARNING

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`.
"AIR_TRAIN"	2	"AirTrain"	"AirTrain Newark"

stops_match_shape_out_of_order

WARNING

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`.	shapeId (?) The id of the shape that is referred to.	tripId (?) The id of the trip that is referred to.	stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`.	stopId1 (?) The id of the first stop that is referred to.	stopName1 (?) The name of the first stop that is referred to.	match1 (?) Latitude and longitude pair of the first matching location.	stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`.	stopId2 (?) The id of the second stop that is referred to.	stopName2 (?) The name of the second stop that is referred to.	match2 (?) Latitude and longitude pair of the second matching location.
2	"shape_airtrain_newark"	"AIR_TRAIN_1"	6	"AIRLINK"	"AirTrain Rail Link"	[40.704132971633335,-74.1901960168362]	5	"TERM_A"	"Terminal A"	[40.687356,-74.190838]
3	"shape_airtrain_newark"	"AIR_TRAIN_2"	9	"TERM_B"	"Terminal B"	[40.69079297181404,-74.17669901627858]	8	"TERM_A"	"Terminal A"	[40.687356,-74.190838]

unexpected_enum_value

WARNING

unexpected_enum_value

An enum has an unexpected value.

You can see more about this notice here.

filename (?) The name of the faulty file.	csvRowNumber (?) The row number of the faulty record.	fieldName (?) The name of the field where the error occurred.	fieldValue (?) Faulty value.
"routes.txt"	2	"route_type"	405

unknown_column

INFO

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file.	fieldName (?) The name of the unknown column.	index (?) The index of the faulty column.
"fare_leg_rules.txt"	"fare_leg_rule_id"	1
"fare_leg_rules.txt"	"rider_category_id"	3
"fare_leg_rules.txt"	"from_zone_id"	7
"fare_leg_rules.txt"	"to_zone_id"	8
"rider_categories.txt"	"min_age"	3
"rider_categories.txt"	"max_age"	4

unknown_file

INFO

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"LICENSE.txt"