Hello everyone,
I find QuestDB incredibly fast and powerful, really happy in the choice of migrating so far.
The only aspect I’m a little sad about is the impossibility of making spatial queries using a polygon as a mask.
Will this ever be supported?
I mitigated the problem with PostGIS, but this forces me to have a dual database repository. Also I know I could probably transform the polygon in geohashes with a small resolution and then use the withing operator with a subquery, but that is just “ugly”.
Hi @LucaBonaldoIT ,
We have other users interested in this feature too, but it is not currently a priority.
We do take community contributions, and this can be implemented using the existing BINARY or VARCHAR types, along with new functions in the griffin query engine. We would be happy to support addition of these features from the community.
Me and my colleague thought we could do that indeed!
It would be super awesome to contribute in a open source project.
To get on the right track it would be nice to hear from someone that already contributed or is currently doing that.
If someone is interested so are we!
They are. I will make a tracking issue and we can start getting some ideas of what features you need and what order to approach them. I’m also happy to go explain how the internal APIs fit together to make this work.
Here is the new issue: Geospatial types and GIS support · Issue #4899 · questdb/questdb · GitHub
It would be great if you could help to flesh this out further. We can identify some first steps for a proof-of-concept i.e a couple of types supported, a couple of functions. For example, taking two points and calculating the connecting line.
Amazing!
I read the issue and found it well-written. I’ll keep an eye out for further updates.
Thank you very much in the meantime!