Hi,
Although a bit annoying, you can probably just ignore the warnings
emitted by ./autogen.sh with autoconf 2.71, and run ./configure right
behind, without trying autoupdate
I've a clean up in https://github.com/OSGeo/gdal/pull/4626 that results
in ./autogen.sh not emitting warning with aut
Hi,
GDAL has the internal default of 80 characters. GDAL users do not really need
other options because fields are automatically expanded when longer strings are
appended afterwards but if the shapefile is used in some other software it does
happen that it is impossible to insert long strings b
Hi Jukka,
works perfectly, thanks!
so no default options to impose the field length but it is alterable after
Cheers!
Matteo
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Hi,
The best I can suggest to do by using just GDAL utilities is to run this kind
of ogrinfo command for each text field that you have in the shapefile schema:
ogrinfo my_shape.shp -sql "alter table my_shape alter column STRING_1 TYPE
character(254)"
(right, the max length is 254).
-Jukka Rah
Hi Jukka,
The strings fields are created by default with width 80. If there are longer
strings in the data the width is automatically extended up till 255 characters
that is the maximum that dBase format supports. If strings are shorter than 80
charaters it is possible to use RESIZE and shrin
On 10/7/21 1:46 PM, Rahkonen Jukka (MML) wrote:
> Hi,
>
> If you are asking the same question in gis.stackexchange please wait some
> minutes if somebody happens to answer you before sending mail to gdal-dev. Or
> vise versa. Crossposting in the long run will not help you to get answers
> faste
I've had a quick look at what it would take to upgrade for autoconf >=
2.70 compatibility, and it is beyond what I am ready to invest,
especially given that part of the code is on the road to be phased out
due to the switch to cmake. Your best/only option is to uninstall your
apt supplied autoconf
