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] 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