ITxPT/DATA4PTTools

journey-pattern-timings: taylor made for nordic profile passingTimes

Closed this issue · 1 comments

The Nordic profile uses passingTimes. An error like: "Expected passing times for StopPointInJourneyPattern(@id='TECBrabantWallon:StopPointInJourneyPattern:32775967-L_PA_2022-22_LG_ME-Mercredi-01-0010000-1" shows that other forms, such as calls, are not considered. I do like this uncovers that there is no 1:1 relationship between the call and inferred ServiceJourneyPattern.

<StopPointInJourneyPattern dataSourceRef="TECBrabantWallon:DataSource" derivedFromObjectRef="TECBrabantWallon:Call:32775967-L_PA_2022-22_LG_ME-Mercredi-01-0010000-1" id="TECBrabantWallon:StopPointInJourneyPattern:32775967-L_PA_2022-22_LG_ME-Mercredi-01-0010000-1" order="1" version="20220111">
  <ScheduledStopPointRef ref="TECBrabantWallon:ScheduledStopPoint:LBkcare*" version="20220111"/>
  <OnwardTimingLinkRef ref="TECBrabantWallon:TimingLink:-551368533" version="20220111"/>
  <ForAlighting>false</ForAlighting>
</StopPointInJourneyPattern>
<Call dataSourceRef="TECBrabantWallon:DataSource" id="TECBrabantWallon:Call:32775967-L_PA_2022-22_LG_ME-Mercredi-02-0010000-1" order="1" version="20220111">
  <ScheduledStopPointRef ref="TECBrabantWallon:ScheduledStopPoint:LBkcare*" version="20220111"/>
  <OnwardTimingLinkView>
    <TimingLinkRef ref="TECBrabantWallon:TimingLink:-551368533"/>
    <RunTime>PT0S</RunTime>
  </OnwardTimingLinkView>
  <Arrival>
    <Time>12:23:00</Time>
  </Arrival>
  <Departure>
    <Time>12:23:00</Time>
    <WaitTime>PT0S</WaitTime>
  </Departure>
</Call>

This rule has been removed in #15