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 <johnn.n...@gmail.com> 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\Hor

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

2018-03-07 Thread Johnn Wani
 5494.00
D3/3: 33 4 6222.00
D3/3: 33 5 6005.00
D3/3: 33 6 5185.00
D3/3: 33 7 5674.00
D3/3: 33 8 6089.00
D3/3: 33 9 5964.00
D3/3: 33 10 6464.00
D3/3: 33 11 6295.00
D3/3: 33 12 6169.00
D3/3: 33 13 5382.00
D3/3: 33 14 5216.00
D3/3: 33 15 4774.00
D3/3: 33 16 3756.00
D3/3: 33 17 4829.00
D3/3: 33 18 5007.00
D3/3: 33 19 5697.00
D3/3: 33 20 5846.00
D3/3: 33 21 5909.00
D3/3: 33 22 6449.00
D3/3: 33 23 6390.00
D3/3: 33 24 6352.00
D3/3: 33 25 6289.00
D3/3: 33 26 6325.00
D3/3: 33 27 6093.00
D3/3: 33 28 6055.00
D3/3: 33 29 6430.00
D3/3: 33 30 6302.00
D3/3: 33 31 6238.00
D3/3: 33 32 6348.00
D3/3: 33 33 6376.00
D3/3: 33 34 6160.00
D3/3: 33 35 5793.00
D3/3: 33 36 5796.00
D3/3: 34 0 5692.00
D3/3: 34 1 5701.00
D3/3: 34 2 6014.00
D3/3: 34 3 6156.00
D3/3: 34 4 5747.00
D3/3: 34 5 5760.00
D3/3: 34 6 5542.00
D3/3: 34 7 5988.00
D3/3: 34 8 6356.00
D3/3: 34 9 5979.00
D3/3: 34 10 5661.00
D3/3: 34 11 5799.00
D3/3: 34 12 5573.00
D3/3: 34 13 5217.00
D3/3: 34 14 4650.00
D3/3: 34 15 4360.00
D3/3: 34 16 4949.00
D3/3: 34 17 5746.00
D3/3: 34 18 5881.00
D3/3: 34 19 5222.00
D3/3: 34 20 5937.00
D3/3: 34 21 5791.00
D3/3: 34 22 6109.00
D3/3: 34 23 6262.00
D3/3: 34 24 6044.00
D3/3: 34 25 6079.00
D3/3: 34 26 6189.00
D3/3: 34 27 5957.00
D3/3: 34 28 5795.00
D3/3: 34 29 5975.00
D3/3: 34 30 6141.00
D3/3: 34 31 5837.00
D3/3: 34 32 5934.00
D3/3: 34 33 6112.00
D3/3: 34 34 5574.00
D3/3: 34 35 5473.00
D3/3: 34 36 4766.00
D3/3: 35 0 6038.00
D3/3: 35 1 5874.00
D3/3: 35 2 6012.00
D3/3: 35 3 5913.00
D3/3: 35 4 5921.00
D3/3: 35 5 6202.00
D3/3: 35 6 5939.00
D3/3: 35 7 6400.00
D3/3: 35 8 6556.00
D3/3: 35 9 6270.00
D3/3: 35 10 6560.00
D3/3: 35 11 5735.00
D3/3: 35 12 5151.00
D3/3: 35 13 4509.00
D3/3: 35 14 4995.00
D3/3: 35 15 4973.00
D3/3: 35 16 5470.00
D3/3: 35 17 5851.00
D3/3: 35 18 5941.00
D3/3: 35 19 5603.00
D3/3: 35 20 5648.00
D3/3: 35 21 5841.00
D3/3: 35 22 6084.00
D3/3: 35 23 5981.00
D3/3: 35 24 6056.00
D3/3: 35 25 6260.00
D3/3: 35 26 6298.00
D3/3: 35 27 6187.00
D3/3: 35 28 6034.00
D3/3: 35 29 5817.00
D3/3: 35 30 6001.00
D3/3: 35 31 5806.00
D3/3: 35 32 5831.00
D3/3: 35 33 5736.00
D3/3: 35 34 5771.00
D3/3: 35 35 5612.00
D3/3: 35 36 4664.00
D3/3: 36 0 5617.00
D3/3: 36 1 5179.00
D3/3: 36 2 5872.00
D3/3: 36 3 5449.00
D3/3: 36 4 5826.00
D3/3: 36 5 5933.00
D3/3: 36 6 5380.00
D3/3: 36 7 5507.00
D3/3: 36 8 5984.00
D3/3: 36 9 5517.00
D3/3: 36 10 6033.00
D3/3: 36 11 5363.00
D3/3: 36 12 4776.00
D3/3: 36 13 3719.00
D3/3: 36 14 5011.00
D3/3: 36 15 4906.00
D3/3: 36 16 5246.00
D3/3: 36 17 5817.00
D3/3: 36 18 5574.00
D3/3: 36 19 5583.00
D3/3: 36 20 4826.00
D3/3: 36 21 5461.00
D3/3: 36 22 5614.00
D3/3: 36 23 5840.00
D3/3: 36 24 5836.00
D3/3: 36 25 6272.00
D3/3: 36 26 6277.00
D3/3: 36 27 6028.00
D3/3: 36 28 5733.00
D3/3: 36 29 5565.00
D3/3: 36 30 4958.00
D3/3: 36 31 5071.00
D3/3: 36 32 5816.00
D3/3: 36 33 5722.00
D3/3: 36 34 5764.00
D3/3: 36 35 5475.00
D3/3: 36 36 4665.00
D1/3: calculate() starts...
(Wed Mar 07 18:43:01 2018) Command finished (6 sec)



On Wed, Mar 7, 2018 at 6:42 PM, Helmut Kudrnovsky <hel...@web.de> wrote:

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

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 <hel...@web.de> 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

[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 Related to r.horizon module

2017-11-30 Thread Johnn Wani
Please find the screenshot of g.region -p command.


Regards
John

On Thu, Nov 30, 2017 at 2:04 PM, Helmut Kudrnovsky <hel...@web.de> wrote:

> Johnn Wani wrote
> > Dear sir,
> >
> > Thanks for your response.
> >
> > I already set my computational region to DEM.
>
> and what does g.region -p say?
>
>
>
>
> -
> 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 Related to r.horizon module

2017-11-30 Thread Johnn Wani
Dear sir,

Thanks for your response.

I already set my computational region to DEM.

Regards
John

On Thu, Nov 30, 2017 at 1:55 PM, Helmut Kudrnovsky <hel...@web.de> wrote:

> Johnn Wani wrote
> > Hello all,
> >
> > 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 elevation=Reprojn34_e077_v3@PERMANENT direction=90 step=5
> > bufferzone=500 maxdistance=500 coordinates=741286,3793821
> > file=horizon.csv*
> >
> > I get the error dialogue that the GRASS 7 has stopped working. A
> > screenshot
> > is attached.
> > ​Please help.​
>
> what does g.region -p say? have you aligned the computational region to
> your
> DEM?
>
>
>
>
> -
> 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 Related to i.landsat8.swlst

2016-09-23 Thread Johnn Wani
Dear Stefan,

Thanks a lot for answering my query,

i.landsat8.swlst add-on now works fine for me.
Thanks for your input regarding use of GLC maps, i use these maps to test
the LST add-on.

Regards
John


On Fri, Sep 23, 2016 at 1:44 AM, Blumentrath, Stefan <
stefan.blumentr...@nina.no> wrote:

> Hei Johnn,
>
>
>
> The command you specified is (except for the n-flag) an example from the
> manual. You would have to replace the input to the options according to
> your data!
>
>
>
> I used i.landsat8.swlst in a project in Oslo and was quite satisfied with
> the results. You can see them here:
>
> http://urban.nina.no/layers/geonode%3Alc81980182015183lgn00_lst_
> const_lc#more
>
>
>
> I documented the production here:
>
> https://github.com/NINAnor/openness/blob/master/oslo_heatmap.sh
>
>
>
> Maybe the shell script gives you some more hints on the usage of the
> module in a processing chain...
>
>
>
> Some hints from my experience with the module:
>
> I would NOT use a one of the rather outdated GLC maps (which for my study
> area in addition were full of NoData). If you have a good land cover map I
> would reclassify it according to the classes used in the GLC maps (see the
> manual of i.landsat8.swlst).
>
>
>
> Kind regards,
>
> Stefan
>
>
>
>
>
> *From:* grass-user [mailto:grass-user-boun...@lists.osgeo.org] *On Behalf
> Of *Johnn Wani
> *Sent:* 21. september 2016 15:06
> *To:* grass-user@lists.osgeo.org
> *Subject:* [GRASS-user] Query Related to i.landsat8.swlst
>
>
>
> Dear all,
>
>
>
> I am a student from India, and first time user of GRASS GIS and i am
> having basic knowledge of GIS.
>
> My aim is to use i.landsat8.swlst add-on to calculate LST from Landsat8
> data for my study area.
>
> I want to know in the following command:
>
>
>
> *i.landsat8.swlst mtl=MTL prefix=B landcover=FROM_GLC -n*
>
>
>
> ​Which Basename i am going to provide as prefix for landsat8 data ??
>
>
>
> Also, my first query on grass-user's mail list.
>
> Please help.
>
>
>
> Regards
>
> --
>
> JOHN MOHD WANI
>
> Ph.D Research Scholar
>
> Department of Civil Engineering
>
> IIT Roorkee, Uttarakhand, INDIA-247667
>
> Mail: johnn.n...@gmail.com
>



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

[GRASS-user] Query Related to i.landsat8.swlst

2016-09-21 Thread Johnn Wani
Dear all,

I am a student from India, and first time user of GRASS GIS and i am having
basic knowledge of GIS.
My aim is to use i.landsat8.swlst add-on to calculate LST from Landsat8
data for my study area.
I want to know in the following command:

*i.landsat8.swlst mtl=MTL prefix=B landcover=FROM_GLC -n*

​Which Basename i am going to provide as prefix for landsat8 data ??

Also, my first query on grass-user's mail list.
Please help.

Regards
-- 
JOHN MOHD WANI
Ph.D Research Scholar
Department of Civil Engineering
IIT Roorkee, Uttarakhand, INDIA-247667
Mail: johnn.n...@gmail.com
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user