Influxdb: GeoHash and GeoSpatial Support :: Feature Request

[ywadi]

Hi,
A very heavy use case I am facing using a time series database is the ability to tag it with a location (GeoLocation) especially for remote sensing and sensor positions globally. In our case at a weather company almost everything is a spatiotemporal set of data.
We are doing it on influx by simply adding a GeoHash string with the data and then query it back with Regex to get all points in time at a certain location.

I would be great if this could be done out of the box, the ability to add a measure with a time and geohash and then simply query them back. Since geohash as a concept solves for the big issue of how to index and lookup data it should be fairly simple with what influx already has.

Leaving it to you guys, and great job with the 0.9 release, amazing difference in performance.

[bencevans]

+1

[pauldanckaert]

This would be a great help! +1

[jeremyforan]

+1 seems natural

[jpdias]

+1

[ankushb]

+1

[chopj]

+1

[kaushikkapil]

+1

[pietermarsman]

+1

[justb4]

+1

[cholmes]

+1

[ehames]

This feature is very handy for IoT projects.

[whitetigle]

+1

[igledaniel]

+1

[sclausen]

+1

[IvanVas]

+1

[gandavar]

+1

[jcr1984]

+1

[lrolsen]

+1

[rbetts]

Those up-voting, it would be helpful to hear more specifics on use cases.

1. What problem are you trying to solve?
2. Would geohash / S2 / space-filling-curves solve your problem?
3. Or, do you need more precision?
4. Are there specific geo functions you need to solve the problem?
5. What are the queries you expect to require? (points in poly? points in radius? ...)
6. What types of charts / graphs would need to be rendered?
7. What types of alerts would need to be triggered?

[lrolsen]

We have a number of geographically distributed sensors. We would like to be able to perform aggregations on the readings made by these sensors based on their geographical location. So for us, being able to tag each series with a geographical location and then query the series using one or more polys to aggregate on the series in those polys would do the trick for us.

With regards to precision, a 5 decimal geohash would be enough for our use cases.

[nfroidure]

We have the same requirement and we found the ES geo-distance implementation very convenient: https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-geodistance-aggregation.html

Would be nice to have something similar on InfluxDB.

[whitetigle]

It seems this have been addressed meanwhile with geo time series like warp10.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically closed because it has not had recent activity. Please reopen if this issue is still important to you. Thank you for your contributions.

[timhallinflux]

This is available via Flux...in the InfluxDB 1.8 release.
https://docs.influxdata.com/flux/v0.65/guides/geo/

Also the Telegraf 1.14 release has a s2 geo processor which will calculate the required s2_cell_id (geohash) used by Flux as a tag (index).