OWSLib
OWSLib copied to clipboard
geopython
OWSLib is a Python package for client programming with Open Geospatial Consortium (OGC) web service (hence OWS) interface standards, and their related content models.
Sorry I'm not really at ease to the use of github. Anyway, for my purpose I've found useful to define a proxy in the WMS url request. I've modified, locally...
* make sure `accessconstraints`, `useconstraints` and `identifier` values are picked when available as `gmx:Anchor` instead of `gco:CharacterString` * extend `resourcelanguage`, MI_Instrument Some background info: https://www.ngdc.noaa.gov/wiki/index.php/Character_String_Extended_Types - """ With the gmx...
we received an error report about a failing layer on our service by a user using owslib in the end it appeared the user added the layer to the owslib...
This is implementation of WCPS ProcessCoverages function.
* Version: `OWSLib = '0.25.0'` My `getfeature` query: ```python response = wfs2.getfeature( typename=name, filter=filter_query, propertyname=['geom', 'ID'], method='GET', outputFormat='json' ) ``` With `method='GET'` it works fine but when `method='POST'` is passed...
This PR solves https://github.com/geopython/OWSLib/issues/813 I would be happy if these changes could be merged. Let me know if further work needs to be done.
Some WFS servers to not define a `name` attribute in the `` tag. in the response of `DescribeFeatureType`. In addition, the `` has no `type` attribute then. Example URLs: *...
I've written a bit of python to get information on a WFS service. OWSLib's _construct_schema fails if there is no schema in the layer name: ``` C:\>python ows2gm.py -wfs "https://SDMDataAccess.sc.egov.usda.gov/Spatial/SDMWGS84Geographic.wfs"...
found this bug when requesting `DistributedSearch` via pycsw with `federatedcatalogues` config. Just as follows: ``` File "/home/bk/vpy_csw/lib/python3.9/site-packages/owslib/catalogue/csw3.py", line 225, in getrecords if xml.startswith(b'
I noticed when making GetCapabilities requests against WFS 2.0.0 services that the keywords list for a FeatureType was empty. The cause was the `ContentMetadata` class searching for `wfs:Keywords` rather than...
