updated readme to remove contradiction #13
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.
The old verbiage in the 3rd paragraph of the extension README implied that label assets must be in the form of GeoJSON FeatureCollection only. This contradicts the specification elsewhere in the extension README and in the
schema.jsonas well, which has accommodations for for raster/GeoTIFF labels as well.Old verbiage:
These labels can take several forms, though all are expected to be contained with a GeoJSON FeatureCollectionNew verbiage:
These labels can take several forms, though the most commonly expected formats are GeoJSON Feature or FeatureCollection for vector labels, and GeoTIFF for raster labels