Make lon lat key order consistent across files#198
Open
wowza8448 wants to merge 1 commit into
Open
Conversation
Contributor
|
@wowza8448 Good catch, thanks. This looks good to me but @robertleeplummerjr and some other people have the authority to approve / merge if you reach out to them by email maybe? |
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
2 participants
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.
#189 fixed the lng lat order, but Shapes were "correct" before this fix so shapes are the one that is broken now. Now this change makes lines, shapes and points consistent to be lng lat from the GeoJSON by default. @nathanorm