Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Chris Holmes
    @cholmes
    Any word on a 1.0.1 pystac release? I'm eagerly waiting on it to unblock a stactools issue to help me make a Planet catalog.
    4 replies
    Jon Duckworth
    @duckontheweb
    PySTAC v1.0.1 is out (https://pypi.org/project/pystac/1.0.1/).
    Jon Duckworth
    @duckontheweb
    PySTAC v1.1.0 is up on PyPi (https://pypi.org/project/pystac/1.1.0)
    4 replies
    Pete Gadomski
    @gadomski
    stactools v0.2.1 (first release in the v0.2 line) is out: https://pypi.org/project/stactools/
    1 reply
    Chris Holmes
    @cholmes
    Any tweets for these? Please do, and I can amplify, or let me know if you want me to do it.
    Rob Emanuele
    @lossyrob
    I usually tweet about pystac, but happy for others to take on some of the sqwakin. @gadomski want to get some retweets?
    2 replies
    Chris Holmes
    @cholmes
    Thanks for the stactools tweet @gadomski. I think we still need the PySTAC 1.1 one. @duckontheweb?
    5 replies
    Tom Augspurger
    @TomAugspurger
    FYI @matthewhanson I ran all of the examples at https://github.com/microsoft/planetarycomputerexamples with pystac-client=0.2.0rc1 and things worked fine.
    Matthew Hanson
    @matthewhanson
    awesome, thx @TomAugspurger !
    Phil Varner
    @philvarner
    Now that the conformance class problem with stac-fastapi is resolved, I can run the validator against it. This issue with /collections returning the wrong content is a pretty major problem that could use some attention stac-utils/stac-fastapi#108
    Phil Varner
    @philvarner
    I just filed several other issues against stac-fastapi based on running the validator
    Could someone who's involved with stac-fastapi give me permission to assign issues to myself? I'd like to do some of the fixes I filed.
    Rob Emanuele
    @lossyrob
    just sent an invite with triage role, I think that should work
    Tom Kralidis
    @tomkralidis

    hi all: using pystac-client 0.2.0, I’m trying to validate the pycsw STAC API support, and getting the following:

    $ stac-client collections http://localhost:8001
    ConformanceClasses.COLLECTIONS not supported

    Any idea how to find out more about this error? Passing the —logging switch doesn’t seem to work. Thanks in advance.

    Angelos Tzotsos
    @kalxas

    also trying to test pycsw stac api implementation with pystac-client and get this error:

    AttributeError Traceback (most recent call last)

    <ipython-input-26-d7471b35385f> in <module>
    ----> 1 for item in mysearch.items():
    2 print(item.id)

    AttributeError: 'ItemSearch' object has no attribute 'items'

    Angelos Tzotsos
    @kalxas
    ok, got past that error by using the get_items() function, the examples need some updating
    Matthew Hanson
    @matthewhanson
    @kalxas documentation is currently being updated, sorry about that!
    @tomkralidis Conformance errors happen if the API doesn’t advertise the correct conformance class. For collections, if the /collections endpoint is supported it will use that to get the collections, otherwise it defaults back to following all the child links from root to get all the collections. In that case it should still work as it uses the fall back, but I will test again.
    You can ignore conformance classes when you open the client with the “ignore_conformance=False” keyword to Client.open(). It will then assume all conformance classes are supported (which will throw errors if they aren’t of course).
    sorry for the status of the docs, working on getting it all cleaned up. Also, let me know if you have any suggestions regarding conformance class checking behavior.
    Angelos Tzotsos
    @kalxas
    thanks @matthewhanson
    Tom Kralidis
    @tomkralidis
    thanks @matthewhanson . Here’s our landing page, with conformance classes. Not sure what’s missing/out of date, however, will dig.
    Matthew Hanson
    @matthewhanson
    pystac-client is looking for "http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/core” to see if the /collections endpoint is supported….clearly there’s a bunch of this conformance stuff to still sort out, and maybe I need to be checking for ogcapi-commons classes.
    All of the standard STAC API implementations out there (stac-fastapi, stac-server, cmr-stac) have been using the same classes, see the Microsoft Planetary Computer as example:
    https://planetarycomputer.microsoft.com/api/stac/v1
    @tomkralidis
    Angelos Tzotsos
    @kalxas
    ah I see
    makes sense, records is also based on features so it should be there I guess
    Matthew Hanson
    @matthewhanson
    @kalxas , so you mean that an ogcapi-records server should include ogcapi-features conformance classes?
    Angelos Tzotsos
    @kalxas
    I have to confirm with the SWG
    we have refactored the records spec recently
    Tom Kralidis
    @tomkralidis
    thanks @matthewhanson and @kalxas. IMHO the conformance dependency architecture needs to be clarified. i.e. if OARec normatively extends OAFeat then are the OARec conformance classes enough (OAFeat) implied? Food for thought.
    1 reply
    Angelos Tzotsos
    @kalxas
    hi @matthewhanson I am trying to get a bbox filter to work against our pycsw implementation
    when I do this with pystac-client:
    mysearch = catalog.search(collections=['metadata:main'], bbox=[13.9,37.0,15.1,37.9], max_items=10)
    I see in the server logs this request happening:
    which results in empty result set
    Phil Varner
    @philvarner
    the problem is that the bbox is being sent with the enclosing [ and ], whereas it should only be a CSV string of 4 or 6 numbers
    but I don't see how that code would cause that problem, since it should convert the list into a tuple
    Matthew Hanson
    @matthewhanson
    @kalxas does your server support POST requests? The default for pystac-client should be POST, in which case the bbox should be an array.
    For GET requests, pystac-client converts arrays to comma-delimited strings here: https://github.com/stac-utils/pystac-client/blob/main/pystac_client/item_search.py#L204
    Angelos Tzotsos
    @kalxas
    @matthewhanson, @tomkralidis has added POST support recently
    the issue has been fixed, it was a bug on our side
    Jon Duckworth
    @duckontheweb
    @matthewhanson It would be good to get your review on stac-utils/pystac#590 before merging to make sure it covers your needs from stac-utils/pystac#589
    Matthew Hanson
    @matthewhanson
    @duckontheweb thanks for the ping, I really need to clean up my filters on GitHub notofications! I’ll try out this branch in pystac-client by deleting my override of the from_dict function
    Jon Duckworth
    @duckontheweb

    @duckontheweb thanks for the ping, I really need to clean up my filters on GitHub notofications! I’ll try out this branch in pystac-client by deleting my override of the from_dict function

    Thanks!

    Jon Duckworth
    @duckontheweb
    @lossyrob @bitner @geospatial-jeff This might be an interesting pattern to consider for the pgstac backend in stac-fastapi once PostGIS 3.2 lands: https://blog.crunchydata.com/blog/waiting-for-postgis-3.2-secure-cloud-raster-access
    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
    Fabian Schindler
    @constantinius
    Hi folks! I'd like to draw your attention to this PR for stactools/sentinel2: stactools-packages/sentinel2#11
    It adds support for Level-1C products. I'd like to know if theres something missing or whether it can be merged?
    3 replies
    Pete Gadomski
    @gadomski
    Chris Holmes
    @cholmes
    Hey @lossyrob and @gadomski - I'm contemplating doing a blog post on stactools, since we never actually 'announced' it when it came out. Want to do a Planet blog post on our support of STAC, and so want to reference something that describes it more deeply. Sound good? Anything you want to add? I'm also open to co-author it with one or both of you.
    2 replies
    Chris Holmes
    @cholmes
    @lossyrob & @gadomski - working on the post a bit now. The list of packages at https://github.com/stac-utils/stactools is much less than https://github.com/stactools-packages/stactools-packages.github.io Looks like the latter is auto-generated, which is nice. Wondering if there's any way to sync the auto-generated list? Or it might be best to just provide a link and not try to summarize in the stactools readme?
    3 replies