Thanks a lot very good information and guidance.
Thanks
Gabriel
On Wed, Aug 21, 2019 at 3:31 AM Nikos Alexandris
wrote:
> * Gabriel Cotlier [2018-08-21 12:00:24 -0300]:
>
> >I would like to ask if nonetheless the effect due to "stray light" the
> >*i.landsat8.swlst* code for split window is
* Gabriel Cotlier [2018-08-21 12:00:24 -0300]:
I would like to ask if nonetheless the effect due to "stray light" the
*i.landsat8.swlst* code for split window is still applicable to Landsat 8
data and whether these error is specially visible on water bodies?
The implemented algorithm (Du,
Dear Markus,
My message to your code: g.region -p n=75:00:15N s=65:00:15S w=179:59:45W
e=180:00:15E res=00:00:30 is in the picture bellow:
[image: image.png]
On Tue, Aug 20, 2019 at 5:34 PM Gabriel Cotlier wrote:
> Dear Markus,
> My grass version is : GRASS GIS 7.6.1
>
> On Tue, Aug 20, 2019
Dear Markus,
My grass version is : GRASS GIS 7.6.1
On Tue, Aug 20, 2019 at 5:13 PM Markus Metz
wrote:
> Dear Gabriel,
>
> On Tue, Aug 20, 2019 at 9:50 PM Gabriel Cotlier
> wrote:
> >
> > Dear Markus,
> > So I run the command g.region w=179:59:45W e=180:00:15E
> >
> > Now my log now before and
Dear Gabriel,
On Tue, Aug 20, 2019 at 9:50 PM Gabriel Cotlier wrote:
>
> Dear Markus,
> So I run the command g.region w=179:59:45W e=180:00:15E
>
> Now my log now before and after the command g.region w=179:59:45W
e=180:00:15E is as follows:
>
> 360 degree EW extent is exceeded by 1 cells
> 360
Dear Markus,
So I run the command g.region w=179:59:45W e=180:00:15E
Now my log now before and after the command g.region w=179:59:45W
e=180:00:15E is as follows:
360 degree EW extent is exceeded by 1 cells
360 degree EW extent is exceeded by 1 cells
(Tue Aug 20 16:41:45 2019) Command finished
Dear Markus,
Thanks a lot for your response and explanation.
Changing the region to w=179:59:45W e=180:00:15E, am I not only avoiding
the warning, but also changing the layers to be physically correct, right?
Thanks again for your help.
regards,
Gabriel
On Tue, Aug 20, 2019 at 4:24 PM Markus
Dear Gabriel,
On Tue, Aug 20, 2019 at 12:19 AM Gabriel Cotlier
wrote:
>
> Dear Markus,
>
> Thanks a lot for the clarification and explanation, your response was
indeed helpful.
>
> I got for all maps in the mapset I used, for both the DMSP original
raster layers and the intercallibrated rasrer
On Mon, Aug 19, 2019 at 12:05 AM Gabriel Cotlier
wrote:
>
> Hello,
> My question is how does it influence the fact that it say:
> 360 degree EW extent is exceeded by 0.999827 cells
this is caused by the truncated resolution of 0.0083330
with a corrected resolution of 00:00:30, the
Hello,
My question is how does it influence the fact that it say:
360 degree EW extent is exceeded by 0.999827 cells
360 degree EW extent is exceeded by 1 cells
[image: image.png]
while when I loaded a first file I defined a region as
[image: Capture.JPG]
which is exactly I suppose the
Hello, another question, regarding *i.nightlights.intercalibration, *can I
run this code as python package/lbrary loading it from Spyder or Jupiter
Notebook instead of using GRASS interface, if so how is a convenient way
to install *i.nightlights.intercalibration *in python using Spyder?
Dear Nikos.
After a long time I'm trying to reproduce a routine I have for doing
intercallibratrion of DMSP 1992-2012 but for some reason It doesn't work to
me. I think is because the problem between the region of the layers 30 arc
sec should resolution be from 0.0083330 to
Dear Nikos,
Thanks a lot for your answer and the orientation.
The information and the link are very useful.
Kind regards,
Gabriel
On Wed, Aug 22, 2018 at 5:19 AM Nikos Alexandris
wrote:
> * Gabriel Cotlier [2018-08-21 12:00:24 -0300]:
>
> >Dear Nikos and GRASS users,
> >
> >I would like to
Dear Nikos and GRASS users,
I would like to ask if nonetheless the effect due to "stray light" the
*i.landsat8.swlst* code for split window is still applicable to Landsat 8
data and whether these error is specially visible on water bodies? and
whether band 10 is better than band 11 in terms of
14 matches
Mail list logo
