From 604e76212b6ba33e014c531484a9d3537df60f9a Mon Sep 17 00:00:00 2001 From: Lukas Martinelli Date: Wed, 21 Sep 2016 21:38:38 +0200 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d1f887e6..c9a5d697 100644 --- a/README.md +++ b/README.md @@ -16,7 +16,7 @@ As of today Mapbox GL styles are usually designed within the cloud based [Mapbox which is a great example how a style editor should look like. The big problem is that Mapbox Studio is not open source and you have to upload your data sources to external servers and -essentially are locked in the Mapbox ecosystem. By reusing existing proprietary base styles you legally tie your style for use with Mapbox services. It is difficult to use other data source like [OSM2VectorTiles](osm2vectortiles.org), [Mapzen](https://mapzen.com/projects/vector-tiles/) or [Kartotherian](https://github.com/kartotherian/kartotherian) or even your own custom vector tile sources. +essentially are locked in the Mapbox ecosystem. By reusing existing proprietary base styles you legally tie your style for use with Mapbox services. It is difficult to use other data source like [OSM2VectorTiles](http://osm2vectortiles.org), [Mapzen](https://mapzen.com/projects/vector-tiles/) or [Kartotherian](https://github.com/kartotherian/kartotherian) or even your own custom vector tile sources. This is why I think we should rally behind and build our own style editor for the Mapbox GL style specification! [Help me get the funding together](https://www.kickstarter.com/projects/174808720/maputnik-visual-map-editor-for-mapbox-gl) to take time of work and make this happen!