News for hackers. Stuff that matters.
Re:H3: Hexagonal hierarchical geospatial indexing system by setr on Wednesday September 15, 2021 @01:57PM (#28542249)
https://h3geo.org/docs/core-library/restable

The smallest granularity is . 0000009 km^2, so I guess 1/3 of an inch. Which seems to me a ridiculously and unnecessarily precise, but who knows

Re:H3: Hexagonal hierarchical geospatial indexing system by junon on Wednesday September 15, 2021 @01:59PM (#28542272)
It wasn't that granular. Maybe a few blocks of the city in size, give or take. The visualizers I'm seeing have a single hexagon span the entirety of Austin, TX for reference. At least in Uber's usecase, that was less than useful.
Re:H3: Hexagonal hierarchical geospatial indexing system by setr on Wednesday September 15, 2021 @02:10PM (#28542380)
It’s a hierarchy… so you can take your pick of granularity? Only thing that matters is min, max and step-size.

Unless we’re talking about different things, I’m not clear why we’re not assuming the tool you remember chose h10 or whatever level was actually useful to it, where the visualizations chose h5

Re:H3: Hexagonal hierarchical geospatial indexing system by junon on Wednesday September 15, 2021 @03:06PM (#28543019)
I don't remember ours being a hierarchy but perhaps it was just the visualization.
Re:H3: Hexagonal hierarchical geospatial indexing system by ambrood on Wednesday September 15, 2021 @09:22PM (#28546773)
Uber's internal stuff used resolution 9 i think...
Re:H3: Hexagonal hierarchical geospatial indexing system by tln on Wednesday September 15, 2021 @02:31PM (#28542605)
That table shows H15 cells are on average 0.9 m^2, or a hexagon with edges 0.59m long.

(The average edge length is 0.5m, but that's not the same as the edge length of the average area hexagon)