Resource details

File name: Trains Express Régionaux ZOU ( Format NeTEx)
Format: NeTEx
Size: 935.41 KB

This resource file is part of the dataset Trains régionaux ZOU !.

Download availability

2025-12-14
100%
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%
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

5,682 errors

  • XSD NeTEx (3,820 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 (1,890 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
Quay, StopPlace and StopPlaceEntrance have a Latitude arrets.xml:6017
Details for debugging purposes
{
  "code": "latitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Latitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6017
  }
}
Quay, StopPlace and StopPlaceEntrance have a Longitude arrets.xml:6017
Details for debugging purposes
{
  "code": "longitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Longitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6017
  }
}
Quay, StopPlace and StopPlaceEntrance have a Latitude arrets.xml:6033
Details for debugging purposes
{
  "code": "latitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Latitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6033
  }
}
Quay, StopPlace and StopPlaceEntrance have a Longitude arrets.xml:6033
Details for debugging purposes
{
  "code": "longitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Longitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6033
  }
}
Quay, StopPlace and StopPlaceEntrance have a Latitude arrets.xml:6043
Details for debugging purposes
{
  "code": "latitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Latitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6043
  }
}
Quay, StopPlace and StopPlaceEntrance have a Longitude arrets.xml:6043
Details for debugging purposes
{
  "code": "longitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Longitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6043
  }
}
Quay, StopPlace and StopPlaceEntrance have a Latitude arrets.xml:6059
Details for debugging purposes
{
  "code": "latitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Latitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6059
  }
}
Quay, StopPlace and StopPlaceEntrance have a Longitude arrets.xml:6059
Details for debugging purposes
{
  "code": "longitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Longitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6059
  }
}
Quay, StopPlace and StopPlaceEntrance have a Latitude arrets.xml:6069
Details for debugging purposes
{
  "code": "latitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Latitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6069
  }
}
Quay, StopPlace and StopPlaceEntrance have a Longitude arrets.xml:6069
Details for debugging purposes
{
  "code": "longitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Longitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6069
  }
}
Quay, StopPlace and StopPlaceEntrance have a Latitude arrets.xml:6085
Details for debugging purposes
{
  "code": "latitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Latitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6085
  }
}
Quay, StopPlace and StopPlaceEntrance have a Longitude arrets.xml:6085
Details for debugging purposes
{
  "code": "longitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Longitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6085
  }
}
Quay, StopPlace and StopPlaceEntrance have a Latitude arrets.xml:6095
Details for debugging purposes
{
  "code": "latitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Latitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6095
  }
}
Quay, StopPlace and StopPlaceEntrance have a Longitude arrets.xml:6095
Details for debugging purposes
{
  "code": "longitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Longitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6095
  }
}
Quay, StopPlace and StopPlaceEntrance have a Latitude arrets.xml:6111
Details for debugging purposes
{
  "code": "latitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Latitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6111
  }
}
Quay, StopPlace and StopPlaceEntrance have a Longitude arrets.xml:6111
Details for debugging purposes
{
  "code": "longitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Longitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6111
  }
}
Quay, StopPlace and StopPlaceEntrance have a Latitude arrets.xml:6129
Details for debugging purposes
{
  "code": "latitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Latitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6129
  }
}
Quay, StopPlace and StopPlaceEntrance have a Longitude arrets.xml:6129
Details for debugging purposes
{
  "code": "longitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Longitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6129
  }
}
Quay, StopPlace and StopPlaceEntrance have a Latitude arrets.xml:6139
Details for debugging purposes
{
  "code": "latitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Latitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6139
  }
}
Quay, StopPlace and StopPlaceEntrance have a Longitude arrets.xml:6139
Details for debugging purposes
{
  "code": "longitude-mandatory",
  "criticity": "error",
  "message": "Quay, StopPlace and StopPlaceEntrance have a Longitude",
  "resource": {
    "filename": "arrets.xml",
    "line": 6139
  }
}
Elapsed time: 3 minutes and 13 seconds.

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

Other resources