[eoxserver-dev] EOXServer - resources - coverages - channel records

[Stephan Krause]

Hi Martin, dear Dev'ers,

we are now about to finish the coverage model changes in 
sandbox_coverage_model. These changes include modifications to the range 
type and channel models as well.

First of all ChannelRecord is renamed to BandRecord and has a new 
structure.The old structure was closely related to the GML Coverage 
model and SWE Common, i.e. to the metadata descriptions of the range 
typel. The new structure is more closely related to the way GDAL stores 
band metadata like data type and so on. So, the

allowed_values_start,
allowed_values_end,
allowed_values_significant_figures

columns all have disappeared. This metadata (needed for SWE Common 
descriptions of the band's data type) is now computed from the data_type 
field of RangeTypeRecord.

You are right that we still have a problem with non-integer Nil Values, 
that we will need for SAR data. I will finish the current data model 
changes and create a ticket for that issue.

regards,
Stephan


On 2011-06-30 12:22, Martin Paces wrote:
>
> Dear all,
>
> after having a look on the EOX server mode for coverages I wonder how 
> would you describe a floating point values channel when you define the 
> values as integers. Imagine a dB scale of a SAR intensity image, 
> having NaN or 1e-30 as the NIL values.
>
> Further I see names like
>
> allowed_values_start (does it mean minimum?)
> allowed_values_end (does it mean maximum?)
> allowed_values_significant_figures (no idea what this could be)
>
> are quite confusing.
>
> Cheers
> Martin
>
>
>