But for building functionality outside of the map I tend to use Leaflet instead due to the ease of use. You can treat the map more like a black box and the API is easier to use.
But for building functionality outside of the map I tend to use Leaflet instead due to the ease of use. You can treat the map more like a black box and the API is easier to use.
Classically you would do this with Tilemill for rasters which was amazing software, if crashy. And since we’re on a mapbox thread what I think put them on the map. I wish it was still actively developed and adapted for vectors.
https://github.com/go-spatial/fresco and https://github.com/maputnik/editor are TileMill-like editing programs, though specific to one tile format and renderer (MapboxGL)
https://github.com/Leaflet/Leaflet/issues/268
https://openlayers.org/en/latest/examples/rotation.html
This is a critical point for anyone selecting an API to build on top of with their own ambitious new web app idea.
Heck I'll just do the straight Google maps api often, it's really easy.
OpenLayer is like vim/emacs, some people think the hassle is worth it.
Nice quote: “Don't lose out on the potential of tomorrow by thinking too big today.”