[GRASS-dev] Re: v.report (in wingrass65svn): ERROR: There is a table connected to input vector map 'c_ele_basin@g7'

Margherita Di Leo dileomargherita at gmail.com
Mon Jan 16 05:32:55 EST 2012


Hi Helmut and Devs,



> Hi,
>
> tested with osgeo4w: grass65-dev-6.5.svn-107.tar.bz2
>
> I've following vector map:
>
> v.info map=c_ele_basin at g7
>
>
> +----------------------------------------------------------------------------+
>  | Layer:           c_ele_basin at g7
> |
>  | Mapset:          g7
> |
>  | Location:        nc_spm_08
> |
>  | Datenbank:       C:\gisdata\grassdata
> |
>  | Titel:
> |
>  | Maßstab:       1:1
> |
>  | Kartenformat:      native
> |
>  | Name des Erzeugers: syringia
> |
>  | Organisation:
> |
>  | Quelldatum:     Sun Jan 15 23:10:24 2012
> |
>
>
> |----------------------------------------------------------------------------|
>  |   Typ der Karte:  Vektor (Level: 2)
> |
>  |
> |
>  |   Anzahl Punkte:       0               Anzahl Flächen:      1
> |
>  |   Anzahl Linien:        0               Anzahl Inseln:    1
> |
>  |   Anzhal Grenzen:   1               Anzahl faces:      0
> |
>  |   Anzahl Zentroid:    1               Anzahl Kerne:    0
> |
>  |
> |
>  |   Karte ist 3D:              No
> |
>  |   Anzahl der dblinks:      1
> |
>  |
> |
>  |         Projektion: Lambert Conformal Conic
> |
>  |               N:            226250    S:            224600
> |
>  |               E:            638130    W:            637240
> |
>  |
> |
>  |   Digitalisierungs-Schwellwert: 0
> |
>  |   Kommentare:
> |
>  |
> |
>
>
> +----------------------------------------------------------------------------+
>
> v.info -h -c map=c_ele_basin at g7
> COMMAND: r.to.vect input="c_ele_basin" output="c_ele_basin" feature="area"
> GISDBASE: C:\gisdata\grassdata
> LOCATION: nc_spm_08 MAPSET: g7 USER: syringia DATE: Sun Jan 15 23:10:24
> 2012
>
> v.info -c map=c_ele_basin at g7
> INTEGER|cat
> INTEGER|value
> CHARACTER|label
> DOUBLE PRECISION|perimeter
> Zeige Typ/Name der Spalten der Datenbank des Layers 1:
>
> the values in the table:
>
> cat: 1
> value:
> label:
> perimeter: 5.82
>
> v.report map=c_ele_basin at g7 option=area
> Zeige Typ/Name der Spalten der Datenbank des Layers 1:
> show type/name of coloumns of layer: 1
> Die Eingabedatei wurde zweimal angegeben.
> the input was twice.
> ERROR: There is a table connected to input vector map 'c_ele_basin at g7',
> but
> there are no categories present in the key column 'cat'. Consider using
> v.to.db to correct this.
> (Sun Jan 15 23:26:06 2012) Befehl ausgeführt (3 sec)
>
> v.to.db map=c_ele_basin at g7 option=cat columns=cat
> Lese Feature...
> Aktualisiere die Datenbank...
> Der Datensatz (cat 1) existiert bereits (nichts eingefügt).
> 1 Kategorien gelesen von der Vektorkarte (Layer 1).
> 1 Datensätze aus der Tabelle selektiert (Layer 1).
> 1 Kategorien gelesen von der Vektorkarte existieren in der Selektion der
> Tabelle.
> 0 Datensätze aktualisiert/eingefügt (Layer 1).
>
> v.to.db-output => the category is already in the table, nothing updated.
>
> any ideas?
>

Could it be related to Ticket #1139?
Anyways I've found that v.report has a strange behavior, i.e. the perimeter
value calculated sometimes is not correct or is zero (grass 6.5svn on
debian). I didn't report it yet because I wasn't able to replicate the
error again. I see that giohappy has the same problem.
Ideas?

Best,
madi



>
> Helmut
>
>
>
>
>
>
> --
> View this message in context:
> http://osgeo-org.1803224.n2.nabble.com/v-report-in-wingrass65svn-ERROR-There-is-a-table-connected-to-input-vector-map-c-ele-basin-g7-but-th-tp7190874p7190874.html
> Sent from the Grass - Dev mailing list archive at Nabble.com.
>
>
>
> --
Eng. Margherita Di Leo
Ph.D. Candidate
Methods and Technologies for Environmental Monitoring
Department of Environmental Engineering and Physics (DIFA)

University of Basilicata
Campus Macchia Romana
85100 - Potenza
Italy

Office: +39-0971205360
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-dev/attachments/20120116/aaa5d031/attachment.html


More information about the grass-dev mailing list