Home » railML newsgroups » railml.timetable » RailML semantics, nextdeparture, recurringschedule
Re: RailML semantics, nextdeparture, recurringschedule [message #724 is a reply to message #723] Tue, 10 May 2011 10:28 Go to previous messageGo to previous message
Joachim Rubröder railML is currently offline  Joachim Rubröder railML
Messages: 0
Registered: November 2019
Dear Tuomas,

I'm not sure if I understand right, what you mean by your "Departure".
Could you please describe this a little bit more in detail?

Here is some rough explanation about the railML basics you mentioned for
clarification:

> timetable->trains->train
If your dealing with passenger information, your "train" will probably be
with type="commercial" and correspond to the train, a passenger is used
to. A train with type="operational" in comparance is a train considered by
a signal box, which is mostly but not necessary the same kind of train.

> circulations/rostering/blocks
The blocks are describing the routine of the day for a specific piece of
rollingstock. This could be within diffferent trains and could include
empty rides before starting the routine for the following day which is
described in the next block.

> operatingperiod->bitmask
This is a bitmask for every day of a timetable period, decribing if the
train is running on this specific day.

> operatingperiod->operatingday->operatingcode->bitmask
This is a different more generic way of describing, like "running Mondays
to Fridays only" with a week based bitmask. This is valid for any week
with some further described deviances.

> ocpTT->sectionTT->distance
Is the running distance between one ocpTT within the path of a train and
the next ocpTT for this train. This information is redundand and could be
calculated by
> track->tracktopology->trackBegin/trackEnd->pos
wich is the correct length of a single track between two switches in a
microscopic view.

But if you consider track/Begin/trackEnd as macrosscopic nodes
corresponding to stations, then you will get the same result:
> ocpTT->sectionTT->distance (running distance for the train between stations)
> track->tracktopology->trackBegin/trackEnd->pos (macroscopic infrastructure
distance between stations)

I hope this will clear up intentions behind the complex structures of
railML a little bit.

Kind regards
Joachim

Tuomas Tiihonen wrote:
>
> Greetings to RailML community!
>
> This is my first post to the forum so I will start with a introduction. I
> am a Software Design Engineer with strong Java/C++ programming/design
> background. I am currently working for Finnish company called Mitron Oy.
> We have headquarters in Forssa/Finland and other offices in
> Tampere/Finland, Mittenaar/Germany and Warszawa/Poland. Mitron focuses on
> passenger information, display, entertainment, announcement and security
> systems for trains, trams, subways, stops, stations and platforms. More
> information about company can be found from www.mitron.com and I am happy
> to answer further queries about me or the company.
>
> Within Mitron we have ongoing discussion about RailML and I have now been
> studying it from technical perspective. Goal of this study is to make
> decision about our commitment to RailML and what our role would be.
>
> During this technical investigation I have had some difficulties related
> to the semantic specification explained (or more accurately not explained)
> in the RailML wiki pages.
>
> I have so many questions about the semantics, but I have to start from
> somewhere so here it goes:
>
> We have thing called "Departure" which I think is close to
> timetable->trains->train in RailML. Our departure knows route and
> timetable for the route for example. Departure knows also list of possible
> next Departures that might come next from the terminal station of first
> departure. What would be the place in RailML to get that information? Is
> the circulations/rostering/blocks semantically identical to this? Does the
> block mean part of train or part of track as an example? I have tried to
> figure out the semantical relations of those mentioned RailML elements,
> but without documentation in wiki it has proved difficult.
>
> Other thing I don't quite get, even though it is mentioned in wiki is
> relation between operatingpediod->operatingday->operatingcode->bitmask and
> operatingperiod->bitmask and operatingdaydeviance and holiday and
> specialservice. Which one overrides which? Why there are period bitmask
> separately from week bitmask and then deviances and holidays?
>
> What is ocpTT->sectionTT->distance. Distance from where to where? Is this
> in relation to infrasructures
> track->tracktopology->trackBegin/trackEnd->pos -attribute? If I would like
> to know distance of two stations along the track/line what is the correct
> place?
>
> With Kindest Regards,
> Mr. Tuomas Tiihonen
>



--
----== posted via PHP Headliner ==----

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: These: Das Aufteilen eines großen RailML-Netzes auf mehrere kleinere RailML-Netze darf zu keinem Verlust an Informationen führen.
Next Topic: timetable.trainParts.trainPart.ocpsTT.ocpTT.times scope value
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri May 17 04:55:25 CEST 2024