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

what footprint to show for high-res data ? #115

Open
falkamelung opened this issue Oct 18, 2024 · 0 comments
Open

what footprint to show for high-res data ? #115

falkamelung opened this issue Oct 18, 2024 · 0 comments
Labels
Discussion Discussion

Comments

@falkamelung
Copy link
Member

falkamelung commented Oct 18, 2024

  1. There have been some changes to the workflow. Can you please remind me what you use for drawing the blue box and what the footprints are used for?

From your screenshot I see it uses mintpy.subset.lalo for the high-res data. It rather should use miaplpy.subset.lalo. If this does not exist, then use mintpy.subset.lalo. If that does not exist then use what it regularly uses.

//perfectly-elegant-tapir/data/HDF5EOS/unittestGalapagosSenDT128/mintpy[613] 

info.py S1_IW1_128_0596_0597_20160605_XXXXXXXX_S00887_S00783_W091208_W091105.he5 | grep subset
  miaplpy.subset.lalo                         -0.86:-0.81,-91.19:-91.13
  mintpy.save.hdfEos5.subset                  yes
  mintpy.subset.lalo                          -0.86:-0.81,-91.19:-91.13

info.py S1_IW1_128_0596_0597_20160605_XXXXXXXX_S00887_S00783_W091208_W091105.he5 | grep footprint

 data_footprint                              POLYGON((-91.2076997919052 -0.7825726544736832,-91.1054128723712 -0.7825726544736832,-91.1054128723712 -0.8873331006288048,-91.2076997919052 -0.8873331006288048,-91.2076997919052 -0.7825726544736832))

 scene_footprint                             POLYGON((-90.79576564433012 -0.6879060069659138,-90.86903846064074 -1.0359985136024503,-91.62398374523922 -0.872931313659136,-91.55057822990057 -0.5251674707332538,-90.79576564433012 -0.6879060069659138))
  1. For the high-res data it used to be drawing the swath/scene footprint (much bigger than the actual data area), and when you click on it you got the smaller, data area. Is this needed? I don't see much benefit of showing the swath. The current data_footprint is a straight N-S-E-W rectangle although the data area is inclined in satellite-flight direction (swath-type but smaller). It would be preferred to show the inclined actual data coverage. I wonder how to do this. Assuming that modifying data_footprint is not a good idea, shall we introduce a new field such as tight_data_footprint ?

One advantage would that it will be straightforward to discern the basic LOS (current) data from vertical and east-west. The latter would always have a straight rectangle.

@falkamelung falkamelung added the Discussion Discussion label Oct 18, 2024
@falkamelung falkamelung changed the title what footprint to show for high-res data what footprint to show for high-res data ? Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion Discussion
Projects
None yet
Development

No branches or pull requests

1 participant