Forum: railml.timetable » Proposal Statistics

Home » railML newsgroups » railml.timetable » Proposal Statistics

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Proposal Statistics [message #637 is a reply to message #636]

Fri, 25 February 2005 10:10

markus.ullius
Messages: 8
Registered: November 2004

Junior Member

I think it's a good idea to have a field describing the content of
statistical data as you have mentioned. Either a manual entry or as
default text the settings of eg. OpenTimeTable (dateperiod, dayselection,
timeslot, ...) could be written in this field.

Best regards
Markus

> For example, if you have the mean departure time of March and the mean
> departure time of calendar week 11 in the same file, an application that
> is reading the file must be able to make a distinction. Whether this is
> based on an somewhat arbitrary identifier ("DatasetMarkus418b" or
> "MonthlyStatisticsMarch2005") or an explicit listing of all parameters
> describing the dataset and its origin is - in my opinion - of minor
> concern.

Report message to a moderator

[Message index]

		Proposal Statistics By: markus.ullius on Mon, 15 November 2004 20:26
		Re: Proposal Statistics By: Daniel Huerlimann on Tue, 07 December 2004 08:25
		Re: Proposal Statistics By: markus.ullius on Mon, 20 December 2004 16:47
		Re: Proposal Statistics By: andreas.voss on Tue, 15 February 2005 15:00
		Re: Proposal Statistics By: markus.ullius on Fri, 25 February 2005 10:10
		Re: Proposal Statistics By: Joachim.Rubröder on Thu, 27 January 2005 13:35
		Re: Proposal Statistics By: markus.ullius on Fri, 04 February 2005 11:01

Previous Topic:	OpenTrack supports version 1.0 of the timetable schema
Next Topic:	Proposal: move the train attribute <kind>

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Thu May 16 05:04:13 CEST 2024