Bridging the gap between Planets Advanced EO Imaging Platform and ESA-CSCDA
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Title of Series | ||
| Number of Parts | 295 | |
| Author | ||
| Contributors | ||
| License | CC Attribution 3.0 Germany: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
| Identifiers | 10.5446/43336 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
| |
| Keywords |
FOSS4G Bucharest 2019247 / 295
15
20
28
32
37
38
39
40
41
42
43
44
46
48
52
54
57
69
72
75
83
85
87
88
101
103
105
106
108
111
114
119
122
123
126
129
130
131
132
137
139
140
141
142
143
144
147
148
149
155
157
159
163
166
170
171
179
189
191
192
193
194
195
196
197
202
207
212
213
214
215
216
231
235
251
252
263
287
00:18
Computing platformMedical imagingGroup actionCASE <Informatik>Lecture/Conference
00:32
Integrated development environmentComputing platformLevel (video gaming)Medical imagingLecture/Conference
00:48
Computing platformMedical imagingGoodness of fitIntegrated development environmentVideo game consoleSatelliteProduct (business)SpacetimeTerm (mathematics)Internet service provider
01:19
SatelliteSpacetimeImage resolutionSatelliteInternet service providerWebsiteVideo game consolePresentation of a groupRow (database)
02:13
RotationSatelliteVideoconferencingLevel (video gaming)Sound effectSurfaceOffice suiteDataflowPoint (geometry)RotationDifferent (Kate Ryan album)Product (business)SatellitePhysical systemImage resolution
03:15
Computer hardwareInheritance (object-oriented programming)Computer programMountain passType theorySource codeAngular resolutionField (computer science)Sign (mathematics)ExistenceSigma-algebraPower (physics)CASE <Informatik>InformationWater vaporGoodness of fitMedical imagingVirtual machineSatelliteMoment (mathematics)View (database)Operator (mathematics)Software testingDivisorPlanningMultiplication signDataflowPresentation of a groupPoint (geometry)UsabilityMetreLink (knot theory)Integrated development environmentState observerCartesian coordinate systemWeb pageFreewareProcess (computing)Complement systemFeld <Mathematik>Point cloud1 (number)Mountain passAnalytic continuationEndliche ModelltheorieComputer animation
05:51
Personal digital assistantField (computer science)Temporal logicSubstitute goodImage resolutionRadiometryResultantMultiplication signPhysical systemTouchscreenSoftware testingFrequencyComputer animation
06:14
Data managementTexture mappingService (economics)Data recoveryImage resolutionSet (mathematics)Level (video gaming)Source codeSatelliteDifferent (Kate Ryan album)MultiplicationIntegrated development environmentComputing platformProcess (computing)Computer-generated imageryPhotographic mosaicWorld Wide Web ConsortiumGraphical user interfaceBridging (networking)Data storage deviceEwe languagePhysical systemInformation retrievalDatabaseOrder (biology)EmailModule (mathematics)outputProduct (business)Traffic reportingExplosionZirkulation <Strömungsmechanik>BriefträgerproblemData structureFile Transfer ProtocolTraffic reportingPlanningTask (computing)Presentation of a groupIntegrated development environmentInheritance (object-oriented programming)Medical imagingState of matterService (economics)Physical systemSpacetimeoutputData storage deviceComputing platformWebsitePower (physics)Multiplication signInternet service providerFunction (mathematics)Connected spaceOrder (biology)Well-formed formulaProjective planeDatabaseState observerProcess (computing)Flow separationDenial-of-service attackGame theoryInformation retrievalEmailProduct (business)Computer programmingSatelliteComputer configurationInterface (computing)DataflowTerm (mathematics)DemosceneFile archiverRight angleCentralizer and normalizerData managementEndliche ModelltheorieCASE <Informatik>Mountain passConnectivity (graph theory)Office suiteModule (mathematics)Computer fileSoftware developerData structureDigital photographyVirtual machineFrame problemRow (database)File formatUsabilityZirkulation <Strömungsmechanik>DeciphermentMappingConformal mapPhase transitionCartesian coordinate systemFile Transfer ProtocolAnalytic setScatteringMetadataLink (knot theory)Computer animation
14:58
Mountain passCursor (computers)Integrated development environmentOrder (biology)EmailComputer programmingCartesian coordinate systemParallel portCodeWebsiteBitFrame problemResultantFormal grammarState of matterComputer animation
16:09
Computer programmingRight angleSource codeArtificial lifeProcedural programmingInformation securityProjective planeService (economics)UsabilityPhysical systemFrame problemData warehouseInterface (computing)Mapping
Transcript: English(auto-generated)
00:07
OK. Hello, everybody. Welcome to the next session. We will be having some interesting talks, two from Planet and one from EoX. Yeah, each talk will have 20 minutes.
00:22
Then you will have the chance to ask questions for five minutes. And yeah, I would suggest we can start now with Rene Grisbach and Holger Jäckle from Planet, giving us an introduction on bridging the gap between the Planet Advanced EoImaging platform
00:41
and the ESA environment. Yeah, good afternoon. Welcome here to this session. So my name is Rene. I'm working for Planet as a pre-sales engineer. And I'm very interested in giving you a deeper insight
01:03
into the technical solutions we provide. And today we want to talk about how we can bridge the gap between the advanced Planet data environment, which is actually really advanced, and the European Space Agency environment for our data.
01:20
So just as a short introduction, what is Planet and Planet constellations when we are a data provider. We have three constellations of satellites in space. One is the old RapidEye constellation of five satellites. Then a big constellation of more than 120 satellites,
01:41
the so-called Planet Scope constellation. It says 120 plus because it's constantly changing. So we are launching new satellites to complete the fleet of DAF satellites. Sometimes we're losing one or two satellites and have to replace them. That's why, so it need to be updated always
02:01
before any presentation. And beside of that, we have 15 SkySat satellites, which you may know from the skybox side. So it's a very high resolution sensor with up to 70 centimeter resolution. So just as an explanation how the things work, I brought a little video animation
02:21
that can explain it better than I do. So I will be quiet for a while. So these systems are complimentary to each other. So while the Planet DAF satellites are scanning the earth from east to west using the earth rotation,
02:43
we use the Planet Sky, the SkySat satellites for pointed target, means targets of special interest where we need to have higher resolution to understand what's happened on the ground.
03:00
So all of these data are offered as geospatial products in different levels of processing up to surface reflectance, corrected data and autorectified data products. So, but actually we wanted to talk about the link between the ESA environment and the planet plans.
03:22
And we see a huge complementing factor in that one. So if you see the Sentinel, let's say the big major earth observation missions worldwide, the Sentinel and Landsat missions. So, and I put down how we see ourselves
03:46
in that environment. So you see, we are constantly developing our satellite power. So there are new builds. So you see the build 13.8 is the current one. And we have a plan to have a 14th,
04:01
a new model for that in place to provide the continuity on data supply. I will stop you on the details of the satellites because my colleague Robert will have a presentation later on and can give you a lot more information about that. So where do we see the benefits of the complimentary use together with the earth observation mission
04:22
from the ESA in Europe? Of course, having a Sentinel satellite is a great thing for everybody. It's free data. It's really great data from quality and from the application point of view. But in some cases, the Sentinel cannot do the job in some cases. And one of the examples for it
04:40
is the monitoring of agricultural resources. It's a big topic in Europe at the moment. There, the local or national paying agency want to check the compliance with good agricultural practices by satellite monitoring. Really in a wall to wall monitoring the satellite imagery.
05:01
And for that they want to switch from the spot checks to a monitoring approach and plan to have a data collection all over Europe twice per week. So two images per week. And that's very ambitious, I would say, even for the Sentinel mission. And there are two gaps which cannot be fulfilled
05:22
by the Sentinel satellite. The satellite ones is if we have cloud on the second day or even in both imaging dates in a week then the paying agency would not have no data. And the idea is to replace or substitute the Sentinel data with planet data. And in cases where the agricultural fields are very small
05:43
and cannot be really assessed by a 10 by 10 meter Sentinel pixel, then also the assessment should be done by planet data. So and that's a short example for a technical test which we showed. The system itself selects the right data
06:02
over a period of time. You see that in the ground timeline. And can provide some qualitative assessment results on a graphical screen. So another big example is the use for the Copernicus emergency mission.
06:20
So there's a Copernicus emergency mapping service in place which of course has a need in any data which is available if something happens somewhere in the world so then somebody needs the data. And we reached an early agreement with ESA that our data can be used for these emergency cases in the way as it is.
06:40
And the way as it is is the planet format. So it's not really compatible to the requirements from the European Space Agency. But nevertheless, at the same times, we understand that for the complementary supply of data, we need to have an equally powerful environment as ESA has.
07:03
So what is available on planet site, so we also have a really powerful image platform which consists of several input imagery. So planet scope, rapidized, as I mentioned, plus the lens and sentinel images. There are processing engines involved storages
07:20
and even a container for analytical applications. But what it misses is the output. And so our data are in first base not in SPIRE Conform yet. So we provide other data packages
07:41
than the ESA would require for the environment including some reports. And then we need to bridge the API solutions between them. And another thing is that ESA requires a physical storage of the data in their environment which is actually contradicting the platform approach.
08:00
And with that, I hand over to Holger. Holger is our colleague from the GAF in Germany. And GAF helps us in implementing these interface between planet and the ESA environment. Okay. Yeah, this adapter system that we built together
08:23
with planet for bridging this gap between the ESA requirements for their interface and the planet API that's already there. We built that for three scenarios that are defined by ESA.
08:42
That's the first scenario, the scenario six is the emergency rest satellite tasking scenario where the tasking request comes from ESA and is processed by the satellite data provider. And the scenario seven is a crisis monitoring
09:00
where this is continuously processed. So when an emergency like a flood is lasting for a longer time, for several weeks for example, then the issue of monitoring is a very specific scenario. And the scenario eight is the retrieval from archive.
09:20
And for that scenario, I want to give you an example how the workflow between the ESA interface, the adapter system that we built together with planet and the planet API, how this works. So in this scenario eight ordering from archive,
09:43
there is one option ordering via email. So the ESA writes an email in that case to the planet customer support where they specify. So this is not a free email. This is an structured email where the ESA defines
10:03
what scenes they want to have. This email cannot be automatically processed. So the planet customer support has to read this email and do an input into our input module
10:20
of the adapter system here in the middle. The input module then forwards this request as an order to our tasking management component, which is a central component in our adapter system. And this order tasking management then creates an order
10:43
using the planet orders v2 API. Then when you provide an order there for the planet orders v2 API, you get returned an order ID and that is stored in the database. And that is the first step in the ordering process.
11:06
There is an alternative workflow for this step, which we will implement in phase two of this project, which is not ordering by email, but ordering via an automated interface, an HMA interface.
11:22
That's basically the same. Then there is an interface that's defined by ESA and provided also by our adapter system that will basically create the same add order for scenario eight request that the input module would create.
11:44
So when we have submitted the order to the planet API, the planet API will deliver those archive products. They will deliver this products in our case to a Google bucket, to a storage bucket,
12:02
which then will issue a notification to our adapter system again, to the order and tasking management. And now with this product that comes from the planet API, we have to build a Copernicus product package. So we have to create a folder structure,
12:22
download the product from the Google bucket, and then create two files. The first file is the Inspire metadata XML file that will be created by our reporting module. The second file that has to be added
12:41
is a circulation report, and those both files are created by the reporting module, then added to this folder structure, and then created a TAR file that's in the end the Copernicus product package. And in the last step of this process, then this CPP, this Copernicus product package,
13:04
has to be disseminated. That means it has to be uploaded to another storage bucket that's also published as an FTP server, and the Copernicus service provider who wants to have those images is then notified by email
13:23
and can then download those CPPs by FTP, for example. Also, for the ISA, a delivery report is created, and the file is also uploaded to the ISA FTP server. ISA is notified by email, and then the process is basically finished, and we can update the status in the database
13:43
that this product is now delivered to ISA. Okay. Thank you, Hooker. So just as a conclusion to that one, just writing up the presentation. So we have data which need to be complimented
14:02
to the ISA, Copernicus Earth Observation missions, and we need to have a connection between the environments to a powerful data supply. We identified the gaps between them and working on a solution. And some of the necessary interfaces are available soon, so we think about a month's time or two months' timeframe.
14:23
But already today, ISA agreed to include the planet and scatter data in the third-party mission program. The new name is EarthNet for that. And I invite you, as developers and so on, to send in your applications for data supply, and leave the link to the site for ISA here.
14:46
And with that, I want to thank you for your attention and ask for a question. Thank you. Yeah, thank you very much for this interesting talk.
15:00
It's great to see the public and the private sector working together to produce great products. A question from my side. What are the requirements in order to get a dataset from the ISA third-party missions? So the ISA third-party mission program, or the new name EarthNet, is a data supply program
15:25
where ISA pays for the data you are requiring. What you need is to go to this website and hand in a formal application that describes a bit your need for data, why you need data, what's the purpose, what do you want to develop, and so on.
15:41
ISA then decides about the amount of data they can assign to you. And with that assignment, we get a parallel email. For that one, we can supply in that frame this data. You can even select the data yourself. We just give you access to the planet environment and set the download code to the one which ISA gave,
16:02
and you are free to choose the data wherever you want. Okay, thanks. Any questions from the audience?
16:26
So for scientific purposes, it would be this EarthNet program. That's a support for scientific usage. But ISA also provides data for commercial purposes. That would be the data warehouse project or Copernicus data warehouse supply.
16:40
And as soon as the adapter system interface will be available, planet data can also be purchased via the ISA thing. I don't know really about the procedure behind that, but it will be handled as any other data source in the Copernicus frame. Okay, I think we got a question here as well.
17:11
So yes, we offered the same thing for the security. Yep, so the question was, if data can be supplied already now for the CMS, for the emergency mapping service,
17:21
what about the security services in the Copernicus program? So we offered the same for the security program and Frontex and the Zat Center are the typical customers for that. They have access to the data and they got the right to download this, but unfortunately they did not use it.
17:40
So it was free to them to choose, but so far they did not use it. Okay, over there, there was something. Peter, no question, okay. I missed it. Any more questions?
18:01
Okay, then thank you very much for the talk. Thank you.
Recommendations
Series of 18 media