#1997: i.landsat.toar for grass-dev is missing the option for landsat8
----------------------------+-----------------------------------------------
Reporter: vesnikos | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Imagery | Version: svn-trunk
Keywords: i.landsat.toar | Platform: All
Cpu: Unspecified |
----------------------------+-----------------------------------------------
Comment(by nikosa):
Replying to [comment:4 nikosa]:
> Replying to [comment:3 neteler]:
> > For the record: r56905, r56906, r56907, r56908
>
> It works for me (tried with 56906).
#1997: i.landsat.toar for grass-dev is missing the option for landsat8
----------------------------+-----------------------------------------------
Reporter: vesnikos | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Imagery | Version: svn-trunk
Keywords: i.landsat.toar | Platform: All
Cpu: Unspecified |
----------------------------+-----------------------------------------------
Comment(by vesnikos):
some minor bugs during my tests:
1) Cosmetic typo at the description of sensor parameter:
It says "Required only if 'metfile' not given (recommended by sanity)"
should be ""Required only if 'metfile' not given (recommended for
sanity)
2) Band8 (panchomatic) has my nature 15m res. The algorithm uses the
regions resolution , and you cannot do anything to override it.
3) timestamp in r.info reads none, the date of acquisition is in the
metadata, so it should be properly implemented
#1997: i.landsat.toar for grass-dev is missing the option for landsat8
----------------------------+-----------------------------------------------
Reporter: vesnikos | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Imagery | Version: svn-trunk
Keywords: i.landsat.toar | Platform: All
Cpu: Unspecified |
----------------------------+-----------------------------------------------
Comment(by nikosa):
Replying to [comment:6 vesnikos]:
> some minor bugs during my tests:
> 2) Band8 (panchomatic) has my nature 15m res. The algorithm uses the
regions resolution , and you cannot do anything to override it.
You can set the region resolution to the desired one! In my scripts I do
that. Maybe in this case an exception could be done and let the module
handle this?
> 3) timestamp in r.info reads none, the date of acquisition is in the
metadata, so it should be properly implemented
though, the "input_prefix=Dummy" and "output_prefix=Dummy" must be
defined.
For the records, if you import Landsat bands using the script found in
GRASS-Wiki
[http://grasswiki.osgeo.org/wiki/LANDSAT#Automated_data_import], the
timestamp is set correctly. However, i.landsat.toar does not take care to
copy this over. Even, the right way would be to grep the info from the
MTL file directly.
| Status: new Priority: normal | Milestone: 7.0.0
Component: Imagery | Version: svn-trunk Keywords:
i.landsat.toar | Platform: All Cpu: Unspecified |
----------------------------+-----------------------------------------------
Comment(by vesnikos):
some minor bugs during my tests:
1) Cosmetic typo at the description of sensor parameter:
It says "Required only if 'metfile' not given (recommended by sanity)"
should be ""Required only if 'metfile' not given (recommended for
sanity)
2) Band8 (panchomatic) has my nature 15m res. The algorithm uses the
regions resolution , and you cannot do anything to override it.
3) timestamp in r.info reads none, the date of acquisition is in the
metadata, so it should be properly implemented
#1997: i.landsat.toar for grass-dev is missing the option for landsat8
----------------------------+-----------------------------------------------
Reporter: vesnikos | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Imagery | Version: svn-trunk
Keywords: i.landsat.toar | Platform: All
Cpu: Unspecified |
----------------------------+-----------------------------------------------
Comment(by nikosa):
Replying to [comment:7 nikosa]:
> Replying to [comment:6 vesnikos]:
> > some minor bugs during my tests:
>
>
> > 2) Band8 (panchomatic) has my nature 15m res. The algorithm uses the
regions resolution , and you cannot do anything to override it.
>
> You can set the region resolution to the desired one! In my scripts I
do that. Maybe in this case an exception could be done and let the module
handle this?
This look more important than I thought in the beginning. Indeed, one
needs to work-around that issue since there is no way to preserve the
15m-s of Band 8 using (the current) i.landsat.toar in one go.
Yeah its still open - It shouldn’t since the main problem is fixed. I’ll open a new ticket for the the resolution bug.
BTW, I have made a script that does what i.landsat.toar does, only that its fixed in that regard. I’ll be more than happy to share it if someone needs it!
N
···
On Fri, Sep 27, 2013 at 2:28 PM, GRASS GIS <trac@osgeo.org> wrote:
#1997: i.landsat.toar for grass-dev is missing the option for landsat8
----------------------------±----------------------------------------------
Reporter: vesnikos | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Band8 (panchomatic) has my nature 15m res. The algorithm uses the
regions resolution , and you cannot do anything to override it.
You can set the region resolution to the desired one! In my scripts I
do that. Maybe in this case an exception could be done and let the module
handle this?
This look more important than I thought in the beginning. Indeed, one
needs to work-around that issue since there is no way to preserve the
15m-s of Band 8 using (the current) i.landsat.toar in one go.
Yeah its still open - It shouldn’t since the main problem is fixed. I’ll open a new ticket for the the resolution bug.
BTW, I have made a script that does what i.landsat.toar does, only that its fixed in that regard. I’ll be more than happy to share it if someone needs it!
N
On Fri, Sep 27, 2013 at 2:28 PM, GRASS GIS <trac@osgeo.org> wrote:
#1997: i.landsat.toar for grass-dev is missing the option for landsat8
----------------------------±----------------------------------------------
Reporter: vesnikos | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Band8 (panchomatic) has my nature 15m res. The algorithm uses the
regions resolution , and you cannot do anything to override it.
You can set the region resolution to the desired one! In my scripts I
do that. Maybe in this case an exception could be done and let the module
handle this?
This look more important than I thought in the beginning. Indeed, one
needs to work-around that issue since there is no way to preserve the
15m-s of Band 8 using (the current) i.landsat.toar in one go.
#1997: i.landsat.toar for grass-dev is missing the option for landsat8
----------------------------+-----------------------------------------------
Reporter: vesnikos | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Imagery | Version: svn-trunk
Keywords: i.landsat.toar | Platform: All
Cpu: Unspecified |
----------------------------+-----------------------------------------------
Comment(by neteler):
Replying to [comment:10 nikosa]:
> This look more important than I thought in the beginning. Indeed, one
needs to work-around that issue since there is no way to preserve the
15m-s of Band 8 using (the current) i.landsat.toar in one go.
#1997: i.landsat.toar for grass-dev is missing the option for landsat8
-----------------------+----------------------------------------------------
Reporter: vesnikos | Owner: grass-dev@…
Type: defect | Status: closed
Priority: normal | Milestone: 7.0.0
Component: Imagery | Version: svn-trunk
Resolution: fixed | Keywords: i.landsat.toar
Platform: All | Cpu: Unspecified
-----------------------+----------------------------------------------------
Changes (by neteler):
* status: new => closed
* resolution: => fixed
Comment:
Replying to [comment:8 nikosa]:
> > Replying to [vesnikos]:
>
> Maybe you can close this ticket as i.landsat.toar knows about Landsat8
now!
> We can open a new ticket for the other issues.
Yes, closing (and also the other issue has been fixed).