When map.fitBounds(...) is called with a bearing option passed in, it seems like the bearing is not taken into the account on calculating the appropriate zoom, resulting in part of the bounded area to not be in view.

mapbox-gl-js version: 1.12.0

browser: Chrome

Steps to Trigger Behavior

1. Create a bounded area with a list of coordinates
2. Call map.fitBounds(...) wi

MGLTilePyramidOfflineRegion should have a countOfTiles method that returns the number of tiles included in the tile pyramid. The implementation would rely on the mbgl::util::tileCount() function added in #9906.

This is the iOS/macOS equivalent to #11108 for Android. It would serve as a built-in alternative to mapbox/turf-swift#47 for applications already using the map SDK, including applica

When I edit a polygon with a zoom level low and I snap this polygon to another one, it's very common the created snap point is not exactly on the line / point.
For me, it's a problem regarding I control if these polygons are not intersecting.

There is some text on the page, but it is hard coding in your index.js.
The better way is to make it customizable by parsing markdown or reading from the config file.

But, I think Gatsby is not as convenient as next.js in terms of reading data.... so do you consider changing the page framework? 😳

This word does not appear in the translation into Transifex:

• Nextcloud additional settings

https://github.com/nextcloud/maps/blob/10aa2edd4882f27dfcbeb7a4d3d387a725a766e0/js/script.js#L986

App:
Maps 0.1.4