Kevin Sahr

> The premise of the question is a little tricky to begin with, since Web Mercator tiles may be very different areas depending where they are on the earth, whereas...

@billyauhk did you include the pentagons in your calculations? Note that the table in the H3 documentation gives the average area for hexagons only. Maybe the table in the documentation...

@billyauhk When we refer to hexagons and pentagons, we are talking about the topology of the cells: all cells at all resolutions have either 5 or 6 neighbors, which makes...

@billyauhk This is standard terminology in global grid literature. An edge is the boundary between two cells. The additional points merely densify that edge in a particular space, they don't...

It looks like you're calculating the area using the formula for a hexagon on a plane. But H3 cells are spherical polygons, so that formula does not apply.

@mlyons-tcc I am contending that the formula you give above is the formula for the area of a planar hexagon, and that a spherical polygon will always have a larger...

@mlyons-tcc The "average hexagon area" is just the surface area of the earth divided by the number of hexagons at each resolution (adjusted for the 12 pentagons). It has no...

I haven't been following the issues daily so sorry for being late to the conversation again... The lack of range checks on arrays throughout H3 core (including the recent `baseCells`...

> To @sahrk' point, another suggestion posted in the issues is to expand the base cells array and ensure we never calculate an index into that array outside of 0-127...

> > Sorry if I wasn't clear, I'm referring to the last `45 bits` of the index marked as `Digit` `1`,`2`,`3`...`15 `on that page. For instance at res 13 what...