Hi,
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 shrink the wi
Hi Even,
If you add -lco RESIZE=YES fields will be resized to their minimum size.
See https://gdal.org/drivers/vector/shapefile.html#layer-creation-options
yep I see. I also read
* String fields without an assigned width are treated as 80 characters
does it mean that if a field is set as TEX
My apologies on typing the link and adding an 's' to the name. Should be
ftp://ftp.coast.noaa.gov/tmp/kwaters/autocad_issue.zip
Thanks for the tip on the configuration option! I agree about the ideal
solution.
Kirk
On Thu, Oct 7, 2021 at 3:59 PM Even Rouault
wrote:
> Kirk,
>
> the download li
Kirk,
the download link doesn't work.
GDAL 3.3 will use geotiff 1.1 conventions by default when a compound CRS
is used. You may try adding -co GEOTIFF_VERSION=1.0 to force GeoTIFF 1.0.
When reading a GeoTIFF 1.1 file, GDAL will report the compoundCRS. For
GeoTIFF 1.0 files, you need to speci
Hi all,
I'm finding a change in georeferencing between GDAL 2.4 and 3.x that
results in AutoCAD not being able to figure out where on earth a geotiff
should be. I don't have AutoCAD, so I'm reliant on what my downstream users
are telling me. These are elevation Tiffs, so they do have a vertical
com
I'd like to keep those images as small as possible. You could just
create a derived Docker image that installs git on top of it. Anyway, it
is not critical if you submit a PR without the updated indexes. I can
easily run the script on my end, before resyncing the CDN
Le 07/10/2021 à 18:17, Jav
Hi
On the contribution process of PROJ-data, there is a step where you should
run "regenerate_index_html.py". For that you need GDAL, and a recent enough
one.
What I do is to use a docker image: osgeo/gdal:alpine-normal-latest (so I
am sure I am up to date)
However, the script also requires "git"
If you add -lco RESIZE=YES fields will be resized to their minimum size.
See https://gdal.org/drivers/vector/shapefile.html#layer-creation-options
Le 07/10/2021 à 17:40, matteo a écrit :
Even,
still a weird issue with the command. I'm using this command
ogr2ogr -f "ESRI Shapefile" /home/matte
Even,
still a weird issue with the command. I'm using this command
ogr2ogr -f "ESRI Shapefile" /home/matteo/myfolder "PG:dbname='mydb'
host=myhost port=5432 user='myuser' password='mypws' sslmode=disable
schemas='dati'" --config PG_USE_COPY YES --config PG_LIST_ALL_TABLES YES
-progress'
so
Hi Even,
thanks for the hint :) it si just an additional step
Cheers!
Matteo
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
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
faster.
-Jukka Rahkonen-
Lähettäjä: gdal-dev Puolesta Mohammed
Hi,
I am using gdal to convert from WFS to geopackge, everything is
working fine but I need to change the name of each table before or after
converting to GeoPackage, because the layer name has a special charachart
that in my application it's not working.
Thank you
we seem to be using deprecated autoconf macros. It should work if you
downgrade autoconf to version 2.69 on your system. I'll look into
fixing our autoconf.ac syntax in a coming PR.
regards,
Thomas
On Thu, Oct 7, 2021 at 9:53 AM APM wrote:
>
> Dear List,
>
>
> if I try to compile gdal, I got an
Dear List,
if I try to compile gdal, I got an error message, see below in this email.
I use Debian testing and git:
git clone https://github.com/OSGeo/gdal.git
cd gdal
git checkout master
cd gdal
./autogen.sh
configure.ac:6172: warning: AC_OUTPUT should be used without arguments.
confi
14 matches
Mail list logo
