cluhring · August 29, 2015 14:18 · rwarbelow · Apr 7, 2015 · cluhring · Apr 7, 2015
diff --git a/OSM, Overpas, Mapbox Studio b/OSM, Overpas, Mapbox Studio
 Currently, I'm working on a group project where we are consuming multiple APIs, including a trail locator api and several floral and fauna APIs. Unfortunately, our trail API isn't that sweet (Lydia's already broken it twice).  This got me thinking about possible alternatives, which led to me wondering why couldn't I just pull in our trail data directly from a map?  

 After much research & several Boulder Maptime meetups, this is what I've learned about a possible solution to our problem:

 In 2004, the OpenStreetMap (OSM) project was founded by Steve Coast (who lives right here in Denver, CO - Telenav) to map the UK, in response to huge government survey datasets sitting idle. By April 2006, the OpenStreetMap Foundation had been established to encourage the growth, development and distribution of free geospatial data and provide geospatial data for anybody to use and share.  Today, OSM is a free, editable, wiki-style map of the world that saw its 20 millionth user edit in January 2014 - thanks largly to the rise of hand-held gps locators and restrictions on the use and availability of map information. http://www.marketingshift.com/uploaded_images/googlevil-706076.jpg, 

 Overpass (or OSM3S) is a read-only API that serves up custom selected parts of the OSM map data. It acts as a database over the web: the client sends a query to the API and gets back the data set that corresponds to the query.  Unlike the main API, which is optimized for editing, Overpass API is optimized for data consumers. Two examples.

 One handy tool created by Overpass is the Overpass-turbo.eu website, which is a web based data mining tool that will run any kind of Overpass API query and shows the results on an interactive map.  This is a great site for three reasons: 1) It allows you to test and develope more or less complicated Overpass API queries. 2) You can save these clickable or static maps with your highlighted/selected OSM features, and 3) It can convert the OSM data to the useable formats like, geoJSON.

 And while I could just make the Overpass API call and render the data directly onto a basic map/application, I've learned how to create a custom map tile/layer using Mapbox Studio to render this data and I hope to have enough time to show you how to do that as well.  Mapbox Studio Demo.
	Currently, I'm working on a group project where we are consuming multiple APIs, including a trail locator api and several floral and fauna APIs. Unfortunately, our trail API isn't that sweet (Lydia's already broken it twice). This got me thinking about possible alternatives, which led to me wondering why couldn't I just pull in our trail data directly from a map?

	After much research & several Boulder Maptime meetups, this is what I've learned about a possible solution to our problem:

	In 2004, the OpenStreetMap (OSM) project was founded by Steve Coast (who lives right here in Denver, CO - Telenav) to map the UK, in response to huge government survey datasets sitting idle. By April 2006, the OpenStreetMap Foundation had been established to encourage the growth, development and distribution of free geospatial data and provide geospatial data for anybody to use and share. Today, OSM is a free, editable, wiki-style map of the world that saw its 20 millionth user edit in January 2014 - thanks largly to the rise of hand-held gps locators and restrictions on the use and availability of map information. http://www.marketingshift.com/uploaded_images/googlevil-706076.jpg,

	Overpass (or OSM3S) is a read-only API that serves up custom selected parts of the OSM map data. It acts as a database over the web: the client sends a query to the API and gets back the data set that corresponds to the query. Unlike the main API, which is optimized for editing, Overpass API is optimized for data consumers. Two examples.

	One handy tool created by Overpass is the Overpass-turbo.eu website, which is a web based data mining tool that will run any kind of Overpass API query and shows the results on an interactive map. This is a great site for three reasons: 1) It allows you to test and develope more or less complicated Overpass API queries. 2) You can save these clickable or static maps with your highlighted/selected OSM features, and 3) It can convert the OSM data to the useable formats like, geoJSON.

	And while I could just make the Overpass API call and render the data directly onto a basic map/application, I've learned how to create a custom map tile/layer using Mapbox Studio to render this data and I hope to have enough time to show you how to do that as well. Mapbox Studio Demo.