Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    MacPingu
    @cehbrecht
    @tomkralidis Thanks : 😊
    Tom Kralidis
    @tomkralidis
    @cehbrecht what do you think of moving OWSLib CI from Travis to GitHub Actions?
    MacPingu
    @cehbrecht

    @cehbrecht what do you think of moving OWSLib CI from Travis to GitHub Actions?

    @tomkralidis sounds good :)

    this one test fails
    similar to travis
    Tom Kralidis
    @tomkralidis
    looks like the test needs to be fixed/updated
    David Huard
    @huard
    Hi @tomkralidis, colleagues at CRIM have developed Weaver, a middleware that can expose WPS1.0 services from multiples servers as an aggregated WPS3.0 REST interface. We'd like to start building client services around this in the upcoming year. My question for you is where should this development take place? Is this something that should go in OWSLib as an "experimental" feature, or is there a pygeoapi-client, or you feel it's too early and we should keep this code in birdy for example (our high level OWSLib.wps wrapper)?
    Tom Kralidis
    @tomkralidis
    @huard by WPS3.0 REST interface, do you mean OGC API - Processes?
    David Huard
    @huard
    Yes, I think that's it.
    Tom Kralidis
    @tomkralidis
    so "OAProc” if you will. We are building out the OGC API part of OWSLib in a clean break style in https://github.com/geopython/OWSLib/tree/master/owslib/ogcapi . I would see a processes.py being put there, for example?
    David Huard
    @huard
    Got it, thanks !
    Tom Kralidis
    @tomkralidis
    note that owslib/ogcapi/__init__.py is akin to “OGC API - Common”. And the code is new-ish Python (function annotations, etc.). Looking forward to your improvements/contributions!
    David Huard
    @huard
    No problem. FYI, work on this is not planned short-term, but later in the year. We're still working on the server-side deployment.
    Tom Kralidis
    @tomkralidis
    Great/+1
    check out the recent update we made in pygeoapi for job management, if any of that is helpful
    Tom Kralidis
    @tomkralidis
    @cehbrecht et. al. if possible I’d like to cut a release of OWSLib given the recent 19115-2 enhancements, so 0.22.0. Any objections/comments/considerations?
    Angelos Tzotsos
    @kalxas
    +1
    MacPingu
    @cehbrecht
    +1
    Tom Kralidis
    @tomkralidis
    thanks. 0.22.0 released.
    MacPingu
    @cehbrecht
    @tomkralidis can we make a new release 0.23.0 with the latest fixes? Just wait for this one (or merge it):
    geopython/OWSLib#739
    Tom Kralidis
    @tomkralidis
    sure, feel free to merge if you approve @cehbrecht and we can cut a release. Is there anything driving this one?
    MacPingu
    @cehbrecht

    @tomkralidis I have prepared the release 0.23:
    geopython/OWSLib#744

    Please cut a release 0.23.0. It has a fix for the wcs timeout issue:
    geopython/OWSLib#738

    Tom Kralidis
    @tomkralidis
    thanks @cehbrecht does the fix constitue 0.23.0 or 0.22.1 ?
    MacPingu
    @cehbrecht
    The list of fixes is longer … so I suggested 0.23.0.
    Tom Kralidis
    @tomkralidis
    ok thanks. I will cut 0.23.0 tomorrow.
    MacPingu
    @cehbrecht
    Thanks 😊
    Tom Kralidis
    @tomkralidis
    thank you :) FYI 0.23.0 released.
    MacPingu
    @cehbrecht

    thank you :) FYI 0.23.0 released.

    :thumbsup:

    Paul van genuchteG
    @pvgenuchten
    I'm trying the docs of owslib on ogcapi-records
    image.png
    at records, don't you need to select a collection first? or if there is 1 collection, it will automatically use that one?
    Paul van genuchteG
    @pvgenuchten
    my catalog (https://apps.titellus.net/ogcapi) has 3 collections, how can i indicate to use one of them?
    Paul van genuchteG
    @pvgenuchten
    trying with: w.collection_items(collections[2].name)
    Tom Kralidis
    @tomkralidis
    @pvgenuchten doesn’t work for me:
    >>> from owslib.ogcapi.records import Records
    >>> r=Records('https://apps.titellus.net/ogcapi/')
    Traceback (most recent call last):
      File "<stdin>", line 1, in <module>
      File "/Users/tkralidi/Dev/OWSLib/OWSLib/owslib/ogcapi/records.py", line 23, in __init__
        super().__init__(url, json_, timeout, headers, auth)
      File "/Users/tkralidi/Dev/OWSLib/OWSLib/owslib/ogcapi/features.py", line 23, in __init__
        super().__init__(url, json_, timeout, headers, auth)
      File "/Users/tkralidi/Dev/OWSLib/OWSLib/owslib/ogcapi/__init__.py", line 65, in __init__
        self.title = response['title']
    KeyError: 'title'
    >>> r=Records('https://a
    Paul van genuchteG
    @pvgenuchten
    image.png
    final slash?
    will be an interesting week of interoperability testing :-)
    i used latest from pip (didn't install master)
    Tom Kralidis
    @tomkralidis
    use master. I don’t see the relvant link relations in the landing page. I’m pushing a fix that fixes the title error above (should be optional)
    so then you would do:
    r.collection_items(‘main’) and so on
    Paul van genuchteG
    @pvgenuchten
    it is a work in progress, i'm collecting issues at https://github.com/geonetwork/geonetwork-microservices/issues, but owslib is an interesting way to test drive the api
    i identified that the problem is that we use 'name' as identifier, but it should be 'id', but indeed, alternative is to use one of the links
    Tom Kralidis
    @tomkralidis
    sorry, correction, I do not need to push a fix here (had locally uncommitted code). This works:
    >>> from owslib.ogcapi.records import Records
    >>> r=Records('https://apps.titellus.net/ogcapi/‘)  # traverse the dict here for the collection name you are interested in
    >>> r.collection_items('main')
    Paul van genuchteG
    @pvgenuchten
    but it's nice to see this working
    r = w.collection_items('3b7cf385-435a-49d6-bf23-775b4b573a72', q="test")
    Tom Kralidis
    @tomkralidis
    @cehbrecht FYI #746 is now WIP. Will send a note when ready for review again
    Tom Kralidis
    @tomkralidis
    FYI #746 now ready for review
    Tom Kralidis
    @tomkralidis
    Hi @cehbrecht : we added a CSW 3 client to. master. Any objections to 0.24.0 release? I know we did 0.23.0 recently, but the CSW 3 client is a big feature that we need to ref in downstream tools.
    Angelos Tzotsos
    @kalxas
    +1