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

conv2tif does not work with different X and Y pixel resolutions #305

Closed
mcgarth opened this issue Oct 26, 2020 · 11 comments
Closed

conv2tif does not work with different X and Y pixel resolutions #305

mcgarth opened this issue Oct 26, 2020 · 11 comments
Assignees

Comments

@mcgarth
Copy link
Contributor

mcgarth commented Oct 26, 2020

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)

@mcgarth
Copy link
Contributor Author

mcgarth commented Oct 26, 2020

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

@Jesse-kearse
Copy link

Jesse-kearse commented Oct 26, 2020

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"

msg = 'X and Y cell sizes do not match: %s & %s'

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

<VRTDataset rasterXSize="23179" rasterYSize="10601">
    <SRS>EPSG:4326</SRS>
    <GeoTransform>171.06490487583588, 0.00010261051442909, 0.0, -42.99785174151206, 0.0, -0.0001027265486936</GeoTransform>
    <VRTRasterBand dataType="Float32" band="1" subClass="VRTRawRasterBand">
        <SourceFilename relativeToVRT="1">filt_topophase.unw.geo</SourceFilename>
        <ByteOrder>LSB</ByteOrder>
        <ImageOffset>0</ImageOffset>
        <PixelOffset>4</PixelOffset>
        <LineOffset>185432</LineOffset>
    </VRTRasterBand>
    <VRTRasterBand dataType="Float32" band="2" subClass="VRTRawRasterBand">
        <SourceFilename relativeToVRT="1">filt_topophase.unw.geo</SourceFilename>
        <ByteOrder>LSB</ByteOrder>
        <ImageOffset>92716</ImageOffset>
        <PixelOffset>4</PixelOffset>
        <LineOffset>185432</LineOffset>
    </VRTRasterBand>
</VRTDataset>

@Jesse-kearse
Copy link

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

@mcgarth
Copy link
Contributor Author

mcgarth commented Oct 26, 2020

I edited your comment, and wrapped the .vrt content in triple backquotes, which solves the display issue

@Jesse-kearse
Copy link

Jesse-kearse commented Oct 26, 2020 via email

@mcgarth
Copy link
Contributor Author

mcgarth commented Oct 26, 2020

Yes I understand what the issue is @Jesse-kearse and will look in to it with the team. Cheers

@mcgarth mcgarth changed the title conv2tif not working with ROI_PAC-looking ISCE products conv2tif does not work with different X and Y pixel resolutions Oct 26, 2020
@mcgarth mcgarth self-assigned this Oct 26, 2020
@mcgarth
Copy link
Contributor Author

mcgarth commented Oct 26, 2020

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 conv2tif step.

@mcgarth
Copy link
Contributor Author

mcgarth commented Oct 27, 2020

#306 has been merged in to master branch

@Jesse-kearse
Copy link

Jesse-kearse commented Oct 27, 2020 via email

@mcgarth
Copy link
Contributor Author

mcgarth commented Nov 16, 2020

Hi @Jesse-kearse, did you have a chance to check whether the changes I made sorted your problem?

@Jesse-kearse
Copy link

Jesse-kearse commented Nov 16, 2020 via email

@mcgarth mcgarth closed this as completed Dec 22, 2020
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

No branches or pull requests

2 participants