2023edits #172
Merged
2023edits #172
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
- This fixes warnings with the asciidoc execution. - Also no longer including DomainSet subset. The only case where subsetting the domain is useful is potentially for irregular grids, though the number of coordinates to list should not be too extensive. The other case is point clouds, where XYZ coordinates must be retrieved for every single point, but in this case using LAS/LAZ subset directly with the coverage request is probably more appropriate. Therefore, we may want to omit this requirements class from Part 1, and rethink whether it is needed in the future.
- Either not included, or redundant
- Matching clause numbers with generated section numbers - Starting to regroup requirements / recommendations / permissions directly within the requirements class file, with the clause section simply containing an overview sub-section and including the requirements class file. - Directly including the examples in the annex and referencing the section of the examples annex in the sections
- Update to overview text - Updating conventions, overview to remove /coverage/* resource and add /coverage/schema resource - Moving CIS-specific content from overview to CIS JSON encoding req. class
2-conformance: summary tables
jerstlouis
requested review from
cmheazel,
Schpidi,
ghobona,
joanma747,
pebau,
tomkralidis,
chris-little,
ayoumans,
glennlaughlin and
pomakis
jerstlouis
force-pushed
the
2023edits
branch
from
931026b
to
2d65796
Compare
|
2023-09-06: Motion to merge these edits Motion: Amy Present: Carl, Joan, Tom, Amy, Jerome |
This was referenced Sep 6, 2023
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.
Proposed draft iteration for OGC API - Coverages, for which I hope to soon hold a SWG vote to approve merging these changes.
19-087.pdf
The main changes is getting rid of all
/coverage/*resources, with a JSON Schema at/schemareplacing the CIS RangeType resource, and the collection description extent with its uniform additional dimension capabilities andgridproperty replacing the CIS DomainSet. It isolates the dependency on the Coverage Implementation Schema to the CIS JSON requirement class.The document was also significantly shortened and simplified overall, while also adding new draft requirement classes for the different encodings (currently a short stub in many cases), for selecting an output CRS, and for scenes making up a coverage.