the reason I was using `geopoly` was because I wanted to use the `geopoly_within` function which, as the docs imply, is supposed to be very fast because it uses the RTree indexes. I must say, this is the first instance of being disappointed at SQLite's performance. I am hardly better than an intermediate user, but I have been using SQLite forever. And I don't ever recall throwing anything at it and not being amazed at how wonderfully it performs. Until now, with `geopoly`. Given the additional overhead of having to create and maintain a VIRTUAL locations table, it hardly seems worth the effort given its lackluster performance. In my case, using RTree alone makes no sense as I can get very fast (though slightly less precise) results doing just a naive bbox query using min and max lats and lngs. And no, Spatialite is not an option. I would much rather just jump to PostGIS if it ever came to that. Though I seriously hope it won't. I do love the simplicity and agility of SQLite too much to give it up (easily).