Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Phil Varner
    @philvarner
    One last-minute fix for STAC API 1.0.0-beta.3 radiantearth/stac-api-spec#192
    Phil Varner
    @philvarner
    Matthias Mohr
    @m-mohr
    STAC Browser v3 Alpha gets deployed to https://radiantearth.github.io/stac-browser now and everyone can check it out. It supports entering your own catalogs (and APIs, although API support is limited and still worked on right now). Feel free (and encouraged) to send any feedback my way already in this stage of the development so that we can come up with the best STAC Browser ever ;-)
    Work items right now: Loading and displaying COGs on the map (via stac-layer), OGC API - Features support, better rendering for more complex metadata (e.g. bands, data cube dimensions, ...)
    Angelos Tzotsos
    @kalxas
    will the stac-browser work against a STAC API server?
    Matthias Mohr
    @m-mohr
    @kalxas Yes
    Anything specific you are thinking about? It already loads APIs right now, just doesn't support OGC API - Features endpoints yet, which I'm implementing right now.
    Angelos Tzotsos
    @kalxas
    we have added STAC API support in pycsw recently
    and we are wondering if we can use stac-browser
    thanks for the feedback, I will test and report back
    Matthias Mohr
    @m-mohr
    Give me a couple more days to finalize API support. Do you have any link I can test with, too?
    Pete Gadomski
    @gadomski
    I wanted to bring folks' attention to the #stac channel in the opendatacube slack: https://opendatacube.slack.com/archives/C02B6CJFTCG. you can request an invite to the opendatacube slack here: http://slack.opendatacube.org/. there's some discussion in that channel around ongoing work to read stac catalogs directly into the opendatacube api (without having to ingest the data into the opendatacube database first)
    Angelos Tzotsos
    @kalxas
    Matthias Mohr
    @m-mohr
    Hmm.... it's likely that the ?f=json is an issue for STAC Browser right now and I'm not sure whether we'll support that. Any chance to make this work just with HTTP headers (e.g. Accept headers)? @kalxas
    jlaura
    @jlaura
    Naive question: Is this the proper way to specify a BBOX for a poly that spans the dateline? I've got the actual poly encoded as a GEOJSON multipolygon, but want to get the BBOX correct. The BBOX is another candidate for what could be what is causing issues on ingest into ES.
    BBOX [178.97616273955, 58.0176601586323, -178.94312261301, 58.5413335623229]
    1 reply
    Matthias Mohr
    @m-mohr

    API support (including the most requested pagination support, excluding search) has landed in STAC Browser v3, so please report any issues you are facing, there are probably some: https://radiantearth.github.io/stac-browser/

    @kalxas Right now your APIs are not supported due to the query parameter f=json, which is not supported. Any chance we can make that work with Accept headers instead of the query parameter?

    Angelos Tzotsos
    @kalxas
    hi @m-mohr
    we will review and report back about the Accept headers
    thank you
    Tom Augspurger
    @TomAugspurger

    I wanted to share some links to prototypes for cataloging tabular data with STAC:

    1. https://github.com/TomAugspurger/table: a stac extension adding a couple fields to Collection and Item for the columns and table metadata
    2. https://github.com/TomAugspurger/stac-table a little python library for generating a STAC Item from a table

    If anyone has thoughts on those I'd be happy for the feedback.

    9 replies
    afasseco
    @afasseco

    Hi

    I recently asked this radiantearth/stac-api-spec#198 in STAC API spec and philvarner suggested I come here.
    What I'm looking for are suggestions or pointers to examples on how to serve the assets in the same service as the STAC API.
    When browsing other STAC APIs I usually see asset urls pointing to s3 or some other download site. Have anybody seen this done in the same service as the STAC API itself?

    philvarner suggested serving under

    /collections/{collection_id}/items/{item_id}/assets/{asset_name}
    and my suggestion was
    /download/itemid

    Any other ideas?

    Thanks.

    11 replies
    Jon Duckworth
    @duckontheweb
    Does anyone have a static STAC 1.0.0 catalog that is publicly available that I could use in our Quickstart guide in PySTAC?
    6 replies
    Yves Moisan
    @ymoisan
    Hi all. I see in the FAQs the issue of the relationship with 19115 is still TBD. Is that still the case ?
    5 replies
    Maxim Lamare
    @maximlamare
    Hi everybody!
    I have been working on a contribution to stactools-packages and would like to know what are the next steps: do I open an issue? If so where? Here: https://github.com/stactools-packages/stactools-packages.github.io ?
    4 replies
    ungarj
    @ungarj
    Hi all, I am getting a parse_exception when using the sat-search command line tool using the earth-search endpoint. Do I use the tool incorrectly or are there currently issues on the endpoint?
    $ sat-search search --datetime 2021-08-01 --bbox 16 46 17 47 --url https://earth-search.aws.element84.com/v0
    Traceback (most recent call last):
      File "/home/ungarj/.virtualenvs/mapchete/bin/sat-search", line 8, in <module>
        sys.exit(cli())
      File "/home/ungarj/.virtualenvs/mapchete/lib/python3.8/site-packages/satsearch/cli.py", line 166, in cli
        main(**kwargs)
      File "/home/ungarj/.virtualenvs/mapchete/lib/python3.8/site-packages/satsearch/cli.py", line 130, in main
        items = search.items(headers=headers)
      File "/home/ungarj/.virtualenvs/mapchete/lib/python3.8/site-packages/satsearch/search.py", line 90, in items
        found = self.found(headers=headers)
      File "/home/ungarj/.virtualenvs/mapchete/lib/python3.8/site-packages/satsearch/search.py", line 62, in found
        results = self.query(url=url, headers=headers, **kwargs)
      File "/home/ungarj/.virtualenvs/mapchete/lib/python3.8/site-packages/satsearch/search.py", line 80, in query
        raise SatSearchError(response.text)
    satsearch.search.SatSearchError: parse_exception
    2 replies
    Rob Emanuele
    @lossyrob
    stac-fastapi 2.1.0 is released, supporting STAC API 1.0.0-beta.3, supporting the filter extension and with experimental CQL support for the pgstac backend
    2 replies
    Phil Varner
    @philvarner
    I think the OGC API bi-weekly mtg is right before the STAC API mtg, so I didn't get an update on these two issues until mid-way through.
    1) conformance classes - OGC is going to split the lower/upper functions into a separate conformance class, which we'll adopt after they've made the change
    2) queryables - they've added the additionalProperties : boolattribute that defines the behavior for if a CQL expression has a term that is not defined in the queryables. When true, the query is not rejected, and it is assumed an Item that does not have it has a value of null (iirc, this is what elasticsearch does)
    Pete Gadomski
    @gadomski

    Question from the OpenDataCube #stac channel:

    Is there a STAC paper I can cite?

    4 replies
    Sylvain Brunato
    @sbrunato

    Hi, we can see in https://github.com/radiantearth/stac-api-spec/tree/master/core that for the Landing Page:

    The returned JSON must be a valid STAC Catalog

    But in landing page examples, "type": "Catalog" is always missing (see example-landing-page-for-stac-api---core or overview.md#example-landing-page).
    Should the examples be updated, or is there a thing that I did not see in the spec?
    Thanks.

    3 replies
    Josh Fix
    @joshfix
    This message was deleted
    1 reply
    goriliukasbuxton
    @goriliukasbuxton
    Hey, Element84 STAC catalog does not have B10 band? https://earth-search.aws.element84.com/v0/collections/sentinel-s2-l2a-cogs
    5 replies
    why?
    Phil Varner
    @philvarner
    Phil Varner
    @philvarner
    Although, one open question now that OGC Part 3 has the changes we recommended is if we need our own conformance classes, or if we should reuse the OGC ones. I'm leaning to re-using the OGC ones.
    2 replies
    YuanBin
    @manyuanbin
    how to contribute to STAC?
    Chris Holmes
    @cholmes
    Welcome @manyuanbin! Would be great for you to contribute to STAC. If you're looking to make a change to the spec itself then see https://github.com/radiantearth/stac-spec/blob/master/CONTRIBUTING.md
    Most of the activity these days is in the 'extensions', see https://github.com/stac-extensions/stac-extensions.github.io
    Right now the spec itself is pretty mature, so if you're looking to contribute more broadly to the STAC ecosystem you can see https://github.com/stac-utils/stac-ecosystem for ideas, or work on one of the projects implementing STAC.
    lainiewright
    @lainiewright
    10 replies
    Fabian Schindler
    @constantinius
    Is this the channel where the Python stactools and its extensions are discussed? If so, I'd like to draw attention to this PR to add Level-1C support for the sentinel2 extension.
    2 replies
    Fabian Schindler
    @constantinius
    sachin kn
    @sachinlionel
    which database is recommended for stac-api?
    1 reply
    Phil Varner
    @philvarner
    There's an alternate proposal out for CQL JSON, and the OGC API team is seeking feedback opengeospatial/ogcapi-features#601
    Phil Varner
    @philvarner
    Had hoped to get STAC API beta.4 out this week, but I've been blocked on getting approval for the Filter Extension updates radiantearth/stac-api-spec#202 and Collections conformance class radiantearth/stac-api-spec#210 -- please review this if you have time!
    Marc Pfister
    @drwelby
    Any work yet on storing information about classified rasters in STAC? Primarily representing maps of values to class names.
    2 replies
    Matthew Hanson
    @matthewhanson
    Published pystac-client 0.3.0-beta.1, updated docs: https://pystac-client.readthedocs.io/en/latest/
    Yves Moisan
    @ymoisan
    In my inbox this morning : The just approved OGC API - EDR (Environmental Data Retrieval) "is not just for accessing ‘environmental’ data but can also support more general spatio-temporal data." Sounds like a STAC API to me.
    1 reply
    Daniel Silk
    @dwsilk
    Hi all - we've got a question about how to summarise Item and Item Asset created/updated datetimes at the Collection level. It's in Discussions on the STAC Spec repo: https://github.com/radiantearth/stac-spec/discussions/1156 (would it be better to just ask here instead?)