[gdal-dev] Calling ogr2ogr via proxy with ntlm authentication

Dirk.Pispers at STADT-KOELN.DE Dirk.Pispers at STADT-KOELN.DE
Mon Aug 10 23:55:48 PDT 2020


Dear GDAL-List,

we're trying to use an QGIS plugin called XPlanung which imports a gml-file into a PostgreSQL/PostGIS database using ogr2ogr.
On computers with an direct internet connection this works fine, but inside our corporate network all internet traffic runs through a proxy with ntlm authentication.
In this case the external references in the input gml-file can't be resolved.

The ogr2ogr call looks like this:
cmd.exe /C  ogr2ogr.exe -f PostgreSQL PG:"host=xplanung_test dbname=xplanung_test port=5436 user=xplanung_test_admin password=xxxxxxxxxxxxxxxxx" -s_srs EPSG:25832 -t_srs EPSG:25832 -lco SCHEMA=import_test -lco LAUNDER=NO -nlt CONVERT_TO_LINEAR -oo XSD=C:\Users\Pispers\AppData\Roaming\QGIS\QGIS3\profiles\default\python\plugins\xplanung\schema\5.2/XPlanGML.xsd -oo REMOVE_UNUSED_LAYERS=YES GMLAS:C:/Eigene/QGIS/XPlanung/FooBar03.gml

I'm using GDAL 3.0.4 inside QGIS 3.10.4 an Windows 10.
In the GDAL documentation I found gdal http options like GDAL_HTTP_PROXY and GDAL_PROXY_AUTH, but I couldn't find out in what way I can integrate them in my ogr2ogr call.

I hope anyone can give me a hint or posts an example call.

Thanks and best regard fron germany

Dirk Pispers


________________________________

Monatlich aktuelle Informationen Ihrer Stadtverwaltung in unserem Newsletter! Newsletter Anmeldung<https://www.stadt-koeln.de/service/onlinedienste/newsletter-anmeldung?para=allgemein>

________________________________

[https://styleguide.bundesregierung.de/resource/blob/72496/1760346/6d7f611945ca42908c50804510c5335b/breg-vorschaubild-01-unterstuetzt-842x595px-jpg-srgb-v01-data.png]<https://www.bundesregierung.de/breg-de/themen/corona-warn-app>

[https://www.stadt-koeln.de/images/footer_wahlhelferaufruf2020.jpg]<http://www.wahlhelfer.koeln/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20200811/8ced445d/attachment.html>


More information about the gdal-dev mailing list