Invalid value Terschelling in field route_short_name
This route_short_name is relatively long, which probably means that it contains a place name. You should only use this field to hold a short code that riders use to identify a route. If this route doesn't have such a code, it's OK to leave this field empty.
in line 2 of routes.txt
| route_id | agency_id | route_short_name | route_long_name | route_desc | route_type | route_color | route_text_color |
|---|
| DOEKSEN:HL|TS | DOEKSEN | Terschelling | Harlingen - Terschelling | | 4 | | |
Invalid value Terschelling in field route_short_name
This route_short_name is relatively long, which probably means that it contains a place name. You should only use this field to hold a short code that riders use to identify a route. If this route doesn't have such a code, it's OK to leave this field empty.
in line 3 of routes.txt
| route_id | agency_id | route_short_name | route_long_name | route_desc | route_type | route_color | route_text_color |
|---|
| DOEKSEN:HL|TS|SD | DOEKSEN | Terschelling | Harlingen - Terschelling (Sneldienst) | | 4 | | |
Invalid value Vlieland in field route_short_name
This route_short_name is relatively long, which probably means that it contains a place name. You should only use this field to hold a short code that riders use to identify a route. If this route doesn't have such a code, it's OK to leave this field empty.
in line 4 of routes.txt
| route_id | agency_id | route_short_name | route_long_name | route_desc | route_type | route_color | route_text_color |
|---|
| DOEKSEN:HL|VL | DOEKSEN | Vlieland | Harlingen - Vlieland | | 4 | | |
Invalid value Vlieland in field route_short_name
This route_short_name is relatively long, which probably means that it contains a place name. You should only use this field to hold a short code that riders use to identify a route. If this route doesn't have such a code, it's OK to leave this field empty.
in line 5 of routes.txt
| route_id | agency_id | route_short_name | route_long_name | route_desc | route_type | route_color | route_text_color |
|---|
| DOEKSEN:HL|VL|SD | DOEKSEN | Vlieland | Harlingen - Vlieland (Sneldienst) | | 4 | | |
Invalid value Sneldienst in field route_short_name
This route_short_name is relatively long, which probably means that it contains a place name. You should only use this field to hold a short code that riders use to identify a route. If this route doesn't have such a code, it's OK to leave this field empty.
in line 6 of routes.txt
| route_id | agency_id | route_short_name | route_long_name | route_desc | route_type | route_color | route_text_color |
|---|
| DOEKSEN:TS|VL|SD | DOEKSEN | Sneldienst | Terschelling - Vlieland | | 4 | | |
High speed travel detected in trip 791:DOEKSEN:TS|VL|SD|18:10: Terschelling to Vlieland. 118458 meters in 1800 seconds. (237 km/h).
High speed travel detected in trip 791:DOEKSEN:TS|VL|SD|09:00: Terschelling to Vlieland. 118458 meters in 1800 seconds. (237 km/h).
High speed travel detected in trip 791:DOEKSEN:TS|VL|SD|09:30: Terschelling to Vlieland. 118458 meters in 1800 seconds. (237 km/h).
High speed travel detected in trip 791:DOEKSEN:VL|HL|SD|10:15: Harlingen to Vlieland. 100605 meters in 2700 seconds. (134 km/h).
High speed travel detected in trip 791:DOEKSEN:HL|VL|SD|12:45: Harlingen to Vlieland. 100605 meters in 2700 seconds. (134 km/h).
High speed travel detected in trip 791:DOEKSEN:HL|VL|SD|10:40: Harlingen to Vlieland. 100605 meters in 2700 seconds. (134 km/h).
High speed travel detected in trip 791:DOEKSEN:HL|VL|SD|17:15: Harlingen to Vlieland. 100605 meters in 2700 seconds. (134 km/h).
High speed travel detected in trip 791:DOEKSEN:VL|HL|SD|18:20: Harlingen to Vlieland. 100605 meters in 2700 seconds. (134 km/h).
High speed travel detected in trip 791:DOEKSEN:VL|HL|SD|18:50: Harlingen to Vlieland. 100605 meters in 2700 seconds. (134 km/h).
High speed travel detected in trip 791:DOEKSEN:VL|HL|SD|14:30: Harlingen to Vlieland. 100605 meters in 2700 seconds. (134 km/h).
High speed travel detected in trip 791:DOEKSEN:HL|VL|SD|17:30: Harlingen to Vlieland. 100605 meters in 2700 seconds. (134 km/h).
High speed travel detected in trip 791:DOEKSEN:VL|HL|SD|13:45: Harlingen to Vlieland. 100605 meters in 2700 seconds. (134 km/h).
High speed travel detected in trip 791:DOEKSEN:VL|HL|SD|09:40: Harlingen to Vlieland. 100605 meters in 2700 seconds. (134 km/h).
High speed travel detected in trip 791:DOEKSEN:VL|HL|SD|12:30: Harlingen to Vlieland. 100605 meters in 2700 seconds. (134 km/h).
Unrecognized column wheelchair_boarding in file stops.txt. This might be a misspelled column name (capitalization matters!). Or it could be extra information (such as a proposed feed extension) that the validator doesn't know about yet. Extra information is fine; this warning is here to catch misspelled optional column names.
in line 1 of stops.txt
| stop_id | stop_code | stop_name | stop_lat | stop_lon | location_type | parent_station | stop_timezone | wheelchair_boarding | platform_code | zone_id |
|---|
| | | | | | | | | | |
Unrecognized column platform_code in file stops.txt. This might be a misspelled column name (capitalization matters!). Or it could be extra information (such as a proposed feed extension) that the validator doesn't know about yet. Extra information is fine; this warning is here to catch misspelled optional column names.
in line 1 of stops.txt
| stop_id | stop_code | stop_name | stop_lat | stop_lon | location_type | parent_station | stop_timezone | wheelchair_boarding | platform_code | zone_id |
|---|
| | | | | | | | | | |
Unrecognized column wheelchair_accessible in file trips.txt. This might be a misspelled column name (capitalization matters!). Or it could be extra information (such as a proposed feed extension) that the validator doesn't know about yet. Extra information is fine; this warning is here to catch misspelled optional column names.
in line 1 of trips.txt
| route_id | service_id | trip_id | trip_headsign | trip_short_name | trip_long_name | direction_id | block_id | shape_id | wheelchair_accessible | bikes_allowed |
|---|
| | | | | | | | | | |
Unrecognized column trip_long_name in file trips.txt. This might be a misspelled column name (capitalization matters!). Or it could be extra information (such as a proposed feed extension) that the validator doesn't know about yet. Extra information is fine; this warning is here to catch misspelled optional column names.
in line 1 of trips.txt
| route_id | service_id | trip_id | trip_headsign | trip_short_name | trip_long_name | direction_id | block_id | shape_id | wheelchair_accessible | bikes_allowed |
|---|
| | | | | | | | | | |
Unrecognized column bikes_allowed in file trips.txt. This might be a misspelled column name (capitalization matters!). Or it could be extra information (such as a proposed feed extension) that the validator doesn't know about yet. Extra information is fine; this warning is here to catch misspelled optional column names.
in line 1 of trips.txt
| route_id | service_id | trip_id | trip_headsign | trip_short_name | trip_long_name | direction_id | block_id | shape_id | wheelchair_accessible | bikes_allowed |
|---|
| | | | | | | | | | |
Unrecognized column trip_short_name in file trips.txt. This might be a misspelled column name (capitalization matters!). Or it could be extra information (such as a proposed feed extension) that the validator doesn't know about yet. Extra information is fine; this warning is here to catch misspelled optional column names.
in line 1 of trips.txt
| route_id | service_id | trip_id | trip_headsign | trip_short_name | trip_long_name | direction_id | block_id | shape_id | wheelchair_accessible | bikes_allowed |
|---|
| | | | | | | | | | |
Unrecognized column fare_units_traveled in file stop_times.txt. This might be a misspelled column name (capitalization matters!). Or it could be extra information (such as a proposed feed extension) that the validator doesn't know about yet. Extra information is fine; this warning is here to catch misspelled optional column names.
in line 1 of stop_times.txt
| trip_id | stop_sequence | stop_id | stop_headsign | arrival_time | departure_time | pickup_type | drop_off_type | timepoint | shape_dist_traveled | fare_units_traveled |
|---|
| | | | | | | | | | |
Unrecognized column timepoint in file stop_times.txt. This might be a misspelled column name (capitalization matters!). Or it could be extra information (such as a proposed feed extension) that the validator doesn't know about yet. Extra information is fine; this warning is here to catch misspelled optional column names.
in line 1 of stop_times.txt
| trip_id | stop_sequence | stop_id | stop_headsign | arrival_time | departure_time | pickup_type | drop_off_type | timepoint | shape_dist_traveled | fare_units_traveled |
|---|
| | | | | | | | | | |