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

Provide GCPs or at least extent with burst data #54

Closed
alexamici opened this issue May 10, 2021 · 2 comments
Closed

Provide GCPs or at least extent with burst data #54

alexamici opened this issue May 10, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@alexamici
Copy link
Member

At the moment the only way to link the burst to the associated GCPs is to match the azimuth_times and slant_range_times.

It would be helpful to attach some information on localisation of the burst (computed to define the burst name) to the burst dataset.

@alexamici
Copy link
Member Author

Added the get_footprint_linestring and the gcp arguments to crop_burst_dataset.

This is very tricky because interpolating on the numerically very different azimuth_time and slant_range_time is unstable and interpolating on line and pixel doesn't return the external polygon, but a slightly shorted one along the azimuth due to how crazily the bursts are encoded in a single tiff file.

This is good enough for many use cases.

@alexamici
Copy link
Member Author

In the end the it is closed by #115

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant