http://apache-carbondata-dev-mailing-list-archive.168.s1.nabble.com/DISCUSSION-Support-for-Geospatial-indexing-tp85268p85513.html
Hi Jacky,
we have checked about geomesa
a. Geomesa is tightly coupled with key-value pair databases like Accumulo, HBase, Google Bigtable and Cassandra databases and used for OLTP queries.
b. Geomesa current spark integration is only in query flow, load from spark is not supported. spark can be used for analytics on geomesa store.
Here they override spark catalyst optimizer code to intercept filter from logical relation and they push down to geomesa server.
All the query logic like spatial time curve building (z curve, quadtree) doesn't happen at spark layer. It happens in geoserver layer which is coupled with key-value pair databases.
c. Geomesa is for spatio-temporal data , not just a spatial data.
so, we cannot integrate carbon with geo mesa directly, but we can reuse some of the logic present in it like quadtree formation and look up.
Also I found another alternative "GeoSpark", this project is not coupled with any store.
so, we will check further about integrating carbon to GeoSpark or reusing some of the code from this.
Also regarding the second point, yes, we can have carbon implementation as a generic framework where we can plugin the different logic.
Thanks,
Ajantha