search

google-code-export / ccc-gistemp

Automatically exported from code.google.com/p/ccc-gistemp
Other
0 stars 0 forks source link

exports of data for GIS software #110

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
David Jones:
It seems to me that to be of use to you ccc-gistemp would need to:
 - produce a gridded dataset that includes sea surface temperatures
(this is generated internally before computing zonal and global
anomalies, but not currently output);
 - produce gridded datasets that could be consumed by GIS software;
 - (and possibly) either regrid to a standard grid, or modify the
algorithm to use a standard grid rather than the Hansen & Lebedeff
grid. 

For more information see thread:
http://groups.google.com/group/ccc-gistemp-discuss/browse_thread/thread/c3818ae1
90d7b3ae

Original issue reported on code.google.com by fraxi...@oxel.net on 10 Mar 2011 at 9:11

GoogleCodeExporter commented 9 years ago 
(Perhaps not directly relevant to the point in question, but hopefully someone 
will find it useful when we get round to "doing GIS" for ccc-gistemp)

Joel Lawhead's pyshp (pure python) library reads and writes "shapefiles" which 
is one of those funky GIS formats.  I've used it and it's approximately awesome.

http://geospatialpython.com/2010/11/introducing-python-shapefile-library.html
http://code.google.com/p/pyshp/

Original comment by drj...@googlemail.com on 18 Aug 2011 at 10:53

GoogleCodeExporter commented 9 years ago 
Note that shapefiles are vector data, the outputs from ccc-gistemp should most 
likely be gridded/raster GIS data. The simplest format there is ArcInfo gridded 
ascii files - see for instance 
http://docs.codehaus.org/display/GEOTOOLS/ArcInfo+ASCII+Grid+format

ArcInfo gridded ascii files are fairly universal.

Original comment by fraxi...@oxel.net on 19 Aug 2011 at 8:27