You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many trains and public transport lines all around Europe are actually present in HAFAS.
I sadly figured out that even though the individual trains are present, there often is no correct line provided in the data.
In my case, I was trying to figure out how to represent the Réseau Express Métropolitain Européen (REME) Strasbourg : Each train number in HAFAS is given an individual line id (e.g. ter30700 - ter30743 for the fluo A09 line).
I'm wondering whether for such cases we could implement a range description to accumulate invalid line numbers into one unified line.
An example of this could be the famous page ranges we know from printing dialogs. I could imagine using the following pattern to describe such a range of lines into one unified line :
Whereas Strings in * represent a non-integer part of the line name and the descriptor in () indicates the numbers to match. This should a) not break existing implementations simply checking the String of the CSV column since the match should be false and b) is less overhead to implement than regular expressions.
Alternatively, well - one could simply add regular expressions to the line identifier column.
Example of invalid SNCF lines in the present CSV representation
Many trains and public transport lines all around Europe are actually present in HAFAS.
I sadly figured out that even though the individual trains are present, there often is no correct line provided in the data.
In my case, I was trying to figure out how to represent the Réseau Express Métropolitain Européen (REME) Strasbourg : Each train number in HAFAS is given an individual line id (e.g.
ter30700
-ter30743
for the fluo A09 line).I'm wondering whether for such cases we could implement a range description to accumulate invalid line numbers into one unified line.
An example of this could be the famous page ranges we know from printing dialogs. I could imagine using the following pattern to describe such a range of lines into one unified line :
*ter*(30700 - 30709; 30711; 30713 - 30718; 30720 - 30736; 30738 - 30741; 30743)
Whereas Strings in
*
represent a non-integer part of the line name and the descriptor in()
indicates the numbers to match. This should a) not break existing implementations simply checking the String of the CSV column since the match should be false and b) is less overhead to implement than regular expressions.Alternatively, well - one could simply add regular expressions to the line identifier column.
Example of invalid SNCF lines in the present CSV representation
With current duplication
With a printer-like range description
Using regular expressions
Preview :
This issue is related to #208 .
The text was updated successfully, but these errors were encountered: