You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
Hello,
I try to use the new MGLTileSourceOptionCoordinateBounds option. But tiles start to get missing if I zoom far in and pan. If I don't use this option than every tile gets displayed correctly.
Platform:
iOS
Mapbox SDK version:
3.7.4
Steps to trigger behavior
use MGLTileSourceOptionCoordinateBounds option
let mglBoundsValue = NSValue(mglCoordinateBounds: mglBounds) let source = MGLRasterSource(identifier: mapTag, tileURLTemplates: [urlTemplate], options: [.tileSize: 256, .tileCoordinateSystem: MGLTileCoordinateSystem.TMS.rawValue, .coordinateBounds: mglBoundsValue])
2. Zoom in until you see the underlying MapBox map
3. Pan in any direction, e.g. to the left
Expected behavior
Tiles should be loaded and displayed for the newly visible map region.
Actual behavior
Only the underlying MapBox map is shown. The tiles are missing.
The text was updated successfully, but these errors were encountered:
Hello,
I try to use the new MGLTileSourceOptionCoordinateBounds option. But tiles start to get missing if I zoom far in and pan. If I don't use this option than every tile gets displayed correctly.
Platform:
iOS
Mapbox SDK version:
3.7.4
Steps to trigger behavior
let mglBoundsValue = NSValue(mglCoordinateBounds: mglBounds) let source = MGLRasterSource(identifier: mapTag, tileURLTemplates: [urlTemplate], options: [.tileSize: 256, .tileCoordinateSystem: MGLTileCoordinateSystem.TMS.rawValue, .coordinateBounds: mglBoundsValue])
2. Zoom in until you see the underlying MapBox map
3. Pan in any direction, e.g. to the left
Expected behavior
Tiles should be loaded and displayed for the newly visible map region.
Actual behavior
Only the underlying MapBox map is shown. The tiles are missing.
The text was updated successfully, but these errors were encountered: