Closed leonardehrenfried closed 3 weeks ago
Here is the complete list of journey and pattern IDs: https://gist.github.com/leonardehrenfried/72657148aaccd837ffa0243b7344814a
@leonardehrenfried I understood this issue. You can see that the second point in the ServiceJourneyPattern
has StopUse
= passthrough. This means that in this case the vehicle (in this case a train) does not stop at the stop, just travels by. The reason why we have this is mainly related to passenger information purposes, this data are also used for some basic travel information products and they want also to visualize such stops even if not served.
Travel times in correspondence of these passthrough points are not set, and therefore you this point is not reported in the structure ServiceJourney
. Can you configure the import so that you simply ignore from the export the passthrough points? I am pretty sure that 920 cases you found have exactly this issue. Most of the rail services in South Tyrol contained such thing.
Upstream issue: https://github.com/opentripplanner/OpenTripPlanner/issues/6036
The NeTEx export available from https://cloud.opendatahub.com/index.php/s/dHXsK9KsFWdKXPC contains 920 instances of the following error, which prevents some service journeys from being imported into OpenTripPlanner.
The
ServiceJourney
and theServiceJourneyPattern
have a different number of passing times/points in sequence.Example
The service journey
it:apb:ServiceJourney:031001T-TI-63-5-43500:sonn:
has nine entries inpassingTimes
.This service journey references the
ServiceJourneyPattern
it:apb:ServiceJourneyPattern:03100T.24a5100166:
at version 5. However, this pattern has ten (not nine) points in sequence:This seems like a data error, since the
StopPointInJourneyPattern
it:apb:StopPointInJourneyPattern:03100T.24a-5-10016602:
is never referenced? What is supposed to happen with the missing stop?cc @rcavaliere