Chambord flooding: An update to "Mapping flooded areas using Sentinel-1 in Google Earth Engine" from Simon

Short after working with Simon on the script for the  article about the mapping of flooded areas, I wanted to be sure that our short script was realistic. I had some time to loose at the airport, so, after finding a wifi connection, I looked for pictures of the flooded areas of the north of France. I found some impressive pictures of the damages like the hippodrome of Mesnil Le Roy and surrounding places, but the most stunning one was surely this aerial view of Chambord.

Francis the 1st was the king of France during the first part of the XVI century. After winning the battle of Marignano, he decided to build a castle to its own glory. The castle is actually located 5 km south of the Loire river in between the cities of Blois and Orleans. The small Cosson river also crosses the park as can been seen on the aerial view. The Cosson overflowed at the end of May 2016 causing damages to the castle estimated in between 0.5 and 1 million euros.

After doing some slight adjustment to the original script, I exported the result from Earth Engine as a Geotiff file and encapsultated it into a KMZ file to load into Google Earth. Some people had already prepared a 3D model of the castle, so it was quite easy to create this  3D view.

Well, I'm really sorry for King Francis, but it seems our first guess of mapping flooded areas was not bad at all.

Mapping the Glacier Bay landslide using Sentinel-1 and Sentinel-2

Dave Petley wrote a nice article in the AGU's Landslide blog about a massive landslide in Glacier Bay, Alaska. This huge avalanche of debris was spotted by a local pilot Paul Swanstrom on June 28. When Paul was above it, "dust was still flying". Later, based on earthquake records in Alaska, the experts figured out that it probably happened at 8:21 am on the same day.

Photo of the the Glacier Bay landslide in Alaska by Paul Swanstrom - MountainFlyingService (click on the image to see the Facebook photo album)


Continue reading

Mapping flooded areas using Sentinel-1 in Google Earth Engine

Exceptional rainfall in May caused heavy flooding in the Paris region. Newspapers and TVs reported that the Seine flood forced the Louvre staff to move away from rising waters the art pieces that were stored in their cellar. But they did not tell you that about 50 km east of the Louvre museum, the flood of the Grand Morin river in Coulommiers also inundated the cellar of my parents-in-law. I'm really concerned about this cellar because I care about my parents-in-law of course, and also because I have let some of my bottles of wine in their cellar. Continue reading

Réfléchissez deux fois avant d'utiliser Google Earth Engine

=> L'une des tendances que l'on pouvait observer au Living Planet Symposium 2016, est l'utilisation croissante de Google Earth Engine. Pour ceux qui ne connaissent pas encore, Google met à disposition des utilisateurs de données de télédétection une plate-forme avec grosse puissance de calcul, bibliothèques et l'accès aux  données ouvertes, dont celles de LANDSAT et des Sentinel,  gratuitement tant qu'on ne dépasse pas certaines limites de stockage de données.  Google en retire une connaissance  des besoins des utilisateurs et des traitements et applications qu'ils développent, et améliore son image de marque (du "green washing")


Je vais répéter ici ce qu'à dit Jordi au Living Planet Symposium et ce qu'il a également expliqué dans son blog : l'utilisation de cette plate-forme est risquée et dangereuse.

Si vous travaillez sur GEE, sachez que :

  • vous n'avez pas les données
  • vous n'avez pas les machines
  • vous n'avez pas les codes

Les travaux que vous développeriez sur cette plate-forme ne pourraient donc pas être répétés ailleurs. Non seulement vous fourniriez donc un tas d'informations à Google, mais en plus, vous ne pouvez plus quitter GEE sans devoir reprendre vos travaux à zéro.

Mauvais scénarios

Voici quelques scénarios tout à fait plausibles mais non moins désagréables :

- google retire le service (c'est arrivé souvent à de nombreux services proposés par google): celà aurait à peu près le même effet qu'un incendie dans votre laboratoire (pendant l'absence du personnel). Plus de données, plus de machines, plus de codes qui tournent, on repart à zéro. Les clauses d'utilisation permettent tout à fait à Google d'arrêter leur service unilatéralement :

7.4 Termination for Convenience. Customer may stop using the Services at any time with or without notice. Customer may terminate this Agreement for its convenience at any time on prior written notice and upon termination, must cease use of the applicable Services. Google may terminate this Agreement for its convenience at any time without liability to Customer.

- google rend le service payant ou le vend à un autre industriel (c'est déjà arrivé aussi): vous devez donc payer cher pour continuer à l'utiliser, ou tout redévelopper chez vous.

- google modifie ses bibliothèques : vos chaînes ne donnent plus les mêmes résultats et vous devez en refaire toute la validation.

Alternatives ?

Ceci dit, le succès de la plate-forme montre qu'elle correspond à un besoin. C'est vrai qu'il est parfois plus long de télécharger la donnée que de la traiter et qu'un traitement à proximité des données permettrait de gagner beaucoup de temps. Mais il nous faudrait des plate-formes basées sur l'utilisation de logiciels open source, que l'on pourrait aussi faire tourner sur ses propres machines. Il est vrai qu'à part GEE, nous sommes plutôt démunis en Europe, à ma connaissance, malgré l'existence de nombreux démonstrateurs publics et moins ambitieux(PEPS, TEP, MEP), ou semi privés, mais largement financés par le public (Helix Nebula, SparkInData...). Pour ma part, je ne vois qu'un organisme public, ou une fédération d'organismes publics qui permettraient de monter une plate-forme libre du niveau de celle de Google, mais cette opinion, que certains qualifieront de passéiste et rétrograde, et qui manque certainement d'imagination, n'engage que moi.

Ceci dit, il y a les exemples pas tout à fait passéistes et rétrogrades du datacube australien, ou de la plate-forme NEX de la NASA.

Mon inventaire des plate-formes disponibles présente probablement des lacunes, n'hésitez pas à nous les signaler en laissant des commentaires..


Some news about Sentinel-2 from Living Planet Symposium


If I haven't posted for more than a week, it is because I have been participating to the Living Planet Symposium 2016 in Prague. With the preparation, travel, and participation to this crazy symposium. I say crazy because it is packed with about 3000 people, of which I know only about 300. When you want to go from a room to another, it takes as much as 20 minutes as you meet at least 3 or 4 of your colleagues and have a chat. But I do not need to tell you, as very likely, you were there too !

One of the 6 to 8 rooms, packed with people at the same time


The good news is that I have had access to a lot of information. I will start by some news about Sentinel-2 of course. Some of these news are not good.

  • The launch of Sentinel-2B has been postponed by to 2017, probably between March and June, due to a delay with the Rockot launcher. This is very annoying as accounting with the time needed for the commissioning phase, it means we will only rely on a 10 days repetitivity during modt of 2017.
  • The availability of Sentinel-2 ortho-rectified data with ground control points has also been postponed to the end of 2016, while initially it was planned in June. ESA says it is due to the fact that the global reference images (GRI) are not ready yet worldwide. We thus will have to cope with registration errors of about 1 pixel within the same orbit and 2 pixels when comparing data from 2 orbits. ESA had announced last year that they would introduce the reference data per continents starting by Europe, but it seems they changed their minds. Still I was told that the GRI for Europe and Australia are available or will be very soon, so why not starting a prodution of ortho-rectified data on those continents ?
  • ESA is also going to change and shorten the very long names of their products and start to distribute data tile wise. Of course, this is good news as the choices made before were not convenient, and it is better correcting it now, as the data backlog is short, but it means everyone will have to change his software. This might delay several productions downstream ESA ground segment.
  • ESA has published a new version of Sen2cor, which is said to seriously enhance the scene classification which was really bad in the previous version, especially for its cloud and cloud shadows mask. I will test it of course, as soon as I find some time.


This image background image is a monthly synthesis of Sentinel-2 images of august 2016, covering the whole Czech Republic. It was processed by MACCS to level 2A  and then to level 3A by the synthesis method we developed at CESBIO and implemented within Sen2Agri package. The overlayed landcover map itself was generated by GISAT in the Czech Republic based mainly on Sentinel-1 data, as Sentinel-2 data last summer were still quite scarce. This poster was shown on the 10x10m advert on the congress centre, alternating with a nice bikini (sorry, I only have the Sentinel image !)


I have been very positively surprised by how our user community has started using the time series, instead of using images only. It is clear we have entered a new chapter of remote sensing history on the application side, with much more robust results. The case studies based on one image have completely disappeared on the presentations, even if they are still present on the posters. Sentinel-1 examples were impressive and joint uses of both Sentinels 1 & 2 are rising. As the recently launched Sentinel-3A seems to be working well, it is clear ESA has set up a great system Europe can be proud of. And on top of that, ESA really know how to organise a symposium !


Radar time series


Thuy le Toan, Thi-Hoa Phan and Alexandre Bouvet from CESBIO just released a nice result on ESA website obtained with time series of Sentinel- 1A images.


On this very cloudy region, the C band radar Sentinel-1A allows to monitor the growth stages of rice, and allow to detect a large reduction of the surface of rice crops at the end of 2015, 2015, in the Mekong delta region. This region suffered from a severe drought related to the El Niño. This news gives us the opportunity to recall that Sentinel familly will receive a new member, Sentinel-1B, to be launched on April the 22nd.

It may be also an opportunity to great new authors on this blog, for instance to explain us how this nice result was obtained ?

Séries temporelles au radar


Thuy le Toan, Thi-Hoa Phan et Alexandre Bouvet du CESBIO viennent de publier sur le site de l'ESA un beau résultat obtenu avec des séries temporelles d'images Sentinel...1-A (pour une fois sur ce blog, ce n'est pas Sentinel-2)



Sur cette région très nuageuse, Sentinel-1A permet de bien suivre les stades de croissance du riz, et a permis de détecter une forte diminution des cultures de riz sur le delta du Mekong, sur la fin de l'année 2015 marquée par une grande sécheresse liée au phénomène El Niño. Ce communiqué est l'occasion de vous rappeler que la famille des Sentinel va encore s'agrandir avec le lancement du satellite Sentinel-1B, ce vendredi 22 avril.

C'est aussi peut-être l'occasion d’accueillir de nouveaux auteurs sur ce blog, par exemple pour nous expliquer comment ce résultat a été obtenu ?