-
Notifications
You must be signed in to change notification settings - Fork 71
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
conv2tif does not work with different X and Y pixel resolutions #305
Comments
Hi @Jesse-kearse, if you give some details here of the problem you are encountering with conv2tif we can help look in to it. Nominally, it sounds like if you've generated .rsc header files from your ISCE products it should work in PyRate |
Thanks for your response, mcgarth. As part of the conv2tif process, the module "write_fullres_geotiff" within pyrate.core.shared.py calls "check_pixel_res_mismatch" Line 896 in eb4a444
It seems to want the x-step and y-step values to be the same, yet the dem that I am using for geocoding has different x and y steps. Will I need to use a "square" dem grid instead? example of geocoded interferogram .vrt file from ISCE
|
sorry the file did not print well in the above comment: EPSG:4326 171.06490487583588, 0.00010261051442909, 0.0, -42.99785174151206, 0.0, -0.0001027265486936 filt_topophase.unw.geo LSB 0 4 185432 filt_topophase.unw.geo LSB 92716 4 185432 |
I edited your comment, and wrapped the .vrt content in triple backquotes, which solves the display issue |
Thankyou Matt
I hope the issue I was trying to explain makes sense to you.
Cheers
…On Mon, Oct 26, 2020 at 5:55 PM Matt Garthwaite ***@***.***> wrote:
I edited your comment, and wrapped the .vrt content in , which solves the
display issue
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#305 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQHOJLRCTOW6VRIKWMTAD2DSMT6LRANCNFSM4S62J5IQ>
.
--
Jesse Kearse
PhD Student
Victoria University of Wellington
|
Yes I understand what the issue is @Jesse-kearse and will look in to it with the team. Cheers |
Hi @Jesse-kearse, I have raised PR #306 which I hope will sort things out for you. It would be great if you could test that for me and let me know if you are able to successfully get through the |
#306 has been merged in to |
Hi Matt
I will explore these changes in the next day or so and get back to you.
Thanks for your help
…On Wed, 28 Oct 2020, 11:04 Matt Garthwaite, ***@***.***> wrote:
#306 <#306> has been
merged in to master branch
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#305 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQHOJLSXSWUCCWHLHQCT6ZTSM47YHANCNFSM4S62J5IQ>
.
|
Hi @Jesse-kearse, did you have a chance to check whether the changes I made sorted your problem? |
Hi Matt
Sorry, I have been caught up in other research - I will run this shortly
and get back to you
…On Mon, Nov 16, 2020 at 6:22 PM Matt Garthwaite ***@***.***> wrote:
Hi @Jesse-kearse <https://github.com/Jesse-kearse>, did you have a chance
to check whether the changes I made sorted your problem?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#305 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQHOJLTN3FNMVHSTOLTUVOLSQCZH7ANCNFSM4S62J5IQ>
.
--
Jesse Kearse
PhD Student
Victoria University of Wellington
|
Hi
I am wanting to convert from the matlab-based version of pyrate to this python-based version. I am using ISCE products, and am running into issues with the conv2tif step. Is this the appropriate place to raise questions about specific errors?
Thanks for any help, and thank you for providing an awesome github repo
Originally posted by @Jesse-kearse in #40 (comment)
The text was updated successfully, but these errors were encountered: