Made geo into its own part, and removed percolation

Author: clintongormley

310_Geolocation/10_Intro.asciidoc renamed to 04_Geolocation.asciidoc

@@ -1,6 +1,8 @@
 [[geoloc]]
-== Geolocation
+= Geolocation
 
+[partintro]
+--
 Gone are the days when we wander around a city with paper maps. Thanks to
 smartphones, we now know exactly where we are all of the time, and we expect
 websites to use that information.  I'm not interested in restaurants in
@@ -29,5 +31,6 @@ other hand, are used purely for filtering.  They can be used to decide whether
 two shapes overlap or not, or whether one shape completely contains other
 shapes.
 
+--
 
 

310_Geolocation.asciidoc

@@ -0,0 +1,14 @@
+include::310_Geopoints/20_Geopoints.asciidoc[]
+
+include::310_Geopoints/30_Filter_by_geopoint.asciidoc[]
+
+include::310_Geopoints/32_Bounding_box.asciidoc[]
+
+include::310_Geopoints/34_Geo_distance.asciidoc[]
+
+include::310_Geopoints/36_Caching_geofilters.asciidoc[]
+
+include::310_Geopoints/38_Reducing_memory.asciidoc[]
+
+include::310_Geopoints/50_Sorting_by_distance.asciidoc[]
+

310_Geolocation/40_Geohashes.asciidoc

@@ -1,8 +1,12 @@
-[[indexing-geopoints]]
-=== Indexing geo-points
+[[geopoints]]
+== Geo-points
+
+A geo-point is a single latitude-longitude point on the Earth's surface. They
+can be used to calculate distance from a point, to determine whether a point
+falls within a bounding box, or in aggregations.
 
 Geo-points cannot be automatically detected with
-<<dynamic-mapping,dynamic mapping>>. Instead, geo-points fields should be
+<<dynamic-mapping,dynamic mapping>>. Instead, `geo_point` fields should be
 mapped explicitly:
 
 [source,json]
@@ -25,7 +29,8 @@ PUT /attractions
 -----------------------
 
 [[lat-lon-formats]]
-==== Lat/Lon formats
+[float]
+=== Lat/Lon formats
 
 With the `location` field defined as a `geo_point`, we can proceed to index
 documents containing latitude/longitude pairs, which can be formatted as