Ahhh ok I see<div>But it's not possible to GRASS to identify each layer of HDF5 file?</div><div>Yes, indeed it looks odd and not very practical :(.</div><div><br></div><div>And regarding other products, example CEOS, it's necessary to specify also CEOS:/file bla bla bla?</div>
<div><br></div><div>Thank you Markus</div><div><br></div><div>Pedro<br><br><div class="gmail_quote">On Fri, Feb 12, 2010 at 1:45 PM, Markus Neteler <span dir="ltr"><<a href="mailto:neteler@osgeo.org">neteler@osgeo.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Fri, Feb 12, 2010 at 1:56 PM, Pedro Roma <<a href="mailto:pedroroma1982@gmail.com">pedroroma1982@gmail.com</a>> wrote:<br>
> Hi<br>
> This is the command:<br>
> r.in.gdal input=/mnt/GIS/data/HDF5_GEO_200101011450 output=file_out<br>
><br>
> and the error is:<br>
> Projection of input dataset and current location appear to match<br>
> ERROR: Selected band (1) does not exist<br>
<br>
</div>As stated in<br>
<div class="im"><a href="http://www.gdal.org/frmt_hdf5.html" target="_blank">http://www.gdal.org/frmt_hdf5.html</a><br>
<br>
</div><div><div></div><div class="h5">you have to specify all the long funky name indicated in SUBDATASETXX.<br>
<br>
Looks odd but it is the only way to the the data imported.<br>
<br>
Markus<br>
</div></div></blockquote></div><br></div>