3

This is my command, which was working OK yesterday:

ogr2ogr -f "GeoJSON" ../geojson/myfile.geojson ../data/gml/myfile.gml 
  -s_srs EPSG:27700 -t_srs EPSG:4326

The output is this: 

ERROR 1: Failed connect to 192.168.4.18:8181; Operation timed out

I'm baffled, why would ogr2ogr need to connect anywhere?

Richard
  • 3,289
  • 6
  • 35
  • 66
  • 1
    GML schema check? – Nathan W Mar 17 '14 at 23:24
  • But then why would it be connecting to somewhere on the local network? And, how can I fix this? – Richard Mar 17 '14 at 23:25
  • No idea just stabbing in the dark at this point. Never seen it do that before. – Nathan W Mar 17 '14 at 23:35
  • 1
    7 years later and my copy of ogr2ogr giving ERROR 1: Failed to connect to 192.168.4.19 which is not a network that I've configured. I've search the source code for the text string, but see nothing. The command does eventually work, but delays everything until it timeouts. – bendecko Jul 31 '21 at 06:55

1 Answers1

1

My ogr2ogr is doing this on a .gml to .geojson conversion.

I was baffled too (see comment a while back).

I've just worked out where the IP address is coming from. It seems ogr2ogr is trying to load the .xsd file specified in the .gml header.

enter image description here

As I said before, the process does complete successfully after a timeout. Alternatively, you could clean the input files prior to processing.

Kadir Şahbaz
  • 76,800
  • 56
  • 247
  • 389
bendecko
  • 128
  • 4