norsk — Enhanced Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-09T15:24:15Z,
for the dataset file:///shared/norsk_0724a77e.zip. No country code was provided.

Use this report alongside our documentation.

A new version of the Canonical GTFS Schedule validator is available! Please update to get the latest/best validation results.

Summary

Agencies included


Feed Info


Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Language:
Norwegian
Feed Start Date:
2025-12-14
Feed End Date:
2027-05-09

Files included


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

Counts


  • Agencies: 58
  • Blocks: 0
  • Routes: 4220
  • Shapes: 23749
  • Stops: 141478
  • Trips: 203322

Specification Compliance report

4341 notices reported (0 errors, 4326 warnings, 15 infos)

Notice Code Severity Total
duplicate_route_name WARNING 6

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`.
8 "1065-AKT:Line:1019" 129 "1065-AKT:Line:2219" "19" "Suldalen - Gimlekollen" -1 "1065-AKT:Authority:AKT_ID"
135 "1065-AKT:Line:2261" 167 "1065-AKT:Line:3001" "M1" "Flekkerøy - Sørlandsparken" -1 "1065-AKT:Authority:AKT_ID"
164 "1065-AKT:Line:270" 181 "1065-AKT:Line:4713" "270" "Flekkefjord - Gyland - Tonstad" -1 "1065-AKT:Authority:AKT_ID"
2983 "1065-SOF:Line:1103_69" 2984 "1065-SOF:Line:1105_69" "100" "Sandane-Byrkjelo" -1 "1065-SOF:Authority:17"
3872 "1065-VKT:Line:1631" 3897 "1065-VKT:Line:1657" "130" "Vear-Tønsberg" -1 "1065-VKT:Authority:VKT_ID"
3782 "1065-VKT:Line:1536" 3929 "1065-VKT:Line:1690" "116" "Løveid-Tønsberg" -1 "1065-VKT:Authority:VKT_ID"
expired_calendar WARNING 9

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.
445 "1065-FLI:DayType:e189689369475703"
450 "1065-HUR:DayType:Spring"
520 "1065-INN:DayType:Cal2026050833646-Mai_Thu_07-Mai_Fri_08-S-MoTuWeThFr"
521 "1065-INN:DayType:Cal2026050833646-Mai_Thu_07-Mai_Fri_08-S-Th"
522 "1065-INN:DayType:Cal2026050833646-Mai_Thu_07-Mai_Fri_08-S-TuFr"
523 "1065-INN:DayType:Cal2026050833646-Mai_Thu_07-Mai_Sun_10-MoTuWeThFr"
2760 "1065-NWB:DayType:13c57e12-35fe-40d1-bb05-be079314f002"
2967 "1065-TEL:DayType:Cal2026050539145-Mai_Tue_05-Oct_Sun_11-S-Fr_4"
3292 "1065-VYX:DayType:43f5d6b41a89a080631120a5ba86dcbd8899ba9c"
mixed_case_recommended_field WARNING 405

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 405 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" "SSS-veien" 705
"stops.txt" "stop_name" "SSS-veien" 706
"stops.txt" "stop_name" "NSB verksted" 2182
"stops.txt" "stop_name" "LSK befalsmesse" 4355
"stops.txt" "stop_name" "LSK befalsmesse" 4356
"stops.txt" "stop_name" "LSK idrettsanlegg" 4359
"stops.txt" "stop_name" "LSK idrettsanlegg" 4361
"stops.txt" "stop_name" "SSS-veien" 6403
"stops.txt" "stop_name" "NSB verksted" 7263
"stops.txt" "stop_name" "LSK befalsmesse" 8519
"stops.txt" "stop_name" "LSK idrettsanlegg" 8522
"stops.txt" "stop_name" "OTI-senteret" 13619
"stops.txt" "stop_name" "OTI-senteret" 13620
"stops.txt" "stop_name" "OTI-senteret" 20264
"stops.txt" "stop_name" "MIF-huset" 26693
"stops.txt" "stop_name" "MIF-huset" 26694
"stops.txt" "stop_name" "SIF-hytta" 27788
"stops.txt" "stop_name" "SIF-hytta" 27789
"stops.txt" "stop_name" "MIF-huset" 29734
"stops.txt" "stop_name" "SIF-hytta" 30315
"stops.txt" "stop_name" "SÅS idrettsplass" 41042
"stops.txt" "stop_name" "SÅS idrettsplass" 41044
"stops.txt" "stop_name" "KK-plassen" 44083
"stops.txt" "stop_name" "KK-plassen" 44084
"stops.txt" "stop_name" "HV-skolen" 44602
"stops.txt" "stop_name" "HV-skolen" 44603
"stops.txt" "stop_name" "SÅS idrettsplass" 47211
"stops.txt" "stop_name" "KK-plassen" 48880
"stops.txt" "stop_name" "HV-skolen" 49176
"stops.txt" "stop_name" "2020 park" 56393
"stops.txt" "stop_name" "2020 park" 56394
"stops.txt" "stop_name" "2020 park" 59032
"stops.txt" "stop_name" "MRK senteret" 73999
"stops.txt" "stop_name" "MRK senteret" 74000
"stops.txt" "stop_name" "MRK senteret" 77860
"stops.txt" "stop_name" "HV-huset" 82601
"stops.txt" "stop_name" "HV-huset" 84480
"stops.txt" "stop_name" "CC vest" 86831
"stops.txt" "stop_name" "CC vest" 86833
"stops.txt" "stop_name" "HV-huset" 88655
"stops.txt" "stop_name" "HV-huset" 88656
"stops.txt" "stop_name" "SAS-museet" 89020
"stops.txt" "stop_name" "SAS-museet" 89021
"stops.txt" "stop_name" "KB-senteret" 90980
"stops.txt" "stop_name" "KB-senteret" 90981
"stops.txt" "stop_name" "GA-terminalen" 91415
"stops.txt" "stop_name" "GA-terminalen" 91416
"stops.txt" "stop_name" "SAS tekniske" 91582
"stops.txt" "stop_name" "HV-huset" 92373
"stops.txt" "stop_name" "SAS-museet" 92558
route_long_name_contains_short_name WARNING 1

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`.
"1065-INN:Line:906" 904 "Femund" "Femund Ii"
stop_has_too_many_matches_for_shape WARNING 2

stop_has_too_many_matches_for_shape

Stop entry that has many potential matches to the trip's path of travel, as defined by the shape entry in shapes.txt.

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. matchCount (?) The number of matches for the stop that is referred to.
147267 "1065-SKY:JourneyPattern:351-133" "1065-SKY:ServiceJourney:351-198392-20332148" 3631064 "1065-NSR:QUAY:58068" "Nordbygda skule" [60.83166400000001,5.282667] 21
147267 "1065-SKY:JourneyPattern:351-133" "1065-SKY:ServiceJourney:351-198392-20332148" 3631068 "1065-NSR:QUAY:58069" "Nordbygda skule" [60.83159969384932,5.281696829028232] 21
stops_match_shape_out_of_order WARNING 1

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.
157658 "1065-SKY:JourneyPattern:555-737" "1065-SKY:ServiceJourney:555-197896-18460923" 3876587 "1065-NSR:QUAY:50761" "Nese" [59.78794765884854,5.125439196181539] 3876586 "1065-NSR:QUAY:50762" "Nese" [59.78801399999999,5.125263999999999]
unexpected_enum_value WARNING 3902

unexpected_enum_value

An enum has an unexpected value.

You can see more about this notice here.

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

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" 701
"routes.txt" 3 "route_type" 704
"routes.txt" 4 "route_type" 704
"routes.txt" 5 "route_type" 704
"routes.txt" 6 "route_type" 704
"routes.txt" 7 "route_type" 704
"routes.txt" 8 "route_type" 704
"routes.txt" 9 "route_type" 704
"routes.txt" 10 "route_type" 704
"routes.txt" 11 "route_type" 704
"routes.txt" 12 "route_type" 704
"routes.txt" 13 "route_type" 704
"routes.txt" 14 "route_type" 704
"routes.txt" 15 "route_type" 704
"routes.txt" 16 "route_type" 704
"routes.txt" 17 "route_type" 704
"routes.txt" 18 "route_type" 704
"routes.txt" 19 "route_type" 704
"routes.txt" 20 "route_type" 704
"routes.txt" 21 "route_type" 704
"routes.txt" 22 "route_type" 704
"routes.txt" 23 "route_type" 704
"routes.txt" 24 "route_type" 704
"routes.txt" 25 "route_type" 704
"routes.txt" 26 "route_type" 704
"routes.txt" 27 "route_type" 704
"routes.txt" 28 "route_type" 704
"routes.txt" 29 "route_type" 704
"routes.txt" 30 "route_type" 701
"routes.txt" 31 "route_type" 701
"routes.txt" 32 "route_type" 704
"routes.txt" 33 "route_type" 704
"routes.txt" 34 "route_type" 704
"routes.txt" 35 "route_type" 704
"routes.txt" 36 "route_type" 704
"routes.txt" 37 "route_type" 704
"routes.txt" 38 "route_type" 704
"routes.txt" 39 "route_type" 704
"routes.txt" 40 "route_type" 704
"routes.txt" 41 "route_type" 704
"routes.txt" 42 "route_type" 704
"routes.txt" 43 "route_type" 701
"routes.txt" 44 "route_type" 704
"routes.txt" 45 "route_type" 704
"routes.txt" 46 "route_type" 704
"routes.txt" 47 "route_type" 704
"routes.txt" 48 "route_type" 704
"routes.txt" 49 "route_type" 704
"routes.txt" 50 "route_type" 704
"routes.txt" 51 "route_type" 704
transfer_distance_above_2_km INFO 15

transfer_distance_above_2_km

The transfer distance from stop to stop in transfers.txt is larger than 2 km.

You can see more about this notice here.

csvRowNumber (?) The row number from `transfers.txt` for the faulty entry. fromStopId (?) The ID of the stop in `from_stop_id`. toStopId (?) The ID of the stop in `to_stop_id`. distanceKm (?) The distance between the two stops in km.
897 "1065-NSR:QUAY:76109" "1065-NSR:QUAY:102047" 2.0055094558408157
898 "1065-NSR:QUAY:76109" "1065-NSR:QUAY:102047" 2.0055094558408157
899 "1065-NSR:QUAY:76109" "1065-NSR:QUAY:102047" 2.0055094558408157
900 "1065-NSR:QUAY:76109" "1065-NSR:QUAY:102047" 2.0055094558408157
901 "1065-NSR:QUAY:76109" "1065-NSR:QUAY:102047" 2.0055094558408157
902 "1065-NSR:QUAY:80162" "1065-NSR:QUAY:80168" 2.0606918839646253
903 "1065-NSR:QUAY:80778" "1065-NSR:QUAY:80161" 2.350071219136175
4238 "1065-NSR:QUAY:83322" "1065-NSR:QUAY:85742" 2.967389540411202
4239 "1065-NSR:QUAY:83322" "1065-NSR:QUAY:85742" 2.967389540411202
4243 "1065-NSR:QUAY:84292" "1065-NSR:QUAY:84500" 2.867437720833962
4244 "1065-NSR:QUAY:84292" "1065-NSR:QUAY:84500" 2.867437720833962
4245 "1065-NSR:QUAY:84292" "1065-NSR:QUAY:84500" 2.867437720833962
4246 "1065-NSR:QUAY:84292" "1065-NSR:QUAY:84500" 2.867437720833962
16609 "1065-NSR:QUAY:60207" "1065-NSR:QUAY:99857" 2.8532553466659563
17801 "1065-NSR:QUAY:102191" "1065-NSR:QUAY:455" 2.12140558691856