-
Notifications
You must be signed in to change notification settings - Fork 7
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
Save the zero-Doppler spacing in meters in the product's metadata #83
Conversation
… azimuth pixel spacing and save it in the RTC-S1 metadata
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code itself looks good to me, but I would like to hold this off until we come up with conclusion about the PR on s1-reader
side.
Sounds good. Thank you, @seongsujeong ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Pending my suggestion about the s1reader version that the patch release of RTC-S1 is going to use.
Also please bump the version of RTC-S1 accordingly.
HI @seongsujeong and @hfattahi , just updated this PR. The check for an empty polygon was introduced in commit 2e6eebb. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Just a nit picks. Thanks for the PR @gshiroma
Co-authored-by: Seongsu Jeong <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks @gshiroma
This PR updates the RTC-S1 SAS to save the zero-Doppler spacing in meters in the products' metadata. It requires the OPERA S1-Reader version
0.2.4
that provides the new attributeaverage_azimuth_pixel_spacing
parsed from the S1 annotation files fieldazimuthPixelSpacing
.