Hello Dillip,
various combinations are possible:
- (begin, end, number) is permitted - the period is then computed as
(end-begin)/number
- (begin, end, period) is permitted
- (begin, period, number) is permitted
- (begin, end, period, number) is not permitted because the values might
contradict
Hello Jakob,
I understand your concern regarding the change or addition of new classes.
It is absolutely fine till things are working, especially with backward
compatibility. A splendid work has been done by you and your team, no
doubts. We are lucky to have your advice, time to time, majority of
Hello Harald,
Thanks for your suggestions
a) I agree that using the same attribute name for two related but subtly
different things is adding unnecessary confusion (I fact, confusion was
recently observed).
Since the 'period' attribute of flows has a lot of history behind it I'll
keep this
Hello Herald,
Thanks for coming up with a proposal.
In my opinion, the word route is ambiguous since it is used for defining a
path as well as a public transit line (or route). Hence, a new class named
line or ptLine should be formed. This class will contain all the properties
of a public transit
Hello
here are some proposals for enhancing the repeated route stuff:
a) change of attribute names
In route I would rename period to cycletime (German: Umlaufzeit)
In flow I would rename period to headway (German: Taktzeit)
b) Can we add the repeat features to trips, if we want to
