I spun up a stac-fastapi service with a pgstac backend as a docker network on a remote server and almost everything is working really well. I am able to open the catalog with pystac_client without any problems and the search endpoint is working great, but get_collections and similar functions are not working because of a problem with the self_href attribute which is getting set to the current working directory on my local machine even!
It looks like the root and self hrefs are the same for my catalog, which might be confounding pystac somehow. I tried playing around with the pystac.stac_object internals and could not identify the exact point at which the href for the selflink gets replaced with a local directory, but I presume it happens because the root href is identical to self.
Here is what I see at my STAC endpoint:
{
"type": "Catalog",
"id": "stac-fastapi",
"title": "ncx-stac",
"description": "stac-fastapi",
"stac_version": "1.0.0",
"conformsTo": [
"https://api.stacspec.org/v1.0.0-rc.1/ogcapi-features/extensions/transaction",
"https://api.stacspec.org/v1.0.0-rc.1/ogcapi-features",
"http://www.opengis.net/spec/ogcapi-features-4/1.0/conf/simpletx",
"https://api.stacspec.org/v1.0.0-rc.1/item-search#fields",
"https://api.stacspec.org/v1.0.0-rc.1/item-search#sort",
"http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/core",
"https://api.stacspec.org/v1.0.0-rc.1/item-search",
"https://api.stacspec.org/v1.0.0-rc.1/item-search#query",
"http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/oas30",
"https://api.stacspec.org/v1.0.0-rc.1/item-search#context",
"https://api.stacspec.org/v1.0.0-rc.1/collections",
"https://api.stacspec.org/v1.0.0-rc.1/core",
"http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/geojson"
],
"links": [
{
"rel": "self",
"type": "application/json",
"href": "http://<IP.ADDRESS>:<PORT>/"
},
{
"rel": "root",
"type": "application/json",
"href": "http://<IP.ADDRESS>:<PORT>/"
},
{
"rel": "data",
"type": "application/json",
"href": "http://<IP.ADDRESS>:<PORT>/collections"
},
{
"rel": "conformance",
"type": "application/json",
"title": "STAC/WFS3 conformance classes implemented by this server",
"href": "http://<IP.ADDRESS>:<PORT>/conformance"
},
{
"rel": "search",
"type": "application/geo+json",
"title": "STAC search",
"href": "http://<IP.ADDRESS>:<PORT>/search",
"method": "GET"
},
{
"rel": "search",
"type": "application/geo+json",
"title": "STAC search",
"href": "http://<IP.ADDRESS>:<PORT>/search",
"method": "POST"
},
{
"rel": "child",
"type": "application/json",
"title": "hls-monthly",
"href": "http://<IP.ADDRESS>:<PORT>/collections/hls-monthly"
},
},
{
"rel": "service-desc",
"type": "application/vnd.oai.openapi+json;version=3.0",
"title": "OpenAPI service description",
"href": "http://<IP.ADDRESS>:<PORT>/api"
},
{
"rel": "service-doc",
"type": "text/html",
"title": "OpenAPI service documentation",
"href": "http://<IP.ADDRESS>:<PORT>/api.html"
}
],
"stac_extensions": [
"https://raw.githubusercontent.com/radiantearth/stac-api-spec/v1.0.0-rc.1/fragments/context/json-schema/schema.json"
]
}Looking around at public STACs, it seems like there is sometimes one more layer (landing page?) above the catalog with the actual STAC endpoint that serves as the root. e.g. https://cmr.earthdata.nasa.gov/stac/
Does anyone have any ideas on how to configure stac-fastapi to generate a link structure that pystac_client interprets correctly? The catalog's links look like this when I open the catalog using pystac_client:
[<Link rel=self target=/home/<USER>/workspace>, # this is a local directory!
<Link rel=root target=http://<IP.ADDRESS>:<PORT>/>,
<Link rel=data target=http://<IP.ADDRESS>:<PORT>/collections>,
<Link rel=conformance target=http://<IP.ADDRESS>:<PORT>/conformance>,
<Link rel=search target=http://<IP.ADDRESS>:<PORT>/search>,
<Link rel=search target=http://<IP.ADDRESS>:<PORT>/search>,
...]When I try to run catalog.get_all_collections() I hit an error because it is searching through my local workspace!
3 replies
When creating a STAC item for multi-band datasets which of these options do people prefer?
- one multi-band asset
- several single-band assets
I have seen both in the wild, and it looks like some of the tooling is better-suited to multi-band assets e.g. https://github.com/developmentseed/rio-stac
1 reply
2 replies
Please excuse my dumb question up front. We're hashing about for a kind of "VRT for point clouds", which STAC+extensions would seem to fit decently except for the desire to have A SINGLE FILE.
Is STAC Collection, Catalog, and Items all jammed single JSON file a valid thing right now? Could it be?
17 replies
As per the EO Extension Specification, there is a limited set of common_name values that are accepted. Does anyone know what values should be placed into the common_name property of the Band Object for bands that don't have an accepted Common Name, e.g. the cloud mask (CLD) or scene classification layer (SCL) bands of Sentinel-2? Should I add these in a PR to the extension, or is there another extension/place these bands should go within a STAC Item? Thanks in advance!
11 replies
stac_item["properties"]["sensor"] == "sentinel2". What's the best way to accomplish this? Setting the "query" argument on the /search endpoint fails because it looks like the queryables don't include the properties. Setting the "filter" argument is silently ignored as far as I can tell. I'm not sure it's supported in the SQLAlchemy backend. Do I need to migrate to the pgstac backend?
I also posted this question in the Issues page of the GIT repo Best way to return maximum item object for a request #348
I would like to return the maximum number of item objects from the server for a given request. I'm running into an error when attempting to increase the limit parameter to the maximum 10000 granule return
We've added recommended citation information for publications if you write about STAC. More details and Bibtex is available from the corresponding repos.
For stac-spec:
STAC Contributors. (2021). SpatioTemporal Asset Catalog (STAC) specification (Version 1.0.0). https://stacspec.org
For stac-api-spec:
STAC API Contributors. (2022). SpatioTemporal Asset Catalog (STAC) API specification (Version 1.0.0-rc.2). https://stacspec.org
5 replies
https://github.com/stac-extensions/forecast
1 reply
2 replies
@cholmes Hey-hey.
I left a sizable PR ( radiantearth/stac-site#63 ) to add links to the logos on the site.
Could you or Stuart take a look?
1 reply
Each stereo asset is a separate item and then use a new "stereo" rel type to link between two items. One or two fields to describe the characterictics may also be good to have (like a common identifier and the "side"), depending on the use case.
5 replies
1 reply
gs:// protocol is no good either. Can anyone share an example of how they adapted the StacIO class of pyStac lib to work with GCS? Or, is there a built-in solution that I am missing?
1 reply
stac-fastapi, does anyone know how to disable individual extensions in the provided pgstac app? We're using the app provided by the stac_fastapi.pgstac.app module (source code) which sets the list of extensions at import time. We'd like to remove the TransactionExtension from that list, but I'm not sure if it's possible to remove an extension after the StacApi object has already been created?
Etag as asset-level metadata. It's easy enough for us to write a custom extension to allow this, but it got me thinking: Since S3/GCS/etc are quite common, has there ever been discussion around a "Cloud Storage" extension? Just brainstorming I can think of a few other metadata properties that may be useful to record - if the object has SSE, requester-pays policies, storage class, etc
2 replies
1 reply
This version incorporates stac-validator and stac-check runs on the collections and items returned by the API, support for passing Authorization: Bearer token header or a query parameter for authorization, and a lot of refactoring the internals of how the http requests are made.
1 reply
$ stac-validator https://earth-search.aws.element84.com/v0/collections/sentinel-s2-l2a/items --item-collection --pages 2
2 replies