Closed
Conversation
… with 0,0 moving coords out of addFeature(), not multiplying x,y coords with path_multiplier becuase the query takes care of it.
…purposes. cleaning up mapbox - splitting into more meaninglful functional blocks
…l, landuse, kind is None, nothing will be sent)
…ng/arc seperated with their MOVE_TO and SEG_ENDs. This simplifies things because the cmd logic is now part of the parser/builder that builds the cordinate array - we no longer need _process_points and _get_cmd_type functions
…trick to get what google pbf wants (big endian)
Open
Member
|
This is no longer relevant, closing. (Split into a separate package anyhow, so doesn't reflect current reality.) |
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.
adding support to mapbox/mvt format