Resource details

File name: Breizhgo Car 56
Format: NeTEx
Size: 382.81 KB

Fichier Netex

This resource file is part of the dataset Réseau interurbain BreizhGo Car.

It is valid from 2026-03-13 to 2026-07-03.

  • network : BreizhGo en Morbihan
  • transport mode : coach

Download availability

2026-02-14
100%
2026-02-15
100%
2026-02-16
100%
2026-02-17
100%
2026-02-18
100%
2026-02-19
100%
2026-02-20
100%
2026-02-21
100%
2026-02-22
100%
2026-02-23
100%
2026-02-24
100%
2026-02-25
100%
2026-02-26
100%
2026-02-27
99.5%
2026-02-28
100%
2026-03-01
100%
2026-03-02
100%
2026-03-03
100%
2026-03-04
100%
2026-03-05
100%
2026-03-06
100%
2026-03-07
100%
2026-03-08
100%
2026-03-09
100%
2026-03-10
100%
2026-03-11
100%
2026-03-12
100%
2026-03-13
100%
2026-03-14
100%
2026-03-15
100%
2026-03-16
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

23,887 errors

Download the report
As a CSV file: As a Parquet file:

Parquet is way more compact file format but it will require you to use some dedicated tooling.

Learn more about it here.

  • XSD NeTEx (23,887 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.

  • French profile

    Set of rules of the French profile.

  • Base rules (16 warnings)

    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 only partially check the compliance with the French profile.
Message Location
Attribute short_name doesn't match 'Loudéac - Rostrenen - Carhaix' Reseaux.xml:65
Details for debugging purposes
{
  "code": "shortname-length",
  "criticity": "warning",
  "message": "Attribute short_name doesn't match 'Loudéac - Rostrenen - Carhaix'",
  "resource": {
    "filename": "Reseaux.xml",
    "line": 65
  }
}
Attribute short_name doesn't match 'Auray-Quiberon' Reseaux.xml:77
Details for debugging purposes
{
  "code": "shortname-length",
  "criticity": "warning",
  "message": "Attribute short_name doesn't match 'Auray-Quiberon'",
  "resource": {
    "filename": "Reseaux.xml",
    "line": 77
  }
}
Attribute short_name doesn't match 'Baud - Camors - Grand-Champ - Vannes' Reseaux.xml:89
Details for debugging purposes
{
  "code": "shortname-length",
  "criticity": "warning",
  "message": "Attribute short_name doesn't match 'Baud - Camors - Grand-Champ - Vannes'",
  "resource": {
    "filename": "Reseaux.xml",
    "line": 89
  }
}
Attribute short_name doesn't match 'Vannes-Pontivy-Loudéac-St Brieuc' Reseaux.xml:110
Details for debugging purposes
{
  "code": "shortname-length",
  "criticity": "warning",
  "message": "Attribute short_name doesn't match 'Vannes-Pontivy-Loudéac-St Brieuc'",
  "resource": {
    "filename": "Reseaux.xml",
    "line": 110
  }
}
Attribute short_name doesn't match 'Ploermel - Malestroit - Vannes' Reseaux.xml:131
Details for debugging purposes
{
  "code": "shortname-length",
  "criticity": "warning",
  "message": "Attribute short_name doesn't match 'Ploermel - Malestroit - Vannes'",
  "resource": {
    "filename": "Reseaux.xml",
    "line": 131
  }
}
Attribute short_name doesn't match 'Vannes - Auray' Reseaux.xml:173
Details for debugging purposes
{
  "code": "shortname-length",
  "criticity": "warning",
  "message": "Attribute short_name doesn't match 'Vannes - Auray'",
  "resource": {
    "filename": "Reseaux.xml",
    "line": 173
  }
}
Attribute short_name doesn't match 'Auray - Vannes' Reseaux.xml:185
Details for debugging purposes
{
  "code": "shortname-length",
  "criticity": "warning",
  "message": "Attribute short_name doesn't match 'Auray - Vannes'",
  "resource": {
    "filename": "Reseaux.xml",
    "line": 185
  }
}
Attribute short_name doesn't match 'La Roche Bernard - Muzillac - Vannes' Reseaux.xml:206
Details for debugging purposes
{
  "code": "shortname-length",
  "criticity": "warning",
  "message": "Attribute short_name doesn't match 'La Roche Bernard - Muzillac - Vannes'",
  "resource": {
    "filename": "Reseaux.xml",
    "line": 206
  }
}
Attribute short_name doesn't match 'Rochefort-en-Terre - Questembert - Vannes' Reseaux.xml:227
Details for debugging purposes
{
  "code": "shortname-length",
  "criticity": "warning",
  "message": "Attribute short_name doesn't match 'Rochefort-en-Terre - Questembert - Vannes'",
  "resource": {
    "filename": "Reseaux.xml",
    "line": 227
  }
}
Attribute short_name doesn't match 'Pénestin - La Roche Bernard - Redon' Reseaux.xml:248
Details for debugging purposes
{
  "code": "shortname-length",
  "criticity": "warning",
  "message": "Attribute short_name doesn't match 'Pénestin - La Roche Bernard - Redon'",
  "resource": {
    "filename": "Reseaux.xml",
    "line": 248
  }
}
Attribute short_name doesn't match 'St-Jean-Brévelay - Plumelec - Monterblanc - Vannes' Reseaux.xml:269
Details for debugging purposes
{
  "code": "shortname-length",
  "criticity": "warning",
  "message": "Attribute short_name doesn't match 'St-Jean-Brévelay - Plumelec - Monterblanc - Vannes'",
  "resource": {
    "filename": "Reseaux.xml",
    "line": 269
  }
}
Attribute short_name doesn't match 'Redon - Plélan-le-Grand' Reseaux.xml:290
Details for debugging purposes
{
  "code": "shortname-length",
  "criticity": "warning",
  "message": "Attribute short_name doesn't match 'Redon - Plélan-le-Grand'",
  "resource": {
    "filename": "Reseaux.xml",
    "line": 290
  }
}
Attribute short_name doesn't match 'Pontivy - Guémené sur Scorff' Reseaux.xml:311
Details for debugging purposes
{
  "code": "shortname-length",
  "criticity": "warning",
  "message": "Attribute short_name doesn't match 'Pontivy - Guémené sur Scorff'",
  "resource": {
    "filename": "Reseaux.xml",
    "line": 311
  }
}
Attribute short_name doesn't match 'Carhaix - Gourin - Le Faouet - Lorient' Reseaux.xml:332
Details for debugging purposes
{
  "code": "shortname-length",
  "criticity": "warning",
  "message": "Attribute short_name doesn't match 'Carhaix - Gourin - Le Faouet - Lorient'",
  "resource": {
    "filename": "Reseaux.xml",
    "line": 332
  }
}
Attribute short_name doesn't match 'Lorient - Kervignac - Etel' Reseaux.xml:353
Details for debugging purposes
{
  "code": "shortname-length",
  "criticity": "warning",
  "message": "Attribute short_name doesn't match 'Lorient - Kervignac - Etel'",
  "resource": {
    "filename": "Reseaux.xml",
    "line": 353
  }
}
Attribute short_name doesn't match 'Pontivy - Baud - Lorient' Reseaux.xml:374
Details for debugging purposes
{
  "code": "shortname-length",
  "criticity": "warning",
  "message": "Attribute short_name doesn't match 'Pontivy - Baud - Lorient'",
  "resource": {
    "filename": "Reseaux.xml",
    "line": 374
  }
}
Elapsed time: 1 minute and 37 seconds.

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

Other resources