Update stac-browser to work with STAC 0.9 and 1.0.0-beta.1 #33
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
In the case where external items are used with the context extension, features are paged during fetch time. Therefore the number of items in the 'items' collection is always less than the item page limit, so it's necessary for the Vue table based paging to always 'stay' on page 1 to show the current item list.
This is useful if you want to test stac-browser against a STAC that does not have the CORS permission to be used in stac-browser. For example, with http-server installed from npm nad running ``` http-server -p 1111 --proxy https://geobase-spot-dev.s3.amazonaws.com/ --cors ``` to proxy the geobase STAC, and then running stac-browser with ``` CATALOG_URL=https://geobase-spot-dev.s3.amazonaws.com/catalog.json \ STAC_PROXY_URL="https://geobase-spot-dev.s3.amazonaws.com|http://localhost:1111" \ npm start ``` Allows for proper browsing of that STAC.
lossyrob
force-pushed
the
feature/rde/work-with-current-stac-versions
branch
2 times, most recently
from
300a8fd
to
a9212a3
Compare
|
Wonderful! What are the common mistakes? |
lossyrob
commented
Jun 8, 2020
lossyrob
commented
Jun 8, 2020
lossyrob
commented
Jun 8, 2020
m-mohr
reviewed
Jun 8, 2020
|
@m-mohr the two that I accounted for were: the spatial extent 'bbox' being a single array of coordinates instead of an array of arrays, and provider roles being a single string instead of an array. |
This updates the collection extent format to the 0.8 and above specification. This also accounts for backwards compatibility, so pre-0.8 STACs will still work.
This commit deletes the "dictionary.json" property map that exists, and creates a `property.js` file that defines mappings between property names and display information for use in the property bar. It also adds properties and extenions for 1.0.0-beta.1.
lossyrob
force-pushed
the
feature/rde/work-with-current-stac-versions
branch
from
a9212a3
to
8ceada8
Compare
This commit adds async schema validation that fetches schema based on the stac version of the object being presented.
lossyrob
force-pushed
the
feature/rde/work-with-current-stac-versions
branch
from
8ceada8
to
de1eb52
Compare
|
Thank you for the review @m-mohr! |
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.
This PR updates stac-browser to work with 1.0.0-beta.1 and 0.9.0 STACs.
Changes of note:
dictionary.jsonproperty map to a js function for comment-ability; split the group definitions (extensions and data providers) from the properties. Added property definitions for 1.0.0-beta.1 extensions so they show up on the side bar - some exceptions for objects that would require more complicated display logic.stac_versionproperty.Catalogs tested against:
Some catalogs had validation errors; I put in some workarounds to account for common mistakes, but in some cases the STACs will need to be corrected to work with the updated stac-browser.