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
    @huard there is a demo for ogcapi-processes now:
    https://global.gotomeeting.com/join/978960909
    Francesco Bartoli
    @francbartoli
    but I’m a too much early fan to be considered as an honest opinion 😁
    paul van genuchten
    @pvgenuchten
    Hi, I'm looking at qgis metasearch for oarec, i noticed the oarec implementation differs quite a bit from the csw implementation, one aspect is even conflicting: CatalogueServiceWeb stores its search results at self.catalog.records, where oarec has a method at self.records(). What is your view on this, the goal is to aligns these implementations at some point, or should be considered to be differently, since the nature of the service is quite different?
    Tom Kralidis
    @tomkralidis
    I would keep these distinct, given OWSLib’s OARec support (like OGC API in general) is a clean break.
    David Huard
    @huard
    Hi @tomkralidis , I'm struggling to understand how reconcile how pygeoapi processes execution works with the schemas defined in ogcapi-processes. The hello-world process in pygeoapi requires inputs that do not seem to match the schema defined in "InlineOrRefData" (id, type).
    Tom Kralidis
    @tomkralidis
    hi @huard the OAProc implementation is draft as we await changes made to OAProc proper. We do need to revisit what the spec looks like today
    David Huard
    @huard
    So I can safely assume the OAProc is the latest state of the spec, and the various implementations might be behind ? In terms of client development, I assume it's best for us to stay in sync with the spec, and not worry too much about test server failures?
    Tom Kralidis
    @tomkralidis
    Probably, yes
    Alex Kmoch
    @allixender

    Hi folks, just reading https://github.com/opengeospatial/ogcapi-features/tree/master/implementations

    The SpatioTemporal Asset Catalog (STAC) specification, more precisely the STAC API specification, is based on OGC API Features. Thus STAC API is a superset of OGC API - Features - Part 1: Core, in that OGC API Features defines many of the resources that STAC uses. A STAC API should be compatible and usable with OGC API Features clients and a STAC server should also be a valid OGC API Features server.

    And owslib can already read oas30 features, right. Could I actually read a stac catalogue with owslib?
    Tom Kralidis
    @tomkralidis
    I've never tested it. Not sure it will work with STAC-Catalog, but I suppose STAC API could work.
    Tom Kralidis
    @tomkralidis
    @cehbrecht FYI I’d like to cut 0.24 soon. Any objections? There are some CSW and OGC API updates that would be valuable to get out there.
    Angelos Tzotsos
    @kalxas
    :+1:
    MacPingu
    @cehbrecht
    +1
    Tom Kralidis
    @tomkralidis

    @cehbrecht I’ve cut 0.24.0 and am having issues building the docs:

    (OWSLib) (base) tkralidi@maui:~/Dev/OWSLib/OWSLib-release/docs$ make html
    sphinx-build -b html -d build/doctrees/en   -c . -A language=en -D language=en -A target= -A languages='en  ' en build/html/en
    Running Sphinx v4.0.0
    loading translations [en]... done
    building [mo]: targets for 0 po files that are out of date
    building [html]: targets for 12 source files that are out of date
    updating environment: [new config] 12 added, 0 changed, 0 removed
    reading sources... [ 83%] notebooks/examples/wms                                                                                                                                     
    Notebook error:
    NoSuchKernel in notebooks/examples/wms.ipynb:
    No such kernel named python3
    make: *** [html] Error 2

    Any idea?

    Tom Kralidis
    @tomkralidis
    for now I’ve commented out the notebooks in the docs to complete the release.
    MacPingu
    @cehbrecht
    @tomkralidis I also have issues with sphinx 4.0 … restricting it to <4.0 make it work again: geopython/pywps#608
    But needs to be solved for sphinx >= 4.0.
    I open an issue on owslib.
    Tom Kralidis
    @tomkralidis
    thanks @cehbrecht
    Tom Kralidis
    @tomkralidis
    thanks for the heads up on ipykernel @cehbrecht ; docs now updated.
    MacPingu
    @cehbrecht

    thanks for the heads up on ipykernel @cehbrecht ; docs now updated.

    👍

    Tom Kralidis
    @tomkralidis
    FYI I cut a bugfix release 0.24.1 to address a CSW issue found on integration testing.
    MacPingu
    @cehbrecht

    FYI I cut a bugfix release 0.24.1 to address a CSW issue found on integration testing.

    :thumbsup:

    Angelos Tzotsos
    @kalxas
    :+1:
    David Huard
    @huard
    I fear this is a stupid question, but I can't find references in the OWSLib documentation related to Point or Polygon objects (which would be inputs to WFS filter objects for example). What is the preferred way to define those in OWSLib ?
    David Huard
    @huard
    Tom Kralidis
    @tomkralidis
    @kalxas are we using https://github.com/geopython/OWSLib/blob/master/etc/debian/control as part of UbuntuGIS/Debian?
    Angelos Tzotsos
    @kalxas
    this needs to be updated
    Tom Kralidis
    @tomkralidis
    ok. I’ve opened #785 to help track
    Tom Kralidis
    @tomkralidis

    looks like we’re having CI failures on the FES2 tests: https://github.com/tomkralidis/OWSLib/runs/3014122595?check_suite_focus=true#step:6:355

    @huard any idea?

    David Huard
    @huard
    Nothing useful. Other "live" tests in the test suite use "service_ok" to check if the site is up, but it didn't work on the link I used (service_ok returned False even though the request completed). Options would be to find a reliable WFS server we can test on, fix service_ok to the test is skipped if the server is down, or just disable the test. Thoughts ?
    David Huard
    @huard
    Is there a date planned for the next release ? I'd need one to be able to use the new WFS spatial filtering features. Also, there seems to be a couple of other bug fix PRs that could be merged and bundled with the next release.
    Tom Kralidis
    @tomkralidis
    +1 @huard. I’d like to cut 0.25.0 tomorrow (Monday 23 August). @cehbrecht thoughts?
    Angelos Tzotsos
    @kalxas
    +1
    MacPingu
    @cehbrecht

    +1 @huard. I’d like to cut 0.25.0 tomorrow (Monday 23 August). @cehbrecht thoughts?

    +1

    Tom Kralidis
    @tomkralidis

    0.25.0 released. Thanks everyone for continued support and contributions!

    https://twitter.com/tomkralidis/status/1429783276596629511

    MacPingu
    @cehbrecht

    0.25.0 released. Thanks everyone for continued support and contributions!

    https://twitter.com/tomkralidis/status/1429783276596629511

    :thumbsup:

    David Huard
    @huard
    Thanks !