You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Good call. Yes, I think we want to treat IfSAR as separate dataset than the 3DEP airborne lidar. Also need to check acquisition time metadata and flightlines. The IfSAR data should be distributed in tiles, which could include multiple flights per tile.
There is value in considering the IfSAR in addition to the small subset of available 3DEP lidar data in AK, as it is a complementary airborne X-band InSAR source with ~5 m posting. I have some existing notes from analysis of IfSAR with WV stereo DEMs that I can share.
Oooh, that's exciting. We should consider the lidar technology type in site selection, and look more closely at QL levels.
Curious about performance of avilable Gm options. I assumed everything in 3DEP archive was linear-mode.
Coincident version: 0.1.dev40+gfa66db4.d20241108
Custom Python 3.12.5 environment
Filter out IfSAR returns from
coincident.search.search(dataset="3dep")
. Or add a boolean argument to include IFSAR results or not.https://www.usgs.gov/centers/eros/science/usgs-eros-archive-digital-elevation-interferometric-synthetic-aperture-radar
Below is how I found the IFSAR flights:
The text was updated successfully, but these errors were encountered: