| Re: Minimal content of a timetable file [message #1293 is a reply to message #1284] |
Mon, 17 August 2015 15:46  |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Dear Susanne, dear Daniel and all others,
> How about other tools? What are they doing with this minimal file?
I want to answer your questions for iRFP/FBS and my remembrance of
earlier discussions mentioned by Daniel.
>> It should be possible to define a timetable file which contains no
infrastructure data (with the exception of the list of
operationalControlPoints), that means completely without trackIDs,
lineIDs, trackRef, sectionTT etc.
I totally agree with Daniel, I also think that this is an important
point for us "<timetable>rs".
> It should be possible to import a timetable of this kind into every of our tools and to display the information in a tabular format and preferable also as (simplified) train graph.
I also agree.
> Since the beginning such a “minimal” example was (see the corresponding railML data below): Zurich Main Station, Departure: 08.01, Zurich Airport, Arrival: 08.13
No objection. But as Susanne wrote: The example seems to contain "pass"
but not "departure" at the first <ocp>.
Despite a train of course cannot start "passing", I think we cannot
exclude this "initial running through" from railML files. For some
reasons, railML files may contain only an excerpt from a greater
network. This can either mean that the software where the railML comes
from has no information on all stations of a train's route or that it
(its user) does not want to export (=publish) this information.
An example may be a border of two Infrastructure Managers (IM). Such
borders often lay on the open line between two stations, possibly at
international borders. For the sake of "exact demarcation" (often de
jure), an offer of one IM is only allowed to contain the route for the
infrastructure of this IM. So, the railML file containing such an offer
may start with "pass" at the fist (or last) <ocp>.
To answer Susannes question quoted at the start of my message:
We would handle such files, meaning we can import (or adjust) a train
starting with "pass" and we can also export such files in special
circumstances.
> These times are not shown in the tabular timetable of railVIVID...
As I stated earlier, it would be good (not only for this purpose) if
railVIVID could display passing times (optionally, may be with a
CheckBox "Show run-through times").
Best regards,
Dirk.
|
|
|
|
Members
Search
Help
Login
Home
