No annotation xml errors with recent SAFE.zip files in topsApp.py #28131
Replies: 1 comment
|
Well, this is stupid, the files that weren't working had a trailing (and unmatched) square bracket in the relevant tag in the xml file. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I am trying to process data from Venezuela and am running into many errors of the same type during the preprocessing steps of topsApp. All of the data files are from the last two weeks, which makes me curious if it is a formatting change (the new IPF version?) or related to the changes in satellite configuration. Data I processed three weeks ago did not seem to have this problem.
I have changed the Sentinel-1.py script to enable the correct orbital calculations for S1C (including the recent maneuvers) and S1D. Similarly, I have updated the eof scripts to download the orbit files for S1D.
The errors are all of this type:
Could not extract swath 1 from ['/staging/venezuela_2026/A106/SLC/S1D_IW_SLC__1SDV_20260618T225011_20260618T225038_003297_005C64_6FC8.zip]']Generated error: No annotation xml file found in /staging/venezuela_2026/A106/SLC/S1D_IW_SLC__1SDV_20260618T225011_20260618T225038_003297_005C64_6FC8.zip]Input XML files: ['/vsizip//staging/venezuela_2026/A106/SLC/S1A_IW_SLC__1SDV_20260611T225051_20260611T225120_064928_082EA4_3D2D.zip/S1A_IW_SLC__1SDV_20260611T225051_20260611T225120_064928_082EA4_3D2D.SAFE/annotation/s1a-iw2-slc-vv-20260611t225052-20260611t225119-064928-082ea4-005.xml']Input TIFF files: ['/vsizip//staging/venezuela_2026/A106/SLC/S1A_IW_SLC__1SDV_20260611T225051_20260611T225120_064928_082EA4_3D2D.zip/S1A_IW_SLC__1SDV_20260611T225051_20260611T225120_064928_082EA4_3D2D.SAFE/measurement/s1a-iw2-slc-vv-20260611t225052-20260611t225119-064928-082ea4-005.tiff']Manifest files: ['/vsizip//staging/venezuela_2026/A106/SLC/S1A_IW_SLC__1SDV_20260611T225051_20260611T225120_064928_082EA4_3D2D.zip/S1A_IW_SLC__1SDV_20260611T225051_20260611T225120_064928_082EA4_3D2D.SAFE/manifest.safe'] MANS: /staging/venezuela_2026/A106/SLC/S1A_IW_SLC__1SDV_20260611T225051_20260611T225120_064928_082EA4_3D2D.zip S1A_IW_SLC__1SDV_20260611T225051_20260611T225120_064928_082EA4_3D2D.SAFE/manifest.safeSetting IPF version to : 004.03Extracting orbit from Orbit File: /staging/venezuela_2026/orbits/S1A_OPER_AUX_RESORB_OPOD_20260612T010311_V20260611T210940_20260612T002710.EOFand they seem to be flagged for the secondary images in particular. I get similar errors for S1C data.
More bizarrely, if I switch the reference and secondary SAFE files in my topsApp.xml file, I can get through the preprocessing step (albeit with divide by zero errors in the baseline calculation) and the processing runs through to topo, but I am not confident that the results are going to be very useful.
Any thoughts on what is going on?
All reactions