Skip to content

Validation Rules

462 of 462 rules

CodeDescriptionSourceSeverityCategory
C.01.02The versions of NeTEx schema being used should be specifiedDATA4PT10structure
C.01.03The versions of the profile being used should be specifiedDATA4PT20structure
C.01.04The PublicationRequest element in the header should be populatedDATA4PT40structure
C.01.05Any Topics mentioned in the Header must be present in the DeliveryDATA4PT40integrity
C.02.01All objects are uniquely identifiedDATA4PT10structure
C.02.03All elements (except CODESPACE) should have a version attribute.DATA4PT10structure
C.02.03-bThe order number on elements in sequences of child elements should be uniqueDATA4PT30semantic
C.02.04All references should include an explicit version on the reference.DATA4PT30integrity
C.02.05All frames should have a default CODE SPACE declaredDATA4PT10structure
C.02.05-bAny local reference should correspond to an object declared elsewhere in the same document.DATA4PT10structure
C.02.06All CODE SPACE prefixes used in identifiers should be declared with a CODE SPACE on the frame.DATA4PT10structure
C.02.07The format of element identifiers should follow any rules specific to the profileDATA4PT40structure
C.03.01The version number of each VERSION FRAME should be populated with a numberDATA4PT20structure
C.03.02The FrameDefaults of a VERSION FRAME should have values appropriate to the contentDATA4PT30structure
C.03.04Only the specialisation of VERSION FRAME (RESORCE FRAME, SITE FRAME, SERVICE FRAME, SERVICE FRAME< TIMETABLE FRAME, and SERVICE CALENDAR FRAME) appropriate to the profile should be usedDATA4PT40structure
C.03.05A TYPE OF FRAME is specified on each VERSION FRAME. and corresponds to one of those required by the profileDATA4PT30structure
C.03.05-bTypes of Frame in use: (EU_PI_COMMON. PI_PI_STOP. EU_PI_NETWORK. EU_PI_TIMETABLE. EU_PI_CALENDAR. EU_PI_LINE_OFFER. EU_PI_NETWORK_OFFER. EU_PI_STOP_OFFER. EU_PI_METADATA)DATA4PT30structure
C.04.01The same object type should only be present in a single frame typeDATA4PT30structure
C.04.02Ordered sequences of child elements shall be serialized in sequence in the accordance with the ascending value of their order attribute -DATA4PT30semantic
C.04.04Single instances of ancillary and child elements should be declared inline as part of an object.DATA4PT40structure
C.04.04-bElements should not be repeated unnecessarily as separate instances.DATA4PT40quality
C.04.05NOTICes should be declared locallyDATA4PT40structure
C.09.01On a VALIDITY CONDITION. ToDate must not be later than FromDate on any date rangeDATA4PT20structure
C.09.02On a VERSION FRAME. ToDate must not be later than FromDate on any date range.DATA4PT10structure
C.09.03ToDate must not be later than FromDate on other date rangesDATA4PT20structure
C.09.04Date ranges of elements in the frame must lie between date ranges of the VALIDITY CONDITION on the VERSION FRAMEDATA4PT20semantic
C.09.06If the URL field is filled. the validity of the URL must be checked and must resolvedDATA4PT40format
C.09.07Check valid ISO codes for lang etc.DATA4PT20structure
C.09.08Check valid ISO codes for Country. etc.DATA4PT30format
C.09.10A coordinate system should be specified for spatial coordinatesDATA4PT20structure
C.09.11WGS84 is the preferred coordinate systemDATA4PT40structure
C.09.12A POINT should normally have spatial coordinates specified.DATA4PT40structure
C.09.13A ZONE should normally have at least a centroid point specified.DATA4PT40structure
S.01.01Every STOP PLACE has a Name or ShortName attibuteDATA4PT20structure
S.01.03Every STOP PLACE has a StopPlaceType attribute with correct valueDATA4PT30structure
S.01.04All stop identifiers (QUAY. all STOP PLACEs. GROUPs OF STOP PLACEs and ACCESS) must comply with the profile codificationDATA4PT30structure
S.01.05A responsible OPERATOR must be declared for each STOP PLACE(Can be defaulted from frame)DATA4PT30structure
S.01.08Any STOP PLACE that is declared should be referenced by a STOP ASSIGNMENTDATA4PT50quality
S.03.01STOP PLACES should be organised hierarchically so as to separate the modes.DATA4PT30structure
S.03.02A Monomodal STOP PLACE should only have QUAYS of a single modeDATA4PT30structure
S.03.02-bSCHEDULED STOP POINT must be assigned to a STOP PLACEDATA4PT50quality
S.03.03MODE of a QUAY of a monomodal STOP PLACE should match the STOP PLACEDATA4PT40semantic
S.03.04Multimodal STOP PLACE and should contain at two different monomodal STOP PLACEs of different MODesDATA4PT40structure
S.03.05GROUP OF STOP PLACEs should contain only STOP PLACEsDATA4PT40structure
S.03.06Name of a QUAY should not repeat those of the STOP PLACEDATA4PT40structure
S.04.01A SCHEDULED STOP POINT must have an instantiated Name fieldDATA4PT30integrity
S.04.02SCHEDULED STOP POINT must have the same mode as the assigned STOP PLACEDATA4PT30semantic
S.04.02-bSCHEDULED STOP POINT must have similar spatial coordinates to those of the assigned STOP PLACEDATA4PT30structure
S.04.03If a SCHEDULED STOP POINT is assigned to a STOP PLACE the type of stop should be consistent on both. And also on any QUAYDATA4PT30integrity
S.08.01Location Is Unreasonable For QUAYDATA4PT30plausibility
S.08.02Location Is Unreasonable For STOP POINTDATA4PT30plausibility
S.08.03Distance Between QUAY and STOP PLACE too longDATA4PT30semantic
S.08.04Check if there are any nearby, very similar locations of the same EntityTypeDATA4PT40structure
S.09.01Distance between SCHEDULED STOP POINTS at a CONNECTION is plausibleDATA4PT30plausibility
S.09.01-bThe location of QUAY and SCHEDULED STOP POINT should be within reasonable distance of the location or surface of STOP PLACEDATA4PT30plausibility
S.15.01Every TOPOGRAPHIC PLACE has a NameDATA4PT40structure
S.15.02Type of TOPOGRAPHIC LOCATIONSDATA4PT40structure
S.15.03PostalRegion attribute on ADDRESS elementDATA4PT40structure
S.15.04Hierarchy of TOPOGRAPHIC LOCATIONSDATA4PT40structure
S.15.06Management of STOP PLACE's additionalTopographicPlaces (belonging to several municipalities)DATA4PT40structure
S.30.05Membership of a SITE by a SITE COMPONENT.DATA4PT40structure
S.31.01The members of a CONSTRAINT ZONE are SCHEDULED STOP POINTsDATA4PT40structure
S.31.02A ROUTING CONSTRAINT ZONE must be defined either by Stop or by a boundaryDATA4PT20structure
S.31.03A ROUTING CONSTRAINT ZONE must specify the nature of its use.DATA4PT40structure
T.02.01Each LINE should have a different name and a different public codeDATA4PT20structure
T.02.02TransportSubmode must be a part of the TransportModeDATA4PT30integrity
T.02.02-bEvery LINE must have an OPERATORDATA4PT30integrity
T.02.03The TypeOfLineRef must meet the profile requirementsDATA4PT40structure
T.02.04MODE and SUBMODE of a LINE must be consistent with stops and journeysDATA4PT30semantic
T.02.05A LINE must have at least one ROUTEDATA4PT30integrity
T.02.05-bThe “inverse” of the SERVICE PATTERN must match the approximate reverse of sequenceDATA4PT40semantic
T.02.08If no RouteRef is available in a SERVICE JOURNEY. a RouteView with LineRef must be availableDATA4PT30structure
T.02.10Check that there is at least one LINE in any GROUP OF LINEsDATA4PT30structure
T.02.11The main line of a GROUP OF LINEs must be part of the groupDATA4PT30integrity
T.02.11-bColour used for each separate LINE should be distinctDATA4PT40quality
T.02.12A LINE must have one or more ROUTE instancesDATA4PT40integrity
T.02.13A ROUTE must be referenced by a SERVICE JOURNEY PATTERN directly or indirectly.DATA4PT40integrity
T.02.14The MODE of a GROUP OF LINEs NETWORK must be consistent with that of the individual LINEsDATA4PT30semantic
T.03.01A primary SERVICE JOURNEY shall have at least one SERVICE PATTTERN, and/or have a list of CALLsDATA4PT20structure
T.03.01-bA ROUTE must have one or more SERVICE PATTERNs that use it.DATA4PT50quality
T.03.01-cA SERVICE JOURNEY must reference a SERVICE PATTERN.DATA4PT30integrity
T.03.03SERVICE JOURNEY PATTERN must contain POINTS IN JOURNEY PATTERNDATA4PT40structure
T.03.03-bA SERVICE JOURNEY PATTERN must have a minimum of two PointsDATA4PT30structure
T.03.04The TransportMode and TransportSubmode of the Journey must respect the choices of the profileDATA4PT30structure
T.03.04-bJOURNEY PATTERNs of SERVICE JOURNEYs shall only include S POINTS IN JOURNEY PATTERN that reference SHCEDULED STOP POINTsDATA4PT10structure
T.03.06An OPERATOR must be declared for each SERVIOCE JOURNEYDATA4PT20structure
T.03.09A substitution SERVICE JOURNEY must reference a SERVICE JOURNEY that it is replacingDATA4PT40integrity
T.04.01Every SERVICE JOURNEY should be referenced either by a GROUP OF SERVICEs or by a SERVICE JOURNEY INTERCHANGE or by an INTERCHANGE RULE.DATA4PT40integrity
T.04.02A SERVICE JOURNEY instances that have a similar DIRECTION and DAY TYPE and JOURNEY PATTERN should be grouped with a GROUP OF SERVICEsDATA4PT30structure
T.07.11DESTINATION DISPLAYs should always have at least one "FrontText"DATA4PT40structure
T.07.12DESTINATION DISPLAY VARIANTs always have at least one "FrontText"DATA4PT40structure
T.07.XXCheck if the Journey PATTERN matches any associated ROUTEDATA4PT40semantic
T.08.01A SERVICE JOURNEY have at least one DAY TYPEDATA4PT20structure
T.08.02A DAY TYPE must have sufficient PropertiesOfDay to characterise itDATA4PT30structure
T.08.05Days without scheduled SERVICE JOURNEYs for a Line must raise a warningDATA4PT30structure
T.08.11Validity period of the SERVICE JOURNEYs must fall within the validity period of the VERSION FRAMEDATA4PT20structure
T.08.12The validity of the timetable must be at least N days.DATA4PT40structure
T.09.01Every POINT IN JOURNEY POINT In a JOURNEY PATTERN used by a JOURNEY must have an PASSING TIME with arrival and departure time (except for the first and last stop)DATA4PT20integrity
T.09.02There should be a time specified on each CALL of a SERVICE JOURNETDATA4PT30structure
T.09.03Successive DayOffset+PassingTimes for the POINTs IN JOURNEY Pattern or CALLS of a Journey must not decrease. NDATA4PT20structure
T.09.06Consistency of schedules: schedules at the earliest and at the latestDATA4PT20semantic
T.09.07Successive timing between stops should be consistent with specified durations from TIMING LINKs tDATA4PT20semantic
T.09.09PASSING TIMEs for successive POINT IN JORUNEY PATTERNS must result in a plausible speed for the MODE and VEHICLE TYPEDATA4PT30plausibility
T.09.10The duration of a SERVICE JORUNEY Journey should be consistent with the timings and distances.DATA4PT30semantic
T.11.01Shared JOURNEY PARTs must be independent of any specific SERVICE JORUNEYDATA4PT40structure
T.11.02Each JOURNEY PART should be coherent with the SERVICE PATTERN of the SERVICE JOURNEYDATA4PT20semantic
T.11.03Timings of each JOURNEY PART should be coherent with the times of the SERVICE JOURNEYDATA4PT10semantic
T.11.05JOURNEY PART is coherent with the parent JOURNEYDATA4PT20semantic
T.11.09JOURNEY PART COUPLEs should be consistent with JOURNEY PARTsDATA4PT20semantic
T.12.02Distance between SCHEDULED STOP POINTS in JOURNEY PATTERN is plausibleDATA4PT30plausibility
T.12.04If the DESTINATION DISPLAY is flagged as changing at a point, then the new DESTINATION DISPLAY must be present.DATA4PT40structure
T.14.01TEMPLATE SERVICE JOURNEYs must have an associated frequency or rhythmDATA4PT20integrity
T.14.01-bSpecific VEHICLE TYPE capabilities should be populated (e.g. wheelchair)DATA4PT40structure
T.14.02RHYTHMICAL JOUREY GROUP should not be used in EPIPDATA4PT20structure
T.14.03For a HEADWAY JOURNEY GROUa frequency must be specifiedDATA4PT20structure
T.14.04End of Period of cadences for JOURNEY FREQUENCY GROUP must be specifiedDATA4PT20structure
T.14.07TEMPLATE SERVICE JOURNEY must have an appropriate type attributeDATA4PT20integrity
T.14.09Reference usage for HEADWAY JOURNEY GROUP and RHYTHMICAL JOURNEY GROUP should be declared in frame and not inlineDATA4PT30integrity
T.14.10JOURNEY FREQUENCY GROUP must contain more than one SERVICE JOURNEYDATA4PT30structure
T.14.XXConsistency of the return routeDATA4PT20semantic
T.14.XX-bLINE and ROUTE should be linked consistentlyDATA4PT20semantic
T.21.01A TRANSFER must have a transfer timeDATA4PT30integrity
T.21.01-bNOTICE ASSIGNMENTS are only related to TIMETABLEs. SERVICE JOURNEYs. POINTs IN JOURNEYPATTERN. SERVICE JOURNEY INTERCHANGEsDATA4PT40structure
T.21.02Transit times should be specified on DEFAULT CONNECTIONs and SITE CONENCTIONs..DATA4PT40structure
T.21.03Transit times should be specified on CONNECTIONs.DATA4PT40structure
T.21.04Checking the type of transferDATA4PT30structure
T.21.05Reasonable walking speed - Consistency between duration and distance of a CONNECTION / TRANSFERDATA4PT20plausibility
T.21.05-bCheck if the SERVICE JOURNEY INTERCHANGE transfer distance is reasonableDATA4PT30plausibility
T.21.07Duration of interchanges between SERVICE JOURNEYSDATA4PT30semantic
T.25.01FLEXIBLE SERVICEA should be characterised by a FlexibleServiceType. This should be coherent with the LINE type.DATA4PT30semantic
T.25.01-bCLASS of USE on PASSENGER CAPACITY should be restricted to subset of possible values.DATA4PT40format
T.25.02FLEXIBLE SERVICEs using point standing for a zone should have the required ZONE.DATA4PT30structure
T.25.02-bOrder of TRAIN COMPONENTsDATA4PT20semantic
T.25.03FLEXIBLE SERVICEs using stopping areas require a zone containing stops.DATA4PT40structure
T.25.03-bCLASS of USE on TRAIN ELEMENT should be restricted to subset of possible values.DATA4PT30format
T.25.04FLEXIBLE SERVICE should be coherent with any frequency intervalDATA4PT20semantic
T.25.05Use specific instances for FLEXIBLE SERVICE PROPERTies for each FLEXIBL SERVICEDATA4PT30structure
T.30.01The URL of the schematic plan must be validDATA4PT40structure
T.30.02Check objects in SCHEMATIC MAPsDATA4PT40structure
T.35.01Specific BOOKING ARRANGEMENTs must be givenDATA4PT30structure
T.40.02A Type of Vehicle must be namedDATA4PT30structure
T.48.01Any SCHEDULED STOP POINT that is declared should be used. i.e. referenced by an assignment or POINT IN PATTERN etc.DATA4PT40quality
AUTHORITY_1Authority missing CompanyNumberEnturINFOstructure
AUTHORITY_2Authority missing NameEnturERRORstructure
AUTHORITY_3Authority missing LegalNameEnturINFOstructure
AUTHORITY_4Authority missing ContactDetailsEnturERRORstructure
AUTHORITY_5Authority missing Url for ContactDetailsEnturERRORstructure
BLOCK_1Block missing VehicleScheduleFrameEnturERRORstructure
BLOCK_2Block missing JourneyEnturERRORstructure
BLOCK_3Block missing DayTypeEnturWARNINGstructure
BOOKING_4Booking propertyEnturERRORintegrity
BOOKING_5Missing BookWhen or MinimumBookingPeriodEnturWARNINGintegrity
COMPOSITE_FRAME_1CompositeFrame - missing ValidityConditionEnturERRORstructure
COMPOSITE_FRAME_2CompositeFrame - invalid nested ValidityConditionEnturWARNINGsemantic
COMPOSITE_FRAME_3CompositeFrame - missing ValidBetweenEnturERRORstructure
COMPOSITE_FRAME_4CompositeFrame - invalid ValidBetweenEnturERRORsemantic
COMPOSITE_FRAME_5CompositeFrame - invalid AvailabilityConditionEnturERRORsemantic
COMPOSITE_FRAME_6CompositeFrame - missing AvailabilityConditionEnturERRORstructure
COMPOSITE_FRAME_SITE_FRAMECompositeFrame - unexpected SiteFrameEnturWARNINGstructure
COMPOSITE_TIMETABLE_FRAME_IN_COMMON_FILECompositeFrame - Illegal TimetableFrame in common fileEnturERRORstructure
DATED_SERVICE_JOURNEY_1DatedServiceJourney missing OperatingDayRefEnturERRORintegrity
DATED_SERVICE_JOURNEY_2DatedServiceJourney missing ServiceJourneyRefEnturERRORintegrity
DATED_SERVICE_JOURNEY_3DatedServiceJourney multiple ServiceJourneyRefEnturERRORintegrity
DATED_SERVICE_JOURNEY_4DatedServiceJourney multiple versionsEnturWARNINGintegrity
DATED_SERVICE_JOURNEY_5DatedServiceJourney multiple references to the same DatedServiceJourneyEnturERRORintegrity
DEAD_RUN_1DeadRun missing PassingTime referencesEnturINFOintegrity
DEAD_RUN_2DeadRun missing JourneyPattern referencesEnturERRORintegrity
DEAD_RUN_3DeadRun missing DayType referencesEnturERRORintegrity
DESTINATION_DISPLAY_1DestinationDisplay missing FrontTextEnturERRORstructure
DESTINATION_DISPLAY_2DestinationDisplay missing DestinationDisplayRef on ViaEnturERRORintegrity
FLEXIBLE_LINE_1FlexibleLine missing FlexibleLineTypeEnturERRORstructure
FLEXIBLE_LINE_10FlexibleLine illegal use of both BookWhen and MinimumBookingPeriodEnturWARNINGintegrity
FLEXIBLE_LINE_11FlexibleLine BookWhen without LatestBookingTime or LatestBookingTime without BookWhenEnturWARNINGintegrity
FLEXIBLE_SERVICE_1FlexibleService missing Id on FlexibleServicePropertiesEnturERRORstructure
FLEXIBLE_SERVICE_2FlexibleService missing version on FlexibleServicePropertiesEnturERRORintegrity
FLEXIBLE_SERVICE_3FlexibleService illegal use of both BookWhen and MinimumBookingPeriodEnturWARNINGintegrity
FLEXIBLE_SERVICE_4FlexibleService BookWhen without LatestBookingTime or LatestBookingTime without BookWhenEnturWARNINGintegrity
INTERCHANGE_1Interchange invalid propertiesEnturWARNINGsemantic
INTERCHANGE_2Interchange unexpected MaximumWaitTimeEnturWARNINGsemantic
INTERCHANGE_3Interchange excessive MaximumWaitTimeEnturWARNINGsemantic
JOURNEY_PATTERN_1JourneyPattern illegal element ServiceJourneyPatternEnturERRORstructure
JOURNEY_PATTERN_2JourneyPattern missing JourneyPatternEnturERRORstructure
JOURNEY_PATTERN_3JourneyPattern missing RouteRefEnturERRORintegrity
JOURNEY_PATTERN_4JourneyPattern missing DestinationDisplayRef on first stop pointEnturERRORintegrity
JOURNEY_PATTERN_5JourneyPattern illegal DestinationDisplayRef on last stop pointEnturWARNINGintegrity
JOURNEY_PATTERN_6JourneyPattern stop point without boarding or alightingEnturWARNINGsemantic
JOURNEY_PATTERN_7JourneyPattern illegal repetition of DestinationDisplayEnturERRORsemantic
JOURNEY_PATTERN_8JourneyPattern illegal use of both BookWhen and MinimumBookingPeriodEnturWARNINGintegrity
JOURNEY_PATTERN_9JourneyPattern BookWhen without LatestBookingTime or LatestBookingTime without BookWhenEnturWARNINGintegrity
LINE_1Line - exactly one Line or FlexibleLineEnturERRORstructure
LINE_2Line missing NameEnturERRORstructure
LINE_3Line missing PublicCodeEnturWARNINGstructure
LINE_4Line missing TransportModeEnturERRORstructure
LINE_5Line missing TransportSubmodeEnturWARNINGstructure
LINE_6Line with incorrect use of RouteEnturERRORstructure
LINE_7Line missing Network or GroupOfLinesEnturERRORstructure
LINE_8Invalid color coding length on PresentationEnturWARNINGformat
LINE_9Invalid color coding value on PresentationEnturWARNINGformat
NETEX_ID_1NeTEx ID duplicated across filesEnturERRORintegrity
NETEX_ID_10Duplicate NeTEx ID across common filesEnturWARNINGintegrity
NETEX_ID_5NeTEx ID unresolved referenceEnturERRORintegrity
NETEX_ID_6NeTEx ID reference to invalid elementEnturERRORintegrity
NETEX_ID_7NeTEx ID invalid valueEnturERRORintegrity
NETEX_ID_8NeTEx ID missing version on elementsEnturERRORintegrity
NETEX_ID_9NeTEx ID missing version on referenceEnturERRORintegrity
NETWORK_1Network missing AuthorityRefEnturERRORintegrity
NETWORK_2Network missing Name on NetworkEnturERRORstructure
NETWORK_3Network missing Name on GroupOfLinesEnturERRORstructure
NOTICE_1Notice missing TextEnturERRORstructure
NOTICE_2Notice missing Text with alternative textEnturERRORstructure
NOTICE_3Notice missing language with alternative textEnturERRORstructure
NOTICE_4Notice duplicated alternative textsEnturERRORintegrity
NOTICE_5Notice duplicated assignmentEnturWARNINGintegrity
NOTICE_6Notice assignment missing reference to noticed objectEnturERRORintegrity
NOTICE_7Notice assignment missing reference to noticeEnturERRORintegrity
OPERATING_PERIOD_1OperatingPeriod invalid time intervalEnturERRORsemantic
OPERATOR_1Operator missing CompanyNumberEnturINFOstructure
OPERATOR_2Operator missing NameEnturERRORstructure
OPERATOR_3Operator missing LegalNameEnturINFOstructure
OPERATOR_4Operator missing ContactDetailsEnturWARNINGstructure
OPERATOR_5Operator missing Url for ContactDetailsEnturWARNINGstructure
OPERATOR_6Operator missing CustomerServiceContactDetailsEnturWARNINGstructure
OPERATOR_7Operator missing Url for CustomerServiceContactDetailsEnturWARNINGstructure
PASSENGER_STOP_ASSIGNMENT_1PassengerStopAssignment missing ScheduledStopPointRefEnturERRORintegrity
PASSENGER_STOP_ASSIGNMENT_2PassengerStopAssignment missing QuayRefEnturERRORintegrity
PASSENGER_STOP_ASSIGNMENT_3PassengerStopAssignment duplicated Quay assignmentEnturWARNINGintegrity
RESOURCE_FRAME_IN_LINE_FILEResourceFrame must be exactly oneEnturERRORstructure
ROUTE_1Route missingEnturERRORstructure
ROUTE_2Route missing NameEnturERRORstructure
ROUTE_3Route missing LineRefEnturERRORintegrity
ROUTE_4Route missing pointsInSequenceEnturERRORstructure
ROUTE_5Route illegal DirectionRefEnturWARNINGintegrity
ROUTE_6Route duplicated orderEnturWARNINGsemantic
ROUTE_7Route missing JourneyPatternEnturERRORstructure
SERVICE_CALENDAR_1ServiceCalendar unused DayTypeEnturWARNINGquality
SERVICE_CALENDAR_2ServiceCalendar empty ServiceCalendarEnturWARNINGquality
SERVICE_CALENDAR_3ServiceCalendar missing ToDateEnturWARNINGstructure
SERVICE_CALENDAR_4ServiceCalendar missing FromDateEnturWARNINGstructure
SERVICE_CALENDAR_5ServiceCalendar invalid time intervalEnturERRORsemantic
SERVICE_FRAME_1ServiceFrame unexpected element GroupOfLinesEnturERRORstructure
SERVICE_FRAME_2ServiceFrame unexpected element timingPointsEnturWARNINGstructure
SERVICE_FRAME_3ServiceFrame missing Projection on RoutePointEnturERRORstructure
SERVICE_FRAME_IN_COMMON_FILE_1ServiceFrame unexpected element LineEnturERRORstructure
SERVICE_FRAME_IN_COMMON_FILE_2ServiceFrame unexpected element RouteEnturERRORstructure
SERVICE_FRAME_IN_COMMON_FILE_3ServiceFrame unexpected element JourneyPatternEnturERRORstructure
SERVICE_JOURNEY_1ServiceJourney must existEnturERRORstructure
SERVICE_JOURNEY_10ServiceJourney missing reference to JourneyPatternEnturERRORintegrity
SERVICE_JOURNEY_11ServiceJourney invalid overriding of transport modesEnturWARNINGsemantic
SERVICE_JOURNEY_12ServiceJourney missing OperatorRefEnturERRORintegrity
SERVICE_JOURNEY_13ServiceJourney missing reference to calendar dataEnturERRORintegrity
SERVICE_JOURNEY_14ServiceJourney duplicated reference to calendar dataEnturERRORintegrity
SERVICE_JOURNEY_16ServiceJourney multiple versionsEnturWARNINGintegrity
SERVICE_JOURNEY_17Non-unique NeTEx id for TimetabledPassingTimeEnturERRORintegrity
SERVICE_JOURNEY_2ServiceJourney illegal element CallEnturERRORstructure
SERVICE_JOURNEY_3ServiceJourney missing element PassingTimesEnturERRORstructure
SERVICE_JOURNEY_4ServiceJourney missing arrival and departureEnturERRORsemantic
SERVICE_JOURNEY_5ServiceJourney missing departure timesEnturERRORsemantic
SERVICE_JOURNEY_6ServiceJourney missing arrival time for last stopEnturERRORsemantic
SERVICE_JOURNEY_7ServiceJourney identical arrival and departureEnturWARNINGsemantic
SERVICE_JOURNEY_8ServiceJourney missing id on TimetabledPassingTimeEnturWARNINGstructure
SERVICE_JOURNEY_9ServiceJourney missing version on TimetabledPassingTimeEnturWARNINGintegrity
SERVICE_LINK_1ServiceLink missing FromPointRefEnturERRORintegrity
SERVICE_LINK_2ServiceLink missing ToPointRefEnturERRORintegrity
SERVICE_LINK_3ServiceLink missing element ProjectionsEnturWARNINGstructure
SERVICE_LINK_4ServiceLink missing coordinate listEnturERRORstructure
SERVICE_LINK_5ServiceLink less than 2 pointsEnturWARNINGsemantic
SITE_FRAME_IN_COMMON_FILESiteFrame unexpected SiteFrame in Common fileEnturWARNINGstructure
SITE_FRAME_IN_LINE_FILESiteFrame unexpected SiteFrame in Line fileEnturWARNINGstructure
TIMETABLE_FRAME_IN_COMMON_FILETimetableFrame illegal in Common fileEnturERRORstructure
VALIDITY_CONDITIONS_IN_COMMON_FILE_1ValidityConditions missing in ServiceFrame or ServiceCalendarFrameEnturERRORstructure
VALIDITY_CONDITIONS_IN_COMMON_FILE_2ValidityConditions missing in ResourceFramesEnturERRORstructure
VALIDITY_CONDITIONS_IN_COMMON_FILE_3ValidityConditions missing in ServiceFramesEnturERRORstructure
VALIDITY_CONDITIONS_IN_COMMON_FILE_4ValidityConditions missing in ServiceCalendarFramesEnturERRORstructure
VALIDITY_CONDITIONS_IN_LINE_FILE_1ValidityConditions missing in all framesEnturERRORstructure
VALIDITY_CONDITIONS_IN_LINE_FILE_2ValidityConditions missing in ServiceFramesEnturERRORstructure
VALIDITY_CONDITIONS_IN_LINE_FILE_3ValidityConditions missing in ServiceCalendarFramesEnturERRORstructure
VALIDITY_CONDITIONS_IN_LINE_FILE_4ValidityConditions missing in TimeTableFramesEnturERRORstructure
VALIDITY_CONDITIONS_IN_LINE_FILE_5ValidityConditions missing in VehicleScheduleFrameEnturERRORstructure
VERSION_NON_NUMERICNon-numeric NeTEx versionEnturWARNINGformat
XML_SCHEMA_ERRORNeTEx XML Schema validation errorEnturCRITICALstructure
XML_SCHEMA_WARNINGNeTEx XML Schema validation warningEnturWARNINGstructure
attribution_without_roleAttribution with no role.MobilityDataWARNINGintegrity
bidirectional_exit_gatePathway is bidirectional and has mode 7 (exit gate).MobilityDataERRORsemantic
big_gap_in_serviceA service has a gap of more than 13 days between active service dates.MobilityDataINFOcurrency
block_trips_with_overlapping_stop_timesTrips with the same block id have overlapping stop times.MobilityDataERRORsemantic
csv_parsing_failedParsing of a CSV file failed.MobilityDataERRORstructure
decreasing_or_equal_stop_time_distanceDecreasing or equal `shape_dist_traveled` in `stop_times.txt`.MobilityDataERRORsemantic
decreasing_shape_distanceDecreasing `shape_dist_traveled` in `shapes.txt`.MobilityDataERRORsemantic
duplicate_fare_mediaTwo distinct fare media have the same fare media name and type.MobilityDataWARNINGquality
duplicate_geo_json_keyA key in `locations.geojson` is duplicated.MobilityDataERRORstructure
duplicate_geography_idGeography id is duplicated across multiple files.MobilityDataERRORintegrity
duplicate_keyDuplicated entity.MobilityDataERRORintegrity
duplicate_route_nameTwo 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`.MobilityDataWARNINGquality
duplicated_columnDuplicated column in CSV.MobilityDataERRORstructure
empty_column_nameA column name is empty.MobilityDataERRORstructure
empty_fileA CSV file is empty.MobilityDataERRORstructure
empty_rowA row in the input file has only spaces.MobilityDataWARNINGstructure
equal_shape_distance_diff_coordinatesTwo consecutive points have equal `shape_dist_traveled` and different lat/lon coordinates in `shapes.txt` and the distance between the two points is greater than the 1.11m.MobilityDataERRORsemantic
equal_shape_distance_diff_coordinates_distance_below_thresholdTwo consecutive points have equal `shape_dist_traveled` and different lat/lon coordinates in `shapes.txt` and the distance between the two points is greater than 0 but less than 1.11m.MobilityDataWARNINGsemantic
equal_shape_distance_same_coordinatesTwo consecutive points have equal `shape_dist_traveled` and the same lat/lon coordinates in `shapes.txt`.MobilityDataWARNINGquality
expired_calendarDataset should not contain date ranges for services that have already expired.MobilityDataWARNINGcurrency
fare_product_with_multiple_default_rider_categoriesThis notice is generated when a fare product is associated with multiple rider categories that are marked as default.MobilityDataERRORsemantic
fare_transfer_rule_duration_limit_type_without_duration_limitA row from GTFS file `fare_transfer_rules.txt` has a defined `duration_limit_type` field but no `duration_limit` specified.MobilityDataERRORintegrity
fare_transfer_rule_duration_limit_without_typeA row from GTFS file `fare_transfer_rules.txt` has a defined `duration_limit` field but no `duration_limit_type` specified.MobilityDataERRORintegrity
fare_transfer_rule_invalid_transfer_countA row from GTFS file `fare_transfer_rules.txt` has a defined `transfer_count` with an invalid value.MobilityDataERRORformat
fare_transfer_rule_missing_transfer_countA row from `fare_transfer_rules.txt` has `from_leg_group_id` equal to `to_leg_group_id`, but has no `transfer_count` specified.MobilityDataintegrity
fare_transfer_rule_with_forbidden_transfer_countA row from `fare_transfer_rules.txt` has `from_leg_group_id` not equal to `to_leg_group_id`, but has `transfer_count` specified.MobilityDataERRORintegrity
fare_transfer_rule_without_transfer_countA row from `fare_transfer_rules.txt` has `from_leg_group_id` equal to `to_leg_group_id`, but has no `transfer_count` specified.MobilityDataERRORintegrity
fast_travel_between_consecutive_stopsA transit vehicle moves too fast between two consecutive stops.MobilityDataWARNINGplausibility
fast_travel_between_far_stopsA transit vehicle moves too fast between two far stops.MobilityDataWARNINGplausibility
feed_expiration_date30_daysDataset should cover at least the next 30 days of service.MobilityDataWARNINGcurrency
feed_expiration_date7_daysDataset should be valid for at least the next 7 days.MobilityDataWARNINGcurrency
feed_info_lang_and_agency_lang_mismatchMismatching feed and agency language fields.MobilityDataWARNINGsemantic
feed_valid_beyond_total_service_windowThe feed is valid 14 days beyond its total service window.MobilityDataINFOcurrency
forbidden_arrival_or_departure_timeThe arrival or departure times are provided alongside pickup or drop-off windows in `stop_times.txt`.MobilityDataERRORintegrity
forbidden_continuous_pickup_drop_offContinuous pickup or drop-off are forbidden when routes.continuous_pickup or routes.continuous_drop_off are 0, 2 or 3 and stop_times.start_pickup_drop_off_window or stop_times.end_pickup_drop_off_window are defined for any trip of this route.MobilityDataERRORintegrity
forbidden_drop_off_typepickup_drop_off_window fields are forbidden when the drop_off_type is regularly scheduled (0).MobilityDataERRORintegrity
forbidden_geography_idA stop_time entry has more than one geographical id defined.MobilityDataERRORintegrity
forbidden_pickup_typepickup_drop_off_window fields are forbidden when the pickup_type is regularly scheduled (0) or must be coordinated with the driver (3).MobilityDataERRORintegrity
forbidden_prior_day_booking_field_valueA forbidden field value is present for a prior-day booking rule in `booking_rules.txt`MobilityDataERRORintegrity
forbidden_prior_notice_start_day`prior_notice_start_day` value is forbidden when `prior_notice_duration_max` is set.MobilityDataERRORintegrity
forbidden_prior_notice_start_time`prior_notice_start_time` value is forbidden when `prior_notice_start_day` value is not set in booking_rules.txt.MobilityDataERRORintegrity
forbidden_real_time_booking_field_valueA forbidden field value is present for a real-time booking rule in `booking_rules.txt`.MobilityDataERRORintegrity
forbidden_same_day_booking_field_valueA forbidden field value is present for a same-day booking rule in `booking_rules.txt`.MobilityDataERRORintegrity
forbidden_shape_dist_traveledA stop_time entry has a `shape_dist_traveled` without a `stop_id` value.MobilityDataERRORintegrity
foreign_key_violationWrong foreign key.MobilityDataERRORintegrity
future_calendarAll services in the feed start in the future; no service covers today's date.MobilityDataINFOcurrency
future_feedThe feed covers the future only.MobilityDataINFOcurrency
geo_json_duplicated_elementDuplicated elements in locations.geojson file.MobilityDataERRORstructure
geo_json_unknown_elementUnknown elements in locations.geojson file.MobilityDataINFOstructure
i_o_errorError in IO operation.MobilityDataERRORruntime
inconsistent_agency_langInconsistent language among agencies.MobilityDataWARNINGsemantic
inconsistent_agency_timezoneInconsistent Timezone among agencies.MobilityDataERRORsemantic
inconsistent_route_type_for_block_idA block should have the same route mode.MobilityDataWARNINGsemantic
inconsistent_route_type_for_in_seat_transferAn in-seat transfer should occur in the same route mode.MobilityDataWARNINGsemantic
invalid_characterThis field contains invalid characters, such as the replacement character ("\uFFFD").MobilityDataERRORformat
invalid_colorA field contains an invalid color value.MobilityDataERRORformat
invalid_currencyA field contains a wrong currency code.MobilityDataERRORformat
invalid_currency_amountA currency amount field has a value that does not match the format of its corresponding currency code field.MobilityDataERRORformat
invalid_dateA field cannot be parsed as date.MobilityDataERRORformat
invalid_emailA field contains a malformed email address.MobilityDataERRORformat
invalid_floatA field cannot be parsed as a floating point number.MobilityDataERRORformat
invalid_geometryA polygon in `locations.geojson` is unparsable or invalid.MobilityDataERRORformat
invalid_input_files_in_subfolderAt least 1 GTFS file is in a subfolder.MobilityDataERRORpackage
invalid_integerA field cannot be parsed as an integer.MobilityDataERRORformat
invalid_language_codeA field contains a wrong language code.MobilityDataERRORformat
invalid_phone_numberA field contains a malformed phone number.MobilityDataERRORformat
invalid_pickup_drop_off_windowThe pickup/drop-off window in `stop_times.txt` is invalid.MobilityDataERRORsemantic
invalid_prior_notice_duration_minAn invalid `prior_notice_duration_min` value is present in a booking rule.MobilityDataERRORsemantic
invalid_row_lengthInvalid csv row length.MobilityDataERRORstructure
invalid_timeA field cannot be parsed as time.MobilityDataERRORformat
invalid_timezoneA field cannot be parsed as a timezone.MobilityDataERRORformat
invalid_urlA field contains a malformed URL.MobilityDataERRORformat
leading_or_trailing_whitespacesThe value in CSV file has leading or trailing whitespaces.MobilityDataWARNINGstructure
location_with_unexpected_stop_timeA location in `stops.txt` that is not a stop is referenced by some `stop_times.stop_id`.MobilityDataERRORsemantic
location_without_parent_stationA location that must have `parent_station` field does not have it.MobilityDataERRORintegrity
malformed_jsonA JSON file is malformed.MobilityDataERRORstructure
missing_bike_allowanceFerry trips should include bike allowance information.MobilityDataWARNINGquality
missing_calendar_and_calendar_date_filesMissing GTFS files `calendar.txt` and `calendar_dates.txt`.MobilityDataERRORpackage
missing_feed_contact_email_and_urlBest Practices for `feed_info.txt` suggest providing at least one of `feed_contact_email` and `feed_contact_url`.MobilityDataWARNINGquality
missing_feed_info_dateOne of `feed_start_date` or `feed_end_date` is specified, but not both.MobilityDataWARNINGintegrity
missing_level_id`stops.level_id` is conditionally required.MobilityDataERRORintegrity
missing_pickup_drop_off_booking_rule_idpickup_booking_rule_id is recommended when pickup_type=2 and drop_off_booking_rule_id is recommended when drop_off_type=2.MobilityDataWARNINGintegrity
missing_pickup_or_drop_off_windowEither the start or end pickup/drop-off window is missing in `stop_times.txt`.MobilityDataERRORintegrity
missing_prior_day_booking_field_valueThe `prior_notice_last_day` and the `prior_notice_last_time` values are required for prior day `booking_type` in booking_rules.txt.MobilityDataintegrity
missing_prior_notice_duration_min`prior_notice_duration_min` value is required for same day `booking_type` in booking_rules.txt.MobilityDataERRORintegrity
missing_prior_notice_last_dayThe `prior_notice_last_day` is required when booking_type=2 (prior day booking) is specified in booking_rules.txt.MobilityDataERRORintegrity
missing_prior_notice_last_timeThe `prior_notice_last_time` is required when booking_type=2 (prior day booking) is specified in booking_rules.txt.MobilityDataERRORintegrity
missing_prior_notice_start_time`prior_notice_start_time` value is required when `prior_notice_start_day` value is set in booking_rules.txt.MobilityDataERRORintegrity
missing_recommended_columnA recommended column is missing in the input file.MobilityDataquality
missing_recommended_fieldA recommended field is missing.MobilityDataWARNINGquality
missing_recommended_fileA recommended file is missing.MobilityDataWARNINGquality
missing_required_agency_idAgency id is required when there are multiple agencies.MobilityDataERRORintegrity
missing_required_columnA required column is missing in the input file.MobilityDataERRORstructure
missing_required_elementA required element is missing in `locations.geojson`.MobilityDataERRORstructure
missing_required_fieldA required field is missing.MobilityDataERRORstructure
missing_required_fileA required file is missing.MobilityDataERRORpackage
missing_stop_name`stops.stop_name` is required for `location_type` equal to `0`, `1`, or `2`.MobilityDataERRORintegrity
missing_stop_times_recordOnly one stop_times record is found where two are required.MobilityDataERRORsemantic
missing_timepoint_value`stop_times.timepoint` value is missing for a record.MobilityDataWARNINGintegrity
missing_trip_edgeMissing trip edge `arrival_time` or `departure_time`.MobilityDataERRORsemantic
mixed_case_recommended_fieldThis field has customer-facing text and should use Mixed Case (should contain upper and lower case letters).MobilityDataWARNINGquality
more_than_one_entityMore than one row in CSV.MobilityDataWARNINGstructure
new_line_in_valueNew line or carriage return in a value in CSV file.MobilityDataERRORstructure
non_ascii_or_non_printable_charNon ascii or non printable char in ID field.MobilityDataWARNINGquality
number_out_of_rangeOut of range value.MobilityDataERRORformat
overlapping_frequencyTrip frequencies overlap.MobilityDataERRORsemantic
overlapping_zone_and_pickup_drop_off_windowTwo entities have overlapping pickup/drop-off windows and zones.MobilityDataERRORsemantic
pathway_dangling_generic_nodeA generic node has only one incident location in a pathway graph.MobilityDataWARNINGsemantic
pathway_loopA pathway starts and ends at the same location.MobilityDataWARNINGsemantic
pathway_to_platform_with_boarding_areasA pathway has an endpoint that is a platform which has boarding areas.MobilityDataERRORsemantic
pathway_to_stop_with_access_outside_of_station_pathwaysA pathway has an endpoint that is a stop with stop_access=1, which should be accessible outside of the station's pathways.MobilityDataERRORsemantic
pathway_to_wrong_location_typeA pathway has an endpoint that is a station.MobilityDataERRORsemantic
pathway_unreachable_locationA location is not reachable at least in one direction: from the entrances or to the exits.MobilityDataERRORsemantic
platform_without_parent_stationA platform has no `parent_station` field set.MobilityDataINFOintegrity
point_near_originA point is too close to origin `(0, 0)`.MobilityDataERRORplausibility
point_near_poleA point is too close to the North or South Pole.MobilityDataERRORplausibility
prior_notice_last_day_after_start_dayPrior notice last day should not be greater than the prior notice start day in booking_rules.txt.MobilityDataERRORsemantic
route_both_short_and_long_name_missingBoth `route_short_name` and `route_long_name` are missing for a route.MobilityDataERRORintegrity
route_color_contrastInsufficient route color contrast.MobilityDataWARNINGquality
route_long_name_contains_short_nameLong name should not contain short name for a single route.MobilityDataWARNINGquality
route_networks_specified_in_more_than_one_fileIndicates that route network identifiers are specified across multiple files.MobilityDataERRORintegrity
route_short_name_too_longShort name of a route is too long (more than 12 characters).MobilityDataWARNINGquality
runtime_exception_in_loader_errorRuntimeException while loading GTFS dataset in memory.MobilityDataERRORruntime
runtime_exception_in_validator_errorRuntimeException while validating GTFS archive.MobilityDataERRORruntime
same_name_and_description_for_routeSame name and description for route.MobilityDataWARNINGquality
same_name_and_description_for_stopSame name and description for stop.MobilityDataWARNINGquality
same_route_and_agency_urlSame `routes.route_url` and `agency.agency_url`.MobilityDataWARNINGquality
same_stop_and_agency_urlSame `stops.stop_url` and `agency.agency_url`.MobilityDataWARNINGquality
same_stop_and_route_urlSame `stops.stop_url` and `routes.route_url`.MobilityDataWARNINGquality
service_extends_far_in_the_futureA service end date is more than 2 years in the future.MobilityDataINFOcurrency
service_has_no_active_day_of_the_weekA service is not valid for any day of the week.MobilityDataWARNINGsemantic
service_window_outside_feed_periodA service window is not covered by the feed's validity period.MobilityDataINFOcurrency
single_shape_pointThe shape within `shapes.txt` contains a single shape point.MobilityDataWARNINGsemantic
start_and_end_range_equalTwo date or time fields are equal.MobilityDataERRORsemantic
start_and_end_range_out_of_orderTwo date or time fields are out of order.MobilityDataERRORsemantic
station_with_parent_stationA station has `parent_station` field set.MobilityDataERRORintegrity
stop_access_specified_for_incorrect_locationA location that is not a stop has stop_access specified.MobilityDataERRORintegrity
stop_access_specified_for_stop_with_no_parent_stationA stop without a value for parent station has stop_access specified.MobilityDataERRORintegrity
stop_has_too_many_matches_for_shapeStop entry that has many potential matches to the trip's path of travel, as defined by the shape entry in `shapes.txt`.MobilityDataWARNINGplausibility
stop_time_timepoint_without_times`arrival_time` or `departure_time` not specified for timepoint.MobilityDataERRORintegrity
stop_time_with_arrival_before_previous_departure_timeBackwards time travel between stops in `stop_times.txt`MobilityDataERRORsemantic
stop_time_with_only_arrival_or_departure_timeMissing `stop_times.arrival_time` or `stop_times.departure_time`.MobilityDataERRORintegrity
stop_too_far_from_shapeStop too far from trip shape.MobilityDataWARNINGplausibility
stop_too_far_from_shape_using_user_distanceStop time too far from shape.MobilityDataWARNINGplausibility
stop_without_location`stop_lat` and/or `stop_lon` is missing for stop with `location_type` equal to`0`, `1`, or `2`MobilityDataERRORintegrity
stop_without_stop_timeA stop in `stops.txt` is not referenced by any `stop_times.stop_id`.MobilityDataWARNINGquality
stop_without_zone_idStop without value for `stops.zone_id` contained in a route with a zone-dependent fare rule.MobilityDataINFOintegrity
stops_match_shape_out_of_orderTwo stop entries are different than their arrival-departure order defined by `shapes.txt`.MobilityDataWARNINGplausibility
thread_execution_errorExecutionException during multithreaded validationMobilityDataERRORruntime
timeframe_only_start_or_end_time_specifiedA row from `timeframes.txt` was found with only one of `start_time` and `end_time` specified.MobilityDataERRORintegrity
timeframe_overlapTwo entries in `timeframes.txt` with the same `timeframe_group_id` and `service_id` have overlapping time intervals.MobilityDataERRORsemantic
timeframe_start_or_end_time_greater_than_twenty_four_hoursA time in `timeframes.txt` is greater than `24:00:00`.MobilityDataERRORformat
too_many_rowsA CSV file has too many rows.MobilityDataERRORstructure
transfer_distance_above_2_kmThe transfer distance from stop to stop in `transfers.txt` is larger than 2 km.MobilityDataINFOplausibility
transfer_distance_too_largeThe transfer distance from stop to stop in `transfers.txt` is larger than 10 km.MobilityDataWARNINGplausibility
transfer_with_invalid_stop_location_typeA stop id field from GTFS file `transfers.txt` references a stop that has a `location_type` other than 0 or 1 (aka Stop/Platform or Station).MobilityDataERRORintegrity
transfer_with_invalid_trip_and_routeA trip id field from GTFS file `transfers.txt` references a route that does not match its `trips.txt` `route_id`.MobilityDataERRORintegrity
transfer_with_invalid_trip_and_stopA trip id field from GTFS file `transfers.txt` references a stop that is not included in the referenced trip's stop-times.MobilityDataERRORintegrity
transfer_with_suspicious_mid_trip_in_seatA trip id field from GTFS file `transfers.txt` with an in-seat transfer type references a stop that is not in the expected position in the trip's stop-times.MobilityDataWARNINGplausibility
translation_foreign_key_violationAn entity with the given `record_id` and `record_sub_id` cannot be found in the referenced table.MobilityDataERRORintegrity
translation_unexpected_valueA field in a translations row has value but must be empty.MobilityDataERRORintegrity
translation_unknown_table_nameA translation references an unknown or missing GTFS table.MobilityDataWARNINGintegrity
trip_coverage_not_active_for_next7_daysTrips data should be valid for at least the next seven days.MobilityDataWARNINGcurrency
trip_distance_exceeds_shape_distanceThe distance between the last shape point and last stop point is greater than or equal to the 11.1m threshold.MobilityDataERRORsemantic
trip_distance_exceeds_shape_distance_below_thresholdThe distance between the last shape point and last stop point is greater than 0 but less than the 11.1m threshold.MobilityDataWARNINGsemantic
trip_headsign_matches_intermediate_stopTrip headsign matches the name of an intermediate stop, not the last stop.MobilityDataINFOquality
trip_with_shape_dist_traveled_but_no_shape_distancesA trip has shape_dist_traveled values in stop_times.txt but the shape referenced by the trip's shape_id does not have shape_dist_traveled values on all of its points in shapes.txt.MobilityDataINFOsemantic
u_r_i_syntax_errorA string could not be parsed as a URI reference.MobilityDataERRORformat
unexpected_enum_valueAn enum has an unexpected value.MobilityDataWARNINGformat
unknown_columnA column name is unknown.MobilityDataINFOstructure
unknown_fileA file is unknown.MobilityDataINFOpackage
unsorted_stop_timesStop times are not sorted by trip_id and stop_sequence.MobilityDataINFOquality
unsupported_feature_typeAn unsupported feature type is used in the `locations.geojson` file.MobilityDataERRORstructure
unsupported_geo_json_typeAn unsupported GeoJSON type is used in the `locations.geojson` file.MobilityDataERRORstructure
unsupported_geometry_typeA GeoJSON feature has an unsupported geometry type in `locations.geojson`.MobilityDataERRORstructure
unusable_tripTrips must have more than one stop to be usable.MobilityDataWARNINGsemantic
unused_parent_stationUnused parent station.MobilityDataquality
unused_shapeShape is not used in GTFS file `trips.txt`.MobilityDataWARNINGquality
unused_stationUnused station.MobilityDataINFOquality
unused_tripTrip is not be used in `stop_times.txt`MobilityDataWARNINGquality
wrong_parent_location_typeIncorrect type of the parent location.MobilityDataERRORintegrity

Co-financed by the Connecting Europe Facility of the European Union