Home » railML newsgroups » railml.timetable » stop probability
Re: stop probability [message #956 is a reply to message #737] Mon, 02 December 2013 12:00 Go to previous message
Joachim Rubröder railML is currently offline  Joachim Rubröder railML
Messages: 0
Registered: November 2019
Hi,
we created a ticket in order to plan this enhancement for a future railML
version: https://trac.assembla.com/railML/ticket/234

Kind regards,
Joachim

-------------------------------------
Joachim Rubröder
Schema Coordinator: railML.timetable

Susanne Wunsch wrote:
>
>
> Hi Joachim,
>
> coord(at)timetablerailmlorg (Joachim Rubröder) writes:
>
>> I would suggest to use an "anyAttribute" within the <stopDescription>.
>> This is the right place, because "stopOnRequest" is already there.
>>
>> If there is anyone else with the same request, we could prepare a new
>> field for a future version.
>
> Thanks for the quick response.
>
> It would be nice to define the anyAttribute in <stopDescription>. That's
> the best place for the needed attribute, I think.
>
> There are further attributes which could be defined in
> <stopDescription>:
>
> * (serviceSectionRef) if platforms, ramps or other facilities are
> defined as "serviceSection"s in IS [1]
>
> * (stopPosition) if serviceSectionRef is used and the train is shorter
> than the service section length
>
> Kind regards...
> Susanne
>
> [1] http://trac2.assembla.com/railML/ticket/122
>
>



--
----== posted via PHP Headliner ==----
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
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: Blockparts: emptyRuns, depotRuns
Next Topic: RFE for connection, DE:Anschluss
Goto Forum:
  


Current Time: Sun May 05 23:18:39 CEST 2024