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

prep_aria: add more metadata #139

Merged
merged 3 commits into from
Jul 25, 2019
Merged

prep_aria: add more metadata #139

merged 3 commits into from
Jul 25, 2019

Conversation

yunjunz
Copy link
Member

@yunjunz yunjunz commented Jul 24, 2019

prep_aria:

  • comment out skimage.transform.resize() because the updated ariaTSsteup.py produces the same size DEM file as the interferogram stack, this eliminates the need of installing scikit-image module while running prep_aria.py within the ARIA-tools python environment.

  • copy over all metadata from unwrappedPhase for the sake of completeness, except for Dates and bperp

  • add metadata extraction for:

    • ANTENNA_SIDE
    • HEADING
    • RANGE_PIXEL_SIZE
    • LON/LAT_REF1/2/3/4
    • CENTER_LINE_UTC
  • write all ifgrams in the sorted order of date1_date2 with date1 < date2

  • comment out geometry dataset azimuthAngle and shadowMask for now since both of them are not required by mintpy. Together with waterMask, they can be added afterward when the products are available from ARIA-tools.

  • more print out message for file IO

utils/ptime: remove obsolete ifgram_date_list() to that ptime.py can be independent from h5py module

add ARIA format link to README.md

Update indentation in smallbaselineApp.cfg

prep_aria:

+ comment out skimage.transform.resize() because the updated ariaTSsteup.py produces the same size DEM file as the interferogram stack, this eliminates the need of installing scikit-image module while running prep_aria.py with the `ARIA-tools` python environment.

+ copy over all metadata from unwrappedPhase for the sake of completeness, except for Dates and bperp

+ add metadata extraction for:
   - ANTENNA_SIDE
   - HEADING
   - RANGE_PIXEL_SIZE
   - LON/LAT_REF1/2/3/4
   - CENTER_LINE_UTC

+ write all ifgrams in the sorted order of date1_date2 with date1 < date2

+ comment out geometry dataset azimuthAngle and shadowMask for now since both of them are not required by mintpy. Together with waterMask, they can be added afterward when the products are available from ARIA-tools.

+ more print out message for file IO

utils/ptime: remove obsolete ifgram_date_list() to that ptime.py can be independent from h5py module

add ARIA format link to README.md

Update indentation in smallbaselineApp.cfg
@yunjunz yunjunz added this to the support ARIA GUNW products milestone Jul 24, 2019
@yunjunz
Copy link
Member Author

yunjunz commented Jul 24, 2019

Hi @ehavazli, could you check if all the operations you have used before work for you?

After 1) this merge and 2) fix the issue with bridging, I will cut a new release.

mintpy/prep_aria.py Outdated Show resolved Hide resolved
mintpy/prep_aria.py Outdated Show resolved Hide resolved
@ehavazli
Copy link
Contributor

everything ran without failing for a small test case (@hfattahi San Francisco data set) so it looks good to me.

meta["WIDTH"] = ds.RasterXSize
meta["NUMBER_OF_PAIRS"] = ds.RasterCount

# ARIA standard products currently don't number of range and
az_angle = float(meta["azimuthAngle"])
Copy link
Member Author

@yunjunz yunjunz Jul 24, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ehavazli and @dbekaert, this value azimuthAngle = -8.77992802893209 does not seem like the azimuthAngle of the satellite orbit (band2 of los.rdr from ISCE/topsStack); but more like the azimuth angle of the LOS vector (from incLocal.rdr), could you confirm?

As a reference, the band2 of los.rdr from ISCE/topsStack for descending track has a typical value of -102

If we got the HEADING angle of the satellite orbit, the ORBIT_DIRECTION can be drived from here.

Copy link
Contributor

@ehavazli ehavazli Jul 24, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

azimuth angle in the VRT metadata is an average value. Azimuth angle information is extracted from the product. I am testing the new ariaTSsetup.py with the orbit direction information being included in the metadata of VRT.

Extracted azimuth angle file can be uploaded into geometryGeo.h5 just like incidence angle by adding the option into prep_aria.py

@ehavazli ehavazli self-requested a review July 25, 2019 18:48
+ use orbitDirection from ARIA metadata
+ hardwire HEADING value for now based on asc/desc orbit
+ add -a/--az-angle option
+ update example
@yunjunz
Copy link
Member Author

yunjunz commented Jul 25, 2019

Updated according to the latest dev branch of ARIA-tools. All metadata seems reasonable to me now. If one of you two could approve this pull request, I will go forward and merge it.

@yunjunz
Copy link
Member Author

yunjunz commented Jul 25, 2019

@ehavazli

Copy link
Collaborator

@hfattahi hfattahi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

@yunjunz yunjunz merged commit 857063f into insarlab:master Jul 25, 2019
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.

None yet

3 participants