Kevin Sahr

> > It might be worth clarifying that each coarser resolution digit represents the hierarchical indexing parent of a cell, which only "contains" the cell if it is the center...

> I believe there _is_ a tie-breaking strategy now, but it's in reference to the local IJK coordinate system on a particular icosahedron face, There is indeed, but it is...

> One issue with this is that to anyone from a geoinformatics or GIS background, a `Point` is represented as `[X,Y]`, which translates to `[longitude,latitude]`. But `(lat, lon)` are polar...

> > What I have seen done that may be a good solution is to **rename it to `LatLngPoint`**; this makes the ordering explicit, and differentiates it from any other...

> linking to #121 - there is still nothing in the documentation about the datum and ellipsoid The datum for H3 is a sphere with the WGS84 authalic radius. I...

> Also a +1 for `LatLng` (camelCase 4ever!). As for `Lng` vs `Lon` I personally prefer `Lng`. Implicit vowels works well enough that some languages are based on it. ;)...

@KeithFolkerts You're calculating the area of a planar hexagon, but H3 hexagons are on the sphere and will have greater area due to the spherical excess. I didn't create the...

@KeithFolkerts It has nothing to do with the icosahedron, the projection, accounting for pentagons, etc. Given the edge length of a hexagon, the hexagon will have a different area if...

The Starlink map looks to me like a web mercator projection with a 2D hex grid superimposed on it (I'm betting just for visualization purposes). So it is a fundamentally...

@Fil That is really nice work! I think it's a very clearly written and accurate description. I was a little surprised by the abruptness of the area change at the...