Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Examples 'nice to haves' #981

Open
3 of 11 tasks
cholmes opened this issue Feb 9, 2021 · 0 comments
Open
3 of 11 tasks

Examples 'nice to haves' #981

cholmes opened this issue Feb 9, 2021 · 0 comments
Labels
Milestone

Comments

@cholmes
Copy link
Contributor

cholmes commented Feb 9, 2021

With the examples refresh there are a ton more of little improvements that we could do. Indeed I could probably spend several days making the most awesome 'fake' catalog. But that's not the best use of time at the moment. So I'm moving all the 'extras' ideas here. I think we can ship 1.0.0-RC1 without any (though others feel free to push back), but keeping for posterity.

  • Add more items in the 'extensions collection' that show off more of the core extensions functionality, but based on the core examples. Would be good to also have one or two that link to some of the more mature extensions that didn't make the core cut, like sar and file.
  • Update 'roles' to show off more of the latest roles best practice stuff in Roles best practice #989
  • Have all items use totally different data (right now the main examples are basically three copies of the same data) - create assets, get the right bounds and other data, generate extents to be right, etc.
  • demonstrate use of a remote schema (using one of the extensions not in the core repo - likely easier after we move extensions out of the core repo)
  • Add another catalog example that just shows how it can be used to organize items? We just have one pure catalog example now, which is 'above' collections, could make sense to have one 'below', but I'm not sure what items to put in it. Perhaps if we have an extension with two examples we can put it in its own catalog.
  • Update any eo:bands to follow recommendations in Eo clarifications #974 - ideally one that just uses assets, and one that is a nice summary of assets in properties.
  • Better summaries, and have a range of items that it actually fully summarizes. Add one to the extensions collection
  • Bug reports for STAC Browser to display everything right - start_datetime & end_datetime (in the catalog link of the item), proj shape/transform, update to use 'visual' role (things work fine now, but should try to use it if it's there).
  • Get a stable location for a browser (could be stacindex), update rel=alternate / type=html to that location and advertise that as well.
  • Register remotedata.io (the sample provider) and make it so all the links work
  • Figure out an automated way to keep self links up to date through releases
@cholmes cholmes added this to the 1.0.0-RC.1 milestone Feb 24, 2021
@cholmes cholmes modified the milestones: 1.0.0-RC.1, 1.0.0 Mar 3, 2021
@cholmes cholmes modified the milestones: 1.0.0, 1.0.0-rc.2, 1.0.0-rc.3 Mar 24, 2021
@m-mohr m-mohr modified the milestones: 1.0.0-rc.3, 1.0.0, 1.0.0-rc.4 Apr 29, 2021
@cholmes cholmes modified the milestones: 1.0.0-rc.4, 1.0.0 May 3, 2021
@cholmes cholmes modified the milestones: 1.0.0, 1.0.1 May 25, 2021
@m-mohr m-mohr added the minor a relatively small change to the spec label May 2, 2023
@m-mohr m-mohr modified the milestones: 1.0.1, 1.1 May 2, 2023
@PowerChell PowerChell removed this from the 1.1 milestone May 6, 2024
@m-mohr m-mohr added this to the future milestone Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants