Rules by enRoute

As of today, enRoute has created 2 sets of rules.

Most straightforward: XML Schema

The objective is to ensure the dataset and each of its file is compliant with NeTEx XML Schema (XSD).

2 options are possible:

• The current XSD: https://github.com/NeTEx-CEN/NeTEx

• The upcoming XSD: https://github.com/NeTEx-CEN/NeTEx/tree/next

Checking against the upcoming XSD allows to make its dataset future-proof of changes/ evolutions of the norm.

The starter kit

These rules have been designed by enRoute team. They cover some of the most basic checks that can be performed on datasets.

The starter kit includes the following rules:

• A StopPlace, Line, Operator, Network, GroupOfLines has a Name

• A ShortName have 12 or less than characters

• A PublicCode have 12 or less than characters

• Quay, StopPlace, StopPlaceEntrance have a Location (Longitude & Latitude)

• A Line has a TransportMode attribute

• A Line has a PresentationColor (warning only)

• A Line doesn’t define its own routes

• A Route has a LineRef

• A (Service)JourneyPattern has a RouteRef

• A ServiceJourney has a JourneyPatternRef

• A (Service)JourneyPattern has two or more pointsInSequence

• A ServiceJourney has one or more dayTypes

• A ServiceJourney has two or more passingTimes

• A DestinationDisplay have a FrontText attribute

• A PassengerStopAssignment has a ScheduledStopPointRef

• Any NeTEx id uses less than 256 characters (warning only)

• TimedPassingTimes are with chronological passing times

It also checks that Referenced Resources are present for:

• ScheduledStopPoint

• Operator

• DayType

• Route

• JourneyPattern

• DestinationDisplay

• Direction

• RoutePoint

The below json file details all the rules contained in the enRoute starter kit:

Open