Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support UAVSAR reading and SET correction #722

Merged
merged 3 commits into from
Jan 17, 2022
Merged

Conversation

yunjunz
Copy link
Member

@yunjunz yunjunz commented Jan 17, 2022

Description of proposed changes

  • support UAVSAR native geometry file reading and SET correction with time info
  • improved auto lat/lon step for geocoding

Reminders

  • Pass Codacy code review (green)
  • Pass Circle CI / local test (green)
  • If modifying functionality, describe changes to function behavior and arguments in a comment below the function declaration.
  • If adding new functionality, add a detailed description to the documentation and/or an example.

+ readfile: support reading UAVSAR .ann/lkv/llh files
   - add read_uavsar_ann() to read the *.ann file into an dict object
   - read_attribute(): add metadata preparation for *.lkv and *.llh file
   - get_slice_list(): provide explicit list of dataset names for *.lkv and *.llh files
   - read_binary_file(): support multiple bands for non-traditional-InSAR processors.

+ prep_isce: add generate_random_baseline_timeseries() to support `-b random` input to generate a bperp time series with random values as place holders for mintpy processing.

+ solid_earth_tides: support T in time [for UAVSAR]
+ readfile/writefile: use numpy data type string as standard for mintpy, and use it for the convention translation during data I/O.
   - DATA_TYPE_ENVI2NUMPY
   - DATA_TYPE_NUMPY2ENVI
   - DATA_TYPE_GDAL2NUMPY
   - DATA_TYPE_NUMPY2GDAL
   - DATA_TYPE_ISCE2NUMPY
   - DATA_TYPE_NUMPY2ISCE

+ ifg_inv: use diff name for numInvOffRg/Az.h5 files
Add utils0.auto_lat_lon_step_size() to calculate the default output lat/lon steps for geocoding.

By default, the current version ensure the same number of rows and columns between input and output files; while this new version ensures the same pixel area between the input and output files and with proper dimension ratio using the bounding box of an rotated rectangle. Thus, this is a better version, especially when the azimuth angle is far from the pure north-south, such as the UAVSAR flight path, or when the space-borne SAR track is long.
@yunjunz yunjunz merged commit 70d606e into insarlab:main Jan 17, 2022
@yunjunz yunjunz deleted the uavsar branch January 17, 2022 05:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant