wcst_import - Sentinel 1 custom recipe should filter invalid lat / long bounds from input files

[Bang Pham Huu]

As Sentinel 1 is non-georeferenced data, it must use gdalwarp to reproject to CRS, typically is EPSG:4326.

In this case, some scenes can have invalid geo bounding boxes for Long axis, e.g:

ubuntu@ecs-parsec1:/tmp$ gdalwarp -tps /data/geo/Sentinel-1/grd/2020-q2/s1b-ew-grd-hh-20200401t074004-20200401t074046-020947-027bbc-001_raw.vrt test.tif
Creating output file that is 937756P x 8348L.
Processing input file /data/geo/Sentinel-1/grd/2020-q2/s1b-ew-grd-hh-20200401t074004-20200401t074046-020947-027bbc-001_raw.vrt.

ubuntu@ecs-parsec1:/tmp$ gdalinfo test.tif
Driver: GTiff/GeoTIFF
Files: test.tif
Size is 937756, 8348
Coordinate System is `'
Origin = (-229.531335575609774,-62.944262398844330)
Pixel Size = (0.000491317991980,-0.000491317991980)
Image Structure Metadata:
  INTERLEAVE=BAND
Corner Coordinates:
Upper Left  (    -229.531,     -62.944) 
Lower Left  (    -229.531,     -67.046) 
Upper Right (     231.205,     -62.944) 
Lower Right (     231.205,     -67.046) 
Center      (   0.8368619, -64.9950237) 

Then, wcst_import cannot import these invalid warped files, otherwise, it will create coverages with invalid bounds (long is not within [-180:180], lat is not within [-90:90]).

In this case, wcst_import should have an warning that these files cannot be imported.