The On-Demand aoi-track API is a higher-level abstract for end-users of how to manage AOIs.
This API maps the concept of “aoi-track” to front end UI, onto the back-end dataset=aoi-track.
See Standard Product S1-GUNW Processing Pipeline for more details on the processing pipeline.
Endpoint | Function | Input | Output/Result |
---|---|---|---|
POST /aoi-track/ | Submit new aoi-track |
|
|
GET /aoi-track/ | List aoi-track
| none |
|
GET /aoi-track/{aoitrack_id} | Get aoi-track |
|
|
Implementation Notes
fork to new create_aoitrack job type
Note: dataset=area_of_interest does not have track info in the dataset. Fork https://github.com/hysds/create_aoi to create alternate “create_aoitrack” where the track number and orbit direct is intrinsic in the dataset. This job creates aoitrack.dataset.json with space and time extents. Update aoitrack.met.json to also include the track_number and orbit_direction. username is already included.
update jenkins to build new job type create_aoitrack and register into https://mamba-mozart.aria.hysds.io/figaro/
create new aoi-track
calls mozart api to submit new job “create_aoi-track:develop”.
reference example of how to submit mozart api job in python: https://github.com/aria-jpl/scihub_acquisition_scraper/blob/develop/crons/aoi_ipf_scrape_cron.py
job type “create_aoi-track:develop” will result in publishing tin GRQ a new dataset=aoi-track
submits sync catch-up jobs for IPF for all acquisitions in that aoi-track.
Assumption: Create AOI of high target areas for the system to keep-up IPFs.
list aoi-track
query GRQ for all dataset type aoi-track
get aoi-track
query GRQ given aoitrack_id
Add Comment