ASP output files#
What the key files in an ASP run directory mean. Most are named with a RUN_PREFIX- followed by a fixed suffix. This is not every file, just those we are most interested in; the ASP output files docs describe everything.
After bundle_adjust -o ba/run#
File |
Contents |
|---|---|
|
Final matches between images (binary) |
|
Per-match reprojection residuals before optimization |
|
…after optimization |
|
Per-image camera adjustment (small text file) |
|
Full log; ASP version, command line, runtime |
After mapproject#
File |
Contents |
|---|---|
|
Image resampled onto reference DEM grid |
After parallel_stereo -o stereo/run#
File |
Contents |
|---|---|
|
Preprocessed left/right images |
|
Per-image masks |
|
Initial disparity from correlation, in whole-pixel shifts |
|
Disparity after subpixel refinement |
|
Final disparity after outlier filtering; the input to triangulation |
|
Gray where the correlator matched, red where it failed |
|
Point cloud (4 bands: x, y, z as offsets from a local origin, and ray intersection error) |
|
Snapshot of stereo parameters used |
|
Per-stage log files |
run-D.tif, run-RD.tif, and run-F.tif are successive versions of the same disparity map, all in one format: three bands holding the horizontal shift, the vertical shift, and a good-pixel mask. A run leaves further intermediates in the same format, such as run-D_sub.tif (the low-resolution disparity that seeds run-D.tif) and run-B.tif (run-D.tif blended across processing tiles).
After point2dem#
File |
Contents |
|---|---|
|
The DEM. Single-band float32, georeferenced. |
|
Orthoimage at the same grid (if |
|
Intersection error gridded onto the DEM (if |
|
Log |
After pc_align#
File |
Contents |
|---|---|
|
Source point cloud after alignment (in reference frame) |
|
4×4 rigid transformation matrix |
|
Inverse, for going back |
|
Log with begin/end percentile errors |