Matthias Günter

@duexw @klement-MENTZ

check if this still relevant.

@skinkie @Aurige It seems that with deckplan this would be a breeze to merge, if it is still valid. Pls advise.

> Question: is there a reason you want to use a NeTEx element, instead of reuse a SIRI element? @Aurige Do you want this methodically?

Nick: CheckConstraint in NeTEx. Enum in NeTEx. reconsiliation. needed with simple NeTEx. Christophe: Is at calls is natural. Occupany varies from day to day. It is different. Nick: Journey and...

not import SIRI.

* switched to part 2 * DayType added * occupancies now also as part of TimetableFrameGroup * occupancies added to JourneyGroup and JourneyPartGroup * made Occupancy a first class citizen...

> Can we have an example for "a call or a timetabled passing time"? Would it also be possible to have OccuptationInFrame which references a ServiceJourney. examples added in next...

have a look at https://3.basecamp.com/4847067/buckets/19640795/uploads/4409256610

I think @Ulf9 @Aurige @nick-knowles you will have to do the PR changes. The new TM conform NeTEx structure is way to complex as for SBB to ever consider implementing...