The SNCF NeTEx data has several problems:
Il y a es problèmes dans le fichier NeTEx.
- Il n'est pas valide avec la version 1.3.0 du NeTEx XSD.
- EPSG::4326, devrait être soit EPSG:4326 ou urn:ogc:def:crs:EPSG::4326. Nous avions déjà mentionné cela il y a 8 mois dans des autres fichiers de la SNCF.
- il y a beaucoup de ref vide ref="". Et se sont des ref mandatoires (e.g. <OperatorRef ref="" version="any"/>.
- si l’attribut dataSourceRef est défini dataSourceRef=»2148» , alors une DataSource doit être définie
- De ne pas avoir des OperatorRef dans Line est une mauvais idée (par exemple Line id="OCESN-87686006-87741793" version="any">). Il y a plusieurs lines avec des informations incomplètes
The most problematic in my view is that they have "Line" without OperatorRef. The OperatorRef is in the ServiceJourney
e.g.
<Line id="OCESN-87686006-87741793" version="any">
<Name> -</Name>
<Description/>
<TransportMode>unknown</TransportMode>
<PublicCode>INCONNU</PublicCode>
<routes>
<RouteRef ref="FR:Route::SN7891FERRE_5931159"/>
<RouteRef ref="FR:Route::SN7891FERRE_5931160"/>
<RouteRef ref="FR:Route::SN7891FERRE_5931162"/>
<RouteRef ref="FR:Route::SN7891FERRE_5931168"/>
<RouteRef ref="FR:Route::SN7891FERRE_5931170"/>
<RouteRef ref="FR:Route::SN7891FERRE_5931177"/>
<RouteRef ref="FR:Route::SN7891FERRE_5931179"/>
<RouteRef ref="FR:Route::SN7891FERRE_5931180"/>
<RouteRef ref="FR:Route::SN7891FERRE_6468899"/>
<RouteRef ref="FR:Route::SN7891FERRE_6468900"/>
<RouteRef ref="FR:Route::SN7891FERRE_6468903"/>
<RouteRef ref="FR:Route::SN7891FERRE_6468904"/>
<RouteRef ref="FR:Route::SN7891FERRE_6514791"/>
<RouteRef ref="FR:Route::SN7891FERRE_7276586"/>
<RouteRef ref="FR:Route::SN7891FERRE_7530815"/>
</routes>
</Line>
<ServiceJourney id="FR:ServiceJourney::SN7891FERRE_5931159" responsibilitySetRef="1187" dataSourceRef="2148" version="any" status="active">
<ValidBetween>
<FromDate>2026-01-23T00:00:00</FromDate>
<ToDate>2026-06-22T23:59:59</ToDate>
</ValidBetween>
<BrandingRef ref="TGVOUIGO"/>
<Distance>0</Distance>
<TransportMode>rail</TransportMode>
<TransportSubmode>
<RailSubmode>highSpeedRail</RailSubmode>
</TransportSubmode>
<ServiceAlteration>planned</ServiceAlteration>
<DepartureTime>10:46:00</DepartureTime>
<dayTypes>
<DayTypeRef ref="FR:DayType:4253:"/>
</dayTypes>
<JourneyPatternRef ref="FR:ServiceJourneyPattern::SN7891FERRE_5931159"/>
<OperatorRef ref="FR:Operator::07B82396-04B1-48F0-84BF-36C7F1B81442:" version="any"/>
<LineRef ref="OCESN-87686006-87741793" version="any"/>
<trainNumbers>
<TrainNumberRef ref="FR:TrainNumber::SN7891FERRE_5931159" version="any"/>
</trainNumbers>
In the transformation this results in may defect lines in the current software.
Imported it looked like this. Which is ok:
We have also this case
The ServiceJourney does not have an Operator and the Line neither:
Can and should we fix the first? should we invent an agency for the second in the GTFS ?
The SNCF NeTEx data has several problems:
The most problematic in my view is that they have "Line" without OperatorRef. The OperatorRef is in the ServiceJourney
e.g.
In the transformation this results in may defect lines in the current software.
Imported it looked like this. Which is ok:
We have also this case
The ServiceJourney does not have an Operator and the Line neither:
Can and should we fix the first? should we invent an agency for the second in the GTFS ?