CN112328572A - Flight history duplication method, device, equipment and storage medium - Google Patents

Flight history duplication method, device, equipment and storage medium Download PDF

Info

Publication number
CN112328572A
CN112328572A CN202010979599.3A CN202010979599A CN112328572A CN 112328572 A CN112328572 A CN 112328572A CN 202010979599 A CN202010979599 A CN 202010979599A CN 112328572 A CN112328572 A CN 112328572A
Authority
CN
China
Prior art keywords
flight
track
target
container
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202010979599.3A
Other languages
Chinese (zh)
Inventor
谢康
范祝满
佘玲玲
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Zhongshuke Technology Co ltd
Original Assignee
Beijing Zhongshuke Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Zhongshuke Technology Co ltd filed Critical Beijing Zhongshuke Technology Co ltd
Priority to CN202010979599.3A priority Critical patent/CN112328572A/en
Publication of CN112328572A publication Critical patent/CN112328572A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21Design, administration or maintenance of databases
    • G06F16/219Managing data history or versioning
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/29Geographical information databases
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/953Querying, e.g. by the use of web search engines
    • G06F16/9537Spatial or temporal dependent retrieval, e.g. spatiotemporal queries
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F18/00Pattern recognition
    • G06F18/20Analysing
    • G06F18/22Matching criteria, e.g. proximity measures

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Bioinformatics & Cheminformatics (AREA)
  • Evolutionary Computation (AREA)
  • Evolutionary Biology (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Bioinformatics & Computational Biology (AREA)
  • Artificial Intelligence (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Remote Sensing (AREA)
  • Traffic Control Systems (AREA)

Abstract

The embodiment of the specification provides a flight history duplication method, a flight history duplication device, flight history duplication equipment and a storage medium, and the flight history duplication method comprises the following steps: establishing a corresponding and associated track object and flight object based on the acquired flight data, and correspondingly storing the track object and the flight object in a first container and a second container; filling the track points and the service data in the flight data into a data structure of a corresponding track object according to a time sequence; when a disk-copying instruction containing a disk-copying time point is received, matching a target track object from the first container and matching a target flight object from the second container; and displaying the target track according to the track point corresponding to the target track object, and dynamically displaying the target flight object from the time point of the disk replication according to the track point corresponding to the target track object and the service data. The embodiment of the specification can realize duplication of flight history of flights.

Description

Flight history duplication method, device, equipment and storage medium
Technical Field
The present disclosure relates to the field of big data processing technologies, and in particular, to a flight history duplication method, device, equipment, and storage medium.
Background
Under the current big data environment, the rapid development of the data analysis field is brought by massive data, and the data mining as a key technology in the data analysis provides necessary guarantee for the rapid development of the data analysis. Because of a plurality of data mining methods, each method has different applicable environments, the development of the data mining method under different environments is extremely important. Data mining is widely applied in many fields (such as information security, finance and the like), but related data mining methods in the aviation field are few. In the field of aviation, if the flight history of a flight can be copied based on mass flight data, the method has important significance for subsequent analysis of flight accidents of the flight and the like. However, at present, there is no implementation scheme that can duplicate the flight history of flights based on massive flight data.
Disclosure of Invention
An object of the embodiments of the present specification is to provide a flight history duplication method, device, equipment and storage medium, so as to implement duplication of flight history of a flight.
In order to achieve the above object, in one aspect, a flight history duplication method includes:
establishing a corresponding and associated track object and flight object based on the acquired flight data, and correspondingly storing the track object and the flight object in a first container and a second container;
filling the track points and the service data in the flight data into a data structure of a corresponding track object according to a time sequence;
when a disk-copying instruction containing a disk-copying time point is received, matching a target track object from the first container and matching a target flight object from the second container;
and displaying the target track according to the track point corresponding to the target track object, and dynamically displaying the target flight object from the time point of the disk replication according to the track point corresponding to the target track object and the service data.
In an embodiment of this specification, the creating a corresponding associated track object and flight object based on the obtained flight data includes:
and creating a track object and a flight object which are associated by the flight identifier in a one-to-one correspondence mode based on the acquired flight data.
In an embodiment of the present specification, the matching a target track object from the first container includes:
and filtering out the flight path object corresponding to the flight path at the flight path time point from the first container by using a first data filter configured in the first container to be used as a target flight path object.
In an embodiment of the present specification, the matching a target flight object from the second container includes:
and filtering out the flight object corresponding to the flight class at the reply time point from the second container by using a second data filter configured in the second container to serve as the target flight object.
In an embodiment of the present specification, the filtering out, from the first container, a flight path object corresponding to a flight crew at the flight crew time point includes:
for each track object in the first container, judging whether the reply time point is positioned between the take-off time and the landing time of the flight corresponding to the track object;
if the reply time point is positioned between the take-off time and the landing time of the flight corresponding to the track object, taking the track object as one of the target track objects for displaying;
and if the reply time point is not between the take-off time and the landing time of the flight corresponding to the track object, filtering the track object by using the first data filter to avoid display.
In an embodiment of the present specification, the filtering out, from the second container, a flight object corresponding to a flight class at the time of the flight number reply time point includes:
for each flight object in the second container, judging whether the reply time point is between the departure time and the landing time of the flight corresponding to the flight object;
if the reply time point is positioned between the departure time and the landing time of the flight corresponding to the flight object, taking the flight object as one of the target flight objects for displaying;
and if the reply time point is not between the departure time and the landing time of the flight corresponding to the flight object, filtering the flight object by using the second data filter to avoid display.
In an embodiment of this specification, the dynamically displaying the target flight object from the reply time point according to the track point and the service data corresponding to the target track object includes:
for each target flight object:
taking out track points and service data under the time points of the disk replication from the corresponding target track object;
displaying the flight state of the target flight object at the reply time point according to the track point and the service data at the reply time point;
and recursion is carried out in this way until the flight state display of the target flight object at the corresponding landing time point is completed.
In an embodiment of this specification, the displaying the flight status of the target flight object at the reply time point includes:
obtaining map slice data corresponding to the track point under the time point of the re-disc;
and taking the map slice data as a reference base map, and three-dimensionally rendering the flight state of the target flight object at the copy time point.
In another aspect, an embodiment of the present specification further provides a flight history duplication apparatus, including:
the creating module is used for creating a corresponding and associated track object and flight object based on the acquired flight data, and correspondingly storing the track object and the flight object in a first container and a second container;
the filling module is used for filling the track points and the service data in the flight data into a data structure of the corresponding track object according to a time sequence;
the matching module is used for matching a target track object from the first container and matching a target flight object from the second container when a disk-copying instruction containing a disk-copying time point is received;
and the display module is used for displaying the target track according to the track point corresponding to the target track object, and dynamically displaying the target flight object from the time point of the flight duplication according to the track point corresponding to the target track object and the service data.
In another aspect, the embodiments of the present specification further provide a computer device, which includes a memory, a processor, and a computer program stored on the memory, and when the computer program is executed by the processor, the computer program executes the instructions of the above method.
In another aspect, the present specification further provides a computer storage medium, on which a computer program is stored, and the computer program is executed by a processor of a computer device to execute the instructions of the method.
As can be seen from the technical solutions provided by the embodiments of the present specification, the embodiments of the present specification may create a corresponding associated flight path object and flight path object based on the acquired flight data, and store the flight path object and the flight path object in a first container and a second container correspondingly; the track points and the service data in the flight data can be filled into the data structure of the corresponding track object according to the time sequence; when a disk copying instruction containing a disk copying time point is received, matching a target flight path object from a first container, and matching a target flight path object from a second container; and then, displaying the target track according to the track point corresponding to the target track object, and dynamically displaying the target flight object from the time point of flight duplication according to the track point corresponding to the target track object and the service data, thereby realizing the flight history playback of the flight based on the flight data, namely realizing the flight history duplication of the flight. Furthermore, since the embodiments of the present specification further establish separate data loading models (i.e. the first container and the second container) for the track object and the flight object, respectively, separation of static data (track object) and dynamic data (flight object) is achieved, and this low coupling manner facilitates separate control of the track object and the flight object.
Drawings
In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort. In the drawings:
FIG. 1 is a flow chart of a flight history duplication method in an embodiment provided in the present specification;
FIG. 2 is a data flow diagram of a flight history replication method in an embodiment provided in the present specification;
FIG. 3 is a rendering diagram of flight objects and track objects in an embodiment provided in the present specification;
fig. 4 is a block diagram of a flight history duplication device in an embodiment provided in the present specification;
fig. 5 is a block diagram of a computer device in an embodiment provided in the present specification.
[ description of reference ]
31. An image acquisition module;
32. a character recognition module;
33. a text word segmentation module;
34. a direction determination module;
35. a text cleaning module;
502. a computer device;
504. a processor;
506. a memory;
508. a drive mechanism;
510. an input/output module;
512. an input device;
55. an output device;
516. a presentation device;
518. a graphical user interface;
520. a network interface;
522. a communication link;
524. a communication bus.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all of the embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification without any inventive step should fall within the scope of protection of the present specification.
The embodiment of the specification relates to a visual flight history duplication technology, and is suitable for an application scenario of flight history duplication based on mass flight data.
The embodiment of the specification provides a flight history duplication method, which can be applied to an aviation monitoring management system and the like. Referring to fig. 1, in some embodiments of the present disclosure, the flight history duplication method may include the following steps:
s101, creating a corresponding and associated track object and flight object based on the acquired flight data, and correspondingly storing the track object and the flight object in a first container and a second container.
And S102, filling the track points and the service data in the flight data into a data structure of the corresponding track object according to a time sequence.
And S103, when a disk copying instruction containing a disk copying time point is received, matching a target track object from the first container, and matching a target flight object from the second container.
And S104, displaying the target track according to the track point corresponding to the target track object, and dynamically displaying the target flight object from the time point of the flight duplication according to the track point corresponding to the target track object and the service data.
As such, embodiments of the present description may create a corresponding associated flight path object and flight path object based on the acquired flight data, and store the flight path object and flight path object in a first container and a second container; the track points and the service data in the flight data can be filled into the data structure of the corresponding track object according to the time sequence; when a disk copying instruction containing a disk copying time point is received, matching a target flight path object from a first container, and matching a target flight path object from a second container; and then, displaying the target track according to the track point corresponding to the target track object, and dynamically displaying the target flight object from the time point of flight duplication according to the track point corresponding to the target track object and the service data, thereby realizing the flight history playback of the flight based on the flight data, namely realizing the flight history duplication of the flight. Furthermore, since the embodiments of the present specification further establish separate data loading models (i.e. the first container and the second container) for the track object and the flight object, respectively, separation of static data (track object) and dynamic data (flight object) is achieved, and this low coupling manner facilitates separate control of the track object and the flight object.
In embodiments of the present description, the flight may include, but is not limited to, any regular or irregular aircraft engaged in public or private transportation of passengers, mail, or cargo, etc.
In embodiments of the present description, the flight data may be information about flight Identifiers (IDs), track points (e.g., coordinate position, altitude, etc.), traffic data (e.g., speed of flight, attitude (e.g., yaw, pitch, and roll), etc.), time to takeoff, time to pre-land (i.e., time to pre-arrival), etc., obtained from one or more data sources. The track point, the service data and the like are data which change with time. In some embodiments of the present description, the data sources may include, for example: aircraft Communication Addressing and Reporting System (ACARS), Broadcast Automatic Dependent Surveillance-Broadcast (ADS-B), 24-hour flight radar (fr 24) and the like.
Due to the large data volume and frequent update of the flight data, in some embodiments of the present specification, a piece of flight data may be periodically obtained from a data source through a set timing task and analyzed (for example, when the flight data is json data, json analysis may be performed on the flight data). For example, for each flight in the set of flights, a piece of flight data may be periodically retrieved. Wherein, the flights in the flight set can be selected according to actual needs. For example, for an airline monitoring management system for an airline farm, the set of flights may include all or a portion of flights taking off and/or landing from the airline farm.
In an embodiment of the present description, the first Container is a Container (Container) for loading a track object, and may also be referred to as a track model (trackmodel). Also, the second container mentioned in the embodiments of the present specification is a container for loading flight objects. The first container and the second container together form a data simulation model (simulatormadel) for implementing flight history duplication. To implement the double-disk visualization, when the first container and the second container are initialized, corresponding layers (for example, the track object layer and the flight object layer shown in fig. 2) are also created for the first container and the second container, respectively.
In the embodiments of the present specification, in order to save container resources, the track object and flight object of each flight may not be created in advance at the time of system initialization; when flight data of a flight is received for the first time, a track object and a flight object corresponding to the relationship are created, the track object is stored in a first container, and the flight object is stored in a second container. On the basis, each flight data is obtained, and the flight data can be filled into the data structure of the corresponding track object according to the time sequence.
In some embodiments of the present specification, the track object and the flight object that are associated with each other based on the acquired flight data may be created, and the track object and the flight object that are associated with each other by a flight ID in a one-to-one correspondence may be created for the acquired flight data, that is, the track object and the flight object may be identified by using the flight ID as a unique value. Therefore, the track object, the flight object and the flight can be conveniently associated in a one-to-one correspondence manner. For example, in the exemplary embodiment shown in fig. 2, the track object 1 to the track object m are correspondingly associated with the flight object 1 to the flight object m in a one-to-one correspondence through the flight ID1 to the flight IDm.
When flight duplication is needed, the duplication object and the duplication time point can be set through a human-computer interface (such as a graphical user interface and the like). Wherein the duplication object indicates which flight or flights to perform the flight history duplication. The duplication time point indicates from which time point the duplication of the duplication object can be started. For example, the flight time of a flight from Beijing to Shanghai is 12:00:00 to 14:00:00 for two hours; when the duplication time point is set, the whole flight time period of duplication can be selected, for example, the duplication time point is set to be 12:00:00, so that the duplication time period is 12:00: 00-14: 00: 00; a part of the duplication can also be selected, for example, the duplication time point is set to be 13:00:00, so that the time period of duplication is 13:00: 00-14: 00: 00.
In some embodiments of the present specification, when a reply command is received (the reply command includes the reply time point and the reply object), a first data filter (for example, as shown in fig. 2) configured in the first container may be utilized to filter out a track object corresponding to the flight crew at the reply time point from the first container as a target track object; and may filter out, from the second container, a flight object corresponding to the flight class at the time of the flight replication time point by using a second data filter (for example, as shown in fig. 2) configured in the second container, so as to serve as the target flight object.
In some embodiments of the present description, filtering out the flight path object corresponding to the flight path at the flight path time point from the first container may include:
1) judging whether the reply time point is between the take-off time and the landing time of the flight corresponding to the track object for each track object in the first container;
2) if the reply time point is positioned between the take-off time and the landing time of the flight corresponding to the track object, taking the track object as one of the target track objects for displaying; and if the reply time point is not between the take-off time and the landing time of the flight corresponding to the track object, filtering the track object by using the first data filter to avoid display.
For example, the flight time of the flight from Beijing to Shanghai is 12:00:00 to 14:00:00 for two hours. If the reply time point is between 12:00:00 and 14:00:00 (for example, the reply time point is 13:00:00), the corresponding track object can be used as one of the target track objects, and if the reply time point is outside 12:00:00 to 14:00:00 (for example, the reply time point is 11:50:00, or the reply time point is 14:20:20), the corresponding track object can not be used as the target track object because the flight has not taken off or the flight has landed.
Similarly, filtering out the flight object corresponding to the flight class at the reply time point from the second container may include:
1) judging whether the reply time point is between the departure time and the landing time of the flight corresponding to the flight object for each flight object in the second container;
2) if the reply time point is positioned between the departure time and the landing time of the flight corresponding to the flight object, taking the flight object as one of the target flight objects for displaying; and if the reply time point is not between the departure time and the landing time of the flight corresponding to the flight object, filtering the flight object by using the second data filter to avoid display.
Thus, by filtering by means of the first data filter and the second data filter, it is possible to display objects according to specified conditions; if the specified condition is satisfied, the display is permitted, and if the specified condition is not satisfied, the display is not permitted. Therefore, simulation effects that the flight objects disappear after landing and do not take off can be vividly realized, and certainly, the corresponding flight path objects are not displayed under the condition that the flight objects disappear after landing or do not take off.
In an embodiment of the present specification, the first data filter and the second data filter are both data filtering components. To facilitate User operations, in some embodiments of the present description, the first data filter and the second data filter may be User Interface (UI) controls.
In some embodiments of this specification, the dynamically displaying the target flight object from the reply time point according to the track point and the service data corresponding to the target track object may include:
for each target flight object:
1) and taking out the track point and the service data under the time point of the re-disk from the corresponding target track object.
2) And displaying the flight state of the target flight object at the reply time point according to the track point and the service data at the reply time point. Obviously, the flight status (e.g. coordinates, altitude, speed, direction, etc.) of the target flight object at the reply time point can be determined according to the track point and the service data at the reply time point, and accordingly the flight status of the target flight object at the reply time point can be displayed in the layer of the target flight object (e.g. as shown in fig. 3). As can be seen from fig. 3, the flight status of the flight object at each flight time point can be dynamically displayed graphically and luxuriantly in the embodiment of the present specification.
3) And recursion is carried out until the flight state display of the target flight object at the corresponding landing time point is completed.
In other embodiments of this specification, the displaying the flight status of the target flight object at the reply time point may further include: obtaining map slice data (such as a global satellite image section, a digital elevation model section and the like based on a geographic information system) corresponding to the track point under the review time point; and taking the map slice data as a reference base map, and three-dimensionally rendering the flight state of the target flight object at the copy time point. Therefore, the rendering effect can be further improved, and the visual experience of the user is enhanced.
While the process flows described above include operations that occur in a particular order, it should be appreciated that the processes may include more or less operations that are performed sequentially or in parallel (e.g., using parallel processors or a multi-threaded environment).
Corresponding to the flight history duplication method, embodiments of the present specification further provide a flight history duplication device, which may be configured in an aviation monitoring management system. Referring to fig. 4, in some embodiments of the present disclosure, the flight history duplication apparatus may include:
the creating module 41 may be configured to create a corresponding associated track object and flight object based on the obtained flight data, and store the track object and the flight object in a first container and a second container correspondingly;
the filling module 42 may be configured to fill track points and service data in the flight data into a data structure of a corresponding track object according to a time sequence;
a matching module 43, configured to, when a reply instruction containing a reply time point is received, match a target track object from the first container and match a target flight object from the second container;
the display module 44 may be configured to display the target track according to the track point corresponding to the target track object, and dynamically display the target flight object from the time point of the flight duplication according to the track point corresponding to the target track object and the service data.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the various elements may be implemented in the same one or more software and/or hardware implementations of the present description.
As shown in fig. 5, embodiments of the present description also provide a computer device 502. The computer device 502 may include one or more processors 504, such as one or more Central Processing Units (CPUs) or Graphics Processors (GPUs), each of which may implement one or more hardware threads. The computer device 502 may also comprise any memory 506 for storing any kind of information, such as code, settings, data, etc., and in a particular embodiment a computer program running on the memory 506 and on the processor 504, which computer program, when being executed by the processor 504, may perform the instructions according to the above-described method. For example, and without limitation, memory 506 may include any one or more of the following in combination: any type of RAM, any type of ROM, flash memory devices, hard disks, optical disks, etc. More generally, any memory may use any technology to store information. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent fixed or removable components of computer device 502. In one case, when the processor 504 executes the associated instructions, which are stored in any memory or combination of memories, the computer device 502 can perform any of the operations of the associated instructions. The computer device 502 also includes one or more drive mechanisms 508, such as a hard disk drive mechanism, an optical disk drive mechanism, etc., for interacting with any memory.
Computer device 502 may also include an input/output module 510(I/O) for receiving various inputs (via input device 512) and for providing various outputs (via output device 55). One particular output mechanism may include a presentation device 516 and an associated graphical user interface 518 (GUI). In other embodiments, the input/output module 510(I/O), the input device 512, and the output device 55 may also be excluded, as just one computer device in the network. Computer device 502 can also include one or more network interfaces 520 for exchanging data with other devices via one or more communication links 522. One or more communication buses 524 couple the above-described components together.
Communication link 522 may be implemented in any manner, such as through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. Communication link 522 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the specification. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processor to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processor, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processor to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processor to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computer device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium which can be used to store information that can be accessed by a computer device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.
The embodiments of this specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The described embodiments may also be practiced in distributed computing environments where tasks are performed by remote processors that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment. In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of an embodiment of the specification. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims (11)

1. A flight history duplication method is characterized by comprising the following steps:
establishing a corresponding and associated track object and flight object based on the acquired flight data, and correspondingly storing the track object and the flight object in a first container and a second container;
filling the track points and the service data in the flight data into a data structure of a corresponding track object according to a time sequence;
when a disk-copying instruction containing a disk-copying time point is received, matching a target track object from the first container and matching a target flight object from the second container;
and displaying the target track according to the track point corresponding to the target track object, and dynamically displaying the target flight object from the time point of the disk replication according to the track point corresponding to the target track object and the service data.
2. The flight history reply method of claim 1, wherein the creating of the corresponding associated flight object and flight object based on the acquired flight data comprises:
and creating a track object and a flight object which are associated by the flight identifier in a one-to-one correspondence mode based on the acquired flight data.
3. The flight history reply method of claim 1, wherein the matching of the target track object from the first container comprises:
and filtering out the flight path object corresponding to the flight path at the flight path time point from the first container by using a first data filter configured in the first container to be used as a target flight path object.
4. The flight history duplication method of claim 1, wherein the matching of the target flight object from the second container comprises:
and filtering out the flight object corresponding to the flight class at the reply time point from the second container by using a second data filter configured in the second container to serve as the target flight object.
5. The flight history reply method according to claim 3, wherein the filtering out the track object corresponding to the flight class at the reply time point from the first container comprises:
for each track object in the first container, judging whether the reply time point is positioned between the take-off time and the landing time of the flight corresponding to the track object;
if the reply time point is positioned between the take-off time and the landing time of the flight corresponding to the track object, taking the track object as one of the target track objects for displaying;
and if the reply time point is not between the take-off time and the landing time of the flight corresponding to the track object, filtering the track object by using the first data filter to avoid display.
6. The flight history duplication method of claim 4, wherein the filtering out of the second container of flight objects corresponding to the flight class at the duplication time point comprises:
for each flight object in the second container, judging whether the reply time point is between the departure time and the landing time of the flight corresponding to the flight object;
if the reply time point is positioned between the departure time and the landing time of the flight corresponding to the flight object, taking the flight object as one of the target flight objects for displaying;
and if the reply time point is not between the departure time and the landing time of the flight corresponding to the flight object, filtering the flight object by using the second data filter to avoid display.
7. The flight history reply method according to claim 1, wherein the dynamically displaying the target flight object from the reply time point according to the track point and the service data corresponding to the target track object comprises:
for each target flight object:
taking out track points and service data under the time points of the disk replication from the corresponding target track object;
displaying the flight state of the target flight object at the reply time point according to the track point and the service data at the reply time point;
and recursion is carried out in this way until the flight state display of the target flight object at the corresponding landing time point is completed.
8. The flight history replying method of claim 7, wherein the displaying the flight status of the target flight object at the replying time point comprises:
obtaining map slice data corresponding to the track point under the time point of the re-disc;
and taking the map slice data as a reference base map, and three-dimensionally rendering the flight state of the target flight object at the copy time point.
9. A flight history duplication device is characterized by comprising:
the creating module is used for creating a corresponding and associated track object and flight object based on the acquired flight data, and correspondingly storing the track object and the flight object in a first container and a second container;
the filling module is used for filling the track points and the service data in the flight data into a data structure of the corresponding track object according to a time sequence;
the matching module is used for matching a target track object from the first container and matching a target flight object from the second container when a disk-copying instruction containing a disk-copying time point is received;
and the display module is used for displaying the target track according to the track point corresponding to the target track object, and dynamically displaying the target flight object from the time point of the flight duplication according to the track point corresponding to the target track object and the service data.
10. A computer device comprising a memory, a processor, and a computer program stored on the memory, wherein the computer program, when executed by the processor, performs the instructions of the method of any one of claims 1-8.
11. A computer storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor of a computer device, executes instructions of a method according to any one of claims 1-8.
CN202010979599.3A 2020-09-17 2020-09-17 Flight history duplication method, device, equipment and storage medium Pending CN112328572A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010979599.3A CN112328572A (en) 2020-09-17 2020-09-17 Flight history duplication method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010979599.3A CN112328572A (en) 2020-09-17 2020-09-17 Flight history duplication method, device, equipment and storage medium

Publications (1)

Publication Number Publication Date
CN112328572A true CN112328572A (en) 2021-02-05

Family

ID=74303834

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010979599.3A Pending CN112328572A (en) 2020-09-17 2020-09-17 Flight history duplication method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN112328572A (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113990111A (en) * 2021-10-20 2022-01-28 成都民航空管科技发展有限公司 Multi-data-source-based control operation situation double-disk analysis method and system
CN114390321A (en) * 2021-10-11 2022-04-22 北京仁光科技有限公司 Method and system for calling copy by signal source, readable storage medium and electronic equipment

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101465065A (en) * 2009-01-15 2009-06-24 北京航空航天大学 Method for obtaining flight current sample data
CN102074126A (en) * 2011-01-19 2011-05-25 清华大学 Historical radar data based air traffic flow analysis system and method
CN102375138A (en) * 2010-08-20 2012-03-14 中国民用航空华东地区空中交通管理局 Radar track and flight information comprehensive display system
CN102682628A (en) * 2012-05-04 2012-09-19 北京民航天宇科技发展有限公司 General aviation operation monitoring system
CN103699781A (en) * 2013-12-05 2014-04-02 中国水产科学研究院东海水产研究所 Method for tracing trawl fishing of beidou boat position
CN111652427A (en) * 2020-05-29 2020-09-11 航科院中宇(北京)新技术发展有限公司 Flight arrival time prediction method and system based on data mining analysis

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101465065A (en) * 2009-01-15 2009-06-24 北京航空航天大学 Method for obtaining flight current sample data
CN102375138A (en) * 2010-08-20 2012-03-14 中国民用航空华东地区空中交通管理局 Radar track and flight information comprehensive display system
CN102074126A (en) * 2011-01-19 2011-05-25 清华大学 Historical radar data based air traffic flow analysis system and method
CN102682628A (en) * 2012-05-04 2012-09-19 北京民航天宇科技发展有限公司 General aviation operation monitoring system
CN103699781A (en) * 2013-12-05 2014-04-02 中国水产科学研究院东海水产研究所 Method for tracing trawl fishing of beidou boat position
CN111652427A (en) * 2020-05-29 2020-09-11 航科院中宇(北京)新技术发展有限公司 Flight arrival time prediction method and system based on data mining analysis

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
申金星: "基于ADS-B多地面站的实时监视系统", 《中国优秀硕士学位论文全文数据库 工程科技Ⅱ辑》 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114390321A (en) * 2021-10-11 2022-04-22 北京仁光科技有限公司 Method and system for calling copy by signal source, readable storage medium and electronic equipment
CN113990111A (en) * 2021-10-20 2022-01-28 成都民航空管科技发展有限公司 Multi-data-source-based control operation situation double-disk analysis method and system

Similar Documents

Publication Publication Date Title
JP2024041823A (en) System and method for managing vehicle data
US20180225976A1 (en) Automated real-time clearance analysis for air traffic
CN112328572A (en) Flight history duplication method, device, equipment and storage medium
FR3061342A1 (en) MANAGING MESSAGES TO AERIAL NAVIGANTS
CN112449750A (en) Log data collection method, log data collection device, storage medium, and log data collection system
US9613447B2 (en) Identifying cyclic patterns of complex events
US11954317B2 (en) Systems and method for a customizable layered map for visualizing and analyzing geospatial data
US20200348148A1 (en) System and method for rendering dynamic data and controlling the visual form of the data on a cockpit display without altering the certified software
CN113259447B (en) Cloud platform deployment method and device, electronic equipment and storage medium
CN104504106A (en) Map covering region rendering method and related equipment
EP3734575A1 (en) System and method for rendering dynamic data and controlling the visual form of the data on a cockpit display without altering the certified software
CN111736994A (en) Resource arranging method, system, storage medium and electronic equipment
US10885797B2 (en) Methods and systems for managing drones with drone operating parameters
CN112231387A (en) Railway data visualization interaction system and method, electronic device and storage medium
CN109558143A (en) The method and device of application deployment in a kind of cluster
CN111951613B (en) Air-ground cooperative wide-area airspace security situation assessment method
CN113051031A (en) Container cluster deployment method of visual artificial intelligence system simulation platform
CN116166735B (en) Aviation data processing method and device, electronic equipment and storage medium
Gunawardena et al. Real-time Uber data analysis of popular Uber locations in Kubernetes environment
Weinert et al. Benchmarking the processing of aircraft tracks with triples mode and self-scheduling
CN115328452A (en) Navigation service operation management situation visualization method, system, server and storage medium
CN109871252A (en) A kind of cloud classroom universal disc implementation method
Zhang Specifying and modeling cloud cyber physical systems based on AADL
CN114564207A (en) Software product processing method and device, computer equipment and storage medium
Mehlitz et al. Analyzing airspace data with race

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20210205