sar-ard / s1ard Goto Github PK
View Code? Open in Web Editor NEWSentinel-1 ARD Prototype Processor
License: MIT License
s1ard's People
Contributors
Stargazers
Watchers
Forkers
keyao22 natangirma avalentino jena-earth-observation-school opendatacubepipelines abradley60s1ard's Issues
STAC Item-Assets: Differentiate between Noise Power assets in asset title
I have put some data processed recently by @johntruckenbrodt into our STAC catalogue. I observed that there are two assets with the same title "Noise Power". When visualizing the items in the STAC Browser, a user cannot identify the difference between both assets, see following screenshot.
I guess this happens according to the following code:
https://github.com/SAR-ARD/S1_NRB/blob/1bf2e6e9560bdef5daf459c585a8f4f7c112a7c5/S1_NRB/metadata/mapping.py#L145-L148
cannot find OCN products with different acquisition time than Level-1 product
The Level-2 OCN products may have different acquisition start and stop times than the corresponding Level-1 product. Currently the OCN scene search does not consider this.
S1B_EW_GRDM_1SDH_20211027T183137_20211027T183242_029325_038002_64DE.zip S1B_EW_OCN__2SDH_20211027T183138_20211027T183242_029325_038002_12D2.zip
SLC edge cleaning applicable to GRD?
The SNAP processing workflow performs a S1_NRB.snap.postprocess step, in which the edges of an SLC are eroded to remove border noise effects. It needs to be revised whether the number of four pixels defined for erosion is applicable to GRD as well. GRD border noise removal is performed, however this step is known to give different results depending on the Sentinel-1 IPF version. Furthermore, border noise pixels have been observed for different products which might be caused by incorporation of nodata areas (value 0) into image resampling.
original source metadata in nested subdirectory
#104 recently introduced the copying of original source metadata into the NRB/ORB product.
The second scene's metadata folder is incorrectly saved into that of the first scene:
Define MGRS tiles for polar regions
Currently the processor makes use of a KML file provided for the Sentinel-2 mission to get the characteristics for individual MGRS tiles. This file does not define areas at the poles:
 |
 |
The MGRS itself grid does define tiles in these areas. An alternative to the KML file has to be found to enable processing of scenes in these regions.
SNAP 9 incompatibility - Error: [NodeId: BandSelect] Operator 'BandSelectOp': Value for 'Source Bands' is invalid: 'NESZ_VV'
Hello again,
so the process proceeded at least on one machine. But I do not find the final product and I also had some errors (see below).
The final products are actually stored in the work/NRB/32***/ directory, right?
commandline outputs:
(nrb_env) ***@***:~/data_storage/florian/S1_NRB$ s1_nrb -c config.ini
checking for missing scenes
Removing missing scene from database tables: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1A_IW_SLC__1SDV_20200601T050821_20200601T050849_032819_03CD2E_5AF0.SAFE
Entry with scene-id:
/codede/Sentinel-1/SAR/SLC/2020/06/01/S1A_IW_SLC__1SDV_20200601T050821_20200601T050849_032819_03CD2E_5AF0.SAFE
was dropped from data and duplicates!
Removing missing scene from database tables: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1A_IW_SLC__1SDV_20200601T050846_20200601T050913_032819_03CD2E_7CC4.SAFE
Entry with scene-id:
/codede/Sentinel-1/SAR/SLC/2020/06/01/S1A_IW_SLC__1SDV_20200601T050846_20200601T050913_032819_03CD2E_7CC4.SAFE
was dropped from data and duplicates!
Removing missing scene from database tables: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1A_IW_SLC__1SDV_20200601T050911_20200601T050938_032819_03CD2E_A088.SAFE
Entry with scene-id:
/codede/Sentinel-1/SAR/SLC/2020/06/01/S1A_IW_SLC__1SDV_20200601T050911_20200601T050938_032819_03CD2E_A088.SAFE
was dropped from data and duplicates!
Removing missing scene from database tables: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1A_IW_SLC__1SDV_20200601T050936_20200601T051003_032819_03CD2E_6C7D.SAFE
Entry with scene-id:
/codede/Sentinel-1/SAR/SLC/2020/06/01/S1A_IW_SLC__1SDV_20200601T050936_20200601T051003_032819_03CD2E_6C7D.SAFE
was dropped from data and duplicates!
Removing missing scene from database tables: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1A_IW_SLC__1SDV_20200601T051001_20200601T051029_032819_03CD2E_4860.SAFE
Entry with scene-id:
/codede/Sentinel-1/SAR/SLC/2020/06/01/S1A_IW_SLC__1SDV_20200601T051001_20200601T051029_032819_03CD2E_4860.SAFE
was dropped from data and duplicates!
Removing missing scene from database tables: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1A_IW_SLC__1SDV_20200601T051027_20200601T051054_032819_03CD2E_E141.SAFE
Entry with scene-id:
/codede/Sentinel-1/SAR/SLC/2020/06/01/S1A_IW_SLC__1SDV_20200601T051027_20200601T051054_032819_03CD2E_E141.SAFE
was dropped from data and duplicates!
Removing missing scene from database tables: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1A_IW_SLC__1SDV_20200601T051051_20200601T051118_032819_03CD2E_AC11.SAFE
Entry with scene-id:
/codede/Sentinel-1/SAR/SLC/2020/06/01/S1A_IW_SLC__1SDV_20200601T051051_20200601T051118_032819_03CD2E_AC11.SAFE
was dropped from data and duplicates!
Removing missing scene from database tables: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T055640_20200601T055707_021836_029727_04AA.SAFE
Entry with scene-id:
/codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T055640_20200601T055707_021836_029727_04AA.SAFE
was dropped from data and duplicates!
Removing missing scene from database tables: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T055705_20200601T055733_021836_029727_306F.SAFE
Entry with scene-id:
/codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T055705_20200601T055733_021836_029727_306F.SAFE
was dropped from data and duplicates!
Removing missing scene from database tables: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T055731_20200601T055758_021836_029727_90CE.SAFE
Entry with scene-id:
/codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T055731_20200601T055758_021836_029727_90CE.SAFE
was dropped from data and duplicates!
Removing missing scene from database tables: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T055755_20200601T055823_021836_029727_98AC.SAFE
Entry with scene-id:
/codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T055755_20200601T055823_021836_029727_98AC.SAFE
was dropped from data and duplicates!
Removing missing scene from database tables: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T055820_20200601T055847_021836_029727_43A7.SAFE
Entry with scene-id:
/codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T055820_20200601T055847_021836_029727_43A7.SAFE
was dropped from data and duplicates!
Removing missing scene from database tables: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170619_20200601T170646_021843_029753_5123.SAFE
Entry with scene-id:
/codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170619_20200601T170646_021843_029753_5123.SAFE
was dropped from data and duplicates!
Removing missing scene from database tables: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170644_20200601T170711_021843_029753_5D9C.SAFE
Entry with scene-id:
/codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170644_20200601T170711_021843_029753_5D9C.SAFE
was dropped from data and duplicates!
Removing missing scene from database tables: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170709_20200601T170737_021843_029753_7199.SAFE
Entry with scene-id:
/codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170709_20200601T170737_021843_029753_7199.SAFE
was dropped from data and duplicates!
Removing missing scene from database tables: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170735_20200601T170801_021843_029753_DFD0.SAFE
Entry with scene-id:
/codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170735_20200601T170801_021843_029753_DFD0.SAFE
was dropped from data and duplicates!
Removing missing scene from database tables: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170759_20200601T170826_021843_029753_76B0.SAFE
Entry with scene-id:
/codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170759_20200601T170826_021843_029753_76B0.SAFE
was dropped from data and duplicates!
Removing missing scene from database tables: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170824_20200601T170851_021843_029753_C512.SAFE
Entry with scene-id:
/codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170824_20200601T170851_021843_029753_C512.SAFE
was dropped from data and duplicates!
Removing missing scene from database tables: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170849_20200601T170916_021843_029753_CABF.SAFE
Entry with scene-id:
/codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170849_20200601T170916_021843_029753_CABF.SAFE
was dropped from data and duplicates!
filtering scenes by name
identifying scenes and extracting metadata
inserting 19 scenes into database
19 scenes registered regularly
0 duplicates registered
###### [ DEM] processing geometry 1 of 2
### downloading DEM tiles
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N46_00_E014_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N46_00_E014_00_DEM/Copernicus_DSM_COG_10_N46_00_E014_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N49_00_E010_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N49_00_E010_00_DEM/Copernicus_DSM_COG_10_N49_00_E010_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N46_00_E011_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N46_00_E011_00_DEM/Copernicus_DSM_COG_10_N46_00_E011_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N46_00_E013_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N46_00_E013_00_DEM/Copernicus_DSM_COG_10_N46_00_E013_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N47_00_E011_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N47_00_E011_00_DEM/Copernicus_DSM_COG_10_N47_00_E011_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N46_00_E007_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N46_00_E007_00_DEM/Copernicus_DSM_COG_10_N46_00_E007_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N47_00_E014_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N47_00_E014_00_DEM/Copernicus_DSM_COG_10_N47_00_E014_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N47_00_E013_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N47_00_E013_00_DEM/Copernicus_DSM_COG_10_N47_00_E013_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N48_00_E008_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N48_00_E008_00_DEM/Copernicus_DSM_COG_10_N48_00_E008_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N50_00_E009_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N50_00_E009_00_DEM/Copernicus_DSM_COG_10_N50_00_E009_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N48_00_E013_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N48_00_E013_00_DEM/Copernicus_DSM_COG_10_N48_00_E013_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N51_00_E011_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N51_00_E011_00_DEM/Copernicus_DSM_COG_10_N51_00_E011_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N46_00_E010_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N46_00_E010_00_DEM/Copernicus_DSM_COG_10_N46_00_E010_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N48_00_E007_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N48_00_E007_00_DEM/Copernicus_DSM_COG_10_N48_00_E007_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N47_00_E010_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N47_00_E010_00_DEM/Copernicus_DSM_COG_10_N47_00_E010_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N46_00_E009_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N46_00_E009_00_DEM/Copernicus_DSM_COG_10_N46_00_E009_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N47_00_E008_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N47_00_E008_00_DEM/Copernicus_DSM_COG_10_N47_00_E008_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N47_00_E012_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N47_00_E012_00_DEM/Copernicus_DSM_COG_10_N47_00_E012_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N49_00_E007_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N49_00_E007_00_DEM/Copernicus_DSM_COG_10_N49_00_E007_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N46_00_E012_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N46_00_E012_00_DEM/Copernicus_DSM_COG_10_N46_00_E012_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N50_00_E007_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N50_00_E007_00_DEM/Copernicus_DSM_COG_10_N50_00_E007_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N50_00_E014_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N50_00_E014_00_DEM/Copernicus_DSM_COG_10_N50_00_E014_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N48_00_E009_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N48_00_E009_00_DEM/Copernicus_DSM_COG_10_N48_00_E009_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N51_00_E009_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N51_00_E009_00_DEM/Copernicus_DSM_COG_10_N51_00_E009_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N51_00_E010_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N51_00_E010_00_DEM/Copernicus_DSM_COG_10_N51_00_E010_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N48_00_E011_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N48_00_E011_00_DEM/Copernicus_DSM_COG_10_N48_00_E011_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N49_00_E012_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N49_00_E012_00_DEM/Copernicus_DSM_COG_10_N49_00_E012_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N51_00_E012_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N51_00_E012_00_DEM/Copernicus_DSM_COG_10_N51_00_E012_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N50_00_E012_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N50_00_E012_00_DEM/Copernicus_DSM_COG_10_N50_00_E012_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N51_00_E014_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N51_00_E014_00_DEM/Copernicus_DSM_COG_10_N51_00_E014_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N48_00_E012_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N48_00_E012_00_DEM/Copernicus_DSM_COG_10_N48_00_E012_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N51_00_E007_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N51_00_E007_00_DEM/Copernicus_DSM_COG_10_N51_00_E007_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N49_00_E014_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N49_00_E014_00_DEM/Copernicus_DSM_COG_10_N49_00_E014_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N47_00_E009_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N47_00_E009_00_DEM/Copernicus_DSM_COG_10_N47_00_E009_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N49_00_E013_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N49_00_E013_00_DEM/Copernicus_DSM_COG_10_N49_00_E013_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N50_00_E010_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N50_00_E010_00_DEM/Copernicus_DSM_COG_10_N50_00_E010_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N51_00_E008_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N51_00_E008_00_DEM/Copernicus_DSM_COG_10_N51_00_E008_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N49_00_E011_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N49_00_E011_00_DEM/Copernicus_DSM_COG_10_N49_00_E011_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N50_00_E013_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N50_00_E013_00_DEM/Copernicus_DSM_COG_10_N50_00_E013_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N49_00_E009_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N49_00_E009_00_DEM/Copernicus_DSM_COG_10_N49_00_E009_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N51_00_E013_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N51_00_E013_00_DEM/Copernicus_DSM_COG_10_N51_00_E013_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N48_00_E014_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N48_00_E014_00_DEM/Copernicus_DSM_COG_10_N48_00_E014_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N47_00_E007_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N47_00_E007_00_DEM/Copernicus_DSM_COG_10_N47_00_E007_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N49_00_E008_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N49_00_E008_00_DEM/Copernicus_DSM_COG_10_N49_00_E008_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N50_00_E008_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N50_00_E008_00_DEM/Copernicus_DSM_COG_10_N50_00_E008_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N46_00_E008_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N46_00_E008_00_DEM/Copernicus_DSM_COG_10_N46_00_E008_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N50_00_E011_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N50_00_E011_00_DEM/Copernicus_DSM_COG_10_N50_00_E011_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N48_00_E010_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N48_00_E010_00_DEM/Copernicus_DSM_COG_10_N48_00_E010_00_DEM.tif
### creating DEM MGRS tiles:
['32UMA', '32UMU', '32UMV', '32UNA', '32UNU', '32UNV', '32UPA', '32UPU', '32UPV', '32UQA', '32UQU', '32UQV', '33UUP_32632', '33UUQ_32632', '33UUR_32632']
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UMA_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:07 Time: 0:00:07
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UMU_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:07 Time: 0:00:07
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UMV_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:08 Time: 0:00:08
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UNA_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:06 Time: 0:00:06
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UNU_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:07 Time: 0:00:07
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UNV_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:05 Time: 0:00:05
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UPA_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:05 Time: 0:00:05
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UPU_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:07 Time: 0:00:07
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UPV_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:07 Time: 0:00:07
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UQA_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:07 Time: 0:00:07
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UQU_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:07 Time: 0:00:07
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UQV_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:07 Time: 0:00:07
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/33UUP_32632_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:09 Time: 0:00:09
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/33UUQ_32632_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:08 Time: 0:00:08
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/33UUR_32632_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:08 Time: 0:00:08
========================================
###### [ DEM] processing geometry 2 of 2
### downloading DEM tiles
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N49_00_E006_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N49_00_E006_00_DEM/Copernicus_DSM_COG_10_N49_00_E006_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N52_00_E012_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N52_00_E012_00_DEM/Copernicus_DSM_COG_10_N52_00_E012_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N52_00_E008_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N52_00_E008_00_DEM/Copernicus_DSM_COG_10_N52_00_E008_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N53_00_E007_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N53_00_E007_00_DEM/Copernicus_DSM_COG_10_N53_00_E007_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N52_00_E006_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N52_00_E006_00_DEM/Copernicus_DSM_COG_10_N52_00_E006_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N53_00_E009_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N53_00_E009_00_DEM/Copernicus_DSM_COG_10_N53_00_E009_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N52_00_E011_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N52_00_E011_00_DEM/Copernicus_DSM_COG_10_N52_00_E011_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N50_00_E006_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N50_00_E006_00_DEM/Copernicus_DSM_COG_10_N50_00_E006_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N53_00_E013_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N53_00_E013_00_DEM/Copernicus_DSM_COG_10_N53_00_E013_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N53_00_E011_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N53_00_E011_00_DEM/Copernicus_DSM_COG_10_N53_00_E011_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N52_00_E009_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N52_00_E009_00_DEM/Copernicus_DSM_COG_10_N52_00_E009_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N53_00_E010_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N53_00_E010_00_DEM/Copernicus_DSM_COG_10_N53_00_E010_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N51_00_E006_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N51_00_E006_00_DEM/Copernicus_DSM_COG_10_N51_00_E006_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N53_00_E012_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N53_00_E012_00_DEM/Copernicus_DSM_COG_10_N53_00_E012_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N53_00_E006_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N53_00_E006_00_DEM/Copernicus_DSM_COG_10_N53_00_E006_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N52_00_E010_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N52_00_E010_00_DEM/Copernicus_DSM_COG_10_N52_00_E010_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N52_00_E007_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N52_00_E007_00_DEM/Copernicus_DSM_COG_10_N52_00_E007_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N53_00_E008_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N53_00_E008_00_DEM/Copernicus_DSM_COG_10_N53_00_E008_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N52_00_E013_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N52_00_E013_00_DEM/Copernicus_DSM_COG_10_N52_00_E013_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N48_00_E006_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N48_00_E006_00_DEM/Copernicus_DSM_COG_10_N48_00_E006_00_DEM.tif
### creating DEM MGRS tiles:
['32UMB', '32UMC', '32UNB', '32UNC', '32UPB', '32UPC', '32UQB', '32UQC', '33UUS_32632', '33UUT_32632']
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UMB_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:07 Time: 0:00:07
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UMC_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:07 Time: 0:00:07
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UNB_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:07 Time: 0:00:07
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UNC_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:06 Time: 0:00:06
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UPB_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:07 Time: 0:00:07
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UPC_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:07 Time: 0:00:07
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UQB_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:07 Time: 0:00:07
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/32UQC_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:06 Time: 0:00:06
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/33UUS_32632_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:08 Time: 0:00:08
creating mosaic and reprojecting to EPSG:32632: /media/data_storage/florian/S1_NRB/work/DEM/Copernicus 30m Global DEM/33UUT_32632_DEM.tif
100%|####################################################################################################################################################################################################################################################################|Elapsed Time: 0:00:09 Time: 0:00:09
========================================
### creating scene-specific DEM mosaic: /media/data_storage/florian/S1_NRB/work/TMP/S1B_IW_SLC__1SDV_20200601T170709_20200601T170737_021843_029753_7199/32632/S1B__IW___A_20200601T170709_DEM_32632.tif
###### [GEOCODE] Scene 1/2: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170709_20200601T170737_021843_029753_7199.SAFE
searching for new POE files
https://scihub.copernicus.eu/gnss/search?q=producttype:AUX_POEORB platformname:Sentinel-1 filename:S1B* beginPosition:[2020-05-31T17:07:09Z TO 2020-06-02T17:07:09Z] endPosition:[2020-05-31T17:07:09Z TO 2020-06-02T17:07:09Z]&format=json
found 1 results
downloading 1 file
deleting 0 RES files
executing node sequences..
Calibration -> ThermalNoiseRemoval
TOPSAR-Deburst
Apply-Orbit-File
Multilook -> BandSelect
Terrain-Flattening
BandMaths
BandMerge
BandMaths
BandMerge
Terrain-Correction
cleaning image edges and converting to GeoTIFF
deleting temporary files
done
###### [NOISE_P] Scene 1/2: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170709_20200601T170737_021843_029753_7199.SAFE
executing node sequences..
Apply-Orbit-File
Calibration -> ThermalNoiseRemoval
TOPSAR-Deburst -> BandSelect
failed: /media/data_storage/florian/S1_NRB/work/RTC/S1B_IW_SLC__1SDV_20200601T170709_20200601T170737_021843_029753_7199/32632/S1B__IW___A_20200601T170709_Orb_Cal_NR_Deb_ML_TC_proc.xml
### creating scene-specific DEM mosaic: /media/data_storage/florian/S1_NRB/work/TMP/S1B_IW_SLC__1SDV_20200601T170735_20200601T170801_021843_029753_DFD0/32632/S1B__IW___A_20200601T170735_DEM_32632.tif
###### [GEOCODE] Scene 2/2: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170735_20200601T170801_021843_029753_DFD0.SAFE
executing node sequences..
Calibration -> ThermalNoiseRemoval
TOPSAR-Deburst
Apply-Orbit-File
Multilook -> BandSelect
Terrain-Flattening
BandMaths
BandMerge
BandMaths
BandMerge
Terrain-Correction
cleaning image edges and converting to GeoTIFF
deleting temporary files
done
###### [NOISE_P] Scene 2/2: /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170735_20200601T170801_021843_029753_DFD0.SAFE
executing node sequences..
Apply-Orbit-File
Calibration -> ThermalNoiseRemoval
TOPSAR-Deburst -> BandSelect
failed: /media/data_storage/florian/S1_NRB/work/RTC/S1B_IW_SLC__1SDV_20200601T170735_20200601T170801_021843_029753_DFD0/32632/S1B__IW___A_20200601T170735_Orb_Cal_NR_Deb_ML_TC_proc.xml
###### [ NRB] Tile 1/1: 32UNA | Scenes 1/1: ['S1B_IW_SLC__1SDV_20200601T170709_20200601T170737_021843_029753_7199.SAFE', 'S1B_IW_SLC__1SDV_20200601T170735_20200601T170801_021843_029753_DFD0.SAFE']
creating raster mask 0
creating vector mask 0
creating raster mask 1
creating vector mask 1
/media/data_storage/florian/S1_NRB/work/NRB/32UNA/S1B_IW_NRB__1SDV_20200601T170726_021843_029753_32UNA_18DC/measurement/s1b-iw-nrb-20200601t170726-021843-029753-32una-vh-g-lin.tifLOG file:
(nrb_env) ***@***:~/data_storage/florian/S1_NRB$ cat work/LOG/20220707T1413_process.log
====================================================================================================================
PROCESSING CONFIGURATION
mode = all
aoi_tiles = ['32UNA']
aoi_geometry = None
mindate = 2020-05-31T00:00:00
maxdate = 2020-06-02T00:00:00
acq_mode = IW
work_dir = /media/data_storage/florian/S1_NRB/work
scene_dir = /codede/Sentinel-1/SAR/SLC/2020/06/01
rtc_dir = /media/data_storage/florian/S1_NRB/work/RTC
tmp_dir = /media/data_storage/florian/S1_NRB/work/TMP
nrb_dir = /media/data_storage/florian/S1_NRB/work/NRB
dem_dir = /media/data_storage/florian/S1_NRB/work/DEM
wbm_dir = /media/data_storage/florian/S1_NRB/work/WBM
log_dir = /media/data_storage/florian/S1_NRB/work/LOG
db_file = /media/data_storage/florian/S1_NRB/scenes.db
kml_file = /media/data_storage/florian/S1_NRB/S2A_OPER_GIP_TILPAR_MPC__20151209T095117_V20150622T000000_21000101T000000_B00.kml
dem_type = Copernicus 30m Global DEM
====================================================================================================================
SOFTWARE
S1_NRB: 1.0.1
snap-core: 9.0.0 | 202206281505
snap-s1tbx: 9.0.0 | 202206281601
python: 3.10.5 | packaged by conda-forge | (main, Jun 14 2022, 07:04:59) [GCC 10.3.0]
python-pyroSAR: 0.17.3
python-spatialist: 0.11.0
python-GDAL: 3.5.1
gdal_threads = 20
====================================================================================================================
[2022-07-07 14:51:17,060] [ INFO] [GEOCODE] -- /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170709_20200601T170737_021843_029753_7199.SAFE [32632] -- 1824.66
[2022-07-07 14:53:55,937] [ ERROR] [NOISE_P] -- /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170709_20200601T170737_021843_029753_7199.SAFE [32632] -- Executing processing graph
done.
INFO: org.esa.snap.core.gpf.operators.tooladapter.ToolAdapterIO: Initializing external tool adapters
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: Incompatible GDAL 3.5.1 found on system. Internal GDAL 3.2.1 from distribution will be used.
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: Internal GDAL 3.2.1 set to be used by SNAP.
INFO: org.esa.snap.core.util.EngineVersionCheckActivator: Please check regularly for new updates for the best SNAP experience.
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: Internal GDAL 3.2.1 set to be used by SNAP.
INFO: org.hsqldb.persist.Logger: dataFileCache open start
org.esa.snap.core.gpf.graph.GraphException: [NodeId: BandSelect] Operator 'BandSelectOp': Value for 'Source Bands' is invalid: 'NESZ_VV'
at org.esa.snap.core.gpf.graph.NodeContext.initTargetProduct(NodeContext.java:79)
at org.esa.snap.core.gpf.graph.GraphContext.initNodeContext(GraphContext.java:199)
at org.esa.snap.core.gpf.graph.GraphContext.initNodeContext(GraphContext.java:182)
at org.esa.snap.core.gpf.graph.GraphContext.initOutput(GraphContext.java:166)
at org.esa.snap.core.gpf.graph.GraphContext.<init>(GraphContext.java:85)
at org.esa.snap.core.gpf.graph.GraphContext.<init>(GraphContext.java:58)
at org.esa.snap.core.gpf.graph.GraphProcessor.executeGraph(GraphProcessor.java:127)
at org.esa.snap.core.gpf.main.DefaultCommandLineContext.executeGraph(DefaultCommandLineContext.java:86)
at org.esa.snap.core.gpf.main.CommandLineTool.executeGraph(CommandLineTool.java:547)
at org.esa.snap.core.gpf.main.CommandLineTool.runGraph(CommandLineTool.java:391)
at org.esa.snap.core.gpf.main.CommandLineTool.runGraphOrOperator(CommandLineTool.java:287)
at org.esa.snap.core.gpf.main.CommandLineTool.run(CommandLineTool.java:188)
at org.esa.snap.core.gpf.main.CommandLineTool.run(CommandLineTool.java:121)
at org.esa.snap.core.gpf.main.GPT.run(GPT.java:59)
at org.esa.snap.core.gpf.main.GPT.main(GPT.java:37)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.esa.snap.runtime.Launcher.lambda$run$0(Launcher.java:55)
at org.esa.snap.runtime.Engine.runClientCode(Engine.java:189)
at org.esa.snap.runtime.Launcher.run(Launcher.java:51)
at org.esa.snap.runtime.Launcher.main(Launcher.java:31)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:84)
at com.install4j.runtime.launcher.UnixLauncher.start(UnixLauncher.java:66)
at install4j.org.esa.snap.runtime.Launcher_gpt.main(Unknown Source)
Caused by: org.esa.snap.core.gpf.OperatorException: Operator 'BandSelectOp': Value for 'Source Bands' is invalid: 'NESZ_VV'
at org.esa.snap.core.gpf.internal.OperatorContext.injectConfiguration(OperatorContext.java:1149)
at org.esa.snap.core.gpf.internal.OperatorContext.initializeOperator(OperatorContext.java:526)
at org.esa.snap.core.gpf.internal.OperatorContext.getTargetProduct(OperatorContext.java:298)
at org.esa.snap.core.gpf.Operator.getTargetProduct(Operator.java:385)
at org.esa.snap.core.gpf.graph.NodeContext.initTargetProduct(NodeContext.java:77)
... 29 more
Caused by: com.bc.ceres.binding.ValidationException: Value for 'Source Bands' is invalid: 'NESZ_VV'
at com.bc.ceres.binding.validators.ValueSetValidator.validateValue(ValueSetValidator.java:37)
at com.bc.ceres.binding.validators.ArrayValidator.validateValue(ArrayValidator.java:37)
at com.bc.ceres.binding.validators.MultiValidator.validateValue(MultiValidator.java:52)
at com.bc.ceres.binding.Property.validate(Property.java:270)
at com.bc.ceres.binding.Property.setValue(Property.java:172)
at com.bc.ceres.binding.dom.DefaultDomConverter.convertDomChildToProperty(DefaultDomConverter.java:194)
at com.bc.ceres.binding.dom.DefaultDomConverter.convertDomChildToPropertySet(DefaultDomConverter.java:182)
at com.bc.ceres.binding.dom.DefaultDomConverter.convertDomToPropertySet(DefaultDomConverter.java:165)
at com.bc.ceres.binding.dom.DefaultDomConverter.convertDomToValue(DefaultDomConverter.java:158)
at org.esa.snap.core.gpf.internal.OperatorContext.configureOperator(OperatorContext.java:1165)
at org.esa.snap.core.gpf.internal.OperatorContext.injectConfiguration(OperatorContext.java:1145)
... 33 more
Error: [NodeId: BandSelect] Operator 'BandSelectOp': Value for 'Source Bands' is invalid: 'NESZ_VV'
[S1B_IW_SLC__1SDV_20200601T170709_20200601T170737_021843_029753_7199_tmp2.xml] failed with return code 1
Traceback (most recent call last):
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/processor.py", line 180, in main
noise_power(infile=scene.scene, outdir=out_dir_scene_epsg, polarizations=scene.polarizations,
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/pyroSAR/snap/util.py", line 1011, in noise_power
gpt(xmlfile=wf_name, tmpdir=procdir, groups=groups, cleanup=cleanup)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/pyroSAR/snap/auxil.py", line 399, in gpt
execute(sub, cleanup=cleanup, gpt_exceptions=gpt_exceptions, gpt_args=gpt_args)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/pyroSAR/snap/auxil.py", line 290, in execute
raise RuntimeError(submessage.format(out, err, os.path.basename(xmlfile), proc.returncode))
RuntimeError: Executing processing graph
done.
INFO: org.esa.snap.core.gpf.operators.tooladapter.ToolAdapterIO: Initializing external tool adapters
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: Incompatible GDAL 3.5.1 found on system. Internal GDAL 3.2.1 from distribution will be used.
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: Internal GDAL 3.2.1 set to be used by SNAP.
INFO: org.esa.snap.core.util.EngineVersionCheckActivator: Please check regularly for new updates for the best SNAP experience.
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: Internal GDAL 3.2.1 set to be used by SNAP.
INFO: org.hsqldb.persist.Logger: dataFileCache open start
org.esa.snap.core.gpf.graph.GraphException: [NodeId: BandSelect] Operator 'BandSelectOp': Value for 'Source Bands' is invalid: 'NESZ_VV'
at org.esa.snap.core.gpf.graph.NodeContext.initTargetProduct(NodeContext.java:79)
at org.esa.snap.core.gpf.graph.GraphContext.initNodeContext(GraphContext.java:199)
at org.esa.snap.core.gpf.graph.GraphContext.initNodeContext(GraphContext.java:182)
at org.esa.snap.core.gpf.graph.GraphContext.initOutput(GraphContext.java:166)
at org.esa.snap.core.gpf.graph.GraphContext.<init>(GraphContext.java:85)
at org.esa.snap.core.gpf.graph.GraphContext.<init>(GraphContext.java:58)
at org.esa.snap.core.gpf.graph.GraphProcessor.executeGraph(GraphProcessor.java:127)
at org.esa.snap.core.gpf.main.DefaultCommandLineContext.executeGraph(DefaultCommandLineContext.java:86)
at org.esa.snap.core.gpf.main.CommandLineTool.executeGraph(CommandLineTool.java:547)
at org.esa.snap.core.gpf.main.CommandLineTool.runGraph(CommandLineTool.java:391)
at org.esa.snap.core.gpf.main.CommandLineTool.runGraphOrOperator(CommandLineTool.java:287)
at org.esa.snap.core.gpf.main.CommandLineTool.run(CommandLineTool.java:188)
at org.esa.snap.core.gpf.main.CommandLineTool.run(CommandLineTool.java:121)
at org.esa.snap.core.gpf.main.GPT.run(GPT.java:59)
at org.esa.snap.core.gpf.main.GPT.main(GPT.java:37)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.esa.snap.runtime.Launcher.lambda$run$0(Launcher.java:55)
at org.esa.snap.runtime.Engine.runClientCode(Engine.java:189)
at org.esa.snap.runtime.Launcher.run(Launcher.java:51)
at org.esa.snap.runtime.Launcher.main(Launcher.java:31)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:84)
at com.install4j.runtime.launcher.UnixLauncher.start(UnixLauncher.java:66)
at install4j.org.esa.snap.runtime.Launcher_gpt.main(Unknown Source)
Caused by: org.esa.snap.core.gpf.OperatorException: Operator 'BandSelectOp': Value for 'Source Bands' is invalid: 'NESZ_VV'
at org.esa.snap.core.gpf.internal.OperatorContext.injectConfiguration(OperatorContext.java:1149)
at org.esa.snap.core.gpf.internal.OperatorContext.initializeOperator(OperatorContext.java:526)
at org.esa.snap.core.gpf.internal.OperatorContext.getTargetProduct(OperatorContext.java:298)
at org.esa.snap.core.gpf.Operator.getTargetProduct(Operator.java:385)
at org.esa.snap.core.gpf.graph.NodeContext.initTargetProduct(NodeContext.java:77)
... 29 more
Caused by: com.bc.ceres.binding.ValidationException: Value for 'Source Bands' is invalid: 'NESZ_VV'
at com.bc.ceres.binding.validators.ValueSetValidator.validateValue(ValueSetValidator.java:37)
at com.bc.ceres.binding.validators.ArrayValidator.validateValue(ArrayValidator.java:37)
at com.bc.ceres.binding.validators.MultiValidator.validateValue(MultiValidator.java:52)
at com.bc.ceres.binding.Property.validate(Property.java:270)
at com.bc.ceres.binding.Property.setValue(Property.java:172)
at com.bc.ceres.binding.dom.DefaultDomConverter.convertDomChildToProperty(DefaultDomConverter.java:194)
at com.bc.ceres.binding.dom.DefaultDomConverter.convertDomChildToPropertySet(DefaultDomConverter.java:182)
at com.bc.ceres.binding.dom.DefaultDomConverter.convertDomToPropertySet(DefaultDomConverter.java:165)
at com.bc.ceres.binding.dom.DefaultDomConverter.convertDomToValue(DefaultDomConverter.java:158)
at org.esa.snap.core.gpf.internal.OperatorContext.configureOperator(OperatorContext.java:1165)
at org.esa.snap.core.gpf.internal.OperatorContext.injectConfiguration(OperatorContext.java:1145)
... 33 more
Error: [NodeId: BandSelect] Operator 'BandSelectOp': Value for 'Source Bands' is invalid: 'NESZ_VV'
[S1B_IW_SLC__1SDV_20200601T170709_20200601T170737_021843_029753_7199_tmp2.xml] failed with return code 1
[2022-07-07 15:21:06,099] [ INFO] [GEOCODE] -- /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170735_20200601T170801_021843_029753_DFD0.SAFE [32632] -- 1592.67
[2022-07-07 15:23:30,265] [ ERROR] [NOISE_P] -- /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170735_20200601T170801_021843_029753_DFD0.SAFE [32632] -- Executing processing graph
done.
INFO: org.esa.snap.core.gpf.operators.tooladapter.ToolAdapterIO: Initializing external tool adapters
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: Incompatible GDAL 3.5.1 found on system. Internal GDAL 3.2.1 from distribution will be used.
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: Internal GDAL 3.2.1 set to be used by SNAP.
INFO: org.esa.snap.core.util.EngineVersionCheckActivator: Please check regularly for new updates for the best SNAP experience.
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: Internal GDAL 3.2.1 set to be used by SNAP.
INFO: org.hsqldb.persist.Logger: dataFileCache open start
org.esa.snap.core.gpf.graph.GraphException: [NodeId: BandSelect] Operator 'BandSelectOp': Value for 'Source Bands' is invalid: 'NESZ_VV'
at org.esa.snap.core.gpf.graph.NodeContext.initTargetProduct(NodeContext.java:79)
at org.esa.snap.core.gpf.graph.GraphContext.initNodeContext(GraphContext.java:199)
at org.esa.snap.core.gpf.graph.GraphContext.initNodeContext(GraphContext.java:182)
at org.esa.snap.core.gpf.graph.GraphContext.initOutput(GraphContext.java:166)
at org.esa.snap.core.gpf.graph.GraphContext.<init>(GraphContext.java:85)
at org.esa.snap.core.gpf.graph.GraphContext.<init>(GraphContext.java:58)
at org.esa.snap.core.gpf.graph.GraphProcessor.executeGraph(GraphProcessor.java:127)
at org.esa.snap.core.gpf.main.DefaultCommandLineContext.executeGraph(DefaultCommandLineContext.java:86)
at org.esa.snap.core.gpf.main.CommandLineTool.executeGraph(CommandLineTool.java:547)
at org.esa.snap.core.gpf.main.CommandLineTool.runGraph(CommandLineTool.java:391)
at org.esa.snap.core.gpf.main.CommandLineTool.runGraphOrOperator(CommandLineTool.java:287)
at org.esa.snap.core.gpf.main.CommandLineTool.run(CommandLineTool.java:188)
at org.esa.snap.core.gpf.main.CommandLineTool.run(CommandLineTool.java:121)
at org.esa.snap.core.gpf.main.GPT.run(GPT.java:59)
at org.esa.snap.core.gpf.main.GPT.main(GPT.java:37)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.esa.snap.runtime.Launcher.lambda$run$0(Launcher.java:55)
at org.esa.snap.runtime.Engine.runClientCode(Engine.java:189)
at org.esa.snap.runtime.Launcher.run(Launcher.java:51)
at org.esa.snap.runtime.Launcher.main(Launcher.java:31)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:84)
at com.install4j.runtime.launcher.UnixLauncher.start(UnixLauncher.java:66)
at install4j.org.esa.snap.runtime.Launcher_gpt.main(Unknown Source)
Caused by: org.esa.snap.core.gpf.OperatorException: Operator 'BandSelectOp': Value for 'Source Bands' is invalid: 'NESZ_VV'
at org.esa.snap.core.gpf.internal.OperatorContext.injectConfiguration(OperatorContext.java:1149)
at org.esa.snap.core.gpf.internal.OperatorContext.initializeOperator(OperatorContext.java:526)
at org.esa.snap.core.gpf.internal.OperatorContext.getTargetProduct(OperatorContext.java:298)
at org.esa.snap.core.gpf.Operator.getTargetProduct(Operator.java:385)
at org.esa.snap.core.gpf.graph.NodeContext.initTargetProduct(NodeContext.java:77)
... 29 more
Caused by: com.bc.ceres.binding.ValidationException: Value for 'Source Bands' is invalid: 'NESZ_VV'
at com.bc.ceres.binding.validators.ValueSetValidator.validateValue(ValueSetValidator.java:37)
at com.bc.ceres.binding.validators.ArrayValidator.validateValue(ArrayValidator.java:37)
at com.bc.ceres.binding.validators.MultiValidator.validateValue(MultiValidator.java:52)
at com.bc.ceres.binding.Property.validate(Property.java:270)
at com.bc.ceres.binding.Property.setValue(Property.java:172)
at com.bc.ceres.binding.dom.DefaultDomConverter.convertDomChildToProperty(DefaultDomConverter.java:194)
at com.bc.ceres.binding.dom.DefaultDomConverter.convertDomChildToPropertySet(DefaultDomConverter.java:182)
at com.bc.ceres.binding.dom.DefaultDomConverter.convertDomToPropertySet(DefaultDomConverter.java:165)
at com.bc.ceres.binding.dom.DefaultDomConverter.convertDomToValue(DefaultDomConverter.java:158)
at org.esa.snap.core.gpf.internal.OperatorContext.configureOperator(OperatorContext.java:1165)
at org.esa.snap.core.gpf.internal.OperatorContext.injectConfiguration(OperatorContext.java:1145)
... 33 more
Error: [NodeId: BandSelect] Operator 'BandSelectOp': Value for 'Source Bands' is invalid: 'NESZ_VV'
[S1B_IW_SLC__1SDV_20200601T170735_20200601T170801_021843_029753_DFD0_tmp2.xml] failed with return code 1
Traceback (most recent call last):
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/processor.py", line 180, in main
noise_power(infile=scene.scene, outdir=out_dir_scene_epsg, polarizations=scene.polarizations,
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/pyroSAR/snap/util.py", line 1011, in noise_power
gpt(xmlfile=wf_name, tmpdir=procdir, groups=groups, cleanup=cleanup)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/pyroSAR/snap/auxil.py", line 399, in gpt
execute(sub, cleanup=cleanup, gpt_exceptions=gpt_exceptions, gpt_args=gpt_args)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/pyroSAR/snap/auxil.py", line 290, in execute
raise RuntimeError(submessage.format(out, err, os.path.basename(xmlfile), proc.returncode))
RuntimeError: Executing processing graph
done.
INFO: org.esa.snap.core.gpf.operators.tooladapter.ToolAdapterIO: Initializing external tool adapters
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: Incompatible GDAL 3.5.1 found on system. Internal GDAL 3.2.1 from distribution will be used.
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: Internal GDAL 3.2.1 set to be used by SNAP.
INFO: org.esa.snap.core.util.EngineVersionCheckActivator: Please check regularly for new updates for the best SNAP experience.
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: Internal GDAL 3.2.1 set to be used by SNAP.
INFO: org.hsqldb.persist.Logger: dataFileCache open start
org.esa.snap.core.gpf.graph.GraphException: [NodeId: BandSelect] Operator 'BandSelectOp': Value for 'Source Bands' is invalid: 'NESZ_VV'
at org.esa.snap.core.gpf.graph.NodeContext.initTargetProduct(NodeContext.java:79)
at org.esa.snap.core.gpf.graph.GraphContext.initNodeContext(GraphContext.java:199)
at org.esa.snap.core.gpf.graph.GraphContext.initNodeContext(GraphContext.java:182)
at org.esa.snap.core.gpf.graph.GraphContext.initOutput(GraphContext.java:166)
at org.esa.snap.core.gpf.graph.GraphContext.<init>(GraphContext.java:85)
at org.esa.snap.core.gpf.graph.GraphContext.<init>(GraphContext.java:58)
at org.esa.snap.core.gpf.graph.GraphProcessor.executeGraph(GraphProcessor.java:127)
at org.esa.snap.core.gpf.main.DefaultCommandLineContext.executeGraph(DefaultCommandLineContext.java:86)
at org.esa.snap.core.gpf.main.CommandLineTool.executeGraph(CommandLineTool.java:547)
at org.esa.snap.core.gpf.main.CommandLineTool.runGraph(CommandLineTool.java:391)
at org.esa.snap.core.gpf.main.CommandLineTool.runGraphOrOperator(CommandLineTool.java:287)
at org.esa.snap.core.gpf.main.CommandLineTool.run(CommandLineTool.java:188)
at org.esa.snap.core.gpf.main.CommandLineTool.run(CommandLineTool.java:121)
at org.esa.snap.core.gpf.main.GPT.run(GPT.java:59)
at org.esa.snap.core.gpf.main.GPT.main(GPT.java:37)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.esa.snap.runtime.Launcher.lambda$run$0(Launcher.java:55)
at org.esa.snap.runtime.Engine.runClientCode(Engine.java:189)
at org.esa.snap.runtime.Launcher.run(Launcher.java:51)
at org.esa.snap.runtime.Launcher.main(Launcher.java:31)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:84)
at com.install4j.runtime.launcher.UnixLauncher.start(UnixLauncher.java:66)
at install4j.org.esa.snap.runtime.Launcher_gpt.main(Unknown Source)
Caused by: org.esa.snap.core.gpf.OperatorException: Operator 'BandSelectOp': Value for 'Source Bands' is invalid: 'NESZ_VV'
at org.esa.snap.core.gpf.internal.OperatorContext.injectConfiguration(OperatorContext.java:1149)
at org.esa.snap.core.gpf.internal.OperatorContext.initializeOperator(OperatorContext.java:526)
at org.esa.snap.core.gpf.internal.OperatorContext.getTargetProduct(OperatorContext.java:298)
at org.esa.snap.core.gpf.Operator.getTargetProduct(Operator.java:385)
at org.esa.snap.core.gpf.graph.NodeContext.initTargetProduct(NodeContext.java:77)
... 29 more
Caused by: com.bc.ceres.binding.ValidationException: Value for 'Source Bands' is invalid: 'NESZ_VV'
at com.bc.ceres.binding.validators.ValueSetValidator.validateValue(ValueSetValidator.java:37)
at com.bc.ceres.binding.validators.ArrayValidator.validateValue(ArrayValidator.java:37)
at com.bc.ceres.binding.validators.MultiValidator.validateValue(MultiValidator.java:52)
at com.bc.ceres.binding.Property.validate(Property.java:270)
at com.bc.ceres.binding.Property.setValue(Property.java:172)
at com.bc.ceres.binding.dom.DefaultDomConverter.convertDomChildToProperty(DefaultDomConverter.java:194)
at com.bc.ceres.binding.dom.DefaultDomConverter.convertDomChildToPropertySet(DefaultDomConverter.java:182)
at com.bc.ceres.binding.dom.DefaultDomConverter.convertDomToPropertySet(DefaultDomConverter.java:165)
at com.bc.ceres.binding.dom.DefaultDomConverter.convertDomToValue(DefaultDomConverter.java:158)
at org.esa.snap.core.gpf.internal.OperatorContext.configureOperator(OperatorContext.java:1165)
at org.esa.snap.core.gpf.internal.OperatorContext.injectConfiguration(OperatorContext.java:1145)
... 33 more
Error: [NodeId: BandSelect] Operator 'BandSelectOp': Value for 'Source Bands' is invalid: 'NESZ_VV'
[S1B_IW_SLC__1SDV_20200601T170735_20200601T170801_021843_029753_DFD0_tmp2.xml] failed with return code 1
[2022-07-07 15:24:08,619] [ ERROR] [ NRB] -- ['/codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170709_20200601T170737_021843_029753_7199.SAFE', '/codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170735_20200601T170801_021843_029753_DFD0.SAFE'] [32632] -- Error reading file '/tmp/spatialist/tmp4_j3cs_v.vrt': failed to load external entity "/tmp/spatialist/tmp4_j3cs_v.vrt"
Traceback (most recent call last):
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/processor.py", line 219, in main
msg = nrb.format(config=config, scenes=scenes, datadir=config['rtc_dir'], outdir=outdir,
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/nrb.py", line 175, in format
tree = etree.parse(source)
File "src/lxml/etree.pyx", line 3538, in lxml.etree.parse
File "src/lxml/parser.pxi", line 1876, in lxml.etree._parseDocument
File "src/lxml/parser.pxi", line 1902, in lxml.etree._parseDocumentFromURL
File "src/lxml/parser.pxi", line 1805, in lxml.etree._parseDocFromFile
File "src/lxml/parser.pxi", line 1177, in lxml.etree._BaseParser._parseDocFromFile
File "src/lxml/parser.pxi", line 615, in lxml.etree._ParserContext._handleParseResultDoc
File "src/lxml/parser.pxi", line 725, in lxml.etree._handleParseResult
File "src/lxml/parser.pxi", line 652, in lxml.etree._raiseParseError
OSError: Error reading file '/tmp/spatialist/tmp4_j3cs_v.vrt': failed to load external entity "/tmp/spatialist/tmp4_j3cs_v.vrt"delete processed RTC products
Currently all processed RTC products are kept forever. The processor should delete them once all possible NRB products have been created from them. However, it needs to be made sure that they are not re-processed at some later point. Perhaps leave the empty folder or some empty text file?
Process breaks during GEOCODE process
Hello again ;-)
I fixed my DEM issues.
However, I'm facing a new problem during GEOCODE process, although I updated the S1TBX:
Here is the log file:
====================================================================================================================
PROCESSING CONFIGURATION
mode = all
aoi_tiles = ['32UNA']
aoi_geometry = None
mindate = 2020-05-31T00:00:00
maxdate = 2020-06-02T00:00:00
acq_mode = IW
work_dir = /media/data_storage/data_storage/florian/S1_NRB/work
scene_dir = /codede/Sentinel-1/SAR/SLC/2020/06/01
rtc_dir = /media/data_storage/data_storage/florian/S1_NRB/work/RTC
tmp_dir = /media/data_storage/data_storage/florian/S1_NRB/work/TMP
nrb_dir = /media/data_storage/data_storage/florian/S1_NRB/work/NRB
dem_dir = /media/data_storage/data_storage/florian/S1_NRB/work/DEM
wbm_dir = /media/data_storage/data_storage/florian/S1_NRB/work/WBM
log_dir = /media/data_storage/data_storage/florian/S1_NRB/work/LOG
db_file = /media/data_storage/data_storage/florian/S1_NRB/scenes.db
kml_file = /media/data_storage/data_storage/florian/S1_NRB/S2A_OPER_GIP_TILPAR_MPC__20151209T095117_V20150622T000000_21000101T000000_B00.kml
dem_type = Copernicus 30m Global DEM II
====================================================================================================================
SOFTWARE
S1_NRB: 1.0.0
snap-core: 8.0.9 | 202112101916
snap-s1tbx: 8.0.6 | 202202100514
python: 3.10.5 | packaged by conda-forge | (main, Jun 14 2022, 07:04:59) [GCC 10.3.0]
python-pyroSAR: 0.17.2
python-spatialist: 0.11.0
python-GDAL: 3.5.0
gdal_threads = 4
====================================================================================================================
[2022-06-30 06:32:28,212] [ ERROR] [GEOCODE] -- /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170709_20200601T170737_021843_029753_7199.SAFE [32632] -- The Terrain-Flattening node does not accept parameter 'outputSigma0'. Please update S1TBX.
Traceback (most recent call last):
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/pyroSAR/snap/util.py", line 467, in geocode
tf.parameters['outputSigma0'] = True
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/pyroSAR/snap/auxil.py", line 1292, in __setitem__
raise KeyError('key {} does not exist'.format(key))
KeyError: 'key outputSigma0 does not exist'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/processor.py", line 155, in main
geocode(infile=scene, outdir=out_dir_scene_epsg, t_srs=epsg, tmpdir=tmp_dir_scene_epsg,
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/pyroSAR/snap/util.py", line 469, in geocode
raise RuntimeError("The Terrain-Flattening node does not accept "
RuntimeError: The Terrain-Flattening node does not accept parameter 'outputSigma0'. Please update S1TBX.
[2022-06-30 06:32:28,314] [ ERROR] [GEOCODE] -- /codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170735_20200601T170801_021843_029753_DFD0.SAFE [32632] -- The Terrain-Flattening node does not accept parameter 'outputSigma0'. Please update S1TBX.
Traceback (most recent call last):
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/pyroSAR/snap/util.py", line 467, in geocode
tf.parameters['outputSigma0'] = True
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/pyroSAR/snap/auxil.py", line 1292, in __setitem__
raise KeyError('key {} does not exist'.format(key))
KeyError: 'key outputSigma0 does not exist'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/processor.py", line 155, in main
geocode(infile=scene, outdir=out_dir_scene_epsg, t_srs=epsg, tmpdir=tmp_dir_scene_epsg,
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/pyroSAR/snap/util.py", line 469, in geocode
raise RuntimeError("The Terrain-Flattening node does not accept "
RuntimeError: The Terrain-Flattening node does not accept parameter 'outputSigma0'. Please update S1TBX.
[2022-06-30 06:32:30,709] [ ERROR] [ NRB] -- ['/codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170709_20200601T170737_021843_029753_7199.SAFE', '/codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170735_20200601T170801_021843_029753_DFD0.SAFE'] [32632] -- list index out of range
Traceback (most recent call last):
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/processor.py", line 219, in main
msg = nrb.format(config=config, scenes=scenes, datadir=config['rtc_dir'], outdir=outdir,
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/nrb.py", line 85, in format
src_ids, snap_datasets, snap_datamasks = get_datasets(scenes=scenes, datadir=datadir,
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/nrb.py", line 329, in get_datasets
snap_dm_ras = re.sub(pattern, 'datamask', pols[0])
IndexError: list index out of rangeReprocessing scenes with different DEM type requires manually deleting old DEM file
Currently we store DEM files used for the GEOCODE process in the following way:
<TMP_dir>/<SLC_fullname>/<EPSG_code>/<SLC_basename>_DEM_<EPSG_code>.tif
Using the generic _DEM_ in the filename will result in a hidden issue if one would reprocess a scene using a different DEM type. In this case the DEM file would not be overwritten due to this line and the scene would be reprocessed with the previously used DEM type instead. I would suggest to use an abbreviation of the DEM type instead of _DEM_ in the filename.
Invalid dates in STAC metadata
When validating STAC items, I have found invalid dates, especially in the assets (created).
https://staclint.com/ reports the following:
Invalid STAC: ValidationError
Error Message: '2023-06-11T22:11:02.808462' does not match '(\\+00:00|Z)$'. Error is in assets -> vv-g-lin -> created
Schema: https://schemas.stacspec.org/v1.0.0/item-spec/json-schema/item.json
Version: 1.0.0
+00:00 or Z is missing at the end.
Related source code for the assets (but in may appear in other parts as well):
https://github.com/SAR-ARD/S1_NRB/blob/1bf2e6e9560bdef5daf459c585a8f4f7c112a7c5/S1_NRB/metadata/stac.py#L218C27-L218C86
Alternative to download S2 tiling grid KML
I have extracted and converted the polygon features of the Sentinel-2 tiling grid KML file to a lightweight 10 MB Flatgeobuf file, which allows random access through GDAL's /vsicurl/. This might be a viable alternative to downloading and storing the 108 MB KML file. Visually the grid aligns to the KML grid. I have not done any other tests though.
Look Direction Image not calculated for all swaths (SLC)
update folder structure in documentation
The folder structure described in the documentation is outdated:
https://s1-nrb.readthedocs.io/en/latest/general/folderstructure.html
- the original source metadata needs to be added
- scenes.db is optional
- *.data items should be highlighted as folders
config.ini: only *.zip input possible?
Dear Marco,
greetings from Bunswick (We met on the ESA LPS) :-)
Currently I want to take a look into your S1_NRB framework and I try to understand how to use it.
Installation went well so far.
However, I read the following in the docs:
scene_dir will be searched recursively for any Sentinel-1 scenes using the regex pattern '^S1[AB].*.zip$'.
We are using CODE-DE (cloud service) for processing and there we have access to the entire Copernicus archive for Germany.
Problem is now, that all the scenes are already unzipped to the *.SAFE folder structure.
Is it still possible to use the config.ini although we do not have the zip files?
Second issue is then, that I do not know how to combine your approach of the "scences" directory with the structure CODE-DE is saving their data.
The CODE-DE structure is using single YEAR, MONTH, DAY folders to split all aquisitions in to single sub-directories.
It would be a fantastic help, if you could share an End-to-End example, how to apply the whole process in a juypter notebook for one single image (in python).
db_file config variable check fails if file not available
pyroSAR has to functionality to automatically create the scenes database file if it is not available. However, you need to specify an existing db_file in the config.ini. If this file does not exist, the processor will not run (see file exists check below in config.py).
https://github.com/SAR-ARD/S1_NRB/blob/main/S1_NRB/config.py#L65-L70
It would be good to either remove this check for this variable or to rename the variable. What do you think?
`ancillary.create_data_mask` - RuntimeError: no intersection between Raster and Vector object
As reported by @gr4n0t4, processing of scene S1A_IW_SLC__1SDV_20210502T171502_20210502T171529_037712_04733D_777C fails during the creation of the data mask layer for tile 32TNR (and possibly others) here:
https://github.com/SAR-ARD/S1_NRB/blob/93fa692c15ccd4821f31900dff2ee5eea324c58c/S1_NRB/ancillary.py#L322
unexpected datatake metadata in L1 products
Several data takes seem to have faulty entries for sliceNumber and totalSlices in the manifest.safe file. For these data takes crossing Germany in 2022 both entries are 0:
- 051EB3 (2022-04-22)
- 052011 (2022-04-25)
- 052F24 (2022-05-28)
(only checked the GRDs)
Currently these scenes cannot be processed because of a check in function S1_NRB.ancillary.check_acquisition_completeness.
Several cases have been found where the scene had 0 as value for both entries but later the scene was re-published and then did contain the right values. It needs to be checked whether re-publication is always intended for scenes with faulty metadata.
remove geometry definition requirement
Currently a user needs to define one or multiple geometries via config parameters aoi_tiles or aoi_geometry. Optimally this requirement is lifted so that a user can just process some scenes without knowing the IDs of the overlapping tiles or creating some geometry vector file.
The IDs of all tiles overlapping with a scene can of course directly be determined inside the processor. However, the processor is currently not able to determine whether all acquired scenes covering this particular tile exist locally. If this is not checked, an NRB tile with incomplete coverage could be created. See #8 for more discussion on this.
For the example scene below, only two tiles (green) can be processed without input from other SLCs acquired in the same data take (yellow):
artefact along scene boundaries
Apparently the GRD buffering and merging does not work perfectly so that the boundary of two merged scenes can still be seen over ocean:
Disvovered in this tile:
S1A_EW_NRB__1SDV_20221215T071803_046339_058CCF_28SBB_9597
Input scenes:
- S1A_EW_GRDM_1SDV_20221215T071713_20221215T071813_046339_058CCF_C7C9
- S1A_EW_GRDM_1SDV_20221215T071813_20221215T071913_046339_058CCF_601B
gaps in data takes
It can happen that some scenes are not made available resulting in gaps in the data take:
In the example above (S1A IW GRD on 2022-09-17) once scene is missing, which currently results in the following error:
RuntimeError: missing the following scenes:
- successor acquisition for scene S1A_IW_GRDH_1SDV_20220917T052551_20220917T052616_045040_0561A9_415F.SAFE
- predecessor acquisition for scene S1A_IW_GRDH_1SDV_20220917T052641_20220917T052706_045040_0561A9_C5D8.SAFE
This error is intended because the processor only sees what is available locally and rightfully complains that the scene is missing. If the scene would indeed only be missing locally, processing the two listed scenes would result in incomplete NRB tiles.
I assume some mechanism is needed to check an online database whether the scene has ever been made available and only raise an error if it has not.
Enable processing across multiple UTM zones
The processor allows definition of AOIs via the two config arguments aoi_tiles and aoi_geomery. Both are only allowed to cover a single UTM zone. In case of aoi_tiles, all tiles must be in the same UTM zone (identical first two digits of the ID, e.g. 32TPT and 32TQT but not 33TUN). Similarly, a geometry defined via aoi_geometry must not cover tiles with multiple UTM zones.
Optimally, a user could define arbitrary tile IDs or geometries.
Optimize noise power processing
Currently the processing of backscatter (NRB) and noise power (NPI) are separated in two different workflows. This was easier to conceptualize although it increases processing time. For NRB, the images are scaled to beta0 and the noise power images (stored as noise equivalent beta zero (NEBZ)) are discarded in further processing. For NPI, images are scaled to sigma nought to derive noise equivalent sigma zero (NESZ) and the backscatter images are discarded. This is done with the SNAP Calibration and ThermalNoiseRemoval operators. THe output of the former controls that of the latter.
SNAP workflows are designed to connect individual operators, which themselves do not necessarily write intermediate products. These workflows can easily become very large and complicated to modify while consuming more compute resources and memory. When developing the NPI workflow, it was decided to separate the processing from the already complex NRB workflow.
pyroSAR, the SNAP processing API used by S1_NRB, is designed to write full connected workflows into an XML file (which can then be kept with the processing results for future reference), but splits these workflows during processing. Smaller workflows writing intermediate results have been found to significantly increase processing speed.
Future versions of the processor could move away from the idea of writing a full workflow for processing and instead execute steps in smaller workflows from the beginning. This way, intermediate results could be named more clearly and be merged in later processing steps. In principle, the following steps (workflows) are necessary:
- data conversion and OSV refinement
- NPI: calibration to sigma0, thermal noise removal, TOPSAR deburst, multi-looking
- NRB: calibration to beta0, thermal noise removal, TOPSAR deburst, multi-looking, terrain flattening
- NRB: computation of local contributing area and gamma-sigma ratio
- merging of outputs from steps 2-5, geocoding
This would avoid separate data converison, OSV refinement and geocoding of noise power images. Noise removal has to be performed before TOPSAR-deburst so the latter step cannot be performed in workflow 1.
Copernicus DEM archive not complete?
I think I accidentally hit a region in Germany where there is no DEM tile on aws, right?
Is there another source for the tif files?
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N52_00_E007_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N52_00_E007_00_DEM/Copernicus_DSM_COG_10_N52_00_E007_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N54_00_E012_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N54_00_E012_00_DEM/Copernicus_DSM_COG_10_N54_00_E012_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N54_00_E006_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N54_00_E006_00_DEM/Copernicus_DSM_COG_10_N54_00_E006_00_DEM.tif
Traceback (most recent call last):
File "/opt/anaconda3/envs/nrb_env/bin/s1_nrb", line 8, in <module>
sys.exit(cli())
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/click/core.py", line 1130, in __call__
return self.main(*args, **kwargs)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/click/core.py", line 1055, in main
rv = self.invoke(ctx)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/click/core.py", line 1404, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/click/core.py", line 760, in invoke
return __callback(*args, **kwargs)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/cli.py", line 18, in cli
S1_NRB.process(config_file=config_file, section_name=section, debug=debug)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/processor.py", line 93, in main
dem.prepare(geometries=geometries, threads=gdal_prms['threads'],
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/dem.py", line 99, in prepare
dem_autoload([geometry], demType=dem_type,
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/pyroSAR/auxdata.py", line 224, in dem_autoload
return handler.load(demType=demType,
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/pyroSAR/auxdata.py", line 739, in load
locals = self.__retrieve(self.config[demType]['url'], remotes, outdir)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/pyroSAR/auxdata.py", line 490, in __retrieve
r.raise_for_status()
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/requests/models.py", line 1022, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N54_00_E006_00_DEM/Copernicus_DSM_COG_10_N54_00_E006_00_DEM.tif
(nrb_env) eouser@jupyterhub:~/data_storage/florian/S1_NRB$ cd /home/eouser/.snap/auxdata/dem/Copernicus\ 30m\ Global\ DEM
(nrb_env) eouser@jupyterhub:~/.snap/auxdata/dem/Copernicus 30m Global DEM$ wget https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N54_00_E006_00_DEM/Copernicus_DSM_COG_10_N54_00_E006_00_DEM.tif
--2022-06-24 14:09:55-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N54_00_E006_00_DEM/Copernicus_DSM_COG_10_N54_00_E006_00_DEM.tif
Resolving copernicus-dem-30m.s3.eu-central-1.amazonaws.com (copernicus-dem-30m.s3.eu-central-1.amazonaws.com)... 52.219.47.112
Connecting to copernicus-dem-30m.s3.eu-central-1.amazonaws.com (copernicus-dem-30m.s3.eu-central-1.amazonaws.com)|52.219.47.112|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2022-06-24 14:09:55 ERROR 404: Not Found.environment variable 'PROJ_LIB' not set
Got this error executing the Docker version
File "/usr/local/envs/nrb_env/bin/s1_nrb", line 8, in <module>
sys.exit(cli())
^^^^^
File "/usr/local/envs/nrb_env/lib/python3.11/site-packages/click/core.py", line 1130, in __call__
return self.main(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/envs/nrb_env/lib/python3.11/site-packages/click/core.py", line 1055, in main
rv = self.invoke(ctx)
^^^^^^^^^^^^^^^^
File "/usr/local/envs/nrb_env/lib/python3.11/site-packages/click/core.py", line 1404, in invoke
return ctx.invoke(self.callback, **ctx.params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/envs/nrb_env/lib/python3.11/site-packages/click/core.py", line 760, in invoke
return __callback(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/envs/nrb_env/lib/python3.11/site-packages/S1_NRB/cli.py", line 18, in cli
S1_NRB.process(config_file=config_file, section_name=section, debug=debug)
File "/usr/local/envs/nrb_env/lib/python3.11/site-packages/S1_NRB/processor.py", line 109, in main
dem.mosaic(geometry=geom, outname=fname_dem, dem_type=config['dem_type'],
File "/usr/local/envs/nrb_env/lib/python3.11/site-packages/S1_NRB/dem.py", line 230, in mosaic
dem_create(src=vrt, dst=outname, pbar=True,
File "/usr/local/envs/nrb_env/lib/python3.11/site-packages/pyroSAR/auxdata.py", line 367, in dem_create
get_egm_lookup(geoid=geoid, software='PROJ')
File "/usr/local/envs/nrb_env/lib/python3.11/site-packages/pyroSAR/auxdata.py", line 1072, in get_egm_lookup
raise RuntimeError("environment variable 'PROJ_LIB' not set")
RuntimeError: environment variable 'PROJ_LIB' not set
Docker should have the environment variable 'PROJ_LIB' set for pyroSAR
Add
RUN echo "export PROJ_LIB=/usr/local/envs/nrb_env/share/proj" >> ~/.bashrc To the docker file (and add proj dependency to pyroSAR) solved the issue
Automatically identify tile names from input scene(s)
Currently, I need to set either a geometry or the tile names in the config file. It would be more easy if the tile names could be automatically extracted from the geometry of the scenes. Otherwise I need to first always look up the tile numbers for each scene that we process.
corrupt WBM tiles through concurrent writing in parallel processes
In parallel processes WBM tiles might be attempted to be created multiple times causing corrupt files. It needs to be made sure that a WBM tile is only created once and other processes needing it wait until it is finished. Or each process creates its own file and only the first to finish renames it to the final file name.
nodata value could not be read from the source file while `creating WBM MGRS tiles`
I have to remote machines (Ubuntu) one with snap 8 and one with snap 9.
Input files are *.SAFE directories for one day over Germany.
I want to process one Tile (32UNA or 32UPC).
I get the same error on every machine while creating WBM MGRS tiles
### creating WBM MGRS tiles:
['32UMA', '32UMB', '32UMC', '32UNA', '32UNB', '32UNC', '32UPA', '32UPB', '32UPC', '32UQA', '32UQB', '32UQC', '33UUS_32632', '33UUT_32632']
Traceback (most recent call last):
File "/opt/anaconda3/envs/nrb_env/bin/s1_nrb", line 8, in <module>
sys.exit(cli())
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/click/core.py", line 1130, in __call__
return self.main(*args, **kwargs)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/click/core.py", line 1055, in main
rv = self.invoke(ctx)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/click/core.py", line 1404, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/click/core.py", line 760, in invoke
return __callback(*args, **kwargs)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/cli.py", line 18, in cli
S1_NRB.process(config_file=config_file, section_name=section, debug=debug)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/processor.py", line 93, in main
dem.prepare(geometries=geometries, threads=gdal_prms['threads'],
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/dem.py", line 124, in prepare
dem_create(src=fname_wbm_tmp, dst=filename,
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/pyroSAR/auxdata.py", line 300, in dem_create
raise RuntimeError('the nodata value could not be read from the source file. Please explicitly define it.')
RuntimeError: the nodata value could not be read from the source file. Please explicitly define it.LOG-File SNAP8 machine:
===================================================================================================================
PROCESSING CONFIGURATION
mode = all
aoi_tiles = ['32UPC']
aoi_geometry = None
mindate = 2020-05-31T00:00:00
maxdate = 2020-06-02T00:00:00
acq_mode = IW
work_dir = /media/data_storage/florian/S1_NRB/work
scene_dir = /codede/Sentinel-1/SAR/SLC/2020/06/01
rtc_dir = /media/data_storage/florian/S1_NRB/work/RTC
tmp_dir = /media/data_storage/florian/S1_NRB/work/TMP
nrb_dir = /media/data_storage/florian/S1_NRB/work/NRB
dem_dir = /media/data_storage/florian/S1_NRB/work/DEM
wbm_dir = /media/data_storage/florian/S1_NRB/work/WBM
log_dir = /media/data_storage/florian/S1_NRB/work/LOG
db_file = /media/data_storage/florian/S1_NRB/scenes.db
kml_file = /media/data_storage/florian/S1_NRB/S2A_OPER_GIP_TILPAR_MPC__20151209T095117_V20150622T000000_21000101T000000_B00.kml
dem_type = Copernicus 30m Global DEM II
====================================================================================================================
SOFTWARE
S1_NRB: 1.0.0
snap-core: unknown
snap-s1tbx: unknown
python: 3.10.5 | packaged by conda-forge | (main, Jun 14 2022, 07:04:59) [GCC 10.3.0]
python-pyroSAR: 0.17.3
python-spatialist: 0.11.0
python-GDAL: 3.5.1
gdal_threads = 10
====================================================================================================================
LOG-File SNAP9 machine:
====================================================================================================================
PROCESSING CONFIGURATION
mode = all
aoi_tiles = ['32UNA']
aoi_geometry = None
mindate = 2020-05-31T00:00:00
maxdate = 2020-06-02T00:00:00
acq_mode = IW
work_dir = /media/data_storage/florian/S1_NRB/work
scene_dir = /codede/Sentinel-1/SAR/SLC/2020/06/01
rtc_dir = /media/data_storage/florian/S1_NRB/work/RTC
tmp_dir = /media/data_storage/florian/S1_NRB/work/TMP
nrb_dir = /media/data_storage/florian/S1_NRB/work/NRB
dem_dir = /media/data_storage/florian/S1_NRB/work/DEM
wbm_dir = /media/data_storage/florian/S1_NRB/work/WBM
log_dir = /media/data_storage/florian/S1_NRB/work/LOG
db_file = /media/data_storage/florian/S1_NRB/scenes.db
kml_file = /media/data_storage/florian/S1_NRB/S2A_OPER_GIP_TILPAR_MPC__20151209T095117_V20150622T000000_21000101T000000_B00.kml
dem_type = Copernicus 30m Global DEM II
====================================================================================================================
SOFTWARE
S1_NRB: 1.0.0
snap-core: 9.0.0 | 202206281505
snap-s1tbx: 9.0.0 | 202206281601
python: 3.10.5 | packaged by conda-forge | (main, Jun 14 2022, 07:04:59) [GCC 10.3.0]
python-pyroSAR: 0.17.3
python-spatialist: 0.11.0
python-GDAL: 3.5.1
gdal_threads = 20
====================================================================================================================
wind normalized backscatter ratio contains absolute path
The function S1_NRB.ard.wind_normalization creates a VRT, which divides the sigma naught backscatter by the wind-modelled backscatter to create a wind-normalized backscatter image. Currently the path to the wind-modelled backscatter is absolute but must be relative.
<ComplexSource>
<SourceFilename relativeToVRT="1">../annotation/s1a-iw-orb-20211020t191358-040207-04c343-28rbs-wm.tif</SourceFilename>
<SourceBand>1</SourceBand>
<SourceProperties RasterXSize="120" RasterYSize="120" DataType="Float32" BlockXSize="512" BlockYSize="512"/>
<SrcRect xOff="0" yOff="0" xSize="120" ySize="120"/>
<DstRect xOff="0" yOff="0" xSize="10980" ySize="10980"/>
<NODATA>-9999</NODATA>
</ComplexSource>geolocation accuracy
The S1-NRB product defines a geolocation accuracy estimation as radial root mean square error (rRMSE) that is based on the accuracy of the source product and that of the DEM. This information needs to be written to the metadata.
The following aspects have to be considered:
- different values for the SLC accuracy have been reported and the source used for this product needs to be documented
- the accuracy must be adjusted when applying ETAD correction
- Copernicus DEM accuracy
- values for different regions of the world can be taken from the Copernicus DEM Product Handbook
- detailed values for individual DEM tiles can be read from an ancillary file *ACM.kml (accuracy mask); however, not all tiles contain this information.
- the ACM file is not present in the freely available option with ID
Copernicus 30m Global DEM
- the accuracy of other supported DEMs is yet to be investigated.
The implementation could be done in multiple stages:
- make use of the global LE90 value reported in the Copernicus DEM Handbook and the accuracy values of the SLCs reported in the S1-NRB product specification. The error at 1 sigma can be estimated from LE90 as LE68 assuming Gaussian distribution
- differentiate between global regions as reported in the DEM Handbook
- read tile-specific accuracy if existing and fall back to values above otherwise
- investigate other sources of SLC accuracy (for example annual Sentinel-1 performance reports) and refine the computation if possible
- include DEM resampling error into the rRMSE computation
- include SAR image processing error into the rRMSE computation
Refer to original source metadata files in source XML and JSON
As implemented with #104, currently the original source metadata files (manifest.safe, annotation folder) are just copied to the source directory of a processed scene. The source metadata files in OGC XML and STAC JSON format, which are generated by the processor should include references to all of the original files. This ensures that programs can completely traverse the available metadata files and check for completeness.
GRD buffering is attempted even when no neighbors exist
Example scene: S1A_IW_GRDH_1SDV_20211020T191351_20211020T191420_040207_04C343_BD6A
### buffering scene with neighboring acquisitions
Traceback (most recent call last):
File "nrb_env\Scripts\s1_nrb-script.py", line 33, in <module>
sys.exit(load_entry_point('S1-NRB', 'console_scripts', 's1_nrb')())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "nrb_env\Lib\site-packages\click\core.py", line 1130, in __call__
return self.main(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "nrb_env\Lib\site-packages\click\core.py", line 1055, in main
rv = self.invoke(ctx)
^^^^^^^^^^^^^^^^
File "nrb_env\Lib\site-packages\click\core.py", line 1404, in invoke
return ctx.invoke(self.callback, **ctx.params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "nrb_env\Lib\site-packages\click\core.py", line 760, in invoke
return __callback(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "nrb_env\Lib\site-packages\click\decorators.py", line 26, in new_func
return f(get_current_context(), *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "s1_nrb\S1_NRB\cli.py", line 61, in cli
S1_NRB.process(config_file=config_file, section_name=section, debug=debug, **extra)
File "s1_nrb\S1_NRB\processor.py", line 244, in main
snap.process(scene=scene.scene, outdir=config['rtc_dir'],
File "s1_nrb\S1_NRB\snap.py", line 684, in process
grd_buffer(src=out_pre, dst=out_buffer, workflow=out_buffer_wf,
File "s1_nrb\S1_NRB\snap.py", line 205, in grd_buffer
wf.insert_node(asm, before=read_ids)
File "pyroSAR\pyroSAR\snap\auxil.py", line 994, in insert_node
newnode.source = before
^^^^^^^^^^^^^^
File "pyroSAR\pyroSAR\snap\auxil.py", line 1261, in source
raise TypeError(
TypeError: node SliceAssembly has multiple sources, which must be reset using a list, not str
"mean of empty slice" error during ENL computation
Just got this error:
S1_NRB\metadata\extract.py:596: RuntimeWarning: Mean of empty slice
_mean = np.nanmean(blocks, axis=(1, 3))
numpy\lib\nanfunctions.py:1872: RuntimeWarning: Degrees of freedom <= 0 for slice.
var = nanvar(a, axis=axis, dtype=dtype, out=out, ddof=ddof,
S1A_IW_GRDH_1SDV_20230101T183417_20230101T183446_046594_05957D_40AA.xml
renaming to accomodate ORB product
Several names of configuration parameters and variable names are specific to NRB and should be renamed to something more universal to apply to ORB as well (before potentially renaming the whole repository). Here's a first list, to be implemented after a more thorough check:
S1_NRB.metadata.mapping:NRB_PATTERN->ARD_PATTERN|RB_PATTERN|NRB_PATTERN+ORB_PATTERN?ORB_MAP->OSV_MAP
config.ini:nrb_dir->ard_dir|rb_dir?rtc_dir->sar_dir?mode:all+rtc+nrb->all+sar+ard?
Terrain Flattening results are currently underperforming
improve log file output
When recently running a larger processing example, I discovered some shortcomings with the current log file content. Some observations:
- one always has to check both the command line stdout as well as the processor log file to get a full picture of the processor run
- each log file entry prints the full list of currently processed scenes. Thsi becomes cluttered when processing a lot of scenes at once
- the time stamp in the log file name contains hour and minute. Being more precise would prevent multiple parallel processes writing into the same file. However, including the second might not be precise enough either. Perhaps a unique identifier needs to be included
- the identification of failed scenes is fairly time consuming; this is due to the very long log files in large processing runs and the insufficient info given on error
just a first list of thoughts. To be further discussed.
scattering area computation fails for S1 SLCs
`ValueError: Invalid integer data type 'f'.` during DEM MGRS creation?
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N48_00_E011_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N48_00_E011_00_DEM/Copernicus_DSM_COG_10_N48_00_E011_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N47_00_E010_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N47_00_E010_00_DEM/Copernicus_DSM_COG_10_N47_00_E010_00_DEM.tif
/home/eouser/.snap/auxdata/dem/Copernicus 30m Global DEM/Copernicus_DSM_COG_10_N46_00_E013_00_DEM.tif <<-- https://copernicus-dem-30m.s3.eu-central-1.amazonaws.com/Copernicus_DSM_COG_10_N46_00_E013_00_DEM/Copernicus_DSM_COG_10_N46_00_E013_00_DEM.tif
### creating DEM MGRS tiles:
['32UMA', '32UMU', '32UMV', '32UNA', '32UNU', '32UNV', '32UPA', '32UPU', '32UPV', '32UQA', '32UQU', '32UQV', '33UUP_32632', '33UUQ_32632', '33UUR_32632']
Traceback (most recent call last):
File "/opt/anaconda3/envs/nrb_env/bin/s1_nrb", line 8, in <module>
sys.exit(cli())
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/click/core.py", line 1130, in __call__
return self.main(*args, **kwargs)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/click/core.py", line 1055, in main
rv = self.invoke(ctx)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/click/core.py", line 1404, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/click/core.py", line 760, in invoke
return __callback(*args, **kwargs)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/cli.py", line 18, in cli
S1_NRB.process(config_file=config_file, section_name=section, debug=debug)
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/processor.py", line 93, in main
dem.prepare(geometries=geometries, threads=gdal_prms['threads'],
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/dem.py", line 111, in prepare
dem_create(src=fname_dem_tmp, dst=filename,
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/pyroSAR/auxdata.py", line 323, in dem_create
nodata = np.iinfo(Dtype(dtype_tmp).numpystr).max
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/numpy/core/getlimits.py", line 656, in __init__
raise ValueError("Invalid integer data type %r." % (self.kind,))
ValueError: Invalid integer data type 'f'.I've got the next issue... this time I do not know, what could be the reason...
Improve usage via CLI & config.ini
See also #2
Some thoughts:
-
s1_nrb init [...]- Initialize a config file in the project directory -
s1_nrb run_config -c /path/to/config.ini- Start a process by specifying a config file. Equivalent to currents1_nrb -cusage -
s1_nrb run [...]- Start a process by specifying all necessary parameters using flags - #80 - Move all notes from config file into separate text file?
Keep pre-processed GRD files for reuse
PR #73 introduced a mechanism to pre-process neighboring GRD scenes to use them for spatial buffering of the target scene (mosaicing and re-subsetting). This way, the individual GRDs overlap and can seamlessly be mosaiced after geocoding. See S1_NRB.snap.pre and S1_NRB.snap.grd_buffer. Currently, a scene's temporary processing directory is deleted after processing. However, the result of the preprocessing step might still be needed for processing its neighbors. The result of function S1_NRB.snap.pre should be kept so that it can be used for processing neighboring scenes.
Error reading temporary VRT file
As reported in #47:
[S1B_IW_SLC__1SDV_20200601T170735_20200601T170801_021843_029753_DFD0_tmp2.xml] failed with return code 1
[2022-07-07 15:24:08,619] [ ERROR] [ NRB] -- ['/codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170709_20200601T170737_021843_029753_7199.SAFE', '/codede/Sentinel-1/SAR/SLC/2020/06/01/S1B_IW_SLC__1SDV_20200601T170735_20200601T170801_021843_029753_DFD0.SAFE'] [32632] -- Error reading file '/tmp/spatialist/tmp4_j3cs_v.vrt': failed to load external entity "/tmp/spatialist/tmp4_j3cs_v.vrt"
Traceback (most recent call last):
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/processor.py", line 219, in main
msg = nrb.format(config=config, scenes=scenes, datadir=config['rtc_dir'], outdir=outdir,
File "/opt/anaconda3/envs/nrb_env/lib/python3.10/site-packages/S1_NRB/nrb.py", line 175, in format
tree = etree.parse(source)
File "src/lxml/etree.pyx", line 3538, in lxml.etree.parse
File "src/lxml/parser.pxi", line 1876, in lxml.etree._parseDocument
File "src/lxml/parser.pxi", line 1902, in lxml.etree._parseDocumentFromURL
File "src/lxml/parser.pxi", line 1805, in lxml.etree._parseDocFromFile
File "src/lxml/parser.pxi", line 1177, in lxml.etree._BaseParser._parseDocFromFile
File "src/lxml/parser.pxi", line 615, in lxml.etree._ParserContext._handleParseResultDoc
File "src/lxml/parser.pxi", line 725, in lxml.etree._handleParseResult
File "src/lxml/parser.pxi", line 652, in lxml.etree._raiseParseError
OSError: Error reading file '/tmp/spatialist/tmp4_j3cs_v.vrt': failed to load external entity "/tmp/spatialist/tmp4_j3cs_v.vrt"Relevant lines of code:
https://github.com/SAR-ARD/S1_NRB/blob/d58048efe08d3a64a3bdfcb19c15472d2bb4c8f5/S1_NRB/nrb.py#L160-L175
inability to process scenes crossing the antimeridian
revise orbit direction information
The manifest.safe file of a scene may contain wrong orbit direction information (ascending/descending) if the data take crosses the poles. This is because the orbit direction of the start of the data take is written to all scenes.
Example scene: S1B_EW_GRDM_1SDH_20210111T143749_20210111T143849_025108_02FD24_6654
This can be adjusted using the startTimeANX and the orbital period and should be done for the NRB product.
outsource STAC metadata generation
Currently S1_NRB creates all STAC metadata iteself. Eventually, it would be good to use a central external package for this.
See for example https://github.com/stactools-packages/sentinel1.
Stripes in Local Incidence Angle and Gamma-Sigma-Ratio when processing with COP-DEM EEA-10
Vertical stripes might occur in the annotation layers -li.tif (Local Incident Angle) and -gs.tif (Gamma-Sigma-Ratio) after processing with the Copernicus 10m EEA DEM.
The example below shows the Local Incident Angle of the RTC output:
This problem has already been reported in regard to the COP-DEM (Global 30m) auto-downloaded by SNAP:
https://forum.step.esa.int/t/stripes-in-incidence-angle-after-terrain-correction/32164
It is possible that this issue has specifically been fixed for the COP-DEM auto-downloaded by SNAP, but not for COP-DEM tiles that have been downloaded from other sources and used as external DEMs in SNAP. We use the latter approach with COP-DEM tiles downloaded from the official data repository Panda.
Software information:
S1_NRB: 0.4.3.dev56+gddc1970
snap-core: 8.0.9 | 202112101916
snap-s1tbx: 8.0.6 | 202202100514
python: 3.9.13 | packaged by conda-forge | (main, May 27 2022, 16:56:21)
[GCC 10.3.0]
python-pyroSAR: 0.17.0
python-spatialist: 0.11.0
python-GDAL: 3.5.0
gdal_threads = 4
output look direction image
The CEOS ARD Ocean Radar Backscatter specification defines a new target per-pixel metadata layer.
"It is representing the planar angle between north and each range direction. It is not constant in range, especially near poles. File format specifications/ contents provided in metadata:
- Sample Type [Height]
- Data Format
- Data Type
- Byte Order
- Bits per sample"
Eventually the processor should be able output this layer.
VRTs as STAC assets
Currently only the COG files are registered as STAC assets in the metadata. It would be great if the VRT files (for log scaling and sigma nought computation) could also be listed here and further be utilized with e.g. xarray.
@maawoo do you know whether this is generally possible?
stripmap thermal noise removal
Due to a bug in SNAP it is currently not possible to remove thermal noise of stripmap images and create the noise power images. The bug has been fixed and the new version SNAP 9 is soon to be released. Once this is done, the processor can activate the noise removal.
See here for details: STEP-32688, SITBX-911
inserting GRD and SLC scenes into the same database can wrongly trigger `check_acquisition_completeness`
See johntruckenbrodt/pyroSAR#251
In the example, the scene S1B_IW_SLC__1SDV_20211114T190431_20211114T190501_029588_0387F4_83FA.zip is not registered regularly into the database, which then results in check_acquisition_completeness raising an error because of a missing predecessor scene.
scene search geometry refinement
The processor currently offers two options for scene selection. From an SQLite database via pyroSAR or via STAC. The former is inaccurate because the database only stores the bounding box and not the actual geometry. A PR has already been opened for this (johntruckenbrodt/pyroSAR#185) and once this has been intergrated it should be used here as well.
delete preprocessed GRD products
The recently introduced GRD buffering mechanism (#73) requires preprocessing of up to two neighboring scenes of the target scene. The preprocessed neighbors are kept after processing and with the closing of #75 in #85 the preprocessed product of the target scene is kept as well so that all can be reused for processing other scenes.
Once all neighbors have been fully processed, the preprocessed product of the target scene should be deleted as well. A mechanism needs to be implemented to control this.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.