Hi all
Well, since I'm only evaluating (for now) how to import GRIB's into
GRASS, I wanted to test the r.region solution.
Can anyone describe me what to do regarding that suggestion?
Hamish, about the patch, I'm using GDAL1.7 so I cannot apply your patch.
I'm going to reply on this in GDAL bug tracker.
Thanks
It is so interesting to see vastly different approaches to solve a
similar problem. I'm downloading NOAA forecast data which is in GRIB
format. I run the files through degrib and then parse the shape files with
a C program using the shapelib libraries and create a new shape file which I
import into GRASS with v.in.ogr. I plot the values with d.vect.thematic.
The resulting maps can be viewed at:
http://www.ars.usda.gov/npa/marc/heatstress
That reminds me, I originally set up a location for each region with an
eye forward on multithreading the map generation phases. I forgot the
reason in the middle of the project and created several regions in one
location. I had to revert back to a location for each region when I
implemented multithreading but reduced the total map generation time from
several hours to 15 minutes. :-)
Randy
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 5189 (20100611) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
