EUROCONTROL LARA - Presentation

Editor's Notes

• #2: Hello everyone let me introduce myself I’m Salvatore and I’m working in EC as trainee. I have been working on LARA project since my arrival two months ago. Today I’m going to talk to you what I have done and what I’m working on.
• #3: First of all I’d like to talk about Prismil Interface and LARA DB briefly and afterwards the going activities. Of course I didn’t developed Primal Interface and LARA DB but I have introduced improvement to them. Such as enhancements of Mission, Google Earth extension and create a new DB with PostGIS.
• #4: Let’s spend a couple of words about LARA Server. I’ll not go through its details. Because it’s not my subject and you know much betters then me too. But just to let you know that I worked with an External Interface that allowed me to have access to LARA dates.
• #5: So. this slide shows us the connection between LARA Server and Prismil Interface and how you could see there is an intermediate db that save all dates from LARA. It is useful to populate the intermediate db because we can use it in Prismil in order to generate the KPI.
• #6: Here we can see in more detail how it works. Firstly LARA Server connects to LARA db secondly it connects to Prismil Client and then Primil Client connects to Intermediate db after that there is a syn between LARA DB and Intermediate DB.
• #7: Let’s see now what I have done in this process so far. As you can see I worked with Mission entity. On the left side there is Prismil Interface DB and on the right one LARA DB. So, before connection there are some dates in LARA DB but not in Prismil Interface. When these two system are syc, some of the dates from LARA DB are imported into Prismil Interface. We can see the last dates thirteen are the same of the right.
• #12: Next step was to investigate for a new DB in LARA using PostGIS. PG is an open source software program that adds support for geographic objects to the PostgreSQL  object-relational database . It’s useful for us because it shows in an easy way which airspaces are disjointed, adjacent and overlapped. The advantage it’s to make the process automatic with a simple query and not manually as we currently do.
• #13: So, how can I create an airspace in PostGIS and Populate it? By running two simple queries we can create it and afterward we can use the normal Insert command to populate it. Here we can see that I only used four airspaces for my test on the left side. On the other side we can see the table created that contains four airspaces.
• #14: The first example is disjoint function if we want to know which airspaces are disjoints from EBTSA28A. We can only execute one query and the results looks like the table on the right so three airspaces are disjoints from EBTSA28A.
• #15: The second example is adjacent function if we want to know which airspaces are adjacent from EBTRAN2. We can only execute one query and the results looks like the table on the right so one airspaces adjacent from EBTRAN2.
• #16: The last example is Overlaps function if we want to know which airspaces are Overlaps from EBTRANA. We can only execute one query and the results looks like the table on the right so two airspaces are Overlaps from EBTRANA.
• #17: In my last task I used Google Earth in order to represent a CDRs in LARA into Google Earth. How you can see I used two CDRs from LARA UN858-SPY-LUTOM and UN858-LUTOM-TERLA and import them into Google Earth. It looks like that screenshot on the right.
• #18: In addition, I updated the Labels in the Layer Usage because before there were no values but just “null”. Now there is a label that shows the name.
• #20: ffsdfsd