Hi Aldo, Martin
In last week I to did some work with adding scale/north to a map.
using 6.4.svn (a couple of days behind update at time of post).
With python wx GUI
Found similar to Aldo, where adding scalebar seemed to be a 'once-off'
option, couldn't click on it etc to edit. using icon on
Silver wrote:
On 30/01/2012 09:52, Shane Litherland wrote:
Hi all,
I'm lost. I have looked around in GRASS for how to report the area (e.g.
in hectares) for a vector map that, yes, has area (i.e. centroids and
boundaries).
I cannot find a way to do this. A bit of web searching
Hi all,
yes,yesYES thank you for your inputs :-)
it was a simple case of me not having a table with the info in to start
with, so once i remedied that with v.to.db (hello old friend, where have
you been hiding?) reports and map queries were a breeze, as well as easy
calculations directly on the
Hi Andr,
You mention that you have streams of different 'order', does that mean
you have a table connected with a column containing a value for each bit
of stream (e.g. the river and tributaries are a combination of vector
lines, and each line between one stream junction and the next has a
Neteler wrote:
On Sat, Jan 21, 2012 at 5:44 AM, Shane Litherland
litherland-f...@bigpond.com wrote:
Hi Markus and mailing list;
I tackled the svn setup today. after several hrs of web browsing,
uninstalling old versions, and trying a few approaches to svn commands,
I think I have succeeded
Hi GRASSers,
I've just clarified something for myself, that I've only occasionally
noticed before because most of my work is with small vector files.
Starting to play with the North Carolina dataset highlighted this issue
for me again, as it has some 'larger' files in there (not that I'd
consider
Hi Markus and mailing list;
I tackled the svn setup today. after several hrs of web browsing,
uninstalling old versions, and trying a few approaches to svn commands,
I think I have succeeded. the 'info' under GRASS HELPABOUT GRASS GIS
now shows I have 'GRASS GIS 6.4.2svn50340 (2012)
A couple of
backported to the 6.4's.
-shane
On Wed, 2011-12-28 at 17:10 +0100, Anna Kratochvílová wrote:
Hi,
On Fri, Dec 23, 2011 at 11:50 PM, Shane Litherland
litherland-f...@bigpond.com wrote:
passing thought - is there a way to rename the display tabs (currently
just 'display 1', 'display 2' etc)? could
Hi Martin, Markus;
appreciate this guidance, I probably glossed over this tip somewhere in
the manuals, you've saved me a bit of study time. Now for me to put it
to use to help save you some time when it comes to deciphering my
problematic posts ;-)
Bear with me, I've got several paddocks worth
Hi again,
I mentioned in an earlier post when GRASS crashed, that I eventually
fixed via tcltk instead of wxgui, and found in the process a
single-point boundary in the area I'd been digitising prior to a crash.
I've found a few more times, that a single-point boundary gets
incorrectly created,
Hi all,
Note this is in the WXPYTHON GUI
I have been digitising vectors, using tools including add new boundary
or centroid, move vertex, delete vertex, split line, probably a few
others too.
Most of the time no problems, but I just had GRASS crash (all windows
disappeared, only the 'terminal'
Fellow GRASSers,
I have been playing/reading through vector classification, in the help
files under v.class, there is reference to d.area.thematic which
actually opens up a help page for d.thematic.area.
I was also looking via the wxgui search module, for either combination
of these tools,
Hi again,
here's some of my experience with the d.vect.thematic in 6.4.2RC2 wxgui:
I tried doing a basic process through the dialog i.e. select a map,
feature type=area, pick a column, 5 intervals, most of other settings
were default.
I ran it, and it showed the vector in thematic colouring, as
Hi all,
been busy away from computer last several weeks.
Last I posted, was playing with ~RC1, and noting several little
glitches, at least one of which I was supposed to file a bug report
on... :-/
Have dusted off my login etc for doing that, and just installed the ~RC2
OK it seems, from
Hi all,
this seems to be a serious thing!
wxGUI, ubuntu 10.04, GRASS 6.4.2RC2;
I created a new vector 'testing_vectors' for troubleshooting.
obviously it was empty to start with.
I chose 'digitize' from the listbox on top-right of map display window,
then selected the vector from listbox that
I found another case where the tool seems to not function fully:
A different vector to my earlier post, has for a given centroid:
layer 1: cats 4,5 and 107
layer 2: cat 40
I checked the connection to this info is fine within the wx digitiser
using the attributes tool there.
the query tool in
Another little query, am I using the 'copy categories' tool the wrong
way... instructions when selecting that tool say 'left click =select;
ctrl+left = unselect, right click=confirm'
I have tried several combos of left and right, e.g. select/confirm
source, select/confirm target; or select source,
on GRASS and a bunch of lost data... but if you want
them, I can get them
regards,
shane.
On Fri, 2011-11-18 at 11:19 +0100, Moritz Lennert wrote:
On 16/11/11 07:12, Shane Litherland wrote:
Hi all,
6.4.2RC1 on ubuntu 10.04.3, using wxgui
when digitising new vector, in 'digitisation settings
.
digitising a boundary and manually adding a centroid doesn't seem to
cause me this grief.
Any more sleuthing required at my end?
regards,
shane.
On Fri, 2011-11-18 at 11:23 +0100, Martin Landa wrote:
2011/11/16 Shane Litherland litherland-f...@bigpond.com:
6.4.2RC1 ubuntu 10.04.3 wxgui
Hi all,
just had an unsavoury experience for the second time since using wxgui
in 6.4.2RC1
when digitising a vector that consisted of boundaries and centroids, I
was attempting to split a boundary to add more adjacent
boundaries/centroids. somewhere in process of trying/learning to get the
hi all,
I had a similar oddity with two rasters that were in Albers Equal Area,
which should have overlapped but appeared to be about 1.5 hemispheres
apart... At first I thought the metadata may have been erroneous but
maybe there's something else afoot. I got around it by opening them in
6.4.2RC1 ubuntu 10.04.3 wxgui
Not as bad as it sounds though...only happened once so far.
At first, I thought it was because I may have had the 'no category' or
'don't save to table' settings ( a hangover from whatever I'd just
done), and when I used the area tool upon completion of a boundary
Hi all,
6.4.2RC1 on ubuntu 10.04.3, using wxgui
when digitising new vector, in 'digitisation settings' on 'attributes'
tab, I can play around with settings to add record to table, auto or
manual cat etc.
Noted that when cat mode is 'next to use' clicking the checkbox on/off
for 'add new record
Hi all,
I have a vector, with three layers each connected to a different table.
I heard about v.db.join and thought that would be a great tool, which it
is but it doesn't satisfy me for this purpose, as it seems to result in
the joined info displaying like one big table with all data from joined
for my system.
wx is 2.8.10.1 so that is same as what you have.
Cheers,
Shane.
On Thu, 2011-10-20 at 12:18 +0200, Martin Landa wrote:
Hi,
2011/10/20 Shane Litherland litherland-f...@bigpond.com:
any others find this too? ubuntu 10.04.3 64 bit, wxGUI python 2.6
seems to work for me. Debian
Hi Martin,
Thanks for comment. will look into it further, including checking
versions etc.
-shane.
On Thu, 2011-10-20 at 12:18 +0200, Martin Landa wrote:
Hi,
2011/10/20 Shane Litherland litherland-f...@bigpond.com:
any others find this too? ubuntu 10.04.3 64 bit, wxGUI python 2.6
seems
Hi Martin,
thanks for confirmation on query tool operation :-)
Further on the other issue (below):
A problem I find, is that some things I click on don't give results, I
get this sort of error:
Traceback (most recent call last):
File /usr/grass-6.4.2RC1/etc/wxpython/gui_modules/mapdisp
On Thu, 2011-10-20 at 12:47 +0200, Martin Landa wrote:
Hi,
2011/10/20 Shane Litherland litherland-f...@bigpond.com:
At first these three different ways to get to v.digit seemed a bit
there is only one way how to start v.digit (Tcl/Tk, from the menu) and
three ways how to reach wxGUI
Hi all,
On 6.4.2RC1, I have just played with v.db.join after seeing it suggested
for a use I thought would benefit me (I'd briefly looked at it on 6.4.1
before upgrade, had similar 'errors' there too).
when I open the dialog box for it (using wxpython GUI), from the listbox
I can select vector
Hi all,
in d.vect dialog, going to select colour for lines/fill, the colour
wheel can be moved around with mouse, but the colour chosen on the wheel
isn't recognised to start with by the dialog. I found I had to click on
the eye-dropper icon, then click the colour wheel with the eye-dropper
tool.
Hi all,
I have started grass wxGUI from a terminal, then open a saved workspace.
that workspace has,
vector 1
vector 2
vector 3
raster 1
in that order in layer manager.
vectors are some lines/boundaries/centroids/points, raster is a fairly
high-res aerial photograph.
All of these layers are
Hi again all,
In 6.4.1 wxGUI, I noticed that the query tool icon in map display gave
user an option to query (display mode) or query (edit mode) - the former
showed details in output window, the latter opened a dialog box allowing
view/edit of data in connected table.
now in 6.4.2RC1, there does
Hi all,
the wxGUI v.digit seems nice! a few things different to tcltk digitiser
to get used to but overall seems to have more versatility.
I have noticed that if I go to vector menu in main window, the option
there is for editing a vector with tcltk.
To use the wx option, one has to either
Hi again,
last night I was playing with the wxGUI digitiser, first time I've used
it (was not available in 6.4.1?)
In figuring out how select/commit worked a little different with mouse,
and how the display showed 'live' movements, I used the move/add/remove
vertex tools, the edit line/boundary,
hi all,
since successful compile of ~RC1, have noted in synaptic package manager
that it thinks libgdal1-1.8.0-grass is a broken package.
Note, this wouldn't have arisen if I had 6.4.1 AND the newer version, I
suppose? But having only 6.4.2RC1 is why the system is having a hissy
fit ;-) the
Hi all,
Still early days in test-driving it, but I managed to swim the deep
waters of compiling from source and I figured I have been successful
because I can type 'grass64' in a terminal and things happen :-)
FYI, below is what I did to 'build/configure/whatever-the-right-term-is'
on ubuntu
Hi all,
over last couple of weeks, wrote about problems with the GUI for d.vect
in wxpython. Basically, tweaking properties for vectors caused GRASS to
freeze after a few operations of d.vect dialog.
I have just been playing with d.vect in wxGUI and it seems to be working
well :-) I've done 3-4
Hi again all,
I'm trying i.ortho.photo from wxGUI to assess an earlier problem. So far
I have hit a similar error message when zooming after a few GCP's are
present, but I am wondering if I have done some things wrong in earlier
steps.
For entering camera position at step 6 for omega/phi/kappa,
] 2.6.32-34-generic #77-Ubuntu SMP Tue Sep 13
19:39:17 UTC 2011 x86_64 GNU/Linux
If you want to see how to 'reproduce' the problems I have, refer back to
earlier post/s.
Thanks :-)
shane.
On Tue, 2011-10-11 at 12:07 +0200, Martin Landa wrote:
Hi,
2011/10/11 Shane Litherland litherland-f
Hi Sebastian et al.,
I gathered from the original post, that you did manage to connect each
table, separately to the vector, using different layers, which I have
done myself several times.
I then gathered that this was not what you ideally wanted, and you then
proceeded to play with connection
Hi all,
I've known about this for awhile but worked around it. Maybe it's
already been reported, it's a small thing.
Using tcltk GUI (ver. 6.4.1), when I have a vector layer, some options
for settings include two icons to show table info - one prints column
names in the output, the other is
Hi all, and Martin FYI,
I see there's a 6.4.2RC release hot off the press. I've had a quick look
at info about it, there's a sizeable amount of things been done around
wxGUI/python, some of the stuff might still be on the wishlist for
backporting etc, but I'll try and install a separate GRASS of
Hi all,
So, I know one can have a 'working' GRASS and a 'try-if-you-dare' GRASS
on the one computer... a quick web search on how to do multiple grass
installs gave me more info on laying turf than on computing though!
The GRASS wiki has good info on compiling from source, but didn't see
anything
with the existing one.
Cheers,
Paulo
On Thu, Oct 13, 2011 at 2:33 PM, Shane Litherland
litherland-f...@bigpond.com wrote:
Hi all,
So, I know one can have a 'working' GRASS and a
'try-if-you-dare' GRASS
on the one computer... a quick web search on how
2011/10/13 Shane Litherland litherland-f...@bigpond.com
Hi all,
So, I know one can have a 'working' GRASS and a
'try-if-you-dare' GRASS
on the one computer... a quick web search on how to do
multiple grass
installs gave me more info
Hi all,
GRASS 6.4.1 on ubuntu 10.04 64 bit, tcltk GUI (because of other wxpython
probs previously reported)
Have been trying my hand at orthophoto georeferencing.
I started with a digital image that was taken with a digital aerial
camera. Has most of the camera settings required for the
at 15:40 +0200, Martin Landa wrote:
2011/10/10 Shane Litherland litherland-f...@bigpond.com:
Anyone know if newer versions of GRASS use python 2.6 or higher?
GRASS (wxGUI) should work with python2.4+ (including 2.6 or 2.7).
Python 3 is not supported.
Martin
I just came across something more in regards to python misbehaviour - it
may well be that GRASS 6.4.1 needs python 2.5 and ubuntu 10.04 has 2.6.
One website that outlined their success with GRASS after getting the 2.5
python version is
http://dipeshbhattarai.com/?p=57
(note they were using
Hi all,
With all quiet on the users emails on my subject, I went web-searching
and found some leads: The ubuntu desktop themes seemed to have an issue
reported for a range of programs that the GNOME/gtk settings needed
hacking/tweaking, see
Hi all,
in digging around for answers in regards to my 'd.vect problems I found
a post by Antonio from 14 April 2010:
.
Hi
I'm using GRASS6.4svn in an Ubuntu Machine and, when I start GRASS I
get
this warning at command line:
(python:3305): Pango-CRITICAL **: pango_layout_get_cursor_pos:
, http://csdc.asu.edu
On Sep 30, 2011, at 11:35 PM, Shane Litherland wrote:
Jim, et al.,
I am not an authority on GRASS, but it may not have been you that 'did
that' - if you were using an earlier version and did a significant
upgrade or a fresh install of a newer
Hi again all,
Took a break from computer, had a brilliant idea... ;-)
Tried running GRASS in good old skool tcltk GUI - it happily let me
query the map display, it happily accepted the sql 'where' clauses for
layer that the python gui ignored, and it happily let me change numerous
times, the
Jim, et al.,
I am not an authority on GRASS, but it may not have been you that 'did
that' - if you were using an earlier version and did a significant
upgrade or a fresh install of a newer version of GRASS, some fine
details like this might end up with new default values (?) I recall
doing a few
Hi all,
I had GRASS 6.4.0 from stable rep's for ubuntu lucid 64-bit, and it was
freezing when I opened the properties dialog for a vector layer. Worked
OK the first time I used it for a layer, but if I tried going back to
change things, everything just 'greyed out' and even after leaving it
for a
/9, Maciej Sieczka msiec...@sieczka.org:
W dniu 08.01.2011 06:01, Shane Litherland pisze:
Hi Maris,
Have braved my first attempt at filing a bug report, and appear to have
put enough together to generate a ticket
Ticket #1256
leftover node when deleting boundaries vertex-by-vertex
but i'd be stretching my computing skills there
too..
Regards,
Shane.
On Sun, 2011-01-09 at 20:39 +0100, Maciej Sieczka wrote:
W dniu 08.01.2011 06:01, Shane Litherland pisze:
Hi Maris,
Have braved my first attempt at filing a bug report, and appear
to have put enough together to generate
Hi again fellow GRASSers,
Just noticed this little issue (GRASS 6.4 on ubuntu 10.04)
I am digitising boundaries, using 'no category' option, then I digitise
centroids with 'next not used' and 'add to table', where I enter
relevant info for my postgres db table. That's all fine.
I then had a
Hi again,
another little thing I found by accident,
If digitising boundaries, then using 'remove vertex' to delete some of a
boundary, vertex-by-vertex... If I kept going and removed all the
vertexes (instead of the correct way of using 'delete
point/line/boundary'), it was possible to end up
while i'm on a roll with my complaining...
i've known about this one for a while, so probably others do too.
in the main v.digit monitor, or some of the GUI bits like 'attributes',
if I try to use the mouse scroll up/down wheel, i get an error pop up,
(or, if i wheel for more than one 'notch' of
report with exact step-by-step how to reproduce this issue.
http://trac.osgeo.org/grass
Maris.
2011/1/7, Shane Litherland litherland-f...@bigpond.com:
Hi again,
another little thing I found by accident,
If digitising boundaries, then using 'remove vertex' to delete some
Hi Hanlie,
I am getting out of my depth here, and might be leading you astray...
But I had a little challenge a few months ago, wanting to generate
points along a line to then use to create other tangent lines (in
science terms, generating belt-transects across a gully, at randomly
defined
Hiya,
I have no probs with my GRASS having been set up (on Ubuntu)
at /home/my-home/GIS/GRASSdata, which, for you, might be equivalent to
c:/users/path-to-your-folders/GIS... (sorry, haven't used that OS for
awhile)...
I'd also recently installed it on a colleagues laptop, I think they were
time in GRASS and come up with my next
'victim'.. I reckon I can give v.digit and its friends a good workout!
Regards,
Shane.
On Tue, 2010-12-07 at 12:03 +0200, Micha Silver wrote:
Shane Litherland wrote:
(my first-ever reply to the list...hope I get the cc / subject stuff
right
at
the source code (have figured out I can do that from source downloads,
yay!) I'll see if I can narrow this one down too..
Hope someone finds a bit of useful stuff in all that rambling!
regards,
shane.
On Fri, 2010-12-03 at 14:07 +0200, Micha Silver wrote:
On 12/02/2010 02:01 PM, Shane Litherland
hi all you GRASSers ;-)
not sure what happened when i first tried to join the mailing list a few
months ago, but i got my user/subscription sorted now :-)
I have been using GRASS for a couple years now, more consistently in the
last 12 months after a steady learning process. So hopefully as I
65 matches
Mail list logo
