Scenario (**NOT REAL DATA**) of deformations for the today M 7.7, #Myanmar #earthquake (up to 1 m on surface), based on #USGS finite-source results. Here also the #Sentinel1 acquisition schedule for #InSAR results terremoti.ingv.it/en/finites… with @antandre71

Details about the "full resolution" algorithm can be found in our publication: doi.org/10.1016/j.rse.2019.1… Contributors to the content of this post: @maferp_13 @CrisTolomei @antandre71 @NikosSvigkas @FraxInSAR @dott109 @claudiodeluca @CnrIrea

Scenario (**NOT REAL DATA**) of deformations for the July 19, M 7.1, #Chile #earthquake (very deep: ~120 Km) Predicted signal not very reliable and at the edge of InSAR sensitivity. Let's wait and see what #Sentinel1 will do. terremoti.ingv.it/en/finites… with @antandre71

Improved source model of the Jan 7, M 7.1 #TibetEarthquake from #InSAR, after asc+dsc #Sentinel1 availability. Data and model here (#INGV Finite Source catalog): terremoti.ingv.it/en/finites… @antandre71 @maferp_13

5 days to the first #Sentinel1 image suitable for #InSAR for the M 7.4 #EarthquakeTaiwan. The scenario (simulated fringes) based on the USGS finite fault shows significant displacements, possibly increased by large aftershocks, up to M 6.4. With @antandre71 and @maferp_13

First #Sentinel1 SAR data and #InSAR results for the Jan. 22, M 7.0 #China #earthquake should arrive in two days (Jan 25). Meanwhile, you could give a look to what we expect in terms of fringes, according to the scenarios, here: terremoti.ingv.it/en/finites… with @antandre71

New and final update of the #MoroccoEarthquake source model, after the availability of 4 #InSAR datasets from @EPOSeu. Data and sources can be found here: terremoti.ingv.it/en/finites… (with @antandre71 @maferp_13 @dott109 @FraxInSAR)🧵

Source model of the M 6.7 #moroccoearthquake derived from inversion of #InSAR data (see cited tweet). More info, model and sampled InSAR data for download (shapefile) here: terremoti.ingv.it/en/finites… ("finite source" tab) With @antandre71 @maferp_13 @FraxInSAR @dott109

Here the scenario based on the GCMT focal mechanism and the Leonard (2010) scaling factors.

Automatic displacement scenario, expected #InSAR fringes and Sentinel-1 orbits & dates for the February 6 M 7.9 #Turkey #earthquake, based on USGS slip distribution. Post-event images acquired 12 days after the pre-event. With @antandre71 *** SCENARIOS ARE NOT REAL DATA ***

Slip model (automatic) of the Nov. 23, Mwp 6.1 #Deprem #earthquake (#Turkey) from #InSAR inversion. #Sentinel1 data from @CopernicusEU, processed at @CnrIrea by @maferp_13, @FraxInSAR, @dott109, @claudiodeluca With @antandre71.

Update - Automatic displacement scenario, expected #InSAR fringes and Sentinel-1 orbits & dates for the Sept., 19, Mw 7.6 #Mexico #earthquake, based on USGS slip distribution (thanks @dara_berg_ ) With @antandre71 *** SCENARIOS ARE NOT REAL DATA ***

Automatic and preliminary displacement scenarios, expected #InSAR fringes and Sentinel-1 orbits & dates for the Sept., 19, Mw 7.6 #Mexico #earthquake, based on USGS focal mechanism. With @antandre71 *** SCENARIOS ARE NOT REAL DATA ***

Automatic displacement scenarios, expected #InSAR fringes and Sentinel-1 orbits & dates for the Sept., 5, Mw 6.7 #Sichuan (#China) #earthquake, based on USGS focal mechanism. With @antandre71 *** SCENARIOS ARE NOT REAL DATA ***

First slip model of the Jul. 27, M 7.0 #Philippine #earthquake, from the inversion of @CopernicusEU #Sentinel #InSAR data processed at @CnrIrea (xitter.cf/maferp_13/status/15547…). With @maferp_13 @FraxInSAR @dott109 @claudiodeluca, @antandre71

Automatic displacement scenarios, expected #InSAR fringes and Sentinel-1 orbits & dates for the July, 27 Mw 7.0 #Philippine #earthquake, based on USGS slip distribution. Waiting for InSAR data, hoping good coherence. With @antandre71 *** SCENARIOS ARE NOT REAL DATA ***

Automatic update of the #AfghanistanEarthquake model, based on the availability of an #InSAR descending track (xitter.cf/maferp_13/status/15427…). Thanks @maferp_13 @FraxInSAR @dott109 @claudiodeluca. With @antandre71.