Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Target release1.0
Epic SNAP-2 - Getting issue details... STATUS
Document statusDRAFT
Document owner

Former user (Deleted)

Designer
Developers
QA

Goals

  • The following Java interfaces and classes currently operate on 32-bit floats: GeoCoding, GeoPos, PixelPos. Derived classes such as TiePointGeoCoding also perform their computations using 32-bit floats, while others, e.g. PixelGeoCoding use 64-bit internally.
  • Many hires applications require 64-bit precision both for internal computation and in the final delivery of results.

Background and strategic fit

Assumptions

Requirements

#TitleUser StoryImportanceNotes
1Tie point interpolation

Part of the problem is caused by the unit (lat lon in degrees, slant range time in seconds) but this should probably stay as is.

At high resolutions (< 1m), neighbouring pixels end up having the same value.

Tie Point Grids and DEMs need to be interpolated to the resolution of the data product.

Interpolators have already been made 64-bit. Now the resulting value needs to be saved as 64-bit.

 

     

User interaction and design

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome

Not Doing

  • No labels