pixel2map needs improved documentation
The pixel2map program has some confusing documentation. It needs improved.
The examples below are Mars Reconnaissance Orbiter/CRISM cubes where scan lines do not overlap in their original state. The major difference is in the output of the application used to project the cube. Both applications will project the cube, but also result in a different spatial outcome. Left Cube: cam2map was chosen to project the cube. Notice the scan lines have been interpolated thus filled. If you want to preserve gaps, cam2map will not achieve this result. In addition, the cube is no longer spatially correct. Right Cube: pixel2map was chosen to project the cube. Notice how the gaps are retained in the output. The cube is spatially correct.
The above paragraph contains "the cube is no longer spatially correct", this section has mislead readers. The cam2map output is spatialy correct it just filled in all the areas between pixels.
#3 Updated by Jason Laura over 2 years ago
- Story points set to 10
This is the developer reviewing the code and documenting the functionality.
This is including use cases:
* Existing use cases
* Vims - what not to do
* DAWN VIR
6 Dev: 4 User
3 tickets - 3sp dev review, 3sp dev documentation, 4 sp user review docs and iterating