GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-13T02:47:12Z,
for the dataset file:///shared/niagararegion.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


  • Niagara Region Transit

Feed Info


Publisher Name:
Niagara Region Transit
Publisher URL:
http://nrtransit.ca
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2025-12-05
Feed End Date:
2026-01-03

Files included


  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. fare_attributes.txt
  5. fare_rules.txt
  6. feed_info.txt
  7. frequencies.txt
  8. routes.txt
  9. shapes.txt
  10. stop_times.txt
  11. stops.txt
  12. transfers.txt
  13. trips.txt

Counts


  • Agencies: 1
  • Blocks: 926
  • Routes: 100
  • Shapes: 268
  • Stops: 1865
  • Trips: 26785

Specification Compliance report

25494 notices reported (0 errors, 25494 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.
22 "21"
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 "20251213" "20260103" "20260112"
leading_or_trailing_whitespaces WARNING 572

leading_or_trailing_whitespaces

The value in CSV file has leading or trailing whitespaces.

This notice is emitted for values protected with double quotes since whitespaces for non-protected values are trimmed automatically by CSV parser.

The validator strips whitespaces from protected values. We do not see any use case when such a whitespace may be needed. On the other hand, some real-world feeds use trailing whitespaces for some values and omit them for the others. This is causing the largest problem when a primary key and a foreign key differ just by a whitespace: it is clear that they are intended to be the same, that is why we always strip whitespaces.

You can see more about this notice here.

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

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) Faulty record's field name. fieldValue (?) Faulty value.
"stop_times.txt" 7309 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7310 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7311 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7312 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7313 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7314 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7315 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7316 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7317 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7318 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7319 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7320 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7321 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7322 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7323 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7324 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7325 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7326 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7327 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7328 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7329 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7330 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7331 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 7332 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 8737 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 8738 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 8739 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 8740 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 8741 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 8742 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 8743 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 8744 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 8745 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 8746 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 8747 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 8748 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 11689 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 11690 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 11691 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 11692 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 11693 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 11694 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 11695 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 11696 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 11697 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 11698 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 11699 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 11700 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 11701 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
"stop_times.txt" 11702 "stop_headsign" "THOROLD STONE ROAD - TOWN & COUNTRY PLAZA "
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.
"fare_attributes.txt" 2 "agency_id"
mixed_case_recommended_field WARNING 24892

mixed_case_recommended_field

This field has customer-facing text and should use Mixed Case (should contain upper and lower case letters).

This field contains customer-facing text and should use Mixed Case (upper and lower case letters) to ensure good readability when displayed to riders. Avoid the use of abbreviations throughout the feed (e.g. St. for Street) unless a location is called by its abbreviated name (e.g. “JFK Airport”). Abbreviations may be problematic for accessibility by screen reader software and voice user interfaces.

Good examples:
Field Text Dataset
"Schwerin, Hauptbahnhof" Verkehrsverbund Berlin-Brandenburg
"Red Hook/Atlantic Basin" NYC Ferry
"Campo Grande Norte" Carris
Bad examples:
Field Text
"GALLERIA MALL"
"3427 GG 17"
"21 Clark Rd Est"

You can see more about this notice here.

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

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"stops.txt" "stop_name" "CANAL BANK ST + TOWNLINE TUNNEL RD" 15
"stops.txt" "stop_name" "PARK ST + ONTARIO ST" 22
"stops.txt" "stop_name" "PARK ST + ST CLAIR AV" 23
"stops.txt" "stop_name" "PARK ST + ST LAWRENCE AV" 24
"stops.txt" "stop_name" "PARK ST + VICTORIA AV" 25
"stops.txt" "stop_name" "WRIGHT ST + SAUER AV" 26
"stops.txt" "stop_name" "NIAGARA ST + QUAKER ROAD" 27
"stops.txt" "stop_name" "DORCHESTER RD + MCLEOD RD" 28
"stops.txt" "stop_name" "MERRITT ST + BALL AV E" 29
"stops.txt" "stop_name" "MCLEOD RD + DORCHESTER RD" 30
"stops.txt" "stop_name" "BROWN RD + BUTTERNUT BL" 31
"stops.txt" "stop_name" "BROWN RD + BUTTERNUT BL" 32
"stops.txt" "stop_name" "GARNER RD + MCLEOD RD" 33
"stops.txt" "stop_name" "GARNER RD + EMILY BLVD" 34
"stops.txt" "stop_name" "GARNER RD + SOURGUM AV" 35
"stops.txt" "stop_name" "GARNER RD + SOURGUM AVE" 36
"stops.txt" "stop_name" "HEARTLAND FOREST" 37
"stops.txt" "stop_name" "OPPOSITE HEARTLAND FOREST" 38
"stops.txt" "stop_name" "BLACKBURN PKWY + HEARTLAND FOREST RD" 39
"stops.txt" "stop_name" "BLACKBURN PKWY + HEARTLAND FOREST RD" 40
"stops.txt" "stop_name" "BLACKBURN PKWY + MONTROSE RD" 41
"stops.txt" "stop_name" "BLACKBURN PKWY + MONTROSE RD" 42
"stops.txt" "stop_name" "DRUMMOND RD + SAM IORFIDA DR" 43
"stops.txt" "stop_name" "DRUMMOND RD + LIONSHEAD AV" 44
"stops.txt" "stop_name" "DRUMMOND RD + OLDFIELD RD" 45
"stops.txt" "stop_name" "DRUMMOND RD + OLDFIELD RD" 46
"stops.txt" "stop_name" "OLDFIELD RD + PENDER ST" 47
"stops.txt" "stop_name" "OLDFIELD RD + PENDER ST" 48
"stops.txt" "stop_name" "DORCHESTER RD + JUBILEE DR" 49
"stops.txt" "stop_name" "DORCHESTER RD + JUBILEE DR" 50
"stops.txt" "stop_name" "BROWN RD + HEARTLAND FOREST RD" 51
"stops.txt" "stop_name" "7771 STANLEY AV" 52
"stops.txt" "stop_name" "STANLEY AV + RAMSEY RD" 53
"stops.txt" "stop_name" "8345 STANLEY AVENUE" 54
"stops.txt" "stop_name" "PROGRESS ST + EARL THOMAS AV" 55
"stops.txt" "stop_name" "EARL THOMAS AV + DON MURIE ST" 56
"stops.txt" "stop_name" "DON MURIE ST + STANLEY AV" 57
"stops.txt" "stop_name" "OLDFIELD RD + COLE CT" 58
"stops.txt" "stop_name" "OLDFIELD RD + COLE CT" 59
"stops.txt" "stop_name" "MONTROSE RD + NIAGARA REGION PUBLIC HEALTH" 60
"stops.txt" "stop_name" "MORRISON-DORCHESTER HUB - UPPER" 61
"stops.txt" "stop_name" "VALLEY WAY + PORTAGE RD" 62
"stops.txt" "stop_name" "KOTTMEIER RD + VAUGHN DR" 63
"stops.txt" "stop_name" "KOTTMEIER RD + VAUGHN DR" 64
"stops.txt" "stop_name" "ALLANBURG RD + HODGKINS AVE" 67
"stops.txt" "stop_name" "KALAR RD + WESTWOOD ST" 68
"stops.txt" "stop_name" "LUNDY'S LANE + BROOKFIELD AV" 69
"stops.txt" "stop_name" "FLORAL SHOWHOUSE - NORTH" 71
"stops.txt" "stop_name" "TABLE ROCK - NORTH" 72
"stops.txt" "stop_name" "QUEEN VICTORIA PARK - NORTH" 73
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`.
"BLUE" 100 "BLUE" "Blue Line"
"GREEN" 101 "GREEN" "Green Line"
stop_without_stop_time WARNING 19

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
632 "610" "ST PAUL ST W + DEXTER ST"
633 "611" "ST PAUL ST W + GREAT WESTERN ST"
634 "612" "ST PAUL ST W + MERIGOLD ST"
635 "613" "ST PAUL ST W + LLOYD ST"
636 "614" "ST PAUL ST W + EDITH ST"
644 "623" "LOUTH ST + ST PAUL ST W"
694 "689" "ST PAUL ST W + CHURCHILL ST"
695 "690" "ST PAUL ST W + LLOYD ST"
696 "691" "ST PAUL ST W + LEEPER ST"
697 "692" "ST PAUL ST W + DEXTER ST"
929 "1005" "CHETWOOD ST + LOUTH ST"
930 "1006" "CHETWOOD ST + EDITH ST"
931 "1007" "CHETWOOD ST + CHURCHILL ST"
932 "1008" "CHETWOOD ST + LLOYD ST"
933 "1009" "CHETWOOD ST + MERIGOLD ST"
934 "1010" "MERIGOLD ST + ST PAUL ST W"
1026 "1449" "MCGUIRE ST + ST PAUL ST W"
1028 "1460" "ST PAUL ST W + HAINER STREET"
1096 "2722" "ST PAUL ST W + FLUMMERFELT ST"
unused_shape WARNING 5

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.
"shp-303-01" 42377
"shp-315-01" 57946
"shp-315-51" 59805
"shp-415-01" 102460
"shp-415-51" 104549