Geographic Information is represented as: Nodes Point Ways Line Closed Line Area (Polygon) eg. Roundabouts Relations Multi (Point / Line / Polygon) eg. Bus Routes / Inner Rings
Why make your own? Tile Usage Policy You’re in control: Design and Content Need tiles in EPSG:27700? 29903? Having OSM Data in a Database enables a lot of things You will learn a lot
Extract Raw Data – Embedded in a map on a web page map.addLayers([ make_layer("http://overpass-api.de/api/interpreter?data= node[amenity=pub](bbox);out+skel; (way[amenity=pub](bbox);node(w););out+skel;", “Blue") ]);
Extract Raw Data – Embedded in a map on a web page map.addLayers([ make_layer("http://overpass- api.de/api/interpreter?data=node[amenity=pub](bbox);out+skel;", "blue"), ]);
Some 'Takeaways‘ License Check obligations if mixing data Data Model Area / Multipolygon handling is complex Usage Policies Desktop prob not an issue. Server, web different Build Your Own No apt-get install tileserver Yet Shapefiles Easy, not complete Postgis Starting point for many possibilities Data APIs Great for snapshots in geojson or POI webpages Data vs Services Is OSM commoditising data? Is that bad?