Open ristiisa opened 8 months ago
@pjleonard37 @persidskiy @aleksproger @OdNairy @evil159 @maios
Any thoughts on this issue?
Hi @ristiisa, just an observation here. What happens if you add values to the padding?
let camera = (try? mapView.mapboxMap.camera(
for: coordinates,
camera: CameraOptions(),
coordinatesPadding: .init(allEdges: 0), // <-- ADD 20 OR MORE TO THIS.
maxZoom: nil,
offset: nil))!
Hi @ristiisa, just an observation here. What happens if you add values to the padding?
let camera = (try? mapView.mapboxMap.camera( for: coordinates, camera: CameraOptions(), coordinatesPadding: .init(allEdges: 0), // <-- ADD 20 OR MORE TO THIS. maxZoom: nil, offset: nil))!
still failure
@ristiisa you can try to workaround it by using mercator projection like here https://github.com/mapbox/mapbox-maps-ios/issues/2113#issuecomment-1935887812
@ristiisa you can try to workaround it by using mercator projection like here #2113 (comment)
I confirm, the fit to bounds does work with mercator projection. For us not a possible workaround though.
in 11.3-rc1 the issue is mostly resolved where the area is now fully visible but not centered.
Environment
Observed behavior and steps to reproduce
Fitting the map to a bounds does not work properly if the angle of the diagonal is steep and the width of the device is small enough.
Expected behavior
Notes / preliminary analysis
The issue seems to be related to the aspect ratio of the screen and the angle of the corner coordinates. As it is possible to find coordinates that work well.
Additional links and references