Skip to content

Parse Segment geometry consistently for maps and navigation - #248

Merged
stef-k merged 2 commits into
mainfrom
fix/237-segment-geometry-parser
Aug 22, 2026
Merged

Parse Segment geometry consistently for maps and navigation#248
stef-k merged 2 commits into
mainfrom
fix/237-segment-geometry-parser

Conversation

@stef-k

@stef-k stef-k commented Aug 22, 2026

Copy link
Copy Markdown
Owner

Summary

  • add one validated Segment geometry parser for GeoJSON LineStrings and encoded polylines
  • use the shared coordinate sequence in map rendering and navigation graph construction
  • reject malformed, unsupported, out-of-range, and insufficient geometry deterministically
  • retain navigation edges without corrupt detailed geometry when parsing fails
  • preserve existing OSRM encoded-polyline handling

Closes #237

Validation

  • parser tests: 21 passed, 0 failed, 0 skipped
  • map/navigation tests: 27 passed, 0 failed, 0 skipped
  • decoder/OSRM boundary tests: 13 passed, 0 failed, 0 skipped
  • ordinary non-Android suite: 1,853 passed, 0 failed, 0 skipped
  • Release tests/Core build: succeeded
  • Android Release build: succeeded
  • git diff --check: passed
  • iOS and mounted-device validation not run

Data and migrations

No API, persistence, schema, migration, or synchronization changes.

@github-actions

Copy link
Copy Markdown

Code Coverage

Package Line Rate Branch Rate Complexity Health
WayfarerMobile.Core 85% 80% 720
Summary 85% (978 / 1149) 80% (486 / 606) 720

@stef-k
stef-k merged commit e501e21 into main Aug 22, 2026
1 check passed
@stef-k
stef-k deleted the fix/237-segment-geometry-parser branch August 22, 2026 17:21
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.

Parse Wayfarer GeoJSON consistently for segment map and navigation

1 participant