Managing airport data with Open Source Software
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 | 156 | |
| Author | ||
| Contributors | ||
| License | CC Attribution 3.0 Unported: 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/68492 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
| |
| Keywords |
00:00
Streaming mediaComputer-assisted translationGeometrySoftwareOpen setOpen sourceData managementPresentation of a groupRow (database)InformationLecture/ConferenceComputer animation
00:34
Local GroupService (economics)Computer networkInformation securityControl flowOperator (mathematics)Operations support systemTotal S.A.SmoothingDifferent (Kate Ryan album)1 (number)Service (economics)Lecture/ConferenceComputer animation
01:22
InformationIntegrated development environmentIntegrated development environmentAreaComputer-assisted translationSoftwareOpen sourceClosed setSoftware developerRegulärer Ausdruck <Textverarbeitung>Strategy gameOperations support system
02:10
Core dumpChannel capacityOpen sourceBuildingSoftwareMountain passBarrelled spaceInformation securityTexture mappingConnected spaceLevel (video gaming)InformationAreaDifferent (Kate Ryan album)Web applicationOpen sourceField (computer science)SoftwarePresentation of a groupOpen setService (economics)Barrelled spaceUniform resource locatorZoom lensDiallyl disulfideMobile WebComputer animationLecture/Conference
04:35
Data storage deviceServer (computing)FingerprintIntegrated development environmentSelf-organizationUsabilityProcess modelingInformationWeb serviceOperator (mathematics)Server (computing)Regulator geneReading (process)Texture mappingDifferent (Kate Ryan album)GeometryComputer fileBitVector spaceIntegrated development environmentINTEGRALSet (mathematics)DatabaseInformationService (economics)Self-organizationMereologyVisualization (computer graphics)Medical imagingCartesian coordinate systemGoodness of fitText editorRule of inferenceProbability density functionField (computer science)MeasurementDatabasePhysical systemProcess (computing)Information securityMobile WebWeb applicationSystem administratorOperator (mathematics)Slide ruleSoftware maintenanceData qualityOrganic computingDrum memoryWeb pageDataflowEndliche ModelltheorieGame controllerState of matterAnalytic setComputer architectureTesselationMiniDiscComputer animationEngineering drawing
12:36
InformationWeb serviceOperator (mathematics)Process modelingOpen sourceCoroutineData integrityData storage deviceDatabaseMetadataFormal verificationIntegrated development environmentText editorAreaGeometryDirac equationCloud computingTexture mappingDatabaseData modelSoftware developerProduct (business)Revision controlLevel (video gaming)Insertion lossProjective planeRegulator geneDifferent (Kate Ryan album)DatabaseMappingInformationImage resolutionPlanningField (computer science)INTEGRALOpen sourceMetadataOperator (mathematics)CoroutineThresholding (image processing)Multiplication signIntegrated development environmentForm (programming)AreaCoordinate systemIdentifiabilityEndliche ModelltheorieMusical ensembleData storage deviceBitSet (mathematics)Game controllerImplementationGraphical user interfaceMeasurementMathematicsProbability density functionComputer-assisted translationDiallyl disulfideSoftware testingData managementRule of inferenceComputer animationProgram flowchartLecture/Conference
18:55
InformationWeb serviceOperator (mathematics)Process modelingRevision controlDifferent (Kate Ryan album)Texture mappingFile formatInternet service providerMusical ensembleInformationAreaIterationEndliche ModelltheorieView (database)Presentation of a groupDataflowLinked dataBitProjective planeInstance (computer science)Computer configurationState of matterInformation securityLatent heatServer (computing)Semantic WebLevel (video gaming)TangentError messageService (economics)BuildingSingle-precision floating-point format2 (number)Semantics (computer science)Lecture/ConferenceProgram flowchart
24:20
Least squaresComputer-assisted translationComputer animation
Transcript: English(auto-generated)
00:00
My name is Pek Kasaraghlan coming from GISPO and I'd like to give you a presentation about how we have developed it together with FINAVIA about the management of the airport data with FOSS4G. Unfortunately, FINAVIA people couldn't join here. Maybe GIS manager is following this online or checking the recordings later on.
00:25
If you have any questions about FINAVIA, I'm happy to pass your contact information or questions to them if you need it. So, FINAVIA for smooth travelling. It's a Finnish state-owned company who is operating about 20 different kind of airports in Finland.
00:44
The most southern one and the biggest one is Helsinki Vanta and I think quite many of you have passed from Helsinki to here in Tartu. And then Ivala is the most northern one. Helsinki airport is about 50 million passengers, over 50 million passengers per year.
01:05
They have about 19 different kind of airports in Finland and they have also a subsidiary AirPro which is taking care about different kind of aviation services in the airports in Helsinki and others.
01:24
In Finland, Avia and about the geospatial information, they want to maintain and develop the GIS data in all airports built environment. It's very strongly regulated operating environment. I will come later on to whether you can idea what's going on there.
01:44
They have a GIS strategy to guideline development of the activities and they are using both the open source and closed source softwares. Their aim is to develop from the CAD to the GIS and backwards so that's always the challenge with this kind of built environment area.
02:11
GISPro is founded in 2012, about 25 people. We develop and train and consult customers in Finland
02:23
and Sweden and we like to be also the advocate for the open source technologies and open data. So, passenger map. In this presentation I give you an idea about the land air, land side information which is like passenger map and then the air side.
02:45
The air side is where the aircraft is travelling. Well probably you never been in the air side. I mean of course in the aircraft but not really in the field because that's a really security and safety issue that passengers don't go in the air side.
03:01
But let's talk about passenger map first. So whenever you arrive in the airport you want to know where you park your car, how you pass the security clearance, before you of course if you have some packages you want to give it away and so on. How to see the information or how to find your location, you can use different kind of web apps. So this
03:28
is an example about the airport map and you can open up in your own browser or in your mobile devices. So it's a little bit slow because I have a very bad network connection. So you see different kind
03:43
of areas in the Helsinki airport. You can go to the selected area and then you can zoom in. And this is like first there's a second level which is a departing level and then you zoom in and you get more information. This is the arrival level in Helsinki and third level is the lobby level. I don't know if you want to go there.
04:10
So you can see all the services. If you go via Helsinki the Moomin shop is the first place to go. And then probably the Finnish people are there about Oakbarrow Irish pub, very full at 6 a.m. when they open up at 5.30.
04:28
And you can also see the drinking water facilities there. So this is very simple idea how the passengers can understand where are the services, different kind of services in the airport.
04:41
Not again. So the passenger map, the same data is in different kind of devices. So this was like desktop application web app but it works also on your mobile phone. But if you go to the airport and you see this kind of
05:00
service information desks, the same data is also there. So whenever they update the data it will go in all these kind of devices. So very basic image about the architecture. There's an airport data editor with good GIS here and storing all the information
05:24
to the post GIS database. And then we have a separate environment where we make a read only copy of the data. And then we have a geo server giving you APIs, WMS, WMTS and then vector files. And
05:41
then of course I show you about the passenger map which is mobile web and devices interface. But there's also other stakeholders who are using directly those APIs with their own systems. So if you go with your good GIS and probably find their WMS services, you can also include or use this data in your own desktop application.
06:10
Good GIS editing environment looks like this. Nothing very special. Only challenge is of course that you have a visualization in good GIS and we have a geo server where we make also the visualization and how to transform the visualization from the good
06:28
GIS to geo server. It's painful to everybody. I don't know when we can solve it. Not maybe in the future but we'll see. This is a very simple kind of environment.
06:44
I have been a little bit working with the passenger maps but mostly my experience is with the aeronautical data, the air side. We have been working with the Finnavi about five years plus and now I start
07:01
to understand how small is my know-how about the aeronautical data and manage of that. So about aviation for GIS nerds, safety and security is first and everything is regulated and it's very
07:23
conservative. In many ways I will say. It's sometimes slowing things but sometimes it's good to have stable environment. Some aviation organization, abbreviations is a key thing to understand. Personally I don't remember or don't even
07:48
know what is the difference with the aerodrome and the airport but there is a difference there. AIS is Aeronautical Information Services. Every nation have an AEI entity, agency, public
08:04
administration who is taking care about the managed aeronautical information in that state. Eurocontrol is European Organization for Safety of Air Negligation. Of course, European Union have own safety agency for the aviation and then FAA is US-based Federal Aviation Authority which is like Eurocontrol plus minus ESA.
08:32
And then there's ICAO which is International Civil Aviation Organization part of the United Nation agencies. So there is a lot
08:42
of different kind of organization and you better understand later on why I like to show you this kind of slide. So everything started in 2010 really about the ADQ, Aeronautical Data Quality. Very interesting European Union regulation. If you think about the INSPIRE, that's like easy stuff.
09:05
If you're comparing those, this original ADQ was replaced with two different kind of regulation in 2014 and 2017. And if you want to read those regulations, easy thing is to download this easy access rules which is about 800 pages full with the PDF.
09:29
It's also available in HTML if you like to read. As working in the airport, I'm most concentrating this first one, easy access rules
09:42
for aerodromes but there's some references to this other regulation so you have to read both if you want to understand what you should do. You can't forget the IXM which is Aeronautical Information Exchange Model, basically GML
10:03
-based XML stuff which you use to transfer the data between different agencies. Don't even start to think about the JSON. I mean we are now in IXM 5.1.1 and there's a
10:22
discussion on what will happen with 5.2 which will come in a few years so it's very conservative as an industry. All those regulations include references to other regulations so they don't want to copy the regulations from A to B so you
10:46
have to read also accounts chapter 17 and 14 and whatever they have to better understand what is actually demanded for the regulation. If somebody want to discuss more about this, maybe we can have a lunch or chew or week or whatever.
11:08
But I like to limit it, what is the regulated, what they actually says in the regulation for the airports and it's very simple. The airport operator which is quite often also the owner of the airport, in Finnavia it's also operator and owner but in
11:28
other countries it could be so that owner is different than operator, have to describe process to maintain aeronautical data of the airport. It's not only the geospatial data, I mean there's other data sets also but I'm just concentrating here in the geospatial information.
11:50
You have to follow accuracy and integrity rules in the field measurements. You have to coordinate, verify and validate all the data and you have to manage the traceability of the data.
12:06
So from the field in the databases and into data deliveries you have to maintain the information what's going on and that makes this kind of data sets very complicated in some way. And airport have to deliver airport aeronautical data to AIS for further publications.
12:28
So very simplified aeronautical data flow. So we have a, maybe I come here so you can see. So there's a, how it works.
12:43
So there's the airport operator here, AIS is here and the Eurocontrol is here and then we have end users who are actually using the data. So the airport is responsible about data collection in the field then they're modeling the data.
13:02
If they collect like runway threshold or aircraft standpoints, they use GPS devices or outside operator is using. They are storing the data in the database and then they make airport charts which will be coming to the end users.
13:21
They are the PDFs if you go to the AIS.EE you can find the airport charts and you can download those PDFs. They are usually not the geospatial PDFs so you have to figure out how to make the coordinate systems and so on if you want to use that in the GUGIS.
13:44
So then airport is responsible to transfer the data with AXM in the AIS. They usually store the data in the database and they make different kind of products. And then this national AIS is delivering the data to Eurocontrol who will take care about that the data is useful for like European wide data sets.
14:10
And they will take care about also that in the middle of the air spaces from Estonia to Finland that all the data is unique and there is no conflicts and so on.
14:23
The conflict resolution in the border area is very interesting but that's not outside of the airport operator issue. So the implementation, we have a PostgreSQL with PostGIS. We use pgAudit to auditing all modifications to external data storage.
14:44
So we have to follow up what kind of updates, inserts and delays have been done. We use pgModeler to make the database model and we are adapting the features from AXM and other regulations.
15:00
So this database is like a Finavia way to handle the airport data. I think it's useful for other players also if you ask it but it's not full features. I mean there's missing pieces but we are working on those.
15:21
And then there was a talk about or there's a lot of talks about the metadata. So the data layer metadata is a simple thing. We have to keep the feature level metadata. So like data source, ADQ, integrity levels and all those kind of information have to be collected in feature level.
15:46
And also we are creating the unique identifiers for every feature so we can think this traceability, manage the traceability. About those ADQ, integrity rules, critical routine essential.
16:01
It means that the critical information has to be validated every year. So there's a runaway threshold or aircraft standpoint, airport has to every year to check that data is not changing. And if it changes, they have to re-measure it in the field. And they manage information about data originator, variable factor, validator and deliver by feature.
16:27
So that's also the challenge to do. So Guji has editing environment, we have several projects for managing different data layers. This is aircraft stand or apron version of the editing environment.
16:46
And it's from the test version. I don't want to have access to the production version. I'm just a developer so that's out of my scope. And then there's a lot of those Guji's forms where you can manage all the information.
17:06
And here's the example about those feature level metadata that you can see. You can see that every field has different kind of... So elevation has a source and elevation has also ADQ integrity.
17:24
And you see in the source we have put some kind of information where the data has gone. So actually we have made data population from the existing API information. On August 11, 2020.
17:45
So the future plans. There's new demands from the customers and users. There's new and updated regulations. They change the regulations before everybody has implemented it. So it's like moving target all the time.
18:04
Idea is to plan to model the airport to the GIS database. Now there's a lot of CAD drawings. And we'd like to transfer the information from the CAD drawings to the GIS database. There's other entity, Euro-K, which has made a definition for the IOTM mapping database.
18:29
Which is a little bit different than the IXM. And a little bit different than what this ADQ is saying that the airport should do. So there's other regulation we have to follow up later on.
18:42
This AMDP is more close to the GIS database than the others. Thank you. Thank you Becca. Thank you Becca for this insight into behind the curtains of what's happening in the airport.
19:04
A passenger view, it's kind of really interesting to see it like this. Do we have any questions?
19:25
Thank you for the presentation. My question is related to the building information modeling. If you're going to also integrate that kind of models for, I don't know.
19:40
Yeah, well, sorry, I have to finish now. So, no answer on that. No, when we talk about the land side and the passenger map, that's public information. And then there's, because of the security reasons, they are not showing, of course, the areas where the passengers can't go.
20:07
So that building model will include that area too, and that will be a very secure way to handle. I mean, there's certain areas that they don't want to map in their airport.
20:24
And that's something that I haven't even seen those, so my security clearance is good enough for that. So there's a different kind of level of security. But those passenger maps, that's the public areas, and we just show those on that.
20:44
And it's a better passenger map. Passenger map is made for the passenger services, not nothing else. Any more questions? So I have, ah.
21:03
So I have just curious, how long does it take to create a map of one iteration of the airport? For your team, basically. Like, how long does it take to finish the QGIS update of a single iteration?
21:21
Oh, you mean the passenger map? Yeah, for instance, because I get it gets updated, but how long it could get like one airport, how long a project like this takes? Well, they have all the data already, so it's only updated. So they update like, and I think it's every night they transfer the data for the passengers, or even faster if necessary.
21:51
A bit of a tangent here. I've been working in specifications the past few years, so I get curious when you talk about things like AXM.
22:00
So two quick questions. Are you publishing data in the AXM format? And second question is, are you considering a linked data approach for a further version of the model? First thing is that no, there's no publicly available AXM to have.
22:20
Second thing about the AXM, that when I have discussion with the Eurocontrol and other agencies about the AXM, it seems to that they really have their own flavor of AXM. There's those vendor options. So it depends, where is my data flow?
22:41
So you have, if you want to use AXM, between the Finnavia and the Finnish AAS, they have to accurate what kind of version or, you know, version of the AXM they are using. And I know that there is a data, or IT service providers in this side,
23:03
and they have different AXM flavors for different states. And it takes also, because, yeah, it's complicated. What was the second question?
23:20
So you refer to coming versions of AXM? Yeah. And also JSON, and I'm wondering if that's related with a will to have a linked data approach, semantic web, all that stuff. I think GeoJSON or other JSON kind of definitions,
23:47
that does not include everything that is needed for my AXM. So we can't go in that. And this 5.2 will fix some errors and add something. And I don't see that I can see the future.
24:01
I mean, I like to retire before AXM will transfer to JSON, but that's it. I mean, yeah. Any more questions? Well, if that's the case, thank you Pekka for the presentation.
24:21
Thank you.