Skip to content

[Feature] Display POIs as markers on the Replay timeline #519

Description

@chdenat

Context

The Replay preparation timeline will support timeline markers. Journey POIs
currently exist in the Replay domain and can be identified along the journey,
but they are not represented on the timeline.

This issue is blocked by lgs1920/timeline#5,
which provides the generic timeline marker rendering, controlled updates,
marker events, tooltips, and snapping support required by the Studio adapter.

Requested behavior

Display the POIs associated with the current journey as markers on the Replay
timeline once the timeline marker capability is available.

Each marker should be positioned according to the POI's projected position in
the Replay timeline and should expose the POI name or label. The marker display
must remain synchronized when the journey, POI list, Replay duration, or
timeline range changes.

Acceptance criteria

  • Current journey POIs with a valid projected journey position are displayed as timeline markers.
  • Each marker is positioned at the corresponding Replay time.
  • Each marker exposes the POI label through its visual label or accessible name.
  • POIs without a valid projected position are omitted without breaking the timeline.
  • Marker positions update when the Replay duration or journey data changes.
  • Markers remain read-only and do not create a second Replay clock.
  • Clicking a marker identifies the corresponding POI and provides an entry point for the existing POI editor or focus behavior.
  • Marker rendering remains available when the timeline is hosted in the Replay widget, drawer, or detached window.
  • Unit and UI tests cover marker projection, updates, missing positions, and marker interaction.

Notes or questions

The proposed scope covers POIs belonging to the current journey. Global POIs are
excluded unless they are part of the journey's Replay POI set.

Technical notes

The marker time should be derived from the canonical Replay timeline and the
POI's projected journey position. The implementation must remain compatible
with the future persisted multi-track timeline model and must not add a second
timeline or Replay time authority.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions