As you can see here, I've done the mapping of the field to be geopoint. I started with just the latlon-values, and then tried to add the geohash representation to see if that would work. I would prefer to only use latlon at the end.
I suspect the issue may be related to the geohash property in the document values, but that's mostly just a guess.
It's easy enough to confirm though - simply add another field with the same geo data, without the geohash property, and see if that works correctly with the TileMap.
It's also possible, though I think unlikely, that the field mapping is wrong. Check the output from /test/_mapping/field/geopoint against Elasticsearch, and see if the type is in fact geo_point.
Looking closely at my reply from the mapping request, I can now see that there are double quotes around the "location" field. This is the discrepancy when using a Mac and it's not using default double quotes in the text editor. When removing the index, and adding mapping without these faulty double quotes, it works. Thanks for the help!
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.