Repository navigation
maxzoom, minzoom, scheme - #38
Merged
Merged
Conversation
mapsam
reviewed
May 2, 2018
|
|
||
| OPTIONAL. Default: 0. >= 0, <= 30. | ||
|
|
||
| An integer specifying the minimum zoom level. |
Contributor
There was a problem hiding this comment.
Since maxzoom has "MUST be >= minzoom" do we want to include the same for minzoom? "MUST be <= maxzoom"
mapsam
reviewed
May 3, 2018
| Implementations MUST treat unknown keys as if they weren't present. However, implementations MUST expose unknown key/values in their API so that API users can optionally handle these keys. Implementations MUST treat invalid values for keys as if they weren't present. If the key is required, implementations MUST treat the entire TileJSON manifest file as invalid and refuse operation. | ||
| Implementations MUST treat unknown keys as if they weren't present. However, implementations MUST expose unknown key/values in their API so that API users can optionally handle these keys. Implementations MUST treat invalid values for keys as if they weren’t present. If the the field is an optional field and the value is invalid, the default value MAY be applied. If the key is required, implementations MUST treat the entire TileJSON manifest file as invalid and refuse operation. | ||
|
|
||
| Default` |
mapsam
added a commit
that referenced
this pull request
Aug 18, 2021
* 3.0 skeleton * name, tilejson, version, description * bounds first draft * MAY assume * update version major example * maxzoom, minzoom, scheme (#38) * zooms, scheme, adds default value info, and adds minzoom MUST value * tiles (#40) * Add tiles field, and add clarification around extensions used * Add center field * data section * copy over grids * legend * template * fix line break * Per pnorman's suggestions * full semver versioning * Update directory name based on valid semver versioning * Forgot to delete the old dir * RFC 8259 is the current JSON spec (#47) RFC 8259 has obsoleted RFC 7159, which obsoleted RFC 4267. Only significant difference from RFC 4267 is that it disallows UTF-16 and UTF-32 encodings for JSON and mandates UTF-8 only. I've also switched the IETF links to the HTML versions and changed "WGS:84" to "WGS 84". * add fillzoom * quick updates from @springmeyer * clarify data field usage * vector_layers (#42) * Expand on empty fields object, provide example, and add subsections * 3.0 notes and updates (#52) * Add note on grid interactivity * Ensure integers are integers in the examples * Consistify use of TileJSON and consistify fillzoom json example with the spec description * Ensure tile endpoints are absolute urls * Use set of tiles instead of tileset * keys and values * update section order & put required first * add extra note about bounds of one dimension * define implementation * add caching, schema.json * add osm.json example * add examples link * fix link * add data types, some review updates * final edits * update CHANGELOG' * update README and changelog Co-authored-by: Carol Hansen <carol@mapbox.com> Co-authored-by: Sean Gillies <sean.gillies@gmail.com>
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.
Per #36, and branched from #37 to avoid huge conflicts.
This PR also adds clarification around "Default" values
cc @mapsam