I agree it would be a good call to have a single OpenAPI doc so that one could potentially publish a STAC service's definitions by inheriting from a single document, something like:
http://api.mystacapi.com/api:openapi: 3.0.3
info:
title: My STAC
version: 1.0.0
description: >-
My STAC Service.
contact:
name: STAC Developer
url: 'http://stacdev.com'
servers:
- description: "Production Server"
url: "https://api.mystacapi.com/"
tags:
- name: STAC
description: Implements the STAC API spec
- name: Capabilities
description: "Essential characteristics of this API"
paths:
'/':
$ref: ' https://api.stacspec.org/v1.0.0-beta.1/openapi.yaml#/paths/~1' <------
not sure why this was commented out, but it seems like we stopped doing the combine doc build at some point?https://github.com/radiantearth/stac-api-spec/blob/master/.circleci/build-openapi.sh
So the script had to be redone. Matt and Matthias tried a couple times, but there was some tricky particular thing that made it a big pain.
radiantearth/stac-spec#1073 - review would be great @philvarner / @matthewhanson / @lossyrob / @jbants / @jisantuc / anyone else (@m-mohr is likely asleep, so hopefully we actually get it merged before he does). Need 3 +1's to merge to master.
Ah shoot... Just realized we didn't actually include the biggest change in the changelog :(
Ok, fixed it, as well as the other little issue Matthias raised. PR needs reviews for dev, and then merge to master: radiantearth/stac-spec#1074
Thanks @matthewhanson and @jisantuc. Now the one that goes from dev to master - radiantearth/stac-spec#1075
I think I'd be in favor to delete the release and quickly re-release. Or we need to instantly publish rc.3
@m-mohr Could you also update https://github.com/radiantearth/stac-spec/blob/master/package.json manually? We use it as current version reference
But feel free to approve it, which will likely lead to merging it sooner.
Same for radiantearth/stac-spec#1075
Oh an I've re-released rc2
Hi all, I have a GeoTIFF with two bands, which I would like to describe in two assets within a STAC item. Is there a way to reference the band number within the asset property? I couldn't find any note about this. Is the recommended way to avoid multi-band files? Thanks.
9 replies
Looking to get the ItemCollection extension finalized. Since it's a new STAC object rather than a typical extension, and it links to specific versions of schemas in stac-spec it makes sense to keep it's version in sync with stac-spec and move to a 1.0.0 release with that.
Any comments on stac-extensions/item-collection#3 ?
Any comments on stac-extensions/item-collection#3 ?
Hi lads, I am new on the chat. In my project we are trying to implement STAC metadata to several datasets. Do you know if it is acceptable to have a STAC item json file with no asset? (I have tried to look it up in the chat before but haven't seen an answer related to this, apologise in advance if it has been answered already). Thank you in advance
Hey @m-mohr , we are a group working on specifications for creating AI ready EO datasets with ESA (https://eo4society.esa.int/projects/aireo/). We have some metadata elements we need to implement using STAC. The metadata elements change based on the profile of your data, like georeferenced image, georeferenced data, classified image, etc. Is there a way to implement these in STAC? Also, if you have time we can have a call.
for others who are validating using json schema -- are you handwriting the full json schema resolution, or does your lib handle that for you? what i'm using in Scala for on-the-fly validation on read from Franklin seems happy to resolve links in the file system but doesn't want to follow http links
@jisantuc:matrix.org I think I also had similar issues with ajv in JS, but the other way round.
looks like either pystac isn't handling the URLs yet or i'm reading the docs about validation incorrectly, but seems like i might be rolling my own here eventually. thanks @m-mohr for chiming in about ajv
@jisantuc:matrix.org Found it again, here's the ajv doc: https://ajv.js.org/guide/managing-schemas.html#asynchronous-schema-loading
There you also need to implement IO (e.g. HTTP requests, loading from file system) yourself, too.
There you also need to implement IO (e.g. HTTP requests, loading from file system) yourself, too.
In the Node Validator I used https://github.com/APIDevTools/json-schema-ref-parser to resolve things before passing them to ajv.