support LAT/LON_REF1/2/3/4 in UTM coordinates#1161
Merged
yunjunz merged 1 commit intoinsarlab:mainfrom Mar 18, 2024
Merged
Conversation
+ docs/api/attributes.md: ensure all LAT/LON attributes represents both latitude/northing and longitude/easting in degrees/meters + utils.utils0.utm2latlon/latlon2utm(): support list/tuple input types + prep_hyp3: - do not convert UTM to lat/lon for LAT/LON_REF1/2/3/4 - add HDF-EOS5 metadata (`beam_mode` and `unwrap_method`) from the HyP3 metadata file + save_hdfeos5.metadata_mintpy2unavco(): convert UTM to lat/lon while calculating the scene_footprint and subset filename suffix + tests/configs/RidgecrestSenDT71: turn ON mintpy.save.hdfEos5 and mintpy.save.hdfEos5.subset options + .circleci/config.yml: add RidgecrestSenDT71 (HyP3) to the routine integration test + tropo_pyaps3.get_bounding_box(): convert UTM to lat/lon
ehavazli
pushed a commit
to ehavazli/MintPy
that referenced
this pull request
Mar 19, 2024
This commit adds the support of UTM coordinates for the `LAT/LON_REF1/2/3/4` metadata in all related docs/code, in addition to the existing support for the Y/X_FIRST/STEP/UNIT and REF_LAT/LON, UTM_ZONE and EPSG. Thus, all mintpy metadata now supports UTM coordinates. + docs/api/attributes.md: ensure all LAT/LON attributes represent both latitude/northing and longitude/easting in degrees/meters + utils.utils0.utm2latlon/latlon2utm(): support list/tuple input types + prep_hyp3: - do not convert UTM to lat/lon for LAT/LON_REF1/2/3/4 - add HDF-EOS5 metadata (`beam_mode` and `unwrap_method`) from the HyP3 metadata file + save_hdfeos5.metadata_mintpy2unavco(): convert UTM to lat/lon while calculating the scene_footprint and subset filename suffix + tests/configs/RidgecrestSenDT71: turn ON mintpy.save.hdfEos5 and mintpy.save.hdfEos5.subset options + .circleci/config.yml: add RidgecrestSenDT71 (HyP3) to the routine integration test + tropo_pyaps3.get_bounding_box(): convert UTM to lat/lon
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of proposed changes
docs/api/attributes.md: ensure all*LAT/LON*attributes represents both latitude/northing and longitude/easting in degrees/metersutils.utils0.utm2latlon/latlon2utm(): support list/tuple input typesprep_hyp3:LAT/LON_REF1/2/3/4beam_modeandunwrap_method) from the HyP3 metadata filesave_hdfeos5.metadata_mintpy2unavco(): convert UTM to lat/lon while calculating the scene_footprinttests/configs/RidgecrestSenDT71.txt: turn ONmintpy.save.hdfEos5option.circleci/config.yml: addRidgecrestSenDT71 (HyP3)to the routine integration testing.tropo_pyaps3.get_bounding_box(): convert UTM to lat/lon if usingLAT/LON_REF1/2/3/4in UTM coordinates.Reminders