Geo: Support geo_point type

[kimchy]

Mapper type called geo_point to support geo based points. The declaration looks as follows:

{
    "pin" : {
        "properties" : {
            "location" : {
                "type" : "geo_point"
            }
        }
    }
}

Input Structure

The above mapping defines a geo_point, which accepts different formats. The following formats are supported:

Lat Lon As Properties

{
    "pin" : {
        "location" : {
            "lat" : 40.12,
            "lon" : -71.34
        }
    }
}

Lat Lon As Array

{
    "pin" : {
        "location" : [40.12, -71.34]
    }
}

Lat Lon As String

{
    "pin" : {
        "location" : "41.12,-71.34"
    }
}

Geohash

{
    "pin" : {
        "location" : "drm3btev3e86"
    }
}

Index Fields

The geo_point type creates two floating point fields, called lat and lon. In our example above, two fields will be create, the first location.lat and the second is location.lon. Though probably not needed, there is an option also to create a third field called geohash with the geohash value (represented as location.geohash). In most cases, those specific fields are not needed when using geo capabilities, and only location will be needed (for example, with geo_distance filter).

Mapping Options

• resolution: controls the floating point resolution of the stored fields. Defaults to 64, but can also be 32.
• geohash: set to true to store also the geohash in the index. defaults to false.
• geohash_precision: sets the geohash precision, defaults to 12.

[kimchy]

Geo support: geo_point type and geo_distance filter, closed by 194e6cb, #279

[decitre]

I have a GeoCouch feeding an es index through _changes.
Documents are compatible with geojson spec.
Is there a way to extend geo_point as a Lon Lat As Array ?

[kimchy]

Can you post a sample format?

[decitre]

In the following example, the geo coordinates are provided for both ES ("location" member) and GeoJSON ("coordinates" member):

{
  "_id": "p996602367",
  "_rev": "1-2b5e6ba6707a19c9bf0a00a9da67cda8",
  "type": "Feature",
  "geometry": {
      "type": "Point",
      "coordinates": [
          7.637420177459717,
          47.80836868286133
      ]
  },
  "children": {},
  "feature_code": 7312,
  "parents": {
      "1016": [
          "a20174512"
      ],
      "1022": [
          "l67331525"
      ]
  },
  "location": {
      "lat": 47.80836868286133,
      "lon": 7.637420177459717
  },
  "properties": {
      "attributes": {
          "11": {
              "value": "WERDERSTRASSE",
              "language": "GER"
          },
          "10": "77",
          "ON": {
              "value": "BUDGET",
              "language": "GER"
          },
          "BN": {
              "value": "BUDGET",
              "language": "GER"
          },
          "%C": "443",
          "TL": {
              "value": "+(49)-(7631)-foobar",
              "language": "GER"
          }
      }
  }
}

[kimchy]

I have just mailed the mailing list to ask if its ok to make this change in ES (breaks backward comp.). If nobody objects too greatly, I can change everywhere to use the array format defined in GeoJSON (that includes queries and facets as well).

[decitre]

That's very "agile" !