Re: [GRASS-user] grass 6.4.3 MSYS interface within windows 8

2013-06-13 Thread Hamish
Miltinho:
 how can I start msys console to run shell script mode within
 grass gis 6.4.3 on windows 8?

I haven't tried GRASS on Windows 8 myself, but from what I
understand there is a feature where you can type in what you
want to run and it will find the menu shortcut for you.

The Start Menu link you are looking for is called:

  GRASS GIS 6.4.3svn GUI with MSYS


the shortcut launches:
C:\Program Files\GRASS GIS 6.4.3svn\msys\msys.bat /grass/grass64svn.sh -wx

and is started from this directory:
C:\Program Files\GRASS GIS 6.4.3svn\msys


if all else fails I hear there are a number of 3rd party
addons to Windows 8 that restore the Start button and menus.


If you discover any secret tricks in getting it to work smoothly,
please let the list know.


regards,
Hamish
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user


[GRASS-user] Installing GRASS on Ubuntu: compilation error

2013-06-13 Thread RichardC
Hi,

I'm trying to install a GRASS7 from SVN into my home directory (I already
have 6.4.3 installed system wide), I'm following the guidelines at

http://trac.osgeo.org/grass/wiki/DownloadSource#GRASS7
http://grasswiki.osgeo.org/wiki/Compile_and_Install_Ubuntu#Compile_from_source


However, on running 'make' I get the following error.

If anyone might recognize the likely source of the errors, I'd be grateful. 


GRASS GIS 7.0.svn 56683 compilation log
--
Started compilation: Thu Jun 13 17:11:56 ICT 2013
--
Errors in:
/home/user/grass7/grass7_trunk/raster/r.external
/home/user/grass7/grass7_trunk/raster/r.in.gdal
/home/user/grass7/grass7_trunk/raster/r.out.gdal
/home/user/grass7/grass7_trunk/vector/v.out.ogr
/home/user/grass7/grass7_trunk/vector/v.in.ogr
/home/user/grass7/grass7_trunk/vector/v.external
--
In case of errors please change into the directory with error and run
'make'.
If you get multiple errors, you need to deal with them in the order they
appear in the error log. If you get an error building a library, you will
also get errors from anything which uses the library.
--
Finished compilation: Thu Jun 13 17:12:59 ICT 2013
make: *** [default] Error 1



Running make in the following error directories gives:

~/grass7/grass7_trunk/raster/r.external
/grass7/grass7_trunk/dist.i686-pc-linux-gnu/lib/libgrass_vector.7.0.svn.so:
undefined reference to `OGR_G_GetGeometryType@GDAL_1.8'




*Configure appears to go without a hitch:*

CFLAGS=-g -Wall LDFLAGS=-s ./configure --prefix=/home/user/grass7
--with-png=yes --with-libtiff=internal --with-geotiff=internal
--with-jpeg=internal --with-gif=internal --with-ecw=yes --with-expat=yes
--with-sqlite3=yes --with-geos=yes --with-python --with-libz=internal
--with-netcdf --with-sqlite --with-threads=yes --without-grass 
--without-ogdi --with-pg=/usr/bin/pg_config --with-xerces=yes
--with-freetype=yes --with-freetype-includes=/usr/include/freetype2/
--with-pg=/usr/bin/pg_config --with-readline --with-ffmpeg=yes
--with-ffmpeg-includes=/usr/include/libavcodec /usr/include/libavformat
/usr/include/libavutil /usr/include/libswscale --enable-largefile
--with-lapack --with-blas --with-postgres=yes
--with-postgres-includes=/usr/include/postgresql --with-mysql=no
--with-odbc=yes --with-python=yes --with-wxwidgets=/usr/bin/wx-config
--with-tcltk-includes=/usr/include/tcl8.5 --with-sqlite3=yes --with-cairo
--with-geos=/home/rcooper/grass7/bin
--with-gdal=/home/rcooper/grass7/bin/gdal-config --with-motif
--with-motif-includes=/usr/include
--with-proj-share=/home/rcooper/grass7/share/proj --with-cxx --enable-debug

...

GRASS is now configured for:  i686-pc-linux-gnu

  Source directory:   /home/user/grass7/grass7_trunk
  Build directory:/home/user/grass7/grass7_trunk
  Installation directory: ${prefix}/grass-7.0.svn
  Startup script in directory:${exec_prefix}/bin
  C compiler: gcc -g -Wall 
  C++ compiler:   c++ -g -O2
  Building shared libraries:  yes
  OpenGL platform:X11

  MacOSX application: no
  MacOSX architectures:   
  MacOSX SDK: 

  BLAS support:   yes
  C++ support:yes
  Cairo support:  yes
  DWG support:no
  FFMPEG support: yes
  FFTW support:   yes
  FreeType support:   yes
  GDAL support:   yes
  NETCDF support: yes
  GEOS support:   yes
  LAPACK support: yes
  Large File support (LFS):   yes
  libLAS support: no
  MySQL support:  no
  NLS support:no
  ODBC support:   yes
  OGR support:yes
  OpenCL support: no
  OpenGL support: yes
  OpenMP support: no
  PNG support:yes
  POSIX thread support:   no
  PostgreSQL support: yes
  Readline support:   yes
  Regex support:  yes
  SQLite support: yes
  TIFF support:   yes
  wxWidgets support:  yes
  X11 support:yes





--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Installing-GRASS-on-Ubuntu-compilation-error-tp5059904.html
Sent from the Grass - Users mailing list archive at Nabble.com.
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user


Re: [GRASS-user] grass 6.4.3 MSYS interface within windows 8

2013-06-13 Thread miltinhoastronauta .
Hi Hamish,

Thanks for your reply.
Worked for me pressing windows superkey button, and typing grass, all
options were available for click.

Best

milton

2013/6/13, Hamish hamis...@yahoo.com:
 Miltinho:
 how can I start msys console to run shell script mode within
 grass gis 6.4.3 on windows 8?

 I haven't tried GRASS on Windows 8 myself, but from what I
 understand there is a feature where you can type in what you
 want to run and it will find the menu shortcut for you.

 The Start Menu link you are looking for is called:

   GRASS GIS 6.4.3svn GUI with MSYS


 the shortcut launches:
 C:\Program Files\GRASS GIS 6.4.3svn\msys\msys.bat /grass/grass64svn.sh
 -wx

 and is started from this directory:
 C:\Program Files\GRASS GIS 6.4.3svn\msys


 if all else fails I hear there are a number of 3rd party
 addons to Windows 8 that restore the Start button and menus.


 If you discover any secret tricks in getting it to work smoothly,
 please let the list know.


 regards,
 Hamish



-- 
Miltinho - m...@rc.unesp.br
Laboratório de Ecologia Espacial e Conservação - LEEC
Depto de Ecologia - UNESP - Rio Claro
Av. 24A, 1515- Bela Vista
13506-900 Rio Claro, SP, Brasil

Fone: +55 19 3526-9647 (office)  19 3526-9680 (lab)
Cel: 19 9853-3220 / 19 9853-5430

Depto Ecologia http://www.rc.unesp.br/ib/ecologia/

PG ECO  BIODIV http://www.rc.unesp.br/ib/ecologia/posbiodiversidade/index.php

CV 
http://buscatextual.cnpq.br/buscatextual/visualizacv.do?id=K4792988H6mostrarNroCitacoesISI=truemostrarNroCitacoesScopus=true

Google citations http://scholar.google.com/citations?user=OWX_2eAJ
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user


Re: [GRASS-user] Installing GRASS on Ubuntu: compilation error

2013-06-13 Thread RichardC
Configure proceeds without error after removing
--with-gdal=/home/rcooper/grass7/bin/gdal-config

However, I receive the following error re running configure for
gdal-grass-1.4.3 $ ./configure \
  --prefix=/home/rcooper/grass7 \
  --with-gdal=/home/rcooper/grass7/bin/gdal-config \
  --with-grass=/home/rcooper/grass7/grass7_trunk/ \
  --with-autoload=/usr/local/lib/gdalplugins/ \
  --with-ld-shared=g++ -shared
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for ranlib... ranlib
using user supplied .so link command ... g++ -shared
user supplied gdal-config (/home/rcooper/grass7/bin/gdal-config)
using /usr/local/lib/gdalplugins/ as GDAL shared library autoload directory
checking for G_asprintf in -lgrass_gis... no
configure: error: --with-grass=/home/rcooper/grass7/grass7_trunk/ requested,
but libraries not found!  Perhaps you need to set LD_LIBRARY_PATH to include
/home/rcooper/grass7/grass7_trunk//lib?


I believe I can set the PATH by modifying .profile in Ubuntu.




--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Installing-GRASS-on-Ubuntu-compilation-error-tp5059904p5059973.html
Sent from the Grass - Users mailing list archive at Nabble.com.
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user


Re: [GRASS-user] Installing GRASS on Ubuntu: compilation error

2013-06-13 Thread Rashad M
Hi Richard,

I had the same problem sometime ago it was due to multiple gdal version
installed:
/usr/lib/
/usr/local/lib/

please see this thread -
http://lists.osgeo.org/pipermail/grass-dev/2013-May/063755.html


On Thu, Jun 13, 2013 at 9:23 PM, RichardC richtcoo...@hotmail.com wrote:

 Configure proceeds without error after removing
 --with-gdal=/home/rcooper/grass7/bin/gdal-config

 However, I receive the following error re running configure for
 gdal-grass-1.4.3 $ ./configure \
   --prefix=/home/rcooper/grass7 \
   --with-gdal=/home/rcooper/grass7/bin/gdal-config \
   --with-grass=/home/rcooper/grass7/grass7_trunk/ \
   --with-autoload=/usr/local/lib/gdalplugins/ \
   --with-ld-shared=g++ -shared
 checking for gcc... gcc
 checking for C compiler default output file name... a.out
 checking whether the C compiler works... yes
 checking whether we are cross compiling... no
 checking for suffix of executables...
 checking for suffix of object files... o
 checking whether we are using the GNU C compiler... yes
 checking whether gcc accepts -g... yes
 checking for gcc option to accept ANSI C... none needed
 checking for g++... g++
 checking whether we are using the GNU C++ compiler... yes
 checking whether g++ accepts -g... yes
 checking for ranlib... ranlib
 using user supplied .so link command ... g++ -shared
 user supplied gdal-config (/home/rcooper/grass7/bin/gdal-config)
 using /usr/local/lib/gdalplugins/ as GDAL shared library autoload directory
 checking for G_asprintf in -lgrass_gis... no
 configure: error: --with-grass=/home/rcooper/grass7/grass7_trunk/
 requested,
 but libraries not found!  Perhaps you need to set LD_LIBRARY_PATH to
 include
 /home/rcooper/grass7/grass7_trunk//lib?


 I believe I can set the PATH by modifying .profile in Ubuntu.




 --
 View this message in context:
 http://osgeo-org.1560.x6.nabble.com/Installing-GRASS-on-Ubuntu-compilation-error-tp5059904p5059973.html
 Sent from the Grass - Users mailing list archive at Nabble.com.
 ___
 grass-user mailing list
 grass-user@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/grass-user




-- 
Regards,
   Rashad
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user


Re: [GRASS-user] NDVI analyses with Landsat 8

2013-06-13 Thread Huub Munstege
Dear all,

in the following link I've uploaded an image that gives a bit more context 
information:

http://www.flickr.com/photos/hmunstege/9036837366/

The problem boils down to the different wavelength range of the the NIR band of 
Landsat 8. It's much narrower and applying the ndvi tools from Landsat 7 
doesn't give a clear image (see the image).
I am not a remote sensing expert, but we use frequently the ndvi index to 
monitor the exploitation of rice schemes along the Niger river in Mali. We 
would love to incorporate the Landsat 8 images in our analyses (without the 
'nodata scratches' of Landsat 7!)

Thanks in advance for your attention.


 


Huub Munstege
BPE 2836
Bamako, Rep. du Mali
Tel:  +223 20226397
Port: +223 78370695 





 De : Nikos Alexandris n...@nikosalexandris.net
À : Huub Munstege hmunst...@yahoo.com 
Cc : grass-user@lists.osgeo.org grass-user@lists.osgeo.org 
Envoyé le : Mercredi 12 juin 2013 21h58
Objet : Re: [GRASS-user] NDVI analyses with Landsat 8
 

Huub Munstege wrote:

 Hello Nikos,

Hello Huub!

 thx for the swift reply. I'll check out the options you mentioned but at
 first sight I noticed that 'i.vi' tool is not available for me ( I'am on
 6.4.3-rc, from the AUR package in Archlinux). I.vi is not a command in the
 'standard' Grass trunk. Neither is it available as an add-on.

Right!  Apologies from my side.  I have a setup giving access to all grass 
modules outside of a grass session [see link to GRASS-Wiki below] which, if 
not properly handled, as described in the wiki (strip paths), it even allows 
access to all grass70 modules from inside a grass64 session.

 Some more explanation as you asked: previous Landsat 7 images we analyzed
 with a simple raster calculation with the following formula:
 float(Band-4 - Band-3) / (Band-4 + Band-3).

I guess using grass64 means sticking to the formula above for NDVI.

 But as you already noticed the bands and ranges have changed under Landsat
 8. Various combinations of bands (4,5 and 8) give a result that is at best
 not so clear cut as the analysis done with L-7.

I didn't test any L8 so far, though I have downloaded some scenes.  Strange, 
in a way -- I would rather think that their improvements would improve S-N-R 
and, thus, derive better vegetation indices... :-?

 The bluntly subtraction with 0.12 is based on on a quick scan of the
 obtained result. Areas without vegetation in our project area should give
 values in the range between -0.05 - 0.

as per L7 data I guess...

 The result of the combination of the 5 and 4 bands in the above formula 
 gives values that are aprroximately 0.12 higher.

I see.  

 Therefore the blunt and in-elegant subtraction which is definitely wrong.
 But it gives us for the time being a better deistinction between cultivated
 irrigation schemes and their surroundings. Maybe I am simply too impatient
 and too eager to work with the new fresh data from L-8.

Sorry for asking again:  did you correct the data in some way or did you 
simply feed the formula with DNs?

 Undoubtedly soon, Grass and the other software will incorporate specific
 modules that will be tailored to the L-8 sensors.
 Cheers and keep up the good work,

Thank you for all of the details regarding your work.

Nikos
---


http://grasswiki.osgeo.org/wiki/Working_with_GRASS_without_starting_it_explicitly#Bash_examples_.28GNU.2FLinux.29

___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user


Re: [GRASS-user] Installing GRASS on Ubuntu: compilation error

2013-06-13 Thread Markus Metz
On Thu, Jun 13, 2013 at 12:35 PM, RichardC richtcoo...@hotmail.com wrote:
 Hi,

 I'm trying to install a GRASS7 from SVN into my home directory (I already
 have 6.4.3 installed system wide), I'm following the guidelines at

 http://trac.osgeo.org/grass/wiki/DownloadSource#GRASS7
 http://grasswiki.osgeo.org/wiki/Compile_and_Install_Ubuntu#Compile_from_source


 However, on running 'make' I get the following error.

 If anyone might recognize the likely source of the errors, I'd be grateful.


 GRASS GIS 7.0.svn 56683 compilation log
 --
 Started compilation: Thu Jun 13 17:11:56 ICT 2013
 --
 Errors in:
 /home/user/grass7/grass7_trunk/raster/r.external
 /home/user/grass7/grass7_trunk/raster/r.in.gdal
 /home/user/grass7/grass7_trunk/raster/r.out.gdal
 /home/user/grass7/grass7_trunk/vector/v.out.ogr
 /home/user/grass7/grass7_trunk/vector/v.in.ogr
 /home/user/grass7/grass7_trunk/vector/v.external
 --
 In case of errors please change into the directory with error and run
 'make'.
 If you get multiple errors, you need to deal with them in the order they
 appear in the error log. If you get an error building a library, you will
 also get errors from anything which uses the library.
 --
 Finished compilation: Thu Jun 13 17:12:59 ICT 2013
 make: *** [default] Error 1



 Running make in the following error directories gives:

 ~/grass7/grass7_trunk/raster/r.external
 /grass7/grass7_trunk/dist.i686-pc-linux-gnu/lib/libgrass_vector.7.0.svn.so:
 undefined reference to `OGR_G_GetGeometryType@GDAL_1.8'




 *Configure appears to go without a hitch:*

 CFLAGS=-g -Wall LDFLAGS=-s ./configure --prefix=/home/user/grass7
 --with-png=yes --with-libtiff=internal --with-geotiff=internal
 --with-jpeg=internal --with-gif=internal --with-ecw=yes --with-expat=yes
 --with-sqlite3=yes --with-geos=yes --with-python --with-libz=internal
 --with-netcdf --with-sqlite --with-threads=yes --without-grass
 --without-ogdi --with-pg=/usr/bin/pg_config --with-xerces=yes
 --with-freetype=yes --with-freetype-includes=/usr/include/freetype2/
 --with-pg=/usr/bin/pg_config --with-readline --with-ffmpeg=yes
 --with-ffmpeg-includes=/usr/include/libavcodec /usr/include/libavformat
 /usr/include/libavutil /usr/include/libswscale --enable-largefile
 --with-lapack --with-blas --with-postgres=yes
 --with-postgres-includes=/usr/include/postgresql --with-mysql=no
 --with-odbc=yes --with-python=yes --with-wxwidgets=/usr/bin/wx-config
 --with-tcltk-includes=/usr/include/tcl8.5 --with-sqlite3=yes --with-cairo
 --with-geos=/home/rcooper/grass7/bin
 --with-gdal=/home/rcooper/grass7/bin/gdal-config

This looks very much like you have a system-wide gdal installation and
a custom gdal installation in /home/rcooper/grass7/. It is nearly
impossible to have two different gdal installations on the same
system. gdal needs to be installed in a standard location such as
/usr/ or /usr/local/. If not, you should read first the manuals of
your compiler and your linker, before you 1) attempt to install gdal
in a non-standard location, 2) compile other software against gdal in
a non-standard location.

You should remove the gdal installation in /home/rcooper/grass7/ and
use the system-wide gdal installation.

Markus M


 --with-motif-includes=/usr/include
 --with-proj-share=/home/rcooper/grass7/share/proj --with-cxx --enable-debug

 ...

 GRASS is now configured for:  i686-pc-linux-gnu

   Source directory:   /home/user/grass7/grass7_trunk
   Build directory:/home/user/grass7/grass7_trunk
   Installation directory: ${prefix}/grass-7.0.svn
   Startup script in directory:${exec_prefix}/bin
   C compiler: gcc -g -Wall
   C++ compiler:   c++ -g -O2
   Building shared libraries:  yes
   OpenGL platform:X11

   MacOSX application: no
   MacOSX architectures:
   MacOSX SDK:

   BLAS support:   yes
   C++ support:yes
   Cairo support:  yes
   DWG support:no
   FFMPEG support: yes
   FFTW support:   yes
   FreeType support:   yes
   GDAL support:   yes
   NETCDF support: yes
   GEOS support:   yes
   LAPACK support: yes
   Large File support (LFS):   yes
   libLAS support: no
   MySQL support:  no
   NLS support:no
   ODBC support:   yes
   OGR support:yes
   OpenCL support: no
   OpenGL support: yes
   OpenMP support: no
   PNG support:yes
   POSIX thread support:   no
   PostgreSQL support: yes
   Readline support:   yes
   Regex support:  yes
   SQLite support: yes
   TIFF support:   yes
   wxWidgets support:  yes
   X11 support:yes





 --
 View this message in context: 
 

[GRASS-user] v.report produces corrupt table of attributes

2013-06-13 Thread Stuart Edwards

Hi --

This simple project involves digitizing and displaying the location of about 
200 borings. There is a pair of state plane co-ordinates and an alpha-numeric 
boring designator - and of course a cat - for each of them. The borings were 
duly digitized using v.digit in GRASS 7 (OS X) and after a number of edits 
(relocations, modification of some attributes, and some deletions) the file 
displays correctly using d.vect. It has also been satisfactorily exported as a 
shapefile as part of an effort to create a labeled dxf CAD layer.
However, v.report creates a table that appears to randomly (unlikely, I know, 
but that's how it appears) redistribute the pairs of co-ordinates among the 
points.
For example, at one boring location v.what generates:
v.what -a map=Borings@PERMANENT layer=-1 
coordinates=1791366.79821,765499.232745 distance=2
East: 1791366.79821
North: 765499.232745
Map: Borings
Mapset: PERMANENT
Type: Point
Id: 117
Layer: 1
Category: 142
Driver: sqlite
Database: /Users/stu/grassdata/270test/PERMANENT/sqlite/sqlite.db
Table: Borings
Key column: cat
cat : 142
boringnumber : B-9-004-13
However, v.report gives:
142|B-9-004-13|1793470.46145773|765224.666245354|0
for cat 142 which is the location of one of the other borings. Almost all of 
the borings are incorrectly identified in the v.report table. I tried v.build 
before running v.report but the results were the same.
Any assistance would be much appreciated as I would like to have an accurate 
table of these locations.

thx

Stu___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user