Resource details

File name: https://eu.ftp.opendatasoft.com/sncf/gtfs/transilien-netexfr.zip
Format: NeTEx
Size: 6.41 MB

fichier NETEX

This resource file is part of the dataset SNCF Transilien.

Download availability

2025-12-15
100%
2025-12-16
100%
2025-12-17
100%
2025-12-18
100%
2025-12-19
100%
2025-12-20
100%
2025-12-21
100%
2025-12-22
100%
2025-12-23
100%
2025-12-24
100%
2025-12-25
100%
2025-12-26
100%
2025-12-27
100%
2025-12-28
100%
2025-12-29
100%
2025-12-30
100%
2025-12-31
100%
2026-01-01
100%
2026-01-02
100%
2026-01-03
100%
2026-01-04
100%
2026-01-05
100%
2026-01-06
100%
2026-01-07
100%
2026-01-08
100%
2026-01-09
100%
2026-01-10
100%
2026-01-11
100%
2026-01-12
100%
2026-01-13
100%
2026-01-14
100%
Learn more
We test this resource download availability every hour by making an HTTP HEAD request with a timeout of 5 seconds. If we detect a downtime, we perform subsequent tests every 10 minutes, until the resource is back online.

For SIRI and SIRI Lite feeds, we perform a GET request: a 401 or 405 status code is considered successful. In case of HTTP 500, the feed will be considered unavailable, unless the body appears to contain SOAP.

Validation report

9,826 errors

  • XSD NeTEx (1,968 errors)

    Every NeTEx resource must comply with the NeTEX XSD, regardless of its profile. The XSD validation does not cover choices made by the French profile.

    Amongst most frequent errors, check that ids are unique, that elements are in the expected order, and that no mandatory attribute is missing.

  • Base rules (7,893 errors)

    These rules are common best practices. They are shared by all NeTEx profiles. Their documentation can be found on enRoute's Wiki.

  • Validation of NeTEx resources is still a work in progress. Currently, we only check that any resource in NeTEx respects the XSD schema and follows some best practices. We do not yet check the compliance with the French profile (nor the dataset structure nor mandatory attributes).
Message Location
A Line has a Presentation lignes.xml:221
Details for debugging purposes
{
  "code": "line-presentation-mandatory",
  "criticity": "warning",
  "message": "A Line has a Presentation",
  "resource": {
    "filename": "lignes.xml",
    "line": 221
  }
}
A Line has a Presentation lignes.xml:226
Details for debugging purposes
{
  "code": "line-presentation-mandatory",
  "criticity": "warning",
  "message": "A Line has a Presentation",
  "resource": {
    "filename": "lignes.xml",
    "line": 226
  }
}
A Line has a Presentation lignes.xml:231
Details for debugging purposes
{
  "code": "line-presentation-mandatory",
  "criticity": "warning",
  "message": "A Line has a Presentation",
  "resource": {
    "filename": "lignes.xml",
    "line": 231
  }
}
A Line has a Presentation lignes.xml:236
Details for debugging purposes
{
  "code": "line-presentation-mandatory",
  "criticity": "warning",
  "message": "A Line has a Presentation",
  "resource": {
    "filename": "lignes.xml",
    "line": 236
  }
}
A Line has a Presentation lignes.xml:241
Details for debugging purposes
{
  "code": "line-presentation-mandatory",
  "criticity": "warning",
  "message": "A Line has a Presentation",
  "resource": {
    "filename": "lignes.xml",
    "line": 241
  }
}
A Line has a Presentation lignes.xml:246
Details for debugging purposes
{
  "code": "line-presentation-mandatory",
  "criticity": "warning",
  "message": "A Line has a Presentation",
  "resource": {
    "filename": "lignes.xml",
    "line": 246
  }
}
A Line has a Presentation lignes.xml:251
Details for debugging purposes
{
  "code": "line-presentation-mandatory",
  "criticity": "warning",
  "message": "A Line has a Presentation",
  "resource": {
    "filename": "lignes.xml",
    "line": 251
  }
}
A Line has a Presentation lignes.xml:256
Details for debugging purposes
{
  "code": "line-presentation-mandatory",
  "criticity": "warning",
  "message": "A Line has a Presentation",
  "resource": {
    "filename": "lignes.xml",
    "line": 256
  }
}
A Line has a Presentation lignes.xml:261
Details for debugging purposes
{
  "code": "line-presentation-mandatory",
  "criticity": "warning",
  "message": "A Line has a Presentation",
  "resource": {
    "filename": "lignes.xml",
    "line": 261
  }
}
A Line has a Presentation lignes.xml:266
Details for debugging purposes
{
  "code": "line-presentation-mandatory",
  "criticity": "warning",
  "message": "A Line has a Presentation",
  "resource": {
    "filename": "lignes.xml",
    "line": 266
  }
}
A Line has a Presentation lignes.xml:271
Details for debugging purposes
{
  "code": "line-presentation-mandatory",
  "criticity": "warning",
  "message": "A Line has a Presentation",
  "resource": {
    "filename": "lignes.xml",
    "line": 271
  }
}
Quay, StopPlace and StopPlaceEntrance have a Latitude Unknown location
Details for debugging purposes
{
  "code": "latitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Latitude",
  "resource": {
    "line": 20318
  }
}
Quay, StopPlace and StopPlaceEntrance have a Longitude Unknown location
Details for debugging purposes
{
  "code": "longitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Longitude",
  "resource": {
    "line": 20318
  }
}
Quay, StopPlace and StopPlaceEntrance have a Latitude Unknown location
Details for debugging purposes
{
  "code": "latitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Latitude",
  "resource": {
    "line": 20328
  }
}
Quay, StopPlace and StopPlaceEntrance have a Longitude Unknown location
Details for debugging purposes
{
  "code": "longitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Longitude",
  "resource": {
    "line": 20328
  }
}
Quay, StopPlace and StopPlaceEntrance have a Latitude Unknown location
Details for debugging purposes
{
  "code": "latitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Latitude",
  "resource": {
    "line": 20366
  }
}
Quay, StopPlace and StopPlaceEntrance have a Longitude Unknown location
Details for debugging purposes
{
  "code": "longitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Longitude",
  "resource": {
    "line": 20366
  }
}
Quay, StopPlace and StopPlaceEntrance have a Latitude Unknown location
Details for debugging purposes
{
  "code": "latitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Latitude",
  "resource": {
    "line": 20376
  }
}
Quay, StopPlace and StopPlaceEntrance have a Longitude Unknown location
Details for debugging purposes
{
  "code": "longitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Longitude",
  "resource": {
    "line": 20376
  }
}
Quay, StopPlace and StopPlaceEntrance have a Latitude Unknown location
Details for debugging purposes
{
  "code": "latitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Latitude",
  "resource": {
    "line": 20434
  }
}
Elapsed time: 7 minutes and 53 seconds.

Validation carried out using the current NeTEx file the 2026-01-14 at 07:26 Europe/Paris using the enRoute Chouette Valid validator.

Other resources