this bug's URL: http://intevation.de/rt/webrt?serial_num=3970
-------------------------------------------------------------------------
Subject: v.in.ogr: CAT becomes DOUBLE instead of INTEGER
Platform: GNU/Linux/i386
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: cvs 2005.01.09
The output of v.in.ogr creates the CAT column as DOUBLE instead of INTEGER.
1. Import a shapefile (it was created by v.out.ogr):
$ v.in.ogr dsn=/home/john/dzialki_rogow/dzialki_rogow.shp output=dzialki_rogow cnames=cat_old
2. See the columns properties:
$ v.info -c dzialki_rogow
Displaying column types/names for database connection of layer 1:
INTEGER|cat_old
DOUBLE PRECISION|CAT <- shouldn't it be INETEGER?
DOUBLE PRECISION|KOD
CHARACTER|WLASCICIEL
CHARACTER|ADRES
CHARACTER|NR_DZIALKI
DOUBLE PRECISION|HECTARES
DOUBLE PRECISION|POW
Using DBF driver.
The shapefile I used in this example is available at http://www.biol.uni.wroc.pl/sieczka/udostepnione/grass/dzialki_rogow.tar.bz2 (19 KB).
Please also take a look at https://intevation.de/rt/webrt?serial_num=3626 "v.out.ogr forces REAL on an INTEGER column"
Are these two bugs dangerous for our data? Please somebody answer.
Maciek
-------------------------------------------- Managed by Request Tracker