Dotdensity #283
Open
Dotdensity #283
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It should be noted that the voronoi approach is obviously wrong near boundaries (see: points in the ocean). These would have to be clipped to a geometry which currently isn't returned by the API (and at that point, tracts could be used instead of voronoi polygons for the dot density input). |
|
This sounds really interesting. Mind providing a screen shot? |
|
@sephcoster has been working on incorporating this upstream. |
|
Very nice! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Wrote in a dotdensity renderer for the HMDA data. Runs off voronoi polygons generated from the tract centroids. Decent way to look at the data where data is dense.. Not as much where data is sparse or zoom level is high.