Opened 4 years ago

Last modified 2 years ago

#24 assigned enhancement

More robust mileages in graphic timetable (de: Robustere Kilometrierung im Bildfahrplan)

Reported by: susanne.wunsch Owned by: birgit.jaekel
Priority: normal Component: Graphic TT Viewer
Version: 1.2.x Keywords:
Cc:

Description (last modified by vasco.kolmorgen)

There are further methods, to derive the mileage of stop points for the graphic timetable. The basic function is requested in #23.

  1. Search for an track/ocsElements/stopPost or track/trackTopology/crossSection where track/@id equals first trainPart/ocpTT/sectionTT/trackRef/@ref and */@ocpRef equals trainPart/ocpTT/@ocpRef, take */@absPos
  2. If no track/ocsElements/stopPost or track/trackTopology/crossSection matches the above condition, take the average value of track/trackTopology/trackBegin/@absPos and track/trackTopology/trackEnd/@absPos
  3. If no trainPart/ocpTT/sectionTT/trackRef/@ref is given, go to operationControlPoints/ocp where */@id equals trainPart/ocpTT/@ocpRef, take the average value of all track/trackTopology/trackBegin/@absPos and track/trackTopology/trackEnd/@absPos that equal ocp/propEquipment/trackRef/@ref
  4. If no infrastructure/tracks/track are defined at all, summarized trainPart/ocpTT/sectionTT/@distance may be taken.

Change History (6)

comment:1 Changed 4 years ago by susanne.wunsch

  • Description modified (diff)

comment:2 Changed 4 years ago by susanne.wunsch

Searching for stopPost, platformEdge and crossSection is already done. The @distance evaluation will be done for older railML versions.

Further enhancement would be to calculate ocp position, if no crossSection, stopPost or platformEdge is given at the referring track from timetable.

Maybe that is too much interpretation of the data and should not be done.

comment:3 Changed 4 years ago by susanne.wunsch

See also #180 for a minimal sample file without tracks, without distances.

comment:4 Changed 3 years ago by vasco.kolmorgen

  • Owner set to birgit.jaekel
  • Priority changed from normal to minor
  • Status changed from new to assigned

comment:5 Changed 2 years ago by vasco.kolmorgen

  • Description modified (diff)
  • Priority changed from minor to normal
  • Version changed from 1.1 to 1.2

After consultation with an external TT import expert a following split up is proposed:

  • № 1 & 2 for V1.2 (March 2017)
  • № 3 for V1.x (Later in 2017ff)
  • № 4 for V2 (postponed up to concrete request or circulating file)

comment:6 Changed 2 years ago by vasco.kolmorgen

  • Version changed from 1.2 to 1.2.x

Postponed to V1.2.x due to high workload

Note: See TracTickets for help on using tickets.