![]() ![]() Kaart-hosting voor uw websites en mobiele apps. Gratis gedetaileerde kaarten van de hele wereld voor uw applicaties. We think deck.gl has huge potential to become the foundation for spatial application development and having the right relationship with different basemap providers will be key.įinally we'd really like to hear from you! What options do you want available? Should we invest more on MVTLayer inside deck.gl and more abstraction of basemaps? We think this is a great opportunity for the community to fundamentally change our relationship with basemaps. Probeer MapTiler Cloud als een voordelig alternatief voor het MapBox Platform. And it's easy to switch between providers with just one line of code! There are already a lot of combinations available within the deck.gl ecosystem: deck.gl + Mapbox deck.gl + Google Maps deck.gl + CARTO basemaps etc. It is about giving freedom of choice and not locking users in. Our goal is to enable CARTO and deck.gl users to seamlessly use Mapbox basemaps Google Maps CARTO OpenStreetMap basemaps their own basemaps Azure Maps Maptiler HERE TomTom and any other technology they choose. Potential direction: to extend the MVTLayer class to support better cartography so that you can create a "basemap" layer from MVT sources. Check out this example.īut in the long term we are also actively consulting with different partners to see if we provide a full solution within the deck.gl ecosystem as part of the Urban Computing Foundation. In the short term we are going to support one of the key initiatives to maintain a fork for Mapbox GL JS v1.13 like other companies will be doing to ensure there is continuation of support for current CARTO basemaps used in deck.gl and existing applications. We are very excited to bring the great new capabilities of MapboxGL 2.0 for those users that want them and we are equally excited by the upcoming Google Maps Vector capabilities. So where next? More deck.glĬARTO will continue investing in basemap neutrality. Collaborating with many companies on deck.gl means a healthy Open Source community and a library that gets better and better for users without the risk of any licencing changes. The key difference is being able to build your map entirely on the basemap JS library or by using deck.gl having the option to change basemap provider painlessly.īy keeping the map sandwich separation it's easier to ensure the "health" of the stack.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |