The field of the disclosure relates generally to aircraft cockpit displays and more particularly, to methods and systems for depicting own ship on aircraft cockpit displays and charting devices.
At least some known aircraft include cockpit displays use charts and other information displays that aid in navigation and situational awareness. For example, charts displayed on electronic displays, referred to herein as electronic charts, typically are used for a wide variety of aspects of flight and flight planning. However, certain elements on such electronic charts may be difficult to read. One reason for this difficulty is that such electronic charts are formatted in the same fashion as paper charts.
On paper aviation charts, for example, the north indicator is placed in the upper right corner of the chart. As the electronic charts are patterned after the paper charts, current digital charting applications also show the north indicator in a static position. The north indicator or compass rose is required to be shown on charting applications but is placed as a chart overlay symbol in a static position, requiring a user to move their view from the own ship indicator to another screen location to determine orientation.
Such digital charting applications may allow the user to switch an appearance of the digital chart from a north up orientation to a heading up orientation depending on the selected/current mode. On certain flight instruments the own ship symbol is found in the heading indicator. However and as stated above, such configurations require a user to change their view and focus away from the own ship indicator to determine an orientation.
In summary, existing solutions have two separate elements for own ship depiction and north indicator depiction which are located at different locations on the map and therefore a pilot has to scan both elements to get an overall understanding of the current aircraft state.
In one aspect, a method for depicting own ship on a display is provided. The method includes receiving position data and heading data for own ship from at least one system, correlating, with a processing device, the position data and heading data with data from a map database, generating a map display on the display based on the correlation between the position data and the data from the map database, overlaying a depiction of own ship on the map display, the depiction based on the correlation between the position and heading data and the data from the map database, and encircling the own ship depiction with a circle overlay and a north indicator overlay proximate the circle overlay, the north indicator indicating a north direction.
In another aspect, a system is provided that includes a processing device, a memory communicatively coupled to the processing device and including map data, a display communicatively coupled to the processing device, and a communications interface communicatively coupled to the processing device. The processing device is operable to receive position data and heading data for own ship via the communications interface, correlate the received position data and heading data with the map data, generate a map display on the display based on the correlation between the position data and the map data, overlay a depiction of own ship on the display, the depiction based on the correlation between the position and heading data and the map data, and encircle the own ship depiction with a circle overlay and a north indicator overlay proximate the circle overlay, the north indicator indicating a north direction.
In still another aspect, one or more computer-readable storage media having computer-executable instructions embodied thereon are provided, wherein when executed by at least one processor, the computer-executable instructions cause the at least one processor to receive position data and heading data for own ship from at least one system, correlate the position data and heading data with data from a map database, generate a map display based on the correlation between the position data and the data from the map database, overlay a depiction of own ship on the map display, the depiction based on the correlation between the position and heading data and the data from the map database, and encircle the own ship depiction with a circle overlay and a north indicator overlay proximate the circle overlay, the north indicator indicating a north direction
The features, functions, and advantages that have been discussed can be achieved independently in various embodiments or may be combined in yet other embodiments further details of which can be seen with reference to the following description and drawings.
The described embodiments are directed to the implementation of an own ship symbol combined with a north indicator on a flight display with the north indicator being in a close circle about the own ship position. The embodiments may be practiced in any of an aviation, land navigation, or water navigation environment. With the location of a north indicator proximate an own ship depiction, a user is able to stay focused on the own ship indicator and readily determine compass orientation.
In the exemplary embodiment, the electronic flight bag 104 includes an electronic storage device configured to store various user-configurable flight-related objects for all required and desired information for a particular flight, such as flight routes, as defined by, for example, way-points, airport information, temporary flight restrictions, and weather information as well as any other user-defined objects associated with a flight, ground operations, and/or flight planning. Certain of these include electronic versions of aviation charts and/or navigation charts, sometimes collectively referred to herein as electronic charts or maps. The electronic flight bag 104 may receive data from various aircraft and ground sensors and systems, determines flight information, for example, position data and heading data, based on the received data in real-time, and displays the flight information and/or alerts the flight crew through display screen 102 and other aural and/or visual indicators positioned on cockpit display panel 100. One or more of the flight systems and the electronic flight bag 104 may correlate position data and heading data with the electronic map data. Such flight information provides the flight crew with additional situational awareness during all phases of aircraft operation. In accordance with the embodiments described herein, the above described examples are considered to incorporate one or more touch screens.
As explained above, the embodiments are directed to a north indicator that is included proximate or about the own ship symbol and not displayed separately on, for example, an electronic map or screen. The embodiments provide better situational awareness due to the fact that own ship heading and north direction indicator can both be seen at a glance. The embodiments further reduce screen cluttering because a separate north indicator is not needed. Workload is reduced because in planning and live mode the same indicator can be used, independent from the phase of flight. As a result, current 2D aircraft attitude information (position and heading) can be found combined in one screen location.
In one embodiment, technical effects of the methods, systems, and computer-readable media described herein include at least one of: (a) receiving position data and heading data for own ship from at least one system, (b) correlating, with a processing device, the position data and heading data with data from a map database, (c) generating a map display on the display based on the correlation between the position data and the data from the map database, (d) overlaying a depiction of own ship on the map display, the depiction based on the correlation between the position and heading data and the data from the map database, and (e) encircling the own ship depiction with a circle overlay and a north indicator overlay proximate the circle overlay, the north indicator indicating a north direction.
As used herein, an element or step recited in the singular and proceeded with the word “a” or “an” should be understood as not excluding plural elements or steps unless such exclusion is explicitly recited. Furthermore, references to “one embodiment” of the present invention or the “exemplary embodiment” are not intended to be interpreted as excluding the existence of additional embodiments that also incorporate the recited features.
As easily understood by those skilled in the art, the embodiments described herein are capable of being implemented on a variety of devices ranging from permanently mounted aircraft displays to portable user devices that have a touch screen, chart display capability, and capability to determine location with respect to an electronic chart. Such hardware and display capabilities are found in numerous consumer devices, for example, so called smartphones and a myriad of portable computing devices.
The described embodiments depend upon a combination of software techniques for manipulating, in real time, the graphical view of the charts to include one of the own ship symbols described herein, with the direction of the indicator or compass being controlled based on data received from one or more other flight units. With the range of devices capable of executing the software necessary for generating such displays understood,
Processor unit 604 serves to execute instructions for software that may be loaded into memory 606. Processor unit 604 may be a set of one or more processors or may be a multi-processor core, depending on the particular implementation. Further, processor unit 604 may be implemented using one or more heterogeneous processor systems in which a main processor is present with secondary processors on a single chip. As another illustrative example, processor unit 604 may be a symmetric multi-processor system containing multiple processors of the same type.
Memory 606 and persistent storage 608 are examples of storage devices. A storage device is any piece of hardware that is capable of storing information either on a temporary basis and/or a permanent basis. Memory 606, in these examples, may be, for example, without limitation, a random access memory or any other suitable volatile or non-volatile storage device. Persistent storage 608 may take various forms depending on the particular implementation. For example, without limitation, persistent storage 608 may contain one or more components or devices. For example, persistent storage 608 may be a hard drive, a flash memory, a rewritable optical disk, a rewritable magnetic tape, or some combination of the above. The media used by persistent storage 608 also may be removable. For example, without limitation, a removable hard drive may be used for persistent storage 608.
Communications unit 610, in these examples, provides for communications with other data processing systems or devices. In these examples, communications unit 610 is a network interface card. Communications unit 610 may provide communications through the use of either or both physical and wireless communication links.
Input/output unit 612 allows for input and output of data with other devices that may be connected to data processing system 600. For example, without limitation, input/output unit 612 may provide a connection for user input through a keyboard and mouse. Further, input/output unit 612 may send output to a printer. Display 614 provides a mechanism to display information to a user.
Instructions for the operating system and applications or programs are located on persistent storage 608. These instructions may be loaded into memory 606 for execution by processor unit 604. The processes of the different embodiments may be performed by processor unit 604 using computer implemented instructions, which may be located in a memory, such as memory 606. These instructions are referred to as program code, computer usable program code, or computer readable program code that may be read and executed by a processor in processor unit 604. The program code in the different embodiments may be embodied on different physical or tangible computer readable media, such as memory 606 or persistent storage 608.
Program code 616 is located in a functional form on computer readable media 618 that is selectively removable and may be loaded onto or transferred to data processing system 600 for execution by processor unit 604. Program code 616 and computer readable media 618 form computer program product 320 in these examples. In one example, computer readable media 618 may be in a tangible form, such as, for example, an optical or magnetic disc that is inserted or placed into a drive or other device that is part of persistent storage 608 for transfer onto a storage device, such as a hard drive that is part of persistent storage 608. In a tangible form, computer readable media 618 also may take the form of a persistent storage, such as a hard drive, a thumb drive, or a flash memory that is connected to data processing system 600. The tangible form of computer readable media 618 is also referred to as computer recordable storage media. In some instances, computer readable media 618 may not be removable.
Alternatively, program code 616 may be transferred to data processing system 600 from computer readable media 618 through a communications link to communications unit 610 and/or through a connection to input/output unit 612. The communications link and/or the connection may be physical or wireless in the illustrative examples. The computer readable media also may take the form of non-tangible media, such as communications links or wireless transmissions containing the program code.
In some illustrative embodiments, program code 616 may be downloaded over a network to persistent storage 608 from another device or data processing system for use within data processing system 600. For instance, program code stored in a computer readable storage medium in a server data processing system may be downloaded over a network from the server to data processing system 600. The data processing system providing program code 616 may be a server computer, a client computer, or some other device capable of storing and transmitting program code 616.
The different components illustrated for data processing system 600 are not meant to provide architectural limitations to the manner in which different embodiments may be implemented. The different illustrative embodiments may be implemented in a data processing system including components in addition to or in place of those illustrated for data processing system 600. Other components shown in
As one example, a storage device in data processing system 600 is any hardware apparatus that may store data. Memory 606, persistent storage 608 and computer readable media 618 are examples of storage devices in a tangible form. The methods described herein may be encoded as executable instructions embodied in a computer readable medium, including, without limitation, a storage device or a memory area of a computing device. Such instructions, when executed by one or more processors, cause the processor(s) to perform at least a portion of the methods described herein.
In another example, a bus system may be used to implement communications fabric 602 and may be comprised of one or more buses, such as a system bus or an input/output bus. Of course, the bus system may be implemented using any suitable type of architecture that provides for a transfer of data between different components or devices attached to the bus system. Additionally, a communications unit may include one or more devices used to transmit and receive data, such as a modem or a network adapter. Further, a memory may be, for example, without limitation, memory 606 or a cache such as that found in an interface and memory controller hub that may be present in communications fabric 602.
As described herein, embodiments include one or more processors and memory devices. The processors are programmed to execute computer-executable instructions, which may be stored in a memory device, to perform the methods described herein. For example, any or all of the operations described herein may be encoded as computer-executable instructions and executed by processor. The methods described herein may be encoded as executable instructions embodied in a computer readable medium, including, without limitation, a storage device or a memory area of a computing device. Such instructions, when executed by one or more processors, cause the processor(s) to perform at least a portion of the methods described herein.
This written description uses examples to disclose various embodiments, which include the best mode, to enable any person skilled in the art to practice those embodiments, including making and using any devices or systems and performing any incorporated methods. The patentable scope is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal languages of the claims.
Number | Name | Date | Kind |
---|---|---|---|
3521227 | Congleton et al. | Jul 1971 | A |
3652836 | Richardson et al. | Mar 1972 | A |
3696385 | Burns | Oct 1972 | A |
4283705 | James et al. | Aug 1981 | A |
4326189 | Crane | Apr 1982 | A |
5045860 | Hodson | Sep 1991 | A |
5136301 | Bechtold et al. | Aug 1992 | A |
5844504 | Etherington | Dec 1998 | A |
5969665 | Yufa | Oct 1999 | A |
6028536 | Voulgaris | Feb 2000 | A |
6038498 | Briffe et al. | Mar 2000 | A |
6057786 | Briffe et al. | May 2000 | A |
6111525 | Berlioz et al. | Aug 2000 | A |
6112141 | Briffe et al. | Aug 2000 | A |
6131297 | Yamamoto | Oct 2000 | A |
6150960 | Voulgaris | Nov 2000 | A |
6199471 | Perruzzi | Mar 2001 | B1 |
6335695 | Kawasaki | Jan 2002 | B1 |
6408248 | Yancey, Jr. | Jun 2002 | B1 |
6453570 | Rahn | Sep 2002 | B1 |
6534712 | Pitrone | Mar 2003 | B1 |
6885313 | Selk et al. | Apr 2005 | B2 |
6934608 | Qureshi | Aug 2005 | B2 |
7054725 | Burch et al. | May 2006 | B2 |
7114263 | Toda | Oct 2006 | B2 |
7191406 | Barber et al. | Mar 2007 | B1 |
7194342 | Horvath et al. | Mar 2007 | B1 |
7215256 | Reusser et al. | May 2007 | B2 |
7295901 | Little et al. | Nov 2007 | B1 |
7308343 | Horvath et al. | Dec 2007 | B1 |
7392486 | Gyde et al. | Jun 2008 | B1 |
7508322 | Krenz et al. | Mar 2009 | B1 |
7772994 | He | Aug 2010 | B2 |
7834779 | He et al. | Nov 2010 | B2 |
7965223 | McCusker | Jun 2011 | B1 |
8159464 | Gribble et al. | Apr 2012 | B1 |
8184020 | He | May 2012 | B2 |
8244466 | DeJonge et al. | Aug 2012 | B2 |
8264378 | Martins et al. | Sep 2012 | B1 |
8306745 | Clark et al. | Nov 2012 | B1 |
8314719 | Grothe | Nov 2012 | B2 |
8392039 | He et al. | Mar 2013 | B2 |
8395533 | Ganille et al. | Mar 2013 | B2 |
8514102 | Palanisamy et al. | Aug 2013 | B2 |
8599046 | Ca | Dec 2013 | B2 |
8645056 | Wipplinger et al. | Feb 2014 | B2 |
8670880 | Baxter | Mar 2014 | B2 |
20030210228 | Ebersole | Nov 2003 | A1 |
20070085707 | Wyatt | Apr 2007 | A1 |
20070168120 | Vandenbergh et al. | Jul 2007 | A1 |
20070236366 | Gur | Oct 2007 | A1 |
20080114537 | Aspen | May 2008 | A1 |
20080125962 | Wipplinger et al. | May 2008 | A1 |
20080275642 | Clark et al. | Nov 2008 | A1 |
20090231163 | He | Sep 2009 | A1 |
20090248297 | Feyersisen et al. | Oct 2009 | A1 |
20100082186 | Burgin et al. | Apr 2010 | A1 |
20100156674 | Dwyer et al. | Jun 2010 | A1 |
20100280753 | Chytil et al. | Nov 2010 | A1 |
20110010082 | Wilson et al. | Jan 2011 | A1 |
20110045848 | Okeya | Feb 2011 | A1 |
20110196598 | Feyereisen | Aug 2011 | A1 |
20110199237 | Clark | Aug 2011 | A1 |
20110199239 | Lutz et al. | Aug 2011 | A1 |
20120310524 | Pepitone et al. | Dec 2012 | A1 |
Entry |
---|
http://www.allstar.fiu.edu/aero/images/headingindicator.gif; Apr. 8, 2010; 1 page. |
http://www.kienzi.ch/flights/2008/images/20080329_121812_Flug_N466M_Zuerich_MontBlanc_Matterhorn_Jungfrau_Saentis_ZuerichS.JPG: Mar. 29, 2008; 1 page. |
http://www.kienzi.ch/flights/2008/images/20080329_121808_Flug_N466M_Zuerich_MontBlanc_Matterhorn_Jungfrau_Saentis_Zuerich$JPG; Mar. 29, 2008; 1 page. |