Can additional, searchable properties fields be added to this? Say I wanted
to do a geosearch by location and by time property?
Is it recommended to shove it into a properties: {} field like geojson? Or
is it supposed to be peer to location or does it not really matter?
On Tuesday, February 24, 2015 at 3:52:50 AM UTC-5, Georgi Ivanov wrote:
>
> Like Jun said,
> You need geo shape type.
>
> The problem is, it is very slow to index shapes (except POINT).
>
> I tried with line-strings and it is extremely slow with linestring 10
> points long or longer.
>
> It is just killing the CPU.
>
>
>
> On Tuesday, February 24, 2015 at 6:38:37 AM UTC+1, Sai Asuka wrote:
>>
>> So I see the elasticsearch claims to use "GeoJSON" as the format for
>> indexing... but when I look at the docs.. the same it gives is:
>>
>>
>> {
>> "location" : {
>> "type" : "polygon",
>> "coordinates" : [
>> [ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0],
>> [100.0, 0.0] ]
>> ]
>> }
>> }
>>
>>
>> Doesn't GeoJSON look like this?
>>
>> {
>> "type": "Feature",
>> "properties": {
>> "name": "Sparkle",
>> "age": 11
>> },
>> geometry: {
>> "type" : "polygon",
>> "coordinates" : [[[100.0, 0.0], [101.0,0.0], [101.0, 1.0], [100.0],
>> [100.0, 0.0]]]
>> }
>> }
>>
>> My question is how do I index polygons in elasticsearch if I want to
>> attach properties to it? If I wanted to perform a bulk load for example,
>> what does one document look like that has polygon information that I can
>> perform geospatial queries on?
>>
>
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/cdb3c63b-a58f-4c0a-bc76-6bc10b163513%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
