Search
  1. Home
  2. France Feeds
  3. tcvo
  4. Source Data Validation Report

tcvo — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-03-23T17:36:39Z,
for the dataset file:///shared/tcvo_6b6be202.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

    Feed Info

    Publisher Name:
    N/A
    Publisher URL:
    N/A
    Feed Email:
    N/A
    Feed Language:
    N/A

    Files included

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

    Counts

    • Agencies: 0
    • Blocks: 0
    • Routes: 9
    • Shapes: 0
    • Stops: 123
    • Trips: 195

    Specification Compliance report

    12 notices reported (1 errors, 10 warnings, 1 infos)

    Notice Code Severity Total
    missing_required_field ERROR 1

    missing_required_field

    A required field is missing.

    The given field has no value in some input row, even though values are required.

    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.
    "agency.txt" 2 "agency_url"
    missing_recommended_file WARNING 1

    missing_recommended_file

    A recommended file is missing.

    You can see more about this notice here.

    filename (?) The name of the faulty file.
    "feed_info.txt"
    mixed_case_recommended_field WARNING 9

    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.
    "routes.txt" "route_long_name" "LIGNE 4 - ORANGE LES VIGNES <> POURTOULES <> PARKING DU BOURB. - TCVO" 2
    "routes.txt" "route_long_name" "LIGNE 1 - AYGUES <> POURTOULES <> ORANGE LES VIGNES - TCVO" 3
    "routes.txt" "route_long_name" "LIGNE 3 - CENTRE FUNERAIRE <> POURTOULES <> PARKING DU BOURB. - TCVO" 4
    "routes.txt" "route_long_name" "LIGNE P1 - ECOLE DU GRES <> COLLEGE GIONO - TCVO" 5
    "routes.txt" "route_long_name" "LIGNE P2 - ECOLE DE LA DEYMARDE <> LYCEE ARGENSOL - TCVO" 6
    "routes.txt" "route_long_name" "LIGNE S1 - COLLEGE GIONO - TCVO" 7
    "routes.txt" "route_long_name" "LIGNE S2 - LEP VITICOLE - TCVO" 8
    "routes.txt" "route_long_name" "LIGNE S3 - COLLEGE ARAUSIO <> LYCEE ARGENSOL - TCVO" 9
    "routes.txt" "route_long_name" "LIGNE P3 - CHAMPLAIN <> ECOLE CHARLEMAGNE" 10
    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.
    "agency.txt" "agency_urlFare" 7