Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Tom Landry
    @Tom_Landry__twitter
    We'll start by completing the Testbed task, then pushing Twitcher to @cehbrecht for review
    But yes, it make sense in a WPS server of course. Then having WPS 2.0 clients... where would that be
    OWSlib maybe?
    @allixender we could not test OWS Context in the current testbed. Participants put most of their efforts in a combination of JSON process descriptions and CWL workflow and application descriptors
    In other words, plan changed and it's not our fault :-) Still, you should know that the sponsor, ESA, is still interested to see OWS Context move forward, so it's a matter of time... probably
    Tom Kralidis
    @tomkralidis
    Good idea. Yes OWSLib has a WPS client which we could update accordingly.
    Tom Kralidis
    @tomkralidis
    hey @cehbrecht RE: geopython/OWSLib#528, I dunno. Call me old fashioned but changing two files, committing the change and cutting a tag seems straightforward with less moving parts and no dependencies. I could be missing a bigger rationale, however
    MacPingu
    @cehbrecht

    Well, you are used to the workflow ;) The reasoning is to have a consistent release (version, tag, trigger docs build?, …) that can be done by more people. It does not hurt, it is a dev dependendy. We have started to use it for all our libraries … Ouranos (Montreal) was first ;)

    Either way, we should document the release process … no matter the tool.

    Here is an example where it came from (python cookiecutter template):

    Tom Kralidis
    @tomkralidis
    I can document the workflow in another PR and perhaps we can compare? I admit things are not very transparent. I'll make a point to do this in the next days
    MacPingu
    @cehbrecht
    We could have a contributing guideline similar to the one generated by the cookiecutter template:
    https://github.com/Ouranosinc/xclim/blob/master/.github/CONTRIBUTING.rst
    Tom Kralidis
    @tomkralidis
    @/all I'd like to update README.rst, CHANGES.rst and AUTHORS.rst to Markdown (.md) files. Any thoughts/objections? I can submit a PR on this later today.
    Tom Kralidis
    @tomkralidis
    @cehbrecht I've added the current release steps in geopython/OWSLib#535
    pretty simple (even I can do it :) )
    Tom Kralidis
    @tomkralidis
    hey @/all anyone else having issues with pytest these days? pydap/pydap#182
    MacPingu
    @cehbrecht
    tomkralidis @tomkralidis watches Travis
    MacPingu
    @cehbrecht

    also noaa service are not available:
    http://www.ngdc.noaa.gov/geoportal/csw

    We use it for test-data but our service_ok check is not intelligent enough to notice.

    Tom Kralidis
    @tomkralidis
    here's hoping :)
    MacPingu
    @cehbrecht
    @tomkralidis would you be happy to make a owslib 0.17.1 release? It includes mostly fixes for wps and wms.
    Tom Kralidis
    @tomkralidis
    @cehbrecht sure, I will do today, does that work?
    MacPingu
    @cehbrecht
    @tomkralidis thanks :)
    Tom Kralidis
    @tomkralidis
    0.17.1 released, sorry for the delay. No email given it's a bugfix rel
    MacPingu
    @cehbrecht
    @tomkralidis thanks :)
    Tom Kralidis
    @tomkralidis
    Hey all: FYI geopython/OWSLib#565
    tonyVeco
    @tonyVeco
    Hi, everyone
    i am quite new in using OWSLib so I have some doubt or questions about it
    I would like to use it with WCS standard, and I would like to know if it is possible to add a colortable parameter when building a query with the getCoverage method
    i mean for example when setting the format as png image
    Jeremiah Cooper
    @Coop56
    Hey all, I noticed that the Travis CI tests were failing because Python 3.4 is no longer supported. PR to remove it is up at geopython/OWSLib#570
    We should also consider adding Python 2.7 and 3 to the classifiers. I can prepare a PR for that as well if there are no objections. Right now caniusepython3 reports that owslib does not support Python 3 because the classifier isn’t there.
    Tom Kralidis
    @tomkralidis
    hi @/all for the OSGeo Code Sprint in a couple of weeks I put up some items for various geopython projects: https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2019#Project_Plans . Please feel free to add/update. I didn't put anything for OWSLib per se, but will anyone be there with interest in OWSLib?
    MacPingu
    @cehbrecht
    @tomkralidis What about an owslib 0.17.2 patch release?
    geopython/OWSLib#583
    Tom Kralidis
    @tomkralidis
    @cehbrecht will do
    Tom Kralidis
    @tomkralidis
    I will cut 0.18.0 given the authentication work by @eric-spitler
    I'll have 0.18 out shortly

    what do folks think about dropping Python 2 support altogether? Areas:

    • drop from Travis
    • drop all usage of six and __future__

    Thoughts? Do none/one/both?

    Tom Kralidis
    @tomkralidis
    MacPingu
    @cehbrecht

    @tomkralidis thanks :)

    +1 for drop Python 2.x altogether. Probably starting by drop from Travis first and converting modules one by one.

    Tom Kralidis
    @tomkralidis
    @cehbrecht I've put forth geopython/OWSLib#584 as a WIP PR that we can work towards. the remove-python2 branch is part of the OWSLib repo (not my fork) so we can all push to it (not a small effort)
    MacPingu
    @cehbrecht
    @tomkralidis ok. I can drop six and clean up the wps module. Also we might want to enable python 3.7 support.
    Tom Kralidis
    @tomkralidis
    +1
    Tom Kralidis
    @tomkralidis
    I think 3.7 is there in .travis.yml?
    Tom Landry
    @Tom_Landry__twitter
    Nothing to add really, just wanted to say hello.
    Jachym Cepicky
    @jachym
    hi all, can someone please have a look at geopython/OWSLib#610
    Jachym Cepicky
    @jachym
    thanks @cehbrecht
    Just van den Broecke
    @justb4
    Q: regarding #587 do you agree we need headers to be able to be passed for all services (not just WMS)? e.g. for auth username/password (Basic Auth) is too limiting. We need e.g. Bearer Token auth. "We"=geopython/GeoHealthCheck#9. Additional problem: GHC only supports Python2 now, and OWSLib Python3 starting 0.18.0, or is a 0.17.2 branch/release still possible?
    Just van den Broecke
    @justb4
    Ok, started solving #587 for at least WMS,WFS,WMTS,TMS: see PR geopython/OWSLib#613.
    Just van den Broecke
    @justb4
    Issue #614 will IMHO break TMS Service for any usage in v0.18.0. Should be fixed with my PR #615, though there is some overlap with PR #613.
    Just van den Broecke
    @justb4
    @/all ahem, anyone has time to look into #587 with PR #613 and #614 with PR #615 ?