<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:10pt"><div><span>Bonjour</span><span><br></span></div><div><span>Je ne parle pas anglais</span><span> de ce fait je ne souhaite plus re</span><span>cevoir vos messages</span></div><div><span>Salutations</span></div><div><span>Daniel<br></span></div><div><span></span></div><div><span></span></div>
<div><br></div><div><span></span></div><div style="font-family: arial, helvetica, sans-serif; font-size: 10pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <font size="2" face="Arial"> <hr size="1"> <b><span style="font-weight:bold;">De :</span></b> "grass-user-request@lists.osgeo.org" <grass-user-request@lists.osgeo.org><br> <b><span style="font-weight: bold;">À :</span></b> grass-user@lists.osgeo.org <br> <b><span style="font-weight: bold;">Envoyé le :</span></b> Jeudi 22 mars 2012 23h03<br> <b><span style="font-weight: bold;">Objet :</span></b> grass-user Digest, Vol 71, Issue 50<br> </font> </div> <br>Send grass-user mailing list submissions to<br> <a ymailto="mailto:grass-user@lists.osgeo.org" href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.osgeo.org/mailman/listinfo/grass-user" target="_blank">http://lists.osgeo.org/mailman/listinfo/grass-user</a><br>or, via email, send a message with subject or body 'help' to<br> <a ymailto="mailto:grass-user-request@lists.osgeo.org" href="mailto:grass-user-request@lists.osgeo.org">grass-user-request@lists.osgeo.org</a><br><br>You can reach the person managing the list at<br> <a ymailto="mailto:grass-user-owner@lists.osgeo.org" href="mailto:grass-user-owner@lists.osgeo.org">grass-user-owner@lists.osgeo.org</a><br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of grass-user digest..."<br><br><br>Today's Topics:<br><br> 1. Re: How Does GRASS Handle PostgreSQL Database Name Change?<br> (Rich Shepard)<br> 2. v.out.ogr: Convert Attribute Database? (Rich Shepard)<br> 3. Re: How Does GRASS Handle
PostgreSQL Database Name Change?<br> (Helmut Kudrnovsky)<br> 4. Re: Re: How Does GRASS Handle PostgreSQL Database Name<br> Change? (Rich Shepard)<br> 5. Re: v.out.ogr: Convert Attribute Database? (Helmut Kudrnovsky)<br> 6. Re: SWAT Integration? (Chris George)<br> 7. Re: SWAT Integration? (Rich Shepard)<br> 8. Re: Re: v.out.ogr: Convert Attribute Database? (Rich Shepard)<br> 9. Re: Re: v.out.ogr: Convert Attribute Database? [SOLVED]<br> (Rich Shepard)<br> 10. r.sun Direct/Diffuse problem (Collin Bode)<br> 11. Re: How Does GRASS Handle PostgreSQL Database Name Change?<br> (Helmut Kudrnovsky)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Thu, 22 Mar 2012 09:59:48 -0700 (PDT)<br>From: Rich Shepard <<a
ymailto="mailto:rshepard@appl-ecosys.com" href="mailto:rshepard@appl-ecosys.com">rshepard@appl-ecosys.com</a>><br>Subject: Re: [GRASS-user] How Does GRASS Handle PostgreSQL Database<br> Name Change?<br>To: <a ymailto="mailto:grass-users@lists.osgeo.org" href="mailto:grass-users@lists.osgeo.org">grass-users@lists.osgeo.org</a><br>Message-ID:<br> <<a ymailto="mailto:alpine.LNX.2.00.1203220956270.26933@salmo.appl-ecosys.com" href="mailto:alpine.LNX.2.00.1203220956270.26933@salmo.appl-ecosys.com">alpine.LNX.2.00.1203220956270.26933@salmo.appl-ecosys.com</a>><br>Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed<br><br>On Thu, 22 Mar 2012, Maris Nartiss wrote:<br><br>> As goes for a GUI crash, please, report it in the issue tracker, as WXGUI<br>> shouldn't crash if DB connection information isn't correct.<br><br> Osgeo didn't like something about my attempts to create an
account so I<br>could post the problem. As it did not tell me what it didn't like, I gave up<br>after a couple of attempts.<br><br> Context: trying to view the attributes of a vector map that apparently was<br>re-projected without the attributes following along. Results:<br><br>DBMI-Postgres driver error:<br>select * from fluvial where 1 = 0<br>ERROR: relation "fluvial" does not exist<br>LINE 1: select * from fluvial where 1 = 0<br> ^<br>GRASS_INFO_ERROR(30342,1): Unable to describe table <fluvial><br>GRASS_INFO_END(30342,1)<br><br>GRASS_INFO_ERROR(30345,1): Unable to describe table <fluvial><br>GRASS_INFO_END(30345,1)<br>DBMI-Postgres driver error:<br>select * from fluvial where 1 = 0<br>ERROR: relation "fluvial" does not exist<br>LINE 1: select * from fluvial where 1 = 0<br>
^<br>GRASS_INFO_ERROR(30425,1): Unable to describe table <fluvial><br>GRASS_INFO_END(30425,1)<br><br>GRASS_INFO_ERROR(30428,1): Unable to describe table <fluvial><br>GRASS_INFO_END(30428,1)<br><br> No more wxGUI.<br><br>Rich<br><br><br><br>------------------------------<br><br>Message: 2<br>Date: Thu, 22 Mar 2012 11:47:52 -0700 (PDT)<br>From: Rich Shepard <<a ymailto="mailto:rshepard@appl-ecosys.com" href="mailto:rshepard@appl-ecosys.com">rshepard@appl-ecosys.com</a>><br>Subject: [GRASS-user] v.out.ogr: Convert Attribute Database?<br>To: <a ymailto="mailto:grass-users@lists.osgeo.org" href="mailto:grass-users@lists.osgeo.org">grass-users@lists.osgeo.org</a><br>Message-ID:<br> <<a ymailto="mailto:alpine.LNX.2.00.1203221134070.26933@salmo.appl-ecosys.com"
href="mailto:alpine.LNX.2.00.1203221134070.26933@salmo.appl-ecosys.com">alpine.LNX.2.00.1203221134070.26933@salmo.appl-ecosys.com</a>><br>Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII<br><br> Trying to convert the attribute database of a vector (points) table from<br>dbf to postgres, and I'm missing a critical step.<br><br> Asked and answered:<br><br>GRASS 6.5.svn (Washington-Kinross):~/grassdata > v.db.connect<br>map=surface_h2o -p<br>Vector map <surface_h2o@buckhorn> is connected by:<br>layer <1> table <suface_water_sites> in database<br></home/rshepard/grassdata/Washington-Kinross/buckhorn/dbf/> through driver<br><dbf> with key <cat><br><br> Used v.out.ogr to export from dbf to a postgres table emulating the<br>example on the manual page:<br><br> The example's syntax is:<br><br>Export to PostgreSQL/PostGIS<br>Export areas from GRASS vector map directly to
PostGIS:<br><br>v.out.ogr input=polygons type=area \<br> dsn="PG:host=localhost dbname=postgis user=postgres" \<br> olayer=polymap format=PostgreSQL<br><br>so I try,<br><br>GRASS 6.5.svn (Washington-Kinross):~/grassdata > v.out.ogr in=surface_h2o<br>type=point dsn="PG:dbname=buckhornmine"<br>Exporting 13 geometries...<br> 100%<br>v.out.ogr complete. 13 features written to <surface_h2o> (ESRI_Shapefile).<br><br>and end up with a directory called PG\:dbname\=buckhornmine/ containing the<br>shapefile.<br><br> What command line do I use to transfer the attributes from the native dbf<br>to a postgres table in the defined database?<br><br>Rich<br><br><br><br><br>------------------------------<br><br>Message: 3<br>Date: Thu, 22 Mar 2012 12:51:22 -0700 (PDT)<br>From: Helmut Kudrnovsky <<a ymailto="mailto:hellik@web.de"
href="mailto:hellik@web.de">hellik@web.de</a>><br>Subject: [GRASS-user] Re: How Does GRASS Handle PostgreSQL Database<br> Name Change?<br>To: <a ymailto="mailto:grass-user@lists.osgeo.org" href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br>Message-ID: <<a ymailto="mailto:1332445882579-4646223.post@n6.nabble.com" href="mailto:1332445882579-4646223.post@n6.nabble.com">1332445882579-4646223.post@n6.nabble.com</a>><br>Content-Type: text/plain; charset=us-ascii<br><br>>But, for those of us attempting new operations a cross-reference to all<br>>relevant modules (in this case attribute database related) would be<br>>extremely helpful. <br><br>it seems it's there, see the bottom of the manual page:<br><br><a href="http://grass.osgeo.org/grass64/manuals/html64_user/db.connect.html"
target="_blank">http://grass.osgeo.org/grass64/manuals/html64_user/db.connect.html</a><br><br>NAME<br>db.connect - Prints/sets general DB connection for current mapset and exits.<br>[...]<br>SEE ALSO<br>db.columns, db.drivers, db.login, db.tables, v.db.addtable, v.db.connect,<br>GRASS SQL interface<br><br>-----<br>best regards<br>Helmut<br>--<br>View this message in context: <a href="http://osgeo-org.1560.n6.nabble.com/How-Does-GRASS-Handle-PostgreSQL-Database-Name-Change-tp4642201p4646223.html" target="_blank">http://osgeo-org.1560.n6.nabble.com/How-Does-GRASS-Handle-PostgreSQL-Database-Name-Change-tp4642201p4646223.html</a><br>Sent from the Grass - Users mailing list archive at Nabble.com.<br><br><br>------------------------------<br><br>Message: 4<br>Date: Thu, 22 Mar 2012 13:09:48 -0700 (PDT)<br>From: Rich Shepard <<a ymailto="mailto:rshepard@appl-ecosys.com" href="mailto:rshepard@appl-ecosys.com">rshepard@appl-ecosys.com</a>><br>Subject: Re:
[GRASS-user] Re: How Does GRASS Handle PostgreSQL<br> Database Name Change?<br>To: <a ymailto="mailto:grass-user@lists.osgeo.org" href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br>Message-ID: <<a ymailto="mailto:alpine.LNX.2.00.1203221307230.3412@salmo.appl-ecosys.com" href="mailto:alpine.LNX.2.00.1203221307230.3412@salmo.appl-ecosys.com">alpine.LNX.2.00.1203221307230.3412@salmo.appl-ecosys.com</a>><br>Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed<br><br>On Thu, 22 Mar 2012, Helmut Kudrnovsky wrote:<br><br>> it seems it's there, see the bottom of the manual page:<br>> NAME<br>> db.connect - Prints/sets general DB connection for current mapset and exits.<br>> [...]<br>> SEE ALSO<br>> db.columns, db.drivers, db.login, db.tables, v.db.addtable, v.db.connect,<br><br>Helmut,<br><br> Those are only for modules in the db.* family. What I meant by a
cross<br>reference would include all the v.db.* modules, too. It did not occur to me<br>to look in the vector modules for ones related to database operations.<br><br>Rich<br><br><br><br><br>------------------------------<br><br>Message: 5<br>Date: Thu, 22 Mar 2012 13:35:22 -0700 (PDT)<br>From: Helmut Kudrnovsky <<a ymailto="mailto:hellik@web.de" href="mailto:hellik@web.de">hellik@web.de</a>><br>Subject: [GRASS-user] Re: v.out.ogr: Convert Attribute Database?<br>To: <a ymailto="mailto:grass-user@lists.osgeo.org" href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br>Message-ID: <<a ymailto="mailto:1332448522518-4646386.post@n6.nabble.com" href="mailto:1332448522518-4646386.post@n6.nabble.com">1332448522518-4646386.post@n6.nabble.com</a>><br>Content-Type: text/plain; charset=us-ascii<br><br>>Used v.out.ogr to export from dbf to a postgres table<br><br>v.out.ogr - Converts GRASS vector map to one of the supported OGR
vector<br>formats. <br><br>v.out.ogr export the entire vector map (geometry and attribute) not only the<br>attribute table<br><br>from the manual:<br><a href="http://grass.osgeo.org/grass64/manuals/html64_user/v.out.ogr.html" target="_blank">http://grass.osgeo.org/grass64/manuals/html64_user/v.out.ogr.html</a><br><br>Export to PostgreSQL/PostGIS<br>Export areas from GRASS vector map directly to PostGIS:<br><br>v.out.ogr input=polygons type=area \<br> dsn="PG:host=localhost dbname=postgis user=postgres" \<br> olayer=polymap format=PostgreSQL<br><br>> v.out.ogr in=surface_h2o<br>>type=point dsn="PG:dbname=buckhornmine" <br><br>missing format definition? <br><br>default format is shape-file<br><br>what I would do (a very lazy way):<br><br>- create a new mapset<br>- using db.connect (Prints/sets general DB connection for current mapset and<br>exits.) to define postgres as the mapset
database backend<br>- g.copy surface_h2o to the new mapset and the attribute table should be<br>automagically in the postgres<br><br><br>-----<br>best regards<br>Helmut<br>--<br>View this message in context: <a href="http://osgeo-org.1560.n6.nabble.com/v-out-ogr-Convert-Attribute-Database-tp4645995p4646386.html" target="_blank">http://osgeo-org.1560.n6.nabble.com/v-out-ogr-Convert-Attribute-Database-tp4645995p4646386.html</a><br>Sent from the Grass - Users mailing list archive at Nabble.com.<br><br><br>------------------------------<br><br>Message: 6<br>Date: Thu, 22 Mar 2012 16:45:48 -0400<br>From: Chris George <<a ymailto="mailto:cwg@iist.unu.edu" href="mailto:cwg@iist.unu.edu">cwg@iist.unu.edu</a>><br>Subject: Re: [GRASS-user] SWAT Integration?<br>To: Rich Shepard <<a ymailto="mailto:rshepard@appl-ecosys.com" href="mailto:rshepard@appl-ecosys.com">rshepard@appl-ecosys.com</a>><br>Cc: <a ymailto="mailto:grass-users@lists.osgeo.org"
href="mailto:grass-users@lists.osgeo.org">grass-users@lists.osgeo.org</a><br>Message-ID: <<a ymailto="mailto:4F6B8F7C.5000605@iist.unu.edu" href="mailto:4F6B8F7C.5000605@iist.unu.edu">4F6B8F7C.5000605@iist.unu.edu</a>><br>Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br><br>There is an open source way to run SWAT, using the MWSWAT interface, <br>which uses MapWindow as the GIS system. You can get it from <br>www.waterbase.org.<br><br>Chris<br><br><br>On 19/03/2012 7:50 PM, Rich Shepard wrote:<br>> About 10 years ago I tried integrating SWAT (Soil and Water Assessment<br>> Tool, from Texas A&M Univ.) with GRASS-4.1. Didn't work too well. Now I'd<br>> like to use the most current version with GRASS-6.5svn.<br>><br>> Is anyone here using SWAT?<br>><br>> (The source download link is broken but I'll write to TAMU about this.)<br>><br>> Rich<br>><br>>
_______________________________________________<br>> grass-user mailing list<br>> <a ymailto="mailto:grass-user@lists.osgeo.org" href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br>> <a href="http://lists.osgeo.org/mailman/listinfo/grass-user" target="_blank">http://lists.osgeo.org/mailman/listinfo/grass-user</a><br><br><br>------------------------------<br><br>Message: 7<br>Date: Thu, 22 Mar 2012 13:53:24 -0700 (PDT)<br>From: Rich Shepard <<a ymailto="mailto:rshepard@appl-ecosys.com" href="mailto:rshepard@appl-ecosys.com">rshepard@appl-ecosys.com</a>><br>Subject: Re: [GRASS-user] SWAT Integration?<br>To: <a ymailto="mailto:grass-users@lists.osgeo.org" href="mailto:grass-users@lists.osgeo.org">grass-users@lists.osgeo.org</a><br>Message-ID: <<a ymailto="mailto:alpine.LNX.2.00.1203221353020.3412@salmo.appl-ecosys.com"
href="mailto:alpine.LNX.2.00.1203221353020.3412@salmo.appl-ecosys.com">alpine.LNX.2.00.1203221353020.3412@salmo.appl-ecosys.com</a>><br>Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed<br><br>On Thu, 22 Mar 2012, Chris George wrote:<br><br>> There is an open source way to run SWAT, using the MWSWAT interface, which<br>> uses MapWindow as the GIS system. You can get it from www.waterbase.org.<br><br>Chris,<br><br> Thank you.<br><br>Rich<br><br><br><br>------------------------------<br><br>Message: 8<br>Date: Thu, 22 Mar 2012 13:57:12 -0700 (PDT)<br>From: Rich Shepard <<a ymailto="mailto:rshepard@appl-ecosys.com" href="mailto:rshepard@appl-ecosys.com">rshepard@appl-ecosys.com</a>><br>Subject: Re: [GRASS-user] Re: v.out.ogr: Convert Attribute Database?<br>To: <a ymailto="mailto:grass-user@lists.osgeo.org" href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br>Message-ID: <<a
ymailto="mailto:alpine.LNX.2.00.1203221355240.3412@salmo.appl-ecosys.com" href="mailto:alpine.LNX.2.00.1203221355240.3412@salmo.appl-ecosys.com">alpine.LNX.2.00.1203221355240.3412@salmo.appl-ecosys.com</a>><br>Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed<br><br>On Thu, 22 Mar 2012, Helmut Kudrnovsky wrote:<br><br>> v.out.ogr input=polygons type=area \<br>> dsn="PG:host=localhost dbname=postgis user=postgres" \<br>> olayer=polymap format=PostgreSQL<br><br>> missing format definition?<br><br>Helmut,<br><br> Er, looks like I did forget the format definition.<br><br>> what I would do (a very lazy way):<br>><br>> - create a new mapset<br>> - using db.connect (Prints/sets general DB connection for current mapset and<br>> exits.) to define postgres as the mapset database backend<br>> - g.copy surface_h2o to the new mapset and the attribute
table should be<br>> automagically in the postgres<br><br> I'll give this a try. I can then delete the original map and copy the new<br>one back to the project mapset.<br><br> Will let everyone know how this works.<br><br>Thanks,<br><br>Rich<br><br><br><br>------------------------------<br><br>Message: 9<br>Date: Thu, 22 Mar 2012 14:00:51 -0700 (PDT)<br>From: Rich Shepard <<a ymailto="mailto:rshepard@appl-ecosys.com" href="mailto:rshepard@appl-ecosys.com">rshepard@appl-ecosys.com</a>><br>Subject: Re: [GRASS-user] Re: v.out.ogr: Convert Attribute Database?<br> [SOLVED]<br>To: <a ymailto="mailto:grass-user@lists.osgeo.org" href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br>Message-ID: <<a ymailto="mailto:alpine.LNX.2.00.1203221359210.4587@salmo.appl-ecosys.com"
href="mailto:alpine.LNX.2.00.1203221359210.4587@salmo.appl-ecosys.com">alpine.LNX.2.00.1203221359210.4587@salmo.appl-ecosys.com</a>><br>Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed<br><br>On Thu, 22 Mar 2012, Rich Shepard wrote:<br><br>> Er, looks like I did forget the format definition.<br><br>> Will let everyone know how this works.<br><br> Sigh. Adding the format=PostgreSQL did the trick. Guess I needed more<br>caffine before lunch so as not to miss a critical option.<br><br>Again, many thanks,<br><br>Rich<br><br><br><br>------------------------------<br><br>Message: 10<br>Date: Thu, 22 Mar 2012 14:17:54 -0700<br>From: Collin Bode <<a ymailto="mailto:collin@berkeley.edu" href="mailto:collin@berkeley.edu">collin@berkeley.edu</a>><br>Subject: [GRASS-user] r.sun Direct/Diffuse problem<br>To: <a ymailto="mailto:grass-user@lists.osgeo.org"
href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br>Message-ID: <<a ymailto="mailto:61B99DE1-A89B-4127-A63E-08CC8EC2E09D@berkeley.edu" href="mailto:61B99DE1-A89B-4127-A63E-08CC8EC2E09D@berkeley.edu">61B99DE1-A89B-4127-A63E-08CC8EC2E09D@berkeley.edu</a>><br>Content-Type: text/plain; charset=us-ascii<br><br>I have a research site in Mendocino County, California where I have taken several months of insolation measurements using two Hukseflux LP02 black body Pyranometers. One is equiped with a shade ring. Measurements were taken in an open field with no topographic shading. Surrounding area is hilly and forested.<br><br>I have run r.sun for every week of the year, and compared the values that match my measurement times. The global radiation values match within 5%. However, the ratio of direct to diffuse radiation is off. r.sun is reporting 20-22% diffuse radiation, while the field
measurements are reporting 7-10% diffuse. <br><br>I am using Linke Turbidity Index values from www.helioclim.org, which look too high. However, when I tried arbitrarily changing the Linke Turbidity index and rerunning r.sun, I could get the diffuse/direct ratio to match field values, but then the global radiation was much too high. <br><br>Am I missing a parameter to help with this? Any suggestions would be appreciated.<br><br>Collin <br><br><br><br><br><br><br>------------------------------<br><br>Message: 11<br>Date: Thu, 22 Mar 2012 15:03:48 -0700 (PDT)<br>From: Helmut Kudrnovsky <<a ymailto="mailto:hellik@web.de" href="mailto:hellik@web.de">hellik@web.de</a>><br>Subject: [GRASS-user] Re: How Does GRASS Handle PostgreSQL Database<br> Name Change?<br>To: <a ymailto="mailto:grass-user@lists.osgeo.org"
href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br>Message-ID: <<a ymailto="mailto:1332453828046-4646675.post@n6.nabble.com" href="mailto:1332453828046-4646675.post@n6.nabble.com">1332453828046-4646675.post@n6.nabble.com</a>><br>Content-Type: text/plain; charset=us-ascii<br><br>> SEE ALSO<br>> db.columns, db.drivers, db.login, db.tables, v.db.addtable, v.db.connect, <br><br>? v.db.addtable, v.db.connect, ... see above ;o) ...<br><br>... it's open source :o) ... concrete suggestions for improvements are<br>welcomed...<br><br><br><br>-----<br>best regards<br>Helmut<br>--<br>View this message in context: <a href="http://osgeo-org.1560.n6.nabble.com/How-Does-GRASS-Handle-PostgreSQL-Database-Name-Change-tp4642201p4646675.html" target="_blank">http://osgeo-org.1560.n6.nabble.com/How-Does-GRASS-Handle-PostgreSQL-Database-Name-Change-tp4642201p4646675.html</a><br>Sent from the Grass - Users mailing list archive at
Nabble.com.<br><br><br>------------------------------<br><br>_______________________________________________<br>grass-user mailing list<br><a ymailto="mailto:grass-user@lists.osgeo.org" href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/grass-user" target="_blank">http://lists.osgeo.org/mailman/listinfo/grass-user</a><br><br><br>End of grass-user Digest, Vol 71, Issue 50<br>******************************************<br><br><br> </div> </div> </div></body></html>