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

Parse azimuth fm rate polynomial #59

Merged

Conversation

seongsujeong
Copy link
Contributor

This PR is in regards to #51 when loading azimuth FM rate polynomial from LADS .xml files. It was found that some S1 SAFE data with old IPF has different format for the polynomial. The examples are as below:

S1A_IW_SLC__1SSV_20150114T015005_20150114T015035_004161_0050BB_87F4 (IPF 2.36)

<azimuthFmRate>
    <azimuthTime>2015-01-14T01:50:05.584900</azimuthTime>
    <t0>5.339831264815916e-03</t0>
    <c0>-2.327628769423934e+03</c0>
    <c1>4.493262758608217e+05</c1>
    <c2>-7.852728113753408e+07</c2>
</azimuthFmRate>

S1B_IW_SLC__1SDV_20170807T010035_20170807T010102_006827_00C043_B7E0 (IPF 2.82)

<azimuthFmRate>
    <azimuthTime>2017-08-07T01:00:35.780368</azimuthTime>
     <t0>5.334643585041154e-03</t0>
    <azimuthFmRatePolynomial count="3">-2.329768045614056e+03 4.502942424994464e+05 -7.864570826763810e+07</azimuthFmRatePolynomial>
</azimuthFmRate>

This fix detects if the field azimuthFmRatePolynomial exists in the input ET, and try different parsing strategy depending on the existence.

Seongsu Jeong and others added 30 commits June 16, 2022 21:12
Co-authored-by: Liang Yu <liangjyu@gmail.com>
Co-authored-by: Liang Yu <liangjyu@gmail.com>
Co-authored-by: Liang Yu <liangjyu@gmail.com>
Co-authored-by: Liang Yu <liangjyu@gmail.com>
Co-authored-by: Liang Yu <liangjyu@gmail.com>
Co-authored-by: Liang Yu <liangjyu@gmail.com>
Co-authored-by: Liang Yu <liangjyu@gmail.com>
Co-authored-by: Liang Yu <liangjyu@gmail.com>
Co-authored-by: Liang Yu <liangjyu@gmail.com>
Co-authored-by: Liang Yu <liangjyu@gmail.com>
seongsujeong and others added 18 commits August 2, 2022 15:17
Co-authored-by: Gustavo H. X. Shiroma <52007211+gshiroma@users.noreply.github.com>
Co-authored-by: Gustavo H. X. Shiroma <52007211+gshiroma@users.noreply.github.com>
Co-authored-by: Gustavo H. X. Shiroma <52007211+gshiroma@users.noreply.github.com>
Co-authored-by: Gustavo H. X. Shiroma <52007211+gshiroma@users.noreply.github.com>
Co-authored-by: Gustavo H. X. Shiroma <52007211+gshiroma@users.noreply.github.com>
Co-authored-by: Gustavo H. X. Shiroma <52007211+gshiroma@users.noreply.github.com>
Co-authored-by: Gustavo H. X. Shiroma <52007211+gshiroma@users.noreply.github.com>
Updating the main branch of this fork to update after `s1_annotation.py`
Copy link
Contributor

@gshiroma gshiroma left a comment

Choose a reason for hiding this comment

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

LGTM. Thank you for the update, @seongsujeong . I just have some minor comments: please avoid these types of qualitative statements, especially in CAPS LOCK: VERY old. Also, please follow PEP8 rules for inline comments (two spaces before and a single space after #): https://peps.python.org/pep-0008/#inline-comments .

Copy link
Contributor

@vbrancat vbrancat left a comment

Choose a reason for hiding this comment

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

LGTM, just some nit-picking :)

src/s1reader/s1_reader.py Outdated Show resolved Hide resolved
src/s1reader/s1_reader.py Outdated Show resolved Hide resolved
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.

4 participants