[GRASS-user] Re : grass-user Digest, Vol 71, Issue 50

Wed Mar 28 03:36:18 EDT 2012

Bonjour

Je ne parle pas anglaisde ce fait je ne souhaite plus recevoir vos messages
Salutations
Daniel

________________________________
 De : "grass-user-request at lists.osgeo.org" <grass-user-request at lists.osgeo.org>
À : grass-user at lists.osgeo.org 
Envoyé le : Jeudi 22 mars 2012 23h03
Objet : grass-user Digest, Vol 71, Issue 50

Send grass-user mailing list submissions to
    grass-user at lists.osgeo.org

To subscribe or unsubscribe via the World Wide Web, visit
    http://lists.osgeo.org/mailman/listinfo/grass-user
or, via email, send a message with subject or body 'help' to
    grass-user-request at lists.osgeo.org

You can reach the person managing the list at
    grass-user-owner at lists.osgeo.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of grass-user digest..."

Today's Topics:

   1. Re: How Does GRASS Handle PostgreSQL Database Name    Change?
      (Rich Shepard)
   2. v.out.ogr: Convert Attribute Database? (Rich Shepard)
   3. Re: How Does GRASS Handle PostgreSQL Database Name    Change?
      (Helmut Kudrnovsky)
   4. Re: Re: How Does GRASS Handle PostgreSQL Database Name
      Change? (Rich Shepard)
   5. Re: v.out.ogr: Convert Attribute Database? (Helmut Kudrnovsky)
   6. Re: SWAT Integration? (Chris George)
   7. Re: SWAT Integration? (Rich Shepard)
   8. Re: Re: v.out.ogr: Convert Attribute Database? (Rich Shepard)
   9. Re: Re: v.out.ogr: Convert Attribute Database? [SOLVED]
      (Rich Shepard)
  10. r.sun Direct/Diffuse problem (Collin Bode)
  11. Re: How Does GRASS Handle PostgreSQL Database Name    Change?
      (Helmut Kudrnovsky)

----------------------------------------------------------------------

Message: 1
Date: Thu, 22 Mar 2012 09:59:48 -0700 (PDT)
From: Rich Shepard <rshepard at appl-ecosys.com>
Subject: Re: [GRASS-user] How Does GRASS Handle PostgreSQL Database
    Name    Change?
To: grass-users at lists.osgeo.org
Message-ID:
    <alpine.LNX.2.00.1203220956270.26933 at salmo.appl-ecosys.com>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Thu, 22 Mar 2012, Maris Nartiss wrote:

> As goes for a GUI crash, please, report it in the issue tracker, as WXGUI
> shouldn't crash if DB connection information isn't correct.

   Osgeo didn't like something about my attempts to create an account so I
could post the problem. As it did not tell me what it didn't like, I gave up
after a couple of attempts.

   Context: trying to view the attributes of a vector map that apparently was
re-projected without the attributes following along. Results:

DBMI-Postgres driver error:
select * from fluvial where 1 = 0
ERROR:  relation "fluvial" does not exist
LINE 1: select * from fluvial where 1 = 0
                       ^
GRASS_INFO_ERROR(30342,1): Unable to describe table <fluvial>
GRASS_INFO_END(30342,1)

GRASS_INFO_ERROR(30345,1): Unable to describe table <fluvial>
GRASS_INFO_END(30345,1)
DBMI-Postgres driver error:
select * from fluvial where 1 = 0
ERROR:  relation "fluvial" does not exist
LINE 1: select * from fluvial where 1 = 0
                       ^
GRASS_INFO_ERROR(30425,1): Unable to describe table <fluvial>
GRASS_INFO_END(30425,1)

GRASS_INFO_ERROR(30428,1): Unable to describe table <fluvial>
GRASS_INFO_END(30428,1)

   No more wxGUI.

Rich

------------------------------

Message: 2
Date: Thu, 22 Mar 2012 11:47:52 -0700 (PDT)
From: Rich Shepard <rshepard at appl-ecosys.com>
Subject: [GRASS-user] v.out.ogr: Convert Attribute Database?
To: grass-users at lists.osgeo.org
Message-ID:
    <alpine.LNX.2.00.1203221134070.26933 at salmo.appl-ecosys.com>
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII

   Trying to convert the attribute database of a vector (points) table from
dbf to postgres, and I'm missing a critical step.

   Asked and answered:

GRASS 6.5.svn (Washington-Kinross):~/grassdata > v.db.connect
map=surface_h2o -p
Vector map <surface_h2o at buckhorn> is connected by:
layer <1> table <suface_water_sites> in database
</home/rshepard/grassdata/Washington-Kinross/buckhorn/dbf/> through driver
<dbf> with key <cat>

   Used v.out.ogr to export from dbf to a postgres table emulating the
example on the manual page:

   The example's syntax is:

Export to PostgreSQL/PostGIS
Export areas from GRASS vector map directly to PostGIS:

v.out.ogr input=polygons type=area \
           dsn="PG:host=localhost dbname=postgis user=postgres" \
           olayer=polymap format=PostgreSQL

so I try,

GRASS 6.5.svn (Washington-Kinross):~/grassdata > v.out.ogr in=surface_h2o
type=point dsn="PG:dbname=buckhornmine"
Exporting 13 geometries...
  100%
v.out.ogr complete. 13 features written to <surface_h2o> (ESRI_Shapefile).

and end up with a directory called PG\:dbname\=buckhornmine/ containing the
shapefile.

   What command line do I use to transfer the attributes from the native dbf
to a postgres table in the defined database?

Rich

------------------------------

Message: 3
Date: Thu, 22 Mar 2012 12:51:22 -0700 (PDT)
From: Helmut Kudrnovsky <hellik at web.de>
Subject: [GRASS-user] Re: How Does GRASS Handle PostgreSQL Database
    Name    Change?
To: grass-user at lists.osgeo.org
Message-ID: <1332445882579-4646223.post at n6.nabble.com>
Content-Type: text/plain; charset=us-ascii

>But, for those of us attempting new operations a cross-reference to all
>relevant modules (in this case attribute database related) would be
>extremely helpful. 

it seems it's there, see the bottom of the manual page:

http://grass.osgeo.org/grass64/manuals/html64_user/db.connect.html

NAME
db.connect - Prints/sets general DB connection for current mapset and exits.
[...]
SEE ALSO
db.columns, db.drivers, db.login, db.tables, v.db.addtable, v.db.connect,
GRASS SQL interface

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.n6.nabble.com/How-Does-GRASS-Handle-PostgreSQL-Database-Name-Change-tp4642201p4646223.html
Sent from the Grass - Users mailing list archive at Nabble.com.

------------------------------

Message: 4
Date: Thu, 22 Mar 2012 13:09:48 -0700 (PDT)
From: Rich Shepard <rshepard at appl-ecosys.com>
Subject: Re: [GRASS-user] Re: How Does GRASS Handle PostgreSQL
    Database Name    Change?
To: grass-user at lists.osgeo.org
Message-ID: <alpine.LNX.2.00.1203221307230.3412 at salmo.appl-ecosys.com>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Thu, 22 Mar 2012, Helmut Kudrnovsky wrote:

> it seems it's there, see the bottom of the manual page:
> NAME
> db.connect - Prints/sets general DB connection for current mapset and exits.
> [...]
> SEE ALSO
> db.columns, db.drivers, db.login, db.tables, v.db.addtable, v.db.connect,

Helmut,

   Those are only for modules in the db.* family. What I meant by a cross
reference would include all the v.db.* modules, too. It did not occur to me
to look in the vector modules for ones related to database operations.

Rich

------------------------------

Message: 5
Date: Thu, 22 Mar 2012 13:35:22 -0700 (PDT)
From: Helmut Kudrnovsky <hellik at web.de>
Subject: [GRASS-user] Re: v.out.ogr: Convert Attribute Database?
To: grass-user at lists.osgeo.org
Message-ID: <1332448522518-4646386.post at n6.nabble.com>
Content-Type: text/plain; charset=us-ascii

>Used v.out.ogr to export from dbf to a postgres table

v.out.ogr - Converts GRASS vector map to one of the supported OGR vector
formats. 

v.out.ogr export the entire vector map (geometry and attribute) not only the
attribute table

from the manual:
http://grass.osgeo.org/grass64/manuals/html64_user/v.out.ogr.html

Export to PostgreSQL/PostGIS
Export areas from GRASS vector map directly to PostGIS:

v.out.ogr input=polygons type=area \
          dsn="PG:host=localhost dbname=postgis user=postgres" \
          olayer=polymap format=PostgreSQL

> v.out.ogr in=surface_h2o
>type=point dsn="PG:dbname=buckhornmine" 

missing format definition? 

default format is shape-file

what I would do (a very lazy way):

- create a new mapset
- using db.connect (Prints/sets general DB connection for current mapset and
exits.) to define postgres as the mapset database backend
- g.copy surface_h2o to the new mapset and the attribute table should be
automagically in the postgres

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.n6.nabble.com/v-out-ogr-Convert-Attribute-Database-tp4645995p4646386.html
Sent from the Grass - Users mailing list archive at Nabble.com.

------------------------------

Message: 6
Date: Thu, 22 Mar 2012 16:45:48 -0400
From: Chris George <cwg at iist.unu.edu>
Subject: Re: [GRASS-user] SWAT Integration?
To: Rich Shepard <rshepard at appl-ecosys.com>
Cc: grass-users at lists.osgeo.org
Message-ID: <4F6B8F7C.5000605 at iist.unu.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

There is an open source way to run SWAT, using the MWSWAT interface, 
which uses MapWindow as the GIS system.  You can get it from 
www.waterbase.org.

Chris

On 19/03/2012 7:50 PM, Rich Shepard wrote:
> About 10 years ago I tried integrating SWAT (Soil and Water Assessment
> Tool, from Texas A&M Univ.) with GRASS-4.1. Didn't work too well. Now I'd
> like to use the most current version with GRASS-6.5svn.
>
> Is anyone here using SWAT?
>
> (The source download link is broken but I'll write to TAMU about this.)
>
> Rich
>
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-user

------------------------------

Message: 7
Date: Thu, 22 Mar 2012 13:53:24 -0700 (PDT)
From: Rich Shepard <rshepard at appl-ecosys.com>
Subject: Re: [GRASS-user] SWAT Integration?
To: grass-users at lists.osgeo.org
Message-ID: <alpine.LNX.2.00.1203221353020.3412 at salmo.appl-ecosys.com>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Thu, 22 Mar 2012, Chris George wrote:

> There is an open source way to run SWAT, using the MWSWAT interface, which
> uses MapWindow as the GIS system.  You can get it from www.waterbase.org.

Chris,

   Thank you.

Rich

------------------------------

Message: 8
Date: Thu, 22 Mar 2012 13:57:12 -0700 (PDT)
From: Rich Shepard <rshepard at appl-ecosys.com>
Subject: Re: [GRASS-user] Re: v.out.ogr: Convert Attribute Database?
To: grass-user at lists.osgeo.org
Message-ID: <alpine.LNX.2.00.1203221355240.3412 at salmo.appl-ecosys.com>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Thu, 22 Mar 2012, Helmut Kudrnovsky wrote:

> v.out.ogr input=polygons type=area \
>          dsn="PG:host=localhost dbname=postgis user=postgres" \
>          olayer=polymap format=PostgreSQL

> missing format definition?

Helmut,

   Er, looks like I did forget the format definition.

> what I would do (a very lazy way):
>
> - create a new mapset
> - using db.connect (Prints/sets general DB connection for current mapset and
> exits.) to define postgres as the mapset database backend
> - g.copy surface_h2o to the new mapset and the attribute table should be
> automagically in the postgres

   I'll give this a try. I can then delete the original map and copy the new
one back to the project mapset.

   Will let everyone know how this works.

Thanks,

Rich

------------------------------

Message: 9
Date: Thu, 22 Mar 2012 14:00:51 -0700 (PDT)
From: Rich Shepard <rshepard at appl-ecosys.com>
Subject: Re: [GRASS-user] Re: v.out.ogr: Convert Attribute Database?
    [SOLVED]
To: grass-user at lists.osgeo.org
Message-ID: <alpine.LNX.2.00.1203221359210.4587 at salmo.appl-ecosys.com>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Thu, 22 Mar 2012, Rich Shepard wrote:

>  Er, looks like I did forget the format definition.

>  Will let everyone know how this works.

   Sigh. Adding the format=PostgreSQL did the trick. Guess I needed more
caffine before lunch so as not to miss a critical option.

Again, many thanks,

Rich

------------------------------

Message: 10
Date: Thu, 22 Mar 2012 14:17:54 -0700
From: Collin Bode <collin at berkeley.edu>
Subject: [GRASS-user] r.sun Direct/Diffuse problem
To: grass-user at lists.osgeo.org
Message-ID: <61B99DE1-A89B-4127-A63E-08CC8EC2E09D at berkeley.edu>
Content-Type: text/plain; charset=us-ascii

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.

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.  

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.  

Am I missing a parameter to help with this?  Any suggestions would be appreciated.

Collin 

------------------------------

Message: 11
Date: Thu, 22 Mar 2012 15:03:48 -0700 (PDT)
From: Helmut Kudrnovsky <hellik at web.de>
Subject: [GRASS-user] Re: How Does GRASS Handle PostgreSQL Database
    Name    Change?
To: grass-user at lists.osgeo.org
Message-ID: <1332453828046-4646675.post at n6.nabble.com>
Content-Type: text/plain; charset=us-ascii

> SEE ALSO
> db.columns, db.drivers, db.login, db.tables, v.db.addtable, v.db.connect, 

? v.db.addtable, v.db.connect, ... see above ;o) ...

... it's open source :o) ... concrete suggestions for improvements are
welcomed...

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.n6.nabble.com/How-Does-GRASS-Handle-PostgreSQL-Database-Name-Change-tp4642201p4646675.html
Sent from the Grass - Users mailing list archive at Nabble.com.

------------------------------

_______________________________________________
grass-user mailing list
grass-user at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

End of grass-user Digest, Vol 71, Issue 50
******************************************
-------------- section suivante --------------
Une pi?ce jointe HTML a ?t? enlev?e...
URL: http://lists.osgeo.org/pipermail/grass-user/attachments/20120328/a982683f/attachment-0001.html