Skip to content

feat(sumo): write list of upcoming edges into additionalData field#536

Draft
kschrab wants to merge 1 commit into
mainfrom
1115-sumo-upcoming-edges
Draft

feat(sumo): write list of upcoming edges into additionalData field#536
kschrab wants to merge 1 commit into
mainfrom
1115-sumo-upcoming-edges

Conversation

@kschrab
Copy link
Copy Markdown
Contributor

@kschrab kschrab commented Oct 8, 2025

Description

Collect a list of upcoming edges within a given range for each updated vehicle. The list is added to the additionalData field within the VehicleData object. Configure through new field upcomingEdgesRange in sumo_config.json.

ℹ️ Just for experimental use and try-out

Issue(s) related to this PR

  • Helps to resolve internal issue 1115

Affected parts of the online documentation

Changes in the documentation required?

No

Definition of Done

Prerequisites

  • You have read CONTRIBUTING.md carefully.
  • You have signed the Contributor License Agreement.
  • Your GitHub user id is linked with your Eclipse Account.

Required

  • The title of this merge request follows the scheme type(scope): description (in the style of Conventional Commits)
  • You have assigned a suitable label to this pull request (e.g., enhancement, or bugfix)
  • origin/main has been merged into your Fork.
  • Coding guidelines have been followed (see CONTRIBUTING.md).
  • All checks on GitHub pass.
  • All tests on Jenkins pass.

Requested (can be enforced by maintainers)

  • New functionality is covered by unit tests or integration tests. Code coverage must not decrease.
  • If a bug has been fixed, a new unit test has been written (beforehand) to prove misbehavior
  • There is no API break in mosaic-geomath.
  • There are no new SpotBugs warnings.

Special notes to reviewer

@kschrab kschrab force-pushed the 1115-sumo-upcoming-edges branch from b538074 to 9fb25c1 Compare October 9, 2025 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant