<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi list,<br>
<br>
I'm running GDAL 1.11.1 on an Ubuntu 14.04.1 64-bit system.<br>
<br>
ogr2ogr fails while trying to convert a Feature Class from a rather
huge FileGDB to a PostGIS table. Unfortunately, I have currently no
means to access the original GDB file directly.<br>
It gives this error:<br>
<pre>ERROR 1: Error occured in filegdbtable.cpp at line 659</pre>
Which breaks down to this line of code:<br>
<br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<a class="code"
href="http://fossies.org/dox/gdal-1.11.1/filegdbtable__priv_8h.html#a2386c8f3b2701f62e44b603c048cab4b"
style="color: rgb(70, 101, 162); font-weight: normal;
text-decoration: none; font-family: monospace, fixed; font-size:
13px; font-style: normal; font-variant: normal; letter-spacing:
normal; line-height: 13px; orphans: auto; text-align: start;
text-indent: -53px; text-transform: none; white-space: pre-wrap;
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(251, 252, 253);">returnErrorIf</a><span
style="color: rgb(0, 0, 0); font-family: monospace, fixed;
font-size: 13px; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height: 13px;
orphans: auto; text-align: start; text-indent: -53px;
text-transform: none; white-space: pre-wrap; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline
!important; float: none; background-color: rgb(251, 252, 253);">(nFieldDescLength
> 10 * 1024 * 1024 || nFieldDescLength < 10 );<br>
<br>
<br>
</span>By putting in a debug output I figured that the
"nFieldDescLength" of my feature class is <i>way</i> larger than
the maximum allowed value of 10 MB.<br>
In fact it's something around 1.6 GiB.... :-o (what kind of field
description is *this*...?)<br>
<br>
Does anyone of you have an idea on what exactly the
"nFieldDescLength" is and - more importantly - why it's limited to
10MB and if further increasing this value would do any harm to the
overall process? Is a field description of 1.6 gigs even realistic
at all or is it more likely that I have a corrupt input file in some
way? Can't I opt to just skip the lousy field description import and
still import what I'm interested in - the <i>data</i> itself?<br>
<br>
Apparently there was already a bug ticket for this problem, which
led to increasing the max. value from 1 to 10 MB [1]<br>
It seems to me this might also be related to the "big file support
problem" [2] which I thought was resolved in version 1.11.1 [3].<br>
<br>
Any help or workaround suggestions are appreciated! <br>
Otherwise I'll have to try if the proprietary ESRI driver can handle
this... (not tested yet).<br>
<br>
Many thanks and best regards,<br>
Matthias<br>
<br>
--<br>
<br>
[1] - <a class="moz-txt-link-freetext" href="https://trac.osgeo.org/gdal/ticket/5660">https://trac.osgeo.org/gdal/ticket/5660</a><br>
[2] - <a class="moz-txt-link-freetext" href="https://trac.osgeo.org/gdal/ticket/5615">https://trac.osgeo.org/gdal/ticket/5615</a><br>
[3] - <a class="moz-txt-link-freetext" href="https://trac.osgeo.org/gdal/wiki/Release/1.11.1-News">https://trac.osgeo.org/gdal/wiki/Release/1.11.1-News</a><br>
</body>
</html>