New better timetable example from Slovenia#765
Conversation
|
fine for me, but maybe put if in NeTEx\examples\standards\slovenia rather than in NeTEx\examples\functions\timetable ? |
|
@atibaut my suggestion would be to change pos to posList. That would already save a considerable amount of data. I notice that ScheduledStopPointRef, ServiceLinkRef, OperatingDayRef, DayTypeRef all lack the version attribute, that this is not being picked up, is a bug in the XML Schema. |
|
This is not true the attribute is present but optional. because you may choose to have versionRef or version defepending on whether it is an internal or external ref. |
|
@atibaut pls update the PR |
91938c9 to
c5e1d48
Compare
|
It is never too late to improve a NeTEx timetable example. 😀 PR updated and rebased onto v2.0 (base retargeted from v1.3):
Validated against Note: the original |
b08e9a4 to
884cf8b
Compare
Updated per review: moved to examples/standards/slovenia, lowercase .xml extension so CI validation finds it, gml namespace declared once on the root element, pos points merged into gml:posList per LineString, and xsi:schemaLocation made relative.
884cf8b to
8b38dd2
Compare
|
@skinkie @TuThoThai the updated example is ready for your review. |
|
Hi @TuThoThai can someone look at this. 😀 |
|
@atibaut, I am moving the base branch to |
| <Name>Petrina - Kočevje (1003)</Name> | ||
| <TransportMode>bus</TransportMode> | ||
| <PublicCode>1003</PublicCode> | ||
| <PrivateCode>51314</PrivateCode> |
There was a problem hiding this comment.
@atibaut, please note that PrivateCode has been depcreated since v2.0 in favour of privateCodes in DataManagedGroup
| <Route id="SI:SI0:Route:00000000-1177-0008-0000-00000004b3b4:IJPP" created="2023-10-06T04:51:58.9174842Z" version="1"> | ||
| <Name>Kočevje 1 7003</Name> | ||
| <LineRef ref="SI:SI0:Line:00000000-1177-0007-0000-00000000c872:IJPP"/> | ||
| <pointsInSequence> |
There was a problem hiding this comment.
@atibaut, in all the pointsInSequence, could you please remove order as it was deprecated in favour of XML ordering?
| <OperatorRef ref="SI:SI0:Operator:00000000-1177-0001-0000-00000000045f:IJPP"/> | ||
| <passingTimes> | ||
| <TimetabledPassingTime id="SI:SI0:TimetabledPassingTime:00000000-1177-0009-0000-000000725b33:IJPP" created="2023-10-06T04:51:58.9174842Z" version="1"> | ||
| <StopPointInJourneyPatternRef version="1" ref="SI:SI0:StopPointInJourneyPattern:00000000-1177-0009-0000-000000725b33:IJPP"/> |
There was a problem hiding this comment.
@atibaut, for all the StopPointInJourneyPatternRef, could we have version at the end to be consistent in the file?
| </Line> | ||
| </lines> | ||
| <scheduledStopPoints> | ||
| <ScheduledStopPoint id="SI:SI0:ScheduledStopPoint:00000000-1177-0003-0000-00000011236e:IJPP" created="2023-10-06T04:51:58.9174842Z" version="1"> |
There was a problem hiding this comment.
@atibaut, I believe that in this file all your ScheduledStopPoint are associated with a Quay via PassengerStopAssignment. So, name could be removed as redundant
This example of a timetable replaces the file Netex_09.2_Bus_SimpleTimetable_Slovenia.xml. The timetable was created from a national NeTEx service in Slovenia (Ministry of Transport/NCUP).