GeoTIFF responses for Hyrax

From OPeNDAP Documentation
Revision as of 15:33, 29 March 2010 by Ndp (talk | contribs) (New page: GeoTIFF Output From Hyrax Why? The Data Access Protocol provides a way to transfer structured data into sophisticated analysis tools without first requiring that the data be packaged in ...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

GeoTIFF Output From Hyrax

Why?

The Data Access Protocol provides a way to transfer structured data into sophisticated analysis tools without first requiring that the data be packaged in particular format like TIFF which is so specialized it can only be practically used for a limited set of purposes. Instead DAP uses a very general self-describing format that can encode virtually anything stored in or processed by a computer. However, there are many applications now available that expect georeferenced data and can at least display such data if it’s encoded in one of several ways. While the main emphasis of OPeNDAP has been to provide data for analysis, these newer display applications are important tools for many users (and potential users) of our software. That is, even though ‘display’ of data has not be a primary focus of our work up to now, that doesn't mean it’s not important.

The idea is that like the netcdf_fileout it would return data in a GeoTIFF format. Obviously Grids would map well to GeoTIFF (assuming that the Grid has the requisite maps). We would need to either creatively represent other data types/structures or simply deny GeoTIFF access for non-grid data types. Even if we never build releasable WMS or WCS services adding this would allow others to easily wrap those services around our server.

Just creating this kind of output has the potential to increase our user base immensely.


How?

The idea is that like the netcdf_fileout it would return data in a GeoTIFF format. Obviously Grids would map well to GeoTIFF (assuming that the Grid has the requisite maps). We would need to either creatively represent other data types/structures or simply deny GeoTIFF access for non-grid data types. Even if we never build releasable WMS or WCS services adding this would allow others to easily wrap those services around our server. What?

Applications that would be able to display information from our servers includes: Google Earth, Google Maps, Google Maps for mobile devices, NASA WorldWind, ESRI ArcGIS Explorer, Adobe PhotoShop, AutoCAD, and Yahoo! Pipes.

To do:

  • What do we need to have to build ta GeoTIFF image? That is, how is a data set like a climatology returned as a GeoTIFF image?