This repository was archived by the owner on Mar 15, 2025. It is now read-only.
WIP: Support VTM Maps #442
Draft
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
|
Can one of the core team members give me the the permission to test this? |
|
add to whitelist |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
This PR is aiming to add the new Map provider VTM (by Mapsforge). It is a partial fix to the mapsforge support (mapsforge itself should be updated too but that is not in scope of this PR).
Related issues
Related to #73
Additional context
This PR will get its Git History cleaned once it is ready for review. Comments by anyone are appreciated at any point in time.
Documentation used to implement the new provider: