Draft
Conversation
Member
|
Thanks @timoore! While this looks reasonable to me, I'm a little hesitant to merge it at the moment. Mostly because I suspect we're eventually going to go in a direction where vector data is encoded in glTF, rather than create a separate Tile content type for GeoJSON specifically. I think we should wait to merge this until either we have some more clarity on that, or we have a more pressing need to deliver this functionality. Does that seem ok to you? |
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.
Support tilesets with GeoJson content via the MAXAR_content_geojson extension.