Could someone confirm that MISR radiance/geometric data need an ad-hoc
importer for grass? I'm going to write down such a tool based on
MISR toolkit, just like to know if i'm wasting my time...
--
Francesco P. Lovergine
Francesco P. Lovergine wrote on 09/06/2007 10:40 AM:
Could someone confirm that MISR radiance/geometric data need an ad-hoc
importer for grass? I'm going to write down such a tool based on
MISR toolkit, just like to know if i'm wasting my time...
Maybe yes - did you check GDAL support? In the end everything goes through
GDAL into GRASS. That would be the best start to add a driver (if needed).
Does 'gdalinfo' fail?
Markus
------------------
ITC -> dall'1 marzo 2007 Fondazione Bruno Kessler
ITC -> since 1 March 2007 Fondazione Bruno Kessler
------------------
On Thu, 2007-09-06 at 10:40 +0200, Francesco P. Lovergine wrote:
Could someone confirm that MISR radiance/geometric data need an ad-hoc
importer for grass? I'm going to write down such a tool based on
MISR toolkit, just like to know if i'm wasting my time...
There is no module to specifically import the data easily, but r.in.gdal
will work.
Take a look at the r.in.aster script for details on importing HDF-EOS
imagery.
--
73, de Brad KB8UYR/6 <rez touchofmadness com>
On Thu, Sep 06, 2007 at 11:11:23AM +0200, Markus Neteler wrote:
Francesco P. Lovergine wrote on 09/06/2007 10:40 AM:
> Could someone confirm that MISR radiance/geometric data need an ad-hoc
> importer for grass? I'm going to write down such a tool based on
> MISR toolkit, just like to know if i'm wasting my time...
>
>
Maybe yes - did you check GDAL support? In the end everything goes through
GDAL into GRASS. That would be the best start to add a driver (if needed).
Does 'gdalinfo' fail?
It does not fail, because it is a HDF file variant, but metadata needs
to be used in order to extract and used properly in order to unpack the
stacked-block structure and use geo-location information.
Yes, I was thinking to that too in order to translate HDF-EOS2/MISR in other formats.
The MISR data are about complicated like the MODIS ones AFAIK.
--
Francesco P. Lovergine
On Thu, Sep 06, 2007 at 02:32:52AM -0700, Brad Douglas wrote:
On Thu, 2007-09-06 at 10:40 +0200, Francesco P. Lovergine wrote:
> Could someone confirm that MISR radiance/geometric data need an ad-hoc
> importer for grass? I'm going to write down such a tool based on
> MISR toolkit, just like to know if i'm wasting my time...There is no module to specifically import the data easily, but r.in.gdal
will work.Take a look at the r.in.aster script for details on importing HDF-EOS
imagery.
Eh, unfortunately ASTER and MODIS data _are_ supported for geolocation in
gdal, so r.in.aster is able to manage a few products directly through
gdal_warp. That's not the same for MISR where a few additional metadata also
need to be used to extract the true radiance and BRF fields and so on.
I think the most clean and effective approach is specializing the HDF4 driver for
MISR products in GDAL...
--
Francesco P. Lovergine