News for hackers. Stuff that matters.
Re:Elasticsearch 1.0.0 released by Argorak on Thursday February 13, 2014 @07:59AM (#7231034)
Sure, ES supports lat/lon as properties, strings, geohash and geojson:

http://www.elasticsearch.org/guide/en/elasticsearch/referenc...

Re:Elasticsearch 1.0.0 released by morganherlocker on Thursday February 13, 2014 @09:54AM (#7231649)
I could be totally wrong, but the docs you linked to do not actually conform to the geojson spec. It is geographic and it is json, but not valid geojson. The part where it says:

> Format in [lon, lat], note, the order of lon/lat here in order to conform with GeoJSON.

.. the data example below is not actually geojson. See the spec:

http://geojson.org/geojson-spec.html

Re:Elasticsearch 1.0.0 released by Argorak on Thursday February 13, 2014 @11:58AM (#7232417)
I think the documentation is not clear here. ElasticSearch has an internal GeoPoint type, which can be read from any kind of JSON document. One of the possible notations is the GeoJSON coordinate notation.

Elasticsearch can map any kind of JSON, so you can, without problems, write a mapping for proper GeoJSON points. (map "type" as unanalyzed string, map "coordinate" as GeoPoint). Arrays of values are generally supported in ES.

The biggest problem is that Elasticsearch probably does not provide all kinds of queries you'd like if you are working with complex shapes. Basically, only distance and simple location queries with polygons are supported.

Re:Elasticsearch 1.0.0 released by morganherlocker on Thursday February 13, 2014 @02:53PM (#7233804)
Thanks for the explanation. Sounds like ES has equal or slightly more support for spatial stuff than MongoDB then (about as much as most people need).
Re:Elasticsearch 1.0.0 released by Argorak on Thursday February 13, 2014 @04:01PM (#7234301)
Well, thanks for pointing it out. That's a good opportunity for improval :).