GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-04T19:46:17Z,
for the dataset file:///shared/etufor2_74ca5d22.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
Portuguese
Feed Start Date:
2022-12-02
Feed End Date:
2023-03-02

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 255
  • Shapes: 493
  • Stops: 4778
  • Trips: 52286

Specification Compliance report

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

Notice Code Severity Total
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.
2 "100539-D"
3 "100539-S"
4 "100539-U"
feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

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 "20260504" "20230302" "20260511"
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 14

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.

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" "RUA MEM DE SA, 675" 2597
"stops.txt" "stop_name" "RUA MEM DE SA, 392" 2598
"stops.txt" "stop_name" "RUA A, S/Nº" 3864
"stops.txt" "stop_name" "RUA C, S/Nº" 3943
"stops.txt" "stop_name" "RUA E, S/Nº" 3944
"stops.txt" "stop_name" "RUA F, S/Nº" 3945
"stops.txt" "stop_name" "RUA 104, S/Nº" 4014
"stops.txt" "stop_name" "RUA 104, S/Nº" 4015
"stops.txt" "stop_name" "RUA D, S/Nº" 4050
"stops.txt" "stop_name" "RUA 8, S/Nº" 4054
"stops.txt" "stop_name" "RUA UM, S/Nº" 4089
"stops.txt" "stop_name" "RUA 15, S/Nº" 4185
"stops.txt" "stop_name" "RUA 15, S/Nº" 4186
"stops.txt" "stop_name" "RUA XV, 52" 4297
route_short_name_too_long WARNING 251

route_short_name_too_long

Short name of a route is too long (more than 12 characters).

You can see more about this notice here.

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

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeShortName (?) The faulty record's `route_short_name`.
"100539-004" 2 "4-Messejana/Papicu/Cambeba/Tj"
"100539-011" 3 "11-Circular 1/Centro"
"100539-012" 4 "12-Circular 2/Centro"
"100539-014" 5 "14-Aguanambi/Rodoviária Ii"
"100539-015" 6 "15-Cj Ceará/Antônio Bezerra I"
"100539-016" 7 "16-Cuca Barra/Papicu"
"100539-020" 8 "20-Campus do Pici"
"100539-021" 9 "21-Luciano Cavalcante/Papicu"
"100539-022" 10 "22-Jardim das Oliveiras/Centro"
"100539-024" 11 "24-Antônio Bezerra/Lagoa/Unifor"
"100539-025" 12 "25-Opaia/Lagoa"
"100539-026" 13 "26-Antônio Bezerra/Messejana"
"100539-027" 14 "27-Siqueira/Papicu/Aeroporto"
"100539-028" 15 "28-Antônio Bezerra/Papicu"
"100539-029" 16 "29-Parangaba/Náutico"
"100539-030" 17 "30-Siqueira/Papicu/13 de Maio"
"100539-034" 18 "34-Corujão/Av. Paranjana I"
"100539-035" 19 "35-Corujão/Av. Paranjana Ii"
"100539-038" 20 "38-Parangaba/Papicu"
"100539-040" 21 "40-Parangaba/Lagoa"
"100539-041" 22 "41-Parangaba/Oliveira Paiva/Papicu"
"100539-042" 23 "42-Antônio Bezerra/Francisco Sá/Papicu"
"100539-043" 24 "43-Cj Ceará/Lagoa/Fernandes Távora"
"100539-044" 25 "44-Parangaba/Papicu/Montese"
"100539-045" 26 "45-Cj Ceará/Papicu/Montese"
"100539-048" 27 "48-Corujão/Parangaba/Papicu"
"100539-049" 28 "49-Siqueira/Oliveira Paiva/Washington Soares"
"100539-050" 29 "50-Siqueira/Papicu/Washington Soares"
"100539-051" 30 "51-Grande Circular I"
"100539-052" 31 "52-Grande Circular Ii"
"100539-053" 32 "53-Messejana/Papicu/Washington Soares"
"100539-055" 33 "55-Corujão/Grande Circular I"
"100539-056" 34 "56-Corujão/Grande Circular Ii"
"100539-057" 35 "57-Corujão/Jardim Iracema"
"100539-058" 36 "58-Corujão/Jardim Guanabara/N Assunção Ii"
"100539-060" 37 "60-Parquelândia/Parangaba"
"100539-063" 38 "63-Corujão/Bom Jardim"
"100539-066" 39 "66-Parangaba/Papicu/Aeroporto"
"100539-067" 40 "67-Lagoa/Albert Sabin"
"100539-068" 41 "68-Messejana/Papicu/Cambeba/Lj"
"100539-069" 42 "69-Lagoa/Papicu/Via Expressa"
"100539-070" 43 "70-Cuca Barra/Parangaba"
"100539-071" 44 "71-Antônio Bezerra/Mucuripe"
"100539-072" 45 "72-Antônio Bezerra/Parangaba"
"100539-073" 46 "73-Siqueira/Praia de Iracema"
"100539-074" 47 "74-Antônio Bezerra/Unifor"
"100539-075" 48 "75-Campus do Pici/Unifor"
"100539-076" 49 "76-Cj Ceará/Aldeota/Papicu"
"100539-077" 50 "77-Parangaba/Mucuripe"
"100539-078" 51 "78-Siqueira/Mucuripe/Ed"
stop_too_far_from_shape WARNING 16

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

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. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
9692 "100539-shape660-V" "100539-D660-T01V01B01-V" 302021 "100539-4724" "Praça Solon Pinheiro, Sn" [-3.731956,-38.52492099999999] 218.96042435778
9692 "100539-shape660-V" "100539-D660-T01V01B01-V" 302022 "100539-5303" "RUA Pedro Pereira, Sn" [-3.731956,-38.52492099999999] 204.08925150955912
9993 "100539-shape703-I" "100539-D703-T01V01B01-I" 310904 "100539-6363" "RUA SÃO Sebastião, S/N" [-3.7253389999999995,-38.568447] 153.71192182539917
8032 "100539-shape604-V" "100539-D604-T01V01B01-V" 257014 "100539-4724" "Praça Solon Pinheiro, Sn" [-3.731836567712084,-38.52494295435283] 218.86762605801292
8032 "100539-shape604-V" "100539-D604-T01V01B01-V" 257015 "100539-5303" "RUA Pedro Pereira, Sn" [-3.7315250000000004,-38.525008] 161.4871879035948
8004 "100539-shape603-V" "100539-D603-T01V01B01-V" 255924 "100539-4724" "Praça Solon Pinheiro, Sn" [-3.731836567712084,-38.52494295435283] 218.86762605801292
8004 "100539-shape603-V" "100539-D603-T01V01B01-V" 255925 "100539-5303" "RUA Pedro Pereira, Sn" [-3.7315250000000004,-38.525008] 161.4871879035948
9385 "100539-shape649-V" "100539-D649-T02V01B01-V" 291019 "100539-4724" "Praça Solon Pinheiro, Sn" [-3.731837812984696,-38.52494129435575] 219.01977497786103
9385 "100539-shape649-V" "100539-D649-T02V01B01-V" 291020 "100539-5303" "RUA Pedro Pereira, Sn" [-3.731291,-38.52505500000001] 140.10772937902587
45016 "100539-shape501-V" "100539-U501-T01V01B01-V" 1462369 "100539-4724" "Praça Solon Pinheiro, Sn" [-3.73193146005329,-38.52779652231308] 107.88838385946002
7888 "100539-shape600-V" "100539-D600-T01V01B01-V" 252739 "100539-4724" "Praça Solon Pinheiro, Sn" [-3.732134999999999,-38.52488] 221.54903854423958
7888 "100539-shape600-V" "100539-D600-T01V01B01-V" 252740 "100539-5303" "RUA Pedro Pereira, Sn" [-3.732134999999999,-38.52488] 222.85284346147472
9710 "100539-shape665-V" "100539-D665-T01V01B01-V" 303074 "100539-4724" "Praça Solon Pinheiro, Sn" [-3.731956,-38.52492099999999] 218.96042435778
9710 "100539-shape665-V" "100539-D665-T01V01B01-V" 303075 "100539-5303" "RUA Pedro Pereira, Sn" [-3.731956,-38.52492099999999] 204.08925150955912
9405 "100539-shape650-V" "100539-D650-T01V01B01-V" 291986 "100539-4724" "Praça Solon Pinheiro, Sn" [-3.732134999999999,-38.52488] 221.54903854423958
9405 "100539-shape650-V" "100539-D650-T01V01B01-V" 291987 "100539-5303" "RUA Pedro Pereira, Sn" [-3.732134999999999,-38.52488] 222.85284346147472
stops_match_shape_out_of_order WARNING 3

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.
38907 "100539-shape316-I" "100539-U316-T01V01B01-I" 1319664 "100539-5287" "Avenida Tristao Goncalves, 823" [-3.729344,-38.533872] 1319663 "100539-5286" "Avenida Tristao Goncalves, 555" [-3.729344,-38.533871999999995]
45051 "100539-shape513-I" "100539-U513-T01V01B01-I" 1463113 "100539-6331" "RUA MON Liberato, S/N" [-3.750429241584227,-38.53218969666705] 1463112 "100539-2426" "RUA Mario Mamede, 1183" [-3.749470971724973,-38.53121825861876]
4370 "100539-shape308-I" "100539-D308-T01V01B01-I" 171817 "100539-5287" "Avenida Tristao Goncalves, 823" [-3.729344,-38.533872] 171816 "100539-5286" "Avenida Tristao Goncalves, 555" [-3.729344,-38.533871999999995]
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.
"20260504" "20221202" "20230302"