grim7reaper

10 ms·

1.
by grim7reaper 11mo ago
I’m pretty sure the approach isn’t that novel, but I really rediscovered it on my own while exploring several compressions approaches (generic compressions with tailored dict like zstd, integer packing/compressions, compressed bitmap,
2.
by grim7reaper 11mo ago
Ha, yeah, I remember reading about your project back in April (I think someone shared it on the GeoRust Discord). Really cool stuff you have here! Can't say I understand all the math behind it, as it's not my forte (even for H3, f
3.
by grim7reaper 11mo ago
They have a page about pros and cons: https://h3geo.org/docs/comparisons/s2/ For my use case, the visual distortion of S2 was quite a no-go. As for DB queries, it really depends on your use case and how you s
4.
by grim7reaper 11mo ago
I'm curious about those interesting stories ^^ Care to share a bit more?
5.
by grim7reaper 11mo ago
amo is using it quite a lot, mainly for the scratch map feature in the Bump Map application, but not only. Use cases are: - data storage - data aggregation/clustering - spatial indexing - geometrical computation (as long as you're
6.
by grim7reaper 11mo ago
I really want to do a DuckDB extension someday, I think it would be pretty cool. I had looked into it 2 years ago but didn't dig further. Now that H3 provides one, maybe I should take another look at it.
7.
by grim7reaper 11mo ago
Author here! Funny to see this on the front page xD That was the blog post for the initial release, and a lot of things have changed since then (definitely deserves a new blog post ^^). The first big change happened six months after the rel