Re: [GRASS-user] r.in.lidar build errors [RESOLVED]

2018-03-07 Thread Rich Shepard 

On Wed, 7 Mar 2018, Markus Metz wrote:


that means you need to rebuild liblas and maybe its dependencies, before
you recompile GRASS


Markus,

  Thank you. The errors I reported were not being able to compile lidar html
files which seemed to me to be independent of the spatial libraries.

  Taking your advice, I recompiled and re-installed proj, gdal, geos,
libLAS, laszip, blas/lapack (and OpenBLAS but the system cannot find it),
etc. Surprisingly (to me) this did the trick.

  While I don't understand the relationship of these libraries to the build
error I accept that there is such a relationship.

Best regards,

Rich

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

Re: [GRASS-user] r.in.lidar build errors

2018-03-07 Thread Markus Metz 
On Wed, Mar 7, 2018 at 10:27 PM, Rich Shepard 
wrote:
>
> On Wed, 7 Mar 2018, Markus Metz wrote:
>
>> Apparently your liblas installation does not find libproj.so.12.
>
>
> Markus,
>
>   There are two issues and I think they're becoming conflated.
>
>   Issue 1: I cannot invoke the installed grass-7.5 because it was built
> against libproj.so.12.0.0 and that library has been upgraded to
> libproj.so.13.0.0.

that means you need to rebuild liblas and maybe its dependencies, before
you recompile GRASS

Markus M

> This issue will be resolved by building the new svn
> source against the newer libproj library.
>
>   Issue 2: Building the new version fails because of errors in:
> /home/rshepard/gis/grass/grass7_trunk/raster/r.in.lidar
> /home/rshepard/gis/grass/grass7_trunk/raster3d/r3.in.lidar
> /home/rshepard/gis/grass/grass7_trunk/vector/v.out.lidar
> /home/rshepard/gis/grass/grass7_trunk/vector/v.in.lidar
>
> and when I run make in each of those directories it fails because it
cannot
> find the *.tmp.html files.
>
>   I can re-post those attempts at running 'make' in each *.lidar directory
> if desired.
>
> HTH,
>
>
> Rich
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] r.in.lidar build errors

2018-03-07 Thread Rich Shepard 

On Wed, 7 Mar 2018, Markus Metz wrote:


Apparently your liblas installation does not find libproj.so.12.


Markus,

  There are two issues and I think they're becoming conflated.

  Issue 1: I cannot invoke the installed grass-7.5 because it was built
against libproj.so.12.0.0 and that library has been upgraded to
libproj.so.13.0.0. This issue will be resolved by building the new svn
source against the newer libproj library.

  Issue 2: Building the new version fails because of errors in:
/home/rshepard/gis/grass/grass7_trunk/raster/r.in.lidar
/home/rshepard/gis/grass/grass7_trunk/raster3d/r3.in.lidar
/home/rshepard/gis/grass/grass7_trunk/vector/v.out.lidar
/home/rshepard/gis/grass/grass7_trunk/vector/v.in.lidar

and when I run make in each of those directories it fails because it cannot
find the *.tmp.html files.

  I can re-post those attempts at running 'make' in each *.lidar directory
if desired.

HTH,

Rich

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

Re: [GRASS-user] r.in.lidar build errors

2018-03-07 Thread Markus Metz 
On Tue, Mar 6, 2018 at 5:22 PM, Rich Shepard 
wrote:
>
>   I think there was a recent thread on *.in.lidar modules, but I paid no
> attention as I'm not currently using lidar data.
>
>   After checking out the latest from the grass7_trunk svn repository I
> configured the source tree and tried to build it. There are errors in the
> *.in.lidar modules; each has errors when I try to build each one
separately:
>
> (r.in.lidar)
> : /error while loading shared libraries: libproj.so.12: cannot open
shared object file: No such file or directory

Apparently your liblas installation does not find libproj.so.12.

If you compiled liblas from source, please recompile liblas.

If you installed liblas from your distro's repo, this distro's repo is
broken and you need to compile liblas from source.

HTH,

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

Re: [GRASS-user] r.in.lidar build errors [UPDATE]

2018-03-07 Thread Rich Shepard 

On Wed, 7 Mar 2018, Martin Landa wrote:


probably liblas is compiled against different version of libproj. Try to
recompile liblas first.


Martin,

  Installed here are libproj-4.4.7 and proj-5.0.0. Today I rebuilt
libLAS-1.8.1 and libspatialite (gdal rebuilt yesterday) so the latest qgis
would build.

Thanks,

Rich



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

Re: [GRASS-user] r.in.lidar build errors [UPDATE]

2018-03-07 Thread Martin Landa 
2018-03-07 20:17 GMT+01:00 Rich Shepard :
>> I suppose I can cd to those directories and touch the filenames so I can
>> build GRASS against the upgraded libproj.so.

probably liblas is compiled against different version of libproj. Try
to recompile liblas first.

Ma

-- 
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] r.in.lidar build errors [UPDATE]

2018-03-07 Thread Rich Shepard 

On Wed, 7 Mar 2018, Rich Shepard wrote:


I suppose I can cd to those directories and touch the filenames so I can
build GRASS against the upgraded libproj.so.


  No, this won't work. The error message is the lack of a makefile 'all' for
r.in.lidar.tmp.html (and the other three modules), but that file does not
exist in the source tree:

~/gis/grass/grass7_trunk/raster/r.in.lidar]$ ls
Makefile projection.c  r_in_lidar_zrange.png
filters.cr.in.lidar.html   r_in_lidar_zrange.svg
filters.hr_in_lidar.pngrast_segment.c
info.c   r_in_lidar_base_raster.pngrast_segment.h
local_proto.hr_in_lidar_base_raster.svgstring_list.c
main.c   r_in_lidar_binning_count.png  support.c
point_binning.c  r_in_lidar_binning_mean.png   test/
point_binning.h  r_in_lidar_dem_mean3D.jpg testsuite/

  The file, r.in.lidar.html exists, but not r.in.lidar.tmp.html. Is the tmp
file generated during the build process? If so, I wonder why the Makefile
doesn't include it.

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

Re: [GRASS-user] r.in.lidar build errors [UPDATE]

2018-03-07 Thread Rich Shepard 

On Wed, 7 Mar 2018, Markus Neteler wrote:


v.in.lidar: error while loading shared libraries: libproj.so.12: cannot
open shared object file: No such file or directory


To me that looks like library not in LD_LIBRARY_PATH error or library
version changed after compilation of GRASS.


Markus,

  The latter is probably the reason. Installed here are:

/usr/lib/libproj.so.13
/usr/lib/libproj.so.13.0.0
/usr/lib/libproj.so

  But, I cannot compile the latest GRASS release (72331) because of the
missing .html files.

  I suppose I can cd to those directories and touch the filenames so I can
build GRASS against the upgraded libproj.so.

Thanks,

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

Re: [GRASS-user] r.in.lidar build errors [UPDATE]

2018-03-07 Thread Markus Neteler 
Rich,

> v.in.lidar: error while loading shared libraries: libproj.so.12: cannot
open shared object file: No such file or directory

To me that looks like library not in LD_LIBRARY_PATH error or library
version changed after compilation of GRASS.

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

Re: [GRASS-user] install grass via repo

2018-03-07 Thread Martin Landa 
Hi,

2018-03-03 21:51 GMT+01:00 Martin Landa :
> unfortunately still haven't found a reason why uploading packages to
> [1] is failing. It's strange because upload to UbuntuGIS works.

somehow solved, package upload [1]. Please try it out. Ma

[1] https://launchpad.net/~grass/+archive/ubuntu/grass-stable/+packages

-- 
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] r.in.lidar build errors [UPDATE]

2018-03-07 Thread Rich Shepard 

On Tue, 6 Mar 2018, Rich Shepard wrote:


(r.in.lidar) : /error while loading shared libraries: libproj.so.12:
cannot open shared object file: No such file or directory
../../include/Make/Html.make:14: recipe for target 'r.in.lidar.tmp.html' 
failed

make: *** [r.in.lidar.tmp.html] Error 1
rm r.in.lidar.tmp.html


  I see that someone added a couple of .html files to the trunck branch in
release 72331. Unfortunately, these did not fis the problems. Here're the
error messages and the results of running 'make' in each directory:

Errors in:
/home/rshepard/gis/grass/grass7_trunk/raster/r.in.lidar
/home/rshepard/gis/grass/grass7_trunk/raster3d/r3.in.lidar
/home/rshepard/gis/grass/grass7_trunk/vector/v.out.lidar
/home/rshepard/gis/grass/grass7_trunk/vector/v.in.lidar

~/gis/grass/grass7_trunk/raster/r.in.lidar]$ make
if [ "/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/bin/r.in.lidar" != "" ] ; then 
GISRC=/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/demolocation/.grassrc75 
GISBASE=/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu 
PATH="/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/bin:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/bin:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/scripts:$PATH"
 
PYTHONPATH="/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/etc/python:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/gui/wxpython:$PYTHONPATH"
 
LD_LIBRARY_PATH="/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/bin:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/bin:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/scripts:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/lib:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/lib:/usr/lib/qt
/lib:" LC_ALL=C LANG=C LANGUAGE=C 
/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/bin/r.in.lidar --html-description < 
/dev/null | grep -v '\|' > r.in.lidar.tmp.html ; fi
/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/bin/r.in.lidar: 
error while loading shared libraries: libproj.so.12: cannot open shared object 
file: No such file or directory
../../include/Make/Html.make:14: recipe for target 'r.in.lidar.tmp.html' failed
make: *** [r.in.lidar.tmp.html] Error 1
rm r.in.lidar.tmp.html

~/gis/grass/grass7_trunk/raster3d/r3.in.lidar]$ make
if [ "/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/bin/r3.in.lidar" != "" ] ; then 
GISRC=/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/demolocation/.grassrc75 
GISBASE=/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu 
PATH="/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/bin:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/bin:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/scripts:$PATH"
 
PYTHONPATH="/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/etc/python:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/gui/wxpython:$PYTHONPATH"
 
LD_LIBRARY_PATH="/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/bin:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/bin:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/scripts:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/lib:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/lib:/usr/lib/q
t/lib:" LC_ALL=C LANG=C LANGUAGE=C 
/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/bin/r3.in.lidar --html-description < 
/dev/null | grep -v '\|' > r3.in.lidar.tmp.html ; fi
/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/bin/r3.in.lidar: 
error while loading shared libraries: libproj.so.12: cannot open shared object 
file: No such file or directory
../../include/Make/Html.make:14: recipe for target 'r3.in.lidar.tmp.html' failed
make: *** [r3.in.lidar.tmp.html] Error 1
rm r3.in.lidar.tmp.html

~/gis/grass/grass7_trunk/vector/v.out.lidar]$ make
if [ "/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/bin/v.out.lidar" != "" ] ; then 
GISRC=/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/demolocation/.grassrc75 
GISBASE=/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu 
PATH="/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/bin:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/bin:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/scripts:$PATH"
 
PYTHONPATH="/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/etc/python:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/gui/wxpython:$PYTHONPATH"
 
LD_LIBRARY_PATH="/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/bin:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/bin:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/scripts:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/lib:/home/rshepard/gis/grass/grass7_trunk/dist.i686-pc-linux-gnu/lib:/usr/lib/q

Re: [GRASS-user] Query regarding r.horizon in GRASS GIS 7.2.2 as a standalone

2018-03-07 Thread Helmut Kudrnovsky 
from the manual [1]

-
At the moment the elevation and maximum distance must be measured in meters,
even if you use geographical coordinates (longitude/latitude). If your
projection is based on distance (easting and northing), these too must be in
meters. The buffer parameters must be in the same units as the raster
coordinates (e.g., for latitude-longitude locations buffers are measured in
degree unit)


 your first report was a module run within a latlon location; check the
buffer option is in the right unit


[1] https://grass.osgeo.org/grass72/manuals/r.horizon.html



-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Users-f3884509.html
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Query regarding r.horizon in GRASS GIS 7.2.2 as a standalone

2018-03-07 Thread Johnn Wani 
Dear sir,

As I run the r.horizon module on a DEM with the projected coordinate
system. It works fine.

Thanks

With sincere regards
John

On Wed, Mar 7, 2018 at 6:48 PM, Johnn Wani  wrote:

> Dear sir,
> Thanks for your quick response.
> Here is my output:
> g.gisenv set=DEBUG=3
>
> (Wed Mar 07 18:42:35 2018) Command finished (0 sec)
>
> (Wed Mar 07 18:42:55 2018)
>
> r.horizon -d --overwrite elevation=n34_e077_1arc_v3 direction=90 step=22.5
> coordinates=741286,3793821 file=horizon.csv
> D1/3: G_set_program_name(): r.horizon
> D2/3: G_file_name(): path =
> H:\Johnn\LEH\GIS_Files\Leh_Grass_Project\Horizon\PERMANENT
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\WIND
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\WIND
> D2/3:   file open: read (mode = r)
> D2/3: G__read_Cell_head
> D2/3: G__read_Cell_head_array
> D3/3: region item: proj:   3
> D3/3: region item: zone:   0
> D3/3: region item: north:  35:00:00.5N
> D3/3: region item: south:  33:59:59.5N
> D3/3: region item: east:   78:00:00.5E
> D3/3: region item: west:   76:59:59.5E
> D3/3: region item: cols:   3601
> D3/3: region item: rows:   3601
> D3/3: region item: e-w resol:  0:00:01
> D3/3: region item: n-s resol:  0:00:01
> D3/3: region item: top:1.000
> D3/3: region item: bottom: 0.000
> D3/3: region item: cols3:  3601
> D3/3: region item: rows3:  3601
> D3/3: region item: depths: 1
> D3/3: region item: e-w resol3: 0:00:01
> D3/3: region item: n-s resol3: 0:00:01
> D3/3: region item: t-b resol:  1
> D3/3: G_adjust_Cell_head: epsilon_ns: 2.77701e-007,
> epsilon_ew: 1e-006
> Note: In latitude-longitude coordinate system specify buffers in degree
> unit
> D1/3: Setting mode: SINGLE_POINT
> D1/3: Using maxdistance 1.00
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\PROJ_INFO
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\PROJ_UNITS
> D3/3: GPJ__get_datum_params: datumname: 
> D1/3: G_find_raster2(): name=n34_e077_1arc_v3 mapset=
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\SEARCH_PATH
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\cell\n34_e077_1arc_v3
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
> D2/3:   file open: read (mode = r)
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
> D2/3:   file open: read (mode = r)
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
> D2/3:   file open: read (mode = r)
> D2/3: G__read_Cell_head
> D2/3: G__read_Cell_head_array
> D3/3: region item: proj:   3
> D3/3: region item: zone:   0
> D3/3: region item: north:  35:00:00.5N
> D3/3: region item: south:  33:59:59.5N
> D3/3: region item: east:   78:00:00.5E
> D3/3: region item: west:   76:59:59.5E
> D3/3: region item: cols:   3601
> D3/3: region item: rows:   3601
> D3/3: region item: e-w resol:  0:00:01
> D3/3: region item: n-s resol:  0:00:01
> D3/3: region item: format: 1
> D3/3: region item: compressed: 2
> D3/3: G_adjust_Cell_head: epsilon_ns: 2.77701e-007,
> epsilon_ew: 1e-006
> D1/3: G_find_raster2(): name=n34_e077_1arc_v3 mapset=
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\cell\n34_e077_1arc_v3
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\fcell\n34_e077_1arc_v3
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
> _Project\Horizon\PERMANENT\g3dcell\n34_e077_1arc_v3
> D1/3: G_find_raster2(): name=n34_e077_1arc_v3 mapset=
> D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
>

Re: [GRASS-user] Query regarding r.horizon in GRASS GIS 7.2.2 as a standalone

2018-03-07 Thread Johnn Wani 
Dear sir,
Thanks for your quick response.
Here is my output:
g.gisenv set=DEBUG=3

(Wed Mar 07 18:42:35 2018) Command finished (0 sec)

(Wed Mar 07 18:42:55 2018)

r.horizon -d --overwrite elevation=n34_e077_1arc_v3 direction=90 step=22.5
coordinates=741286,3793821 file=horizon.csv
D1/3: G_set_program_name(): r.horizon
D2/3: G_file_name(): path =
H:\Johnn\LEH\GIS_Files\Leh_Grass_Project\Horizon\PERMANENT
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\WIND
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\WIND
D2/3:   file open: read (mode = r)
D2/3: G__read_Cell_head
D2/3: G__read_Cell_head_array
D3/3: region item: proj:   3
D3/3: region item: zone:   0
D3/3: region item: north:  35:00:00.5N
D3/3: region item: south:  33:59:59.5N
D3/3: region item: east:   78:00:00.5E
D3/3: region item: west:   76:59:59.5E
D3/3: region item: cols:   3601
D3/3: region item: rows:   3601
D3/3: region item: e-w resol:  0:00:01
D3/3: region item: n-s resol:  0:00:01
D3/3: region item: top:1.000
D3/3: region item: bottom: 0.000
D3/3: region item: cols3:  3601
D3/3: region item: rows3:  3601
D3/3: region item: depths: 1
D3/3: region item: e-w resol3: 0:00:01
D3/3: region item: n-s resol3: 0:00:01
D3/3: region item: t-b resol:  1
D3/3: G_adjust_Cell_head: epsilon_ns: 2.77701e-007,
epsilon_ew: 1e-006
Note: In latitude-longitude coordinate system specify buffers in degree unit
D1/3: Setting mode: SINGLE_POINT
D1/3: Using maxdistance 1.00
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\PROJ_INFO
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\PROJ_UNITS
D3/3: GPJ__get_datum_params: datumname: 
D1/3: G_find_raster2(): name=n34_e077_1arc_v3 mapset=
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\SEARCH_PATH
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\cell\n34_e077_1arc_v3
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
D2/3:   file open: read (mode = r)
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
D2/3:   file open: read (mode = r)
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
D2/3:   file open: read (mode = r)
D2/3: G__read_Cell_head
D2/3: G__read_Cell_head_array
D3/3: region item: proj:   3
D3/3: region item: zone:   0
D3/3: region item: north:  35:00:00.5N
D3/3: region item: south:  33:59:59.5N
D3/3: region item: east:   78:00:00.5E
D3/3: region item: west:   76:59:59.5E
D3/3: region item: cols:   3601
D3/3: region item: rows:   3601
D3/3: region item: e-w resol:  0:00:01
D3/3: region item: n-s resol:  0:00:01
D3/3: region item: format: 1
D3/3: region item: compressed: 2
D3/3: G_adjust_Cell_head: epsilon_ns: 2.77701e-007,
epsilon_ew: 1e-006
D1/3: G_find_raster2(): name=n34_e077_1arc_v3 mapset=
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\cell\n34_e077_1arc_v3
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\fcell\n34_e077_1arc_v3
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\g3dcell\n34_e077_1arc_v3
D1/3: G_find_raster2(): name=n34_e077_1arc_v3 mapset=
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\cell\n34_e077_1arc_v3
D1/3: G_find_raster2(): name=n34_e077_1arc_v3 mapset=
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\cellhd\n34_e077_1arc_v3
D2/3: G_file_name(): path = H:\Johnn\LEH\GIS_Files\Leh_Grass
_Project\Horizon\PERMANENT\cell\n34_e077_1arc_v3
D2/3: G_file_name():

Re: [GRASS-user] Query regarding r.horizon in GRASS GIS 7.2.2 as a standalone

2018-03-07 Thread Helmut Kudrnovsky 
Johnn Wani wrote
> Dear sir,
> 
> Thanks for your response.
> 
> I tried with NC sample dataset and it worked fine.
> 
> 
> Regards
> John
> 
> On Wed, Mar 7, 2018 at 4:23 PM, Helmut Kudrnovsky 

> hellik@

>  wrote:
> 
>> Johnn Wani wrote
>> > Dear GRASS GIS users,
>> >
>> > I am a student from India. I am using *GRASS GIS 7.2.2 as a standalone*
>> in
>> > Windows 10 operating system.
>> >
>> > My aim is to use r.horizon module to calculate horizon at a point in my
>> > study area and save it to a .csv file. As I run the following command
>> in
>> > the console window on GRASS GIS:
>> >
>> > r.horizon -d --overwrite elevation=n34_e077_1arc_v3@PERMANENT
>> direction=90
>> > step=22.5 coordinates=741302,3793829 file=C:\Users\user\horizon.csv
>> >
>> > But I am receiving an error message as attached herewith. Earlier also
>> I
>> > got the same error message but at that time it was due to non-alignment
>> of
>> > my DEM.
>> > This time my DEM is aligned, here is the output of g.region -p command:
>> >
>> >  g.region -p
>> >
>> > projection: 3 (Latitude-Longitude)
>> > zone:   0
>> > datum:  wgs84
>> > ellipsoid:  wgs84
>> > north:  35:00:00.5N
>> > south:  33:59:59.5N
>> > west:   76:59:59.5E
>> > east:   78:00:00.5E
>> > nsres:  0:00:01
>> > ewres:  0:00:01
>> > rows:   3601
>> > cols:   3601
>> > cells:  12967201
>> > (Wed Mar 07 15:15:14 2018) Command finished (0 sec)
>>
>> have you tried the example with the NC sample data set mentioned in the
>> manual?
>>
>>
>>
>>
>> -
>> best regards
>> Helmut
>> --
>> Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Users-f3884509.html
>> ___
>> grass-user mailing list
>> 

> grass-user@.osgeo

>> https://lists.osgeo.org/mailman/listinfo/grass

Could you set

g.gisenv set="DEBUG=3"

before you run the module on your own data and report the debug output




-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Users-f3884509.html
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Query regarding r.horizon in GRASS GIS 7.2.2 as a standalone

2018-03-07 Thread Johnn Wani 
Dear sir,

Thanks for your response.

I tried with NC sample dataset and it worked fine.


Regards
John

On Wed, Mar 7, 2018 at 4:23 PM, Helmut Kudrnovsky  wrote:

> Johnn Wani wrote
> > Dear GRASS GIS users,
> >
> > I am a student from India. I am using *GRASS GIS 7.2.2 as a standalone*
> in
> > Windows 10 operating system.
> >
> > My aim is to use r.horizon module to calculate horizon at a point in my
> > study area and save it to a .csv file. As I run the following command in
> > the console window on GRASS GIS:
> >
> > r.horizon -d --overwrite elevation=n34_e077_1arc_v3@PERMANENT
> direction=90
> > step=22.5 coordinates=741302,3793829 file=C:\Users\user\horizon.csv
> >
> > But I am receiving an error message as attached herewith. Earlier also I
> > got the same error message but at that time it was due to non-alignment
> of
> > my DEM.
> > This time my DEM is aligned, here is the output of g.region -p command:
> >
> >  g.region -p
> >
> > projection: 3 (Latitude-Longitude)
> > zone:   0
> > datum:  wgs84
> > ellipsoid:  wgs84
> > north:  35:00:00.5N
> > south:  33:59:59.5N
> > west:   76:59:59.5E
> > east:   78:00:00.5E
> > nsres:  0:00:01
> > ewres:  0:00:01
> > rows:   3601
> > cols:   3601
> > cells:  12967201
> > (Wed Mar 07 15:15:14 2018) Command finished (0 sec)
>
> have you tried the example with the NC sample data set mentioned in the
> manual?
>
>
>
>
> -
> best regards
> Helmut
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Users-f3884509.html
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user




-- 
*JOHN MOHD WANI*
Ph.D. Research Scholar
Department of Civil Engineering
IIT Roorkee, Uttarakhand, INDIA-247667
Mail: johnn.n...@gmail.com
(M): +91-8126910585
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] r.in.lidar fails in Win7

2018-03-07 Thread Marco Alicera 
Thanks Martin.
I have got some errors with the Microsoft Visaul C++ Redistributable
Packages, I will have to see later what affects and how to solve it, but
Grass is v.in.lidar running and scanning "9613851 points..."
--
Marco


2018-03-01 10:37 GMT+01:00 Martin Landa :

> 2018-03-01 10:19 GMT+01:00 Marco Alicera :
> > oops, relevant detail.
> > OS: Windows 7 Enterprise 64 bit
>
> please try out 7.4.0 64bit [1]. Ma
>
> [1] https://grass.osgeo.org/grass74/binary/mswindows/
> native/x86_64/WinGRASS-7.4.0-1-Setup-x86_64.exe
>
> --
> Martin Landa
> http://geo.fsv.cvut.cz/gwiki/Landa
> http://gismentors.cz/mentors/landa
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Query regarding r.horizon in GRASS GIS 7.2.2 as a standalone

2018-03-07 Thread Helmut Kudrnovsky 
Johnn Wani wrote
> Dear GRASS GIS users,
> 
> I am a student from India. I am using *GRASS GIS 7.2.2 as a standalone* in
> Windows 10 operating system.
> 
> My aim is to use r.horizon module to calculate horizon at a point in my
> study area and save it to a .csv file. As I run the following command in
> the console window on GRASS GIS:
> 
> r.horizon -d --overwrite elevation=n34_e077_1arc_v3@PERMANENT direction=90
> step=22.5 coordinates=741302,3793829 file=C:\Users\user\horizon.csv
> 
> But I am receiving an error message as attached herewith. Earlier also I
> got the same error message but at that time it was due to non-alignment of
> my DEM.
> This time my DEM is aligned, here is the output of g.region -p command:
> 
>  g.region -p
> 
> projection: 3 (Latitude-Longitude)
> zone:   0
> datum:  wgs84
> ellipsoid:  wgs84
> north:  35:00:00.5N
> south:  33:59:59.5N
> west:   76:59:59.5E
> east:   78:00:00.5E
> nsres:  0:00:01
> ewres:  0:00:01
> rows:   3601
> cols:   3601
> cells:  12967201
> (Wed Mar 07 15:15:14 2018) Command finished (0 sec)

have you tried the example with the NC sample data set mentioned in the
manual?




-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Users-f3884509.html
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] Query regarding r.horizon in GRASS GIS 7.2.2 as a standalone

2018-03-07 Thread Johnn Wani 
Dear GRASS GIS users,

I am a student from India. I am using *GRASS GIS 7.2.2 as a standalone* in
Windows 10 operating system.

My aim is to use r.horizon module to calculate horizon at a point in my
study area and save it to a .csv file. As I run the following command in
the console window on GRASS GIS:

r.horizon -d --overwrite elevation=n34_e077_1arc_v3@PERMANENT direction=90
step=22.5 coordinates=741302,3793829 file=C:\Users\user\horizon.csv

But I am receiving an error message as attached herewith. Earlier also I
got the same error message but at that time it was due to non-alignment of
my DEM.
This time my DEM is aligned, here is the output of g.region -p command:

 g.region -p

projection: 3 (Latitude-Longitude)
zone:   0
datum:  wgs84
ellipsoid:  wgs84
north:  35:00:00.5N
south:  33:59:59.5N
west:   76:59:59.5E
east:   78:00:00.5E
nsres:  0:00:01
ewres:  0:00:01
rows:   3601
cols:   3601
cells:  12967201
(Wed Mar 07 15:15:14 2018) Command finished (0 sec)

Please help

With sincere regards
-- 
*JOHN MOHD WANI*
Ph.D. Research Scholar
Department of Civil Engineering
IIT Roorkee, Uttarakhand, INDIA-247667
Mail: johnn.n...@gmail.com
(M): +91-8126910585
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Query regarding r.horizon in GRASS GIS

2018-03-07 Thread Helmut Kudrnovsky 
[never send private mail, always use the GRASS GIS user list]

 >>Gesendet: Mittwoch, 07. März 2018 um 10:52 Uhr
>>Von: "Johnn Wani" 
>>Betreff: Query regarding r.horizon in GRASS GIS
>>
>>Dear sir,
>>Greetings from India,
>> 
>>I am a student from India. I am using GRASS GIS 7.2.2 as a standalone in 
>>Windows 10 operating system.
>> 
>>My aim is to use r.horizon module to calculate horizon at a point in my study 
>>area and save it to a .csv file. As I run the following command in the 
>>console window on GRASS GIS:
>> 
>>r.horizon -d --overwrite elevation=n34_e077_1arc_v3@PERMANENT direction=90 
>>step=22.5 coordinates=741302,3793829 file=C:\Users\user\horizon.csv
>> 
>>But I am receiving an error message as attached herewith. Earlier also I got 
>>the same error message but it was due to non-alignment of my DEM.
>>This time my DEM is aligned here is the output of g.region -p command:
>> 
>> g.region -p  
>>
>>projection: 3 (Latitude-Longitude)
>>zone:   0
>>datum:  wgs84
>>ellipsoid:  wgs84
>>north:  35:00:00.5N
>>south:  33:59:59.5N
>>west:   76:59:59.5E
>>east:   78:00:00.5E
>>nsres:  0:00:01
>>ewres:  0:00:01
>>rows:   3601
>>cols:   3601
>>cells:  12967201
>>(Wed Mar 07 15:15:14 2018) Command finished (0 sec) 
>> 
>>Please help
>>Sorry for any inconvenience caused by this mail
>> 
>>With sincere regards--
>>
>>JOHN MOHD WANIPh.D. Research Scholar 
>>Department of Civil EngineeringIIT Roorkee, Uttarakhand, INDIA-247667
>>Mail: johnn.n...@gmail.com[mailto:johnn.n...@gmail.com]
>>(M): +91-8126910585
 
please post wich winGRASS version, standalone or OSGeo4W?

have a look into the manual of r.horizon:
https://grass.osgeo.org/grass74/manuals/r.horizon.html

there is an example with the NC sample data set.

test this example on your computer and see if it works.

kind regards
Helmut
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user