Information processing device, information processing program, and information processing method

Abstract

To provide technology that facilitates the creation of flight logs even when operating multiple unmanned aircraft from different manufacturers.SOLUTION: An information processing device includes: an identification unit 3 that identifies an unmanned aircraft and flight plan information based on first relationship information associating airframe manufacturing information provided by a manufacturer of the unmanned aircraft, imaging device manufacturing information provided by an imaging device manufacturer, and airframe identification information, second relationship information concerning a flight schedule, and third relationship information associating metadata and image information captured by an imaging device mounted on the unmanned aircraft during takeoff and landing; a determination Unit 4 that determines the takeoff and landing times and locations of the unmanned aircraft based on the identified unmanned aircraft, the identified flight schedule information, and the image relationship information; and an output unit 5 that outputs a flight log concerning the identified unmanned aircraft based on the identified unmanned aircraft, the identified flight schedule information, the takeoff and landing times, and the shooting locations.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an information processing device, an information processing program, and an information processing method. [Background technology]

[0002] In recent years, unmanned aerial vehicles (UAVs), commonly known as drones, have been used in fields such as agriculture, surveying, material quantity measurement, inspection, maintenance, disaster investigation, etc. The following technologies have been disclosed regarding such UAVs.

[0003] For example, Patent Document 1 discloses a flight management system for actively managing the flights of unmanned aircraft. The flight management system includes a pre-flight risk calculation unit that calculates a pre-flight risk using flight risk-related information including flight plan information for the unmanned aircraft before the flight of the unmanned aircraft, a flight risk calculation unit that calculates a flight risk using flight record information and flight risk-related information for the unmanned aircraft during the flight of the unmanned aircraft, and a flight performance evaluation unit that evaluates the validity of the flight of the unmanned aircraft using the flight record information after the flight of the unmanned aircraft.

[0004] Furthermore, Patent Document 2 discloses a data recording method for easily acquiring location information indicating the locations where reference points are located. In this method, a mobile object equipped with an imaging device can acquire location information indicating its own current location, and records the data. First, the imaging device captures multiple aerial images from above an area where multiple reference points where the mobile object can land are located at predetermined intervals, in order to create three-dimensional data corresponding to the area. In parallel with capturing the aerial images, the mobile object lands at each of the multiple reference points, and records the location information after landing at the reference points. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Publication No. 2020-024475 [Patent Document 2] Japanese Patent Publication No. 2022-102366 Summary of the Invention [Problem to be solved by the invention]

[0006] When flying an unmanned aerial vehicle, the Aviation Act requires that a flight log be created for each individual aircraft. Therefore, a flight log must be created for each aircraft (registration number). The flight records in the flight log are also used to manage the pilot's individual flight time and show their career history.

[0007] Until now, the methods used have been to record flight data by hand in a paper flight logbook, or to manually input flight dates, times, and locations one by one into applications such as EXCEL (registered trademark) or online, and then record the data in a database, etc. However, such manual input work is time-consuming and labor-intensive, and inefficient, when the number of unmanned aerial vehicles being flown increases.

[0008] Furthermore, even if an attempt is made to build a UAS (Unmanned Aircraft System) to achieve automatic input, it is generally expected that it will be required to use unmanned aircraft from the same manufacturer with common specifications.

[0009] However, it is expected that additional equipment will be purchased as needed depending on the purchase price and timing. Assuming handwritten records in a paper flight logbook, it is expected that any equipment with a certain functionality will be purchased regardless of manufacturer. As a result, unmanned aircraft from multiple manufacturers will be operated. Examples of such operations include multiple pilots sharing and flying unmanned aircraft with the same registration number (such as aircraft owned by a company or organization), or a single pilot flying unmanned aircraft from multiple manufacturers (such as a multi-vehicle owner). Even in the former case, it is expected that multiple aircraft from different manufacturers will be handled. Therefore, it is necessary to manage multiple unmanned aircraft with different specifications, i.e., from different manufacturers, in a single system and create a flight logbook.

[0010] Therefore, the present invention provides a technology that allows for easy creation of a flight log even when operating multiple unmanned aerial vehicles from different manufacturers. [Means for solving the problem]

[0011] An information processing device according to one aspect of the present invention includes first relationship information in which aircraft manufacturing information for identifying an unmanned aircraft provided by a manufacturer is associated with imaging device manufacturing information for identifying an imaging device provided by a manufacturer of an imaging device mounted on the unmanned aircraft, and aircraft identification information for identifying the unmanned aircraft; second relationship information in which the aircraft manufacturing information is associated with a scheduled flight date and a scheduled takeoff time for the unmanned aircraft; and third relationship information in which image information captured in connection with takeoff or landing of the unmanned aircraft and meta information for the image information are associated, the meta information including the imaging device manufacturing information, the date of capture, and the time of capture. the flight logbook for the identified unmanned aerial vehicle based on the identified unmanned aerial vehicle, the identified flight schedule information, and the third relationship information; a determination unit for determining the time and location of takeoff and landing of the unmanned aerial vehicle based on the identified unmanned aerial vehicle, the identified flight schedule information, and the third relationship information; and an output unit for outputting a flight logbook for the identified unmanned aerial vehicle based on the identified unmanned aerial vehicle, the identified flight schedule information, the time of takeoff and landing, and the shooting location.

[0012] The identification unit is characterized in that it acquires, from the third relationship information, a third relationship information group that matches the aircraft identification information for the identified unmanned aerial vehicle and whose shooting date contained in the meta information matches the scheduled flight date of the identified flight schedule information, and whose shooting time contained in the meta information is between a first predetermined time before the scheduled takeoff time and a second predetermined time, as the target image relationship information group.

[0013] The determination unit is characterized in that, from the third relationship information having the earliest shooting time among the target image relationship information group, it determines the earliest shooting time as the takeoff time and the shooting position as the takeoff location, and from the third relationship information having the latest shooting time, it determines the latest shooting time as the landing time and the shooting position as the landing location.

[0014] The determination unit is characterized in that it determines the takeoff time and takeoff location, and the landing time and landing location of the unmanned aerial vehicle based on the appearance pattern of a predetermined symbol that appears in the image of the image information corresponding to the target image relationship information group and the meta information corresponding to the image information.

[0015] The determination unit is characterized in that it determines the takeoff time and takeoff location, and the landing time and landing location of the unmanned aerial vehicle based on altitude information or air pressure information contained in the meta information of the image information corresponding to the target image relationship information group.

[0016] An information processing program according to one aspect of the present invention is provided on a computer, the information processing program including: first relationship information associating aircraft manufacturing information for identifying an unmanned aircraft provided by a manufacturer, imaging device manufacturing information for identifying an imaging device provided by a manufacturer of an imaging device mounted on the unmanned aircraft, and aircraft identification information for identifying the unmanned aircraft; second relationship information associating the aircraft manufacturing information with a scheduled flight date and a scheduled takeoff time for the unmanned aircraft; and third relationship information associating image information taken in connection with the takeoff or landing of the unmanned aircraft and meta information for the image information, the meta information including the imaging device manufacturing information, the year of taking the image, and the aircraft identification information; The system executes an identification process to identify the unmanned aerial vehicle and flight schedule information of the unmanned aerial vehicle related to the image information based on the first relationship information, the second relationship information, and the third relationship information obtained from a storage unit that stores the first relationship information, the second relationship information, and the third relationship information, which includes the date, the time of shooting, and the location of shooting; a determination process to determine the time and location of takeoff and landing of the unmanned aerial vehicle based on the identified unmanned aerial vehicle, the identified flight schedule information, and the third relationship information; and an output process to output a flight logbook related to the identified unmanned aerial vehicle based on the identified unmanned aerial vehicle, the identified flight schedule information, the time of takeoff and landing, and the location of shooting.

[0017] In an information processing method according to one aspect of the present invention, a computer generates first relationship information that associates aircraft manufacturing information for identifying an unmanned aircraft provided by a manufacturer, imaging device manufacturing information for identifying an imaging device provided by a manufacturer of an imaging device mounted on the unmanned aircraft, and aircraft identification information for identifying the unmanned aircraft; second relationship information that associates the aircraft manufacturing information with a scheduled flight date and a scheduled takeoff time for the unmanned aircraft; and third relationship information that associates image information taken in connection with the takeoff or landing of the unmanned aircraft and meta information for the image information, wherein the meta information includes the imaging device manufacturing information, the date of taking the image, The system is characterized by performing an identification process to identify the unmanned aerial vehicle and flight schedule information of the unmanned aerial vehicle related to the image information based on the first relationship information, the second relationship information, and the third relationship information obtained from a storage unit that stores the first relationship information, the second relationship information, and the third relationship information, which includes the shooting time and the shooting location; a determination process to determine the takeoff and landing time and location of the unmanned aerial vehicle based on the identified unmanned aerial vehicle, the identified flight schedule information, and the third relationship information; and an output process to output a flight logbook related to the identified unmanned aerial vehicle based on the identified unmanned aerial vehicle, the identified flight schedule information, the takeoff and landing time, and the shooting location. [Effects of the Invention]

[0018] According to a technology relating to one aspect of the present invention, a flight log can be easily created even when operating multiple unmanned aerial vehicles from different manufacturers. [Brief explanation of the drawings]

[0019] [Figure 1] 1 is a diagram illustrating an information processing device according to one aspect of the present invention. [Figure 2] 1 is a diagram illustrating an example of the overall configuration of an unmanned aerial vehicle management system according to an embodiment of the present invention. [Figure 3] FIG. 2 is a diagram illustrating an example of a data structure of a database managed by a management server in this embodiment. [Figure 4]FIG. 1 is a diagram showing an example of a flow of aerial photography and uploading of the aerial photography data to a management server in this embodiment (Example 1). [Figure 5] FIG. 2 is a diagram showing an example of a flowchart of a flight logbook creation process in the present embodiment (Example 1). [Figure 6] 10 is an example of a flight logbook output as a report in this embodiment. [Figure 7] 10A and 10B are diagrams illustrating an example of a helipad in this embodiment (Example 2) and the angle of view of a camera when an unmanned aerial vehicle takes off and lands on the helipad. [Figure 8] FIG. 10 is a diagram showing an example of a flow of aerial photography and uploading of the aerial photography data to a management server in this embodiment (Example 2). [Figure 9] FIG. 10 is a diagram showing an example of a flowchart of a flight logbook creation process in this embodiment (Example 2). [Figure 10] FIG. 2 is a block diagram illustrating an example of the configuration of a hardware environment of a computer that executes a program according to the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0020] 1 is a diagram showing an information processing device according to one aspect of the present invention. The information processing device 1 includes a storage unit 2, an identification unit 3, a determination unit 4, and an output unit 5. An example of the information processing device 1 is a management server 12, which will be described later.

[0021] The storage unit 2 stores first relationship information, second relationship information, and third relationship information. An example of the first relationship information is the unmanned aerial vehicle management DB 52 described below. The first relationship information is information in which aircraft manufacturing information, imaging device manufacturing information, and aircraft identification information are related to each other. The aircraft manufacturing information (for example, the aircraft serial number described below or a combination of the aircraft manufacturer and the aircraft serial number) is information that identifies the unmanned aerial vehicle assigned by the manufacturer. The imaging device manufacturing information (for example, the camera serial number described below or a combination of the camera manufacturer and the camera serial number) is information that identifies the imaging device assigned by the manufacturer of the imaging device installed in the unmanned aerial vehicle. The aircraft identification information (for example, the unmanned aerial vehicle ID described below) is information that identifies the unmanned aerial vehicle.

[0022] An example of the second relationship information is the later-described flight schedule management DB 53. The second relationship information is information in which aircraft identification information is associated with the scheduled flight date and scheduled takeoff time for the unmanned aerial vehicle.

[0023] An example of the third relationship information is the image file management DB 54 described below. The third relationship information is information in which image information and meta information of the image information are related to each other. The image information is image information captured in connection with the takeoff or landing of the unmanned aerial vehicle. For example, the image information is image information captured by an imaging device mounted on the unmanned aerial vehicle during takeoff and landing, and is, for example, still image information or video image information. Furthermore, for example, the image information may be image information captured as a screenshot of the operation screen of a control terminal that controls the unmanned aerial vehicle. The meta information is information including imaging device manufacturing information, the date and time of the image capture, the time of the image capture, and the location of the image capture, and is, for example, Exif (Exchangeable Image File Format) information.

[0024] The identification unit 3 identifies the unmanned aerial vehicle and the flight schedule information of the unmanned aerial vehicle related to the image information based on the first relationship information, the second relationship information, and the third relationship information. An example of the identification unit 3 is the identification unit 43 described below.

[0025] The determination unit 4 determines the time and location of takeoff and landing of the unmanned aerial vehicle based on the identified unmanned aerial vehicle, the identified flight schedule information, and the third relationship information. An example of the determination unit 4 is a determination unit 44 described below.

[0026] The output unit 5 outputs a flight logbook for the identified unmanned aerial vehicle based on the identified unmanned aerial vehicle, the identified flight schedule information, the takeoff and landing times, and the imaging positions included in the meta information. An example of the output unit 5 is the output control unit 45 described below.

[0027] With this configuration, a flight log can be easily created even when operating multiple unmanned aircraft from different manufacturers. In other words, a flight log for an unmanned aircraft can be created using image information captured by the unmanned aircraft and its metadata, regardless of the specifications of the unmanned aircraft, so a flight log can be easily created even when flying unmanned aircraft from multiple different manufacturers. This makes it easy to create a flight log even when multiple pilots share and fly unmanned aircraft with the same registration number (such as aircraft owned by a company or organization) or when a single pilot flies unmanned aircraft from multiple different manufacturers (such as when owning multiple aircraft).

[0028] From the third relationship information, the identification unit 3 acquires, from among the third relationship information group (record group) that matches the aircraft identification information related to the identified unmanned aerial vehicle and whose shooting date included in the meta information matches the scheduled flight date included in the identified flight schedule information, the third relationship information group (record group) whose shooting time included in the meta information is between a first predetermined time before the scheduled takeoff time and a second predetermined time, as a target image relationship information group. For example, the first predetermined time = 5 minutes, 10 minutes, 15 minutes, etc., and the second predetermined time = "scheduled landing time - scheduled takeoff time + α" (α = 5 minutes, 10 minutes, 15 minutes, etc.).

[0029] By configuring it in this manner, it is possible to identify which unmanned aircraft the image information and its meta information belong to by comparing it with unmanned aircraft-related information, and it is also possible to identify which unmanned aircraft the image information and its meta information belong to by comparing it with flight schedule information.

[0030] The determination unit 4 may determine the earliest shooting time as the takeoff time and the shooting position as the takeoff location from the third relationship information having the earliest shooting time among the target image relationship information group, and may determine the latest shooting time as the landing time and the shooting position as the landing location from the third relationship information having the latest shooting time.

[0031] By configuring in this manner, the takeoff time and takeoff location, and the landing time and landing location can be determined from the identified unmanned aircraft and the record group identified from its flight schedule information.

[0032] The determination unit 4 determines the takeoff time and takeoff location, and the landing time and landing location of the unmanned aerial vehicle based on the appearance pattern of a predetermined symbol appearing in an image of the image information corresponding to the target image-related information group and the meta information corresponding to the image information. The predetermined symbol refers to, for example, a symbol that appears as a subject in an image when a two-dimensional code attached to a helipad is photographed. The symbol appearance pattern may be, for example, a takeoff appearance pattern in which, when multiple consecutive photographs are taken with the two-dimensional code as the subject, the two-dimensional code is recognizable by image recognition technology in the earliest photographed image, but becomes unrecognizable by image recognition technology in subsequent photographs (a takeoff appearance pattern). Alternatively, the two-dimensional code may be unrecognizable by image recognition technology in the earliest photographed image, but becomes recognizable by image recognition technology in subsequent photographs, and the two-dimensional code no longer moves on the screen (a landing appearance pattern).

[0033] By configuring it in this manner, image recognition technology can be used to determine whether an unmanned aircraft has taken off or landed, and if it is determined that it has taken off, the takeoff time and location of the unmanned aircraft can be determined from the image taken at that time, and if it is determined that it has landed, the landing time and location can be determined from the image taken at that time.

[0034] In addition, the determination unit 4 may determine the takeoff time and takeoff location, and the landing time and landing location of the unmanned aerial vehicle based on altitude information or air pressure information contained in the meta information of the image information corresponding to the target image related information group.

[0035] By configuring it in this way, the takeoff and landing of the unmanned aircraft can be determined using altitude or air pressure, and if it is determined that the unmanned aircraft has taken off, the takeoff time and takeoff location can be determined from images taken at that time, and if it is determined that the unmanned aircraft has landed, the landing time and landing location can be determined from images taken at that time.

[0036] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0037] 2 is a diagram showing an example of the overall configuration of an unmanned aerial vehicle management system in this embodiment. The unmanned aerial vehicle management system 11 includes a management server 12, an unmanned aerial vehicle 13, and a control terminal 14.

[0038] The control terminal 14 is a terminal device that allows the operator to wirelessly remotely control the unmanned aerial vehicle 13. The unmanned aerial vehicle 13 can fly based on control signals transmitted from the control terminal 14. The unmanned aerial vehicle 13 (UAV) may also be referred to as an aircraft, drone, multicopter, RPAS (Remote Piloted Aircraft Systems), UAS (Unmanned Aircraft Systems), or the like.

[0039] The unmanned aerial vehicle 13 includes, for example, a flight controller 21, a memory unit 22, a communication unit 23, four ESCs (Electronic Speed ​​Controllers) 24, four motors 25, four propellers 26, and a camera 27. In this embodiment, a quadcopter with four rotating propellers will be described as an example, but the invention is not limited to this, and may also be an unmanned aerial vehicle or a vertical take-off and landing aircraft (VTOL) with even more rotating propellers, such as a hexacopter or octocopter.

[0040] The flight controller 21 receives instructions from the control terminal 14 and sends commands to the ESC 24 to adjust the rotation speed of the motor 25, thereby controlling the flight of the unmanned aerial vehicle 13. The ESC 24 can adjust the rotation speed of the motor 25 with the correct voltage, and rotates the motor 25 in accordance with commands from the flight controller 21. The propeller 26 provides lift and propulsion to the unmanned aerial vehicle 13 body, and is rotated by the motor 25.

[0041] Storage unit 22 is a storage device that processes image files captured by camera 27 and stores them in storage unit 22. Storage unit 22 may be, for example, a recording medium that reads and writes data using a built-in flash memory, or may be a removable storage medium such as an SD card.

[0042] The camera 27 is a camera incorporating a CCD (Charge Coupled Device). The camera 27 has a GNSS (Global Navigation Satellite System) function. The camera 27 is mounted on the unmanned aerial vehicle 13 via a gimbal, and the orientation of the camera 27 relative to the main body of the unmanned aerial vehicle 13 can be changed.

[0043] The camera 27 can record shooting information (meta information) indicating the circumstances and settings at the time of shooting together with the image data in an Exif (Exchangeable Image File Format) header, etc. The meta information includes, for example, the shooting date and time, the latitude and longitude recorded by GNSS, the manufacturer name (manufacturer / distributor) of the camera 27, and the camera model name.

[0044] It is also possible to mount an altimeter (barometer) on camera 27 or unmanned aerial vehicle 13, and set the altitude (or air pressure) at the time an image is captured in the meta information of that image.

[0045] When an image file taken by the unmanned aerial vehicle 13 is input, the management server 12 creates a flight log relating to the flight of the unmanned aerial vehicle 13 based on the image file. The management server 12 includes a control unit 41 and a memory unit 51. Note that hereinafter, the "database" will be referred to as "DB."

[0046] The memory unit 51 stores, for example, an unmanned aerial vehicle management DB 52, a flight schedule management DB 53, an image file management DB 54, and a flight record DB 55. The unmanned aerial vehicle management DB 52 is a database that manages unmanned aerial vehicles 13 individually. The flight schedule management DB 53 is a database that manages information necessary for creating flight records, such as flight overviews. The image file management DB 54 is a database that manages image files taken from the air by unmanned aerial vehicles. The flight record DB 55 is a database that manages flight records.

[0047] The control unit 41 is a processor that controls the entire management server 12, and functions as an acquisition unit 42, an identification unit 43, a determination unit 44, and an output control unit 45 by reading and executing the program related to this embodiment from the memory unit 51.

[0048] The acquisition unit 42 acquires commands or information input by the user. For example, when the user inputs information about the unmanned aerial vehicle 13, the camera mounted thereon, and flight schedule information, the acquisition unit 42 acquires the information and registers it in the corresponding database. Furthermore, when the user inputs an image file obtained by aerial photography using the unmanned aerial vehicle 13, the acquisition unit 42 stores the image file in the image file management DB 54.

[0049] The identification unit 43 identifies the unmanned aerial vehicle 13 that captured the image information and its flight schedule information based on the unmanned aerial vehicle management DB 52, the flight schedule management DB 53, and the image file management DB 54. That is, the identification unit 43 can identify which unmanned aerial vehicle the image file belongs to by comparing it with the unmanned aerial vehicle management DB 52. The identification unit 43 can also identify which unmanned aerial vehicle the image file belongs to by comparing it with the flight schedule information. The identification unit 43 registers the identified information in the flight record DB 55.

[0050] The determination unit 44 determines the time and place of takeoff and landing of the unmanned aerial vehicle based on the identified unmanned aerial vehicle, the identified flight schedule information, and the image file management DB 54. The determination unit 44 registers information related to the determined time and place of takeoff and landing in the flight record DB 55.

[0051] For example, the determination unit 44 may acquire a group of records from the image file management DB 54 based on the identified unmanned aerial vehicle and the identified flight schedule information, and determine the earliest shooting time from the record with the earliest shooting time as the takeoff time and the shooting location as the takeoff location, and the latest shooting time from the record with the latest shooting time as the landing time and the shooting location as the landing location.

[0052] In addition, the determination unit 44 acquires a group of records from the image file management DB 54 based on the identified unmanned aircraft and the identified flight schedule information, and determines the takeoff time and takeoff location, and the landing time and landing location of the unmanned aircraft based on the appearance pattern of a predetermined symbol that appears in the image of the image information corresponding to the group of records and the meta information corresponding to the image information.

[0053] The output control unit 45 generates a flight record based on the information registered in the flight record DB 55, and can display the generated flight record on a display device or output it as a report to a printer.

[0054] 3 is a diagram showing an example of the data structure of a database managed by the management server 12 in this embodiment. In this embodiment, a unit of related information managed in each database is called a "record." Note that the database structure described below is an example and is not limited to this.

[0055] The unmanned aerial vehicle management DB 52 includes data items such as "unmanned aerial vehicle ID," "registration code," "aircraft manufacturer," "aircraft serial number," "camera manufacturer," "camera serial number," and "total flight time." The item "unmanned aerial vehicle ID" stores identification information (unmanned aerial vehicle ID) that identifies the unmanned aerial vehicle. The item "registration code" stores the registration code of the unmanned aerial vehicle notified by the Minister of Land, Infrastructure, Transport and Tourism. The item "aircraft manufacturer" stores information that identifies the manufacturer of the unmanned aerial vehicle. The item "aircraft serial number" stores the serial number of the unmanned aerial vehicle 13 assigned by the manufacturer of the unmanned aerial vehicle. The item "camera manufacturer" stores information that identifies the manufacturer of the camera installed in the unmanned aerial vehicle. The item "camera serial number" stores the serial number of the aerial photography camera 27 installed in the unmanned aerial vehicle 13 assigned by the camera manufacturer. The item "total flight time" stores the total flight time of the unmanned aerial vehicle 13.

[0056] The flight schedule management DB53 includes data items such as "unmanned aircraft ID," "planned flight date," "name of person operating the aircraft," "flight summary," "planned takeoff time," and "planned landing time." The item "unmanned aircraft ID" stores identification information (unmanned aircraft ID) that identifies the unmanned aircraft. The item "planned flight date" stores the planned flight date of the unmanned aircraft 13. The item "name of person operating the aircraft" stores the name of the person who plans to operate the unmanned aircraft 13. The item "flight summary" stores a summary of the flight, such as the purpose of the flight and route information such as waypoints. The item "planned takeoff time" stores the planned takeoff time of the unmanned aircraft 13. The item "planned landing time" stores the planned landing time of the unmanned aircraft 13.

[0057] The image file management DB 54 stores, for example, unmanned aerial vehicle IDs and image files in association with each other. The item "unmanned aerial vehicle ID" stores identification information (unmanned aerial vehicle ID) that identifies the unmanned aerial vehicle. An image file includes header information, thumbnail image data of the image data (e.g., JPEG format, PNG format, etc.), and the image data itself (e.g., JPEG format, PNG format, etc.). The header information stores meta information of the image data in a format that complies with the Exchangeable Image File Format (Exif). The header information includes, as meta information, for example, "camera manufacturer," "camera serial number," "photograph date," "photograph time," "photograph location," "image data name," and "storage location." The item "camera manufacturer" stores information that identifies the manufacturer of the camera installed in the unmanned aerial vehicle. The item "camera serial number" stores the serial number of the aerial photography camera 27 installed in the unmanned aerial vehicle 13, assigned by the camera manufacturer. The item "photograph date" stores the date the image was taken. The item "photograph time" stores the time the image was taken. The item "photography location" stores the location (latitude, longitude) of the photography location.

[0058] The flight record DB 55 includes data items such as "unmanned aircraft ID," "registration code," "flight date," "name of person who flew," "flight summary," "takeoff location," "landing location," "takeoff time," "landing time," "flight duration," "total flight duration," and "matters that affected flight safety." The item "unmanned aircraft ID" stores identification information (unmanned aircraft ID) that identifies the unmanned aircraft. The item "registration code" stores the registration code of the unmanned aircraft notified by the Minister of Land, Infrastructure, Transport and Tourism. The item "flight date" stores the flight date of the unmanned aircraft 13. The item "name of person who flew the unmanned aircraft 13" stores the name of the person who flew the unmanned aircraft 13. The item "flight summary" stores a summary of the flight, such as the purpose of the flight and route information such as stopover points. The item "takeoff location" stores the takeoff position (latitude, longitude) of the unmanned aircraft 13. The item "landing location" stores the landing position (latitude, longitude) of the unmanned aircraft 13. The item "takeoff time" stores the takeoff time of the unmanned aerial vehicle 13. The item "landing time" stores the landing time of the unmanned aerial vehicle 13. The item "flight time" stores the flight time of the unmanned aerial vehicle 13. The item "total flight time" stores the total flight time of the unmanned aerial vehicle 13. The item "matters that affected flight safety" stores matters that affected flight safety.

[0059] An example of a variation of the embodiment of this embodiment will be described below.

[0060] 4 is a diagram showing an example of the flow of aerial photography and uploading of the aerial photography data to the management server in this embodiment (Example 1). First, the user uses an input device to register the registration code, aircraft manufacturer, aircraft serial number, camera manufacturer, and camera serial number of the unmanned aircraft 13 to be used in the unmanned aircraft management DB 52 of the management server 12 (S1). At this time, "0" is stored as the default in the "total flight time" field corresponding to the registered unmanned aircraft 13 in the unmanned aircraft management DB 52. Note that the unmanned aircraft ID is assigned unique information in the unmanned aircraft management system 11.

[0061] The user uses the input device to register flight schedule information for the unmanned aircraft 13 in the flight schedule management DB 53 of the management server 12 (S2). The flight schedule information includes the unmanned aircraft ID of the unmanned aircraft 13, the scheduled flight date, the name of the pilot, a flight summary, the scheduled takeoff time, the scheduled landing time, etc.

[0062] The user then actually flies the unmanned aerial vehicle 13 to take aerial photographs. At this time, the user first takes a photograph using the control terminal 14 in response to or while performing the takeoff operation of the unmanned aerial vehicle 13 (S3). If the unmanned aerial vehicle 13 does not have an automatic photography start function, the user may perform the takeoff operation after taking a photograph. Here, the object is to collect meta information of the image at the time of photography, so the subject is not limited.

[0063] Thereafter, the user takes a photograph using the control terminal 14 in response to the landing operation or while performing the takeoff operation of the unmanned aerial vehicle 13 (S4). If the unmanned aerial vehicle 13 does not have an automatic shooting start function, the user may perform the landing operation after taking a photograph. Here, the purpose is to collect meta information of the image at the time of shooting, so the subject is not limited.

[0064] After the flight of the unmanned aerial vehicle 13 has ended, the user uploads the captured image files to the management server 12 (S5). The captured image files are stored in the memory unit 22 of the unmanned aerial vehicle 13. The image files stored in the memory unit 22 may be uploaded to the management server 12 via a wired connection such as a USB (Universal Serial Bus) cable or wirelessly such as Bluetooth. Alternatively, if the memory unit 22 is a removable SD card or the like, the SD card may be read by an SD card reader of the management server 12 and uploaded to the management server 12. Note that depending on the model of the unmanned aerial vehicle 13, the images may be automatically uploaded to the management server 12.

[0065] FIG. 5 is a diagram illustrating an example of a flowchart of a flight logbook creation process in this embodiment (example 1).

[0066] The management server 12 acquires one image file from the multiple uploaded image files (S11). The management server 12 acquires an unmanned aerial vehicle ID corresponding to the combination of the camera manufacturer and camera serial number of the acquired image file from the unmanned aerial vehicle management DB 52 (S12). The management server 12 associates the acquired image file with the acquired unmanned aerial vehicle ID and registers them in the image file management DB 54 (S13). The management server 12 repeats the processes of S11 to S13 for the number of uploaded image files.

[0067] Next, the management server 12 acquires one unprocessed record (S14) from the flight schedule management DB 53. The management server 12 acquires the unmanned aerial vehicle ID, the scheduled flight date, the scheduled takeoff time, and the scheduled landing time from the acquired record.

[0068] The management server 12 acquires from the image file management DB 54 a group of unprocessed records whose image capture times are between a first predetermined time before the scheduled takeoff time and a second predetermined time from a group of records whose image capture dates match the acquired unmanned aerial vehicle ID and whose image capture dates match the scheduled flight date (S15). Here, for example, the first predetermined time is set to "10 minutes" and the second predetermined time is set to "scheduled landing time - scheduled takeoff time + 10 minutes." Note that if each unmanned aerial vehicle is operated so that it flies only once a day, the management server 12 may acquire from the image file management DB 54 a group of unprocessed records whose image capture dates match the acquired unmanned aerial vehicle ID and whose image capture dates match the scheduled flight date.

[0069] The management server 12 acquires the earliest photographing time as the takeoff time and the photographing position as the takeoff location from the record having the earliest photographing time among the acquired records, and acquires the latest photographing time as the landing time and the photographing position as the landing location from the record having the latest photographing time (S16).

[0070] The management server 12 calculates the flight time by subtracting the earliest image capture time (takeoff time) from the latest image capture time (landing time) (S17). The management server 12 acquires the registration code and total flight time contained in the record corresponding to the acquired unmanned aerial vehicle ID from the unmanned aerial vehicle management DB 52 (S18). The management server 12 adds the flight time calculated in S17 to the acquired total flight time to calculate a new total flight time (S19).

[0071] The management server 12 acquires the "name of the person who flew the aircraft" and "flight summary" from the record acquired in S14 from the flight schedule management DB 53 (S20). The management server 12 registers the information acquired from each database (unmanned aircraft ID, registration code, shooting date, name of the person who flew the aircraft, flight summary, takeoff location, landing location, takeoff time, landing time) and calculated information (flight time, total flight time) in the flight record DB 55 (S21).

[0072] The management server 12 updates the "total flight time" included in the target record of the unmanned aerial vehicle management DB 52 (i.e., the record read out in S18) with the new total flight time calculated in S19 (S22).

[0073] The management server 12 repeats the processes of S14 to S22 for the number of record groups acquired from the image file management DB 54 corresponding to the unprocessed records acquired in S14. As a result, flight logbook information is generated in the flight record DB 55.

[0074] The management server 12 outputs (S23) the flight log based on the flight record DB 55. The flight log may be displayed on a display or may be printed out as a form using a printer.

[0075] 6 is an example of a flight logbook output as a form in this embodiment. In addition to the "registration code of the unmanned aerial vehicle," "date of flight," "name of the person who flew the flight," "flight summary," "takeoff location," "landing location," "takeoff time," "landing time," "flight duration," "total flight duration," and "matters that affected flight safety," the flight logbook also includes information about the malfunction and its handling, such as "date of occurrence," "malfunction," "treatment and other details," and "person who confirmed it."

[0076] If necessary, information such as "items that affected flight safety," "date of occurrence," "defects," "treatments and other matters," and "person who confirmed them" can be entered on a management screen (not shown) and registered in the flight record DB 55.

[0077] According to the first embodiment, by utilizing the meta information of the image file, flight logs for unmanned aircraft of different manufacturers can be efficiently created without depending on the specifications of the unmanned aircraft of different manufacturers.

[0078] In the first embodiment, the "takeoff location" and "landing location" are respectively represented by latitude and longitude information measured by GNSS, but this is not limiting. The latitude and longitude information may be converted into address information or a place name on map information by reverse geocoding. The address information may be, for example, a prefecture name + city / ward / county name + town / village name (block number, house number, etc. may be added as needed). The place name on map information may be, for example, a proper noun such as XX playground, XX park, XX factory, etc.

[0079] Furthermore, the image data may be not only still images but also moving images. In this case, the header information may store meta information (meta information) of the moving image data in a format conforming to Exif. That is, in the case of moving images, for example, the shooting start time may be the takeoff time, the shooting start time may be the landing time, the shooting start position may be the takeoff location, and the shooting end position may be the landing location.

[0080] Next, as a second embodiment, an example of creating a flight logbook using image processing technology that determines the takeoff and landing of an unmanned aerial vehicle based on whether or not a two-dimensional code attached to a helipad is recognized will be described. In the second embodiment, the unmanned aerial vehicle management system 11 is also used. In the second embodiment, the same mechanisms, configurations, or processes as those in the first embodiment are denoted by the same reference numerals as those in the first embodiment, and their description will be omitted.

[0081] 7 is a diagram illustrating an example of a helipad in this embodiment (Example 2) and the angle of view of the camera when the unmanned aerial vehicle takes off and lands on the helipad. A helipad is generally a place where helicopters take off and land, but in Example 2, it is a simple sheet that can be installed and removed sequentially for the unmanned aerial vehicle 13 to take off and land.

[0082] As shown in Figure 7(A), the helipad 61 in Example 2 has one or more two-dimensional codes 62 attached thereto. The two-dimensional codes 62 may be printed on the helipad or attached to the helipad. In Example 2, a sticker with the two-dimensional code 62 printed thereon is attached to an existing helipad sheet.

[0083] As shown in Figure 7(B), the two-dimensional code 62 is placed on the helipad 61 at a position that moves in and out of the field of view of the camera 27 depending on the takeoff and landing of the unmanned aerial vehicle 13.

[0084] 8 is a diagram showing an example of the flow of aerial photography and uploading of the aerial photography data to the management server in this embodiment (Example 2). First, the user uses an input device to register the registration code, aircraft manufacturer, aircraft serial number, camera manufacturer, and camera serial number of the unmanned aircraft 13 to be used in the unmanned aircraft management DB 52 of the management server 12 (S31). At this time, "0" is stored as the default in the "total flight time" field corresponding to the registered unmanned aircraft 13 in the unmanned aircraft management DB 52. Note that the unmanned aircraft ID is assigned unique information in the unmanned aircraft management system 11.

[0085] The user uses the input device to register flight schedule information for the unmanned aircraft 13 in the flight schedule management DB 53 of the management server 12 (S32). The flight schedule information includes the unmanned aircraft ID of the unmanned aircraft 13, the scheduled flight date, the name of the pilot, a flight summary, the scheduled takeoff time, the scheduled landing time, etc.

[0086] Then, before takeoff, the user places the unmanned aerial vehicle 13 in the center of the helipad 61 and affixes a sticker with a two-dimensional code 62 printed on it in a position that will be within the field of view of the camera 27 (S33).

[0087] Then, the user actually flies the unmanned aerial vehicle 13 to take aerial photographs. At this time, the user first takes multiple photographs while operating the unmanned aerial vehicle 13 to take off using the control terminal 14, and then causes the unmanned aerial vehicle 13 to take off from the helipad 61 (S34). If the unmanned aerial vehicle 13 does not have an automatic photography start function, the user may take multiple photographs while operating the unmanned aerial vehicle 13 to take off.

[0088] Thereafter, the user takes multiple photographs while performing landing operations on the unmanned aerial vehicle 13 using the control terminal 14, and lands the unmanned aerial vehicle 13 near the center of the helipad 61 (S35). Note that if the unmanned aerial vehicle 13 does not have an automatic photography start function, the user may take multiple photographs while performing landing operations.

[0089] After the flight of the unmanned aerial vehicle 13 has ended, the user uploads the captured image files to the management server 12 (S36). The captured image files are stored in the memory unit 22 of the unmanned aerial vehicle 13. The image files stored in the memory unit 22 may be uploaded to the management server 12 via a wired connection such as a USB (Universal Serial Bus) cable or wirelessly such as Bluetooth. Alternatively, if the memory unit 22 is a removable SD card or the like, the SD card may be read by an SD card reader of the management server 12 and uploaded to the management server 12. Note that depending on the model of the unmanned aerial vehicle 13, the images may be automatically uploaded to the management server 12.

[0090] Fig. 9 is a diagram showing an example of a flowchart of a flight logbook creation process in this embodiment (Example 2). In Fig. 9, the processes of S11 to S13 and S23 are the same as those in Fig. 5, and therefore the description thereof will be omitted.

[0091] After the processes of S11 to S13, the management server 12 acquires (S41) one unprocessed record from the flight schedule management DB 53. The management server 12 acquires the unmanned aerial vehicle ID and the scheduled flight date from the acquired record.

[0092] The management server 12 acquires from the image file management DB 54 a group of unprocessed records that match the acquired unmanned aerial vehicle ID and whose photography date matches the scheduled flight date (S42). As described in S15 of Fig. 5, from the image file management DB 54, it is also possible to acquire a group of unprocessed records whose photography time falls within a first predetermined time to a second predetermined time before the scheduled takeoff time, from the group of records that match the acquired unmanned aerial vehicle ID and whose photography date matches the scheduled flight date.

[0093] The management server 12 reads out image data corresponding to the earliest record from the acquired record group (S43), and determines whether or not the two-dimensional code 62 is present in the read image data (S44).

[0094] The management server 12 reads out the image data of the next earliest record from the acquired record group until it recognizes the two-dimensional code 62 in the read image data (NO in S44, S43). Note that if the two-dimensional code 62 cannot be recognized in the acquired record group, the process returns to S41.

[0095] If the two-dimensional code 62 is recognized in the read image data (YES in S44), the management server 12 reads image data corresponding to the next earliest record from the acquired record group (S45).The management server 12 determines whether the two-dimensional code 62 is present in the read image data (S46).

[0096] While the management server 12 is recognizing the two-dimensional code 62 in the read image data, it reads out image data of the next earliest record from the acquired record group (NO in S46, S45).

[0097] If the two-dimensional code 62 cannot be recognized in the read image data (YES in S46), the management server 12 obtains the shooting time as the takeoff time and the location information as the takeoff location from the meta information of the image data (S47).

[0098] The management server 12 reads out image data corresponding to the next earliest record from the acquired record group (S48). The management server 12 determines whether a two-dimensional code has been recognized from the read image and whether the movement of the two-dimensional code has stopped within the image (S49).

[0099] The management server 12 reads out the image data of the next earliest record from the acquired record group until it recognizes that the two-dimensional code has stopped moving in the image and recognizes that the two-dimensional code has stopped moving in the image (NO in S49, S48).

[0100] If a two-dimensional code is recognized from the read image and the stop of movement of the two-dimensional code within the image is recognized (YES in S49), the management server 12 obtains the shooting time as the landing time and the location information as the landing location from the meta information of the image data (S50).

[0101] The management server 12 calculates the flight time by subtracting the takeoff time from the landing time (S51). The management server 12 acquires the registration code and total flight time contained in the record corresponding to the acquired unmanned aerial vehicle ID from the unmanned aerial vehicle management DB 52 (S52). The management server 12 adds the flight time calculated in S51 to the acquired total flight time to calculate a new total flight time (S53).

[0102] The management server 12 acquires the "name of the person who flew the aircraft" and "flight summary" from the record acquired in S14 from the flight schedule management DB 53 (S54). The management server 12 registers the information acquired from each database (unmanned aircraft ID, registration code, shooting date, name of the person who flew the aircraft, flight summary, takeoff location, landing location, takeoff time, landing time) and calculated information (flight time, total flight time) in the flight record DB 55 (S55).

[0103] The management server 12 updates the "total flight time" included in the target record of the unmanned aerial vehicle management DB 52 (i.e., the record read out in S18) with the new total flight time calculated in S53 (S56).

[0104] The management server 12 determines whether or not there are any records in the record group that have not yet been read (S57). If there are any records in the record group that have not yet been read (YES in S57), the process returns to S43. If all records included in the record group have been read (NO in S57), the process from S41 onwards is carried out for the next record group.

[0105] The management server 12 repeats the processes of S41 to S56 for the number of record groups acquired from the image file management DB 54 corresponding to the unprocessed records acquired in S41. As a result, flight logbook information is generated in the flight record DB 55.

[0106] The management server 12 outputs (S23) the flight log based on the flight record DB 55. The flight log may be displayed on a display or may be printed out as a form using a printer.

[0107] In the processes of S43 to S47, an appearance pattern (takeoff appearance pattern) is detected in which the two-dimensional code was recognizable by image recognition technology in the earliest captured image, but became unrecognizable by image recognition technology in subsequently captured images. In addition, in the processes of S48 to S50, an appearance pattern (landing appearance pattern) is detected in which the two-dimensional code was unrecognizable by image recognition technology in the earliest captured image, but became recognizable by image recognition technology in subsequently captured images, and the two-dimensional code stopped moving on the screen. However, the detection pattern for the two-dimensional code is not limited to this. For example, the direction in which the two-dimensional code moves in consecutive images may be detected. For example, if a two-dimensional code in one image of consecutively captured photos moves downward in the next image and then disappears off the screen in the next image, it can be determined that the unmanned aerial vehicle has taken off. In addition, if a two-dimensional code in an image taken at one point in time moves upward and stops in the next image taken at the same time, it can be determined that the unmanned aerial vehicle has landed.

[0108] According to Example 2, the takeoff and landing of an unmanned aircraft can be determined by whether or not the two-dimensional code contained in the image data is recognized, so that flight logs for unmanned aircraft from different manufacturers can be efficiently created without depending on the specifications of unmanned aircraft from different manufacturers.

[0109] Although a two-dimensional code is used in the second embodiment, the present invention is not limited to this and may be a figure, mark, etc. that can be recognized by the management server. Furthermore, when the management server 12 reads a two-dimensional code in an image, location information (latitude, longitude) of the location where the two-dimensional code is installed may be embedded.

[0110] In another embodiment, if the camera 27 or the unmanned aerial vehicle 13 also has an altimeter (or barometer) function and can include altitude (or air pressure) in the meta information, the takeoff or landing of the unmanned aerial vehicle may be determined based on the detected altitude (or air pressure) value. For example, a photograph is taken before takeoff, and another photograph is taken after takeoff. A photograph is also taken upon landing. Then, for example, if the difference between the altitude (or air pressure) at a certain point in time when a photograph is taken and the altitude (or air pressure) at the time when a photograph is taken before takeoff is equal to or greater than a predetermined value (e.g., 0.5 m), the unmanned aerial vehicle may be determined to have taken off. Also, for example, if the difference between the altitude (or air pressure) at a certain point in time when a photograph is taken and the altitude (or air pressure) at the time when a photograph is taken before takeoff is less than a predetermined value (e.g., 0.5 m) or is 0, the unmanned aerial vehicle may be determined to have landed.

[0111] In another embodiment, the control terminal (transmitter) may have a GNSS function, a photographing function (equipped with a camera), a display function (equipped with a display), and a recording function, and may capture a screenshot of the control terminal screen in response to takeoff and landing operations, thereby acquiring the image file. Specifically, when a takeoff operation (or landing operation) is performed using the control device provided on the control terminal, a screenshot of the control terminal's display screen is captured in conjunction with the operation. The captured image is recorded on an SD card detachable from the control terminal. Meta information for the captured image includes the date and time of capture and the location information (latitude and longitude) of the control terminal. This allows, for example, even for a pesticide sprayer not equipped with a camera, the flight start and end times, latitude, and longitude can be obtained from the meta information in the image file. Applying the first embodiment, a user may upload the captured image file to the management server 12 (S5 in FIG. 4). As a result, the processing of FIG. 5 can be performed, similar to the first embodiment.

[0112] 10 is an example of a configuration block diagram of a hardware environment of a computer that executes a program in this embodiment. The computer 201 is, for example, the management server 12. The computer 201 is configured with a CPU 202, a ROM 203, a RAM 204, a storage device 205, an input I / F 206, an output I / F 207, a communication I / F 208, a reading device 209, and a bus 210.

[0113] Here, CPU (Central Processing Unit) refers to a central processing unit. ROM refers to read-only memory. RAM refers to random access memory. I / F refers to an interface. A CPU 202, ROM 203, RAM 204, a storage device 205, an input I / F 206, an output I / F 207, a communication I / F 208, and, if necessary, a reading device 209 may be connected to the bus 210.

[0114] The CPU 202 reads the program according to this embodiment from the storage device 205, and when functioning as the management server 12, for example, executes the program as an acquisition unit 42, an identification unit 43, a decision unit 44, and an output control unit 45. The ROM 203 is a read-only memory. The RAM 204 is a memory for temporary storage.

[0115] The storage device 205 is a device that stores large amounts of information. Various types of storage devices can be used as the storage device 205, such as a hard disk, a solid state drive (SSD), or a flash memory card. The storage device 205 stores programs according to the embodiments of the present invention, as well as various databases and data stored in the storage unit 51.

[0116] The input I / F 206 can be connected to input devices such as a keyboard, a mouse, an electronic camera, a web camera, a microphone, a scanner, a sensor, a tablet, a touch panel, an information reading device, etc. The output I / F 207 can be connected to output devices such as a display, a touch panel, a projector, a printer, a speaker, etc.

[0117] The communication I / F 208 is an interface such as a port for connecting to a communication network and communicating with other devices. The communication network may be the Internet, a local area network (LAN), a wide area network (WAN), a dedicated line, a wired line, a wireless line, etc. The reading device 209 is a device for reading portable recording media.

[0118] The program for realizing the processes described in the above embodiments may be stored in, for example, the storage device 205 from a program provider via a communication network and the communication I / F 208. The program for realizing the processes described in the above embodiments may also be stored in a commercially available portable storage medium. In this case, the portable storage medium may be set in the reading device 209, and the program may be read and executed by the CPU 202. Various types of storage media can be used as the portable storage medium, such as a CD-ROM, a flexible disk, an optical disk, a magneto-optical disk, an IC card, a USB memory device, or a semiconductor memory card. The program stored in such a storage medium is read by the reading device 209.

[0119] Furthermore, the program may be installed on a stand-alone computer, or may be installed by a cloud computer and provide only its functions to the user.

[0120] According to this embodiment, a flight logbook can be easily created even when operating multiple unmanned aircraft from different manufacturers. In other words, even when operating multiple commercially available unmanned aircraft with different specifications, a flight logbook can be easily created without making any special adjustments to each unmanned aircraft.

[0121] This aspect has been described above based on embodiments and modifications. However, the above-described embodiments are intended to facilitate understanding of this aspect and are not intended to limit this aspect. This aspect may be modified or improved without departing from the spirit and scope of the claims, and equivalents thereof are included in this aspect. Furthermore, if a technical feature is not described as essential in this specification, it may be deleted as appropriate. [Explanation of symbols]

[0122] 1. Information processing equipment 2 Storage area 3 Specific part 4 Decision Section 5 Output section 11 Unmanned Aerial Vehicle Management System 12 Management Server 13 Unmanned aerial vehicle 14 Control terminal 21 Flight Controller 22 Memory section 23 Communications Department 24 ESC 25 motor 26 propeller 27 Camera 41 Control Unit 42 Analysis Department 43 Output section 51 Storage section 52 Unmanned aircraft management DB 53 Flight Schedule Management DB 54 Image file management database 55 Flight Record DB 61 Helipad 62 2D Code

Claims

1. a storage unit for storing first relationship information that associates aircraft manufacturing information for identifying the unmanned aircraft provided by a manufacturer, imaging device manufacturing information for identifying the imaging device provided by the manufacturer of an imaging device mounted on the unmanned aircraft, and aircraft identification information for identifying the unmanned aircraft; second relationship information that associates the aircraft manufacturing information with a scheduled flight date and scheduled takeoff time for the unmanned aircraft; and third relationship information that associates image information taken in connection with the takeoff or landing of the unmanned aircraft and meta information of the image information, the meta information including the imaging device manufacturing information, the date and time of the image, and the location of the image; an identification unit that identifies the unmanned aerial vehicle and flight schedule information of the unmanned aerial vehicle related to the image information based on the first relationship information, the second relationship information, and the third relationship information; a determination unit that determines a time and location for takeoff and landing of the unmanned aerial vehicle based on the identified unmanned aerial vehicle, the identified flight schedule information, and the third relationship information; an output unit that outputs a flight logbook related to the identified unmanned aerial vehicle based on the identified unmanned aerial vehicle, the identified flight schedule information, the takeoff and landing times, and the photographing location; An information processing device comprising:

2. The identification unit acquires, from the third relationship information, a third relationship information group that matches the aircraft identification information related to the identified unmanned aerial vehicle and whose shooting date included in the meta information matches the scheduled flight date of the identified flight schedule information, and whose shooting time included in the meta information is within a first predetermined time to a second predetermined time before the scheduled takeoff time, as a target image relationship information group.

2. The information processing apparatus according to claim 1, wherein:

3. The determination unit determines, from third relationship information having an earliest shooting time among the target image relationship information group, the earliest shooting time as the takeoff time and the shooting position as the takeoff location, and from third relationship information having a latest shooting time, the latest shooting time as the landing time and the shooting position as the landing location.

3. The information processing apparatus according to claim 2, wherein:

4. The determination unit determines a takeoff time and a takeoff location and a landing time and a landing location of the unmanned aerial vehicle based on an appearance pattern of a predetermined symbol appearing in an image of image information corresponding to the target image-related information group and the meta information corresponding to the image information.

3. The information processing apparatus according to claim 2, wherein:

5. The determination unit determines the takeoff time and takeoff location and the landing time and landing location of the unmanned aerial vehicle based on altitude information or atmospheric pressure information included in meta information of image information corresponding to the target image-related information group.

3. The information processing apparatus according to claim 2, wherein:

6. On the computer, an identification process for identifying the unmanned aerial vehicle and flight schedule information of the unmanned aerial vehicle related to the image information based on the first relationship information, the second relationship information, and the third relationship information obtained from a storage unit that stores: first relationship information that associates aircraft manufacturing information that identifies the unmanned aerial vehicle and is assigned by a manufacturer, imaging device manufacturing information that identifies the imaging device assigned by a manufacturer of the imaging device installed on the unmanned aerial vehicle, and aircraft identification information that identifies the unmanned aerial vehicle; second relationship information that associates the aircraft manufacturing information with a scheduled flight date and a scheduled takeoff time for the unmanned aerial vehicle; and third relationship information that associates image information taken in connection with the takeoff or landing of the unmanned aerial vehicle and meta information of the image information, the meta information including the imaging device manufacturing information, the date and time of the image, and the location of the image; a determination process for determining a time and location for takeoff and landing of the unmanned aerial vehicle based on the identified unmanned aerial vehicle, the identified flight schedule information, and the third relationship information; an output process for outputting a flight logbook related to the identified unmanned aerial vehicle based on the identified unmanned aerial vehicle, the identified flight schedule information, the takeoff and landing times, and the photographing locations; An information processing program characterized by causing the program to execute the above.

7. The computer an identification process for identifying the unmanned aerial vehicle and flight schedule information of the unmanned aerial vehicle related to the image information based on the first relationship information, the second relationship information, and the third relationship information obtained from a storage unit that stores: first relationship information that associates aircraft manufacturing information that identifies the unmanned aerial vehicle and is assigned by a manufacturer, imaging device manufacturing information that identifies the imaging device assigned by a manufacturer of the imaging device installed on the unmanned aerial vehicle, and aircraft identification information that identifies the unmanned aerial vehicle; second relationship information that associates the aircraft manufacturing information with a scheduled flight date and a scheduled takeoff time for the unmanned aerial vehicle; and third relationship information that associates image information taken in connection with the takeoff or landing of the unmanned aerial vehicle and meta information of the image information, the meta information including the imaging device manufacturing information, the date and time of the image, and the location of the image; a determination process for determining a time and location for takeoff and landing of the unmanned aerial vehicle based on the identified unmanned aerial vehicle, the identified flight schedule information, and the third relationship information; an output process for outputting a flight logbook related to the identified unmanned aerial vehicle based on the identified unmanned aerial vehicle, the identified flight schedule information, the takeoff and landing times, and the photographing locations; An information processing method comprising:

Images