Changes between Initial Version and Version 1 of Ticket #3236


Ignore:
Timestamp:
Nov 18, 2009, 1:25:11 PM (11 years ago)
Author:
warmerdam
Comment:

Chaitanya,

Could you review this problem and propose improvements to error out properly at the 2GB mark? Possibly some of the changes will need to be upstreamed by me.

Keep in mind it is important for us to preserve the existing ability to read and write .dbf files much larger than 2GB.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3236

    • Property Keywords Shape added
    • Property Owner changed from warmerdam to chaitanya
    • Property Component changed from Utilities to OGR_SF
    • Property Cc warmerdam added
  • Ticket #3236 – Description

    initial v1  
    22ogr2ogr -f "ESRI Shapefile" -append -update combined_shapefile.shp shapefile_number_n.shp -nln combined_shapefile.
    33
    4 Process is progressing well to the point where the .shp file is reaching 2 GB size. Exact file size then was 2 147 484 604 bytes.  What happens is that ogr2ogr starts to pring these error messages:
     4Process is progressing well to the point where the .shp file is reaching 2 GB size. Exact file size then was 2 147 484 604 bytes.  What happens is that ogr2ogr starts to pring these error messages:
    55ERROR 1: Error in psSHP->sHooks.FSeek() or fwrite() writing object to .shp file.
    66