Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ENH: [SAR] Don't use SNAP #2

Open
remi-braun opened this issue Jul 2, 2021 · 5 comments
Open

ENH: [SAR] Don't use SNAP #2

remi-braun opened this issue Jul 2, 2021 · 5 comments
Assignees
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@remi-braun
Copy link
Member

remi-braun commented Jul 2, 2021

Calibration

RADARSAT-2

Sentinel-1

https://sentinels.copernicus.eu/documents/247904/685163/S1-Radiometric-Calibration-V1.0.pdf/66e69a62-11ae-4160-916b-f2b97cb8a350?t=1432307754000

TerraSAR-X

COSMO Skymed

Terrain-Correction

RADARSAT-2

Use RPCs: https://gis.stackexchange.com/questions/303233/error-in-orthorectification-of-radarsat-2-scenes-with-gdal-and-rpc-dem-informa

Should be implementable like DIMAP orthorectification:

        kwargs = {"RPC_DEM": dem_path, "RPC_DEM_MISSING_VALUE": 0}
        # TODO:  add "refine_gcps" ? With which tolerance ? (ie. '-refine_gcps 500 1.9')
        #  (https://gdal.org/programs/gdalwarp.html#cmdoption-gdalwarp-refine_gcps)

        # Reproject
        # WARNING: may not give correct output resolution
        out_arr, dst_transform = warp.reproject(
            src_arr,
            rpcs=rpcs,
            src_crs=WGS84,
            dst_crs=self.crs(),
            resolution=self.resolution,
            src_nodata=0,
            dst_nodata=0,  # input data should be in integer
            num_threads=MAX_CORES,
            resampling=Resampling.bilinear,
            **kwargs,
        )

We just need to extract RPCs from product.xml

Sentinel-1

Use GCPS, retrievable with opening directly the .SAFE product

TerraSAR-X

Simply use TDX1_SAR__MGD_SE___SM_S_SRA_20201016T231611_20201016T231616.xml

COSMO Skymed

Use GCPS, retrievable with opening directly band from tyhe .h5 file: COSMO/CSKS4_DGM_B_HI_04_HH_RA_FF_20201008224042_20201008224049.h5://S01/SBI

LinearToFromdB

TODO

Despeckle

TODO

Specific S1

ThermalNoiseRemoval

TODO

Apply-Orbit-File

TODO

Remove Remove-GRD-Border-Noise

TODO

@remi-braun remi-braun added the enhancement New feature or request label Jul 2, 2021
@remi-braun remi-braun changed the title ENH: Do not geocode Sentinel-3 with SNAP ENH: Do not use SNAP Sep 8, 2021
@remi-braun remi-braun self-assigned this Sep 28, 2021
@remi-braun remi-braun changed the title ENH: Do not use SNAP ENH: [SAR] Do not use SNAP Sep 29, 2021
@remi-braun remi-braun added the 1.0 label Oct 7, 2021
@remi-braun
Copy link
Member Author

remi-braun commented Nov 29, 2021

1st step should be the Despeckling operation as:

  • it is already another graph
  • it is the same operation for every SAR sensor
  • it takes a lot of time for almost nothing

Look at findpeaks which have filters deriving from pyradar. Or maybe reimplement them ?

@remi-braun remi-braun removed the 1.0 label Mar 16, 2022
@remi-braun
Copy link
Member Author

Maybe look at sarsen :)

@Scartography
Copy link

Not ideal but freshly released: https://github.com/bopen/xarray-sentinel

@remi-braun
Copy link
Member Author

Thanks for the insight! 😄
I think sarsen is from the same team but a bit lower level, so I maybe easier to be used by EOReader.

This issue will be really hard to complete, especially if ESA will keep to add new SAR constellations at this rate 😅

@remi-braun remi-braun added the help wanted Extra attention is needed label Sep 13, 2022
@remi-braun
Copy link
Member Author

@remi-braun remi-braun changed the title ENH: [SAR] Do not use SNAP ENH: [SAR] Don't use SNAP Dec 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants