[Gdal-dev] Recommendations for vertical data in GDAL

[Frank Warmerdam]

Ray Gardener wrote:
> 
> 
>>
>> On a few specific points:
>>  o I'm not too keen on encoding procedural relationships between raw
>>    pixels values and elevation values.  But the "raster attribute table"
>>    could potentially be used to encode descrete mappings for a limited
>>    number of pixel values.
> 
> Well, it's not just for elevations, any kind of band data would be 
> served by that. The driver's already a bunch of format-specific code 
> anyway, it doesn't change anything to make it have a logical-to-physical 
> and vice-versa method. In fact, that's almost the first thing it should 
> have since we need to abstract content access.

Ray,

My concern isn't with how a driver might transform the data to present
it to the application.  I'm fine with that.  I'm just afraid of making
procedural relationships part of the data model, or else we need a way of
supporting them in many formats.

Best regards,
-- 
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | President OSGF, http://osgeo.org