Opened 10 years ago

Closed 10 years ago

#2721 closed defect (invalid)

gdal_contour fails with 4gig+ file

Reported by: treaves Owned by: pramsey
Priority: medium Milestone:
Component: postgis Version: 2.1.x
Keywords: Cc:

Description

I am attempting to import contour information into a PostGIS-enabled database. I am trying to follow the information on this site: http://wiki.openstreetmap.org/wiki/Contours#Importing_the_SRTM3_data_.28deprecated.29 and am using the script. The page states that srtm_generate_hdr.sh is no longer needed, but, I can find no instructions that do not use this script.

I am importing data from ds.cr.usgs.gov/srtm/version2_1/SRTM1/Region_01 . The first couple of files in that directory import. When the file N38W114.hgt.zip is processed, however, one of the intermediate files created by shp2pgsql starts growing in size, and when it reaches just over four gig, the max file size, it fails. This particular data file isn't the largest that is imported.

So I'm not sure how to troubleshoot were exactly the issue is; I suppose the issue could be with the data file, but, as several other files imported fine, I think the issue may be with shp2pgsql.

Change History (4)

comment:1 by treaves, 10 years ago

It's the shp file that grows & fails. Also, the app does not notice this failure, and continues to try & process the input.

comment:2 by treaves, 10 years ago

RROR 1: Failed to write shape object. File size cannot reach 4294967228 + 808. ERROR 1: Failed to write shape object. File size cannot reach 4294967228 + 808.

These are the actual error messages.

comment:3 by treaves, 10 years ago

Summary: shp2pgsql fails with 4gig+ filegdal_contour fails with 4gig+ file

Sorry, this is gdal_contour, not shp2pgsql.

comment:4 by Bborie Park, 10 years ago

Resolution: invalid
Status: newclosed

gdal_contour and that error are directly from GDAL, not PostGIS. You should ask the GDAL mailing list.

Note: See TracTickets for help on using tickets.