Changeset 30458
- Timestamp:
- Mar 4, 2008, 1:52:48 AM (16 years ago)
- File:
-
- 1 edited
-
grass/trunk/lib/gis/gisrasterlib.dox (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
grass/trunk/lib/gis/gisrasterlib.dox
r29975 r30458 32 32 - \subpage \ref GRASS_5_raster_API 33 33 - \subpage \ref Upgrades_to_Raster_Functions 34 - \subpage \ref Null_no_data 34 35 - \subpage \ref Color_Functions 35 36 - \subpage \ref New_functions_to_support_colors_for_floating_point … … 1639 1640 1640 1641 <P> 1642 1643 \section Null_no_data NULL (no data) handling 1644 1645 -2^31 (= 0x80000000 = -2147483648) is the null value 1646 for the CELL type, so you'll never see that value in a map. 1647 1648 The FP nulls are the all-ones bit patterns. These corresponds to NaN 1649 according to the IEEE-754 formats, although it isn't the "default" NaN 1650 pattern generated by most architectures (which is usually 7fc00000 or 1651 ffc00000 for float and 7ff8000000000000 or fff8000000000000 for 1652 double, i.e. an all-ones exponent, the top-bit of the mantissa set, 1653 and either sign). 1654 1655 So far as arithmetic is concerned, any value with an all-ones exponent 1656 and a non-zero mantissa is treated as NaN. But the GRASS 1657 G_is_[fd]_null_value() functions only consider the all-ones bit 1658 pattern to be null. I intend to change this in 7.x so that all FP NaN 1659 values are treated as null. This will mean that code which can 1660 generate NaNs doesn't have to explicitly convert them to the GRASS 1661 null value. 1641 1662 1642 1663 \section Color_Functions Color Functions (new and upgraded)
Note:
See TracChangeset
for help on using the changeset viewer.
