Major code review of G3d library and related modules

Announced with Ticket #1389 a major code review by Sören Gebbert was done to remove the confusion about the row ordering implementation in the G3d library and to provide a consistent behavior for all G3d related modules. Since r46788 the G3d library and therefor all related modules are using now consistently the row order approach of the raster library. The coordinate ordering and tile approach is visualized here: ​G3d volume layout.

Changes in the G3D library

• Consolidation of putValue() and getValue() function from several different source files into a single source file
• Re-implementation and addition of several coordinate transform functions
• Rewrite of the nearest neighbor resampling function
• A new function to compute the optimal tile size for new created G3d maps was implemented
• Update of the Doxygen documentation to document the row order approach
• Added test suite to test the get- and putValue() functions as well as the coordinate transform functions

G3d related module changes

All G3d related modules have been code reviewed, three new modules have been implemented and several have been modified to use the correct row order approach. Test cases for automated testing using the new planed ​test framework have been implemented for many modules.

• New modules
  • r3.colors to modify color tables for raster3d maps
  • r3.colors.out to export raster3d color tables
  • r3.retile to create new raster3d maps with different tile size

• Only code review for modules
  • v.vol.rst
  • r3.timestamp
  • r3.in.v5d
  • r3.out.v5d
  • r3.univar

• Code reviewed, bug fixes and test cases designed and implemented for modules
  • r.to.rast3
  • r.to.rast3elev
  • r3.to.rast
  • r3.inascii
  • r3.out.ascii
  • r3.out.vtk
  • r3.stats
  • r3.cross.rast
  • r3.null
  • v.to.rast3

• Major code and functionality updates
  • r3.in.ascii
  • r3.out.ascii
  • r3.info