Search
  1. Home
  2. Canada Feeds
  3. edmonton-streetcar
  4. Source Data Validation Report

edmonton-streetcar — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-09-11T18:57:51Z,
for the dataset file:///shared/edmonton-streetcar_358eb5ea.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Edmonton Radial Railway Society
Feed Email:
colinjstepney@gmail.com
Feed Language:
English
Feed Start Date:
2026-05-01
Feed End Date:
2026-12-31

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. routes.txt
  8. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. transfers.txt
  12. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 4
  • Shapes: 2
  • Stops: 7
  • Trips: 108

Specification Compliance report

10 notices reported (0 errors, 5 warnings, 5 infos)

Notice Code Severity Total
duplicate_route_name WARNING 2

duplicate_route_name

Two distinct routes have either the same route_short_name, the same route_long_name, or the same combination of route_short_name and route_long_name.

All routes of the same route_type with the same agency_id should have unique combinations of route_short_name and route_long_name.

Note that there may be valid cases where routes have the same short and long name, e.g., if they serve different areas. However, different directions must be modeled as the same route.

Example of bad data:

route_id route_short_name route_long_name
route1 U1 Southern
route2 U1 Southern

You can see more about this notice here.

csvRowNumber1 (?) The row number of the first occurrence. routeId1 (?) The id of the the first occurrence. csvRowNumber2 (?) The row number of the other occurrence. routeId2 (?) The id of the the other occurrence. routeShortName (?) Common `routes.route_short_name`. routeLongName (?) Common `routes.route_long_name`. routeTypeValue (?) Common `routes.route_type`. agencyId (?) Common `routes.agency_id`.
3 "NB" 4 "FringeNB" "Northbound" "High Level Bridge Streetcar (Northbound)" 0 "ERRS"
2 "SB" 5 "FringeSB" "Southbound" "High Level Bridge Streetcar (Southbound)" 0 "ERRS"
expired_calendar WARNING 3

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.
6 "fringecore"
7 "fringesat"
8 "fringecar2"
big_gap_in_service INFO 3

big_gap_in_service

A service has a gap of more than 13 days between active service dates.

You can see more about this notice here.

serviceId (?) The service_id that has the gap. gapStartDate (?) The first day of the gap. gapEndDate (?) The last day of the gap. gapDurationDays (?) The number of days in the gap.
"saturday" "2026-08-08" "2026-08-29" 20
"weekend" "2026-08-09" "2026-08-29" 19
"sunday" "2026-08-09" "2026-08-30" 20
feed_valid_beyond_total_service_window INFO 1

feed_valid_beyond_total_service_window

The feed is valid 14 days beyond its total service window.

You can see more about this notice here.

feedStartDate (?) The feed start date from feed_info.txt. feedEndDate (?) The feed end date from feed_info.txt. serviceWindowStartDate (?) The earliest active service date across all services. serviceWindowEndDate (?) The latest active service date across all services.
"2026-05-01" "2026-12-31" "2026-05-15" "2026-10-12"
unknown_column INFO 1

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.
"calendar_dates.txt" "notes" 4