Re: [GRASS-user] G7: r.random problems with creation of vector points

2013-09-04 Thread Markus Metz
On Tue, Aug 27, 2013 at 1:08 PM, Johannes Radinger
 wrote:
> Hi,
>
> I am running the latest revision of GRASS7 (rev 57514). When I try to create
> random vector points based on a raster map input using the tool r.random I
> get something
> very weird but definitely no vector points. I seems that the points are
> somehow lines.
>
> Here what I am doing (tested with absolute n and with %n):
> r.random input=river_raster n=2 vector_output=source_points_test

Can you check with v.info if there is anything else but points in the
vector source_points_test?

>
> Is there anything I a doing wrong or is this a bug in r.random?
> Maybe someone can test that. Thank you!

I could not reproduce this with nc_spm data using a stream network
derived from elev_lid792_1m.


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


Re: [GRASS-user] GRASS and libgeos 3.1.1/3.3.3

2013-09-04 Thread Gary Nobles
Hi Hamish, thank you for your help
I renamed the libgdal.so links in /usr/lib/ to xlibgdal and now grass works
again, that was the problem!



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/GRASS-and-libgeos-3-1-1-3-3-3-tp5075764p5076000.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 and libgeos 3.1.1/3.3.3

2013-09-04 Thread Gary Nobles
$ ldd libgdal.so.1 | grep geos
libgeos_c.so.1 => /usr/lib/libgeos_c.so.1 (0x7f8652f4b000)
libgeos-3.1.1.so => not found
libgeos-3.3.3.so => /usr/lib/libgeos-3.3.3.so (0x7f864f8f6000)
$ ldd libgdal.so | grep geos
libgeos_c.so.1 => /usr/lib/libgeos_c.so.1 (0x7fc26729a000)
libgeos-3.1.1.so => not found
libgeos-3.3.3.so => /usr/lib/libgeos-3.3.3.so (0x7fc263c45000)
$ ldd /usr/lib/grass64/lib/libgdal.so | grep geos
libgeos_c.so.1 => /usr/lib/libgeos_c.so.1 (0x7fef3a3de000)
libgeos-3.3.3.so => /usr/lib/libgeos-3.3.3.so (0x7fef337a7000)

So it is the gdal which is causing te conflict?
How do I uninstall it? just delete the libgeos files?



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/GRASS-and-libgeos-3-1-1-3-3-3-tp5075764p5075993.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 and libgeos 3.1.1/3.3.3

2013-09-04 Thread Hamish
Gary wrote:

> the -d has caused it to use the development version! But as GRASS had the
> same problem with 12.10 this shouldnt be the source of the main problem, is
> there anyway to revert to the 1.9.0-3.1ubuntu1?

I suspect the immediate problem is the extra+outdated GDAL version in
/usr/local/. It would be strange if a newer version of the GDAL ubuntu
package were depending on an older version of GEOS, right?

In addition, I don't see GEOS 3.1.1 available in any of the recent
ubuntu versions, so suspect the /usr/local/ custom installed version
is to blame for the bulk of the trouble.
  http://packages.ubuntu.com/search?keywords=libgeos


You can use "ldd" on the libraries found with:

$ locate libgdal | grep '\.so'

to verify which one(s) are looking for libgeos 3.1.1.

e.g.
$ ldd /usr/lib/libgdal.so.1 | grep geos
$ ldd /usr/lib/grass64/lib/libgdal.so | grep geos


Hamish

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


Re: [GRASS-user] GRASS and libgeos 3.1.1/3.3.3

2013-09-04 Thread Gary Nobles

apt-cache policy libgdal1 
libgdal1:
  Installed: 1.9.0-3.1ubuntu4
  Candidate: 1.9.0-3.1ubuntu4
  Version table:
 *** 1.9.0-3.1ubuntu4 0
500 http://archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages
100 /var/lib/dpkg/status

I had the problem with Grass in 12.10, so I upgraded to 13.04 using the
do-release-upgrade -d

the -d has caused it to use the development version! But as GRASS had the
same problem with 12.10 this shouldnt be the source of the main problem, is
there anyway to revert to the 1.9.0-3.1ubuntu1?



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/GRASS-and-libgeos-3-1-1-3-3-3-tp5075764p5075955.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 and libgeos 3.1.1/3.3.3

2013-09-04 Thread Gary Nobles
>... /usr/local/lib/libgdal.so.1 ? Did you have a custom installed version
>of GDAL in /usr/local? That may be the conflict. 

in this directory is the libgdal.so.1 file and libgdal.so file, both link to
a shared library libgdal.so.1.13.2 which is also in this directory

dir /usr/local/lib/ contents:
Python (dir)
R (dir)
libgdal.a (AR archive)
site_ruby (dir)

libgdal.la
libgdal.so
libgdal.so.1
libgdal.so.1.13.2

Does this help?



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/GRASS-and-libgeos-3-1-1-3-3-3-tp5075764p5075952.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 and libgeos 3.1.1/3.3.3

2013-09-04 Thread Hamish
> Gary wrote:

>>  dpkg -l | grep libgdal
>> 
>>  ii  libgdal1             1.9.0-3.1ubuntu4   amd64        Geospatial Data
>>  Abstraction Library
> 
> ok, same as me & 13.04,
>   http://packages.ubuntu.com/search?suite=raring&keywords=libgdal

er, hang on: you've got 1.9.0-3.1ubuntu4? 

me & ubuntu 13.04 have 1.9.0-3.1ubuntu1.


The 1.9.0-3.1ubuntu4 package looks like it comes from Saucy Salamander
(aka 13.10) which isn't released yet, due next month:
   http://packages.ubuntu.com/search?suite=all&keywords=libgdal

? any clues about the ubuntu version in /etc/apt/sources.list and 
/etc/apt/sources.list.d/ ?


what does this say about installed vs. available GDAL versions:

$ apt-cache policy libgdal1

?

Hamish

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


Re: [GRASS-user] GRASS and libgeos 3.1.1/3.3.3

2013-09-04 Thread Hamish
Gary wrote:

> dpkg -l | grep libgdal
> 
> ii  libgdal1             1.9.0-3.1ubuntu4   amd64        Geospatial Data
> Abstraction Library

ok, same as me & 13.04,
  http://packages.ubuntu.com/search?suite=raring&keywords=libgdal


> rc  libgdal1-1.5.0   1.5.4-4                 amd64        Geospatial Data
> Abstraction Library
> rc  libgdal1-1.6.0   1.6.3-3build2         amd64        Geospatial Data
> Abstraction Library
> rc  libgdal1-1.7.0   1.7.3-6ubuntu3      amd64        Geospatial Data
> Abstraction Library

(all removed)
 
> ldd /usr/lib/grass64/bin/g.proj | grep geos
> 
> /usr/lib/grass64/bin/g.proj: /usr/local/lib/libgdal.so.1: no version
> information available (required by /usr/lib/grass64/bin/g.proj)

... /usr/local/lib/libgdal.so.1 ? Did you have a custom installed version
of GDAL in /usr/local? That may be the conflict.

 
> libgeos_c.so.1 => /usr/lib/libgeos_c.so.1 (0x7fed2e466000)
> libgeos-3.1.1.so => not found
> libgeos-3.3.3.so => /usr/lib/libgeos-3.3.3.so (0x7fed2b4dc000)
> 
> So the problem is with the absense of 3.1.1, any way to tell grass to only
> use 3.3.3? 

I think it's actually GDAL which wants GEOS 3.1.1, the problem comes
along to GRASS through there when GRASS loads in GDAL.

> All this happened after upgrading ubuntu and upgrading packages,

I'd heard it prefers fresh installs to in-place upgrades, but I've never
tried it myself.

> I hadn't checked grass for a few months until I came to use it, it
> would be nice to get to my PhD data! I have backed up the mapsets on
> another drive,

I'd be confident that your data is ok, GRASS can be loaded onto any other
computer of opportunity to access it in an emergency.

> I tried completely removing grass and reinstalling but it didnt solve
> the problem.

Look for files related to an old GDAL version in the /usr/local/ dirs.


regards,
Hamish

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


Re: [GRASS-user] GRASS and libgeos 3.1.1/3.3.3

2013-09-04 Thread Gary Nobles
Hi Hamish,

dpkg -l | grep libgdal

ii  libgdal1 1.9.0-3.1ubuntu4   amd64Geospatial Data
Abstraction Library
rc  libgdal1-1.5.0   1.5.4-4 amd64Geospatial Data
Abstraction Library
rc  libgdal1-1.6.0   1.6.3-3build2 amd64Geospatial Data
Abstraction Library
rc  libgdal1-1.7.0   1.7.3-6ubuntu3  amd64Geospatial Data
Abstraction Library

ldd /usr/lib/grass64/bin/g.proj | grep geos


/usr/lib/grass64/bin/g.proj: /usr/local/lib/libgdal.so.1: no version
information available (required by /usr/lib/grass64/bin/g.proj)

libgeos_c.so.1 => /usr/lib/libgeos_c.so.1 (0x7fed2e466000)
libgeos-3.1.1.so => not found
libgeos-3.3.3.so => /usr/lib/libgeos-3.3.3.so (0x7fed2b4dc000)


So the problem is with the absense of 3.1.1, any way to tell grass to only
use 3.3.3? 

All this happened after upgrading ubuntu and upgrading packages, I hadn't
checked grass for a few months until I came to use it, it would be nice to
get to my PhD data! I have backed up the mapsets on another drive, I tried
completely removing grass and reinstalling but it didnt solve the problem.
Thanks for your help

Gary



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/GRASS-and-libgeos-3-1-1-3-3-3-tp5075764p5075928.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] i.landsat.toar comments have only 0 value

2013-09-04 Thread Nikos Alexandris
On Friday 30 of August 2013 02:56:14 Beatrice wrote:

> Dear All,

Good Day Beatrice,

 
> I have been running i.landsat.toar but have just noted this problem. For me
> it shows zeros both in the command output (verbose) and output metadata
> (r.info). An example for one of the bands:

 
> From command output:
> 
>  LANDSAT: 5 SENSOR: TM
>  ACQUISITION DATE 2011-07-05 [production date 2011-11-29]
>Earth-sun distance= 0.
>Solar elevation angle = 0.
>Atmospheric correction = dos4
>Percent of solar irradiance in path radiance = 0.
> ---
>  BAND 1  (code 1)
>calibrated digital number (DN): 0.0 to 0.0
>calibration constants (L): 0.000 to 0.000
>at-surface radiance = 0. * DN + -0.000
>mean solar exoatmospheric irradiance (ESUN): -0.000
>at-surface reflectance = radiance / 0.0
>the darkness DN with a least 1000 pixels is 1
>the DN mode is 53
> ---


> From r.info for the same band:
>  | Earth-sun distance (d)  -0.
>  | 
>  | Digital number (DN) range . 0 to 0
>  | 
>  | Calibration constants (Lmin to Lmax) .. +0.000 to +0.000
>  | 
>  | DN to Radiance (gain and bias)  +0.0 and +0.0
>  | 
>  | Mean solar irradiance (ESUN) .. 0.000
>  | 
>  | Reflectance = Radiance divided by . 0.0
>  | 
>  | 
>  | 
>  | Dark object (1000 pixels) DN =  1
>  | 
>  | Mode in reflectance histogram . 0.0


This doesn't look healthy.  However, I think it is a past problem which is 
fixed.

 
> Running i.landsat.toar -p results to
> 
> number=5
> creation=2011-11-29
> date=2011-07-05
> sun_elev=45.585310
> sensor=TM
> bands=7
> sunaz=44.259879
> 
> Which I think confirms that i.landsat.toar can read input values from my
> metafile. The output bands have values in the range of surface
> reflectance/temperature (for band 6). For example
> 
> Band 1 output - Range of data:min = 0.01  max = 0.461925184292249, Data
> Units:   unitless
> Band 2 output - Range of data:min = 0.01  max = 0.925906812458597, Data
> Units:   unitless
> Band 3 output - Range of data:min = 0.01  max = 0.785829845850446, Data
> Units:   unitless
> .
> .
> Band 6 output - Range of data:min = 203.371307953013  max =
> 327.669907753679, Data Units:   Kelvin
> 
> I have same results when using MTL or MTLOld as source of metadata, on TM or
> ETM+ sensors and different atmospheric correction methods (uncorrected,
> DOS). I am running winGRASS7 revision 57466.
> 
> Is there a problem with the printed output from r.info/command output or are
> these zeros the actual values that i.landsat.toar uses as input to
> computations?

I doubt that r.info has a problem reading the metadata that pertain to a 
queried raster map.  If I am not wrong, it merely reads simple text files that 
reside inside the "hist" directory inside the corresponding Mapset.

My guess is that you use an older version of i.landsat.toar whicj, indeed, 
produces empty raster maps.  Unfortunately, I do not use (nor have any access 
to a Windows machine) so as to be in position to help directly.  We need 
feedback from someone with a Windows OS.

(
On/Off-Topic:  is there a way to run and test GRASS in an emulated Windows 
environment for those who don't have a legally licensed Windows OS?
)

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