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

Decide how to handle CRS transforms #17

Open
aazuspan opened this issue Oct 13, 2023 · 0 comments
Open

Decide how to handle CRS transforms #17

aazuspan opened this issue Oct 13, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@aazuspan
Copy link
Contributor

Need to decide how best to handle CRS transforms when exporting NAIP imagery, to ensure that predicted maps can be aligned with other rasters.

See @grovduck's comment from #11:

I guess my thought would be this cascade:

  1. If CRS_TRANSFORM is defined in config.py, use that preferentially (this is probably what I would do to ensure that all predictions lined up with other covariates in further modeling.)
  2. (This one might be tricky because the lidar dataset isn't referenced in 03_export.ipynb). Use the crsTransform of the lidar data that was used to fit the model. This ensures the same snap to the lidar data for prediction and comparison.
  3. If neither 1. or 2. is present, use the (projected) corner of the BBOX to set the transform.
@aazuspan aazuspan added the enhancement New feature or request label Oct 13, 2023
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

No branches or pull requests

1 participant