You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on some caching code for my own project using owslib, i was puzzled to see two requests on the remote service.. and quickly figured out it was owslib itself doing two requests, for the creation of a single object.
>>> from owslib.wfs import WebFeatureService
>>> x = WebFeatureService('https://xxx/wxs/geor_loc/ows', version='1.1.0')
reproducible with owslib 0.31.0 (the second set of requests) and 0.27.2 (the version shipped with debian 12, and first set of requests) - i dont see the same behaviour with WMS 1.3.0 or 1.1.1, so that seems specific to WFS, and happens for WFS 1.1.1 and 2.0.0.
after a quick look at the code, i see https://github.com/geopython/OWSLib/blob/master/owslib/feature/wfs110.py#L207 and i wonder if the 'is redundant' comment is about that weird behaviour of if it comes from elsewhere, but doing two requests is suboptimal, especially if generating the capabilities document is expensive serverside.
The text was updated successfully, but these errors were encountered:
@landryb - I think this may be the same issue as #520 with possible fix in #548 (although I've not tested this yet).
oh great, i can confirm #548 fixes the issue, tested it by locally removing the __new__ method only in wfs110.py, creating a WFS object with version='1.1.0' yields a single getcapabilities request, while doing the same call with version'=2.0.0' yields two getcapabilities requests.
While working on some caching code for my own project using owslib, i was puzzled to see two requests on the remote service.. and quickly figured out it was owslib itself doing two requests, for the creation of a single object.
triggers this in the remote service accesslog
reproducible with owslib 0.31.0 (the second set of requests) and 0.27.2 (the version shipped with debian 12, and first set of requests) - i dont see the same behaviour with WMS 1.3.0 or 1.1.1, so that seems specific to WFS, and happens for WFS 1.1.1 and 2.0.0.
after a quick look at the code, i see https://github.com/geopython/OWSLib/blob/master/owslib/feature/wfs110.py#L207 and i wonder if the 'is redundant' comment is about that weird behaviour of if it comes from elsewhere, but doing two requests is suboptimal, especially if generating the capabilities document is expensive serverside.
The text was updated successfully, but these errors were encountered: