On mardi 12 mai 2020 21:21:30 CEST Rahkonen Jukka (MML) wrote: > Hi, > > 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".
Hum, normally there's code to handle that in the driver. And even a test (against a stub server). Are you using GDAL 3.1 / master ? If so, how can I replicate that ? -- Spatialys - Geospatial professional services http://www.spatialys.com
_______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
