ENOENT issue when writing shapefile about ogr2ogr HOT 8 CLOSED

To follow up with some more info:

After I get the ENOENT errors such as:
ENOENT, readdir '/tmp/ogr_4b3b30097b2'

If I navigate to the /tmp folder, I see a similarly-named file, but the last number is 1 number less than the file listed in the ENOENT message. For example, I see a handful of ogr_ files, and the last in the list is ogr_4b3b30097b1.json.

I've noticed this the last few times I've tried running the GeoJSON to shapefile writer.

Not sure if this is part of the puzzle, but it seems like it's looking for a file that's one character different than what's actually there. Is it possible that the auto name generator is running 2 times?

Thanks

from ogr2ogr.

Hmm... are you using the same version of gdal in the amazon env as in your local env?

from ogr2ogr.

mmm. gdal-config on my vm reports 1.7.3.
gdal-config on my S3 server reports 1.9.0.

What version of GDAL did you develop against?

from ogr2ogr.

Travis is testing against 1.9.2 currently and I run 1.10.1 locally. The API's for the command line tool have been pretty consistent though. Does any file/workflow suffer the same fate regardless of environment?

Another thing to try is listening to the 'ogrinfo' event to see what is happening while trying to do the conversion. It may be that the underlying ogr2ogr command is failing and unable to do the conversion:

var ogr = ogr2ogr(myGeoJSONObject).format('ESRI Shapefile')
ogr.on('ogrinfo', console.error) // any warning, errors, info from ogr2ogr gets dumped here

var shapefile = ogr.stream();

from ogr2ogr.

Thanks for the tip. However, trying the code above yields:
TypeError: Object # (Ogr2ogr) has no method 'on'

Also, the process works fine on a Winodws environment, and an Ubuntu VM...which is why I assumed it was some sort of environmental or permissions problem.

Also, not sure if it matters, but I also have Mapnik 2.2 installed, which relies on GDAL as well.

from ogr2ogr.

are you running the latest version of ogr2ogr module? on('ogrinfo') was recently added

from ogr2ogr.

Thanks for the ideas. Yes, I was running the latest version. There must have been a GDAL version conflict with Mapnik 2.2.0 (which loads 1.9).

In my project, instead of installing GDAL from the ppa (sudo add-apt-repository ppa:ubuntugis/ppa), I just installed the package (sudo apt-get install gdal-bin).

Works fine now.

Thanks!

from ogr2ogr.

Glad to hear it's working now! Thanks for the update.

On Jan 25, 2014, at 2:44 PM, Ryan Whitley [email protected] wrote:

Thanks for the ideas. Yes, I was running the latest version. There must have been a GDAL version conflict with Mapnik 2.2.0 (which loads 1.9).

In my project, instead of installing GDAL from the ppa (sudo add-apt-repository ppa:ubuntugis/ppa), I just installed the package (sudo apt-get install gdal-bin).

Works fine now.

Thanks!

—
Reply to this email directly or view it on GitHub.

from ogr2ogr.