-
-
Notifications
You must be signed in to change notification settings - Fork 155
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
status/design of stac implementation #876
Comments
* add items link to collection, improves #876 * update title text --------- Co-authored-by: Genuchten <paul.vangenuchten@wur.nl> Co-authored-by: Tom Kralidis <tomkralidis@gmail.com>
There is an ongoing plan to improve the compatibility between STAC tooling and pycsw in the next few months. |
We will review our STAC support as part of the next release. |
@pvgenuchten can you give this another round of testing and provide feedback? Below is an example based on pycsw master (via https://demo.pycsw.org/gisdata/stac). Modelling STAC assets is currently not supported (note that if a pycsw metadata repository holds a STAC item with assets, they will be emitted accordingly). |
I'm curious to learn more about the implementation of stac in pycsw. Maybe some of my questions are more functional on how the implementation is supposed to work.
From the https://demo.pycsw.org/cite, there is a link to stac api, following that I arrive in https://demo.pycsw.org/cite/search (why
search
and notstac
), however on that endpoint I would expect a listing of collections (metadata.main) which then links to /items which provides the actual listing of stac itemsWhen i post the /search url in https://radiantearth.github.io/stac-browser, i arrive in a nice catalogue page
However there is no option to continue into any items or assets from the collection endpoint
The problem may be that https://demo.pycsw.org/cite/collections/metadata:main?f=json does not include a link to /items as for example https://paituli.csc.fi/geoserver/ogc/stac/collections/luke_erosion_susceptibility_of_agricultural_areas_at_paituli?f=json has (why is stac browser even querying that endpoint, because it is a ogc-api-records endpoint)
On the html output of pycsw i'm actually able to drill down into a stac item from the search page https://demo.pycsw.org/cite/stac/collections/metadata:main/items/urn:uuid:e9330592-0932-474b-be34-c3a3bb67c7db
Notice the
/stac/
part in the url. Now when navigating for example to /cite/stac/collections/metadata:main/items or /cite/stac/collections/metadata:main I get a 500 error. Could be ok, since these links are not advertised, but a bit unexpected.None of the records advertise assets, although they sure have links to datasets, what is the mechanism to include a dataset-href as an asset (https://docs.pycsw.org/en/latest/stac.html does not mention assets, so maybe this has not been implemented yet?)
interestingly the ogcapi-records implementation in pygeoapi displays quite nicely in stac browser
A suggestion could be to combine ogcapi-records and stac in a single endpoint, and only in details enable configuration of specific stac or ogcapi-records aspects.
The text was updated successfully, but these errors were encountered: