Is your feature request related to a problem? Please describe.
Not a problem, but currently the set-up requires a lot of data movement when users might be only needing a tiny fraction. Download is only supported for global files.
For insar pair conservative is at min 2 TROPO dates to be downloaded, and 4 if they want to perform temporal interpolation to the SAR time. As expected this can become rapidly a large volume. This is becoming privative to the using the data. Not all users will have the expertise to access the data through S3 and subset themselves on the fly.
Describe the solution you'd like
Past vertex/asf search support with the ARIA GUNW and extraction of the coh, unw layers might be a good place given similarity on the netcdf format and supported with GDAL drives.
it would be nice is asf_search and then through vertex allows for bbox intersect on the fly of this data using e.g. gdal.
Is your feature request related to a problem? Please describe.
Not a problem, but currently the set-up requires a lot of data movement when users might be only needing a tiny fraction. Download is only supported for global files.
For insar pair conservative is at min 2 TROPO dates to be downloaded, and 4 if they want to perform temporal interpolation to the SAR time. As expected this can become rapidly a large volume. This is becoming privative to the using the data. Not all users will have the expertise to access the data through S3 and subset themselves on the fly.
Describe the solution you'd like
Past vertex/asf search support with the ARIA GUNW and extraction of the coh, unw layers might be a good place given similarity on the netcdf format and supported with GDAL drives.
it would be nice is asf_search and then through vertex allows for bbox intersect on the fly of this data using e.g. gdal.