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
Common plot format to show number of multi-sensor overlaps for sites of interest. Take in user-input GeoDataFrame that contains multiple primary aerial LiDAR sites. Also take into account same parameters for cascading_search
The first plot/map will show the entire user-input GeoDataFrame, with color ramp for acquisition date.
Could also break this up into two plots pre-2019 and then 2019-present. Use threshold for the first valid L2A GEDI acquisition dates.
Then a round of plots for hits of unique combinations of each additional source (eg. WV stereo, ICESat-2, GEDI) defined in the cascading search params. So the LiDAR footprints that have valid overlaps for each unique combination of each additional source are shown in subplots
Then users will know what 'hit combination' they want to analyze. Or, if they already knew this before, they can call the below function for additional contextual data:
All LiDAR footprint extents with color ramps based on: acquisition date, total overlap area, mean elevation, standard deviation elevation, range elevation, and a land cover pie chart for each site where the size of the pie chart is relative to the overlap area
I think this should be more of an 'estimated' search, so searching and analyzing chull or simplified geometries since there will be a lot of polygon processing going on under the hood.
Let me know your thoughts!
The text was updated successfully, but these errors were encountered:
Common plot format to show number of multi-sensor overlaps for sites of interest. Take in user-input GeoDataFrame that contains multiple primary aerial LiDAR sites. Also take into account same parameters for
cascading_search
Then users will know what 'hit combination' they want to analyze. Or, if they already knew this before, they can call the below function for additional contextual data:
I think this should be more of an 'estimated' search, so searching and analyzing chull or simplified geometries since there will be a lot of polygon processing going on under the hood.
Let me know your thoughts!
The text was updated successfully, but these errors were encountered: