Skip to content

Support SNAP .znap input reading #84

@Simon-van-Diepen

Description

@Simon-van-Diepen

SNAP outputs per epoch:

  • A .znap (SNAP-specific .zarr)-archive, one per acquisition (currently named YYYYMMDD-coreg.znap, can be altered if necessary/preferred), containing the following layers:
    * h2ph_<polarisation>_<epoch>: height-to-phase screen with the reference DEM subtracted cropped to the AoI (e.g. h2ph_VV_06Jan2023)
    * i_<polarisation>_<epoch>: real component of the reduced SLCs cropped to the AoI (e.g. i_VV_06Jan2023)
    * q_<polarisation>_<epoch>: imaginary component of the reduced SLCs cropped to the AoI (e.g. q_VV_06Jan2023)
    * incident_angle: incidence angle at each pixel
    * slant_range_time: slant range time at each pixel
    * elevation: DEM (only at the mother epoch)
    - coordinates:
    * latitude: latitude coordinates cropped to the AoI
    * latitude_<polarisation>: latitude coordinates cropped to the AoI (only at the mother epoch, difference unclear) (e.g. latitude_VV)
    * longitude: longitude coordinates cropped to the AoI
    * longitude_<polarisation>: longitude coordinates cropped to the AoI (only at the mother epoch, difference unclear) (e.g. longitude_VV)
    - metadata:
    * product metadata (in a JSON file located in *.znap/SNAP/product_metadata.json, related to Support reading metadata from SNAP corregistration results #82 )
    * ground control points (empty)
    * pins (empty)

This collection of .znap archives needs to be read into sarxarray, but the existing implementation does not allow for such a collection of .zarr archives (and real and imag do not exist in the variables as they have different names).

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions