<br><br><div class="gmail_quote">On Tue, Oct 4, 2011 at 10:16 AM, Jennifer Adams <span dir="ltr"><<a href="mailto:jma@cola.iges.org">jma@cola.iges.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word">Hi, Jonathan -- <div>GrADS should be able to read your .he5 file if it contains gridded data. The file naming convention is unconventional, and it is not immediately apparent to me what the two date strings mean. Your best bet may be to use chsub to map complete filenames to the time steps they contain, something like :</div>
<div><br></div><div>dset /Users/jonathanwsmith/DATA/OMI_DOMINO_NO2/FIRST_LEG/%ch</div><div>chsub 1 XX OMI-Aura_<span class="Apple-style-span" style="background-color: rgb(255, 255, 0);">L2-</span>OMDOMINO_2006m0522t0926-o09846_v003-2010m1007t075325.he5</div>
<div><br></div></div></blockquote><div><br></div><div>These are Level 2 files, therefore swath data. The strings identify the orbit and processing time, not really grads templatable. What I do in my own research is to grid these Level 2 files to a global lat/lon grid, with lots of UNDEFs where the swath isn't (thanks to compression, file size is not an issue); I do this in python. Here is an example for OMI aerosols:</div>
<div><br></div><div> <a href="http://opendap.nccs.nasa.gov:9090/dods/AeroObs/0.25_deg/omaeruv">http://opendap.nccs.nasa.gov:9090/dods/AeroObs/0.25_deg/omaeruv</a></div><div><br></div><div>The ability of handling swath data is something that GrADS developers have talked about in many occasions, but it is yet to be implemented.</div>
<div><br></div><div> Arlindo</div></div><div><br></div>-- <br>Arlindo da Silva<br><a href="mailto:dasilva@alum.mit.edu">dasilva@alum.mit.edu</a><br>