I'm having an issue that the offset of rows and columns is different depending on the size of the radius. The code is..
d3hexbin.hexbin().radius(tileSize)
Depending on the size, the row shifts. Hard to explain, so will provide images. It also seems like it's different depending on machine and/or browser.
The relationship between row vs column seems unpredictable, which causes problems for my code. Would like to know if there's a way to make this predictable. Maybe there is some math I can do to make sure I get one state vs the other.
I call one good and one bad, but actually it doesn't matter to me, as long as it can be predictable.
Hi, first thanks for this great plugin!
I'm having an issue that the offset of rows and columns is different depending on the size of the radius. The code is..
d3hexbin.hexbin().radius(tileSize)
Depending on the size, the row shifts. Hard to explain, so will provide images. It also seems like it's different depending on machine and/or browser.
The relationship between row vs column seems unpredictable, which causes problems for my code. Would like to know if there's a way to make this predictable. Maybe there is some math I can do to make sure I get one state vs the other.
I call one good and one bad, but actually it doesn't matter to me, as long as it can be predictable.
Good State (tile size 39)
Bad State (tile size 37)
code can be found here https://github.com/snellcode/insulam/blob/main/src/services/map.ts