-
Notifications
You must be signed in to change notification settings - Fork 6
Description
New format for the range-range velocity pair:
-
chip_size_height
[maximum value across the two input granules]- Propagate NaN's
-
chip_size_width
[maximum value across the two input granules]- Propagate NaN's
-
chip_size_height:azimuth_pixel_size and chip_size_width:range_pixel_size
- We are only using chip_size_width:range_pixel_size
- Take the maximum chip_size_width:range_pixel_size and use that to populate both:
chip_size_height:azimuth_pixel_size and chip_size_width:range_pixel_size
-
img_pair_info attributes (attributes that become data arrays in datacubes):
NOTE: granule 1 is the one with the earliest mid date-
acquisition_date_img1
[minimum acquisition_date] -
acquisition_date_img2
[maximum acquisition_date] -
date_center
[average date_center] -
date_dt
[not sure about this one] -
roi_valid_percentage
[not sure about this one] -
satellite_img1
[just "1"] -
satellite_img2
[just "1"] -
sensor_img1
[granule 1 sensor_img1]
* granule 1 is the one with the earliest mid date -
sensor_img2
[granule 2 sensor_img1]
* granule 1 is the one with the earliest mid date -
Centroid longitude and latitude
- Compute based on new x and y extends.
-
id_img1/2 should reference the original granules, then much of the metadata gets filled with NaNs and the user needs to look at the original granules
-
flight_direction_img1/2 gets populated from the input granules as one granule will be ascending and the other descending.
-
mission_data_take_ID_img1/2 are NaN's
-
mission_img1/2 is always 'S'
-
-
interp_mask
[any interp_mask in granule 1 or granule 2] -
v_error
[we need to propagate this from granule 1 or granule 2 range errors] -
vx and vy attributes (attributes that become data arrays in datacubes):
[we need to propagate this from granule 1 or granule 2 range errors]error_modeled
error_slow
error_stationary
stable_shift
stable_shift_slow
stable_shift_stationary
Notes:
- Do we keep M11, M12, va, vr?
[NO]