<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi David,<br>
<br>
On 22/07/10 13:33, David Epstein wrote:
<blockquote cite="mid:1279769608.5736.18.camel@system76-pc" type="cite">
<pre wrap="">Thank you for explaining these details. After converting the PGeo file,
the shapefile dbf is over 2GB. This fails to load into postgres with
both shp2pgsql & ogr2ogr. With the former I get an fseek error & with
the latter:
ERROR 1: INSERT command for new feature failed.
ERROR: new row for relation "parcel_esri_exp" violates check constraint
"enforce_geotype_wkb_geometry"
Do you know if this problem will exist regardless of the source format?
Do I need to divide the geometry, load, and then recombine in postGIS?
I'm certain 2GB is not the largest file people are working with--what do
people do to move between formats?
</pre>
</blockquote>
<br>
I don't know much about the file limitations of shapefiles. The OGR doc
[1] says the following:<br>
<blockquote>"Geometry: The Shapefile format explicitly uses 32bit
offsets and so cannot
go over 8GB (it actually uses 32bit offsets to 16bit words).
Hence, it is is not recommended to use a file size over 4GB."<br>
</blockquote>
So, your file size should not be an issue (assuming you don't use a FAT
file system). I tend to think that something is not right with your
geometries. A search for "violates check constraint
enforce_geotype_wkb_geometry" might give some hints what could be wrong
with your data.<br>
<br>
Regards, Roald<br>
<br>
<br>
</body>
</html>