Home » railML newsgroups » railml.timetable » Fahrgastzahlen in railML
Re: Fahrgastzahlen in railML [message #934 is a reply to message #922] Tue, 12 March 2013 18:39 Go to previous messageGo to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 311
Registered: August 2008
Senior Member
Dear all

and @dear Christoph: Which kind of "Fahrgastzahlen" do you mean? Actually
counted numbers of passengers of the past? Or expected numbers of
passengers in the meaning of "minimum seating places to be available"?

I also think (like Joachim) that "Fahrgastzahlen" of the first type
(actually counted) are a matter of the greater topic "actual data" (in
contrary to "pre-planned timetable data"). It is strongly connected with
the question "At which day these passenger numbers have been counted",
which leads us back to the already discussed topic "actual operating
days". We agreed to handle this outside the scope of the current
<timetable> scheme.

Concerning numbers of passengers in the second meaning (expected), they
are clearly a matter of <timetable> in the pre-planned meaning so I could
imagine some elements and attributes for them in the current scheme. But I
would name them "minimum necessary places" or so - not "passenger numbers"
to clarify the difference.

It would fit to the typical "Musterfahrplan" (pattern timetable) of
advertisements / competitions where normally all trains have minimum
places to be provided by the competitor. Often they are distinguished by
operating days (Mon-Fri, Sat, Sun). So either we allow a kind of
operatingPeriodRef with this information or we expect to place different
trains/trainParts for each operatingPeriodRef. The latter would be ok from
my side.

Best regards,
Dirk.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: problems with <train>s: uniqueness constraints, scope
Next Topic: train uniqueness constraint II
Goto Forum:
  


Current Time: Thu May 16 13:34:10 CEST 2024