SNAP Auxdata

Goals

• Find a common home for auxdata

Background and strategic fit

Former user (Deleted): how to generally deal with modules (processors) that require lots of auxdata. We actually don't want them to be kept in the toolbox repository in order to avoid copying of data that rarely changes. One option is to put auxdata in separate Maven modules and let a processor depend on them. The advantage would be that we have them under Maven configuration control (groupId + artifactId + version). We may combine this approach with the actual auxdata be kept somewhere else, e.g. //step.esa.int/auxdata/${dataset}, which may be downloaded on demand to .snap/auxdata/${dataset} if a processor requires them.

Luis Veci: We also have auxdata that doesn't change but can be large and should be downloaded as need such as DEMs. There are also small data like orbit files and calibration files which are routinely produced for active missions and are static for retired missions.

Assumptions

• We can use > 100GB on step
• If more space is needed in the future ESA will provide
• Users have internet access to download data as needed

Requirements

User interaction and design

Questions

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

Not Doing