Any plans for geo support? Looks like you have lat/lon stored as two independent doubles, which does not lend itself well to any sort of geo operations.
If anyone from questdb is around, and want tips on how to go around implementing GIS support for a database, hit me up! Email on my profile.
Will do. Thanks for offering help!
Yes, this is part of the roadmap. Right now, we don't have any interesting query to showcase that would use these columns - they are here because they are part of the original dataset and we are keeping them for when we demo further releases.