Home » railML newsgroups » railml.timetable » Proposal Statistics
Re: Proposal Statistics [message #635 is a reply to message #634] Fri, 04 February 2005 11:01 Go to previous message
markus.ullius is currently offline  markus.ullius
Messages: 8
Registered: November 2004
Junior Member
Hello Joachim

> The attribute 'type' as in TRAIN can be added for STATISTIC as well, but
> I'm thinking of a more detailed new element 'stopType' for the TRAIN
> describing the different kinds of conditional and operational stops.
> Should such a new element be used for STATISTIC in the same way?

Maybe this may make sense - also to be 'compatible' with the
non-statsitical parts.

> The 'statisticType ' seems to be reasonable as well, what values besides
> "mean" and "median" could be used there?

There could also be some kind of %-mean, %-median, indicating the mean and
median for the best x % of the trains -> value-field for the %-value would
also be required

> And what about your attributes needed for standard deviation?

The standard deviation would require some kind of float-value giving the
stdDev - whereas the mean and median could either be "timestamps" or
"delayvalues" indicating the delay from the "scheduled-timestamp"

Best regards
Markus Ullius
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: OpenTrack supports version 1.0 of the timetable schema
Next Topic: Proposal: move the train attribute <kind>
Goto Forum:
  


Current Time: Wed May 15 17:42:20 CEST 2024