On Wed, Jan 27, 2010 at 2:26 AM, Rich Shepard wrote:
> For the past few decades my geomorphic efforts have been related to the
> streams and river draining basins, not the terrestrial landforms themselves
> (other than hydrologic aspects). I'd appreciate some pointers to get me back
> to speed in
Manuel Seeger wrote:
> I'm using grass 7.svn (r39763) on ubuntu 9.10.
> Querying with v.what.vect I get the followng error:
>
>v.what.vect
> vector=zemmer_poi...@zemmer_som column=DRP
> qvector=drp_cl...@zemmer qcolumn=Prozess
> Traceback (most recent call last):
> File "/usr/local/gr
Alessandro wrote:
> I am just compiled GRASS grass-6.4.0RC5 from source and I
> am experiencing some trouble with g.region
>
> g.region -p
> ERROR: region for current mapset is invalid
> missing>
>run "g.region"
>
>
> I understand that this is bug that has been highlighted
> some
On Wed, 27 Jan 2010, Markus Neteler wrote:
Can you please try with the latest 6.4.SVN snapshot?
http://grass.osgeo.org/grass64/source/snapshot/
... and report back?
Markus,
I, too, was hit with this error earlier this afternoon. I was trying to
run r.slope.aspect on a 1m DEM and kept getti
On Wed, Jan 27, 2010 at 2:54 AM, Alessandro Bertan
wrote:
> Dear grass users,
>
> I am just compiled GRASS grass-6.4.0RC5 from source and I am
> experiencing some trouble with g.region
>
> g.region -p
> ERROR: region for current mapset is invalid
>
> run "g.region"
>
>
> I understand
Tim Michelsen schrieb:
> > > what do the inputs for i.sunshine in GRASS7 mean?
> > >
> > > i.sunhours doy=name lat=name
> >
Achim:
> > I guess
> >
> > doy = day of year
> >
> > lat = latitude
> >
> > While doy in (1-365)
> > And lat in (0-90)?
> >
> > Should be. But why "name"??
>
Timmie:
> I
Dear grass users,
I am just compiled GRASS grass-6.4.0RC5 from source and I am
experiencing some trouble with g.region
g.region -p
ERROR: region for current mapset is invalid
run "g.region"
I understand that this is bug that has been highlighted some months ago:
http://trac.osge
I successfully cut out of the source DEM a small area matching that of the
project watershed. When I ran r.slope.aspect the output maps looked as they
should.
Feeling irrationally exuberant that I might be able to quickly move on to
hydrological modeling, I just tried running r.shaded.relief
For the past few decades my geomorphic efforts have been related to the
streams and river draining basins, not the terrestrial landforms themselves
(other than hydrologic aspects). I'd appreciate some pointers to get me back
to speed interpreting the output maps from r.slope.aspect.
TIA,
Rich
On Tue, 26 Jan 2010, Glynn Clements wrote:
You could try repeating the cropping process, using g.region's align=
option to align the grid to the source map.
Glynn,
FIXED the problem.
I re-ran 'r.mapcalc "aberDEM=demNW"' and it cleaned up all the problems.
r.slope.aspect produces output m
On Tue, 26 Jan 2010, Rich Shepard wrote:
Now I cannot find my notes on how I cropped the larger DEM to the
boundary of the project area. I know that v.overlay works on two vector
maps but ... I've dropped the ball on that operation.
Found it!
r.mapcalc "newmap=oldmap"
Rich
_
On Tue, 26 Jan 2010, Glynn Clements wrote:
You could try repeating the cropping process, using g.region's align=
option to align the grid to the source map.
Now I cannot find my notes on how I cropped the larger DEM to the boundary
of the project area. I know that v.overlay works on two vect
Wow that is amazing, thanks so much Martin.
-Colin
2010/1/19 Martin Landa :
> Hi,
>
> I have set up regular WinGRASS builds, currently for 6.4.svn and
> 6.5.svn (built daily). Servers kindly provided by CTU in Prague.
>
> http://josef.fsv.cvut.cz/wingrass/
>
> Enjoy! Martin
>
> --
> Martin Landa
On Tue, 26 Jan 2010, Glynn Clements wrote:
It's possible that the cropping may have changed the grid slightly.
Glynn,
I do hope it's something simple. I can't do more until I have a good DEM
map for the project area.
What are the grid parameters (bounds, resolution, rows/cols) for the
sou
> front-end, LyX, to be much quicker and more productive than writing
> LaTeX in
> emacs. So I'm not totally averse to using the pointy-thingie when it's
> demonstrably more productive. :-)
The same applies to the new GRASS GUI.
It's awesome and once you get acustomated pretty useful.
You may wanna
On Tue, 26 Jan 2010, Hamish wrote:
6.5 may be fine for day to day work, but "production runs" I strongly
recommend a versioned stable release. If for no other reason than to
publish with reproducible results.
Hamish,
Thank you. This fully answers my question.
Much appreciated,
Rich
__
Rich wrote:
> A couple of module features I
> want to use are in 6.5 and that version is
> for back porting of changes to 6.4.0. Should I continue to
> use 6.5 or should I periodically get the weekly snapshot of 6.4.0 and
> rebuild?
It depends on if you are willing to help test and diagnose pot
Rich wrote:
> Source metadata:
>
> Map_Projection:
> Map_Projection_Name: Lambert Conformal Conic
> Lambert_Conformal_Conic:
> Standard_Parallel: 43.00
> Standard_Parallel: 45.50
>
> Longitude_of_Central_Meridian: -120.50
> Lati
Rich Shepard wrote:
>The source originally-imported DEM produces appropriate slope and aspect
> maps. The sub-region I cut out with v.in.region (I believe that's the module
> I used) doesn't calculate properly. Therefore, the problem is with the
> sub-map.
It's possible that the cropping may
On Tue, 26 Jan 2010, Glynn Clements wrote:
2. Upsampling the source data with e.g. r.resamp.interp.
Glynn,
When would one use r.resamp.interp and when r.resamp.rst? The latter
incorporates functions of r.slope.aspect with the resampling/resolution
change, but what decision criteria guide wh
On Tue, 26 Jan 2010, Glynn Clements wrote:
First, the current region's grid should at least match that of the
input map, and ideally of the original data.
Glynn,
The number of rows and columns has been changed but not the resolution. At
least, not deliberately.
If the data has been resamp
Rich Shepard wrote:
>I believe that I asked about this before but I don't have the thread
> saved, and I don't know where the mail list is archived.
>
>I have a 10m DEM and tried running r.slope.aspect on it. The output files
> (one each for slope and aspect) look like static divided int
On Tue, 26 Jan 2010, Rich Shepard wrote:
I have a 10m DEM and tried running r.slope.aspect on it. The output files
(one each for slope and aspect) look like static divided into square cells.
The same problem occurs when I refine the resolution to 1m. I believe that
Markus N. wrote a comment abo
On Tue, 26 Jan 2010, Rich Shepard wrote:
I followed the instructions on the Wiki page but something's missing. Do
I need to rebuild grass64 first?
The README.txt file in the r.inund.fluv directory showed me what to do: 'cd
/usr4/grass64' and 'make install'.
Rich
__
I downloaded the r.inund.fluv tree from the svn server and built using
'make MODULE_TOPDIR=/usr4/grass64/'. All went well ... until I tried to
install it.
The error message is:
/usr/bin/ginstall -c /usr4/grass64/dist.i686-pc-linux-gnu/bin/r.inund.fluv
/usr/local/grass-6.4.0svn/bin/
/usr/bin
A couple of module features I want to use are in 6.5 and that version is
for back porting of changes to 6.4.0. Should I continue to use 6.5 or should
I periodically get the weekly snapshot of 6.4.0 and rebuild?
Thanks,
Rich
___
grass-user mailing lis
I believe that I asked about this before but I don't have the thread
saved, and I don't know where the mail list is archived.
I have a 10m DEM and tried running r.slope.aspect on it. The output files
(one each for slope and aspect) look like static divided into square cells.
The same problem
ersion of GRASS is a relatively
recent feature, and may still have bugs.
__ Information from ESET NOD32 Antivirus, version of virus signature
database 4807 (20100126) __
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
__
On Tue, 26 Jan 2010, Rebecca Bennett wrote:
db.connect -p shows
driver:sqlite
database:$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite
schema:
group:
Rebecca,
Allow me to suggest that you name your SQLite databases by project,
location, or other unique identifier. Naming the database with the
appl
António Rocha wrote:
> The thing is that I went here:
> http://trac.osgeo.org/grass/browser/grass/trunk/doc/raster and I
> donwloaded the r.example that is there.
> At least I didn«t saw any information regarding GRASS version :(.
>
> Now I realize thatr the trunk relates with 7.0 version and
OK I think I have cracked this by removing the quotation marks from the
column descriptors in the command :blush:. I now have a point file with
attributes and a database that works (hopefully).
Many thanks to all who contributed suggestions,
Rebecca
--
View this message in context:
http://n2.n
Hi all,
I would like to have all commands issued and all command output
recorded as it was available with the TCL/TK-based GIS Manager in a
separate console window but with the wxgui.
I expected it can be provided in the command output window tab, but I
have not found how it can be set to do that
OK, sorry I spotted an obvious error looking at that again. Removing the
extra "columns=" I ran the command again
v.in.ascii -z -n input=/home/rebecca/lidar/08.txt output=test_08_attribute
format=point {fs= } skip=0 {columns= 'x double precision, y double
precision, z double precision, i double
Genius, thanks for that suggestion Mark!
Having changed the database to have a .db at the end I re-ran the import,
getting the following output and error
"Scanning input for column types...
Maximum input row length: 35
Minimum number of columns: 4
Maximum number of columns: 4
DBMI-SQLite dri
M S wrote:
Looking at mine, the only difference I see is that the name of the
database is missing a ".db" extension. Please let me know if that
makes a difference.
For the sqlite driver, the database must be a file, not a directory. The
GRASS standard is sqlite.db I think. I would delete th
Looking at mine, the only difference I see is that the name of the
database is missing a ".db" extension. Please let me know if that
makes a difference.
Mark
On Tue, Jan 26, 2010 at 9:09 AM, Rebecca Bennett wrote:
>
> Hi Mark
>
> db.connect -p shows
>
> driver:sqlite
> database:$GISDBASE/$LOCAT
Hi Mark
db.connect -p shows
driver:sqlite
database:$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite
schema:
group:
Rebecca
--
View this message in context:
http://n2.nabble.com/Help-with-importing-points-and-their-attributes-tp4460359p4460798.html
Sent from the Grass - Users mailing list archive at Na
What does 'db.connect -p' show?
Mark
On Tue, Jan 26, 2010 at 9:02 AM, Rebecca Bennett wrote:
>
> Dear Sela,
>
> Thank you for your advice. I have re-run the import having corrected the
> format as you suggest, using the command below:
>
> v.in.ascii -z -n input=/home/rebecca/lidar/08.txt output=
Dear Sela,
Thank you for your advice. I have re-run the import having corrected the
format as you suggest, using the command below:
v.in.ascii -z -n input=/home/rebecca/lidar/08.txt output=test_08_attribute
format=point {fs= } skip=0 {columns=columns= 'x double precision, y double
precision, z d
António Rocha wrote:
> /home/anrr/Downloads/grass-6.4.svn_src_snapshot_2010_01_16-2/dist.i686-pc-linux-gnu/include/grass/nviz.h:21:69:
> error: X11/Xmu/StdCmap.h: No such file or directory
debian$ apt-file search X11/Xmu/StdCmap.h
libxmu-headers: /usr/include/X11/Xmu/StdCmap.h
apparently you st
Uopps. I thought I could only do that before "make install" :)
Even so, when I run "make" at
/home/anrr/Downloads/grass-6.4.svn_src_snapshot_2010_01_16-2/lib/nviz I got the
following error:
a...@vpc-anrr:~/Downloads/grass-6.4.svn_src_snapshot_2010_01_16-2/lib/nviz$ makegcc
-I/home/anrr/Downlo
Greetings Glynn
The thing is that I went here:
http://trac.osgeo.org/grass/browser/grass/trunk/doc/raster and I
donwloaded the r.example that is there.
At least I didn«t saw any information regarding GRASS version :(.
Now I realize thatr the trunk relates with 7.0 version and in Branches I
c
On Tuesday 26 January 2010 02:13:28 stephen sefick wrote:
> I have a rather large map that I need to fill the null values in. I
> have compiled grass 6.5. Any help would be greatly appreciated. Is
> this the proper way to go about this?
>
> r.fillnulls --overwrite input=ft_bragg_lidar_2009
> ou
On Mon, 25 Jan 2010, Hamish wrote:
Roger wrote:
PS. Where is v.to.rast on the wx menu system?
in the wx GUI try:
Help -> Show menu tree
then
Search: [command]
then type in v.to.rast
Regretably, on my 6.4.0RC5, there are only GRASS GIS Help, GRASS GIS GUI
Help, and About GRASS GIS to c
Fixed in all branches r40656-9
Markus M
Jaros?aw Jasiewicz wrote:
Margherita Di Leo pisze:
Hi list!
I often used r.watershed without problems, but today i had a very
strange one. Please can anyone verify that?
I used Spearfish mapset, map: elevation.10m:
g.region res=100
r.watershed eleva
45 matches
Mail list logo
