Make it possible to use Choropleth layer with data containing NaNs. #972
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
HaudinFlorence
force-pushed
the
allow_nans_with_Choropleth
branch
from
4f412de
to
b96d8c6
Compare
HaudinFlorence
force-pushed
the
allow_nans_with_Choropleth
branch
3 times, most recently
from
e31f8cc
to
a9886b1
Compare
…he NaN regions have a dedicated color referred to as nan_color (black is set as default value) and a dedicated opacity referred to as nan_opacity (set to 0.4 as default value).
HaudinFlorence
force-pushed
the
allow_nans_with_Choropleth
branch
from
a9886b1
to
079ee97
Compare
|
Thanks!! |
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.
Make it possible to use Choropleth layer with data containing NaNs. The NaN regions have a dedicated color referred to as nan_color (black is set as default value) and a dedicated opacity referred to as nan_opacity (set to 0.4 as default value).
Resolve issue #428