Dr. Southern,
Can you provide a link for the code you downloaded? I didn't find
it at GISCAN.
Thanks, Dave
--
David W. Roberts office 406-994-5670
Professor
Thanks Markus! I'll push this along.
On 5/15/21 3:01 PM, Markus Neteler wrote:
Dave, Ben,
Thanks to Anna and Tomas I now remember that the same happened in
Fedora as well (last year).
It seems that Arch/Manjaro are still missing this upstream fix for
wxPseudoDC.FindObjects crash:
Colleagues,
Finally, after probably a year I now have no errors about
incompatible versions of wxwidgets, wxpython, and GRASS. However, when
I execute
d.mon wx0
it pops up the box, but which then spontaneously disappears after about
10-15 seconds. It leaves behind the MONITORS/wx0
Michael, you define perseverance. Markus, you are extraordinarily
gracious with your time and expertise. This is a happy outcome that
demonstrates the depth of commitment of the GRASS community.
Bravo, Dave R.
On 12/23/20 4:39 PM, mdwxman via grass-user wrote:
GRASS GIS 7.8.5 exported
I compiled 7.8.3 from source successfully. However, I get an error when
tying to start a monitor
GRASS GIS 7.8.3 > d.mon wx3
Mapset in Location
GRASS GIS 7.8.3
> Traceback (most recent call last):
path problem but six.py is
clearly in /usr/local/grass78/gui/wxpython/mapdisp
Thanks in advance for any help, Dave Roberts
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
I compiled 7.8.3 from source successfully. However, I get an error when
tying to start a monitor
GRASS GIS 7.8.3 > d.mon wx3
Mapset in Location
GRASS GIS
7.8.3 > Traceback (most recent call last):
Thanks Helmut
v.extract demo cats=1-100 out=new
worked like a charm! Sorry I missed your point the first time.
Dave
On 11/27/16 23:46, Helmut Kudrnovsky wrote:
Thanks for the suggestion, but the area with no centroid doesn't
have a cat.
that's exactly what I've meant.
then do v.extract
Kudrnovsky wrote:
Dave Roberts wrote
After editing a map with wxgui I ended up with 39 areas and 38
centroids. How do I find and delete the area with no centroid?
I have tried many combinations of v.info, v.category, v.to.db, and
visualizing with d.vect. If I use v.clean tool=rmarea with slowly
After editing a map with wxgui I ended up with 39 areas and 38
centroids. How do I find and delete the area with no centroid?
I have tried many combinations of v.info, v.category, v.to.db, and
visualizing with d.vect. If I use v.clean tool=rmarea with slowly
increasing thresholds it gets
Thanks Anna. Wow, only two lines of code!
v.to.rast inp=new_mountains out=new_mountains attr=cat use=attr
r.univar map=srtm zones=new_mountains
Thanks, Dave
On 11/20/16 13:20, Anna Petrášová wrote:
On Sun, Nov 20, 2016 at 3:12 PM, Dave Roberts <drobe...@montana.edu> wrote:
Friends,
Friends,
I have succeeded (finally) in heads-up digitizing the mountain
ranges of the Rocky Mountains. Now I want to know the minimum and
maximum elevation for each range. I have a suitable DEM, but I cannot
figure out a combination or r.mapcalc or other that will give me this.
perhaps I'm alright.
Dave
On 11/19/16 11:45, Dave Roberts wrote:
Friends,
I recently made some changes to postgresql (deleted from package
manager and installed from source 9.5.1). It was a hassle because they
install in different locations and put the bin files in different
places, etc
Friends,
I recently made some changes to postgresql (deleted from package
manager and installed from source 9.5.1). It was a hassle because they
install in different locations and put the bin files in different
places, etc. It's all working now, except for GRASS, which seems to be
Hi Anna, yes I can create tickets now. I'll do that this weekend.
Thanks, Dave
On 11/18/16 10:03, Anna Petrášová wrote:
On Fri, Nov 18, 2016 at 10:41 AM, Dave Roberts <drobe...@montana.edu> wrote:
Friends,
I am trying to make use of the wxgui digitizer and finding it somewhat
chall
Friends,
I am trying to make use of the wxgui digitizer and finding it
somewhat challenging. One issue is that I like to run from the console
(i.e. grass73 -text) and that produces a subtly different widget than if
I run from the gui (i.e. grass73 -gui). Using the console version, when
I
Rich,
I'm working on a page for my tutorial on "GRASS for Ecologists"
called "Living with ESRI". Let me know how your project works out so I
can benefit from your experience.
Dave
On 10/27/16 11:13, Rich Shepard wrote:
Dave,
Yes, I have/had this; don't know if it's still on the
Rich,
I would look at the excellent MDB-tools package
(http://mdbtools.sourceforge.net). mdb-export will pull a specific layer
out of the mdb file. Unless it's a point coverage it's not going to
contain spatial data though, and even for point coverages it's rare to
the the point
Thanks Rich. Comments interspersed.
On 10/25/16 13:33, Rich Shepard wrote:
On Tue, 25 Oct 2016, Dave Roberts wrote:
So now when I see "geometry" in a manual page or GRASS-user posting I
interpret that to mean "vertices, nodes, centroids, and associated
cat
On 10/24/16 14:39, Markus Metz wrote:
On Mon, Oct 24, 2016 at 4:07 PM, Anna Petrášová <kratocha...@gmail.com> wrote:
On Mon, Oct 24, 2016 at 9:04 AM, Dave Roberts <drobe...@montana.edu> wrote:
Frequently in GRASS help files or emails in this list the term "geometry" is
used.
Frequently in GRASS help files or emails in this list the term
"geometry" is used. Is geometry synonymous with a record in the coor
file, or does it have a broader meaning?
Thanks, Dave
--
___
grass-user mailing list
grass-user@lists.osgeo.org
Anna,
Sorry, my two emails arrived in the wrong order due to some odd
behavior of the email system. Comments interspersed.
On 10/19/16 08:47, Anna Petrášová wrote:
On Wed, Oct 19, 2016 at 10:07 AM, Dave Roberts <drobe...@montana.edu> wrote:
Recent versions of GRASS (at least as
in a way I find confusing.
I would have expected that it would only influence the polygon I click
on, but often other polygons change color as well, depending on their
cat values in other tables.
Is there a way to turn this behavior off?
Dave Roberts
Actually, the highlight color depends on the map color scheme and isn't
always yellow.
Dave Roberts
--
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
of v.category will straighten all of this out.
In the meantime, I discovered that I could import layers from a GDB
individually with v.in.ogr, so all is well.
Dave
On 10/12/16 14:33, Helmut Kudrnovsky wrote:
Dave Roberts wrote
I'm having difficulty getting the wx devices to show vector
On 10/12/16 15:04, Dave Roberts wrote:
Indeed. I should have held out a little longer on canceling.
Dave
--
David W. Roberts office 406-994-4548
Professor and Head
Indeed. I should have held out a little longer on canceling.
Dave
--
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
Sorry, closing the query output widget works as well, so maybe that's as
intended.
Dave
On 10/12/16 13:29, Dave Roberts wrote:
In GRASS 7.3.svn (and maybe earlier) querying a polygon in an wx device
with your mouse highlights the polygon in yellow. However, the
highlight is too persistent
In GRASS 7.3.svn (and maybe earlier) querying a polygon in an wx device
with your mouse highlights the polygon in yellow. However, the
highlight is too persistent, i.e. a d.erase does not make it go away,
although the render map icon will clear it.
--
I'm having difficulty getting the wx devices to show vector features.
For example, I have a map called newveg. v.info clearly shows that
newveg has areas, e.g.
Number of points: 0 Number of centroids: 38183
Number of lines: 0 Number of boundaries: 97451
Number of areas:
into
GRASS source code and I wouldn't want to tackle this yet.
Thanks, Dave
On 10/04/16 06:32, Helmut Kudrnovsky wrote:
Dave Roberts wrote
Thanks Helmut, Thanks Anna
I compiled the trunk version, and the map query tool now clearly behaves
differently, but not how I expected
1) it shows all layers
Thanks Helmut, Thanks Anna
I compiled the trunk version, and the map query tool now clearly behaves
differently, but not how I expected
1) it shows all layers in the map query results, regardless of what
layer (if any) was selected in d.vect
I.e.
d.vect map
d.vect map layer=1
v.vect map
dniu 03.10.2016 o 23:18, Markus Neteler pisze:
On Mon, Oct 3, 2016 at 7:12 PM, Dave Roberts <drobe...@montana.edu>
wrote:
Hi Markus,
Given your kind offer I elected to try and compile GRASS again. This
time I was successful (after a few false starts). The primary
problem was
python con
on this rthread should probably have been switched to
Arch linux GRASS build, but I left it alone to allow tracking
On 10/03/16 15:18, Markus Neteler wrote:
On Mon, Oct 3, 2016 at 7:12 PM, Dave Roberts <drobe...@montana.edu> wrote:
Hi Markus,
Given your kind offer I elected to try and c
Thanks Moritz. This looks like the solution I was looking for.
However, I have not been successful at building GRASS from source for
quite a long time (just tried again and generated fatal errors in over
50 directories), so it will be a little while before I can test the
patch. At a first
Thanks Helmut,
On 10/02/16 02:53, Helmut Kudrnovsky wrote:
{material deleted for space ...}
it seems that d.what.vect [1] reports always all data of all layers.
the same with v.what although the queried layer is specified.
so maybe a bug/enhancement ticket is needed.
[1]
handles cats
(i.e. boundaries or centroids).
Just to check, you can have a look at this wiki entry :
https://grasswiki.osgeo.org/wiki/Vector_Database_Management#GRASS_GIS_vector_management_model
Best,
Vincent.
Le vendredi 30 septembre 2016 à 15:47 -0600, Dave Roberts a écrit :
d.vect has an option
d.vect has an option for layer= but I don't get any consistent effect
from the query tool in the map display. For example
GRASS GIS 7.0.4 > v.db.connect -p fuel
Vector map is connected by:
layer <1/LAB> table in database
through driver
with key
layer <2/ARC> table in database
through
Sadly, it's not just Microsoft users that take the GUI view. A couple
of years ago GRASS was reviewed in Linux Journal and they didn't even
mention it was scriptable. I wrote a letter to the editor to point that
out and they responded that that was minimally interesting.
Dave Roberts
On 09
I have a vector feature with four areas and two layers. Each of the
two layers is tied to a different sqlite table. I'm trying to make what
is currently layer 2 the default, and to delete the no longer needed
layer 1. I tried
v.category inp=new_ascii op=chlayer type=centroid layer=2,1
Paul,
On 09/06/16 16:28, Paul Kelly wrote:
The proj4 parameter in g.proj takes a PROJ string description, not a
file containing one.
So,
g.proj -c proj4="+proj=longlat +datum=WGS84"
should work, as far as I can think.
Indeed it does, and that seems to be the end of the line. So it's
. So, I'm still struggling for the
syntax of aproj4 file I guess.
Thanks all, Dave
On 09/06/16 14:37, Markus Neteler wrote:
Hi,
On Sep 6, 2016 9:25 PM, "Dave Roberts" <drobe...@montana.edu
<mailto:drobe...@montana.edu>> wrote:
Hi Ken, Hi Sajid,
Thanks for the
Sajid, I have no problem getting EPSG specs to work, but that's a lttle
too indirect for the audience I'm trying to reach.
Thanks, Dave
On 09/06/16 08:12, Ken Mankoff wrote:
On 2016-09-06 at 13:21, Dave Roberts <drobe...@montana.edu> wrote:
I'm trying to understand the simple
Dear All,
I'm trying to understand the simplest way in GRASS7 to create a
location from the command line without using a georeferenced file. So
far, it appears to be
% grass70 -c newLocation
at the OS prompt, followed by
GRASS GIS 7.0.4 > g.proc -c wkt=some WKT text file
inside of the
Friends,
I'm using GRASS 70-svn on Arch linux to generate figures for a
report. The general process is
1) GRASS - d.out.file format=png
2) xfig - import the PNG file, annotate, and export as PDF
3) TeX - import the file in a dvipdfm \special
However, I'm now having problems with
,
On Fri, Jul 18, 2014 at 1:56 PM, Dave Roberts
dvr...@ecology.msu.montana.edu mailto:dvr...@ecology.msu.montana.edu
wrote:
Friends,
I'm using GRASS 70-svn on Arch linux to generate figures for a
report. The general process is
1) GRASS - d.out.file format=png
2) xfig
boundary type=boundary col=white
Dave
On 06/17/2014 11:26 AM, Markus Neteler wrote:
Dave,
On Mon, Jun 16, 2014 at 9:59 PM, Dave Roberts
...
Then simply sh litho.sh would produce the reuslts I wanted, and if I
decided on a different color scheme it was a trival matter to edit the file
Dear all,
I frequently want a thematic map for a variable that is not numeric,
and thus not permisaable in d.vect.thematic. In the past a simple
solution was to write a shell script with d.vect commands. For example,
I could create a file called litho.sh with the following lines
d.vect
Friends,
Would it be possible to get d.what.vect back in GRASS 7? The
current query tool works OK if I don't have too many maps loaded, but it
oftern returns an extensive list of stuff I'm not interetsed in and
buries what I'm after.
E.g., if I execute multiple d.vect commands with
Friends,
Sorry, this DID work for points inside the polygon of interest.
I guess I was too tired.
Dave
On 05/30/2014 05:42 PM, Dave Roberts wrote:
Friends,
I am trying to drop random points through two vector maps to
establish the correspondence between them. I couldn't figure
Friends,
I am trying to drop random points through two vector maps to
establish the correspondence between them. I couldn't figure out how to
do that with v.random so I created a database table with 10,000 random
points within the bounds of the region, and then used v.in.db to bring
the
Johannes,
pvanb has a post on is blog about this. Look at
http://pvanb.wordpress.com/?s=lyr
It's a post from Feb 5
Dave
On 02/25/2014 06:07 AM, Johannes Radinger wrote:
Hi all,
just I short question. Although I don't think that is possible, but is
there a way to import/use a legend file
Ultimately had to recompile GRASS-6.4.3 to get d.mon to work again. The
make generated numerous errors, but much to my surprise make install
worked and solved my problem (at least for now).
Dave
On 02/21/2014 02:08 PM, Vaclav Petras wrote:
On Fri, Feb 21, 2014 at 4:06 PM, Dave Roberts
:
Thanks for the good words, Dave - no need for that!
Quick notes inline, it is already tomorrow here:
On Wed, Feb 19, 2014 at 11:52 PM, Dave Roberts
dvr...@ecology.msu.montana.edu wrote:
Hi Markus,
You're a saint. I'm at work right now, so I'll have to run the suggested
commands below when I get
at 11:58 PM, Dave Roberts
dvr...@ecology.msu.montana.edu wrote:
Markus,
Despite (or perhaps because of) downloading and installing new wxPython,
gdal, fftw, and others I have forgotten, compiling grass7_trunk generated
numerous errors. libgrass_gmath.7.0.svn.so compiled successfully
Friends,
I have broken my copy of GRASS 6.4.3. Impressed with the GRASS70
display, I foolishly tried
d.mon wx0
in GRASS64. It not only did not display, now no monitors exist, i.e.
GRASS 6.4.3 d.mon -l
no known monitors
It has affected all my locations, not just the one where I
Hi Martin,
Thanks. I do understand that. But now I have no X monitors (nor
png or anything else for that matter).
Dave
On 02/21/2014 09:18 AM, Martin Landa wrote:
Hi,
2014-02-21 17:10 GMT+01:00 Dave Robertsdvr...@ecology.msu.montana.edu:
d.mon wx0
in GRASS64. It not only did not
you don't mind.
On Fri, Feb 21, 2014 at 2:57 PM, Dave Roberts
dvr...@ecology.msu.montana.edu mailto:dvr...@ecology.msu.montana.edu
wrote:
Hi Vaclav,
Thanks for your help. I'm running Scientific Linux 6
(EL6-based). when I enter d.mon x0 it says there is no such monitor.
Isn't
Hi Hamish. Thanks for the help.
g.version -r returns 6.4.3
echo $GISBASE returns /usr/local/grass-6.4.3
echo $GRASS_LD_LIBRARY_PATH returns /usr/local/grass-6.4.3/lib
echo $LD_LIBRARY_PATH returns /usr/local/grass-6.4.3/lib
All good so far. However,
ls $GISBASE/lib shows no libgrass_gmath
Colleagues,
I'm trying to do a simple dissolve on a vector map and getting a
library error
v.dissolve inp=vmap out=dom_mid_60 column=dom_mid_60
. . .
. . .
v.extract: error while loading shared libraries:
libgrass_gmath.6.4.2.so:
?
Thanks, Dave
On 12/31/2013 06:00 PM, Dave Roberts wrote:
Colleagues,
I know this must be easy, but I haven't found it.
Suppose I have three grids (a, b, and c) where each grid is 0 or 1,
and the 1s are mutually exclusive. I want a new grid where if grid
a=1 then newgrid = 1; if grid b=1
to take it up in C with the API.
Thanks Tyler!
On 01/01/2014 09:56 AM, Tyler Smith wrote:
Dave Roberts dvr...@ecology.msu.montana.edu wrote:
Colleagues,
I know this must be easy, but I haven't found it.
Suppose I have three grids (a, b, and c) where each grid is 0 or 1,
and the 1s
Friends,
After some alternative approaches to a simple problem of
compositing rasters (see previous posts, esp. compositing rasters @9:32)
I developed a very crude function to update rasters
r.update target mask x y
updates raster target by substituting y everywhere that raster mask has
Hi Anna,
On 01/01/2014 01:50 PM, Anna Petrášová wrote:
Hi Dave,
On Wed, Jan 1, 2014 at 3:10 PM, Dave Roberts
dvr...@ecology.msu.montana.edu mailto:dvr...@ecology.msu.montana.edu
wrote:
Friends,
After some alternative approaches to a simple problem of
compositing rasters
Colleagues,
I know this must be easy, but I haven't found it.
Suppose I have three grids (a, b, and c) where each grid is 0 or 1,
and the 1s are mutually exclusive. I want a new grid where if grid
a=1 then newgrid = 1; if grid b=1 then new grid = 2; if grid c=1 then
newgrid = 3.
is madness.
Any ideas?
Thanks, Dave
On 11/26/2013 02:25 AM, Markus Metz wrote:
On Tue, Nov 26, 2013 at 3:39 AM, Dave Roberts
dvr...@ecology.msu.montana.edu wrote:
Friends,
I'm not exactly a newbie, but still yet quite naive in GRASS. This seems
like a simple problem, but I suspect unforeseen
I would suggest to run
v.category inp=geo type=centroid out=new_geo op=add layer=2 --o
Thanks Markus! Now I'm getting somewhere. v.info shows geo and new_geo
in perfect correspondence for areas, islands, boundaries, etc.
d.what.vect shows new_geo with the original data in layer 1 and
Markus,
Thanks a mill! I'll try that when I get back to that machine.
I really appreciate you time end expertise. You're a scholar and a
gentleman.
Dave
On 11/26/2013 08:48 AM, Markus Metz wrote:
On Tue, Nov 26, 2013 at 4:34 PM, Dave Roberts
dvr...@ecology.msu.montana.edu wrote
Markus,
v.to.db map=new_geo layer=2 column=surgeo option=query qlayer=1
qcolumn=surgeo
In this example, the column surgeo in layer 2 must exist and must be
of the same type like the column surgeo in layer 1.
the qcolumn actually had a different name, but with that small
correction this
Friends,
I'm not exactly a newbie, but still yet quite naive in GRASS. This
seems like a simple problem, but I suspect unforeseen problems with the
simple solution.
I have imported a surficial geology map from a shapefile. There are
1082 polygons. Each of the polygons with the same
Thanks Hamish. It seems only likely that such a routine would exist.
Here's the part where I need a little help though. It appears that
v.distance from=pnt to=area dmax=0 upload=cat column=areacat
will find and report the cat number of the polygon that points lie
within, and I can use that
Friends,
If I understand correctly (based on experience with my own data),
when GRASS calculates the topology for vector area data it doesn't
actually ensure that the centroid lies within the area it represents.
If the area is a torus, or at least hollow in a general way, then the
Friends,
This is the second time in two days I have had to post an apology
and retraction for hasty questions. I apologize for testing everyone's
patience. Thanks Markus; I was composing this message when I saw your
post. I mistook a centroid of a polygon too small to plot at the
the
file structures of GRASS vectors to attempt that in GRASS. If any
GRASS programmers are interested let me know and perhaps we could work
it out as an add-on.
Thanks, Dave R
Markus Metz wrote:
Dave Roberts wrote:
It does raise a question, however, of what the conditions
Friends,
I have an vector area map with numerous polygons with centroids. When I do
v.what.rast vector=A raster=B column=C
It appears to run, but doesn't actually enter any data into column C in
the associated table in Postgres. Reading the help file, I suspect this
is because A is an area
I'm working landform analysis using r.neighbors. The help file says
that size can go up to 25 (or +/1 12 pixels). I need much bigger
neighborhoods than that, so I just entered a large number and it seems
to work (although it's slow). Does anybody know what the true limits of
the r.neighbors
It appears that running r.neighbors with really large neighborhoods
results in mostly NULLs. A neighborhood of 31 seemed to work, but 51
returned only a tiny portion of the map.
Dave
--
David W. Roberts
Friends,
Sorry about an erroneous posting with respect to running
r.neighbors with large neighborhoods (51 in this case). My problem was
the current region, not r.neighbors which seesm to work fine with large
windows.
Dave
--
Fiends,
I'm a GRASS newbie trying to choose between GRASS6 and GRASS7 for a
new project. I'm working in R and PostgreSQL, but have lots of Arc
stuff to import.
I realize that GRASS7 did away with d.mon, but is there really no
replacement other than the full GUI? If I enter
79 matches
Mail list logo