3 ms·
Having used this, its not without its issues. * Adds a performance penalty over straight Mapbox-GL. * No support for animations / flyovers / etc. * You h
by davidjhamp 9y ago
Having used this, its not without its issues.
* Adds a performance penalty over straight Mapbox-GL.
* No support for animations / flyovers / etc.
* You have to give width/height in pixels for map size.
* Can't introspect map to get layer / point data w/o hacks.
The recent ver 3.0 was a big improvement.
- codor 9y agoThese issues were big enough that I just recently removed this library on a new project in favor of straightforward Mapbox GL JS. The inability to use percentages for height/width is a major drawback. No sense in adding size to the bundle for fewer options.
- davidjhamp 9y agoSeconded, in our case we haven't yet but its on the roadmap.
- pendragon 9y agoIt does not make it easy to access the mapbox library API directly. It claims there is a way, but it's not documented.
- davidjhamp 9y agoYou can get the mapbox-gl map instance by using a ref and then grabbing the mapbox-gl map off of that (but not documented or officially supported).