Several ESA Geohazards Exploitation Platform (GEP) early adopters applying for the scenario 2 'New EO Service Development' are currently supported for the integration of their data processing chain on the GEP Cloud environment.
The resulting processor integration is then made available from the GEP Portal to users (upon sign-in credentials for https://geohazards-tep.eo.esa.int/). On the Portal, authenticated users can select data over an area of interest, set processing parameters, run a processing job and share their results on the platform.
To support these processor integration activities, we have defined an application template, dedicated to the access and the processing of Sentinel-1 data from the Platform. The template, together with the installation procedure, is available on GitHub at https://github.com/Terradue/dcs-template-insar-sentinel1
Based on this application template, under src/main/app-resources/myapp/run, developers of new Processing applications can now retrieve from the Platform's catalogue the Sentinel-1 products together with the Precise Orbit Ephemerides data (POEORB) or the Restituted Orbits data (RESORB), as handled by the ESA Precise Orbit Determination (POD) solutions.
From a running workflow, a function is typically getting the start/end time of the current Sentinel-1 product to be processed, and an OpenSearch query is then performing the retrieval (using the "enclosure" parameter, that provides with the file download location) of the corresponding PODs. A last step is downloading the orbital data from the enclosure reference, and storing it on the proper file system location, in order to be ingested by the SAR processing code embedded in the new application.
In average, ESA releases the Sentinel-1 POD Precise Orbit Ephemerides 20 days after the related acquisition. If you want to process Sentinel-1 products acquired in near-real time, you can also use the orbital data enclosed within the Sentinel-1 product.
To learn more about Sentinel-1 mission and products: Sentinel-1 User Handbook