matchhostfsowner VS h3

I wrote a portable solution for the user ID mapping problem: https://github.com/FooBarWidget/matchhostfsowner

I'm at the verge of releasing version 1.0 of MatchHostFsOwner, a solution for the Docker filesystem owner matching problem. MatchHostFsOwner is my first serious Rust project. It's an entrypoint program to be used in Docker containers. Rust's error handling idioms force me to take all possible error conditions seriously, while also encouraging me to have proper error messages for each error condition. I use rust-musl-builder to generate statically-linked Linux binaries that work on all Linux distros.

I'm working on a solution based on strategy 1 (matching the container's UID/GID with the host's). This solution already works, and I've already deployed it in a few of my own projects, but isn't very well-documented yet. I'm also working on more automated tests to guarantee that it's rock-solid. Would you be interested in testing it and giving feedback once it's in a more ready state?

It looks like the base Kontur dataset uses H3 resolution 8, and there’s a lookup table here. “400m” seems to refer to the edge length (which averages to 461m).

I can speak to quadtrees, but the primary reason for using this is that you need a geographic "dictionary" (not using the word map to avoid confusion with charts), and you're perhaps already using the H3 hexagonal grid system.

HexSet: is a way of storing a set of H3 cells in a tree, and doing fast (2-20 ns on my 2013 trashcan Mac Pro) membership tests. You must first convert the input data (e.g. GeoJSoN polygon) into H3 cells.

> What an amazing tool that can completely change function names when it converts from C to Go.

How can one read the code of the benchmark, then switch into virulent sarcasm mode without trying to understand the code? And seeing "+1" comments without any effort to understand is also disheartening.

The blog post had a link about the Go helper functions the author used. It lands on https://github.com/akhenakh/goh3/blob/main/h3.go This shows that the `FromGeo()` function used by the Go benchmark is a helper that calls transpiled functions. The benchmark code itself was of course not transpiled, so the sarcasm was unneeded and wrong.

If anyone wants to dig in deeper, the C function `latLngToCell()` calls 2 functions, see https://github.com/uber/h3/blob/master/src/h3lib/lib/h3Index...

Uber just released their library to perform geospatial indexing - https://h3geo.org/. This might be an useful building block for you.