Merged
Conversation
Contributor
Author
|
Now that I think about it, maybe the better solution would be just to make sure that the |
Owner
|
My first reaction was just specify your bins in float numpy.arange give an array of in only if the three values(start, stop, step) are int. |
This file contains hidden or 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
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.
The following code from example was causing problems:
WIth the traceback:
The reason is when the step is 1 (or any other integer), coordinates that are created are also integers (it lon/lat can be divided without reminder). Then when an attempt is made to add floats to them, it causes a problem.
Not sure if it's the right place to convert coordinates to floats, or it should be done earlier.