Getting too large numbers for Longitude?

[haywood1]

For some reason i keep getting latitude in the number of 100822540197861.69 any ideas why. I was hoping more to have hexagons as a half but stayed at 1km and still keep getting this issue.

The code and some of the GeoJSON is here as the GeoJSON is quite large: https://jsfiddle.net/nxcn02dt/

[DenisCarriere]

@haywood1 Thanks for reporting this, however this bug seems to have larger issues.

I've been able to fix the Longitude issue by using Center coordinates to calculate the xFraction/cellWidth & yFraction/cellHeight.

1. Distance Issue

Also calculating distance([-180, -90], [180, -90]) causes issues in the results when the latitude is the same:

Edit: Not an issue distance([-180, -90], [180, -90]) should equal to 0.

> distance([-180, -90], [180, 90])
20021.369981327753
> distance([-180, -90], [180, -90])
9.557969094904018e-29
> distance([-180, 90], [180, 90])
9.557969094904018e-29
> distance([-180, 90], [180, -90])
20021.369981327753

2. Hexgrid distortion

Would be opened as a separate issue

When the bbox extents becomes larger the grids become more and more distorted.

Solution: This could be resolved by transforming the coordinates to an equidistance projection, applying the grid, then converting back to degrees.

hexgrid([-185, -90, 180, 90], 500, 'kilometers');

Hex Grid using World BBox

Hex Triangle Grid

[DenisCarriere]

Published a patch release for @turf/hex-grid v4.3.1 with the fix.