[gdal-dev] OAPIF and apikey
Rahkonen Jukka (MML)
jukka.rahkonen at maanmittauslaitos.fi
Tue May 12 14:21:30 PDT 2020
I wonder how I could deal with an OGC API Features service that requires to use apikey as an extra parameter in each request. First step is easy because I can just add the apikey parameter to the URL of the landing page (?api-key=xxxyyyzzzkkk) but the link to collections in the document that is returned comes without the apikey and ogrinfo and og2ogr are using the link as is. Result is a "HTTP 401 not authorized".
OAPIF supports USERPWD and I found that various vsi systems have service specific configuration options https://gdal.org/user/virtual_file_systems.html. WFS driver https://gdal.org/drivers/vector/wfs.html supports UserPwd and COOKIE. WMS driver supports also UserPwd but I did not find any example of concatenating base URLs with extra parameters.
I think that the WMS driver could also benefit from extra parameters which would be added to GetMaps because WMS servers support quite nice features with their own vendor options.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the gdal-dev