#GRASS IRC Log - 2008-06-06

For logs after Feb 3, 2007, all times are GMT-8. Prior logs are GMT-9.
Back to Logs
00:24:04 CIA-10: martinl * r31644 /grass/branches/develbranch_6/gui/wxpython/gui_modules/globalvar.py: wxGUI: import gettext in globalvar module ( related to r31641 )
00:25:36 sigq: grassfeed: Changeset [31644]: wxGUI: import gettext in globalvar module ( related to r31641 ) <https://trac.osgeo.org/grass/changeset/31644>
00:26:04 CIA-10: martinl * r31645 /grass/trunk/gui/wxpython/gui_modules/globalvar.py:
00:26:04 CIA-10: wxGUI: import gettext in globalvar module ( related to r31642 )
00:26:04 CIA-10: [merge devbr6, r31644]
01:09:55 wildintellect: anyone familiar with the bearing notation in m.cogo?
01:11:08 : <_wolf_> wildintellect: have you read: http://grass.itc.it/grass62/manuals/html62_user/m.cogo.html
01:11:09 sigq: Title: GRASS GIS: m.cogo ( at grass.itc.it )
01:11:16 wildintellect: yes
01:11:27 wildintellect: I don't get the direction notation used
01:11:43 : * _wolf_ is reading
01:11:58 wildintellect: 23:14:12 is an angle apparently?
01:12:18 wildintellect: is that DMS notation?
01:12:23 : <_wolf_> Yes bearings are headings
01:13:09 wildintellect: right but is that 23 degrees?
01:13:26 wildintellect: I guess I figured it out
01:13:40 : <_wolf_> : )
01:13:40 wildintellect: 23 degree, 14 minutes 12 seconds
01:14:05 wildintellect: hmm, I think that tool could use a rewrite
01:14:45 wildintellect: people usually record bearing/headings 0-360
01:14:49 : <_wolf_> P23 N 23:14:12 W 340 means Point at 23N 23 deg 14 min 12 s W and a bearing of 340 degrees
01:15:05 wildintellect: 340 is the distance
01:15:32 wildintellect: I get it now, it's just a crappy way of doing it, time to go tinker my spreadsheet into that format
01:15:35 : <_wolf_> it doesn't look like a distance
01:15:44 wildintellect: manual says it is
01:16:12 wildintellect: it's linear units in whatever your mapset units are
01:16:14 : <_wolf_> doesn't the module output distances
01:16:20 wildintellect: it can
01:16:27 wildintellect: but that's the inverse operation
01:16:39 wildintellect: I have bearing and distance and I want coordinates
01:16:48 wildintellect: the tool can be used both directions
01:18:22 : <_wolf_> you are right it is indeed an odd format...
01:18:56 : <_wolf_> so I suppose P23 is the label of the point... how odd
01:19:02 : <_wolf_> morning RMatev
01:20:40 RMatev: gm
01:22:16 wildintellect: crap most of my bearing are past 90 so I'm going to have to figure out what west of south gives me
01:41:50 wildintellect: well I got it to work
01:42:08 wildintellect: not sure if they're right, need to make a shapefile and overlay
01:44:07 wildintellect: hmm, which column in the output is the x and which is the y
01:58:26 wildintellect: ok maybe m.cogo doesn't work as I thought, better check my numbers
07:53:53 sigq`: grassfeed: Changeset [31647]: set svn:ignore properties for grassflyer <https://trac.osgeo.org/grass/changeset/31647> || Changeset [31646]: Added directory for Martin Landa's SoC 2008 project <https://trac.osgeo.org/grass/changeset/31646> || Ticket #184 ( defect created ): v.in.garmin - detect gpstrans or gardump instead of user flag <https://trac.osgeo.org/grass/ticket/184>
08:04:52 CIA-10: martinl * r31648 /grass-addons/visualization/nviz2/cmd/ ( 14 files ): Initial experimental NVIZ CLI prototype ( under progress )
08:05:56 sigq`: grassfeed: Changeset [31648]: Initial experimental NVIZ CLI prototype ( under progress ) <https://trac.osgeo.org/grass/changeset/31648>
08:45:00 CIA-10: martinl * r31649 /grass-addons/visualization/nviz2/cmd/ ( args.c change_view.c local_proto.h main.c ): nviz2/cmd: parameter for 'vertical exaggeration' added
08:46:24 sigq`: grassfeed: Changeset [31649]: nviz2/cmd: parameter for 'vertical exaggeration' added <https://trac.osgeo.org/grass/changeset/31649>
09:18:17 CIA-10: martinl * r31650 /grass-addons/visualization/nviz2/cmd/: svn:ignore prop defined for nviz2/cmd
09:19:10 sigq`: grassfeed: Changeset [31650]: svn:ignore prop defined for nviz2/cmd <https://trac.osgeo.org/grass/changeset/31650>
09:53:33 Manel: Hi everybody
09:56:52 Manel: after [ v.segment input="glines1@manuel" output="pts1" llayer=2 ] I get "pts1" without database
09:56:59 Manel: is that normal?
09:57:14 Manel: GRASS 6.2.2 ( admprojected ):~ > v.db.connect -p pts1
09:57:14 Manel: ERROR: Database connection for map <pts1> is not defined in DB file
12:38:48 Manel: Hi
12:39:02 WRichard: hello
12:39:38 Manel: I have a point layer with categorie, but without database
12:40:46 Manel: with "v.to.db -p map=gpoints1 type=point opt=cat" I can see the categories
12:41:15 Manel: but cannot put this categories in a table
12:42:38 Manel: i have tried to add a new table to the layer
12:43:41 Manel: with " v.category gpoints1 out=gpts1 layer=2 type=point opt=print "
12:44:59 Manel: then > v.db.addtable gpts1 layer=2 col="catnum integer"
12:46:41 Manel: and finally < v.to.db gpts1 layer=2 opt=cat col=catnum type=point
12:47:02 Manel: what ist wrong?
13:01:23 Manel: I do something wrong
18:16:03 : * _wolf_ is away