The SAR-MPC team has announced that Sentinel-1 IPF Auxiliary Data Files are now also available through a STAC API. This is a small but useful update for users working with Sentinel-1 processing chains, because auxiliary files are often needed to understand, reproduce, or troubleshoot SAR processing workflows.
The main official access point for end users remains the Copernicus Data Space Ecosystem, but SAR-MPC also provides complementary access to the auxiliary data it generates. According to the SAR-MPC documentation, the available IPF Auxiliary Data File types include AUX_INS, AUX_CAL, AUX_PP1, AUX_PP2, AUX_ML2 and AUX_SCS, with access provided through the SAR-MPC website, API and STAC API.
For the GEP community, the interesting point is not only the availability of the files, but the use of STAC as a common discovery interface. Having Sentinel-1 auxiliary data exposed through STAC makes it easier to integrate metadata discovery into notebooks, processing environments, validation workflows, and reproducible EO processing chains.
This may be useful, for example, when checking which auxiliary file applies to a specific Sentinel-1 product, documenting processing inputs, or preparing workflows that need to keep track of the exact processor context used for an analysis.
Useful links:
- SAR-MPC products — Sentinel-1 IPF Auxiliary Files
- SAR-MPC API documentation
- Copernicus Data Space Ecosystem
This is also a good reminder that open EO processing is not only about access to satellite scenes. Reliable access to auxiliary data, metadata, processor versions and processing context is part of what makes EO workflows easier to reproduce, compare and share.
This topic is shared for community awareness and open-science discussion. It is not an official announcement by GEP, ESA, the European Commission, Copernicus Data Space Ecosystem, or SAR-MPC.