Maintaining basemap independence means our users are not locked into a single provider and that can be quite important in situations when the provider adjusts pricing or their licensing arrangements.īut how can we achieve that independence? Let's start looking at how a map is usually made. It's just not feasible to force users to use a single basemap provider across all projects.īut there is a second reason. Sometimes there is an underlying business reason such as the user having an existing commitment with a given provider. Another project might choose Mapbox to make the most of their new 3D visualization capabilities.
For example a project might require the use of Google Maps because of the superb POI database it provides. Well first of all different geospatial projects have different needs. Basemap Neutralityīasemap neutrality means that you can use the CARTO platform and easily create apps with a variety of different basemap providers be that Mapbox Google Maps HERE TomTom MapTiler or our very own CARTO basemaps that are derived from OpenStreetMap. This change highlights a very important consideration that we at CARTO have been actively promoting for some time: basemap neutrality. Previously Open Source MapboxGL is a great solution and could be used with many different data sources so it became the de facto way to render basemaps. This library is responsible for the visualization of the so-called basemap the cartography layer that underpins most maps. Many organizations are using Mapbox GL JS directly or fork from it. This move has produced shockwaves in the geospatial industry. As of version 2.0 Mapbox GL JS cannot be used without accepting new Mapbox service terms.
#Carto series insight license
The library has gone from an Open Source BSD license to a proprietary one. This week Mapbox announced that they were changing the license of their MapboxGL JS library as part of their latest v2.0 release.
0 kommentar(er)
