Technologies for usage in airports

Abstract

This disclosure enables various technologies for airports to adequately or timely provide usable information for decision-making with respect to a road therein, an aircraft therein, or an FOD on the road, while being sufficiently reliable or accurate.

Description

TITLETECHNOLOGIES FOR USAGE IN AIRPORTSCROSS-REFERENCE TO RELATED PATENT APPLICATION

[0001] This patent application claims a benefit of priority to US Provisional Patent Application 63 / 525,506 filed 07 July 2023; which is incorporated herein by reference for all purposes.TECHNICAL FIELD

[0002] This disclosure relates to airports.BACKGROUND

[0003] A foreign object debris (FOD) positioned on a road on which an aircraft moves in an airport may present a danger to the aircraft. As such, the airport may have an inspection system to detect the FOD. However, the inspection system may not be able to adequately or timely provide usable information for decision-making with respect to the road, the aircraft, or the FOD. Likewise, the system may not be sufficiently reliable or accurate.SUMMARY

[0004] This disclosure enables various technologies for usage in airports. These technologies solve various technological problems noted above. For example, some of these technologies adequately or timely provide usable information for decision-making with respect to the road, the aircraft, or the FOD, while being sufficiently reliable or accurate.DESCRIPTION OF DRAWINGS

[0005] FIG. 1 shows a diagram of an embodiment of an architecture for usage in an airport according to this disclosure.

[0006] FIG. 2 shows a diagram of an embodiment of an airport having a road with a side and an aircraft on the road along the side according to this disclosure.

[0007] FIG. 3 shows a diagram of an embodiment of an airport with a road, a computing terminal, and a set of towers hosting a set static cameras and a set of nonstatic cameras, where the set of towers is spaced apart from the road for the set of static cameras and the non-static cameras oriented towards the road and send a first set of video streams from the set of static cameras and a set of second video streams from the set of non-static cameras to the computing instance for use by an operator at the computing terminal to monitor the road according to this disclosure.

[0008] FIG. 4 shows a diagram of an embodiment of a computing terminal with a user interface with a panorama video stream and a schematic top view, a computing instance, and a set of towers hosting a set static cameras and a set of non-static cameras, where the set of towers is spaced apart from the road for the set of static cameras and the non- static cameras to be oriented towards the road and send a set of video streams from the set of static cameras and a set of video streams from the set of non-static cameras to the computing instance for use by an operator at the computing terminal to monitor the road according to this disclosure.

[0009] FIG. 5 shows a diagram of an embodiment of an architecture for usage in an airport according to this disclosure.

[0010] FIG. 6 shows a diagram of an embodiment of a set of identifications and a set of notifications that a computing instance is programmed to do according to this disclosure.

[0011] FIG. 7 shows a diagram of an embodiment of a set of technological benefits of an architecture according to this disclosure.

[0012] FIG. 8 shows a diagram of an embodiment of a set of clearances for usage of an architecture according to this disclosure.

[0013] FIG. 9 shows a diagram of an embodiment of an architecture for usage in an airport according to this disclosure.

[0014] FIG. 10 shows a diagram of an embodiment of a schematic top view and a panorama video stream based on a set of static cameras positioned along a side of a ride oriented towards the road on which on an aircraft is positioned presented on a display according to this disclosure.

[0015] FIG. 11 shows a diagram of an embodiment of a schematic top view and a panorama video stream based on a first set of static cameras positioned along a first side (side A) of a road on which on an aircraft is positioned oriented towards the road and a second set of static cameras positioned along a second side (side B) of the road oriented towards the road presented on a display according to this disclosure.

[0016] FIG. 12 shows a diagram of an embodiment of a set of video streams from a set of static cameras getting dewarped when warped and then stitched for presentation as a panorama video stream on a display according to this disclosure.

[0017] FIG. 13 shows a diagram of an embodiment of a redundancy for a set of static cameras for working with a computing instance to generate a panorama video stream according to this disclosure.

[0018] FIG. 14 shows a diagram of an embodiment of a panorama video stream along with its technological advantages according to this disclosure.

[0019] FIG. 15 shows a diagram of an embodiment of a set of non-static cameras positioned along a side of a road for imaging the road such that a computing instance can detect an FOD on the road according to this disclosure.

[0020] FIG. 16 shows a diagram of an embodiment of a first set of non-static cameras positioned along a first side (side A) of a road for imaging the road and a second set of non-static cameras positioned along a second side (side B) of the road for imaging the road, where the first set of non-static cameras is hosted directly opposite the second set of non-static cameras, such that a computing instance can detect an FOD on the road according to this disclosure.

[0021] FIG. 17 shows a diagram of an embodiment of a first set of non-static cameras positioned along a first side (side A) of a road for imaging the road and a second set of non-static cameras positioned along a second side (side B) of the road for imaging the road, where the first set of non-static cameras is hosted indirectly opposite (offset) the second set of non-static cameras, such that a computing instance can detect an FOD on the road according to this disclosure.

[0022] FIG. 18 shows a diagram of an embodiment of a set of non-static cameras being hosted to image an FOD from a set of fields of view that are optically different from each other from a side of a road according to this disclosure.

[0023] FIG. 19 shows a diagram of an embodiment of a first set of non-static cameras being hosted to image an FOD from a first set of fields of view that are optically different from each other from a first side of a road and a second set of non-static cameras being hosted to image the FOD from a second set of fields of view that are optically different from each other from a second side of the road indirectly opposing the first side according to this disclosure.

[0024] FIG. 20 shows a diagram of an embodiment of a redundancy for a set of non- static cameras for working with a computing instance to identify an FOD according to this disclosure.

[0025] FIG. 21 shows a diagram of an embodiment of a non-static camera configured for a patrol tour to image a set of sub-zones with a zone according to this disclosure.

[0026] FIG. 22 shows a diagram of an embodiment of a non-static detection of an FOD along with its technological advantages according to this disclosure.

[0027] FIG. 23 shows a diagram of an embodiment of a user interface according to this disclosure.

[0028] FIG. 24 shows a diagram of an embodiment of a user interface simultaneously presenting a panorama video stream depicting a profile view of an aircraft and a schematic top view of a road on which the aircraft moves, where the schematic top view is segmented into a set of zones corresponding to a set of towers hosting a set of static cameras and a set of non-static cameras according to this disclosure.

[0029] FIG. 25 shows a diagram of an embodiment of a user interface presenting a pane with a content identified or formed based on a set of video streams from a set of static cameras or a set of non-static cameras oriented towards a road on which an aircraft is positioned according to this disclosure.

[0030] FIG. 26 shows a diagram of an embodiment of a legend for a user interface presented on a display according to this disclosure.

[0031] FIG. 27 shows a diagram of an embodiment of a set of panes from a user interface presented on a display according to this disclosure.

[0032] FIG. 28 shows a diagram of an embodiment of a legend for a user interface presented on a display according to this disclosure.

[0033] FIG. 29 shows a diagram of an embodiment of a position of an operator operating a computing terminal according to this disclosure.

[0034] FIG. 30 shows a diagram of an embodiment of a set of parameters for an architecture according to this disclosure.

[0035] FIGS. 31 a to 31 c show a diagram of an embodiment of a set of parameters for an architecture according to this disclosure.

[0036] FIGS. 32a to 32b show a diagram of an embodiment of a set of regulations for an architecture to be compliant with according to this disclosure.DETAILED DESCRIPTION

[0037] As explained above, this disclosure enables various technologies for usage in airports. These technologies solve various technological problems noted above. For example, some of these technologies adequately or timely provide usable information for decision-making with respect to the road, the aircraft, or the FOD, while being sufficiently reliable or accurate. This disclosure may, however, be embodied in many different forms and should not be construed as necessarily being limited to various embodiments disclosed herein. Rather, these embodiments are provided so that this disclosure is thorough and complete, and fully conveys various concepts of this disclosure to skilled artisans. Note that like numbers or similar numbering schemes can refer to like or similar elements throughout.

[0038] Various terminology used herein can imply direct or indirect, full or partial, temporary or permanent, action or inaction. For example, when an element is referred to as being "on," "connected" or "coupled" to another element, then the element can be directly on, connected or coupled to the other element or intervening elements can be present, including indirect or direct variants. In contrast, when an element is referred to as being "directly connected" or "directly coupled" to another element, there are no intervening elements present.

[0039] As used herein, a term "about" or "substantially" refers to a + / -10% variation from a nominal value / term.

[0040] Although various terms, such as first, second, third, and so forth can be used herein to describe various elements, components, regions, layers, or sections, note thatthese elements, components, regions, layers, or sections should not necessarily be limited by such terms. Rather, these terms are used to distinguish one element, component, region, layer, or section from another element, component, region, layer, or section. As such, a first element, component, region, layer, or section discussed below could be termed a second element, component, region, layer, or section, without departing from this disclosure.

[0041] As used herein, when this disclosure states herein that something is "based on" something else, then such statement refers to a basis which may be based on one or more other things as well. In other words, unless expressly indicated otherwise, as used herein "based on" inclusively means "based at least in part on" or "based at least partially on."

[0042] As used herein, a term "or" is intended to mean an inclusive "or" rather than an exclusive "or." That is, unless specified otherwise, or clear from context, "X employs A or B" is intended to mean any of natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied under any of the foregoing instances. For example, X includes A or B can mean X can include A, X can include B, and X can include A and B, unless specified otherwise or clear from context.

[0043] As used herein, each of singular terms "a," "an," and "the" is intended to include a plural form (e.g., two, three, four, five, six, seven, eight, nine, ten, tens, hundreds, thousands, millions) as well, including intermediate whole or decimal forms (e.g., 0.0, 0.00, 0.000), unless context clearly indicates otherwise. Likewise, each of singular terms "a," "an," and "the" shall mean "one or more," even though a phrase "one or more" may also be used herein.

[0044] As used herein, each of terms "comprises," "includes," or "comprising," "including" specify a presence of stated features, integers, steps, operations, elements, or components, but do not preclude a presence or addition of one or more other features, integers, steps, operations, elements, components, or groups thereof.

[0045] FIG. 1 shows a schematic diagram of an embodiment of an architecture for usage in an airport according to this disclosure. In particular, there is an architecture 100 which includes a road 102, an aircraft 104, an FOD 106, a tower 108, a static camera110, a non-static camera 112, a computing instance 114, a videowall 116, and a computing terminal 118.

[0046] As further explained below, there may be a set of towers 108 (1 to n), a set of static cameras 110 (1 to n), and a set of non-static cameras 112 (1 to n). Each tower 108 in the set of towers 108 may respectively host the static camera 110 or the non-static camera 112, as further explained below. The set of towers 108 may include at least two towers 108, which may be opposing (directly or indirectly / offset) each other with the road 102 extending therebetween or consecutive to each other on one side of the road 102, whether identically or sufficiently identically spaced apart or distanced from each other or the road 102 (or side thereof) or not identically or not sufficiently identically spaced apart or distanced from each other or the road 102 (or side thereof). The set of static cameras 110 may include at least two static cameras 110, which may be opposing (directly or indirectly / offset) each other with the road 102 extending therebetween or consecutive to each other on one side of the road 102, whether identically or sufficiently identically spaced apart or distanced from each other or the road 102 or not identically or not sufficiently identically spaced apart or distanced from each other or the road 102, to provide quality imaging resolution (e.g., pixels per meter), which may be identical across the set of static cameras 110. The set of non-static cameras 112 may include at least two non-static cameras 112, which may be opposing (directly or indirectly / offset) each other with the road 102 extending therebetween or consecutive to each other on one side of the road 102, whether identically or sufficiently identically spaced apart or distanced from each other or the road 102 or not identically or sufficiently identically spaced apart or distanced from each other or the road 102, to provide quality imaging resolution (e.g., pixels per meter), which may be identical across the set of non-static cameras 112.

[0047] There may be a network over which the static camera 110 or the non-static camera 112 are in communication with the computer instance 114. The network, whether wired, waveguide, or wireless, includes a local area network (LAN), a wide area network (WAN), a satellite network, a cellular network, or any other suitable network. The network can include Internet. Although the network can be a single network, this is not required and the network can be a group or collection of suitable networks collectively operating together in concert to accomplish various functionality, as disclosed herein.

[0048] There may be a network over which the videowall 116 or the computing terminal 118 are in communication with the computing instance 114. The network, whether wired, waveguide, or wireless, includes a LAN, a WAN, a satellite network, a cellular network, or any other suitable network. The network can include Internet. Although the network can be a single network, this is not required and the network can be a group or collection of suitable networks collectively operating together in concert to accomplish various functionality, as disclosed herein.

[0049] The road 102 can be tiled, blocked, paved, asphalted, rubberized, grassed (e.g., natural, artificial), or concreted in an airport or an airfield, whether military or civilian. The road can include a runway, a taxiway, a tarmac, a flight deck, an apron, or any other suitable road on which the aircraft 104 can move, whether self or towed. The road is rectilinear, but can be non-rectilinear (e.g., curved, arcuate). The road 102 has a side (e.g. , a lateral edge portion) along which the tower 108 is positioned off the road 102 while being spaced apart (e.g., within about 25 meters, 50 meters, 75 meters) from the side. The set of towers 108 can be positioned along the side, as further explained below. When the road 102 has another side, then there may be another set of towers 108 oppositely positioned along that another side, whether directly or indirectly, as further explained below.

[0050] The aircraft 104 can be an airplane, a helicopter, a drone, or any other suitable aerial vehicle, whether military or civilian. The aircraft 104 may have a profile view when imaged from a lateral side thereof, as further explained below.

[0051] The FOD 106 can include a bird, a tool, a tire, a wheel, a foil, an aerostructure piece, a component of the aircraft 104 or another aircraft, an animal, a vehicle, a luggage item, a suitcase, a missile, a rocket, a bomb, a wildlife object, a rock, a bolt, a nut, a screw, a nail, a beverage container, a coin, a badge, a fragment of the road 102, a vegetation item, a bush, a tree, a garment, or any other suitable object that can interfere with, endanger, or hazard the aircraft 104 or another aircraft.

[0052] The tower 108 may include a frame assembled (e.g., fastened, mated, adhered, magnetized, telescoped) from a set of components (e.g., a set of tubular members), where the frame is positioned along the side of the road 102, spaced apart from the road 102. The set of towers 108 can be positioned along the side, spaced apartfrom the road 102, as further explained below. Each tower 108 in the set of towers 108 may be structurally identical to each other, while being spaced apart from the side of the road 102 at a substantially equal distance (e.g., within about 25, 50, 100 meters) and spaced apart from each other at a substantially equal distance (e.g., within about 25, 50, 100 meters). There may be two sets of towers 108, where the first set of towers 108 opposes (directly or ind irectly / offset) the second set of towers 108 such that the road 102 extends therebetween.

[0053] The static camera 110 includes a video camera that is stationary and has a field of view towards the road 102 and generates a video stream from the field of view. The tower 108 hosts the static camera 110. The static camera 110 may be fastened, adhered, magnetized, mated, or otherwise secured to the tower 108. The static camera 110 may include a microphone. The static camera 110 may include a wide lens, a fisheye lens, or another suitable type of lens. The static camera 110 may include a wiper for a lens or the lens may be heated. The static camera 110 can be powered via a mains electricity source, a battery, or a renewable energy source.

[0054] When the static camera 110 generates the video stream that is warped (e.g., distorted), then the video stream may be subsequently dewarped, whether by the static camera 110 or the computing instance 114, by a dewarping algorithm. The dewarping algorithm may include a processor hosted by the static camera 110 or the computing instance 114: extracting a setting from a file associated with a wide-angle camera; determining, based on the setting, a first set of coordinates of a pixel of a first image, where the determining of the first set of coordinates is for each cell of a sparse conversion map represented as a first look-up table, where the sparse conversion map corresponds to a sparse grid of pixels of a second image, where the first image is captured via the wide-angle camera; determining, via interpolating the first set of coordinates, a second set of coordinates of a pixel of the first image such that the first image would be less rectilinear than the second image when displayed, where the determining of the second set of coordinates is for each cell of a full conversion map, where the second set of coordinates is represented as a second look-up table, where the full conversion map corresponds to a full grid of pixels of the second image; and enabling, based on the interpolating, the second image to be presented, where the first image is less rectilinearthan the second image. For example, the dewarping algorithm can be constituted as disclosed in US Patent 9947079, which is incorporated by reference herein for all purposes disclosed herein.

[0055] The set of static cameras 110 may be spaced apart from the side of the road at a set of distances that are substantially same to each other (e.g., within about 25, 50, 100 meters). The set of static cameras 110 may be spaced apart from each other at a set of distances that are substantially same to each other (e.g., within about 25, 50, 100 meters). The set of static cameras 110 may be oriented towards the road 102, as further described below. The set of static cameras 110 may have a set of fields of view that are optically parallel to each other while overlapping each other such that the set of static cameras 110 is able to generate a set of video streams synchronously or asynchronously imaging the set of fields of view.

[0056] The non-static (e.g., dynamic) camera 112 includes a video camera that is non- stationary (e.g., movable) and has a field of view towards the road 102 and generates a video stream from the field of view. The tower 108 hosts the non-static camera 112. The non-static camera 110 may be fastened, adhered, magnetized, mated or otherwise secured to the tower 108. The non-static camera 112 may include a microphone. The non-static camera 112 may be configured for a patrol tour (e.g., move along a set of preset positions while imaging from the set of preset positions), which may be iterative over a period of time. The non-static camera 112 may include a wide lens, a fisheye lens, or another suitable type of lens. The non-static camera 112 may be a pan-tilt-zoom (PTZ) camera or another suitable type of non-static camera 112. The non-static camera 112 may include a wiper for a lens or the lens may be heated. The non-static camera 112 can be powered via a mains electricity source, a battery, or a renewable energy source, whether same as the static camera 110 or a different one or a different type of source.

[0057] When the non-static camera 112 generates the video stream that is warped (e.g., distorted), then the video stream may be subsequently dewarped, whether by the non-static camera 112 or the computing instance 114, by a dewarping algorithm. The dewarping algorithm may include a processor hosted by the non-static camera 112 or the computing instance 114: extracting a setting from a file associated with a wide-angle camera; determining, based on the setting, a first set of coordinates of a pixel of a firstimage, where the determining of the first set of coordinates is for each cell of a sparse conversion map represented as a first look-up table, where the sparse conversion map corresponds to a sparse grid of pixels of a second image, where the first image is captured via the wide-angle camera; determining, via interpolating the first set of coordinates, a second set of coordinates of a pixel of the first image such that the first image would be less rectilinear than the second image when displayed, where the determining of the second set of coordinates is for each cell of a full conversion map, where the second set of coordinates is represented as a second look-up table, where the full conversion map corresponds to a full grid of pixels of the second image; and enabling, based on the interpolating, the second image to be presented, where the first image is less rectilinear than the second image. For example, the dewarping algorithm can be constituted as disclosed in US Patent 9947079, which is incorporated by reference herein for all purposes disclosed herein.

[0058] The set of non-static cameras 112 may be oriented towards the road 102, as further described below. The set of non-static cameras 112 may be spaced apart from the side at a set of distances that are substantially same to each other (e.g., within about 25, 50, 100 meters). The set of non-static cameras 112 may be spaced apart from each other at a set of distances that are substantially same to each other (e.g., within about 25, 50, 100 meters). The set of non-static cameras 112 may have a set of fields of view that may be optically parallel to each other or overlapping each other such that the set of non- static cameras 112 is able to generate a set of video streams synchronously or asynchronously imaging the set of fields of view.

[0059] On the tower 108, there may be the static camera 110 and the non-static camera 112, which may be replicated on the set of towers 108. The field of view of the static camera 110 can overlap with the field of view of the non-static camera 112. The static camera 110 can be positioned over the non-static camera 112. However, the static camera 110 can be positioned below the non-static camera 112 or lateral or diagonal thereto.

[0060] The computing instance 114 is in communication (e.g., wired, wireless, waveguide) with the static camera 110 and the non-static camera 112 when the static camera 110 and the non-static camera 112 are hosted by the tower 108. The computinginstance 114 can control the static camera 110 or the non-static camera 112. The set of towers 108 may host the set of static cameras 110 and the set of non-static cameras 112, each tower 108 hosting at least one static camera 110 and at least one non-static camera 112, where the computing instance 114 may receive a set of video streams from the set of static cameras 110 oriented towards the road 102 and a set of video streams from the set of non-static camera 112 oriented towards the road 102, as further explained below. The computing instance 114 may be not in any communication with any radiofrequency radar locally tracking the aircraft 102.

[0061] The computing instance 114 includes a single server, whether physical or virtual, or a set of servers, whether physical or virtual, operating in concert to enable a logical instance scalably and fault-tolerantly enabling various methods, as further explained below. The computing instance 114 may include a processor and a memory storing a set of instructions executable by the processor to enable a method for processing the set of video streams received from the set of static cameras 110 and the set of video streams received from the set of non-static cameras 112, as further explained below. The computing instance 114 may be running an operating system (OS) (e.g., Windows, Linux) and an application program (e.g., a video surveillance program) on the OS.

[0062] The videowall 116 includes a set of electronic displays (e.g., monitors, televisions, plasma, liquid crystal, electrophoretic, flat, curved, volumetric) that are logically tiled together to create one large electronic display. The videowall 116 may be operated by a controller in communication (e.g., wired, wireless, waveguide) with the computing instance 114 such that the computing instance 114 can control what is displayed on the videowall 116.

[0063] The computing terminal 118 (e.g., a desktop computer, a laptop computer) is in communication (e.g., wired, wireless, waveguide) with the computing instance 114. The computing terminal 118 may be running an OS (e.g., Windows, Linux) and an application program (e.g., a web browser application program, a client program for a video surveillance program) on the OS. The application program may have a user interface, which may be graphical. The user interface may have a navigation section (e.g., a set of navigation buttons, an address bar, an options menu, a tab section, a bookmark bar) anda viewport operative based on the navigation section, where the viewport is below or lateral to the navigation section. Note that computing terminal 118 may include the videowall 116 or may not include the videowall 118.

[0064] For example, as further explained below, the architecture 100 may include a system with the set of towers 108 that may be positioned along the side of the road 102 on which the aircraft 104 moves. The set of static cameras 110 may (i) be hosted by the set of towers 108, (ii) be spaced apart from the side at a first set of distances that are substantially same to each other, (iii) are be optically parallel to each other, and (iv) have a first set of fields of view towards the side while overlapping each other such that the set of static cameras 110 generates a first set of video streams synchronously imaging the first set of fields of view. Therefore, the computing instance 114 may be programmed to access the first set of video streams, identify the aircraft 104 in the first set of video streams when the aircraft 104 is on the road 102 along the side, track the aircraft 104 in the first set of video streams when the aircraft is on the road 102 along the side, stitch the first set of video streams such that a panorama video stream is formed depicting the profile view when the aircraft 104 is on the road 102 along the side, and present the panorama video stream on the videowall 116 such that the profile view is visible when the aircraft 104 is on the road 102 along the side. The system may further include the set of non-static cameras 112 that may (i) be hosted by the set of towers 108, (ii) be spaced apart from the side at a second set of distances that are substantially same to each other, (iii) are scheduled to perform a set of patrol tours to image the road 102, and (iv) have a second set of fields of view towards the side while overlapping each other such that the set of non-static cameras 112 generates a second set of video streams imaging the second set of fields of view where at least two non-static cameras 112 of the set of non- static cameras 112 are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road 102 simultaneously from at least two fields of view in the second set of fields of view that are optically different from each other. Therefore, the computing instance 114 may be programmed to detect the FOD 106 on the common segment in at least two video streams of the second set of video streams imaged by the at least two non-static cameras 112 performing the at least two patrol tours from the at least two fields of view when the FOD 106 is on the common segment andpresent the user interface on the application program running on the computing terminal 118, where the user interface is programmed to allow an operator to perform a visual inspection of the FOD 106 that has been detected on the common segment and take an action (e.g., generate an alert, call an emergency service) based on the visual inspection. Since at least one tower 108 of the set of towers 108 may host at least one non-static camera 112 of the set of non-static cameras 112 that is redundant to at least one static camera 110 of the set of static cameras 110 hosted by the at least one tower 108, if the at least one static camera 110 is inoperative (e.g., broken), then the at least one non- static camera 112 can take over (e.g., based on a manual request, based on an automated detection of a relevant fault), i.e. , failover or substitute for the static camera 110, and generate a respective video stream to be included in the first set of video streams based on which the panorama video stream may be formed. Such form of redundancy can be as long as needed or for a predetermined time period. Note that the system may be embodied as a kit before the system is assembled, where the kit has a set of components that are collectively configured to enable the system, as disclosed herein. Likewise, there may be a method where the kit is provided (e.g., manufactured, shipped, assembled, configurated) to a user and enabled (e.g., instructed, launched) as the system, as disclosed herein. Therefore, these configurations adequately or timely provide usable information for decision-making with respect to the road 102, the aircraft 104, or the FOD 106, while being sufficiently reliable or accurate.

[0065] For example, as further explained below, the architecture 100 may include a system with the tower 108 positionable along the side of the road 102 on which the aircraft 104 having the profile view moves. The system may further include the static camera 110 hosted by the tower 108, where the static camera 110 has a first field of view towards the side and configured to generate a first video stream depicting the profile view. The system may further include the non-static camera 112 hosted by the tower 108, where the non- static camera 112 has a second field of view towards the side and configured to perform a patrol tour to image the road 102 such that the non-static camera 112 generates a second video stream in which the FOD 106 on the road 102 is detected by the computing instance 114. Since the non-static camera 112 may be redundant to the static camera 110, if the static camera 110 is inoperative (e.g. , broken), then the non-static camera 112can take over (e.g., based on a manual request, based on an automated detection of a relevant fault), i.e., failover or substitute for the static camera 110, and generate a respective video stream. Such form of redundancy can be as long as needed or for a predetermined time period. Note that the system may be embodied as a kit before the system is assembled, where the kit has a set of components that are collectively configured to enable the system, as disclosed herein. Likewise, there may be a method where the kit is provided (e.g., manufactured, shipped, assembled, configurated) to a user and enabled (e.g., instructed, launched) as the system, as disclosed herein. Therefore, these configurations adequately or timely provide usable information for decision-making with respect to the road 102, the aircraft 104, or the FOD 106, while being sufficiently reliable or accurate.

[0066] For example, as further explained below, the architecture 100 may include a system with the set of towers 108 positioned along the side of the road 102 on which the aircraft 104 moves, where the aircraft 104 has the profile view. The system may further include the set of static cameras 110 that may (i) be hosted by the set of towers 108, (ii) be spaced apart from the side at a first set of distances that are substantially same, (iii) be optically parallel to each other, and (iv) have a first set of fields of view towards the side while overlapping each other such that the set of static cameras 110 generates a first set of video streams synchronously imaging the first set of fields of view. The system may further include the set of non-static cameras 112 that may (i) be hosted by the set of towers 108, (ii) be spaced apart from the side at a second set of distances that are substantially same, (iii) be scheduled to perform a set of patrol tours to image the road 102, and (iv) have a second set of fields of view towards the side while overlapping each other such that the set of non-static cameras 112 generates a second set of video streams imaging the second set of fields of view where at least two non-static cameras 112 of the set of non-static cameras 112 are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road 102 simultaneously from at least two fields of view in the second set of fields of view that are optically different from each other. Since at least one tower 108 of the set of towers 108 hosts at least one non-static camera 112 of the set of non-static cameras 112 that is redundant to at least one static camera 110 of the set of static cameras 110 hosted by the at least one tower 108, if thestatic camera 110 is inoperative (e g., broken), then the non-static camera 112 can take over (e.g., based on a manual request, based on an automated detection of a relevant fault), i.e. , failover or substitute for the static camera 110, and generate a respective video stream. Such form of redundancy can be as long as needed or for a predetermined time period. Likewise, since the set of non-static cameras 112 have the set of fields of view towards the side while overlapping each other and at least one non-static camera 112 of the at least two non-static cameras 112 is redundant to at least one another non-static camera 112 of the at least two non-static cameras 112, if the another non-static camera 112 of the at least two non-static cameras 112 is inoperative (e.g., broken), then the at least one non-static camera 112 of the at least two non-static cameras 112 can take over (e.g., based on a manual request, based on an automated detection of a relevant fault), i.e., failover or substitute for the another non-static camera 112 of the at least two non- static cameras 112, and generate a respective video stream. Such form of redundancy can be as long as needed or for a predetermined time period. Note that the system may be embodied as a kit before the system is assembled, where the kit has a set of components that are collectively configured to enable the system, as disclosed herein. Likewise, there may be a method where the kit is provided (e.g., manufactured, shipped, assembled, configurated) to a user and enabled (e.g., instructed, launched) as the system, as disclosed herein. Therefore, these configurations adequately or timely provide usable information for decision-making with respect to the road 102, the aircraft 104, or the FOD 106, while being sufficiently reliable or accurate.

[0067] For example, as further explained below, the architecture 100 may include a system with a user interface simultaneously presenting a panorama video stream, a schematic top view, and a pane. The panorama video stream may be formed from a first set of video streams sourced from a set of static cameras 110 that may (i) be hosted by the set of towers 108 positioned along the side of the road 102 on which the aircraft 104 having the profile view moves, (ii) be spaced apart from the side at a first set of distances that are substantially same, (iii) be optically parallel to each other, and (iv) have a first set of fields of view towards the side while overlapping each other such that the set of static cameras 110 generates the first set of video streams synchronously imaging the first set of fields of view. The panorama video stream may present the profile view. The schematictop view may presents a graphic corresponding to the aircraft 104 on the road 102. The schematic top view may correspond to the panorama video stream. The pane may present a content related to the road 102, the aircraft 104, or the FOD 106 detected on the road 102 from a second set of video streams sourced from the set of non-static cameras 112 that may (i) be hosted by the set of towers 108, (ii) be spaced apart from the side at a second set of distances that are substantially same, (iii) be scheduled to perform a set of patrol tours to image the road 102, and (iv) have a second set of fields of view towards the side while overlapping each other such that the set of non-static cameras 112 generates the second set of video streams imaging the second set of fields of view where at least two non-static cameras 112 of the set of non-static cameras 112 are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road 102 simultaneously from at least two fields of view in the second set of fields of view that are optically different from each other, where the FOD 106 is positioned on the common segment. Therefore, these configurations adequately or timely provide usable information for decision-making with respect to the road 102, the aircraft 104, or the FOD 106, while being sufficiently reliable or accurate.

[0068] For example, as further explained below, the architecture 100 may include a system with a first configuration and a second configuration, where the first configuration opposes the second configuration. Each of the first configuration and the second configuration respectively includes: (i) the set of towers 108 positioned along the side of the road on which the aircraft having the profile view moves; (ii) the set of static cameras 110 that may (i) be hosted by the set of towers 108, (ii) be spaced apart from the side at a first set of distances that are substantially same, (iii) be optically parallel to each other, and (iv) have a first set of fields of view towards the side while overlapping each other such that the set of static cameras 110 generates a first set of video streams synchronously imaging the first set of fields of view; and (iii) the set of non-static cameras 112 that may (i) be hosted by the set of towers 108, (ii) be spaced apart from the side at a second set of distances that are substantially same, (iii) be scheduled to perform a set of patrol tours to image the road 102, and (iv) have a second set of fields of view towards the side while overlapping each other such that the set of non-static cameras 112 generates a second set of video streams imaging the second set of fields of view whereat least two non-static cameras 112 of the set of non-static cameras 112 are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road 102 simultaneously from at least two fields of view in the second set of fields of view that are optically different from each other. Since at least one tower 108 of the set of towers 108 hosts at least one non-static camera 112 of the set of non-static cameras 112 that is redundant to at least one static camera 110 of the set of static cameras 110 hosted by the at least one tower 108, if the static camera 110 is inoperative (e.g., broken), then the non-static camera 112 can take over (e.g., based on a manual request, based on an automated detection of a relevant fault), i.e. , failover or substitute for the static camera 110, and generate a respective video stream. Such form of redundancy can be as long as needed or for a predetermined time period. Likewise, since the set of non- static cameras 112 have the set of fields of view towards the side while overlapping each other and at least one non-static camera 112 of the at least two non-static cameras 112 is redundant to at least one another non-static camera 112 of the at least two non-static cameras 112, if the another non-static camera 112 of the at least two non-static cameras 112 is inoperative (e.g., broken), then the at least one at least one non-static camera 112 of the at least two non-static cameras 112 can take over (e.g., based on a manual request, based on an automated detection of a relevant fault), i.e., failover or substitute for the another non-static camera 112 of the at least two non-static cameras 112, and generate a respective video stream. Such form of redundancy can be as long as needed or for a predetermined time period. Note that the system may be embodied as a kit before the system is assembled, where the kit has a set of components that are collectively configured to enable the system, as disclosed herein. Likewise, there may be a method where the kit is provided (e.g., manufactured, shipped, assembled, configurated) to a user and enabled (e.g., instructed, launched) as the system, as disclosed herein. Therefore, these configurations adequately or timely provide usable information for decision-making with respect to the road 102, the aircraft 104, or the FOD 106, while being sufficiently reliable or accurate.

[0069] For example, as further explained below, the architecture 100 may include a system with the set of towers 108 positioned along the side of the road 102 on which the aircraft 104 having the profile view moves. The system may further include the set of staticcameras 110 that may (i) be hosted by the set of towers 108, (ii) be spaced apart from the side at a set of distances that are substantially same, (iii) be optically parallel to each other, and (iv) have a set of fields of view towards the side while overlapping each other such that the set of static cameras 110 generates a set of video streams synchronously imaging the set of fields of view. The system may further include the computing instance 114 programmed to: access the set of video streams; identify the aircraft 104 in the set of video streams when the aircraft 104 is on the road 102 along the side; track the aircraft 104 in the set of video streams when the aircraft is on the road 104 along the side; stitch the set of video streams such that a panorama video stream is formed depicting the profile view when the aircraft 104 is on the road 102 along the side; and present the panorama video stream on a display such that the profile view is visible and a visual identifier for the profile view is presented over the panorama video stream when the aircraft 104 is on the road 102 along the side. Note that the system may be embodied as a kit before the system is assembled, where the kit has a set of components that are collectively configured to enable the system, as disclosed herein. Likewise, there may be a method where the kit is provided (e.g., manufactured, shipped, assembled, configurated) to a user and enabled (e.g., instructed, launched) as the system, as disclosed herein. Therefore, these configurations adequately or timely provide usable information for decision-making with respect to the road 102, the aircraft 104, or the FOD 106, while being sufficiently reliable or accurate.

[0070] For example, as further explained below, the architecture 100 may include a system with the set of towers 108 positioned along the side of the road 102 on which the aircraft 104 having the profile view moves. The system may further include the set of nonstatic cameras 112 that may (i) be hosted by the set of towers 108, (ii) be spaced apart from the side at a set of distances that are substantially same, (iii) be scheduled to perform a set of patrol tours to image the road 102, and (iv) have a set of fields of view towards the side while overlapping each other such that the set of non-static cameras 112 generates a set of video streams imaging the set of fields of view where at least two nonstatic cameras 112 of the set of non-static cameras 112 are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road 102 simultaneously from at least two fields of view in the set of fields of view that are opticallydifferent from each other. The system may further include the computing instance 114 programmed to: access the set of video streams; detect the FOD 106 on the common segment in at least two video streams of the set of video streams imaged by the at least two non-static cameras 112 performing the at least two patrol tours from the at least two fields of view when the FOD 106 is on the common segment; and present a user interface on an application program running on the computing terminal 118, where the user interface is programmed to allow an operator to perform a visual inspection of the FOD 106 that has been detected on the common segment and take an action based on the visual inspection. Since at least one non-static camera 112 of the at least two non-static cameras 112 is redundant to at least one another non-static camera 112 of the at least two non-static cameras 112, if the another non-static camera 112 of the at least two non- static cameras 112 is inoperative (e.g., broken), then the at least one at least one non- static camera 112 of the at least two non-static cameras 112 can take over (e.g., based on a manual request, based on an automated detection of a relevant fault), i.e. , failover or substitute for the another non-static camera 112 of the at least two non-static cameras 112, and generate a respective video stream. Such form of redundancy can be as long as needed or for a predetermined time period. Note that the system may be embodied as a kit before the system is assembled, where the kit has a set of components that are collectively configured to enable the system, as disclosed herein. Likewise, there may be a method where the kit is provided (e.g., manufactured, shipped, assembled, configurated) to a user and enabled (e.g., instructed, launched) as the system, as disclosed herein. Therefore, these configurations adequately or timely provide usable information for decision-making with respect to the road 102, the aircraft 104, or the FOD 106, while being sufficiently reliable or accurate.

[0071] For example, as further explained below, the architecture 100 may include a system with the set of towers 108 positioned along the side of the road 102 on which the aircraft 104 having the profile view moves. The system may further include the set of static cameras 110 that may (i) be hosted by the set of towers 108, (ii) be spaced apart from the side at a set of distances that are substantially same, (iii) are optically parallel to each other, and (iv) have a set of fields of view towards the side while overlapping each other such that the set of static cameras 110 generates a set of video streams synchronouslyimaging the set of fields of view. The system may further include the computing instance 114 programmed to: access the set of video streams; identify the aircraft 104 in the set of video streams when the aircraft 104 is on the road 102 along the side; track the aircraft 104 in the set of video streams when the aircraft 104 is on the road 102 along the side; stitch the set of video streams such that a panorama video stream is formed depicting the profile view when the aircraft 104 is on the road 102 along the side; and present the panorama video stream on a display such that the profile view is visible when the aircraft 104 is on the road 102 along the side, where the panorama video stream has a single zoom. Note that the system may be embodied as a kit before the system is assembled, where the kit has a set of components that are collectively configured to enable the system, as disclosed herein. Likewise, there may be a method where the kit is provided (e.g., manufactured, shipped, assembled, configurated) to a user and enabled (e.g., instructed, launched) as the system, as disclosed herein. Therefore, these configurations adequately or timely provide usable information for decision-making with respect to the road 102, the aircraft 104, or the FOD 106, while being sufficiently reliable or accurate.

[0072] For example, as further explained below, the architecture 100 may include a system with a user interface simultaneously presenting a panorama video stream and a pane. The panorama video stream may formed from a first set of video streams sourced from the set of static cameras 110 that may (i) be hosted by a set of towers positioned along the side of the road 102 on which the aircraft 104 having a profile view moves, (ii) be spaced apart from the side at a first set of distances that are substantially same, (iii) are optically parallel to each other, and (iv) have a first set of fields of view towards the side while overlapping each other such that the set of static cameras 110 generates the first set of video streams synchronously imaging the first set of fields of view. The panorama video stream may presents the profile view. The panorama video stream may have a single zoom. The pane may present a content related to the road 102, the aircraft 104, or a FOD 106 detected on the road 102 from a second set of video streams sourced from the set of non-static cameras 112 that may (i) be hosted by the set of towers 108,(ii) be spaced apart from the side at a second set of distances that are substantially same,(iii) be scheduled to perform a set of patrol tours to image the road 102, and (iv) have a second set of fields of view towards the side while overlapping each other such that theset of non-static cameras 112 generates the second set of video streams imaging the second set of fields of view where at least two non-static cameras 112 of the set of nonstatic cameras 112 are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road 102 simultaneously from at least two fields of view in the second set of fields of view that are optically different from each other, where the FOD 106 is positioned on the common segment. Note that the system may be embodied as a kit before the system is assembled, where the kit has a set of components that are collectively configured to enable the system, as disclosed herein. Likewise, there may be a method where the kit is provided (e.g., manufactured, shipped, assembled, configurated) to a user and enabled (e.g., instructed, launched) as the system, as disclosed herein. Therefore, these configurations adequately or timely provide usable information for decision-making with respect to the road 102, the aircraft 104, or the FOD 106, while being sufficiently reliable or accurate.

[0073] For example, as further explained below, the architecture 100 may include a system with the set of towers 108 positioned along the side of the road 102 on which the aircraft 104 having the profile view moves. The system may further include the set of non- static cameras 112 that may (i) be hosted by the set of towers 108, (ii) be spaced apart from the side at a set of distances that are substantially same, (iii) be scheduled to perform a set of patrol tours to image the road 102, and (iv) have a set of fields of view towards the side while overlapping each other such that the set of non-static cameras 112 generates a set of video streams imaging the set of fields of view where at least two non- static cameras 112 of the set of non-static cameras 112 are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road 102 simultaneously from at least two fields of view in the set of fields of view that are optically different from each other, attempt to detect an FOD on the common segment, and generate at least two confidence level estimates for the FOD on the common segment when detected. The system may further include the computing instance 114 programmed to: access the set of video streams and the at least two confidence level estimates; form a determination whether the FOD is present on the common segment based on the at least two confidence level estimates; and present a user interface on an application program running on a computing terminal, wherein the user interface is programmed toallow an operator to perform a visual inspection of the FOD that has been detected on the common segment and take an action based on the visual inspection. Note that the system may be embodied as a kit before the system is assembled, where the kit has a set of components that are collectively configured to enable the system, as disclosed herein. Likewise, there may be a method where the kit is provided (e.g., manufactured, shipped, assembled, configurated) to a user and enabled (e.g., instructed, launched) as the system, as disclosed herein. Therefore, these configurations adequately or timely provide usable information for decision-making with respect to the road 102, the aircraft 104, or the FOD 106, while being sufficiently reliable or accurate.

[0074] For example, as further explained below, the architecture 100 may include a system with the set of towers 108 positioned along the road 102 on which the aircraft 104 having the profile view moves. The system may further include the set of non-static cameras 112 that may (i) be hosted by the set of towers 108, (ii) be spaced apart from the road 102 at a set of distances that are substantially same, (iii) are scheduled to perform a set of patrol tours to image the road 102, and (iv) have a set of fields of view towards the road 102 while overlapping each other such that the set of non-static cameras 112 generates a set of video streams imaging the set of fields of view where at least two non-static cameras 112 of the set of non-static cameras 112 are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road 102 simultaneously from at least two fields of view in the set of fields of view that are optically different from each other, attempt to detect an FOD on the common segment, and generate at least two confidence level estimates for the FOD on the common segment when detected. The system may further include the computing instance 114 programmed to: access and the at least two confidence level estimates; form a determination whether the FOD is present on the common segment based on the at least two confidence level estimates; and present a user interface on an application program running on a computing terminal, wherein the user interface is programmed to allow an operator to perform a visual inspection of the FOD that has been detected on the common segment and take an action based on the visual inspection. Note that the system may be embodied as a kit before the system is assembled, where the kit has a set of components that are collectively configured to enable the system, as disclosed herein. Likewise, theremay be a method where the kit is provided (e.g., manufactured, shipped, assembled, configurated) to a user and enabled (e.g., instructed, launched) as the system, as disclosed herein. Therefore, these configurations adequately or timely provide usable information for decision-making with respect to the road 102, the aircraft 104, or the FOD 106, while being sufficiently reliable or accurate.

[0075] FIG. 2 shows a diagram of an embodiment of an airport having a road with a side and an aircraft on the road along the side according to this disclosure. As explained above in context of FIG. 1 , the airport has the road 102 with the side, where the aircraft 104 is positioned. As shown in FIG. 2, the airport has a set of roads 102, some of which are interconnected. The set of towers 108 may be positioned along some roads 102, many roads 102, most roads 102, or all roads 102, whether along entire lengths or less than that, or in segments. The set of static cameras 110 may be oriented towards some roads 102, many roads 102, most roads 102, or all roads 102, whether along entire lengths or less than that, or in segments. The set of non-static cameras 112 may be oriented towards some roads 102, many roads 102, most roads 102, or all roads 102, whether along entire lengths or less than that or in segments.

[0076] FIG. 3 shows a diagram of an embodiment of an airport with a road, a computing terminal, and a set of towers hosting a set static cameras and a set of nonstatic cameras, where the set of towers is spaced apart from the road for the set of static cameras and the non-static cameras oriented towards the road and send a first set of video streams from the set of static cameras and a set of second video streams from the set of non-static cameras to the computing instance for use by an operator at the computing terminal to monitor the road according to this disclosure. As explained above in context of FIGS. 1-2, the road 102 (e.g., a runway) has the side along which the set of towers 108 is positioned such that the set of static cameras 110 is oriented towards to road 102 and the set of non-static cameras 112 is oriented towards the road. Each tower 108 in the set of towers 108 respectively hosts the static camera 110 and the non-static camera 112, where the static camera 110 is respectively positioned above the non-static camera 112 and the static camera 110 has the field of view that respectively overlaps with the field of view of the non-static camera 112. Therefore, the architecture includes a set of fields of view for the static cameras 110 that are consecutive and relative to theside of the road 102 and a set of fields of view for the non-static cameras 112 that are consecutive and relative to the side of the road 102. Although the set towers 108 has three towers 108, this is not required and there may be a single tower 108 or four, five, six, seven, eight, nine, ten, or more towers 108, as needed.

[0077] FIG. 4 shows a diagram of an embodiment of a computing terminal with a user interface with a panorama video stream and a schematic top view, a computing instance, and a set of towers hosting a set static cameras and a set of non-static cameras, where the set of towers is spaced apart from the road for the set of static cameras and the non- static cameras to be oriented towards the road and send a set of video streams from the set of static cameras and a set of video streams from the set of non-static cameras to the computing instance for use by an operator at the computing terminal to monitor the road according to this disclosure. As explained above in context of FIGS. 1 -3, the video wall 116 or the computing terminal 118 may have a user interface with a panorama video stream and a schematic top view, which may be positioned side-by-side to each other.

[0078] The panorama video stream is formed by the computing instance 114 from the set video streams received from the set of static cameras 110 hosted by the set of towers 118 positioned along the side of the road 102 off the road 102. Therefore, when the aircraft 104 is on the road 102, as imaged from the set of static cameras 110, the panorama video stream depicts the profile view of the aircraft 104. The computing instance 114 forms the panorama video stream by stitching the set of video streams. If any video stream or the set of video streams is warped (e.g., distorted) due to the set of static cameras 110 (e.g. , wide angle lenses, fisheye lenses), then the computing instance 114 dewarps the video stream or the set of video streams, as explained above, which may be in parallel, and then stitches the set of video streams to form the panorama video stream such that the panorama video stream is flat. For example, the panorama video may be dynamically created in real-time.

[0079] The panorama video stream can be formed to enable a single zoom therefor. As such, the videowall 116 or the computing terminal 118 may be enabled to zoom into or out from the panorama video stream as the single zoom. The panorama video stream may be a flat panorama video stream which may have the single zoom. These configurations may be replicated when there are multiple panorama video streams.

[0080] The set of towers 108 hosts the set static cameras 110 and the set of non-static cameras 112, where the set of towers 108 is equadistantly spaced apart from the road 102 off the road 102 and from each other for the set of static cameras 110 and the nonstatic cameras 112 to be oriented towards the road 102 and respectively send the set of video streams from the set of static cameras 110 and the set of video streams from the set of non-static cameras 112 to the computing instance 114. The fields of view of the set of static cameras 110 overlap each other and optically parallel to each other (e.g., by optical central axes), while the set of static cameras 110 synchronously images toward the road 102, which may enable for frame-syncing for the panorama video stream. Since the road 102 has a first end portion and a second end portion, the panorama video stream may depict the road 102 from the first end portion to the second end portion, i.e. , end-to- end. Therefore, when the aircraft 104 is on the road 102, as imaged from the set of static cameras 110, the panorama video stream depicts the profile view of the aircraft 104, which may be during taxing on the road 102, landing on the road 102, or takeoff from the road 102.

[0081] The panorama video stream may be presented on the videowall 116 or the computing terminal 118. The videowall 116 and the computing terminal 118 are colocated (e.g., positioned in a same building or parcel of property). However, this configuration is not required and the videowall 116 and the computing terminal can be not co-located 118 (e.g., not positioned in a same building or parcel of property).

[0082] The schematic top view corresponds to the road 102 (e.g., a plan map) and has a graphic (e.g., an icon) corresponding to the aircraft 104 positioned thereon. The graphic can move on the schematic top view corresponding to the aircraft 104 moving on the road 102 or the profile view of the aircraft 104 moving in the panorama video stream. The graphic can move in a same direction as the profile view of the aircraft 104 (e.g., along a parallel plane) or not in a same direction (e.g., opposite direction) as the profile view of the aircraft 104. The graphic may correspond to a type of the aircraft 104, which may be selected by the computing instance 114 based on a set of flight data for the aircraft, or may be generic to the aircraft 104.

[0083] The set of video streams from the set of non-static cameras 112 may be received by the computing instance 114. In response, the computing instance mayprocess the set of video streams from the set of non-static cameras 112 such that the computing instance 114 detects the FOD 106, identifies the FOD 106, and allows the computing terminal 118 to be operated for the FOD 106 to be presented on the user interface, which may include zooming into the FOD.

[0084] FIG. 5 shows a diagram of an embodiment of an architecture for usage in an airport according to this disclosure. As explained above in context of FIGS. 1-4, the architecture 100 includes the tower 108 hosting the static camera 110 and the non-static camera 112, where the static camera 110 is positioned above the non-static camera 112. However, this configuration is not required and the static camera 110 can be positioned below, lateral or diagonal to the non-static camera 112. The static camera 110 sends the set of video streams to the computing instance 114 and the non-static camera 112 sends the set of video streams to the computing instance 114, which may include a video management system (e.g., a video management software and a video management server), where the panorama video stream is formed and the FOD 106 may be detected (e.g., via an artificial neural network (ANN)). The computing instance 114 is may feed data for display on the videowall 116 or the computing terminal 118. The computing terminal 118 may command the computing instance 114 to take an action (e.g., activate an alarm, direct a team to the road 102, the FOD 106, the common segment, or the aircraft 104). When deployed as disclosed herein, the ANN may be trained to allow for detecting the airplane 104 from multiple fields of view, land vehicles (e.g., trucks, cars, buses), and animate objects (e.g., people, animals, birds), whether as the FOD or not.

[0085] FIG. 6 shows a diagram of an embodiment of a set of identifications and a set of notifications that a computing instance is programmed to do according to this disclosure. As explained above in context of FIGS. 1 -5, the architecture 100 includes the computing instance 114 which is programmed to process the set of video streams from the set of static cameras 110 and the set of video streams from the non-static cameras 112 to identify various dangers or hazards to the road 102, the aircraft 104, which may be embodied as the FOD 106. The computing terminal 118 may communicate with the computing instance 114 to respond to the FOD 106 by taking an action in the user interface or external to the user interface. The action in the user interface may include activating or deactivating a user input element (e.g., a button) to cause a certain algorithmto initiate or halt, an output device (e.g., a speaker) to output an output (e.g., a sound), an emergency responder to be deployed, or another suitable action, which may be enabled via the panorama video stream or the pane, as further explained below.

[0086] FIG. 7 shows a diagram of an embodiment of a set of technological benefits of an architecture according to this disclosure. As explained above in context of FIGS. 1 -6, the architecture 100 has some technological benefits, which may adequately or timely provide usable information for decision-making with respect to the road 102, the aircraft 104, or the FOD 106, while being sufficiently reliable or accurate.

[0087] FIG. 8 shows a diagram of an embodiment of a set of clearances for usage of an architecture according to this disclosure. As explained above in context of FIGS. 1 -7, the architecture 100 includes the set of towers 108 positionable along the road 102 along the side off the road 102 for the set of static cameras 110 and the set of non-static cameras 112 to be oriented towards the road. To avoid interference between the set of towers 108 and the aircraft 104 on the road 102 or to maximize longevity of the set of towers 108, the set of static cameras 110, or the set of non-static cameras 112, the architecture 100 is positioned to comply with the set of clearances shown in FIG. 8. Note that the set of clearance is an example and other set of clearances, different from the set of clearances, individually or collectively, whether more or less, is possible.

[0088] FIG. 9 shows a diagram of an embodiment of an architecture for usage in an airport according to this disclosure. As explained above in context of FIGS. 1-8, the architecture 100 includes the computing instance 114 which includes a set of servers, which may include a subset of servers for archiving, a subset of servers for splicing (stitching), a subset of servers for FOD detection, a subset of servers for failover processing, and other relevant computing hardware (e.g., administrator terminals, routers, switches, fiberoptics, cabling). The subset of servers for archiving enables recording of the panorama video stream, the first set of video streams, or the second set of video streams into an archive accessible from the user interface such that an incident involving the aircraft 104 on the road 102 or the FOD 106 on the common segment can be investigated on the user interface. The archive may enable the panorama video stream to be played back at a computing terminal or be switched to an original video resolution of a video stream from a particular static camera 110 (before or after dewarping) at acomputing terminal, as disclosed herein. The subset of servers for splicing (stitching) enables the panorama video stream to formed from the set of video streams sent by the set of static cameras 110. The subset of servers for FOD detection may detect the FOD 106 in the set of video streams sent by the set of non-static cameras 112. The computing instance 114 may be programmed to identify a smoke, a steam, a fire, or a liquid extending from the road 102 or the aircraft 104 and issue an alert on the user interface. During patrol tours, the computing instance 114 may be programmed to detect the FOD 106 and another object or event involving the road 102, the aircraft 104, or the FOD 106, where some non-static cameras 112 detect the FOD 106 and some non-static cameras detect another object or event involving the road 102, the aircraft 104, or the FOD 106. These configurations may be adapted when there are multiple sets of towers 108, where each tower 108 hosting the static camera 110 and the non-static camera 112, such that these subsets of servers provide more accurate detection or identification of objects or events, as disclosed herein, and for investigation of incidents, as disclosed herein. Note that the patrol tours as disclosed herein, due to simultaneous imaging from different fields of view, enable a sufficiently reliable detection of the FOD and identification of the FOD, including its properties, attributes or characteristics (e.g., size, type, material), whether on the non-static cameras 112 or the computing instance 114.

[0089] The videowall 116 presents the panorama video stream. The computing terminal 118 presents the user interface, which may simultaneously present the panorama video stream and the schematic top view. Although the videowall 116 is colocated with the computing terminal 118, this is not required and the videowall 116 may be not co-located with the computing terminal 118.

[0090] FIG. 10 shows a diagram of an embodiment of a schematic top view and a panorama video stream based on a set of static cameras positioned along a side of a ride oriented towards the road on which on an aircraft is positioned presented on a display according to this disclosure. As explained above in context of FIGS. 1 -9, the architecture 100 includes the set of towers 108 that may be positioned along the side of the road 102 on which the aircraft 104 moves. The set of static cameras 110 may (i) be hosted by the set of towers 108, (ii) be spaced apart from the side at the set of distances that are substantially same to each other, (iii) are be optically parallel to each other, and (iv) havethe set of fields of view towards the side while overlapping each other such that the set of static cameras 110 generates the set of video streams synchronously imaging the set of fields of view. Therefore, the computing instance 114 may be programmed to access the set of video streams, identify the aircraft 104 in the set of video streams when the aircraft 104 is on the road 102 along the side, track the aircraft 104 in the set of video streams when the aircraft is on the road 102 along the side, stitch the set of video streams such that the panorama video stream is formed depicting the profile view when the aircraft 104 is on the road 102 along the side, and present the panorama video stream on the videowall 116 or the computing terminal 118 such that the profile view is visible when the aircraft 104 is on the road 102 along the side. The panorama video stream may be a flat panorama video stream, which may have the single zoom (e.g., in or out).

[0091] FIG. 11 shows a diagram of an embodiment of a schematic top view and a panorama video stream based on a first set of static cameras positioned along a first side (side A) of a road on which on an aircraft is positioned oriented towards the road (first configuration) and a second set of static cameras positioned along a second side (side B) of the road oriented towards the road (second configuration) presented on a display according to this disclosure. As explained above in context of FIGS. 1 -10, there is another set of towers 108 with another set of static cameras 110 and another set of non-static cameras 112, where the another set of towers 108 is opposite (directly or indirectly / offset) the set of towers 108, the another set of static cameras 110 opposite (directly or indirectly / offset) the set of static cameras 110, and the another set of non-static cameras 112 opposite (directly or indirectly / offset) the set of non-static cameras 112. Therefore, the aircraft 104 has another profile view that is imaged. Accordingly, the computing instance 114 receives the set of video streams from the set of static cameras 110 and another set of video streams from the another set of static cameras 110. As such, the computing instance may form the panorama video stream from stitching (and dewarping) the set of video streams from the set of static cameras 110 and another panorama video stream from stitching (and dewarping) the another set of static cameras 110. The another panorama video stream may be a flat panorama video stream, which may have the single zoom (e.g., in or out). Accordingly, the videowall 116 or the computing terminal 118 can present the profile view of the aircraft 104 (side A) in the panorama video stream (first)and another profile view of the aircraft 104 (side B) in the another panorama video stream (second), whether simultaneously (e.g., side-by-side) or alternating (e.g., one-at-a-time). Due to such reversed presentation, the videowall 116 or the computing terminal 118 can present the profile view and the another profile view as moving in different (e.g., opposite) directions when tracking the aircraft 104, which may occur when simultaneously presenting the panorama video stream and the another panorama video stream. As such, if needed, then one of such profile views or panorama video streams may flipped or reversed so that the profile view and the another profile view do not appear to be moving in different (e.g., opposite) directions when tracking the aircraft 104, which may occur when simultaneously presenting the panorama video stream and the another panorama video stream. Therefore, in such situation, then the profile view in the panorama video stream and the another profile view in the another panorama video stream may appear to be moving in a common direction (e.g., towards an edge of a display when viewed upright). Therefore, the videowall 116 or the computing terminal 118 may simultaneously present the panorama video stream and the another panorama video stream or alternate between presenting the panorama video stream and the another panorama video stream.

[0092] FIG. 12 shows a diagram of an embodiment of a set of video streams from a set of static cameras getting dewarped when warped and then stitched for presentation as a panorama video stream on a display according to this disclosure. As explained above in context of FIGS. 1-11 , the computing instance 114 dewarps, if needed, the set of video streams received from the set of static cameras 110 and then stitches the set of video streams as dewarped to form the panorama video stream. The panorama video stream may be a flat panorama video stream, which may have the single zoom (e.g., in or out).

[0093] FIG. 13 shows a diagram of an embodiment of a redundancy for a set of static cameras for working with a computing instance to generate a panorama video stream according to this disclosure. As explained above in context of FIGS. 1 -12, since at least one tower 108 of the set of towers 108 may host at least one non-static camera 112 of the set of non-static cameras 112 that is redundant to at least one static camera 110 of the set of static cameras 110 hosted by the at least one tower 108, if the at least one static camera 110 is inoperative (e.g., broken), then the at least one non-static camera 112 can take over (e.g., based on a manual request, based on an automated detectionof a relevant fault), i.e., failover or substitute for the static camera 110, and generate a respective video stream to be included in the set of video streams based on which the panorama video stream may be formed. Such form of redundancy can be as long as needed or for a predetermined time period. Note that this may occur when the at least one non-static camera 112 is positioned to have a common optical axis or field of view with the at least one static camera 110 on the at least one tower 108. Likewise, note that when such failover occurs, the at least one non-static camera 112 can be synchronized or configured with the set of static cameras 110 that are operative such that the panorama video stream can still be generated or not distorted. The panorama video stream may be a flat panorama video stream, which may have the single zoom (e.g., in or out).

[0094] FIG. 14 shows a diagram of an embodiment of a panorama video stream along with its technological advantages according to this disclosure. As explained above in context of FIGS. 1 -13, how the panorama video stream is generated and how the panorama video stream is presented provides various technological advantages, as explained in FIG. 14.

[0095] FIG. 15 shows a diagram of an embodiment of a set of non-static cameras positioned along a side of a road for imaging the road such that a computing instance can detect an FOD on the road according to this disclosure. As explained above in context of FIGS. 1 -14, the set of non-static cameras 112 that may (i) be hosted by the set of towers 108, (ii) be spaced apart from the side at the set of distances that are substantially same to each other, (iii) are scheduled to perform a set of patrol tours to image the road 102, and (iv) have the set of fields of view towards the side while overlapping each other such that the set of non-static cameras 112 generates the set of video streams imaging the set of fields of view where at least two non-static cameras 112 of the set of non-static cameras 112 are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road 102 simultaneously from at least two fields of view in the set of fields of view that are optically different from each other. Therefore, the computing instance 114 may be programmed to detect the FOD 106 on the common segment in at least two video streams of the set of video streams imaged by the at least two non-static cameras 112 performing the at least two patrol tours from the at least two fields of view when the FOD 106 is on the common segment and present the user interface on theapplication program running on the computing terminal 118, where the user interface is programmed to allow the operator to perform the visual inspection of the FOD 106 that has been detected on the common segment and take the action (e.g., generate an alert, call an emergency service) based on the visual inspection. The computing instance 114 may be programmed to identify the FOD 106 that has been detected (e.g., a bird, a fragment of a tire). However, note that this configuration is not required. For example, the set of non-static cameras 112 may (i) be hosted by the set of towers 108, (ii) be spaced apart from the side at a set of distances that are substantially same, (iii) be scheduled to perform a set of patrol tours to image the road 102, and (iv) have a set of fields of view towards the side while overlapping each other such that the set of non-static cameras 112 generates a set of video streams imaging the set of fields of view where at least two non-static cameras 112 of the set of non-static cameras 112 are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road 102 simultaneously from at least two fields of view in the set of fields of view that are optically different from each other, attempt to detect an FOD (e.g., a tire segment, awheel, a mechanical tool) on the common segment, and generate at least two confidence level estimates for the FOD on the common segment when detected. These at least two non- static cameras 112 may be similarly trained by an ANN to detect the FOD on the common segment, whether frontally or laterally, before deployment as disclosed herein (e.g., for edge computing). As such, these at least two non-static cameras 112 may attempt to detect the FOD on the common segment from these at least two fields of view in the set of fields of view that are optically different from each other and may generate their own respective identical or non-identical confidence levels indicating whether that respective camera 112 estimates the FOD to be an actual FOD or not. For example, one such non- static camera 112 may generate its own confidence level estimate of the FOD at 30% from one field of view (e.g., front), whereas the other non-static camera 112 may generate its own confidence level estimate of the FOD at 95% from the other field of view (e.g., lateral). For example, one such non-static camera 112 may generate its own confidence level estimate of the FOD as low from one field of view (e.g., diagonal) whereas the other non-static camera 112 may generate its own confidence level estimate of the FOD as high from another field of view (e.g., rear). Regardless of how such confidence levelestimates are expressed, these confidence level estimates may be availed (e.g., sent) to the computing instance 114. Therefore, the computing instance 114 may be programmed to: access the set of video streams from the set of non-static cameras 112 and these at least two confidence level estimates; form a determination whether the FOD is present on the common segment based on these at least two confidence level estimates; and present a user interface on an application program running on a computing terminal, where the user interface is programmed to allow an operator to perform a visual inspection of the FOD that has been detected on the common segment and take an action based on the visual inspection, as disclosed herein. The computing instance 114 may form the determination that the FOD is present on the common segment if a higher confidence estimate level of these at least two confidence level estimates satisfies or does not satisfy a predetermined threshold, since the FOD is sufficiently dangerous to the aircraft 104 that a false positive, if any, may be acceptable to an operator of the computing instance 114 or the application program running on the computing terminal. Although this configuration has been described with respect to at least two non-static cameras 112 that are laterally neighboring, whether consecutively or non-consecutively, this configuration is not required and similar techniques may apply when at least two non-static cameras 112 are opposite each other, whether directly (e.g., facing) or indirectly (e.g., offset), whether consecutively or non-consecutively.

[0096] The common segment may be imaged from at least two non-static cameras 112 (e.g., three) that are consecutively hosted on at least two towers 108 (e.g., three) from the set of towers 108, which may be on a per-side basis, as further explained below. When there are two non-static cameras 112 consecutively positioned along the side of the road 102 while having overlapping fields of view, then either non-static camera 112 one can redundant to the other non-static camera 112, as explained herein. When there are three non-static cameras 112 consecutively positioned along the side of the road 102 while having overlapping fields of view, then either or both of the non-middle non-static cameras 112 can be redundant to the middle non-static camera.

[0097] The common segment may be imaged from at least two non-static cameras 112 (e.g., three) that are consecutively hosted on at least two towers 108 (e.g., three) from the set of towers 108, which may be on a per-side basis, as further explained below.When there are two non-static cameras 112 consecutively positioned along the side of the road 102 while having overlapping fields of view, then either non-static camera 112 one can redundant to the other non-static camera 112, as explained herein. When there are three non-static cameras 112 consecutively positioned along the side of the road 102 while having overlapping fields of view, then either or both of the non-middle non-static cameras 112 can be redundant to the middle non-static camera.

[0098] FIG. 16 shows a diagram of an embodiment of a first set of non-static cameras positioned along a first side (side A) of a road for imaging the road (first configuration) and a second set of non-static cameras positioned along a second side (side B) of the road for imaging the road (second configuration), where the first set of non-static cameras is hosted directly opposite the second set of non-static cameras, such that a computing instance can detect an FOD on the road according to this disclosure. FIG. 17 shows a diagram of an embodiment of a first set of non-static cameras positioned along a first side (side A) of a road for imaging the road (first configuration) and a second set of non-static cameras positioned along a second side (side B) of the road for imaging the road (second configuration), where the first set of non-static cameras is hosted indirectly opposite (offset) the second set of non-static cameras, such that a computing instance can detect an FOD on the road according to this disclosure. FIG. 18 shows a diagram of an embodiment of a set of non-static cameras being hosted to image an FOD from a set of fields of view that are optically different from each other from a side of a road according to this disclosure. FIG. 19 shows a diagram of an embodiment of a first set of non-static cameras being hosted to image an FOD from a first set of fields of view that are optically different from each other from a first side of a road (first configuration) and a second set of non-static cameras being hosted to image the FOD from a second set of fields of view that are optically different from each other from a second side of the road (second configuration) indirectly opposing the first side according to this disclosure. As explained above in context of FIGS. 1-15, there is another set of towers 108 with another set of static cameras 110 and another set of non-static cameras 112, where the another set of towers 108 is opposite (directly or indirectly / offset) the set of towers 108, the another set of static cameras 110 opposite (directly or indirectly / offset) the set of static cameras 110, and the another set of non-static cameras 112 opposite (directly or indirectly / offset) theset of non-static cameras 112. Therefore, the road 102 may be imaged from different fields of view per side, which may enable the FOD 106 to be imaged from different fields of view per side, while enabling redundancy for at least one non-static camera 112 from a neighboring non-static camera 112 per side. As such, the computing instance 114 may receive the set of video streams from the set of non-static cameras 112 and another set of video streams from the another set of non-static cameras 112, which may collectively allow the computing instance 114 to more accurately detect the FOD 106 or identify the FOD 106 or detect an event involving the road 102, the aircraft 104, or the FOD 106 or identify the event involving the road 102, the aircraft 104, or the FOD 106. The computing instance 114 may be programmed to identify a smoke, a steam, a fire, or a liquid extending from the road 102 or the aircraft 104 and issue an alert on the user interface. During patrol tours, the computing instance 114 may be programmed to detect the FOD 106 and another object or event involving the road 102, the aircraft 104, or the FOD 106, where some non-static cameras 112 detect the FOD 106 and some non-static cameras detect another object or event involving the road 102, the aircraft 104, or the FOD 106.

[0099] FIG. 20 shows a diagram of an embodiment of a redundancy for a set of non- static cameras for working with a computing instance to identify an FOD according to this disclosure. As explained above in context of FIGS. 1 -19, since the set of non-static cameras 112 have the set of fields of view towards the side while overlapping each other and at least one non-static camera 112 of at least two non-static cameras 112 that are consecutive to each other is redundant to at least one another non-static camera 112 of the at least two non-static cameras 112, if the another non-static camera 112 of the at least two non-static cameras 112 is inoperative (e.g., broken), then the at least one non- static camera 112 of the at least two non-static cameras 112 can take over (e.g., based on a manual request, based on an automated detection of a relevant fault), i.e. , failover or substitute for the another non-static camera 112 of the at least two non-static cameras 112, and generate a respective video stream. Such form of redundancy can be as long as needed or for a predetermined time period.

[0100] FIG. 21 shows a diagram of a non-static camera configured for a patrol tour to image a set of sub-zones with a zone according to this disclosure. As explained above in context of FIGS. 1 -20, the non-static camera 112 may be configured for a patrol tour (e.g.,move along a set of preset positions while imaging from the set of preset positions), which may be iterative over a period of time. Correspondingly, the set of non-static cameras 112 may have the set of patrol tours. As such, the patrol tour may include the non-static camera 112 iterating through a set of sub-zones within a zone dedicated to the field of view of that non-static camera 112. As shown in FIG. 21 , the zone includes twelve subzones, although less or more sub-zones are possible, as needed. The zone or the set of sub-zones may be associated with a geolocational coordinate or a set of geolocational coordinates based on which the computing instance 114 geolocates the FOD 106 on the common segment of the road 102, generates a geolocational content associated with the FOD 106 that has been identified, and presents the geolocational content on the user interface for the operator to perform the visual inspection of the FOD 106 and take the action based on the visual inspection. The geolocation coordinate or the set of geolocation coordinates may be in a format of World Geodetic System 1984 (WGS84), International Terrestrial Reference Frame (ITRF), or another suitable format. These modalities of configuration may be replicated when there multiple sets of towers 108, each tower 108 including at least one non-static cameras 112, as explained herein, to provide more accurate geolocation or detection of the FOD 106 or identification of the FOD 106.

[0101] The video stream from the non-static camera 112 or the set of video streams from the set of non-static cameras 112 may allow the computing instance 114 to detect an object other than the FOD 106 (e.g., a human, an airport worker, a stranger) or an event (e.g., a fire, a collision of the aircraft 104) on the road 102. Therefore, the computing instance 114 may be programmed to detect the object other than the FOD 106 or an event (e.g., a fire) on the common segment of the road 102 and the user interface on the computing terminal 118 may be programmed to allow the operator to take an action (e.g., issue an alert, call an emergency service provider) based on the object being identified. The computing instance 114 may be programmed to identify the object (e.g., a human, an airport worker, a stranger) or the event (e.g., a fire, a collision of the aircraft 104) that has been detected. The computing instance 114 may be programmed to identify a smoke, a steam, a fire, or a liquid extending from the road 102 or the aircraft 104 and issue an alert on the user interface.

[0102] FIG. 22 shows a diagram of an embodiment of a non-static detection of an FOD along with its technological advantages according to this disclosure. As explained above in context of FIGS. 1 -21 , how the non-static camera 112 or the set of non-static cameras 112 is configured and positioned to image the road 102 such that the computing instance 114 detects and identifies the FOD 106 provides various technological advantages, as explained in FIG. 22.

[0103] FIG. 23 shows a diagram of an embodiment of a user interface according to this disclosure. FIG. 24 shows a diagram of a user interface simultaneously presenting a panorama video stream depicting a profile view of an aircraft and a schematic top view of a road on which the aircraft moves, where the schematic top view is segmented into a set of zones corresponding to a set of towers hosting a set of static cameras and a set of non-static cameras according to this disclosure. FIG. 25 shows a diagram of a user interface presenting a pane with a content identified or formed based on a set of video streams from a set of static cameras or a set of non-static cameras oriented towards a road on which an aircraft is positioned according to this disclosure. FIG. 26 shows a diagram of an embodiment of a legend for a user interface presented on a display according to this disclosure. FIG. 27 shows a diagram of an embodiment of a set of panes from a user interface presented on a display according to this disclosure. FIG. 28 shows a diagram of an embodiment of a legend for a user interface presented on a display according to this disclosure. FIG. 29 shows a diagram of an embodiment of a position of an operator operating a computing terminal according to this disclosure. As explained above in context of FIGS. 1-22, the user interface may be presented on the videowall 116 or the computing terminal 118 (e.g., a display thereof). The user interface may present at least one of the panorama video stream, the schematic top view, or a pane (or a set of panes). The user interface may simultaneously present at least two of the panorama video stream, the schematic top view, or the pane (or the set of panes). The pane may include a visual tile. The set of panes may include a set of visual tiles. Note that these user interfaces may be presented in various ways. For example, there may be a right section of the user interface windows or panes (top and bottom) is responsible for a presenting the panorama video stream and a study of events using image magnification, as disclosed herein. The right section may also include a protocol of events, i.e. , incidentson the road 102, which may be in the panorama video stream. There may be a left section of the user interface with windows or panes (top and bottom) responsible for presenting with the FOD and allowing for a study of the FOD using image magnification, as disclosed herein. The left section may include a protocol of detected FODs (e.g., garbage, animals, birds, people, land vehicles). There may be a central section having an enlarged image of the aircraft 104 moving along the road 102.

[0104] The panorama video stream may correspond, which may be end-to-end, to the road 102, be flat, or have the single zoom (e.g., in and out), which may be controlled from the computing terminal 118. The panorama video stream presents the profile view of the aircraft 104 (although other views of the aircraft 104 are possible depending on how the aircraft 104 is positioned on the road 102, how the road 102 is positioned, or how the set of static cameras 110 is positioned). These modalities of presentation may be replicated if there are multiple panorama video streams presented in the user interface of the computing terminal 118 or the videowall 116.

[0105] The computing instance 114 may be programmed to present the panorama video stream in the user interface on the computing terminal 118 and a visual identifier (or indicator) for the profile view of the aircraft 104 over the panorama video stream presented in the user interface on the computing terminal 118. The visual identifier (or indicator) may include a flight identifier (e.g., an alphanumeric string) associated with the aircraft 104, which may be color-coded to match or contrast the visual identifier (or indicator). The visual identifier (or indicator) may include a pair of brackets, including parenthesis, enclosing the profile view of the aircraft 104, a bounding box enclosing the profile view of the aircraft 104, a pointer pointed at the profile view of the aircraft 104, a line visually associated with the profile view of the aircraft 104, a shape visually associated with the profile view of the aircraft 104, or any other type of the visual identifier (or indicator) for the profile view of the aircraft 104. If there are multiple aircraft 104, then there may be a visual identifier (or indicator) for each aircraft 104. The visual identifier (or indicator) may be generic to the aircraft 104 or change (e.g., custom or unique) for each aircraft 104, which may be based on the computing instance 114 accessing a set flight data for the aircraft 104 and selecting a visual identifier (e.g., a type of aircraft 104, a model of aircraft 104, an airline coloring scheme of aircraft 104) based on the set of flightdata. These modalities of presentation may be replicated if there are multiple panorama video streams presented in the user interface on the computing terminal 118, whether identically or different to minimize viewer confusion. The visual identifiers (or indicators) for the profile views over the panorama video streams may be of same type (e.g., same color-coding, same shape, same size) or not of same type.

[0106] The computing instance 114 may programmed to present a visual identifier (or indicator) for the profile view of the aircraft 104 over the panorama video stream presented on the videowall 116. The visual identifier (or indicator) may include a flight identifier (e.g., an alphanumeric string) associated with the aircraft 104, which may be color-coded to match or contrast the visual identifier. The visual identifier (or indicator) may include a pair of brackets, including parenthesis, enclosing the profile view of the aircraft 104, a bounding box enclosing the profile view of the aircraft 104, a pointer pointed at the profile view of the aircraft 104, a line visually associated with the profile view of the aircraft 104, a shape visually associated with the profile view of the aircraft 104, or any other type of the visual identifier (or indicator) for the profile view of the aircraft 104. If there are multiple aircraft 104, then there may be the visual identifier for each aircraft 104. The visual identifier (or indicator) may be generic to the aircraft 104 or change (e.g., custom or unique) for each aircraft 104, which may be based on the computing instance 114 accessing a set flight data for the aircraft 104 and selecting a visual identifier (e.g., a type of aircraft 104, a model of aircraft 104, an airline coloring scheme of aircraft 104) based on the set of flight data. These modalities of presentation may be replicated if there are multiple panorama video streams presented in the videowall 116, whether identically or different to minimize viewer confusion.

[0107] There may be multiple panorama video streams simultaneously presented if there are multiple roads 102 being monitored. Likewise, as explained above, for one road 102, there may be two panorama video streams, which may be presented simultaneously or alternated, where one panorama video stream presents one profile view of the aircraft 104 from one side thereof and another panorama video streams presents another profile view of the aircraft 104 from another side thereof. Since these profile views may be moving in the panorama video streams in different (e.g., opposite) directions, if desired (e.g., to minimize viewer confusion), then one of such panorama video streams may beflipped or reversed so that the profile views move on the panorama video streams in a common direction (e.g., toward a lateral side of a viewport).

[0108] The schematic top view may be simultaneously presented with the panorama video stream or the pane (or the set of panes), which may be side-by-side. The schematic top view may correspond, which may be end-to-end, to the road 102 or to the panorama video stream, which may be end-to-end, to function as a map of the road 102. The schematic top view may be parallel to the panorama video stream. There may be multiple schematic top views simultaneously presented if there are multiple roads 102 being monitored. When the user interface presents two panorama video streams, as explained above, the schematic top view may extend (e.g., interpose) between the two panorama video streams. The pane (or the set of panes) may be simultaneously presented with the panorama video stream or the schematic top view. Some of such panes may be positioned along the panorama video stream. Some of such panes may be positioned along the schematic top view.

[0109] The pane (or the set of panes) may present a content related to the road 102, the aircraft 104, or the FOD 106, as sourced from the set of static cameras 110 or the set of non-static cameras 112, as appropriate. The pane (or the set of panes) may present the profile view of the aircraft 104. When there are two profile views of the aircraft 104 (portside and starboard), then the set of panes may present those two profile views of the aircraft 104, which may appear to be from different sides. If desired (e.g., to minimize viewer confusion), then one of such profile views may be flipped or reversed so that the profile views appear consistently oriented in a common direction (e.g., toward a lateral side of a viewport). Some of the panes may present a log of events at least one of which includes the FOD 106. Some of the panes may present an image of the FOD 106 and a detail related to the FOD 106 (e.g., a date stamp, a time stamp, an assigned identifier for the FOD 106). Some of the panes may presents the profile view of the aircraft 104 when the aircraft 104 is on the road 102. There may be two different panes presenting different content related to the road 102, the aircraft 104, or the FOD 106.

[0110] The pane (or the set of panes) may presents a visual identifier (or indicator) for the FOD 106. The visual indicator (or indicator) may include a pair of brackets enclosing the FOD 106 in the pane, a bounding box enclosing the FOD 106 in the pane, a pointerpointed at the FOD 106 in the pane, a line visually associated with the FOD 106 in the pane, or a shape visually associated with the FOD 106 in the pane.

[0111] The panorama video stream, which may be flat and have the single zoom, as controlled by the computing terminal 118, may present a visual identifier (or indicator) for the profile view of the aircraft 104 over the panorama video stream when the aircraft 104 is on the road 102 along the side. The visual identifier (or indicator) may include a pair of brackets, including parenthesis, enclosing the profile view of the aircraft 104, a bounding box enclosing the profile view of the aircraft 104, a pointer pointed at the profile view of the aircraft 104, a line visually associated with the profile view of the aircraft 104, a shape visually associated with the profile view of the aircraft 104, or any other type of the visual identifier (or indicator) for the profile view of the aircraft 104.

[0112] The schematic top view may present a graphic (e.g., an icon) for the aircraft 104 on the road 102. The graphic may be generic to the aircraft 104 or change (e.g., custom or unique) for each aircraft 104, which may be based on the computing instance 114 accessing a set flight data for the aircraft 104 and selecting a graphic (e.g., a type of aircraft 104, a model of aircraft 104, an airline coloring scheme of aircraft 104) based on the set of flight data.

[0113] The graphic may move in the schematic top view as the aircraft 104 moves on the road 102. The graphic may move in the schematic top view as the profile view of the aircraft 104 in the panorama video stream or the visual identifier (or indicator) for the aircraft 104 over the panorama video stream moves when the aircraft 104 moves on the road 102. The graphic may move in the schematic top view in a same common direction as the profile view of the aircraft 104 in the panorama video stream or the visual identifier (or indicator) for the aircraft 104 moves over the panorama video stream when the aircraft 104 moves on the road 102 or in a different (e.g., opposite) direction as the profile view of the aircraft 104 in the panorama video stream or the visual identifier (or indicator) for the aircraft 104 moves over the panorama video stream when the aircraft 104 moves on the road 102. The graphic may move in the schematic top view together (e.g., in-sync) with the profile view of the aircraft 104 in the panorama video stream when the aircraft 104 moves on the road 102 or the visual identifier (or indicator) for the aircraft 104 over the panorama video stream when the aircraft 104 moves on the road 102. The graphicmay move in the schematic top view when the aircraft 104 moves on the road 102 based on the computing instance 114 instructing the graphic to move in the schematic top view as the computing instance 114 tracks the aircraft 104 on the road from the set of video streams sourced from the set of static cameras 110 or the set of video streams sourced from the set of non-static cameras 112 when the aircraft 104 moves on the road 102. The user interface includes a lateral end portion and the visual identifier (or indicator) for the aircraft 104 presented over the panorama video stream and the graphic in the schematic top view may move together (e.g., in-sync) towards the lateral end portion when the aircraft 104 moves on the road 102. If there are multiple roads 102 being monitored, then there may be multiple top schematic views, one per road 102, and multiple panorama video streams, one per road 102, presented, which may be simultaneously, in the user interface. The multiple top schematic views may extend between the multiple panorama video streams, with corresponding schematic view and panorama video stream extending along each other to minimize viewer confusion.

[0114] The schematic top view may present a set of graphics (e.g., a set of icons) for the set of towers 108. The schematic top view may be segmented (e.g., a set dashed partition lines) into a set of zones corresponding to the set of towers 108 (e.g., one tower per zone), one graphic per zone. Each zone in the set of zones presented in the schematic top view may be labeled with an address, which may correspond to a unit of length for the road 102 (e.g., 1000 meters, 1100 meters, 1200 meters, 1300 meters, 1400 meters). When there are multiple sets of towers 108, then these modalities of presentation may be replicated accordingly.

[0115] FIG. 30 shows a diagram of a set of parameters for an architecture according to this disclosure. FIGS. 31 a-31 c shows a diagram of a set of parameters for an architecture according to this disclosure. As explained above in context of FIGS. 1 -29, the architecture 100 includes various components, which have certain performance standards and configuration parameters. At least one static camera 110 of the set of static cameras 110 has a first matrix size and at least one non-static camera 112 of the set of non-static cameras 112 has a second matrix size, which may be identical to the first matrix size. At least one static camera 110 of the set of static cameras 110 has a first pixel bit depth and at least one non-static camera 112 of the set of non-static cameras 112 has asecond pixel bit depth, which may be identical to the first pixel bit depth. At least one static camera 110 of the set of static cameras 110 has a first frame rate and at least one nonstatic camera 112 of the set of non-static cameras 112 has a second frame rate depth, which may be identical to the first frame rate. At least one non-static camera 112 of at least two non-static cameras 112 may be redundant to at least one another non-static camera 112 of the at least two non-static cameras 112. The computing instance 114 may be programmed to distinguish the FOD 106 based on a type thereof. The type includes at least two of a vehicle, a person, and an animal.

[0116] The architecture 100 may further include a light source hosted by at least one tower 108 of the set of towers 108. The light source may be in communication with the computing instance 114 such that the light source is controllably directable to output a light at or in a direction of the road 102, the aircraft 104, or the FOD 106 based on a content sourced from the set of streams imaged by the set of static cameras 110 or the set of streams imaged by the set of non-static cameras 112 or as commanded by the computing terminal 118. The light source may include a laser light source, an infrared light source, or another suitable light source. The light source may be controllably directable to output the light at or in the direction of the road 102, the aircraft 104, or the FOD 106. The light source may be an infrared light source configured to output an infrared light and hosted by at least one tower 108 of the set of towers 108, where the infrared light source is in communication with the computing instance 114 such that the computing instance controls the infrared light source to output the infrared light towards the road 102, the aircraft 104, or the FOD 106 based on at least one video stream of the set of video streams sourced from the set of static cameras 110 or the set of video streams sourced from the set of non-static cameras 112.

[0117] The computing terminal 118 may be operated by the operator who make take the action on the user interface. The action may be performing the visual inspection of the FOD 106 that has been detected on the common segment on the user interface and take the action (e.g., generate an alert, call an emergency service, activate an alarm, send a message to the aircraft 102, direct the light source at the road 102 or the aircraft 104 or the FOD 106) based on the visual inspection on the user interface. The action maybe based on the light being output by the light source (e.g., direct an emergency service team to a specific spot on the road 102 or on the airplane 104).

[0118] FIGS. 32a to 32b show a diagram of an embodiment a set of regulations for an architecture to be compliant with according to this disclosure. As explained above in context of FIGS. 1 -31 , the architecture 100 may or may not be compliant with government regulations identifier in FIGS. 32a to 32b.

[0119] As used herein, terms, such as "then," "next," or other similar forms are not intended to limit an order of steps. Rather, these terms are simply used to guide a reader through this disclosure. Although process flow diagrams may describe some operations as a sequential process, many of those operations can be performed in parallel or concurrently. In addition, the order of operations may be re-arranged.

[0120] As used herein, a term “response” or “responsive” are intended to include a machine-sourced action or inaction, such as an input (e.g., local, remote), or a user- sourced action or inaction, such as an input (e.g., via user input device).

[0121] Unless otherwise defined, all terms (including technical and scientific terms) used herein have a same meaning as commonly understood by skilled artisans to which this disclosure belongs. These terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in context of relevant art and should not be interpreted in an idealized or overly formal sense, unless expressly so defined herein.

[0122] Features or functionality described with respect to certain embodiments may be combined and sub-combined in or with various other embodiments. Also, different aspects, components, or elements of embodiments, as disclosed herein, may be combined and sub-combined in a similar manner as well. Further, some embodiments, whether individually or collectively, may be components of a larger system, wherein other procedures may take precedence over or otherwise modify their application. Additionally, a number of steps may be required before, after, or concurrently with embodiments, as disclosed herein. Note that any or all methods or processes, as disclosed herein, can be at least partially performed via at least one entity or actor in any manner.

[0123] Hereby, all issued patents, published patent applications, and non-patent publications that are mentioned or referred to in this disclosure are herein incorporatedby reference in their entirety for all purposes, to a same extent as if each individual issued patent, published patent application, or non-patent publication were specifically and individually indicated to be incorporated by reference. To be even more clear, all incorporations by reference specifically include those incorporated publications as if those specific publications are copied and pasted herein, as if originally included in this disclosure for all purposes of this disclosure. Therefore, any reference to something being disclosed herein includes all subject matter incorporated by reference, as explained above. However, if any disclosures are incorporated herein by reference and such disclosures conflict in part or in whole with this disclosure, then to an extent of the conflict or broader disclosure or broader definition of terms, this disclosure controls. If such disclosures conflict in part or in whole with one another, then to an extent of conflict, the later-dated disclosure controls.

[0124] Various embodiments of the present disclosure may be implemented in a data processing system suitable for storing and / or executing program code that includes at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements include, for instance, local memory employed during actual execution of the program code, bulk storage, and cache memory which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.

[0125] I / O devices (including, but not limited to, keyboards, displays, pointing devices, DASD, tape, CDs, DVDs, thumb drives and other memory media, etc.) can be coupled to the system either directly or through intervening I / O controllers. Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modems, and Ethernet cards are just a few of the available types of network adapters.

[0126] This disclosure may be embodied in a system, a method, and / or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present disclosure. The computer readable storage medium can be a tangible device that can retain and store instructionsfor use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing.

[0127] Computer readable program instructions described herein can be downloaded to respective computing / processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and / or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and / or edge servers. A network adapter card or network interface in each computing / processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing / processing device.

[0128] Computer readable program instructions for carrying out operations of the present disclosure may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. A code segment or machine-executable instructions may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or programstatements. A code segment may be coupled to another code segment or a hardware circuit by passing and / or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, among others. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In various embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present disclosure.

[0129] Aspects of the present disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer readable program instructions. The various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer soft-ware, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but suchimplementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0130] The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and / or flowchart illustration, and combinations of blocks in the block diagrams and / or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

[0131] Words such as “then,” “next,” etc. are not intended to limit the order of the steps; these words are simply used to guide the reader through the description of the methods. Although process flow diagrams may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function or the main function.

[0132] Although various embodiments have been depicted and described in detail herein, skilled artisans know that various modifications, additions, substitutions and the like can be made without departing from this disclosure. As such, these modifications, additions, substitutions and the like are considered to be within this disclosure.

Claims

CLAIMSWhat is claimed is:1 . A system, comprising: a set of towers positioned along a side of a road on which an aircraft moves, wherein the aircraft has a profile view; a set of static cameras that (i) are hosted by the set of towers, (ii) are spaced apart from the side at a first set of distances that are substantially same, (iii) are optically parallel to each other, and (iv) have a first set of fields of view towards the side while overlapping each other such that the set of static cameras generates a first set of video streams synchronously imaging the first set of fields of view; a set of non-static cameras that (i) are hosted by the set of towers, (ii) are spaced apart from the side at a second set of distances that are substantially same, (iii) are scheduled to perform a set of patrol tours to image the road, and (iv) have a second set of fields of view towards the side while overlapping each other such that the set of nonstatic cameras generates a second set of video streams imaging the second set of fields of view where at least two non-static cameras of the set of non-static cameras are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road simultaneously from at least two fields of view in the second set of fields of view that are optically different from each other, wherein at least one tower of the set of towers hosts at least one non-static camera of the set of non-static cameras that is redundant to at least one static camera of the set of static cameras hosted by the at least one tower; a computing instance programmed to: access the first set of video streams; identify the aircraft in the first set of video streams when the aircraft is on the road along the side; track the aircraft in the first set of video streams when the aircraft is on the road along the side; detect a foreign object debris (FOD) on the common segment in at least two video streams of the second set of video streams imaged by the at least two non-staticcameras performing the at least two patrol tours from the at least two fields of view when the FOD is on the common segment; stitch the first set of video streams such that a panorama video stream is formed depicting the profile view when the aircraft is on the road along the side; present the panorama video stream on a videowall such that the profile view is visible when the aircraft is on the road along the side; and present a user interface on an application program running on a computing terminal, wherein the user interface is programmed to allow an operator to perform a visual inspection of the FOD that has been detected on the common segment and take an action based on the visual inspection.

2. The system of claim 1 , wherein the first set of video streams is dewarped before the first set of video streams is stitched.

3. The system of claim 1 , wherein the at least one static camera is positioned above or below the at least one non-static camera on the at least one tower.

4. The system of claim 1 , wherein the common segment is imaged from the at least two non-static cameras that are consecutively hosted on at least two towers from the set of towers.

5. The system of claim 4, wherein the at least two non-static cameras are at least three non-static cameras, wherein the at least two towers are at least three towers.

6. The system of claim 1 , wherein the videowall and the computing terminal are colocated.

7. The system of claim 1 , wherein the videowall and the computing terminal are not colocated.

8. The system of claim 1 , wherein the computing instance is programmed to present a visual identifier for the profile view over the panorama video stream.

9. The system of claim 8, wherein the visual identifier includes a pair of brackets enclosing the profile view, a bounding box enclosing the profile view, a pointer pointed at the profile view, a line visually associated with the profile view, or a shape visually associated with the profile view.

10. The system of claim 1 , wherein the action is a first action, wherein the computing instance is further programmed to: detect an object other than the FOD on the common segment in the at least two video streams, wherein the user interface is programmed to allow the operator to take a second action based on the object being detected.11 . The system of claim 1 , wherein the computing instance is further programmed to: record the panorama video stream, the first set of video streams, or the second set of video streams into an archive accessible from the user interface such that an incident involving the aircraft on the road or the FOD on the common segment can be investigated on the user interface.

12. The system of claim 1 , wherein the road is a runway having a first end portion and a second end portion, wherein the panorama video stream is directed at the runway from the first end portion to the second end portion.

13. The system of claim 1 , wherein the computing instance is further programmed to enable a single zoom for the panorama video stream.

14. The system of claim 1 , wherein the set of towers is a first set of towers, wherein the set of static cameras is a first set of static cameras, wherein the set of non-static cameras is a first set of non-static cameras, wherein the side is a first side, wherein the road has a second side opposing the first side, wherein the set of patrol tours is a first set of patroltours, wherein the panorama video stream is a first panorama video stream, wherein the profile view is a first profile view, and further comprising: a second set of towers positioned along the second side; a second set of static cameras that (i) are hosted by the second set of towers, (ii) are spaced apart from the second side at a third set of distances that are substantially same, (iii) are optically parallel to each other, and (iv) have a third set of fields of view towards the second side while overlapping each other such that the second set of static cameras generates a third set of video streams synchronously imaging the third set of fields of view; a second set of non-static cameras that (i) are hosted by the second set of towers, (ii) are spaced apart from the second side at a fourth set of distances that are substantially same, (iii) are scheduled to perform a second set of patrol tours to image the road, and (iv) have a fourth set of fields of view towards the second side while overlapping each other such that the second set of non-static cameras generates a fourth set of video streams imaging the fourth set of fields of view where at least two non-static cameras of the second set of non-static cameras are scheduled to perform at least two patrol tours of the second set of patrol tours to image the common segment simultaneously from at least two fields of view in the fourth set of fields of view that are optically different from each other, wherein at least one tower of the second set of towers hosts at least one non- static camera of the second set of non-static cameras that is redundant to at least one static camera of the second set of static cameras hosted by the at least one tower of the second set of towers, wherein the visual inspection is a first visual inspection; and wherein the computing instance is further programmed to: access the third set of video streams; identify the aircraft in the third set of video streams when the aircraft is on the road along the second side between the first side and the second side; track the aircraft in the third set of video streams when the aircraft is on the road along the second side between the first side and the second side; detect the foreign object debris (FOD) on the common segment in at least two video streams of the fourth set of video streams imaged by the at least two non-static cameras of the second set of non-static cameras performing the at least two patrol toursof the second set of patrol tours from the at least two fields of view in the fourth set of fields of view when the FOD is on the common segment; stitch the third set of video streams such that a second panorama video stream is formed depicting a second profile view when the aircraft is on the road along the second side between the first side and the second side; and present the second panorama video stream on the videowall such that the second profile view is visible when the aircraft is on the road along the second side, wherein the user interface is programmed to allow the operator to perform a second visual inspection of the FOD that has been identified on the common segment in the at least two video streams of the fourth set of video streams and take the action based on the second visual inspection.

15. The system of claim 14, wherein the first set of towers directly opposes the second set of towers.

16. The system of claim 1 , wherein the first set of towers indirectly opposes the second set of towers.

17. The system of claim 14, wherein the user interface is programmed to simultaneously present the first panorama video stream and the second panorama video stream.

18. The system of claim 14, wherein the user interface is programmed to allow the user interface to alternate between presenting the first panorama video stream and the second panorama video stream.

19. The system of claim 14, wherein at least one distance of the first set of distances is substantially identical to at least one distance of the third set of distances.

20. The system of claim 14, wherein at least one distance of the second set of distances is substantially identical to at least one distance of the fourth set of distances.

21. The system of claim 14, wherein the computing instance is programmed to form the second panorama video stream based on dewarping the third set of video streams before the third set of video streams is stitched.

22. The system of claim 14, wherein the at least one static camera of the second set of static cameras is positioned above or below the at least one non-static camera of the second set of non-static cameras on the at least one tower of the second set of towers.

23. The system of claim 14, wherein the common segment is imaged from the at least two non-static cameras of the second set of non-static cameras that are consecutively hosted on at least two towers of the second set of towers.

24. The system of claim 23, wherein the at least two non-static cameras of the second set of non-static cameras are at least three non-static cameras, wherein the at least two towers of the second set of towers are at least three towers.

25. The system of claim 14, wherein the computing instance is programmed to present a visual identifier for the second profile view over the second panorama video stream.

26. The system of claim 25, wherein the visual identifier includes a pair of brackets enclosing the second profile view, a bounding box enclosing the second profile view, a pointer pointed at the second profile view, a line visually associated with the second profile view, or a shape visually associated with the second profile view.

27. The system of claim 14, wherein the computing instance is programmed to present a first visual identifier for the first profile view over the first panorama video stream and a second visual identifier for the second profile view over the second panorama video stream, wherein the first visual identifier and the second visual identifier are of same type.

28. The system of claim 14, wherein the computing instance is programmed to present a first visual identifier for the first profile view over the first panorama video stream and asecond visual identifier for the second profile view over the second panorama video stream, wherein the first visual identifier and the second visual identifier are not of same type.

29. The system of claim 14, wherein the action is a first action, wherein the computing instance is further programmed to: detect an object other than the FOD on the common segment in the in at least two video streams of the fourth set of video streams, wherein the user interface is programmed to allow the operator to take a second action based on the object being detected.

30. The system of claim 14, wherein the computing instance is further programmed to: record the second panorama video stream, the third set of video streams, or the fourth set of video streams into an archive accessible from the user interface such that an incident involving the aircraft on the road or the FOD on the common segment can be investigated on the user interface.

31. The system of claim 14, wherein the road is a runway having a first end portion and a second end portion, wherein the second panorama video stream is directed at the runway from the first end portion to the second end portion.

32. The system of claim 14, wherein the computing instance is further programmed to enable a single zoom for the second panorama video stream.

33. The system of claim 14, wherein the common segment is imaged from (i) at least three non-static cameras of the first set of non-static cameras that are consecutively hosted on at least three towers of the first set of towers such that at least two non-static cameras of the at least three non-static cameras are redundant to at least one non-static camera of the at least three non-static cameras or (ii) at least three non-static cameras of the second set of non-static cameras that are consecutively hosted on at least three towers of the second set of towers such that at least two non-static cameras of the atleast three non-static cameras are redundant to at least one non-static camera of the at least three non-static cameras.

34. The system of claim 33, wherein at least three non-static cameras of the first set of non-static cameras that are consecutively hosted on at least three towers of the first set of towers such that at least two non-static cameras of the at least three non-static cameras are redundant to at least one non-static camera of the at least three non-static cameras.

35. The system of claim 33, wherein at least three non-static cameras of the second set of non-static cameras that are consecutively hosted on at least three towers of the second set of towers such that at least two non-static cameras of the at least three non-static cameras are redundant to at least one non-static camera of the at least three non-static cameras.

36. The system of claim 1 , wherein the common segment is imaged from at least three non-static cameras of the set of non-static cameras that are consecutively hosted on at least three towers of the set of towers such that at least two non-static cameras of the at least three non-static cameras are redundant to at least one non-static camera of the at least three non-static cameras.

37. The system of claim 1 , wherein at least one patrol tour of the set of patrol tours includes at least one non-static camera of the set of non-static cameras iterating through a set of sub-zones within a zone dedicated to at least one of field of view of the second set of fields of view, wherein the zone or the set of sub-zones is associated with a geolocational coordinate or a set of geolocational coordinates based on which the computing instance geolocates the FOD on the common segment, generates a geolocational content associated with the FOD that has been detected, and presents the geolocational content on the user interface for the operator to perform the visual inspection of the FOD and take the action based on the visual inspection.

38. The system of claim 37, wherein the at least one patrol tour is included in the at least two patrol tours.

39. The system of claim 1 , further comprising: a light source hosted by at least one tower of the set of towers, wherein the light source is in communication with the computing instance such that the light source is controllably directable to output a light at or in a direction of the road, the aircraft, or the FOD based on a content sourced from the first set of streams or the second set of streams.

40. The system of claim 39, wherein the light source includes a laser light source.41 . The system of claim 39, wherein the light source includes an infrared light source.

42. The system of claim 39, wherein the light source is controllably directable to output the light at or in the direction of the road.

43. The system of claim 39, wherein the light source is controllably directable to output the light at or in the direction of the aircraft.

44. The system of claim 39, wherein the light source is controllably directable to output the light at or in the direction of the FOD.

45. The system of claim 39, wherein the action is based on the light being output by the light source.

46. The system of claim 1 , wherein the computing instance is not in any communication with any radiofrequency radar locally tracking the aircraft.

47. The system of claim 1 , wherein the computing terminal includes the videowall.

48. The system of claim 1 , wherein the computing terminal does not include the videowall.

49. The system of claim 1 , wherein the user interface simultaneously presents (i) the panorama video stream and (ii) a schematic top view of the road corresponding to the panorama video stream.

50. The system of claim 49, wherein the user interface simultaneously presents (i) the panorama video stream, (ii) the schematic top view, and (iii) a pane presenting a content related to the road, the aircraft, or the FOD.51 . The system of claim 50, wherein the content is related to the road.

52. The system of claim 50, wherein the content is related to the aircraft.

53. The system of claim 50, wherein the content is related to the FOD.

54. The system of claim 50, wherein the content includes a log of events at least one of which includes the FOD.

55. The system of claim 50, wherein the content includes an image of the FOD and a detail related to the FOD.

56. The system of claim 49, wherein the user interface simultaneously presents (i) a visual identifier for the profile view over the panorama video stream when the aircraft is on the road along the side among the at least two fields of view of the first set of fields of view and (ii) a graphic for the aircraft over the schematic top view.

57. The system of claim 56, wherein the visual identifier and the graphic move together when the aircraft moves on the road.

58. The system of claim 56, wherein the user interface includes a lateral end portion, wherein the visual identifier and the graphic move together towards the lateral end portion when the aircraft moves on the road.

59. The system of claim 50, wherein the pane presents the profile view when the aircraft is on the road.

60. The system of claim 49, wherein the schematic top view presents a graphic for a position of at least one tower of the set of towers.

61. The system of claim 60, wherein the schematic top view is segmented into a set of zones corresponding to the set of towers, wherein at least one zone of the set of zones contains the graphic.

62. The system of claim 50, wherein the pane presents a visual indicator for the FOD.

63. The system of claim 62, wherein the visual indicator includes a pair of brackets enclosing the FOD in the pane, a bounding box enclosing the FOD in the pane, a pointer pointed at the FOD in the pane, a line visually associated with the FOD in the pane, or a shape visually associated with the FOD in the pane.

64. The system of claim 62, wherein the pane is a first pane, wherein the user interface presents a second pane simultaneous with the first pane, wherein the content is a first content, wherein the second pane presents a second content related to the road, the aircraft, or the FOD.

65. The system of claim 1 , wherein the computing instance is further programmed to identify a smoke, a steam, a fire, or a liquid extending from the aircraft and issue an alert on the user interface.

66. The system of claim 1 , wherein at least one non-static camera of the set of non-static cameras includes a wiper.

67. The system of claim 1 , further comprising: an infrared light source configured to output an infrared light and hosted by at least one tower of the set of towers, wherein the infrared light source is in communication with the computing instance such that the computing instance controls the infrared light source to output the infrared light towards the road, the aircraft, or the FOD based on at least one video stream of the first set of video streams or the second set of video streams.

68. The system of claim 1 , wherein at least one static camera of the set of static cameras has a first matrix size and at least one non-static camera of the set of non-static cameras has a second matrix size identical to the first matrix size.

69. The system of claim 1 , wherein at least one static camera of the set of static cameras has a first pixel bit depth and at least one non-static camera of the set of non-static cameras has a second pixel bit depth identical to the first pixel bit depth.

70. The system of claim 1 , wherein at least one static camera of the set of static cameras has a first frame rate and at least one non-static camera of the set of non-static cameras has a second frame rate depth identical to the first frame rate.71 . The system of claim 1 , wherein at least one non-static camera of the at least two non- static cameras is redundant to at least one another non-static camera of the at least two non-static cameras.

72. The system of claim 1 , wherein the computing instance is programmed to distinguish the FOD based on a type thereof.

73. The system of claim 72, wherein the type includes at least two of a vehicle, a person, and an animal.

74. The system of claim 1 , wherein the set of non-static cameras includes at least one non-static camera other than the at least two non-static cameras that is in communication with the computing instance such that the computing instance is programmed to identify an object or an event other than the FOD during the at least two patrol tours.

75. The system of claim 1 , wherein the panorama video stream is a flat panorama video stream.

76. The system of claim 1 , wherein the action is a first action, wherein the computing instance is further programmed to: identify an event involving the aircraft on the road or the FOD on the common segment from the first set of video streams or the second set of video streams, wherein the user interface is programmed to allow the operator to take a second action based on the event being identified.

77. The system of claim 1 , wherein the computing instance is programmed to present a visual identifier for the profile view over the panorama video stream presented on the videowall.

78. The system of claim 77, wherein the visual identifier includes a flight identifier associated with the aircraft.

79. The system of claim 1 , wherein the computing instance is programmed to present the panorama video stream in the user interface and a visual identifier for the profile view over the panorama video stream presented in the user interface.

80. The system of claim 79, wherein the visual identifier includes a flight identifier associated with the aircraft.

81. A kit, comprising:a set of towers, a set of static cameras, a set of non-static cameras, and a computing instance collectively configured to enable: the set of towers to be positioned along a side of a road on which an aircraft moves, wherein the aircraft has a profile view; the set of static cameras to (i) be hosted by the set of towers, (ii) be spaced apart from the side at a first set of distances that are substantially same, (iii) be optically parallel to each other, and (iv) have a first set of fields of view towards the side while overlapping each other such that the set of static cameras is able to generate a first set of video streams synchronously imaging the first set of fields of view; the set of non-static cameras to (i) be hosted by the set of towers, (ii) be spaced apart from the side at a second set of distances that are substantially same, (iii) be scheduled to perform a set of patrol tours to image the road, and (iv) have a second set of fields of view towards the side while overlapping each other such that the set of non-static cameras generates a second set of video streams imaging the second set of fields of view where at least two non-static cameras of the set of non-static cameras are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road simultaneously from at least two fields of view in the second set of fields of view that are optically different from each other, wherein at least one tower of the set of towers hosts at least one non-static camera of the set of non-static cameras that is redundant to at least one static camera of the set of static cameras hosted by the at least one tower; the computing instance to: access the first set of video streams; identify the aircraft in the first set of video streams when the aircraft is on the road along the side; track the aircraft in the first set of video streams when the aircraft is on the road along the side; detect a foreign object debris (FOD) on the common segment in at least two video streams of the second set of video streams imaged by the at least two non-static cameras performing the at least two patrol tours from the at least two fields of view when the FOD is on the common segment;stitch the first set of video streams such that a panorama video stream is formed depicting the profile view when the aircraft is on the road along the side; present the panorama video stream on a videowall such that the profile view is visible when the aircraft is on the road along the side; and present a user interface on an application program running on a computing terminal, wherein the user interface is programmed to allow an operator to perform a visual inspection of the FOD that has been detected on the common segment and take an action based on the visual inspection.

82. A method, comprising: providing a set of towers, a set of static cameras, a set of non-static cameras, and a computing instance to a user; enabling the user to: position the set of towers along a side of a road on which an aircraft moves, wherein the aircraft has a profile view; position the set of static cameras to (i) be hosted by the set of towers, (ii) be spaced apart from the side at a first set of distances that are substantially same, (iii) be optically parallel to each other, and (iv) have a first set of fields of view towards the side while overlapping each other such that the set of static cameras is able to generate a first set of video streams synchronously imaging the first set of fields of view; position the set of non-static cameras to (i) be hosted by the set of towers,(ii) be spaced apart from the side at a second set of distances that are substantially same,(iii) be scheduled to perform a set of patrol tours to image the road, and (iv) have a second set of fields of view towards the side while overlapping each other such that the set of non-static cameras generates a second set of video streams imaging the second set of fields of view where at least two non-static cameras of the set of non-static cameras are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road simultaneously from at least two fields of view in the second set of fields of view that are optically different from each other, wherein at least one tower of the set of towers hosts at least one non-static camera of the set of non-static cameras that isredundant to at least one static camera of the set of static cameras hosted by the at least one tower; operate the computing instance to: access the first set of video streams; identify the aircraft in the first set of video streams when the aircraft is on the road along the side; track the aircraft in the first set of video streams when the aircraft is on the road along the side; detect a foreign object debris (FOD) on the common segment in at least two video streams of the second set of video streams imaged by the at least two non-static cameras performing the at least two patrol tours from the at least two fields of view when the FOD is on the common segment; stitch the first set of video streams such that a panorama video stream is formed depicting the profile view when the aircraft is on the road along the side; present the panorama video stream on a videowall such that the profile view is visible when the aircraft is on the road along the side; and present a user interface on an application program running on a computing terminal, wherein the user interface is programmed to allow an operator to perform a visual inspection of the FOD that has been detected on the common segment and take an action based on the visual inspection.

83. A system, comprising: a tower positionable along a side of a road on which an aircraft having a profile view moves; a static camera hosted by the tower, wherein the static camera has a first field of view towards the side, wherein the static camera is configured to generate a first video stream depicting the profile view; and a non-static camera hosted by the tower, wherein the non-static camera has a second field of view towards the side, wherein the non-static camera is configured to perform a patrol tour to image the road such that the non-static camera generates asecond video stream in which a foreign object debris (FOD) on the road is detectable, wherein the non-static camera is redundant to the static camera.

84. A system, comprising: a set of towers positioned along a side of a road on which an aircraft moves, wherein the aircraft has a profile view; a set of static cameras that (i) are hosted by the set of towers, (ii) are spaced apart from the side at a first set of distances that are substantially same, (iii) are optically parallel to each other, and (iv) have a first set of fields of view towards the side while overlapping each other such that the set of static cameras generates a first set of video streams synchronously imaging the first set of fields of view; and a set of non-static cameras that (i) are hosted by the set of towers, (ii) are spaced apart from the side at a second set of distances that are substantially same, (iii) are scheduled to perform a set of patrol tours to image the road, and (iv) have a second set of fields of view towards the side while overlapping each other such that the set of non- static cameras generates a second set of video streams imaging the second set of fields of view where at least two non-static cameras of the set of non-static cameras are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road simultaneously from at least two fields of view in the second set of fields of view that are optically different from each other, wherein at least one tower of the set of towers hosts at least one non-static camera of the set of non-static cameras that is redundant to at least one static camera of the set of static cameras hosted by the at least one tower, wherein at least one non-static camera of the at least two non-static cameras is redundant to at least one another non-static camera of the at least two non-static cameras.

85. A system, comprising: a user interface simultaneously presenting a panorama video stream, a schematic top view, and a pane, wherein the panorama video stream is formed from a first set of video streams sourced from a set of static cameras that (i) are hosted by a set of towers positioned along a side of a road on which an aircraft having a profile view moves, (ii) arespaced apart from the side at a first set of distances that are substantially same, (iii) are optically parallel to each other, and (iv) have a first set of fields of view towards the side while overlapping each other such that the set of static cameras generates the first set of video streams synchronously imaging the first set of fields of view, wherein the panorama video stream presents the profile view, wherein the schematic top view presents a graphic corresponding to the aircraft on the road, wherein the schematic top view corresponds to the panorama video stream, wherein the pane presents a content related to the road, the aircraft, or a FOD detected on the road from a second set of video streams sourced from a set of non-static cameras that (i) are hosted by the set of towers, (ii) are spaced apart from the side at a second set of distances that are substantially same, (iii) are scheduled to perform a set of patrol tours to image the road, and (iv) have a second set of fields of view towards the side while overlapping each other such that the set of non-static cameras generates the second set of video streams imaging the second set of fields of view where at least two non-static cameras of the set of non-static cameras are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road simultaneously from at least two fields of view in the second set of fields of view that are optically different from each other, wherein the FOD is positioned on the common segment.

86. A system, comprising: a first configuration and a second configuration, wherein the first configuration opposes the second configuration, wherein each of the first configuration and the second configuration respectively includes: a set of towers positioned along a side of a road on which an aircraft moves, wherein the aircraft has a profile view; a set of static cameras that (i) are hosted by the set of towers, (ii) are spaced apart from the side at a first set of distances that are substantially same, (iii) are optically parallel to each other, and (iv) have a first set of fields of view towards the side while overlapping each other such that the set of static cameras generates a first set of video streams synchronously imaging the first set of fields of view; anda set of non-static cameras that (i) are hosted by the set of towers, (ii) are spaced apart from the side at a second set of distances that are substantially same, (iii) are scheduled to perform a set of patrol tours to image the road, and (iv) have a second set of fields of view towards the side while overlapping each other such that the set of non-static cameras generates a second set of video streams imaging the second set of fields of view where at least two non-static cameras of the set of non-static cameras are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road simultaneously from at least two fields of view in the second set of fields of view that are optically different from each other, wherein at least one tower of the set of towers hosts at least one non-static camera of the set of non-static cameras that is redundant to at least one static camera of the set of static cameras hosted by the at least one tower, wherein at least one non-static camera of the at least two non-static cameras is redundant to at least one another non-static camera of the at least two non-static cameras.

87. A system, comprising: a set of towers positioned along a side of a road on which an aircraft moves, wherein the aircraft has a profile view; a set of static cameras that (i) are hosted by the set of towers, (ii) are spaced apart from the side at a set of distances that are substantially same, (iii) are optically parallel to each other, and (iv) have a set of fields of view towards the side while overlapping each other such that the set of static cameras generates a set of video streams synchronously imaging the set of fields of view; a computing instance programmed to: access the set of video streams; identify the aircraft in the set of video streams when the aircraft is on the road along the side; track the aircraft in the set of video streams when the aircraft is on the road along the side; stitch the set of video streams such that a panorama video stream is formed depicting the profile view when the aircraft is on the road along the side; andpresent the panorama video stream on a display such that the profile view is visible and a visual identifier for the profile view is presented over the panorama video stream when the aircraft is on the road along the side.

88. A system, comprising: a set of towers positioned along a side of a road on which an aircraft moves, wherein the aircraft has a profile view; a set of non-static cameras that (i) are hosted by the set of towers, (ii) are spaced apart from the side at a set of distances that are substantially same, (iii) are scheduled to perform a set of patrol tours to image the road, and (iv) have a set of fields of view towards the side while overlapping each other such that the set of non-static cameras generates a set of video streams imaging the set of fields of view where at least two non-static cameras of the set of non-static cameras are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road simultaneously from at least two fields of view in the set of fields of view that are optically different from each other, wherein at least one non-static camera of the at least two non-static cameras is redundant to at least one another non-static camera of the at least two non-static cameras; a computing instance programmed to: access the set of video streams; detect a foreign object debris (FOD) on the common segment in at least two video streams of the set of video streams imaged by the at least two non-static cameras performing the at least two patrol tours from the at least two fields of view when the FOD is on the common segment; and present a user interface on an application program running on a computing terminal, wherein the user interface is programmed to allow an operator to perform a visual inspection of the FOD that has been detected on the common segment and take an action based on the visual inspection.

89. A system, comprising:a set of towers positioned along a side of a road on which an aircraft moves, wherein the aircraft has a profile view; a set of static cameras that (i) are hosted by the set of towers, (ii) are spaced apart from the side at a set of distances that are substantially same, (iii) are optically parallel to each other, and (iv) have a set of fields of view towards the side while overlapping each other such that the set of static cameras generates a set of video streams synchronously imaging the set of fields of view; a computing instance programmed to: access the set of video streams; identify the aircraft in the set of video streams when the aircraft is on the road along the side; track the aircraft in the set of video streams when the aircraft is on the road along the side; stitch the set of video streams such that a panorama video stream is formed depicting the profile view when the aircraft is on the road along the side; and present the panorama video stream on a display such that the profile view is visible when the aircraft is on the road along the side, wherein the panorama video stream has a single zoom.

90. A system, comprising: a user interface simultaneously presenting a panorama video stream and a pane, wherein the panorama video stream is formed from a first set of video streams sourced from a set of static cameras that (i) are hosted by a set of towers positioned along a side of a road on which an aircraft having a profile view moves, (ii) are spaced apart from the side at a first set of distances that are substantially same, (iii) are optically parallel to each other, and (iv) have a first set of fields of view towards the side while overlapping each other such that the set of static cameras generates the first set of video streams synchronously imaging the first set of fields of view, wherein the panorama video stream presents the profile view, wherein the panorama video stream has a single zoom, wherein the pane presents a content related to the road, the aircraft, or a FOD detected on the road from a second set of video streams sourced from a set of non-static cameras that (i)are hosted by the set of towers, (ii) are spaced apart from the side at a second set of distances that are substantially same, (iii) are scheduled to perform a set of patrol tours to image the road, and (iv) have a second set of fields of view towards the side while overlapping each other such that the set of non-static cameras generates the second set of video streams imaging the second set of fields of view where at least two non-static cameras of the set of non-static cameras are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road simultaneously from at least two fields of view in the second set of fields of view that are optically different from each other, wherein the FOD is positioned on the common segment.

91. A system, comprising: a set of towers positioned along a side of a road on which an aircraft moves, wherein the aircraft has a profile view; a set of non-static cameras that (i) are hosted by the set of towers, (ii) are spaced apart from the side at a set of distances that are substantially same, (iii) are scheduled to perform a set of patrol tours to image the road, and (iv) have a set of fields of view towards the side while overlapping each other such that the set of non-static cameras generates a set of video streams imaging the set of fields of view where at least two non-static cameras of the set of non-static cameras are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road simultaneously from at least two fields of view in the set of fields of view that are optically different from each other, attempt to detect a foreign object debris (FOD) on the common segment, and generate at least two confidence level estimates for the FOD on the common segment when detected; a computing instance programmed to: access the set of video streams and the at least two confidence level estimates; form a determination whether the FOD is present on the common segment based on the at least two confidence level estimates; and present a user interface on an application program running on a computing terminal, wherein the user interface is programmed to allow an operator to perform avisual inspection of the FOD that has been detected on the common segment and take an action based on the visual inspection.

92. A system, comprising: a set of towers positioned along a road on which an aircraft moves, wherein the aircraft has a profile view; a set of non-static cameras that (i) are hosted by the set of towers, (ii) are spaced apart from the road at a set of distances that are substantially same, (iii) are scheduled to perform a set of patrol tours to image the road, and (iv) have a set of fields of view towards the road while overlapping each other such that the set of non-static cameras generates a set of video streams imaging the set of fields of view where at least two non- static cameras of the set of non-static cameras are scheduled to perform at least two patrol tours of the set of patrol tours to image a common segment of the road simultaneously from at least two fields of view in the set of fields of view that are optically different from each other, attempt to detect a foreign object debris (FOD) on the common segment, and generate at least two confidence level estimates for the FOD on the common segment when detected; a computing instance programmed to: access the set of video streams and the at least two confidence level estimates; form a determination whether the FOD is present on the common segment based on the at least two confidence level estimates; and present a user interface on an application program running on a computing terminal, wherein the user interface is programmed to allow an operator to perform a visual inspection of the FOD that has been detected on the common segment and take an action based on the visual inspection.

93. A system, comprising: a tower positioned along a road on which an aircraft moves, wherein the aircraft has a profile view; a camera positioned along the road; anda user interface.

Images