com presentations: slides for IPC, including a screen cast in case wifi breaks: mongo-osm-ipc.xml slides/map/gc-example.webm

Commit:    bce0cbd6edc93327b646baf03d2c740b98519225
Author:    Derick Rethans <[email protected]>         Wed, 23 Oct 2013 16:01:37 +0100
Parents:   432cd1b21450d399d05a48bb4c26ef8ffc43abd3
Branches:  master

Link:       http://git.php.net/?p=presentations.git;a=commitdiff;h=bce0cbd6edc93327b646baf03d2c740b98519225

Log:
slides for IPC, including a screen cast in case wifi breaks

Changed paths:
  A  mongo-osm-ipc.xml
  A  slides/map/gc-example.webm


Diff:
diff --git a/mongo-osm-ipc.xml b/mongo-osm-ipc.xml
new file mode 100644
index 0000000..94c8da3
--- /dev/null
+++ b/mongo-osm-ipc.xml
@@ -0,0 +1,170 @@
+<?xml version="1.0" encoding="utf-8"?>
+<presentation css="10gen-strict.css">
+<topic>MongoDB</topic>
+<title>Finding a pub with MongoDB and OpenStreetMap</title>
+<event>International PHP Conference</event>
+<location>Münich, Germany</location>
+<lat>48.13056</lat><lon>11.58973</lon>
+<date>October 28th, 2013</date>
+<speaker>Derick Rethans</speaker>
+<email>[email protected]</email>
+<twitter>derickr</twitter>
+<joindin>http://joind.in/9524</joindin>
+
+<slide>slides/mongodb/title.xml</slide>
+
+<slide>slides/mongodb/closed-pub.xml</slide>
+<!-- A few words about our dataset -->
+<slide>slides/mongodb/few-words-about-osm.xml</slide>
+
+<slide>slides/mongodb/flat-vs-sphere.xml</slide>
+
+<slide>slides/map/flat-sphere-flickr.xml</slide>
+
+<!-- DATA STORAGE -->
+<!--
+	No more [ lon, lat ], but geojson instead
+
+SAY WHERE ELSE GeoJson is used
+-->
+<slide>slides/mongodb/geojson.xml</slide>
+
+<!--
+	POINT:
+    show an image, and the GeoJson under 
+-->
+<slide>slides/mongodb/geojson-point.xml</slide>
+<!--
+	LINESTRING:
+    show an image, and the GeoJson under 
+-->
+<slide>slides/mongodb/geojson-linestring.xml</slide>
+<!--
+	POLYGON:
+    show an image, and the GeoJson under 
+-->
+<slide>slides/mongodb/geojson-polygon.xml</slide>
+
+<!--
+	CELLS,
+    We divide the surface of the earth into cells
+        A library called S2 from Google does the hard work
+    Cells have a level which define the size of the cell.
+    S2 provides 31 levels
+    The higher the level, the smaller the cell, and therefore the more needed to cover the earth
+    By default, we use all levels between 500m on a side and 100km on a side
+-->
+<slide>slides/mongodb/cells.xml</slide>
+<!--
+	Show grid of (part of) London:
+	- Point, Westminster palace
+	- Line, Oxford Street
+    - Polygon, Hyde Park
+-->
+<slide>slides/mongodb/cells-level10-example-london-1.xml</slide>
+<slide>slides/mongodb/cells-level10-example-london-2.xml</slide>
+<slide>slides/mongodb/cells-level10-example-london-3.xml</slide>
+
+
+<!-- operators
+    $near
+        find stuff near a point
+        index required
+    $geoWithin
+        find stuff within a polygon/circle
+        index NOT required
+    $geoIntersects
+        find stuff that intersects with other stuff
+        index NOT required
+
+-->
+<slide>slides/mongodb/geo-in-2.4.xml</slide>
+
+<!-- near
+	- Example with road and park
+	- slide with index/no index, and comparsion with 2.2?
+-->
+<!-- geoWithin
+	- Example with road and park
+	- slide with index/no index, and comparsion with 2.2?
+-->
+<!-- geoIntersects
+	- Example with road and park
+	- slide with index/no index, and comparsion with 2.2?
+-->
+<slide>slides/mongodb/geo-near.xml</slide>
+
+<!--
+	NEAR
+
+    Starts from a point
+    Looks at concentric donuts from that point
+    Want to look at documents within the donut
+    If distance from query point to document is within the donut, output
+    Adapts size of the donut as needed
+-->
+<slide>slides/mongodb/geo-near-explanation-0.xml</slide>
+<slide>slides/mongodb/geo-near-explanation-1.xml</slide>
+<slide>slides/mongodb/geo-near-explanation-2.xml</slide>
+<slide>slides/mongodb/geo-near-explanation-3.xml</slide>
+<slide>slides/mongodb/geo-near-explanation-4.xml</slide>
+<slide>slides/mongodb/geo-near-explanation-5.xml</slide>
+<slide>slides/mongodb/geo-near-explanation-6.xml</slide>
+<slide>slides/mongodb/geo-near-explanation-7.xml</slide>
+
+<!--
+	GeoWithin/GeoIntersecs
+
+    Generate a covering for geometry in query
+    Look at all points in all overlapping cells
+        Cells may be larger or smaller than our covering
+        Must look at cells that contain our covering
+        Must look at cells that we contain
+    See if documents are within or intersect our query geometry
+
+	Show examples of:
+	- within: The Palace of Westminster (point) in "City of Westminster" (polygon)
+	- intersect: thames (line) crossing London (polygon)
+-->
+<slide>slides/mongodb/geo-within.xml</slide>
+<slide>slides/mongodb/geo-within-1.xml</slide>
+<slide>slides/mongodb/geo-within-2.xml</slide>
+
+<slide>slides/mongodb/geo-intersects.xml</slide>
+
+
+<!--
+Without index:
+    $near
+        Look at every point
+        Sort by distance
+        Very slow, so requires an index.
+    $geoWithin
+        Look at every document
+        Is it within the query polygon?
+        Order is arbitrary
+    $geoIntersects
+        Look at every document
+        Does it intersect with the query geometry?
+        Order is arbitrary
+-->
+<!-- AGGREGATION:
+
+	- show tube stations per borough
+	- show pubs by borough
+
+http://docs.mongodb.org/manual/reference/aggregation/#stage._S_geoNear
+
+- distance is important
+- $geoNear in aggregation can't deal with more than one 2dsphere index
+- spherical option is *required* when using a 2dsphere index
+-->
+<slide>slides/mongodb/geo-aggregation.xml</slide>
+<slide>slides/mongodb/geo-aggregation2.xml</slide>
+
+<slide>slides/map/osm-xapi.xml</slide>
+<slide>slides/map/import-script-manchester.xml</slide>
+
+<slide>slides/mongodb/resources.xml</slide>
+
+</presentation>
diff --git a/slides/map/gc-example.webm b/slides/map/gc-example.webm
new file mode 100644
index 0000000..4bd4b8a
Binary files /dev/null and b/slides/map/gc-example.webm differ