h3 VS open-location-code

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.

Pluscode is a trademark. The actual standard is called "open location code" and is unrestricted - https://github.com/google/open-location-code/

Yeah, that seems like a bad design choice. If you look at the spec [0], you can see that they only use "23456789CFGHJMPQRVWX" in the codes. They apparently scored the letters based on how well they can spell 10000 words in 30 languages, without thinking about character similarity. If they had involved actual humans instead of counting letter frequency, they might have noticed that the letter W looks similar to VV, and that its English name is "double U". And tried a letter like N or Y, which would be much harder to confuse.

[0] https://github.com/google/open-location-code/blob/main/docs/...

Lots of thoughts from the founders incl comparison with other systems here: https://github.com/google/open-location-code/wiki/Evaluation-of-Location-Encoding-Systems

It's licensed Apache 2.0 https://github.com/google/open-location-code

I wish https://plus.codes/ took off. The benefit compared to what 3 words is that you can use the closest city to give directions and cells next to each other share the bigger cell name.

And an additional shoutout for https://plus.codes/ from Google.

New to this so sorry if this is stupid. I've been trying to use https://plus.codes to try to check an address for availability at starlink. Whatever code I put in, it simply tells me afterwards "please enter an address or a plus code". That website seems to give me either a shorter or a longer plus code. Neither of them seems to make the starlink website happy. When I try putting in the address, it doesn't like that either. Confused on where to go from here.