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

Allow user to manually specify EPSG for output projection #147

Open
scottstanie opened this issue Oct 10, 2023 · 0 comments
Open

Allow user to manually specify EPSG for output projection #147

scottstanie opened this issue Oct 10, 2023 · 0 comments

Comments

@scottstanie
Copy link
Collaborator

Currently are getting the most common projection from the input SLCs here

projection = _get_mode_projection(file_list)

then using that to warp any difference inputs to the same projection before stitching here:
to_srs_name = osr.SpatialReference(projection).GetName()
logger.info(
f"Reprojecting {fn} from {from_srs_name} to match mode projection"
f" {to_srs_name}"
)

This is fine for most cases, but we may want to specify one EPSG for all stitching calls.
If we have a frame which falls on the border of two UTM zones, and there's a chance that a frame with missing data for some dates will get stitched to a different EPSG than the other images.

Additionally, we should do another check before running gdal_merge that the bounds we are passing make sense with the projection, as right now we are assuming that the bounds match the most-common projection

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

1 participant