-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Scattergeo BADNUM #1538
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Scattergeo BADNUM #1538
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
bfe0211
make scattergeo calcdata 1-1 with lon/lat items in fullData
etpinard 18091e8
rm `placeholder` early exit in scattergeo hover routine
etpinard a705ed1
update geojson util calcTraceToLineCoords to use BADNUM
etpinard 64cbf2f
flatten scattegeo_test.js
etpinard f84627d
set lonlat to [BADNUM, BADNUM] if lon OR lat is non-numeric
etpinard e85fba5
only need to check lonlat[0] === BADNUM
etpinard 6a7e2a4
Merge branch 'master' into scattergeo-badnum
etpinard aec6248
make sure mapbox-gl canvas does not inherit left and top css
etpinard 1abbd90
:hocho: scattermapbox/calc.js | :recycle: scattergeo/calc.js
etpinard 3e64aa0
update scattermapbox convert & hover
etpinard 785bade
update mapbox baselines
etpinard 5c2393a
:hocho: last remaining signs of `placeholder` key in calcdata
etpinard b5cd573
replace false values with BADNUM in empty calcdata traces
etpinard 248b760
Merge pull request #1564 from plotly/scattermapbox-badnum2
etpinard File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the record, I just had a discussion with @etpinard about this where my gut reaction was that we should do
instead of creating all the nodes and then deleting the bad ones.
The conclusion we came to though is that the way it is here is actually better, despite being a bit less "d3-idiomatic." The rationale is that bad points should be considered an edge case, so we don't worry about the overhead of creating and deleting their nodes (which will happen on every replot), just about how the
.each
call to test (good) points for removal compares to whateverfilterOutBadPoints
does. And since the latter would always need to duplicate thecalcdata
array, it's almost certainly slower than this.each
.