Home » railML newsgroups » railml.timetable » ocpType begin/end/stop
Re: ocpType begin/end/stop [message #743 is a reply to message #742] Wed, 24 August 2011 14:12 Go to previous messageGo to previous message
Joachim Rubröder railML is currently offline  Joachim Rubröder railML
Messages: 0
Registered: November 2019
Hello Andreas,
many thanks for your posting.

This is a good argument to get rid of the "begin/end" in the ocpType. I
would vote for separate new attributes, indicating that a commercial or
operational train either begins/ends or is crossing the border to
somewhere outside e.g. an other country.

The ocpType has currently a mixture of two different meanings:
- stop/pass to indicate whether the train stops at this entry or passes
this point
- begin/end at the first/last entry to indicate if the train is really
starting/ending or just crossing the border of the examined area.

What less confusing attributes would you suggest?

Kind regards,
Joachim

--
----== posted via PHP Headliner ==----
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: offene Diskusionspunkte (Fahrzeugidentität über Zugabschnitte, abweichende Laufwege, ocps)
Next Topic: Mapping of code and abbreviation for ocps
Goto Forum:
  


Current Time: Mon May 13 10:33:49 CEST 2024