maps

Map:

• setZoom
• setZoomAround
• fitWorld
• panTo
• panBy
• flyToBounds
• setMinZoom
• setMaxZoom
• panInsideBounds
• stop
• locate
• stopLocate
• addHandler
• createPane
• getPane
• getPanes
• getContainer
• getSize
• getPixelBounds
• [ ]

The current implementation of the maps API lacks support for the snapshot() functionality.

https://github.com/microg/GmsCore/blob/master/play-services-maps-core-mapbox/src/main/kotlin/org/microg/gms/maps/mapbox/GoogleMap.kt#L483

This is a requirement for location sharing in Signal messenger.

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

maptalks's version and what browser you use?
v0.43.0, chrome

Issue description
Layers do not share WebGL context, which creates glitches when a map has more than one 3d layer. For example a buildings layer with a 3D line will not hide the line behind the buildings.
In particular, I am implementing a 3D terrain layer but this layer will not hide (behind mountains) any other 3d element

One can add stops, but it is currently impossible to change the order of the stops.

Also, it would be nice to have an overview of all the stops and adresses. There only is map view for multi stop routes right now.

How did you install WebODM (docker, installer, etc.)?

Seriously dockerized here.

What's your browser and operating system? (Copy/paste the output of https://www.whatismybrowser.com/)

Not relevant.

What is the problem?

Autovacuum is either not set or untuned in WebODM

How can we reproduce this? (What steps trigger the probl

'react-autocomplete' (https://github.com/reactjs/react-autocomplete) is no longer maintained and causing warnings

react-dom.development.js:12357 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

• Move code with side effects to componentDidMount, and set initial state in the constructor.
• R

Context: this from @agila5: https://twitter.com/a_gilardi5/status/1487813588454678528

I have not had a chance to read the explanation and am not sure what we should say on the topic but guess it's worth a mention here. Any thoughts?