feat: position convert #1381
Open
feat: position convert #1381
Conversation
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.
This PR is based on traccar/traccar#5566.
This PR adds support for the following map platforms:
PS: Baidu Maps support is not included in this PR because its tile cutting algorithm is different from the norm and requires further investigation.
This PR completes the display of different coordinates for different map types. Specifically: when using Amap, display GCJ-02 coordinates; when using OpenFreeMap, display original coordinates.
This PR fixes an i18n translation error:
mapOpenFreeMapinzh.json: should be开放自由地图