This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Geometry encoding #34
Merged
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
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.
Resolves #32 - see comments there for initial discussion. The main advantage to this approach is that all API wrappers which require geometries as input can accept common python vector data structures.
This PR adds an
encodingmodule providing a few useful functions, mainlyencode_waypointsandencode_polylinewhich take iterables of feature-like objects and return data fit for posting to mapbox APIs.There is a dependency on polyline which is a nice Python2/3 port of mapbox/polyline. The other option (gpolyencode) is not Python 3 compatible and doesn't give results consistent with mapbox/polyline (see gist)