Daniele Romagnoli a écrit :
> The fillValue is equal to the minimun value.
> As an instance: fillValue = 0;
> validMin = 0; validMax = 255
> scale = 0.15
> offset = 0
(...snip...)
> defined categories: Category("No data":[0.0 ... 0.0]),
> Category("values":[4.9E-324 ... 255.0]) ---- Note the value 4.9E-324
> having defined the Minimum = 0 EXCLUDED.
Given that the "non-geophysics" view typically uses integer values (it is not
forced, but this is the typical case) while the "geophysics" view uses floating
point values, why not defines the validMin to 1?
Alternatively, you can also try to create a NumberRange as below:
NumberRange range = NumberRange.create(0, false, 255, true);
where the boolean argument tells that 0 is exclusive while 255 is inclusive.
Martin
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
