Skip to content

Report camera fov and apply paddings - #21

Merged
wf9a5m75 merged 4 commits into
developfrom
feat/camera-paddings
Nov 12, 2026
Merged

wf9a5m75 merged 4 commits into
developfrom
feat/camera-paddings

Conversation

@wf9a5m75

Copy link
Copy Markdown
Contributor

Summary

This provider now

  • reports MapCameraPosition.fov for its engine, and
  • honours MapCameraPosition.paddings on move / animate: the target lands at the centre of the padded area, and the camera read back reports the target with the same paddings.

Depends on the core feat/camera-paddings PR (and, where noted, the provider's tilt fix PR).

fov 30.0 (measured; pitch capped at 35); paddings emulated and corrected with the map's projection. Known: read-back can stay ~25 m off after a padded move.

Commits

  • Apply camera paddings and report fov on MapKit
  • Measure the padded target with MapKit's projection
  • Apply MapKit padding corrections on separate run loop turns
  • Merge remote-tracking branch 'origin/develop' into feat/camera-paddings

MKMapCamera has no padding, so the camera center is shifted with the
core CameraPaddingEmulation (using MapKit's measured vertical fov, 30°)
and shifted back on read; the read camera carries paddings and fov.
MapKit's scale differs slightly from the model and its pitch limit
depends on altitude, so after each move (and at the end of an
animation) the camera center is corrected with the map's projection,
and the target is read back from the padded center.
Back-to-back setCamera calls let MapKit fold the region-change
notifications, so the state kept the camera from before the correction.
@wf9a5m75
wf9a5m75 merged commit 0bb772c into develop Nov 12, 2026
2 checks passed
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