Timeline for Best approach for indexing a SQLite database containing geoJSON spatial objects?

Current License: CC BY-SA 3.0

6 events

when toggle format	what		by	license	comment
Aug 24, 2015 at 12:55	comment	added	William Smith		As it turns out, I had a lot of difficulty getting Spatialite to work. I was able to get the pod installed and everything seemed fine at first, but later I realized there was a problem with the compiled architectures; no 64 bit. I found a Homebrew example where all of the architectures were built, but the resulting file size concerned me. Ultimately, I dropped back and went with vanilla R*Tree because the fast indexing is my primary requirement. Some of those spatial functions written into Spatialite would have made my life a lot easier, though.
Aug 23, 2015 at 0:28	comment	added	BradHards		The point of R*Tree in SQLite (and hence gpkg / splite) isn't the table with the values, its the efficient indexing.
Aug 22, 2015 at 16:44	comment	added	user30184		The RTree in Spatialite an GeoPackage is actually just a table that holds xmin, ymin, xmax, ymax values. You can as well create similar table by yourself, index the fields and make queries like `(select id from rtree_tablename_geom where minx<BBOX_maxx and maxx>BBOX_minx and miny<BBOX_maxy and maxy>BBOX_miny);`
Aug 22, 2015 at 2:25	vote	accept	William Smith
Aug 22, 2015 at 2:25	comment	added	William Smith		After reviewing the RTree documentation and finding some tutorials on how to compile a custom amalgamation of SQLite for iOS (not clear on all those details yet), it looks like RTree offers exactly what I need. However, the Spatialite extension seems to offer a lot more than just efficient virtual tables for indexing envelopes. I'm still trying to figure out how to turn the extension on in iOS, but if I can do that I think Spatialite is the route I'm going to take. Thanks for the suggestions!
Aug 22, 2015 at 0:14	history	answered	BradHards	CC BY-SA 3.0