[GRASS-user] Upper case letters for defining columns via v.db.addtable
Hi, when I want to specify a column in v.db.addtable, all upper case letters in the column name get converted to lower case. I'm working on GRASS 71 (trunk). Is this an intended behaviour? v.db.addtable map=myMap table=test layer=3 columns="My_COL INT" cheers, /Johannes ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] Categories in new layers of vector maps
Hi, I am slightly confused about creating new layers for vector maps and adding a category value. I want to add a layer and subsequently I want to use v.what.rast to query a raster map and update that layer. Hence, I need categories in the new layer. However, it seems that adding a new table and connect it to a specific layer (v.db.addtable) does not create/update the category column (in GRASS 71, trunk): Here an example for the NC-dataset: v.db.addtable map=firestations@PERMANENT layer=2 DB settings already defined, nothing to do Reading features... Updating database... 0 categories read from vector map (layer 2) 0 records updated/inserted (layer 2) And when I try to manually update the category I am also not successful: v.to.db map=firestations@PERMANENT layer=2 option=cat columns=cat Reading features... Updating database... 0 categories read from vector map (layer 2) 0 records updated/inserted (layer 2) Maybe I just got something wrong? The map "firestations@PERMANENT" has categories (stored in layer 1) v.category input=firestations@PERMANENT option=report Layer/table: 1/firestations type countminmax point 71 1 71 line 0 0 0 boundary 0 0 0 centroid 0 0 0 area 0 0 0 face 0 0 0 kernel 0 0 0 all 71 1 71 v.category complete. 0 features modified. Any suggestions? best, Johannes ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Upper case letters for defining columns via v.db.addtable
Johannes Radinger wrote > Hi, > > when I want to specify a column in v.db.addtable, all upper case letters > in > the column name get converted to lower case. I'm working on GRASS 71 > (trunk). Is this an intended behaviour? > > v.db.addtable map=myMap table=test layer=3 columns="My_COL INT" > > > cheers, > > /Johannes > > ___ > grass-user mailing list > grass-user@.osgeo > http://lists.osgeo.org/mailman/listinfo/grass-user a quick test here with sqlite as db-backend: v.db.addcolumn map=mybusstop@user1 columns=My_COL integer v.db.addcolumn --verbose map=mybusstop@user1 columns=My_COL2 integer Adding column to the table v.db.addcolumn --verbose map=mybusstop@user1 columns=My_COL3 INT Adding column to the table db.columns table=mybusstop cat ROUTES UPDATED STREET_1 STREET_2 CAMPUS SHELTER BENCHES DISPLAY_MP SIGNS RECEPTACLE COMMENT_ ID X Y Latitude Longitude Map_Size Time_Pt WWTm_pt GoTri_Name MDTm_Pt My_COL My_COL2 My_COL3 seems to work here. - best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Upper-case-letters-for-defining-columns-via-v-db-addtable-tp5167120p5167156.html Sent from the Grass - Users mailing list archive at Nabble.com. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Upper case letters for defining columns via v.db.addtable
> a quick test here with sqlite as db-backend: also tested with dbf as db-backend: v.db.addcolumn --verbose map=mybusstopdbf@g7 columns=My_COL4 integer Adding column to the table db.columns table=mybusstopdbf cat ROUTES UPDATED STREET_1 STREET_2 CAMPUS SHELTER BENCHES DISPLAY_MP SIGNS RECEPTACLE COMMENT_ ID X Y Latitude Longitude Map_Size Time_Pt WWTm_pt GoTri_Name MDTm_Pt My_COL4 - best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Upper-case-letters-for-defining-columns-via-v-db-addtable-tp5167120p5167161.html Sent from the Grass - Users mailing list archive at Nabble.com. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] Possible to use vector attribute for r.carve's depth parameter
Hi, I have a series of vector polygon layer where there is an attribute for estimated depth of the rivers/streams. I want to use this in r.carve [0] to improve the river/stream channel of my DEM. As I understand it, r.carve [0] only uses a single float value to carve the stream channel. Instead of looping a series of r.carve run for each depth attribute, is it possible to just use the attribute of the vector polygon? Thanks! [0] http://grass.osgeo.org/grass70/manuals/r.carve.html -- cheers, maning -- "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ -- ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Categories in new layers of vector maps
Hi Johannes, On Mon, Oct 13, 2014 at 10:18 AM, Johannes Radinger wrote: > The map "firestations@PERMANENT" has categories (stored in layer 1) > v.category input=firestations@PERMANENT option=report > Layer/table: 1/firestations > type countminmax > point 71 1 71 > line 0 0 0 > boundary 0 0 0 > centroid 0 0 0 > area 0 0 0 > face 0 0 0 > kernel 0 0 0 > all 71 1 71 > v.category complete. 0 features modified. > > > > Any suggestions? you should use the v.category to copy the categories from layer1 to layer2. Pietro ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Upper case letters for defining columns via v.db.addtable
Hi Helmut, v.db.addcolumn is also working here. Can you please test v.db.addtable with columns specified. This module does not work correctly in my case. /Johannes On Mon, Oct 13, 2014 at 11:44 AM, Helmut Kudrnovsky wrote: > > a quick test here with sqlite as db-backend: > > also tested with dbf as db-backend: > > v.db.addcolumn --verbose map=mybusstopdbf@g7 columns=My_COL4 integer > Adding column to the table > > db.columns table=mybusstopdbf > cat > ROUTES > UPDATED > STREET_1 > STREET_2 > CAMPUS > SHELTER > BENCHES > DISPLAY_MP > SIGNS > RECEPTACLE > COMMENT_ > ID > X > Y > Latitude > Longitude > Map_Size > Time_Pt > WWTm_pt > GoTri_Name > MDTm_Pt > My_COL4 > > > > > > - > best regards > Helmut > -- > View this message in context: > http://osgeo-org.1560.x6.nabble.com/Upper-case-letters-for-defining-columns-via-v-db-addtable-tp5167120p5167161.html > Sent from the Grass - Users mailing list archive at Nabble.com. > ___ > grass-user mailing list > grass-user@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-user > ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Categories in new layers of vector maps
Johannes Radinger wrote > Hi, > > I am slightly confused about creating new layers for vector maps and > adding > a category value. > I want to add a layer and subsequently I want to use v.what.rast to query > a > raster map and update > that layer. Hence, I need categories in the new layer. However, it seems > that adding a new table and connect it to a specific layer (v.db.addtable) > does not create/update the category column (in GRASS 71, trunk): > > Here an example for the NC-dataset: > > v.db.addtable map=firestations@PERMANENT layer=2 > > DB settings already defined, nothing to do > Reading features... > Updating database... > 0 categories read from vector map (layer 2) > 0 records updated/inserted (layer 2) > > > And when I try to manually update the category I am also not successful: > v.to.db map=firestations@PERMANENT layer=2 option=cat columns=cat > > Reading features... > Updating database... > 0 categories read from vector map (layer 2) > 0 records updated/inserted (layer 2) > > Maybe I just got something wrong? > > > The map "firestations@PERMANENT" has categories (stored in layer 1) > v.category input=firestations@PERMANENT option=report > > Layer/table: 1/firestations > type countminmax > point 71 1 71 > line 0 0 0 > boundary 0 0 0 > centroid 0 0 0 > area 0 0 0 > face 0 0 0 > kernel 0 0 0 > all 71 1 71 > v.category complete. 0 features modified. > > > > Any suggestions? > > > best, > Johannes > > ___ > grass-user mailing list > grass-user@.osgeo > http://lists.osgeo.org/mailman/listinfo/grass-user a possible workflow (but maybe not the only one): g.copy vect=hospitals@PERMANENT,myhospitals v.db.addtable map=myhospitals@testnewlayer table=myhospitalslayer2 layer=2 DB settings already defined, nothing to do Lese Objekte... Aktualisiere die Datenbank... 0 Kategorien gelesen von der Vektorkarte (Layer 2). 0 Datensätze aktualisiert/eingefügt (Layer 2). v.category --verbose input=myhospitals@testnewlayer layer=2 output=myhospitals2layers option=add Using native format Verarbeite Objekte... Kopiere Attributtabelle(n)... Erstelle Topologie für die Vektorkarte ... Registriere Primitive... 160 primitives registered 160 Vertices registriert Erzeuge Flächen... 0 areas built 0 isles built Füge Inseln hinzu... Füge Zentroide hinzu... Die Topologie wurde erstellt. Anzahl der Knoten: 0 Anzahl der Primitive: 160 Anzahl der Punkte: 160 Anzahl der Linien: 0 Anzahl der Grenzen: 0 Anzahl der Zentroide: 0 Anzahl der Flächen: 0 Anzahl der Inseln: 0 v.category komplett. 160 features modified. v.to.db map=myhospitals2layers@testnewlayer layer=2 option=cat columns=cat Lese Objekte... Aktualisiere die Datenbank... 160 Kategorien gelesen von der Vektorkarte (Layer 2). 160 Kategorien gelesen von der Vektorkarte existieren nicht in der Selektion der Tabelle. 160 Datensätze aktualisiert/eingefügt (Layer 2). v.db.addcolumn --quiet map=myhospitals2layers@testnewlayer layer=2 columns=testquery double v.category input=myhospitals2layers@testnewlayer option=report v.category komplett. 0 features modified. Layer/Tabelle: 1/myhospitals2layers_hospitals Typ AnzahlMinMax Punkt160 1160 Linie 0 0 0 Grenze 0 0 0 Zentroid 0 0 0 Fläche 0 0 0 Oberfläche 0 0 0 Kernel 0 0 0 Alle 160 1160 Layer/Tabelle: 2/myhospitals2layers_myhospitalslayer2 Typ AnzahlMinMax Punkt160 1160 Linie 0 0 0 Grenze 0 0 0 Zentroid 0 0 0 Fläche 0 0 0 Oberfläche 0 0 0 Kernel 0 0 0 Alle 160 1160 g.region -p -a --verbose rast=elevation@PERMANENT align=elevation@PERMANENT v.what.rast --verbose map=myhospitals2layers@testnewlayer layer=2 raster=elevation@PERMANENT column=testquery Reading features from vector map... WARNING: 158 Punkte außerhalb der Region wurden übersprungen. Update vector attributes... 2 Kategorien aus dem Vektor geladen. 160 Kategorien aus der Tabelle geladen. 0 Kategorien des Vektors fehlen in der Tabelle. v.what.rast komplett. 2 records updated. - best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Categories-in-new-layers-of-vector-maps-tp5167141p5167191.html Sent from the Grass - Users mailing list archive at Nabble.com. ___ grass-user mailing list grass-user@lists.osgeo.or
Re: [GRASS-user] Categories in new layers of vector maps
Johannes Radinger wrote > Hi, > > I am slightly confused about creating new layers for vector maps and > adding > a category value. > I want to add a layer and subsequently I want to use v.what.rast to query > a > raster map and update > that layer. Hence, I need categories in the new layer. However, it seems > that adding a new table and connect it to a specific layer (v.db.addtable) > does not create/update the category column (in GRASS 71, trunk): > > Here an example for the NC-dataset: > > v.db.addtable map=firestations@PERMANENT layer=2 > > DB settings already defined, nothing to do > Reading features... > Updating database... > 0 categories read from vector map (layer 2) > 0 records updated/inserted (layer 2) > > > And when I try to manually update the category I am also not successful: > v.to.db map=firestations@PERMANENT layer=2 option=cat columns=cat > > Reading features... > Updating database... > 0 categories read from vector map (layer 2) > 0 records updated/inserted (layer 2) > > Maybe I just got something wrong? > > > The map "firestations@PERMANENT" has categories (stored in layer 1) > v.category input=firestations@PERMANENT option=report > > Layer/table: 1/firestations > type countminmax > point 71 1 71 > line 0 0 0 > boundary 0 0 0 > centroid 0 0 0 > area 0 0 0 > face 0 0 0 > kernel 0 0 0 > all 71 1 71 > v.category complete. 0 features modified. > > > > Any suggestions? > > > best, > Johannes > > ___ > grass-user mailing list > grass-user@.osgeo > http://lists.osgeo.org/mailman/listinfo/grass-user one possible workflow (but maybe not the only one): g.copy vect=hospitals@PERMANENT,myhospitals v.db.addtable map=myhospitals@testnewlayer table=myhospitalslayer2 layer=2 DB settings already defined, nothing to do Lese Objekte... Aktualisiere die Datenbank... 0 Kategorien gelesen von der Vektorkarte (Layer 2). 0 Datensätze aktualisiert/eingefügt (Layer 2). v.category --verbose input=myhospitals@testnewlayer layer=2 output=myhospitals2layers option=add Using native format Verarbeite Objekte... Kopiere Attributtabelle(n)... Erstelle Topologie für die Vektorkarte ... Registriere Primitive... 160 primitives registered 160 Vertices registriert Erzeuge Flächen... 0 areas built 0 isles built Füge Inseln hinzu... Füge Zentroide hinzu... Die Topologie wurde erstellt. Anzahl der Knoten: 0 Anzahl der Primitive: 160 Anzahl der Punkte: 160 Anzahl der Linien: 0 Anzahl der Grenzen: 0 Anzahl der Zentroide: 0 Anzahl der Flächen: 0 Anzahl der Inseln: 0 v.category komplett. 160 features modified. v.to.db map=myhospitals2layers@testnewlayer layer=2 option=cat columns=cat Lese Objekte... Aktualisiere die Datenbank... 160 Kategorien gelesen von der Vektorkarte (Layer 2). 160 Kategorien gelesen von der Vektorkarte existieren nicht in der Selektion der Tabelle. 160 Datensätze aktualisiert/eingefügt (Layer 2). v.db.addcolumn --quiet map=myhospitals2layers@testnewlayer layer=2 columns=testquery double v.category input=myhospitals2layers@testnewlayer option=report v.category komplett. 0 features modified. Layer/Tabelle: 1/myhospitals2layers_hospitals Typ AnzahlMinMax Punkt160 1160 Linie 0 0 0 Grenze 0 0 0 Zentroid 0 0 0 Fläche 0 0 0 Oberfläche 0 0 0 Kernel 0 0 0 Alle 160 1160 Layer/Tabelle: 2/myhospitals2layers_myhospitalslayer2 Typ AnzahlMinMax Punkt160 1160 Linie 0 0 0 Grenze 0 0 0 Zentroid 0 0 0 Fläche 0 0 0 Oberfläche 0 0 0 Kernel 0 0 0 Alle 160 1160 g.region -p -a --verbose rast=elevation@PERMANENT align=elevation@PERMANENT v.what.rast --verbose map=myhospitals2layers@testnewlayer layer=2 raster=elevation@PERMANENT column=testquery Reading features from vector map... WARNING: 158 Punkte außerhalb der Region wurden übersprungen. Update vector attributes... 2 Kategorien aus dem Vektor geladen. 160 Kategorien aus der Tabelle geladen. 0 Kategorien des Vektors fehlen in der Tabelle. v.what.rast komplett. 2 records updated. - best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Categories-in-new-layers-of-vector-maps-tp5167141p5167194.html Sent from the Grass - Users mailing list archive at Nabble.com. ___ grass-user mailing list grass-user@lists.osg
Re: [GRASS-user] Upper case letters for defining columns via v.db.addtable
> Can you please test v.db.addtable with columns specified. This module does not work correctly in my case. confirmed. maybe open a ticket. - best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Upper-case-letters-for-defining-columns-via-v-db-addtable-tp5167120p5167196.html Sent from the Grass - Users mailing list archive at Nabble.com. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Upper case letters for defining columns via v.db.addtable
>Can you please test v.db.addtable with columns specified. This module does not work correctly in my case. it's maybe around http://trac.osgeo.org/grass/browser/grass/trunk/scripts/v.db.addtable/v.db.addtable.py#L106 - best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Upper-case-letters-for-defining-columns-via-v-db-addtable-tp5167120p5167199.html Sent from the Grass - Users mailing list archive at Nabble.com. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Compile GRASS GIS 7
Please let me know if y'all need anything else. Thanks for all of the help! GRASS GIS compilation log - Started compilation: Mon Oct 13 08:08:20 CDT 2014 -- Errors in: /home/USER/source/grass/grass7/tools/timer /home/USER/source/grass/grass7/lib/raster /home/USER/source/grass/grass7/lib/pngdriver /home/USER/source/grass/grass7/lib/psdriver /home/USER/source/grass/grass7/lib/htmldriver /home/USER/source/grass/grass7/lib/cairodriver /home/USER/source/grass/grass7/lib/display /home/USER/source/grass/grass7/lib/gtcltk /home/USER/source/grass/grass7/lib/form /home/USER/source/grass/grass7/lib/vector/diglib /home/USER/source/grass/grass7/lib/vector/Vlib /home/USER/source/grass/grass7/lib/vector/neta /home/USER/source/grass/grass7/lib/vector/vedit /home/USER/source/grass/grass7/lib/imagery /home/USER/source/grass/grass7/lib/cluster /home/USER/source/grass/grass7/lib/sites /home/USER/source/grass/grass7/lib/rst/interp_float /home/USER/source/grass/grass7/lib/lidar /home/USER/source/grass/grass7/lib/raster3d /home/USER/source/grass/grass7/lib/gpde /home/USER/source/grass/grass7/lib/init /home/USER/source/grass/grass7/lib/stats /home/USER/source/grass/grass7/lib/ogsf /home/USER/source/grass/grass7/lib/nviz /home/USER/source/grass/grass7/lib/temporal/t.connect /home/USER/source/grass/grass7/lib/manage /home/USER/source/grass/grass7/db/drivers/postgres /home/USER/source/grass/grass7/db/drivers/sqlite /home/USER/source/grass/grass7/db/drivers/dbf /home/USER/source/grass/grass7/db/drivers/ogr /home/USER/source/grass/grass7/db/db.columns /home/USER/source/grass/grass7/db/db.connect /home/USER/source/grass/grass7/db/db.copy /home/USER/source/grass/grass7/db/db.createdb /home/USER/source/grass/grass7/db/db.databases /home/USER/source/grass/grass7/db/db.describe /home/USER/source/grass/grass7/db/db.login /home/USER/source/grass/grass7/db/db.drivers /home/USER/source/grass/grass7/db/db.dropdb /home/USER/source/grass/grass7/db/db.tables /home/USER/source/grass/grass7/db/db.select /home/USER/source/grass/grass7/db/db.execute /home/USER/source/grass/grass7/display/d.colortable /home/USER/source/grass/grass7/display/d.barscale /home/USER/source/grass/grass7/display/d.erase /home/USER/source/grass/grass7/display/d.font /home/USER/source/grass/grass7/display/d.fontlist /home/USER/source/grass/grass7/display/d.colorlist /home/USER/source/grass/grass7/display/d.geodesic /home/USER/source/grass/grass7/display/d.grid /home/USER/source/grass/grass7/display/d.graph /home/USER/source/grass/grass7/display/d.his /home/USER/source/grass/grass7/display/d.histogram /home/USER/source/grass/grass7/display/d.info /home/USER/source/grass/grass7/display/d.labels /home/USER/source/grass/grass7/display/d.legend /home/USER/source/grass/grass7/display/d.linegraph /home/USER/source/grass/grass7/display/d.profile /home/USER/source/grass/grass7/display/d.mon /home/USER/source/grass/grass7/display/d.rast /home/USER/source/grass/grass7/display/d.path /home/USER/source/grass/grass7/display/d.rast.arrow /home/USER/source/grass/grass7/display/d.rast.num /home/USER/source/grass/grass7/display/d.rgb /home/USER/source/grass/grass7/display/d.title /home/USER/source/grass/grass7/display/d.rhumbline /home/USER/source/grass/grass7/display/d.text /home/USER/source/grass/grass7/display/d.vect /home/USER/source/grass/grass7/display/d.vect.chart /home/USER/source/grass/grass7/display/d.thematic.area /home/USER/source/grass/grass7/display/d.where /home/USER/source/grass/grass7/general/g.dirseps /home/USER/source/grass/grass7/general/g.copy /home/USER/source/grass/grass7/general/g.cairocomp /home/USER/source/grass/grass7/general/g.access /home/USER/source/grass/grass7/general/g.findetc /home/USER/source/grass/grass7/general/g.filename /home/USER/source/grass/grass7/general/g.findfile /home/USER/source/grass/grass7/general/g.gisenv /home/USER/source/grass/grass7/general/g.list /home/USER/source/grass/grass7/general/g.gui /home/USER/source/grass/grass7/general/g.mapset /home/USER/source/grass/grass7/general/g.mapsets /home/USER/source/grass/grass7/general/g.mkfontcap /home/USER/source/grass/grass7/general/g.message /home/USER/source/grass/grass7/general/g.mlist /home/USER/source/grass/grass7/general/g.mremove /home/USER/source/grass/grass7/general/g.pnmcomp /home/USER/source/grass/grass7/general/g.ppmtopng /home/USER/source/grass/grass7/general/g.parser /home/USER/source/grass/grass7/general/g.rename /home/USER/source/grass/grass7/general/g.tempfile /home/USER/source/grass/grass7/general/g.region /home/USER/source/grass/grass7/general/g.version /home/USER/source/grass/grass7/general/g.remove /home/USER/source/grass/grass7/general/g.proj /home/USER/source/grass/grass7/general/manage/lister /home/USER/source/grass/grass7/raster /home/USER/source/grass/grass7/raster3d/r3.cross.rast /home/USER/source/grass/grass7/raster3d/r3.gwflow /home/USER/source/grass/grass7/raster3d/r3.in.bin /home/USER/source/grass/grass7/raster3d/r3.gradient /home/USER/source/gra
Re: [GRASS-user] Compile GRASS GIS 7
On Mon, Oct 13, 2014 at 3:31 PM, stephen sefick wrote: > Please let me know if y'all need anything else. Thanks for all of the help! We need to know what happens *inside* the subdirectories :-) > GRASS GIS compilation log > - > Started compilation: Mon Oct 13 08:08:20 CDT 2014 > -- > Errors in: > /home/USER/source/grass/grass7/tools/timer cd /home/USER/source/grass/grass7/tools/timer make --> which error? > /home/USER/source/grass/grass7/lib/raster cd /home/USER/source/grass/grass7/lib/raster make --> which error? The others may depend on this initial problems, so let's start with the first issues. Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Compile GRASS GIS 7
Stephen, Almost seems as though there are permissions problems; are you doing this as yourself (your login) or root? Also, what is the result of ./configure? Very odd results! Tom On Mon, Oct 13, 2014 at 7:31 AM, stephen sefick wrote: > Please let me know if y'all need anything else. Thanks for all of the help! > > GRASS GIS compilation log > - > Started compilation: Mon Oct 13 08:08:20 CDT 2014 > -- > Errors in: > /home/USER/source/grass/grass7/tools/timer > /home/USER/source/grass/grass7/lib/raster > /home/USER/source/grass/grass7/lib/pngdriver > /home/USER/source/grass/grass7/lib/psdriver > /home/USER/source/grass/grass7/lib/htmldriver > /home/USER/source/grass/grass7/lib/cairodriver > /home/USER/source/grass/grass7/lib/display > /home/USER/source/grass/grass7/lib/gtcltk > /home/USER/source/grass/grass7/lib/form > /home/USER/source/grass/grass7/lib/vector/diglib > /home/USER/source/grass/grass7/lib/vector/Vlib > /home/USER/source/grass/grass7/lib/vector/neta > /home/USER/source/grass/grass7/lib/vector/vedit > /home/USER/source/grass/grass7/lib/imagery > /home/USER/source/grass/grass7/lib/cluster > /home/USER/source/grass/grass7/lib/sites > /home/USER/source/grass/grass7/lib/rst/interp_float > /home/USER/source/grass/grass7/lib/lidar > /home/USER/source/grass/grass7/lib/raster3d > /home/USER/source/grass/grass7/lib/gpde > /home/USER/source/grass/grass7/lib/init > /home/USER/source/grass/grass7/lib/stats > /home/USER/source/grass/grass7/lib/ogsf > /home/USER/source/grass/grass7/lib/nviz > /home/USER/source/grass/grass7/lib/temporal/t.connect > /home/USER/source/grass/grass7/lib/manage > /home/USER/source/grass/grass7/db/drivers/postgres > /home/USER/source/grass/grass7/db/drivers/sqlite > /home/USER/source/grass/grass7/db/drivers/dbf > /home/USER/source/grass/grass7/db/drivers/ogr > /home/USER/source/grass/grass7/db/db.columns > /home/USER/source/grass/grass7/db/db.connect > /home/USER/source/grass/grass7/db/db.copy > /home/USER/source/grass/grass7/db/db.createdb > /home/USER/source/grass/grass7/db/db.databases > /home/USER/source/grass/grass7/db/db.describe > /home/USER/source/grass/grass7/db/db.login > /home/USER/source/grass/grass7/db/db.drivers > /home/USER/source/grass/grass7/db/db.dropdb > /home/USER/source/grass/grass7/db/db.tables > /home/USER/source/grass/grass7/db/db.select > /home/USER/source/grass/grass7/db/db.execute > /home/USER/source/grass/grass7/display/d.colortable > /home/USER/source/grass/grass7/display/d.barscale > /home/USER/source/grass/grass7/display/d.erase > /home/USER/source/grass/grass7/display/d.font > /home/USER/source/grass/grass7/display/d.fontlist > /home/USER/source/grass/grass7/display/d.colorlist > /home/USER/source/grass/grass7/display/d.geodesic > /home/USER/source/grass/grass7/display/d.grid > /home/USER/source/grass/grass7/display/d.graph > /home/USER/source/grass/grass7/display/d.his > /home/USER/source/grass/grass7/display/d.histogram > /home/USER/source/grass/grass7/display/d.info > /home/USER/source/grass/grass7/display/d.labels > /home/USER/source/grass/grass7/display/d.legend > /home/USER/source/grass/grass7/display/d.linegraph > /home/USER/source/grass/grass7/display/d.profile > /home/USER/source/grass/grass7/display/d.mon > /home/USER/source/grass/grass7/display/d.rast > /home/USER/source/grass/grass7/display/d.path > /home/USER/source/grass/grass7/display/d.rast.arrow > /home/USER/source/grass/grass7/display/d.rast.num > /home/USER/source/grass/grass7/display/d.rgb > /home/USER/source/grass/grass7/display/d.title > /home/USER/source/grass/grass7/display/d.rhumbline > /home/USER/source/grass/grass7/display/d.text > /home/USER/source/grass/grass7/display/d.vect > /home/USER/source/grass/grass7/display/d.vect.chart > /home/USER/source/grass/grass7/display/d.thematic.area > /home/USER/source/grass/grass7/display/d.where > /home/USER/source/grass/grass7/general/g.dirseps > /home/USER/source/grass/grass7/general/g.copy > /home/USER/source/grass/grass7/general/g.cairocomp > /home/USER/source/grass/grass7/general/g.access > /home/USER/source/grass/grass7/general/g.findetc > /home/USER/source/grass/grass7/general/g.filename > /home/USER/source/grass/grass7/general/g.findfile > /home/USER/source/grass/grass7/general/g.gisenv > /home/USER/source/grass/grass7/general/g.list > /home/USER/source/grass/grass7/general/g.gui > /home/USER/source/grass/grass7/general/g.mapset > /home/USER/source/grass/grass7/general/g.mapsets > /home/USER/source/grass/grass7/general/g.mkfontcap > /home/USER/source/grass/grass7/general/g.message > /home/USER/source/grass/grass7/general/g.mlist > /home/USER/source/grass/grass7/general/g.mremove > /home/USER/source/grass/grass7/general/g.pnmcomp > /home/USER/source/grass/grass7/general/g.ppmtopng > /home/USER/source/grass/grass7/general/g.parser > /home/USER/source/grass/grass7/general/g.rename > /home/USER/source/grass/grass7/general/g.tempfile > /home/USER/source/grass/grass7/general/g.region > /home/USER/source/g
Re: [GRASS-user] Categories in new layers of vector maps
On 13/10/14 10:18, Johannes Radinger wrote: Hi, I am slightly confused about creating new layers for vector maps and adding a category value. Have you read the section "Vector object categories and attribute management" in the vector processing intro: http://grass.osgeo.org/grass64/manuals/vectorintro.html ? If that is not clear, we should probably try to enhance it. Moritz ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Problems installing add-ons GRASS 7
Hi,
On Wed, Sep 17, 2014 at 6:59 PM, Luis Miguel Royo Pérez
wrote:
> Hi everyone,
>
> I'm getting this error when I try to install add-ons in Lubuntu 14.04
>
> Unable to load extensions. Traceback (most recent call last):
> File "/usr/lib/grass70/scripts/g.extension", line 1081, in
> version = grass.version()['version'].split('.')
> KeyError: 'version'
>
> I've installed the dev packages. Am I missing something? or is just a bug
> due it's a beta version?
Well, there should not be such a problem in a beta.
How did you install it? Please post the apt... sequence in order to better help.
And the output of
g.region -r
g.region -v
thanks,
Markus
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Problems with r.viewshed
Hi, just for the record: I tried and did not have a problem: GRASS 7.0.0svn (latlong):~ > r.viewshed -b input=srtmv4_spain output=visPort coordinates=-3.74034324324,42.5352702703 obs_elev=9 tgt_elev=1.75 max_dist=3 Computing events... 100% Computing visibility... 100% Writing output raster map... 100% GRASS 7.0.0svn (latlong):~ > GRASS 7.0.0svn (latlong):~ > d.mon wx0 GRASS 7.0.0svn (latlong):~ > d.rast srtmv4_spain 100% GRASS 7.0.0svn (latlong):~ > d.rast visPort 100% --> looks ok. Then I tried with a large computational region: GRASS 7.0.0svn (latlong):~ > g.region n=50 s=30 w=-20 e=20 -p projection: 3 (Latitude-Longitude) zone: 0 datum: wgs84 ellipsoid: wgs84 north: 50N south: 30N west: 20W east: 20E nsres: 0:00:30 ewres: 0:00:30 rows: 2400 cols: 4800 cells: 1152 GRASS 7.0.0svn (latlong):~ > r.viewshed -b input=srtmv4_spain output=visPort coordinates=-3.74034324324,42.5352702703 obs_elev=9 tgt_elev=1.75 max_dist=3 ERROR: option : exists. GRASS 7.0.0svn (latlong):~ > r.viewshed -b input=srtmv4_spain output=visPort coordinates=-3.74034324324,42.5352702703 obs_elev=9 tgt_elev=1.75 max_dist=3 --o Intermediate files will not be deleted in case of abnormal termination. Intermediate location: /home/neteler/grassdata/latlong/neteler/.tmp/oboe.localdomain/929.0 To save space delete these files manually! Memory manager registering memory in MM_IGNORE_MEMORY_EXCEEDED mode. Start sweeping. Computing events... 100% Initialize sweepline... 100% Determine visibility... 100% Sweeping done. Saving grid to --> also fine. I am using a 64bit Linux computer (Fedora 20), are you also on 64bit? Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] my first script
Hi,
thanks for your help.
At moment I have another problem
in my script I have this line:
#grass.run_command('v.in.lines', overwrite=True, input =
output_esond_txt , output = output_esond_gis, fs='|')
grass.run_command('v.in.ascii', overwrite=True, format= 'point',
fs='|', input = output_esond_txt, output = output_esond_gis )
output is:
"output" non Š riconosciuto come comando interno o esterno,
un programma eseguibile o un file batch.
why?
I have made many attempts whith grass6.4.2 grass6.4.3 grass6.4.4
in windows Vista
you know the problem?
thanks in advance
Giuliano
2014-10-13 7:43 GMT+02:00 Johannes Radinger :
> Hi,
>
> It seems to raise an error related to the flag(s) you are specifying in
> oneof your grass modules you are using in your script. Flags in grass
> python scripts should be used like: flags="a" or for two flags: flags="ab".
> Note this does not need a "-" like in the bash command.
>
> Best,
> /johannes
>
>
>
> Original message
> From: Giuliano Urgeghe
> Date: 13/10/2014 02:44 (GMT+01:00)
> To: grass-user@lists.osgeo.org
> Subject: [GRASS-user] my first script
>
>
> Hi all,
> I have my first script in python for grass
> but when I launch it on windows vista for grass 6.4.2 in quantum gis
> I have this output:
> ...
> File "C:\PROGRA~1\QUANTU~3\apps\grass\grass-6.4.2\etc\pyth
> on\grass\script\core.py", line 189, in run_command
> ps = start_command(*args, **kwargs)
> File "C:\PROGRA~1\QUANTU~3\apps\grass\grass-6.4.2\etc\pyth
> on\grass\script\core.py", line 167, in start_command
> args = make_command(prog, flags, overwrite, quiet,
> verbose, **options)
> File "C:\PROGRA~1\QUANTU~3\apps\grass\grass-6.4.2\etc\pyth
> on\grass\script\core.py", line 124, in make_command
> raise ScriptError("'-' is not a valid flag")
> grass.script.core.ScriptError: "'-' is not a valid flag"
>
> someone know this problem?
>
> thanks in advance
> Giuliano
>
>
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] Fwd: my first script
-- Forwarded message --
From: Giuliano Urgeghe
Date: 2014-10-13 23:53 GMT+02:00
Subject: Re: [GRASS-user] my first script
To: Johannes Radinger
Cc: grass-user@lists.osgeo.org
Hi,
thanks for your help.
At moment I have another problem
in my script I have this line:
#grass.run_command('v.in.lines', overwrite=True, input =
output_esond_txt , output = output_esond_gis, fs='|')
grass.run_command('v.in.ascii', overwrite=True, format= 'point',
fs='|', input = output_esond_txt, output = output_esond_gis )
output is:
"output" non Š riconosciuto come comando interno o esterno,
un programma eseguibile o un file batch.
why?
I have made many attempts whith grass6.4.2 grass6.4.3 grass6.4.4
in windows Vista
you know the problem?
thanks in advance
Giuliano
2014-10-13 7:43 GMT+02:00 Johannes Radinger :
> Hi,
>
> It seems to raise an error related to the flag(s) you are specifying in
> oneof your grass modules you are using in your script. Flags in grass
> python scripts should be used like: flags="a" or for two flags: flags="ab".
> Note this does not need a "-" like in the bash command.
>
> Best,
> /johannes
>
>
>
> Original message
> From: Giuliano Urgeghe
> Date: 13/10/2014 02:44 (GMT+01:00)
> To: grass-user@lists.osgeo.org
> Subject: [GRASS-user] my first script
>
>
> Hi all,
> I have my first script in python for grass
> but when I launch it on windows vista for grass 6.4.2 in quantum gis
> I have this output:
> ...
> File "C:\PROGRA~1\QUANTU~3\apps\grass\grass-6.4.2\etc\pyth
> on\grass\script\core.py", line 189, in run_command
> ps = start_command(*args, **kwargs)
> File "C:\PROGRA~1\QUANTU~3\apps\grass\grass-6.4.2\etc\pyth
> on\grass\script\core.py", line 167, in start_command
> args = make_command(prog, flags, overwrite, quiet,
> verbose, **options)
> File "C:\PROGRA~1\QUANTU~3\apps\grass\grass-6.4.2\etc\pyth
> on\grass\script\core.py", line 124, in make_command
> raise ScriptError("'-' is not a valid flag")
> grass.script.core.ScriptError: "'-' is not a valid flag"
>
> someone know this problem?
>
> thanks in advance
> Giuliano
>
>
--
Ing. Giuliano Urgeghe
Via Prunizzedda 61 - 07100 Sassari
giulian...@gmail.com
tel. 3283268186
Cerca di non inviarmi files .doc, .xls, .ppt, .dwg
Preferisco formati liberi.
Please try to avoid to send me .doc, .xls, .ppt, .dwg files.
I prefer free formats.
http://it.wikipedia.org/wiki/Formato_aperto
http://en.wikipedia.org/wiki/Open_format
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] my first script
On Mon, Oct 13, 2014 at 5:53 PM, Giuliano Urgeghe
wrote:
> Hi,
> thanks for your help.
> At moment I have another problem
> in my script I have this line:
> #grass.run_command('v.in.lines', overwrite=True, input =
> output_esond_txt , output = output_esond_gis, fs='|')
> grass.run_command('v.in.ascii', overwrite=True, format= 'point',
> fs='|', input = output_esond_txt, output = output_esond_gis )
>
> output is:
> "output" non Š riconosciuto come comando interno o esterno,
> un programma eseguibile o un file batch.
>
Not sure, but could you try use different separator
grass.run_command('v.in.ascii', overwrite=True, format= 'point', fs=',',
input = output_esond_txt, output = output_esond_gis )
or, since | is a default, not using it in the command at all?
grass.run_command('v.in.ascii', overwrite=True, format= 'point', input =
output_esond_txt, output = output_esond_gis )
Anna
> why?
> I have made many attempts whith grass6.4.2 grass6.4.3 grass6.4.4
> in windows Vista
>
> you know the problem?
>
> thanks in advance
> Giuliano
>
> 2014-10-13 7:43 GMT+02:00 Johannes Radinger :
>
>> Hi,
>>
>> It seems to raise an error related to the flag(s) you are specifying in
>> oneof your grass modules you are using in your script. Flags in grass
>> python scripts should be used like: flags="a" or for two flags: flags="ab".
>> Note this does not need a "-" like in the bash command.
>>
>> Best,
>> /johannes
>>
>>
>>
>> Original message
>> From: Giuliano Urgeghe
>> Date: 13/10/2014 02:44 (GMT+01:00)
>> To: grass-user@lists.osgeo.org
>> Subject: [GRASS-user] my first script
>>
>>
>> Hi all,
>> I have my first script in python for grass
>> but when I launch it on windows vista for grass 6.4.2 in quantum gis
>> I have this output:
>> ...
>> File "C:\PROGRA~1\QUANTU~3\apps\grass\grass-6.4.2\etc\pyth
>> on\grass\script\core.py", line 189, in run_command
>> ps = start_command(*args, **kwargs)
>> File "C:\PROGRA~1\QUANTU~3\apps\grass\grass-6.4.2\etc\pyth
>> on\grass\script\core.py", line 167, in start_command
>> args = make_command(prog, flags, overwrite, quiet,
>> verbose, **options)
>> File "C:\PROGRA~1\QUANTU~3\apps\grass\grass-6.4.2\etc\pyth
>> on\grass\script\core.py", line 124, in make_command
>> raise ScriptError("'-' is not a valid flag")
>> grass.script.core.ScriptError: "'-' is not a valid flag"
>>
>> someone know this problem?
>>
>> thanks in advance
>> Giuliano
>>
>>
>
>
>
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] fatal error: 'libintl.h' file not found (OSX)
libintl.h is not part of the OS X system, so it needs to be included in the GRASS app. I don't build my GRASS app with libintl, but I think Michael Barton does. But first, make sure you have the latest version of GRASS, 6.4.4. Michael may have missed libintl.h in older versions but fixed it later. On Oct 12, 2014, at 3:23 PM, Svein Harald Sønderland wrote: > Anyone know how to get the r.stream addons to work on mac?? > > When trying to install I get this error: > > /Applications/GRASS/GRASS-6.4.app/Contents/MacOS/include/grass/glocale.h:9:10: > fatal error: 'libintl.h' file not found > #include > > Installed grass gis 6.4.3 on my mac OSX v.10.9.5. > GIS Library Revision 50937 (2012-02-25) > Python: 2.6.8 > wxPython: 2.8.12.1 > > Error message: > > (Sun Oct 12 22:11:35 2014) > g.extension.py extension=r.stream.extract > svnurl=http://svn.osgeo.org/grass/grass-addons/grass6 > WARNING: GRASS_ADDON_PATH has more items, using first defined - > '/Users/snarrald/Library/GRASS/6.4/Modules/bin' > WARNING: Extension already installed. Re-installing... > Fetching from GRASS-Addons SVN (be patient)... > Compiling... > /Applications/GRASS/GRASS-6.4.app/Contents/MacOS/include/Mak > e/Grass.make:423: warning: overriding commands for target `/ > Users/snarrald/Desktop/GrassData/GBNP/GBNP/.tmp/Gravenstein. > local/53389.0/r.stream.extract/bin' > /Applications/GRASS/GRASS-6.4.app/Contents/MacOS/include/Mak > e/Grass.make:414: warning: ignoring old commands for target > `/Users/snarrald/Desktop/GrassData/GBNP/GBNP/.tmp/Gravenstei > n.local/53389.0/r.stream.extract/bin' > In file included from close.c:2: > /Applications/GRASS/GRASS-6.4.app/Contents/MacOS/include/gra > ss/glocale.h:9:10: fatal error: 'libintl.h' file not found > #include > ^ > 1 error generated. > make: *** [OBJ.x86_64-apple-darwin12.4.0/close.o] Error 1 > ERROR: Compilation failed, sorry. Please check above error messages. > (Sun Oct 12 22:11:41 2014) Command finished (5 sec) > ___ > grass-user mailing list > grass-user@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-user - William Kyngesburye http://www.kyngchaos.com/ First Pogril: Why is life like sticking your head in a bucket filled with hyena offal? Second Pogril: I don't know. Why IS life like sticking your head in a bucket filled with hyena offal? First Pogril: I don't know either. Wretched, isn't it? -HitchHiker's Guide to the Galaxy ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
