Geo Point indexing

Hi @ll,

i tried to index data using the Java Api (XContentBuilder adding a GeoPoint
as a field), which is indexed as type String, the value looks like
[22.2,33.3]. Then i did some research and found the following page:
http://www.elasticsearch.org/blog/geo-location-and-search/ with the comment
saying:

"Update: The automatic mapping of “geo enabled” properties has been
disabled since publishing this article. You have to provide the correct
mapping for geo properties. Please see the documentationhttp://www.elasticsearch.org/guide/reference/mapping/geo-point-type.html
."

I'm now wondering if there is a way to enable the automatic mapping of "geo
enabled" properties (Configurable?)?
Why was is disabled? (in my case it would be very helpful, because i need
to index dynamically).

Anyways, the link to the documentation in the comment is not working for me.

Thanks in advance and best regards,
Tho

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi Tho,

unfortunately the automatic mapping of the geo_point has been disabled and
you have to define it on your own. Maybe I can ask about your usecase?

cheers,
Florian

On Wednesday, October 23, 2013 2:01:51 PM UTC+2, Tho82 wrote:

Hi @ll,

i tried to index data using the Java Api (XContentBuilder adding a
GeoPoint as a field), which is indexed as type String, the value looks
like [22.2,33.3]. Then i did some research and found the following page:
Elasticsearch Platform — Find real-time answers at scale | Elastic with the
comment saying:

"Update: The automatic mapping of “geo enabled” properties has been
disabled since publishing this article. You have to provide the correct
mapping for geo properties. Please see the documentationhttp://www.elasticsearch.org/guide/reference/mapping/geo-point-type.html
."

I'm now wondering if there is a way to enable the automatic mapping of
"geo enabled" properties (Configurable?)?
Why was is disabled? (in my case it would be very helpful, because i need
to index dynamically).

Anyways, the link to the documentation in the comment is not working for
me.

Thanks in advance and best regards,
Tho

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Will dynamic templates work? Both in terms of Tho's scheme and in terms of
the geo point mapping limitations.

--
Ivan

On Thu, Oct 24, 2013 at 1:16 AM, Florian Schilling <
florian.schilling@elasticsearch.com> wrote:

Hi Tho,

unfortunately the automatic mapping of the geo_point has been disabled and
you have to define it on your own. Maybe I can ask about your usecase?

cheers,
Florian

On Wednesday, October 23, 2013 2:01:51 PM UTC+2, Tho82 wrote:

Hi @ll,

i tried to index data using the Java Api (XContentBuilder adding a
GeoPoint as a field), which is indexed as type String, the value looks
like [22.2,33.3]. Then i did some research and found the following page:
Elasticsearch Platform — Find real-time answers at scale | Elastichttp://www.elasticsearch.org/blog/geo-location-and-search/with the comment saying:

"Update: The automatic mapping of “geo enabled” properties has been
disabled since publishing this article. You have to provide the correct
mapping for geo properties. Please see the documentationhttp://www.elasticsearch.org/guide/reference/mapping/geo-point-type.html
."

I'm now wondering if there is a way to enable the automatic mapping of
"geo enabled" properties (Configurable?)?
Why was is disabled? (in my case it would be very helpful, because i
need to index dynamically).

Anyways, the link to the documentation in the comment is not working for
me.

Thanks in advance and best regards,
Tho

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi,

my usecase is, that i want to index an EMF Model structure with 1 root
element dynamically without having the overhead of creating an index
mapping by myself. I have several fields, which contains an GeoPoint (which
i set as a GeoPoint into the XContentBuilder), and i want to provide geo
search with that dynamic mapping.

I don't understand why that feature already worked and why it was disabled,
i would love to use that feature. And i didn't found any parameter in the
configuration file to enable it, which would be very helpful.

Best regards,
Tho

Am Donnerstag, 24. Oktober 2013 10:16:59 UTC+2 schrieb Florian Schilling:

Hi Tho,

unfortunately the automatic mapping of the geo_point has been disabled and
you have to define it on your own. Maybe I can ask about your usecase?

cheers,
Florian

On Wednesday, October 23, 2013 2:01:51 PM UTC+2, Tho82 wrote:

Hi @ll,

i tried to index data using the Java Api (XContentBuilder adding a
GeoPoint as a field), which is indexed as type String, the value looks
like [22.2,33.3]. Then i did some research and found the following page:
Elasticsearch Platform — Find real-time answers at scale | Elastic with the
comment saying:

"Update: The automatic mapping of “geo enabled” properties has been
disabled since publishing this article. You have to provide the correct
mapping for geo properties. Please see the documentationhttp://www.elasticsearch.org/guide/reference/mapping/geo-point-type.html
."

I'm now wondering if there is a way to enable the automatic mapping of
"geo enabled" properties (Configurable?)?
Why was is disabled? (in my case it would be very helpful, because i
need to index dynamically).

Anyways, the link to the documentation in the comment is not working for
me.

Thanks in advance and best regards,
Tho

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Dynamic mapping worked! I just defined a string field and a field name, the
parameter i defined was indexed afterwards as type geo_point.
Thanks for the tip Ivan..

Cheers, Tho

Am Donnerstag, 24. Oktober 2013 23:32:31 UTC+2 schrieb Ivan Brusic:

Will dynamic templates work? Both in terms of Tho's scheme and in terms of
the geo point mapping limitations.

Elasticsearch Platform — Find real-time answers at scale | Elastic

--
Ivan

On Thu, Oct 24, 2013 at 1:16 AM, Florian Schilling <
florian....@elasticsearch.com <javascript:>> wrote:

Hi Tho,

unfortunately the automatic mapping of the geo_point has been disabled
and you have to define it on your own. Maybe I can ask about your usecase?

cheers,
Florian

On Wednesday, October 23, 2013 2:01:51 PM UTC+2, Tho82 wrote:

Hi @ll,

i tried to index data using the Java Api (XContentBuilder adding a
GeoPoint as a field), which is indexed as type String, the value looks
like [22.2,33.3]. Then i did some research and found the following page:
Elasticsearch Platform — Find real-time answers at scale | Elastichttp://www.elasticsearch.org/blog/geo-location-and-search/with the comment saying:

"Update: The automatic mapping of “geo enabled” properties has been
disabled since publishing this article. You have to provide the correct
mapping for geo properties. Please see the documentationhttp://www.elasticsearch.org/guide/reference/mapping/geo-point-type.html
."

I'm now wondering if there is a way to enable the automatic mapping of
"geo enabled" properties (Configurable?)?
Why was is disabled? (in my case it would be very helpful, because i
need to index dynamically).

Anyways, the link to the documentation in the comment is not working for
me.

Thanks in advance and best regards,
Tho

--
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 elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.