Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@dadofsambonzuki just wanted to share what I was playing with this weekend. When I installed h3 on my system using the requirements.txt in this PR I was getting an error when trying to generate the h3 geometry using poly fill. I am honestly not confident that this implementation gives the same result as yours...
From reading about h3 it seems like their resolution scale is defined from 0-15 and doesn't have a direct physical meaning (like degrees or km). I also was only able to get h3 to run in WGS84 (units degrees) and not web mercator (units area). Right now this code is building a grid at scale 2 (very coarse), aggregating, converting to web mercator and then calculating area/density. Because the CRS is so warped in many parts of the map I expect there is quite a bit of error in the area calculation. This should be less of an issue as the hex size gets smaller. I am guessing the version of the code you had running before was aggregating at scale 8, which is probably more appropriate for an interactive map, but wasn't displaying the static plot