"Something went wrong determining bboxes", Sentinel 1 with topsApp.py

Added by Alexander Handwerger over 3 years ago

Hello,

I am having trouble processing several interferograms using topsApp.py. However, I have been able to process several other interferograms with the same path and frame. I see the following flags: “ Could not extract swath 1”, “no suitable orbit file found”, “no Swaths contain burst overlaps”, and finally “Something went wrong determining bboxes”. I have checked the SLC directories for each scene and all of the required data are there. I also have the corresponding orbit files. Any help would be appreciated. Please see attached files for topsApp.py output in the file named topsApp_out.txt.

Thanks,
Alexander

topsApp_out.txt Magnifier (5.9 kB)

topsApp.xml Magnifier (8.8 kB)

slave.xml Magnifier (3.4 kB)

master.xml Magnifier (3.4 kB)


Replies (6)

RE: "Something went wrong determining bboxes", Sentinel 1 with topsApp.py - Added by Piyush Agram over 3 years ago

Check your orbit folder. You are using data thats pretty recent and you probably haven't updated your orbits.

RE: "Something went wrong determining bboxes", Sentinel 1 with topsApp.py - Added by Alexander Handwerger over 3 years ago

Thank you. My script to download the orbits was not including the S1B orbit files. After downloading the S1B orbit files, I am now able to process the interferograms.

Thanks again,

RE: "Something went wrong determining bboxes", Sentinel 1 with topsApp.py - Added by Matt Cook about 1 year ago

Hi Piyush,

I have a similar error when using topsApp.py with sentinel-1 data.

I'm using the following sentinel-1 data:
master = S1A_IW_SLC__1SDV_20190205T172131_20190205T172200_025797_02DE7F_1A55.zip
slave = S1A_IW_SLC__1SDV_20190524T172133_20190524T172203_027372_031660_F602.zip

With the corresponding orbit files:
S1A_OPER_AUX_POEORB_OPOD_20190226T120833_V20190205T225942_20190207T005942.EOF
S1A_OPER_AUX_POEORB_OPOD_20190614T130552_V20190524T225942_20190526T005942.EOF
Do these seem correct?

Aux files:
I have downloaded all of the currently active aux files and are all kept in one directory (see attached). I think this may be where I am going wrong. Should I directly link the correct aux file in the path?

Once I run topsApp.py topsApp.xml I get the following error:

The currently supported sensors are: ['SENTINEL1']
Input XML files: ['/vsizip//data/anaconda3/envs/ISCE/lib/python3.7/site-packages/isce/Sentinel1/S1A_IW_SLC__1SDV_20190205T172131_20190205T172200_025797_02DE7F_1A55.zip/S1A_IW_SLC__1SDV_20190205T172131_20190205T172200_025797_02DE7F_1A55.SAFE/annotation/s1a-iw1-slc-vv-20190205t172131-20190205t172159-025797-02de7f-004.xml']
Input TIFF files: ['/vsizip//data/anaconda3/envs/ISCE/lib/python3.7/site-packages/isce/Sentinel1/S1A_IW_SLC__1SDV_20190205T172131_20190205T172200_025797_02DE7F_1A55.zip/S1A_IW_SLC__1SDV_20190205T172131_20190205T172200_025797_02DE7F_1A55.SAFE/measurement/s1a-iw1-slc-vv-20190205t172131-20190205t172159-025797-02de7f-004.tiff']
Manifest files: ['/vsizip//data/anaconda3/envs/ISCE/lib/python3.7/site-packages/isce/Sentinel1/S1A_IW_SLC__1SDV_20190205T172131_20190205T172200_025797_02DE7F_1A55.zip/S1A_IW_SLC__1SDV_20190205T172131_20190205T172200_025797_02DE7F_1A55.SAFE/manifest.safe']
MANS: /data/anaconda3/envs/ISCE/lib/python3.7/site-packages/isce/Sentinel1/S1A_IW_SLC__1SDV_20190205T172131_20190205T172200_025797_02DE7F_1A55.zip S1A_IW_SLC__1SDV_20190205T172131_20190205T172200_025797_02DE7F_1A55.SAFE/manifest.safe
Setting IPF version to : 002.91
Could not extract swath 1 from ['/data/anaconda3/envs/ISCE/lib/python3.7/site-packages/isce/Sentinel1/S1A_IW_SLC__1SDV_20190205T172131_20190205T172200_025797_02DE7F_1A55.zip']
Generated error: No suitable orbit file found. If you want to process anyway - unset the orbitdir parameter

And then at the end I get 'Something went wrong in determining bboxes'.

I've tried a few things you have mentioned in other forums on here like http://earthdef.caltech.edu/boards/4/topics/918?r=1251#message-1251 but nothing has worked yet. Is there anything obvious you can see I'm doing wrong?

Hope this made sense. Thanks for your time.

Matt

topsApp.xml Magnifier (251 Bytes)

master.xml Magnifier (641 Bytes)

slave.xml Magnifier (639 Bytes)

Aux files.PNG (70.1 kB)

RE: "Something went wrong determining bboxes", Sentinel 1 with topsApp.py - Added by Piyush Agram about 1 year ago

Your orbit files dont span your images. Use the correct orbit files. See time tags of coverage for product and orbit files.

RE: "Something went wrong determining bboxes", Sentinel 1 with topsApp.py - Added by Matt Cook about 1 year ago

Ahh yes I wasn't paying attention to the time.

Thank you Piyush.

RE: "Something went wrong determining bboxes", Sentinel 1 with topsApp.py - Added by Lennart Kramer 5 months ago

I have a similar Error. When I run --dostep=verifyDEM in topsApp.py I get `Exception: Something went wrong in determining bboxes`: My sentinel-1 Data is directly from 2014 and the folder names are:

- S1A_IW_SLC__1SSV_20141103T195043_20141103T195057_003122_00395A_F396.zip
- S1A_IW_SLC__1SSV_20141127T195042_20141127T195056_003472_004117_2B48.zip

I then Downloaded two precise orbit files:

- S1A_OPER_AUX_POEORB_OPOD_20141123T123513_V20141101T225944_20141103T005944.EOF
- S1A_OPER_AUX_POEORB_OPOD_20141217T123843_V20141125T225944_20141127T005944.EOF

But I need to confess that I don't know exactly how to read the naming convention and to determine if my products are covered. Moreover, I couldn't find any "Aux_cal" information for that date on https://qc.sentinel1.eo.esa.int/aux_cal/. Is this a problem or can I continue?

Sorry for the naive question. Any help is highly appreciated:)
`

(1-6/6)