add comment geojsonpoint #3956
Closed
add comment geojsonpoint #3956
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
|
Thanks for bringing this up! We'll update the documentation to cover coordinate order/naming.
|
christophstrobl
added a commit
that referenced
this pull request
Feb 9, 2022
Mention the relation of Point/GeoJsonPoint x/y coordinates to longitude/latitude. Original Pull Request: #3956
|
Thank you @sangyongchoi for your contribution! Merged to main development line via bc027be. |
christophstrobl
pushed a commit
that referenced
this pull request
Feb 17, 2022
Mention x -> longitude, y -> latitude relation. Closes: #3956
christophstrobl
added a commit
that referenced
this pull request
Feb 17, 2022
Mention the relation of Point/GeoJsonPoint x/y coordinates to longitude/latitude. Original Pull Request: #3956
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.
Hello, I found some discomfort while using GeoJsonPoint.
The meaning of x and y is not clear.
In my country, longitude and latitude are used more often than x and y.
I thought there would be a case like mine, so I added the following comment.
Please consider adding
thank you.