20,741
edits
Canvas EFB framework: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 53: | Line 53: | ||
}} | }} | ||
}} | }} | ||
== Motivation == | |||
{{FGCquote|1= I've noticed that a number of aircraft start having some kind of an "Electronic Flight Bag" (EFB), like the 787-8. They allow to view check lists, manuals, flight plan, airport charts, IAPs, SIDs and STARs etc. This is quite a nice development, at least for modern aircraft.|2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/34492026/ | title = <nowiki>[Flightgear-devel] Electronic Flight Bag</nowiki> | author = <nowiki>Jens Thoms Toerring</nowiki> | date = Sep 26th, 2015 }}}} | |||
{{FGCquote|1= The problem I see is that, at the moment, each aircraft has its own implementation, so a lot of work is done repeatedly.|2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/34492026/ | title = <nowiki>[Flightgear-devel] Electronic Flight Bag</nowiki> | author = <nowiki>Jens Thoms Toerring</nowiki> | date = Sep 26th, 2015 }}}} | |||
{{FGCquote|1= Thus I have been wondering a bit if it would make sense to develop a kind of framework for electronic flight bags.|2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/34492026/ | title = <nowiki>[Flightgear-devel] Electronic Flight Bag</nowiki> | author = <nowiki>Jens Thoms Toerring</nowiki> | date = Sep 26th, 2015 }}}} | |||
{{FGCquote|1= SIDS, STARs, and approaches are free for the US (where they're in the Public Domain, like most government-produced material). For Canada, they're not *libre* (free-as-in-speech), but you can get them *gratuit* (free-as-in-beer) from FltPlan.com. |2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/34492895/ | title = <nowiki>Re: [Flightgear-devel] Electronic Flight Bag</nowiki> | author = <nowiki>David Megginson</nowiki> | date = Sep 26th, 2015 }}}} | |||
{{FGCquote|1= I *think* what Jens is describing is just a global _framework_ to store these kinds of documents which then each plane would use, so that you don't have to copy files into every aircraft directory separately - it'd then still be up to the user to acquire the _content_ in a legal way and put it there. Without myself being much into airliner operation, to me this sounds a very useful idea. I think the best path forward is to get in touch with a few airliner maintainers who have used this kind of thing already, talk to them about a good interface/standard and then go ahead and do it - once it runs for 2-3 demo cases, others are going to adopt it.|2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/34493581/ | title = <nowiki>Re: [Flightgear-devel] Electronic Flight Bag</nowiki> | author = <nowiki>Renk, Thorsten</nowiki> | date = Sep 27th, 2015 }}}} | |||
{{FGCquote|1= at least a big part of it is about having a central location where EFBs built into the aircrafts can find data that all of them need. That are not SIDs or STARs as XML files (or whatever format would be used by the route manager) , but the corresponding approach plates, airport charts etc., i.e. stuff that you want to present to the user as graphics. Of course, there could bne more to such a framework in supporting functionalities shared by all EFBs.|2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/34494204/ | title = <nowiki>Re: [Flightgear-devel] Electronic Flight Bag</nowiki> | author = <nowiki>Jens Thoms Toerring</nowiki> | date = Sep 27th, 2015 }}}} | |||
== Background == | == Background == | ||
{{cquote | {{cquote | ||