Hi Chris,
Yes, we are have seen GeoWave. From conversations with the GeoWave
team, we did make a number of similar design choices. Both projects
are under active development. Each project has looked different
datasets and focused on different analytics.
The big notable difference between the implementations is the space
filling curve we use to index quad tries. They use an external,
compact Hilbert curve library while we have rolled our own
GeoHash/Z-curve/Morton order code. GeoMesa has added support for
attribute indexes. (I'm not sure if GeoWave has added a similar
feature.) With separate spatio-temporal and attribute indexes,
GeoMesa can likely select smaller Accumulo ranges than one would
need to using a compact Hilbert curve covering all the data.
Ideally, that'd lead to a boost in query performance. I don't know
of any benchmarks, and each project can be tuned. Anyhow, I think
that's the most fair comparison I can make as a biased developer.
Cheers,
Jim
On 01/13/2015 05:24 PM, Chris Snider
wrote:
Hi,
Ran across this product the other day and
wondered if anyone on the GeoMesa team had any familiarization
with it:
https://ngageoint.github.io/geowave/
Chris Snider
Senior Software
Engineer
Intelligent
Software Solutions, Inc.
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://www.locationtech.org/mailman/listinfo/geomesa-users
|
