Post-maneuver orbit determination

Abstract

A display system can be configured to receive, via a user interface, an identifier associated with an orbital object and determine a maneuver of the orbital object. The maneuver can include a perturbation of the path of the orbital object. Based on the identifier, the display system can determine pre-maneuver and post-maneuver orbital parameters associated with the orbital object and generate a display interface. The display interface can include a longitude-time graph having a longitude axis and a time-axis and an indication of the determined orbital parameters. The post-maneuver orbital parameters can be determined based at least in part on the pre-maneuver orbital parameters.

Description

EXOAN.030WO PATENTPOST-MANEUVER ORBIT DETERMINATIONINCORPORATION BY REFERENCE OF RELATED APPLICATIONS

[0001] This application claims the benefit under 35 U.S.C. § 119(e) of U.S. Provisional Patent Application No. 63 / 729,244, filed December 06, 2024, the entire contents of which are incorporated by reference herein and are made a part of this specification.BACKGROUNDField

[0002] This disclosure relates generally to tracking orbital objects such as satellites and visual interfaces and to computer configurations used in such tracking.Description of Related Art

[0003] Visualization interfaces can be used to allow a user to view, manipulate, and adjust data representing tracked orbital objects (e.g., satellites). Tracking orbital objects involves taking in an amount of data and incorporating that data into a workable and usable interface and using the data to determine and analyze an orbital state of the orbital objects.

[0004] Tracking orbital objects may be done using photographs of objects in space and tracking their positions using a plurality of photographs. Visualization systems have been developed in various fields that provide some functionality with regard to portraying various information. However, many features are lacking, and many problems exist in the art for which this application provides solutions.SUMMARY

[0005] Example embodiments described herein have innovative features, no single one of which is indispensable or solely responsible for their desirable attributes. Without limiting the scope of the claims, some of the advantageous features will now be summarized.

[0006] In some embodiments, a system for determining and displaying orbital parameters may receive, via an orbital object data interface, orbital object data from an orbital object data source, receive via a user interface, selection of identifiers associated with an orbital object and an estimated maneuver time for the orbital object, determine a pre-maneuver orbitalparameter based at least in part on the orbital object data associated with times (having time identifiers) before estimated maneuver time and determine a post-maneuver orbital parameter based at least in part on the orbital object data associated with times after the estimated maneuver time. In some embodiments, the system may determine the post-maneuver orbital parameter based on the pre-maneuver orbital parameter. In some embodiments, the system may determine one or both a pre-maneuver uncertainty parameter and a post-maneuver uncertainty parameter. In some such embodiments, the system may determine the postmaneuver orbital parameter based on the pre-maneuver orbital parameter and one or both the pre-maneuver uncertainty parameter and the post-maneuver uncertainty parameter. In some cases, the system may further determine a maneuver characterization parameter indicative a maneuver time or time interval, a change in the position of the orbital object, and / or a change in the speed of the orbital object. In some cases, the system may determine the maneuver characterization parameter based at least in part or determined pre-maneuver and postmaneuver orbital parameters.

[0007] In some implementations, the maneuver uncertainty parameter may comprise a residual value, a variance, or another parameter or set parameters (e.g., a covariance matrix, or another statistical parameter) that may quantify precision of a determined pre / post- maneuver orbital parameter and / or the deviation of the determined pre / post-maneuver parameter from the corresponding pre-post-maneuver data points received from the orbital object data interface 185. In some cases, the residual value may comprise difference between a determined orbital path and the data points (e.g., longitude-time points) used to calculate the orbital path.

[0008] The maneuver can include a perturbation of a path (e.g., an orbital path) of the orbital object and / or a perturbation of a speed of the orbital object.

[0009] The user interface may comprise a display interface having graphical user interface configured to receive the selection of the identifiers associated with the orbital object, the estimated maneuver time, via a user interaction with the graphical user interface. The display interface can include a longitude-time graph having a longitude axis spanning from a lower-longitude limit to an upper-longitude limit and a time-axis spanning from the lower-time limit to the upper-time limit. The identifiers may be used to display orbital object data aslongitude-time data points on the longitude-time graph. In some examples, graphical user interface may comprise at least a portion of the longitude-time graph.

[0010] In some embodiments, the identifiers may comprise: a name identifier, a time identifier, a latitude identifier, a longitude identifier, an azimuth & elevation identifier, a right ascension identifier, and a declination identifier.

[0011] The system can generate an indication of one or more of a pre-maneuver orbital parameter and a post-maneuver orbital parameter, in the longitude-time graph. The display interface can include a time slider in the longitude-time graph, where the user can adjust the time slider to provide an estimated maneuver time to the system.

[0012] In some embodiments, a system for determining and displaying orbital parameters may receive, via the user interface, identifiers associated with an orbital object, determine or receive an estimated maneuver time for the orbital object, and automatically determine a post-maneuver parameter, and a maneuver characterization parameter by determining a pre-maneuver orbital parameter and a post-maneuver orbital parameter.

[0013] The system may use a received or determined maneuver time to divide received orbital object data to pre- and post-maneuver orbital object data, determine premaneuver orbital parameter using the pre-maneuver orbital object data and determine the postmaneuver orbital object data using the pre-maneuver orbital parameter and post-maneuver orbital object data.

[0014] In some aspects, the techniques described herein relate to a system for determining and transmitting a post-maneuver orbital parameter of an orbital object: an orbital object data interface configured to receive orbital object data from an orbital object data source covering at least a selected time period, the orbital object data including identifiers corresponding to the orbital object; a non-transitory computer-readable storage storing instructions that are machine-executable; and a hardware processor in communication with the non-transitory computer-readable storage, wherein the instructions, when executed by the hardware processor, cause the system to: receive the identifiers; receive a lower-time limit and an upper-time limit indicating the selected time period; generate a display interface including: a longitude-time graph including: a longitude axis spanning from a lower-longitude limit to an upper-longitude limit: and a time-axis spanning from the lower-time limit to the upper-time limit; generate data for displaying a plurality of longitude-time points based on the identifiers;determine an estimated maneuver time indicating a boundary dividing the plurality of longitude-time points into a first plurality of longitude-time points and a second plurality of longitude- time points, wherein the first plurality of longitude-time points represents a premaneuver time period, and the second plurality of longitude-time points represents a postmaneuver time period; determine a pre-maneuver orbital parameter using a first portion of the identifiers associated with the first plurality of longitude-time points; determine a maneuver characterization parameter based on at least one of the first portion of the identifiers; determine the post-maneuver orbital parameter using at least the pre-maneuver orbital parameter and the maneuver characterization parameter; and transmit the determined maneuver characterization parameter and the determined post-maneuver orbital parameter.BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The following drawings and the associated descriptions are provided to illustrate embodiments of the present disclosure and do not limit the scope of the claims.

[0016] Figure 1 schematically illustrates an example orbital visualization and computing system.

[0017] Figure 2 schematically illustrates a network configuration that allows for the passing of data to a visualization system.

[0018] Figure 3 schematically illustrates a schematic of an example visualization display.

[0019] Figure 4A schematically illustrates an example visualization display with a longitude-time graph, scalar-time graph, a longitude-latitude graph, and a display area.

[0020] Figure 4B schematically illustrates a detailed view of an example longitudetime graph that may be a part of the visualization display described in Figure 4A.

[0021] Figure 4C schematically illustrates a detailed view of an example longitudelatitude graph that may be a part of the visualization display described in Figure 4A.

[0022] Figure 4D schematically illustrates a detailed view of an example scalartime graph that may be a part of the visualization display described in Figure 4A.

[0023] Figure 4E schematically illustrates an example visualization display having a synchronized analysis plot.

[0024] Figure 4F schematically illustrates an example visualization display having a geographical map indicating the locations of orbital object date sources.

[0025] Figure 5 schematically illustrates an example maneuver represented in a visualization display indicating an orbital object has moved from a first orbital path to a second orbital path.

[0026] Figure 6A schematically illustrates an example orbital path determined for selected orbital object data within a selected time window without considering a maneuver performed by the corresponding orbital object within the time window. The inset shows temporal variation of residual values for the determined orbital path and selected orbital object data.

[0027] Figure 6B schematically illustrates an example pre-maneuver orbital path and a corresponding post-maneuver orbital path determined for the selected orbital object data and time window shown in FIG. 6A using a single-maneuver cold start process and an estimated maneuver time provided by a user or determined by the system.

[0028] Figure 7 schematically illustrates an example pre-maneuver orbital path and a corresponding post-maneuver orbital path determined for the selected orbital object data and time window shown in FIG. 6A using a single-maneuver warm start process and an estimated maneuver time provided by a user or determined by the system.

[0029] Figure 8A illustrates example multiple pre-maneuver and post-maneuver orbital paths determined for a selected orbital object using a multi-maneuver warm start process.

[0030] Figure 8B is a flow diagram illustrating an example multi-maneuver warm start process.

[0031] These and other features will now be described with reference to the drawings summarized above. The drawings and the associated descriptions are provided to illustrate embodiments and not to limit the scope of any claim. Throughout the drawings, reference numbers may be reused to indicate correspondence between referenced elements. In addition, where applicable, the first one or two digits of a reference numeral for an element can frequently indicate the figure number in which the element first appears.DETAILED DESCRIPTION

[0032] Although certain embodiments and examples are disclosed below, inventive subject matter extends beyond the specifically disclosed embodiments to other alternative embodiments and / or uses and to modifications and equivalents thereof. Thus, the scope of the claims appended hereto is not limited by any of the particular embodiments described below. For example, in any method or process disclosed herein, the acts or operations of the method or process may be performed in any suitable sequence and are not necessarily limited to any particular disclosed sequence. Various operations may be described as multiple discrete operations in turn, in a manner that may be helpful in understanding certain embodiments; however, the order of description should not be construed to imply that these operations are order dependent. Additionally, the structures, systems, and / or devices described herein may be embodied as integrated components or as separate components. For purposes of comparing various embodiments, certain aspects and advantages of these embodiments are described. Not necessarily all such aspects or advantages are achieved by any particular embodiment. Thus, for example, various embodiments may be carried out in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other aspects or advantages as may also be taught or suggested herein.

[0033] Described herein are methodologies and related systems for visualizing data (e.g., tracks, orbits, photographs, measurements, maneuvers, transfer actions, etc.) from satellites and other orbital objects, and allowing a user to use the data to determine or estimate an orbital parameter or an orbital event for the orbital object among other data driven functionalities associated with characterizing orbital past and / or future orbital state of an orbital object. It will be understood that although the description herein is in the context of satellites, one or more features of the present disclosure can also be implemented in tracking objects other than satellites like, for example, aircraft, watercraft, projectiles, and other objects. Some embodiments of the methodologies and related systems disclosed herein can be used with various tracking systems, including, for example, those based on government databases.

[0034] In various implementations, an orbital parameter (e.g., a pre-maneuver or post-maneuver parameter) of an orbital object may comprise a kinematic parameter (e.g., a component of the position vector, velocity vector, or acceleration vector, and the like), a dynamic parameter (e.g., a force or a torque acting on the orbital object or another parameterthat affects the motion of the orbital object). Tn some cases, the dynamic parameter may comprise a parameter that may change in time, and can be associated with position and / or orientation of the orbital object and a characteristic of the orbital object (e.g.. a physical characteristic). For example, a dynamic orbital parameter may comprise a ratio between an effective area and the mass of the orbital object. In some such examples, one or both the effective area and mass may change in time, and the effective area may depend on one or both position and orientation of the orbital object.

[0035] In some examples, a dynamic orbital parameter may be configured to calculate or estimate solar radiation pressure experienced by the orbital object. In some such examples, such dynamic orbital parameter may comprise the coefficient of optical reflectivity of a surface of the object multiplied by a first effective area divided by the mass of the orbital object, where radiation pressure is proportional to the first effective area (e.g., the first effective area can be an area illuminated by solar radiation for a given position and orientation of the object). In some cases, this orbital parameter may be referred to as CrAM (Coefficient of reflectivity times Area divided by Mass).

[0036] In some examples, a dynamic orbital parameter may be configured to calculate atmospheric drag experienced by the orbital object. In some such examples, such dynamic orbital parameter may comprise the coefficient of drag for the orbital object multiplied by a second effective area divided by the mass of the orbital object, where the drag force is proportional to the second effective area (e.g., the second effective area can be the projection of a surface of the orbital object on a plane orthogonal to the velocity vector for a given position and orientation of the object). In some cases, this orbital parameter may be referred to as CdAM (Coefficient of drag times Area divided by Mass).

[0037] Unless explicitly indicated otherwise, terms as used herein will be understood to imply their customary and ordinary meaning.

[0038] Disclosed herein are methods and systems relating generally to the tracking of objects in orbit (e.g., satellites), other orbital objects, and related systems and methods of providing an interactive user interface to interact with data related to the tracking of these objects. The information therein can be stored in one or more databases.

[0039] Tracking objects in orbit and other orbital objects can include receiving image data (e.g., photographs) of portions of the sky from one or more telescopes positionedat various positions across the globe. The photograph data can be used to map out the entirety or near entirety of the sky. Various altitudes above sea level may be tracked. The data can be tracked and processed in real-time. For example, a contemporary database may be configured to receive real-time image data. A historical database may be configured to store data received before a threshold time. The threshold time may be a specified amount of time (e.g., years, months, days, etc.). Alternatively, the threshold time may refer to a time based on a user action. For example, the historical database may be configured to store data received before a user causes the system to display the user interface. Using an algorithm, the received data may be consolidated and categorized. For example, the algorithm may be configured to determine whether objects that appear in a plurality of photographs correspond to the same object over time and space.

[0040] In some embodiments, an orbital visualization and computing system may be configured to allow a user to determine an orbital event using on orbital data received from a data server and / or directly from an orbital data collecting system (e.g., a ground based or space-based telescope). In some examples, the orbital event may comprise a maneuver performed by an orbital object. The orbital visualization and computing system may comprise a non-transitory computer-readable storage storing instructions that are machine-executable and a hardware processor in communication with the non-transitory computer-readable storage, where the instructions, when executed by the hardware processor, cause the orbital visualization and computing system to determine a post-maneuver parameter and / or a maneuver characterization parameter using a warm start maneuver characterization process that determines the post-maneuver orbital parameter and / or the maneuver characterization parameter based at least in part on a determined pre-maneuver orbital parameter using orbital observations collected in a post-maneuver period. Advantageously, determining the postmaneuver orbital parameter and / or the maneuver characterization parameter based at least in part on the determined pre-maneuver orbital parameter allows reducing the post-maneuver period to less than 5 minutes after a real maneuver time, less than 10 minutes after a real maneuver time, less than 30 minutes after a real maneuver time, or less than 60 minutes after a real maneuver time, where the real maneuver time can be a time at which the maneuver has been initiated or completed.

[0041] In some cases, the maneuver characterization parameter may comprise a maneuver time determined by the system or provided by a user. In some cases, a user may use the system to determine the maneuver time by providing an estimated maneuver time to the system and causing the system to determine the maneuver time by determining a parameter and a post-maneuver parameter.

[0042] In some embodiments, during a maneuver characterization process, the system may calculate values of one or more auxiliary parameters indicative of an uncertainty parameter, or residual characteristics of a determined pre- or post-maneuver parameter. The auxiliary parameters may be used by the system and / or the user to determine an estimated maneuver time, select a time window for maneuver determination, or select a number premaneuver and / or post-maneuver data points for maneuver determination. For example, temporal variation of an auxiliary parameter (e.g., a residual value) comprise a behavior indicative of a maneuver performed by the orbital object.

[0043] The system enables the determination and transmission of post-maneuver orbital parameters by leveraging a hardware processor and machine-executable instructions stored in a non-transitory computer-readable storage. This arrangement ensures efficient processing and accurate computation of orbital parameters.

[0044] By receiving orbital object data, including identifiers, from an orbital object data source, the system facilitates the integration of real-time or historical data into the analysis, allowing for precise tracking and maneuver characterization of orbital objects.

[0045] The generation of a display interface with a longitude-time graph, including a longitude axis and a time axis, provides a visual representation of orbital data. This graphical interface allows users to intuitively interact with and analyze the orbital object's trajectory over a selected time period.

[0046] The division of longitude- time points into pre-maneuver and post-maneuver periods based on an estimated maneuver time enables the system to isolate and analyze the effects of a maneuver. This segmentation supports the accurate determination of pre-maneuver and post-maneuver orbital parameters.

[0047] The determination of the post-maneuver orbital parameter using both the pre-maneuver orbital parameter and post-maneuver data ensures continuity and accuracy in theorbital analysis. This approach reduces the reliance on extensive post-maneuver data, enabling quicker and more efficient calculations.

[0048] The transmission of the determined post-maneuver orbital parameter ensures that the results can be utilized by other systems or stored for further analysis, supporting applications such as satellite tracking, collision avoidance, and orbital adjustments.

[0049] The system's ability to process and display orbital data within a defined time window enhances user control and flexibility, allowing for focused analysis of specific orbital events or maneuvers.Orbital domain data access and analysis

[0050] Described herein are methodologies and related systems for processing space domain data (e.g.. orbital object data) associated with one or more orbital objects (e.g., satellites) and generating displays comprising orbital parameters (e.g., orbital paths), reports, alerts, and determining parameters associated with orbital events (e.g., changes of an orbital state and / or maneuvers performed by orbital objects) to provide a user with information about the orbital objects and their interactions. In various embodiments, the orbital data may be received, among other sources, from telescopes, satellites, or databases, e.g., via a network connection. In some embodiments, orbital object data may comprise photographs received from one or more satellites. In some embodiments, a system may allow the user to request information about orbital objects, modify the information, determine or estimate an orbital parameter based on the information. However, the embodiments are not so limited and the system may have other capabilities and provide other functionalities with respect to receiving and selecting data, processing data, and presenting the resulting information. It will be understood that although the description herein is in the context of satellites, one or more features of the present disclosure can also be implemented in tracking objects other than satellites like, for example, aircraft, watercraft, projectiles, and other objects. Some embodiments of the methodologies and related systems disclosed herein can be used with various tracking systems, including, for example, those based on government databases.

[0051] Figure 1 schematically illustrates an example orbital visualization and computing system 100 for receiving orbital object data 147 from one or more orbital object data sources 155, processing orbital object data 147, e.g.. in response to user requests received via a user interface (e.g. a graphical user interface), determining orbital parameters for anorbital object selected by the user based on orbital object data 147, detecting and characterizing an orbital event (e.g., a maneuver performed by an orbital object), and the like. In some examples, the orbital visualization and computing system 100 may be configured to generate space domain awareness (SDA) data by processing orbital object data 147. In some embodiments, an orbital object data source may comprise a contemporary data server 150, a historical data server 140, or a metadata (or miscellaneous data) server 154. In some embodiments, the contemporary data server 150 may receive orbital object data from one or more telescopes 113-1, 113-2, ..., 113-N. In some cases, at least two telescopes (e.g., 113-1 and 113-2) may be positioned at different locations across planet earth. In some cases, at least one telescope can be an orbital telescope orbiting the earth.

[0052] In some embodiments, orbital visualization and computing system 100 may comprise an orbital object data interface 185 configured to receive orbital object data 147 (e.g., photographs) from an orbital object data source of the orbital object data sources 155, via a data network 144. In some cases, orbital object data interface 185 may directly receive orbital object data 147 from a telescope (e.g., via a wireless link). In various implementations, orbital object data 147 may include real-time or substantially rea-time telescope data, historical telescope data, or other data (e.g., data received from a government database).

[0053] In some embodiments orbital object data 147 may include image data (e.g., photographs) of portions of the sky from one or more telescopes positioned at various positions across the globe. The photograph data can be used to map out the entirety or near entirety of the sky. Various altitudes above sea level may be tracked. The data can be tracked and processed substantially in real-time. For example, a contemporary data server 150 may be configured to receive real-time image data. A historical database may be configured to store data received before a threshold time. The threshold time may be a specified amount of time (e.g., years, months, days, etc.). Alternatively, the threshold time may refer to a time based on a user action. For example, the historical database may be configured to store data received before a user causes the system to display the user interface. Using an algorithm, the received data may be consolidated and categorized. For example, the algorithm may be configured to determine whether objects that appear in a plurality of photographs correspond to the same object over time and space.

[0054] In some embodiments, the orbital visualization and computing system 100, herein referred to as system 100, may comprise an electronic processor 145 and machine- readable instructions (e.g., a software suite) stored in a non-transitory memory 146 executed by the electronic processor 145. In some embodiments, at least a portion of the machine- readable instructions may be stored in and executed by a cloud computing platform or system. In some such embodiments, the system 100 may use one or more tools available via the cloud computing platform to enhance or augment the performance of the core machine-readable instructions with respect to data processing, data management, user interaction, or other aspects.

[0055] In some embodiments, execution of the machine-readable instructions by the processor 145 may cause system 100 to generate a visualization display 102 comprising a graphical user interface (GUI) using a GUI control 187, where the GUI is configured to receive user inputs and present requested information via the visualization display 102 comprising one or more graphs, charts, tables, or other interactive interfaces and displays, hr some embodiments, the user interface may comprise one or both of a graphical user interface (GUI) and a text-based user interface. In some embodiments, system 100 may interact with a user via an alternative user interface 163. In some embodiments, the visualization display 102 may comprise any type of digital display device, such as a desktop computer, a laptop computer, a projection-style device, a smartphone, a tablet, a wearable device, or any other display device.

[0056] In some embodiments, the visualization display 102 may comprise one or more plots or regions configured to display raw and / or processed orbital object data in different domains (e.g., different spatial coordinates, time domain, space-time domain, and the like). In some examples, a first plot 104 of the visualization display 102 may comprise a longitude-time graph, a second plot 108 of the visualization display 102 may comprise a scalar-time graph, a third plot 112 of the visualization display 102 may comprise a longitude-latitude graph, and a fourth plot 116 of the visualization display 102 may comprise an image chip, a solar phase indicator, or another graph.

[0057] In some cases, system 100 may process orbital object data automatically or in response to user interactions with a user interface. In some examples, a user may interact with the GUI to select a portion of orbital object data 147 received by the orbital object data interface 185 and cause the system 100 to present, process, and / or modify the received portionof orbital object data and generate requested information or SDA data. For example, the user may the GUI to generate a graph (e.g., a plurality of longitude-time data points) indicating temporal change of longitude of orbital objects based on orbital object data received from one or more telescopes during a specified time window (e.g., a time window provided by the user) and cause the system 100 to identify an orbital object in the graph by selecting the a portion of the graph (e.g.. a group of longitude-time data points).

[0058] Figure 2 is an example network configuration 194 for a visualization system 190. The architecture of the visualization system 190 can include an arrangement of computer hardware and software components used to implement aspects of the present disclosure. The visualization system 190 may include more or fewer elements than those shown in Figure 1. It is not necessary, however, that all of these elements be shown in order to provide an enabling disclosure. In some embodiments, the visualization system 190 is an example of what may be referred to under different names.

[0059] As illustrated, the visualization system 190 can include a hardware processor 188, a memory 146, a real-time orbital object data interface 172, a tagging interface 174, an image interface 176, a real-time connection interface 178, and / or an real-time connection interface 178, each of which can communicate with one another by way of a communication bus 142 or any other data communication technique. The hardware processor 188 can read and write to memory 146 and can provide output information for the visualization display 102. The real-time orbital object data interface 172, tagging interface 174, image interface 176, and / or real-time connection interface 178 can be configured to accept input from an input device 164, such as a keyboard, mouse, digital pen, microphone, touch screen, gesture recognition system, voice recognition system, and / or another input device capable of receiving user input. In some embodiments, the visualization display 102 and the input device 164 can have the same form factor and share some resources, such as in a touch screen-enabled display.

[0060] In some embodiments, the real-time orbital object data interface 172, the tagging interface 174, the image interface 176, and / or the real-time connection interface 178 can be connected to a historical data server 140, a contemporary data server 150, and / or a metadata server 154 via one or more data networks 144 (such as the Internet, 3G / Wi- Fi / LTE / 5G networks, satellite networks, etc.). The real-time orbital object data interface 172 can receive graphical data information related to orbital objects via the network 144 (thenetwork 144 can provide one-way communication or two-way communication). In some embodiments, the real-time orbital object data interface 172 may receive, where applicable, object data information or information that can be used for location determination (such as a cellular and / or Wi-Fi signal that can be used to triangulate a location) and determine the position of one or more objects.

[0061] The tagging interface 174 can receive tagging data from a user via the input / output device interface 182. The metadata server 154 can provide an application programming interface (API) that the tagging interface 174 can access via the network 144 (such as, for example, a 3G, Wi-Fi, LTE, or similar cellular network). The metadata server 154 may comprise data from one or more third-party providers. For example, the metadata server 154 may comprise government information (e.g., received from a United States Air Force satellite database). The image interface 176 may receive track information (such as, for example, an ordered list of known location coordinates) from a historical data server 140, contemporary data server 150. and / or metadata server 154 via the network 144. The track information can also include track-related information, such as photos, videos, or other data related to orbiting objects. In some embodiments, instead of receiving the track information over a network 144 from a historical data server 140, the system can receive such track information from a user via a computer-readable storage device, such as, for example, a USB thumb drive. The image interface 176 can also receive images (e.g., photographs, video) from a contemporary data server 150. In some embodiments, the map data can provide longitude, latitude, altitude information, and any other information related to orbiting objects.

[0062] The memory 146 can contain computer program instructions (grouped as modules or components in some embodiments) that the hardware processor 188 can execute in order to implement one or more embodiments described herein. The memory 146 can generally include RAM, ROM and / or other persistent, auxiliary or non-transitory computer- readable media. The memory 146 can store an operating system 122 that provides computer program instructions for use by the hardware processor 188 in the general administration and operation of the visualization system 190.

[0063] The memory 146 can include computer program instructions and other information for implementing aspects of the present disclosure including a graphic module 124,a tagging module 126, a data integration module 128, a synchronization module 130, a user settings module 132, other modules, and / or any combination of modules.

[0064] In some embodiment, the memory 146 may include the graphic module 124 that generates a track from the received ordered list of known locations using algorithms, such as interpolation or extrapolation algorithms. Additionally, the graphic module 124 may, in response to a user determination, alter the format (e.g., axes, labels, values) of the graphical display.

[0065] In some embodiments, the memory 146 includes a tagging module 126 that the hardware processor 188 executes in order update, in response to a user action, aspects (e.g., metadata, values) of the underlying data. Accordingly, the tagging module 126 can provide data (e.g., updates) to the synchronization module 130. The data integration module 128 can correlate various data automatically or in response to a user input. For example, the data integration module 128 can combine data from the one or more servers (e.g., the historical data server 140. the contemporary data server 150, and the metadata server 154) that may be used for displaying on the visualization display 102.

[0066] In some embodiments, the memory 146 includes a synchronization module 130 that can be configured to correlate various aspects of data from the one or more servers. For example, the synchronization module 130 can be configured to synchronize the display of a data set on multiple graphs or to synchronize elements (e.g., axes, labels, dimensions, alignments, etc.) of one or more graphs of the visualization display 102. The synchronization module 130 can update data based on inputs from the tagging module 126 (such as stitched objects or elements), guidance parameters from the user settings module 132, and / or inputs from the data integration module 128.

[0067] In some embodiments, the memory 146 includes a user settings module 132. The user settings module 132 can provide access to various user settings related to user preferences, including graph parameters, graph configurations (e.g., layout, orientation, formatting, etc.) and modes (e.g., display mode, tag mode, etc.). For example, the threshold values used for determination of the direction guidance mode may be accessed through the user settings module 132. In some instances, the user settings module 132 may provide connectivity to a data store 168 and access user settings from or store user settings to the data store 168. Examples of functionality implemented by the user settings module 132 are morefully described, for example, with reference to Figures 2-1 OD. In some embodiments, other interfaces and modules, such as the real-time orbital object data interface 172, the tagging interface 174, the image interface 176, real-time connection interface 178, and / or input / output device interface 182 may have access to the data store 168.

[0068] The historical data server 140 may communicate via the network 144 with a historical data interface. The historical data interface may include one or more of the realtime orbital object data interface 172, the tagging interface 174, the image interface 176, and the real-time connection interface 178. The historical data interface may be configured to receive historical data of objects in orbit around a planet from a historical data set. The historical data may comprise a time, a latitude, a longitude, a scalar, and / or an object identifier (e.g., name) for each object. The historical data can comprise data collected over a period of time greater than a threshold time (e.g., a year).

[0069] The amount of historical data can be unusually immense. For example, the amount of historical data may include billions of data identifiers derived from petabytes or even exabytes of photographic data. The historical data obtained may be increasing over time. Such an immense amount of data can cause serious challenges related to, for example, maintaining, sorting, extracting, transmitting, and / or displaying that data, particularly in a timely and organized fashion. This data may be supplemented from other databases (e.g., the metadata server 154), such as third-party databases. Such third-party databases may include government organizations, such as military groups (e.g., the United States Air Force), but may include private (e.g., commercial) sources additionally or alternatively.

[0070] The contemporary data server 150 may communicate via the network 144 with a real-time (e.g., contemporary) data interface configured to receive contemporary data of objects in orbit around a planet from a contemporary data set. The contemporary data may comprise a time, a latitude, a longitude, an object identifier, and / or a scalar for each object. The contemporary data may comprise data collected after the historical data available from the historical data set. The contemporary data may include data received within a few minutes or even seconds of a current time. The contemporary data may be data stored after a user has initiated a particular action, such as causing the system to generate a visualization display 102. In such a case, the system can be configured to update the visualization display 102 with pixels associated with the data collected after the generation of the visualization display 102.

[0071] Figure 3 shows a schematic of an example visualization display 102. Such a visualization display 102 may operate within the network configuration 194 of Figure 2, for example. The visualization display 102 may be displayed on any type of digital display device, such as a desktop computer, a laptop computer, a projection-style device, a smartphone, a tablet, a wearable device, or any other display device. The visualization display 102 may include a first plot (or display area) 104, a second plot 108, a third plot 112, and / or a fourth plot 116.

[0072] The first plot 104 and second plot 108 may be displayed with similar (e.g., within a few pixels) vertical dimensions and / or similar vertical alignment. For example, the first plot 104 may be disposed directly left of the second plot 108. The third plot 112 may have similar vertical dimensions and / or similar vertical alignment as the fourth plot 116. The first plot 104 may have similar horizontal dimensions and / or similar horizontal alignment as the third plot 112. In some embodiments, the second plot 108 may have similar horizontal dimensions and / or similar horizontal alignment as the fourth plot 116. In some designs, the second plot 108 may include a tagging interface (e.g., a stitching and / or splicing interface).

[0073] Figure 4A shows an example visualization display 200 with a longitudetime graph 204, scalar-time graph 208, a longitude-latitude graph 212, and a display area 216. The visualization display 200 may correspond in some or all respects with the visualization display 102 of Figure 3.

[0074] The visualization display 200 can include a longitude-time graph area 228. In some embodiments, the longitude-time graph area 228 is bounded by a first longitude axis 224 and a first time-axis 220. Each of the first longitude axis 224 and / or first time-axis 220 can include one or more axis labels. In some designs, the axis labels of the first longitude axis 224 are not shown in relation to the longitude-time graph 204 but in relation only to, for example, the longitude-latitude graph 212. The axis labels of the first longitude axis 224 and / or first time-axis 220 may be equidistant from one another to portray equal intervals of the respective longitude or time. The first longitude axis 224 may span any portion of longitudes found on a planet (e.g., Earth). For Earth, the range may be from 180 W (e.g., 180° West or -180°) to 180 E (e.g., 180° East or +180°) or any range therein. For example, as shown in Figure 4A, the first longitude axis 224 spans from 180 W to 120 E. However, other ranges are possible, examplesof which are described below. The first longitude axis 224 may run eastern-most to westernmost from left to right (e.g., as shown), but other configurations are possible.

[0075] The first time-axis 220 may span any time from a historical time to nearly a current time of a user. For example, as shown by Figure 4A, the first time-axis 220 may span from 2014-07 (e.g., July 2014) to 2017-07 (e.g., July 2017). The displayed time may correspond to a universal time, such as the coordinated universal time (UTC). Stored time values may similarly be in UTC. The latest time may be labeled “current time,” “now,” or a similar label and / or may indicate to a user that data from the most current time available are displayed. The most current time available may include time within a few seconds (e.g., 1-60 seconds) or a few minutes (e.g., 1-30 minutes) of a present time at which a viewer is observing the data. The first time-axis 220 may span from a historical time from an earliest time when a database (e.g., a historical data server 140, a metadata server 154) has available data. The earliest time when the database has data may be as far back as the year 2010. In some embodiments, the historical data server 140. the contemporary data server 150. and / or the metadata server 154, may be configured to store some or all of the corresponding data in shortterm memory storage (e.g., Random Access Memory (RAM)). The first time-axis 220 may include axis labels that run earliest to most recent from top to bottom (e.g., as shown), but other variations are possible. Axis labels may be spaced equidistant from each other to indicate equal time intervals therebetween. An axis label may show a corresponding time to include a year, a month, a day, an hour, a minute, and / or a second, depending on the level of specificity that is available, the span of the first time-axis 220, and / or the level of detail that is needed for a particular display.

[0076] Each axis label of the first longitude axis 224 and / or first time-axis 220 may include gridlines. For example, the longitude-time graph 204 may include one or more horizontal gridlines 296 and / or vertical gridlines 294 (not shown). The vertical gridlines 294 and horizontal gridlines 296 may aid a viewer in identifying a particular point within one or more of the graphs. To further aid a user in visualizing the orbital object information, in some embodiments, the longitude-time graph 204 may display a longitude-time map (not shown). The longitude-time map may be a geographical map of a portion of the planet. For example, the longitude-time map may identify the contours and / or limits of various landmasses (e.g., continents, islands). This information may help a user quickly ascertain over which landmassor body of water, for example, an orbital object may be located. For example, it may be useful to a viewer to see that a satellite orbits above a portion of Africa (or other planetary location). Points displayed on the corresponding graph (e.g., the longitude-time graph 204) may be superimposed over the geographic map (e.g., the longitude-time map).

[0077] The longitude-latitude graph 212 may include a longitude-latitude graph area 240 that is bounded by a second longitude axis 236 and a latitude axis 232. Each of the second longitude axis 236 and / or the latitude axis 232 can include one or more axis labels. The second longitude axis 236 and the first longitude axis 224 may be identical. For example, first longitude axis 224 may respond to a user input in the same way as the second longitude axis 236. In some embodiments, the axis labels of the second longitude axis 236 represent the values of the axis labels for the longitude-time graph 204. The axis labels of the second longitude axis 236 and / or the latitude axis 232 may be equidistant from one another to portray equal intervals of the respective longitude or latitude. Like the first longitude axis 224, the second longitude axis 236 may span any portion of longitudes found on the planet. For example, as shown in Figure 4A, the second longitude axis 236 spans from 180 W to 120 E. However, other ranges are possible. Like the first longitude axis 224, the second longitude axis 236 may run easternmost to western-most from left to right (e.g., as shown in Figure 4A), but other configurations are possible.

[0078] The latitude axis 232 may span any latitude found on the planet. For example, the latitude axis 232 may span from 90 S (e.g., 90° South) to 90 N (e.g., 90° North) or any range therein. For example, as shown in Figure 4A, the latitude axis 232 may range from 15 S (e.g., 15° South) to 15 N (e.g., 15° North). The latitude axis 232 may include axis labels that run western-most to eastern-most from left to right (e.g., as shown in Figure 4A), but other variations are possible. Axis labels may be spaced equidistant from each other to indicate equal latitude intervals therebetween.

[0079] Each axis label of the first longitude axis 224 and / or latitude axis 232 may include gridlines. For example, the longitude-latitude graph 212 may include one or more horizontal gridlines 296 and / or vertical gridlines 294. In some designs, the vertical gridlines 294 may correspond to gridlines found in the longitude-time graph 204. If the first longitude axis 224 and the second longitude axis 236 span the same values, then the same vertical gridlines 294 may appear to run through both the longitude-time graph 204 and the longitude-latitude graph 212. In some embodiments, the longitude-latitude graph 212 may display a longitude-latitude map. In some designs, the longitude-latitude map may include a portion of the same features in the longitude-time map. The longitude-latitude map may be a geographical map of a portion of the planet. For example, the longitude-latitude map may identify the contours and / or limits of various landmasses (e.g., continents, islands). This information may help a user quickly ascertain over which landmass or body of water, for example, an orbital object may be located. For example, it may be useful to a viewer to see that a satellite orbits above a portion of Africa (or other planetary location). Points displayed on the corresponding graph (e.g., the longitude-latitude graph 212) may be superimposed over the geographic map (e.g., the longitude-latitude map).

[0080] The scalar-time graph 208 may include a scalar-time graph area 252 that is bounded by a scalar axis 248 and a second time-axis 244. Each of the scalar axis 248 and / or the second time-axis 244 can include one or more axis labels. The second time-axis 244 and the first time-axis 220 may be identical. For example, first time-axis 220 may respond to a user input in the same way as the second time-axis 244. In some embodiments, the axis labels of the first time-axis 220 represent the values of the axis labels for the scalar-time graph 208. The axis labels of the scalar axis 248 and / or the second time-axis 244 may be equidistant from one another to portray equal intervals of the respective longitude or latitude. Like the first timeaxis 220, the second time-axis 244 may span any time from a historical time to nearly a current time of a user. Additional details on the historical and (nearly) current times are discussed above in regard to the longitude-time graph 204.

[0081] Like the first time-axis 220, the second time-axis 244 may include axis labels that run earliest to most recent from top to bottom (e.g., as shown in Figure 4A), but other variations are possible. Axis labels may be spaced equidistant from each other to indicate equal time intervals therebetween. An axis label may show a corresponding time to include a year, a month, a day, an hour, a minute, and / or a second, depending on the level of specificity that is available, the span of the first time-axis 220, and / or the level of detail that is needed for a particular display. As shown in Figure 4A, each axis label may not include superfluous detail (e.g., not show a year at each interval) in order to reduce clutter and to increase clarity for a viewer.

[0082] The scalar axis 248 may span any value of scalars associated with scalars within a database. Each scalar displayed may correspond to a magnitude or other value. For example, the magnitude may represent an intensity (e.g., of light from the orbital object). However, other scalar values are also possible, such as a size, a projected area, a temperature, a mass, a radar cross section, an altitude, an inclination, a delta-V, a time until a certain event, a probability of a certain event, etc. Many variants are possible. The scalar axis 248 may include axis labels that run greatest to smallest from left to right (e.g., as shown in Figure 4A), but other variations are possible. Axis labels may be spaced equidistant from each other to indicate equal scalar intervals therebetween.

[0083] Each axis label of the scalar axis 248 and / or the second time-axis 244 may include gridlines. For example, the scalar-time graph 208 may include one or more horizontal gridlines 296 and / or vertical gridlines 294. In some designs, the horizontal gridlines 296 may correspond to gridlines found in the longitude-time graph 204. If the first time-axis 220 and the second time-axis 244 span the same values, then the same horizontal gridlines 296 may appear to run through both the longitude-time graph 204 and the scalar-time graph 208.

[0084] The visualization display 200 may further include a display area 216. The display area 216 may be configured to display an image chip 268. This may offer a viewer an opportunity to see an underlying photograph from which image data were extracted that correspond to a set of data or identifiers that are associated with one or more points displayed by the visualization display 200. The image chip 268 may correspond to a photograph of one or more orbital objects. For example, the image chip 268 may be a representation of the photograph. In some cases, the image chip 268 may display an object image 270 that represents an orbital object. The image chip 268 may include multiple object images 270 (e.g., sequential images, summated images (see below), etc.). The display area 216 may also include an interface toggle 266, which is described in more detail below.

[0085] The visualization display 200 may further include a point marker 256. The point marker 256 may be used to identify a pixel associated with one or more points (e.g., longitude-time points) indicated by a user within the display currently. For example, the point marker 256 may comprise a highlighted pixel (or cluster of pixels around the highlighted pixel) to identify the current pixel / point. The one or more points displayed by the visualization display 200 may be received from one or more databases (e.g., the historical data server 140,the contemporary data server 150, the metadata server 154) via one or more data interfaces (e.g., the real-time orbital object data interface 172, the tagging interface 174, the image interface 176, the real-time connection interface 178). The data interfaces may be referred to as application program interfaces (e.g., APIs). The user may use an input device (e.g., a keyboard, a mouse, a digital pen, a microphone, a touch screen, etc.) to indicate the currently identified pixel. The point marker 256 may further be indicated by a horizontal tracking line 260 and / or vertical tracking line 264. As shown in Figure 4A, each of the horizontal tracking line 260 and vertical tracking line 264 may be visible in multiple graphs. For example, if the point marker 256 is displayed in the longitude-time graph 204, the horizontal tracking line 260 may be displayed in both the longitude-time graph 204 and the scalar-time graph 208. Similarly, the vertical tracking line 264 may be visible in both the longitude-time graph 204 and the longitude-latitude graph 212.

[0086] The point marker 256 may be associated with one or more point marker metadata stamps. The one or more point marker metadata stamps may display one or more data types not evident from a graph in which the point marker 256 is currently displayed. For example, in the longitude-time graph 204, a scalar stamp 274 and / or object identifier stamp 282 may be displayed. This may be because the longitude-time graph 204 is not configured to display scalar and / or object identifier information. Similarly, a time value, scalar value, and / or object identifier may be displayed for an identified pixel within the longitude-latitude graph 212. Moreover, a longitude value, latitude value, and / or object identifier may be displayed for an identified pixel within the scalar-time graph 208. As shown in Figure 4A, the scalar stamp 274 and / or object identifier stamp 282 may be displayed near (e.g., within a few pixels of) the point marker 256. The scalar stamp 274 can display a scalar value corresponding to a point associated with the identified (e.g., highlighted) pixel. As shown, the scalar value could be, for example, “12.1 VMag.” Similarly, the object identifier stamp 282 may display an object identifier (e.g., object name) corresponding to the point associated with the identified pixel. As shown, the object identifier could be, for example, 27820:11023 (AMC-9 (GE-12)). In some embodiments, as noted above, a latitude stamp (not shown) can be displayed. The latitude stamp may be displayed near the point marker 256 and may display a latitude value corresponding to the point associated with the identified pixel.

[0087] One or more of the horizontal tracking line 260 and / or the vertical tracking line 264 may have corresponding tracking line metadata stamps. The one or more tracking line metadata stamps may correspond to data types displayed by the corresponding graph in which the identified pixel is displayed. For example, as shown in Figure 4A, an identified pixel within the longitude-time graph 204 may include a horizontal tracking line 260 and / or the vertical tracking line 264 that correspond, respectively, to a tracking line time stamp 298 and / or a tracking line longitude stamp 290. Similarly, an identified pixel within the longitude-latitude graph 212 may include a horizontal tracking line 260 and / or vertical tracking line stamp 290 that correspond, respectively, to a tracking line latitude stamp and / or a tracking line longitude stamp 290. Moreover, an identified pixel within the scalar-time graph 208 may correspond to a horizontal tracking line 260 and / or vertical tracking line stamp 290 that correspond, respectively, to a tracking line time stamp and / or a tracking line scalar stamp. In this way, a user can quickly identify one or more values associated with the pixel identified by the point marker 256. The horizontal tracking line stamp (e.g., tracking line time stamp 298) and / or the vertical tracking line stamp (e.g., tracking line longitude stamp 290) may be displayed near the corresponding tracking line.

[0088] As shown in Figure 4A, the longitude-time graph 204 may include one or more unhighlighted collections 272 of longitude-time points, highlighted collections 276 of longitude-time points, and / or selected collections 280 of longitude-time points. Similarly, the longitude-latitude graph 212 may include one or more unhighlighted collections 284 of longitude-latitude points, highlighted collections 288 of longitude-latitude points, and / or selected collections 292 of longitude-latitude points. Moreover, the scalar-time graph 208 may include various scalar-time points 254 within the scalar-time graph area 252. The scalar-time points 254 may include points that are highlighted, unhighlighted, and / or selected.Object Tracking

[0089] The visualization display 200 described herein can be used to track orbital objects and present that data to a user / viewer in a meaningful way. The systems displayed herein provide a novel way of presenting high-dimensional (e.g., four-dimensional, fivedimensional, or higher dimensional) data in a way that is understandable by a human viewer.

[0090] For additional detail related to Figure 4A, reference will now include reference to Figures 4B-4D. Figure 4B shows a detailed view of an example longitude-time graph 204 that may be a part of the visualization display 200 described in Figure 4A. The first longitude axis 224 may span from a lower-longitude limit 312 to an upper-longitude limit 316. Similarly, the first time-axis 220 may span from a lower time-limit 304 to an upper-time limit 308. Within the longitude-time graph area 228, the visualization display 200 may include one or more sets of longitude-time points. The one or more sets of longitude-time points may correspond to one or more pixels. Each set of longitude- time points may correspond to data on one or more orbital objects around the planet. For example, each of the one or more longitudetime points may correspond to a data set comprising historical data and / or contemporary data. Each set of longitude-time points may correspond to a set of identifiers. The set of identifiers may include a longitude value, a latitude value, a time value, a scalar value, and / or an object (e.g., name) identifier. Each set of identifiers may be obtained from one or more photographs. The photographs may contain image data from which one or more identifiers of the set of identifiers can be obtained (e.g., through algorithm).

[0091] The longitude- time points displayed within the longitude-time graph area 228 may be points that have a time value between the lower-time limit 304 and the upper-time limit 308. Additionally or alternatively, the displayed longitude-time points may have a longitude value between the lower-longitude limit 312 and the upper-longitude limit 316.

[0092] As shown in Figure 4B, the point marker 256 may comprise one or more highlighted pixels that can help a user determine which pixel is identified by a user input device. If the pixel is associated with object data, the scalar stamp 274 and / or object identifier stamp 282 may be displayed within the longitude-time graph area 228. One or both of the scalar stamp 274 and the object identifier stamp 282 may be displayed in an area easily associated with the point marker 256. If the identified pixel does not contain corresponding object data, then the respective scalar stamp 274 and / or object identifier stamp 282 may not be displayed. As shown the pixel currently identified by the point marker 256 is a pixel that includes a selected collection 280 of longitude-time points.

[0093] In order to further aid a user, an interface toggle 320 may be included in the longitude- time graph 204. The interface toggle 320 may be manipulated by a user from an input device (e.g., function keys on a keyboard, a mouse, etc.). The interface toggle 320 maycommunicate with the user settings module 132 (see Figure 4A) to determine, for example, display settings for the longitude-time graph 204. A user may be able to adjust the display settings using the interface toggle 320. For example, the user may be able to click a box to switch a view type. The user may be able to filter what types of points (e.g., unhighlighted, highlighted, selected) are displayed. The interface toggle 320 may allow a user to toggle the display of the longitude-time map on and off. For example, as shown in Figure 4B, the longitude-time map is toggled off while in Figure 4A it is toggled on.

[0094] Figure 4C shows a detail view of an example longitude-latitude graph 212 that may be a part of the visualization display 200 described in Figure 4A. The second longitude axis 236 may span from a lower-longitude limit 412 to an upper-longitude limit 416. Similarly, the latitude axis 232 may span from a lower-latitude limit 408 to an upper-latitude limit 404. The longitude-latitude points displayed within the longitude-latitude graph area 240 may be points that have a latitude value between the lower-latitude limit 408 and the upperlatitude limit 404. Additionally or alternatively, the displayed longitude-latitude points may have a longitude value between the lower-longitude limit 412 and the upper-longitude limit 416.

[0095] The longitude-latitude graph area 240 may include various displayed longitude-latitude points. For example, the longitude-latitude graph 212 may display one or more unhighlighted collections 284 of longitude-latitude points, highlighted collections of longitude-latitude points (not shown), and / or selected collections 292 of longitude-latitude points. In some cases, the one or more selected collections 292 of longitude-latitude points may include highlighted longitude-latitude points. Figure 4C shows the point marker 256 over a point in a selected collection 292 of longitude-latitude points.

[0096] As shown in Figure 4C, the point marker 256 may be displayed within the longitude-latitude graph 212. For example, a user may use an input device to indicate where and / or in which graph the point marker 256 is located. As noted above, if the point marker 256 is displayed within the longitude-latitude graph 212, a tracking line latitude stamp 422 may be displayed. The tracking line latitude stamp 422 displays a latitude value associated with a longitude-latitude point corresponding to the pixel identified by the point marker 256. Additionally or alternatively, a tracking line longitude stamp 290 may be displayed. One ormore point marker metadata stamps (e.g., the scalar stamp 274, the object identifier stamp 282, a latitude stamp, a longitude stamp, a time stamp) may be displayed, as described above.

[0097] An interface toggle 426 may be included to aid a user in interacting with the longitude-latitude graph 212. For example, the interface toggle 426 may allow a user to toggle a view of the longitude-latitude map on or off. The interface toggle 426 may be manipulated by a user from an input device (e.g., function keys on a keyboard, a mouse, etc.). As shown in Figure 4C, the longitude-latitude map is toggled on. Other functionality is also possible.

[0098] Figure 4D shows a detail view of an example scalar-time graph 208 that may be a part of the visualization display 200 described in Figure 4A. The scalar-time graph 208 may show one of a number of possible scalar values. For example, the scalar may refer to a magnitude, such as an intensity of reflected light. However, a number of other scalar values are possible, such as a size, a projected area, a temperature, a mass, a radar cross section, an altitude, an inclination, a delta-V, a time until a certain event, a probability of a certain event, etc. In some embodiments, the scalar-time graph 208 may show residual values associated with a track or a group of longitude-time points in the longitude-time graph 204. In some cases, the track or the group of longitude- time points may be selected by a user or by system 100 (e.g., in response to a user input). In some examples, the residual values may indicate a difference between the track, or the group of longitude-time points an orbital parameter (e.g., an orbital path) determined by the system 100 based at least in part the track or the group the group of longitude-time points. In some embodiments, the scalar-time graph 208 may show values of an auxiliary parameter determined based at least in part on a track or a group of longitude-time points. In some such embodiments, the auxiliary parameter may be configured to assist the user with evaluating a calculation performed by the system 100 (e.g., evaluating the accuracy of a calculation performed by the system 100), a user input, or a selection made bay a user. In some examples, the system 100 may determine a residual value of a determined orbital path by determining a difference between a timepoint of the determined orbital path and a corresponding timepoint of a received orbital path (e.g. a reference orbital path received from server). In some examples, the system 100 may determine a residual value of a determined orbital path by determining a difference between a timepoint of the determined orbital path and another time point associated with orbital object data used to generate the determined orbital path.

[0099] The scalar axis 248 may span from a lower-scalar limit 512 to an upperscalar limit 516. Similarly, the second time-axis 244 may span from a lower-time limit 504 to an upper-time limit 508. The scalar-time points displayed within the scalar-time graph area 252 may be points that have a scalar value between the lower-scalar limit 512 and the upperscalar limit 516. Additionally or alternatively, the displayed scalar-time points may have a time value between the lower-time limit 504 and the upper-time limit 508.

[0100] As shown in Figure 4D, the point marker 256 may be displayed within the scalar-time graph 208. As noted above, if the point marker 256 is displayed within the scalartime graph 208, one or more metadata stamps may be displayed. For example, the tracking line time stamp 298 may indicate a time value of a scalar-time point corresponding to the pixel identified by the point marker 256. Similarly, a tracking line scalar stamp (not shown) may indicate a scalar value of a scalar-time point corresponding to the pixel identified by the point marker 256 Additionally or alternatively, one or more point marker metadata stamps (e.g., the scalar stamp 274, the object identifier stamp 282, a latitude stamp, a longitude stamp, a time stamp) may be displayed, as described above.

[0101] The scalar-time graph 208 may display one or more unhighlighted collections 584 of scalar-time points, highlighted collections 584 of scalar-time points (not shown), and / or selected collections 580 of scalar-time points. As shown, the point marker 256 identifies a pixel associated with a point in a selected collection 580 of scalar-time points. An interface toggle 522 may be included to aid a user in interacting with the scalar- time graph 208. For example, the interface toggle 522 may allow a user to toggle which type(s) (e.g., unhighlighted, highlighted, selected) points are displayed. Additionally or alternatively, the interface toggle 522 may allow a user to toggle between a stitching panel and a graph and / or to toggle which type of scalar is displayed by the scalar-time graph 208. Other functionality is also possible.

[0102] With reference generally to Figures 4A-4D, the system may allow a user to interact with the visualization display 200 in a variety of beneficial ways. For example, a user may be able to pan and zoom within one or more graphs in the visualization display 200. Panning may be up, down, left, right, or any other direction along an axis. Zooming may include zooming in and / or out. The user may give a panning input and / or a zooming input via an input device. The panning input and / or zooming input may comprise a scrolling of a mousewheel, a click of a mouse, a pinch motion, a flick motion, a swipe motion, a tap, and / or any other input identifying a pan or zoom action. The visualization display 200 may be configured to allow simultaneous manipulation of multiple graphs. For example, in response to a user input to pan or zoom the first time-axis 220 or the second time-axis 244, the system may set the lower-time limit 304 equal to the lower-time limit 504 and / or set the upper-time limit 308 equal to the upper-time limit 508. Similarly, in response to a user input to pan or zoom the first longitude axis 224 or the second longitude axis 236, the system may set the lower-longitude limit 312 equal to the lower-longitude limit 412 and set the upper-longitude limit 316 equal to the upper-longitude limit 416.

[0103] A user may be able to set the upper and / or lower limits of a given axis. Additionally or alternatively, the user may be able to set axis spacing, axis intervals, axis labels, axis formatting, axis length, and or other aspects associated with one or more axes. Once set, the system may be configured to automatically update that axis. In some embodiments, the system may be configured to automatically update a corresponding axis. For example, automatically updating a corresponding axis may include setting a common alignment for both of the two axes, setting a common length for both of them, and / or disposing them parallel to one another. The first longitude axis 224 and second longitude axis 236 may be corresponding axes. Similarly, the first time-axis 220 and second time-axis 244 may be corresponding axes.

[0104] Zooming may be defined as changing a total span (e.g., a difference between an upper-axis limit and a lower-axis limit) of one or more axes in the visualization display 200. A single axis may be zoomed in or out by the user. A single graph (e.g., two perpendicular axes) may be zoomed in or out. However, the system may be configured to allow a user to zoom in and / or out on multiple axes and / or graphs simultaneously. For example, zooming in on the longitude-time graph 204 may adjust not only the first time-axis 220 and first longitude axis 224, but it may adjust the second time-axis 244 as well.

[0105] Zooming and / or panning in one axis or one graph may affect which points are displayed in other graphs within the visualization display 200. For example, in an adjustment of the lower-time limit 304 or the upper-time limit 308, the system may be configured to update the longitude-latitude graph 212 to display pixels corresponding only to longitude-latitude points corresponding to a set of identifiers having a time identifier between the lower- time limit 304 and the upper- time limit 308.

[0106] Panning and / or zooming may be done within a graph or along an axis. For example, in response to a user input to pan or zoom along a length of first time-axis 220, the system may be configured to simultaneously modify one or more of the lower-time limit 304 and / or the upper-time limit 308. In response to a user input to pan or zoom along a length of second time-axis 244, the system may be configured to simultaneously modify one or more of the lower-time limit 504 and / or the upper-time limit 508. Additionally or alternatively, in response to a user input to pan or zoom along a length of the first longitude axis 224, the system may be configured to simultaneously modify one or more of the lower-longitude limit 312 and / or the upper-longitude limit 316. In response to a user input to pan or zoom along a length of the second longitude axis 236, the system may be configured to simultaneously modify one or more of the lower-longitude limit 412 and / or the upper-longitude limit 416. Additionally or alternatively, in response to a user input to pan or zoom along a length of the latitude axis 232, the system may be configured to simultaneously modify one or more of the upper-latitude limit 404 and / or the lower-latitude limit 408. In response to a user input to pan or zoom along a length of the scalar axis 248, the system may be configured to simultaneously modify one or more of the lower-scalar limit 512 and the upper-scalar limit 516.

[0107] Further, in response to a user input to adjust the lower-longitude limit 312 or the upper-longitude limit 316, the system may update the scalar-time graph 208 to display pixels corresponding only to scalar-time points corresponding to a set of identifiers having a longitude identifier between the lower-longitude limit 312 limit and the upper-longitude limit 316. Similarly, in response to a user input to adjust the upper-latitude limit 404 or the lower- latitude limit 408, the system may update one or more of the longitude-time graph 204 and / or the scalar-time graph 208 to display pixels corresponding only to respective longitude-time points and / or scalar-time points corresponding to a set of identifiers having a latitude identifier between the lower-longitude limit 312 and the upper-longitude limit 316.

[0108] Moreover, in response to a user input to adjust the lower-scalar limit 512 or the upper-scalar limit 516, the system may update one or more of the longitude-time graph 204 and the longitude-latitude graph 212 graph to display pixels corresponding only to respective longitude-time points and / or longitude-latitude points corresponding to a set of identifiers having a scalar identifier between the lower-scalar limit 512 limit and the upper-scalar limit 516.

[0109] As noted above, the system may be configured to store dozens of petabytes of data. This can provide a variety of challenges. One of which is how the data are displayed in a way that is helpful to a human user. Accordingly, in certain embodiments, the visualization display 200 may be configured to divide a graph (e.g., the longitude-time graph 204) into a plurality of pixels. Each pixel may represent a corresponding bin of data. Each bin can be configured to store historical and / or contemporary data as well as metadata.

[0110] In some cases, a single pixel may correspond to a bin containing dozens, hundreds, or even thousands of data sets corresponding to orbital objects. To aid a user in digesting such a large amount of data, the visualization display 200 may be configured to display an indication of the amount of data (e.g., the number of objects, the number of sets of object identifiers) stored therein. For example, a user may use the point marker 256 to identify a pixel. The system can be configured to display a number of object identifiers (e.g., a number of unique object identifiers) between one and a total number of object identifiers associated with the bin associated with the identified pixel. An object identifier can be any type of identifier of an orbital object. The object identifier may comprise one or more letters, numbers, symbols, or any combination of these.

[0111] In some designs, the system is configured to receive a selection from a user of a target object identifier. For example, the system may sequentially cycle (e.g., automatically, manually) through a display of each object identifier associated with the identified pixel (e.g., every second, every two seconds, in response to a user input, etc.). As a different example, the system may be configured to display a list of object identifiers from which a user may select the target object identifier. The system may be configured only to display unique object identifiers since many object identifiers in a single bin may be identical. In some embodiments, the system may not display one or more of the metadata stamps (e.g., the tracking line longitude stamp 290, the horizontal tracking line 260, the object identifier stamp 282, the scalar stamp 274, etc.) until an object identifier has been selected. In certain embodiments, the system displays metadata stamps for each unique object identifier present in the bin. The visualization display 200 may implement a color scale or gray scale to provide information about the number of unique orbital object identifiers in a bin. For example, bins with more unique orbital object identifiers may correspond to lighter pixels while bins with fewer unique orbital object identifiers may be darker. Bins with no orbital object identifiersmay be black. This situation may arise, for example, when viewing a small portion (e.g., zoomed in) of the data in a graph.

[0112] The system can be configured to identify one or more values (e.g., by various metadata time stamps described herein) associated with a default data set. The point marker 256 is an example of an interface element that can identify values in the default data set. The default data set may be determined based on one or more default rules. The default rule(s) may be based on a storage time (e.g., most recently stored), a view time (e.g., most recently viewed), a numerical value (e.g., smallest latitude), an object identifier (e.g., earliest object identifier by alphabetical order), or any other default measure.

[0113] As a user moves the point marker 256, the system may automatically (e.g., in real-time) update the identified values (e.g., metadata time stamps) associated with the updated pixel corresponding to an updated data set. The updated data set may be determined using the same or different rules described above. The user may move the point marker 256 over an updated pixel in a variety of ways, such as by mousing over the pixel using an input device (e.g., mouse), tapping on the pixel (e.g., using a touchscreen), typing in information associated with the updated pixel, or in any other way to identify a pixel.

[0114] It may be advantageous to allow a user to save one or more settings associated with the visualization display 200. For example, a user may wish to return at a later time to a point or set of points displayed by the visualization display 200. This may be accomplished in a number of ways. For example, a user may be configured to bookmark one or more values associated with the target point (e.g., an object identifier, a longitude value, a time value, etc.). The system may store a list of the user’s bookmarks to allow for easy access at a future time. The system may be configured to store a set of points based, for example, on the points having a common object identifier. For example, multiple points may correspond to the same object as it orbits the planet. Thus, multiple points in time and space may reference the same object. The user may be able to retrieve the set of points by inputting the object identifier (e.g., selecting it from a list, typing it in).

[0115] Additionally or alternatively, the system may be able to allow a user to save a view of one or more graphs. For example, a user may be able to bookmark a particular view within the longitude- time graph 204. Accordingly, the system may associate with the bookmark stored values for a bookmark-min longitude value (e.g., the lower-longitude limit312), a bookmark-max longitude value (e.g., the upper-longitude limit 316), a bookmark-min time value (e.g., the lower-time limit 304), and / or a bookmark-max time value (e.g., the uppertime limit 308). Similar usage may be made for other values (e.g., a scalar value, an object identifier, a latitude). Points that satisfy these bookmark-min and / or bookmark-max values could be displayed by the system in response to a user selection of the associated bookmark.Display Synchronization

[0116] One of the benefits of various embodiments described herein is the ability of a user to quickly and easily view and digest an immense amount of data containing variables in three, four, or more dimensions. To help a user visualize data containing higher-dimension values, various graphs of the visualization display 200 may be synchronized to each other.

[0117] For example the first longitude axis 224 and second longitude axis 236 may be synchronized as a user zooms one of them, allowing for a seamless viewing experience when viewing each of the graphs. In some cases, as the first longitude axis 224 and the second longitude axis 236 are synchronized to each other, the scalar-time graph 208 may be also synchronized and updated.

[0118] In some cases, the image chip 268 corresponds to a photograph from which object data has been obtained associated with a pixel identified by the point marker 256. In some embodiments, the image chip 268 identifies which of the plurality of object images 270 corresponds to the data associated with the pixel identified (e.g., by the point marker 256). For example, a marker may be displayed indicating a location of the object within the at least one photograph. The marker may comprise a circle, a box, crosshairs, a coloring, a flicker, or any other indication of an object within a photograph. The user may identify the pixel associated with the object image 270 in other ways described above.

[0119] Image chip 268 data may be received from one or more databases. For example, the system may receive the image chip 268 data from a database remote from the system. Additionally or alternatively, the data may be received from a database local to the system. The image chip 268 data may be received via one or more pointers (e.g., hyperlinks) that point to corresponding databases. For example, various image chip 268 data may be stored on databases associated with the imager (e.g., telescope) from which the data was first obtained.

[0120] The user may select one or more objects from an image chip 268 and a corresponding point or plurality of points may be indicated (e.g., highlighted, supplied with a marker) on one or more of the graphs in the visualization display 200. Additionally or alternatively, the user may be able to select a point or plurality of points on one or more of the graphs in the visualization display 200 and have one or more images (e.g., photo, video) displayed by the image chip 268 with associated marker. In some designs, the image chip 268 is configured to show a video corresponding to multiple points within a graph in the visualization display 200. The multiple points may comprise a common object identifier.

[0121] In some embodiments, the system 100 may determine an orbit of an orbital object based on orbital object data 147 or a selected portion of the orbital object data 147 and display the orbit in the visualization and display 102 one or both longitude-time graph 104 or longitude-latitude graph 112. In some cases, determining the orbit may comprise calculating or estimating one or more orbital parameters. In some cases, the system 100 may display one or more of the determined orbital parameters via the visualization display 102, e.g., numeric value. In some such cases, the system 100 may update the numeric value as different points of the determined orbits are selected by a user via an interaction with the visualization display 102 or an alternative user interface 163. For example, the system 100 may display estimated numerical values of one or both CrAM and CdRAM on a region or section of the first, second, third, or fourth plots 104, 108, 112, 116.

[0122] In some cases, determining the orbit may comprise calculating a level of uncertainty for the orbit and the corresponding parameters and / or calculated data points. In various implementations, the uncertainty of the orbit may comprise a level of residual(s), a variance, or another parameter or set parameters (e.g., a statistical parameter or a covariance matrix) that may quantify precision of the determined orbit and / or the deviation of the determined orbit from the corresponding orbital object data 147 received from the orbital object data interface 185.

[0123] In some embodiments, system 100 may provide an indication of longitudetime points used to determine a scalar identifier displayed in the scalar-time graph 208. For example, with reference to Figure 4A, when user selects a collection 280 or a subset of the collection 280, regions 266a, 266b. in the scalar-time graph 208 that contain values of a scalaridentifier (e.g. residual values) associated with the collection 280, may be highlighted or shaded to indicate the values determined based on longitude-time points in the collection 280.

[0124] In some embodiments, the fourth plot 116 of the visualization display 102 may include an analysis plot that displays calculated values of a parameter (e.g., an astronomical parameter). In some cases, the parameter can be time-dependent parameter (e.g., an astronomical parameter derived as a function of time). Figure 4E schematically illustrates an example visualization display 102 comprising an analysis plot 452 comprising a first scalar axis 458 spanning from a first lower-scalar limit to a first upper-scalar limit, a second scalar axis 454 spanning from a second lower-scalar limit to a second upper-scalar limit, and a graph 456 comprising a plurality of data points associated with an astronomical parameter. In some examples, a first scalar represented by the first scalar axis 458 can be a derived parameter (e.g., derived as a function of time). In some cases, individual ones of the data points 456 may correspond to a pair of identifiers comprising a first identifier between the first lower-scalar limit to the first upper-scalar limit and a second identifier between the second lower-scalar limit to the second upper-scalar limit. In some examples, the data points 456 can be associated with one or more longitude-time points. In some embodiments, the system 100 may be configured to calculate an individual data point of the data points 456 for a selected longitudetime point. In some embodiments, calculated values of the data points 456 on the analysis plot 452 may be synchronously updated with respect to the longitude-time graph 204 and a user selection of a longitude-time point. In one example, the first identifier may comprise absolute visual magnitude (Mv) and the second identifier may comprise a solar phase. In some embodiments, the analysis plot 452 may comprise a marker 459 indicating a value of the first identifier corresponding to a time point selected by a user on the longitude-time graph. In some examples, the marker 459 may comprise a line substantially parallel to the second scalar axis 454, the line traversing at least part of the analysis plot 452. In implementations, some examples, the visualization display 102 may synchronously update the analysis plot 452 by determining the value of the first identifier based at least in part on the time point selected by the user and updating a position of the marker with respect to the first scalar axis. In some embodiments, when the parameter determined and displayed in the analysis plot 452 is a periodic function of time, the analysis plot 452 may comprise a folded (or wrapped) plot where each determined data point corresponds to multiple time points separated by the period of theperiodic parameter. Tn some such embodiments, the marker 459 may be configured to periodically scan the analysis plot 452, e.g., along the first scalar axis 458 when a sequence of longitude-time points comprising time points separated by the period.

[0125] In some embodiments, the visualization display 102 may comprise at least a portion of a geographical map indicating locations of a plurality of orbital object data sources on the geographical map. Figure 4F schematically illustrates an example visualization display 102 including a geographical map 464 comprising one or more indicators indicating geographical locations of one or more orbital object data sources from which the orbital object data displayed on the visualization display 102 are received. In some embodiments, the geographical map 464 may be overlaid on a previously-described element of the visualization display 102 (e.g., the longitude-latitude graph 212, longitude-time graph 204, or any other portion of the visualization display 102 described herein). In some embodiments, in response to a user selection of one or more data points on one of the plots 104, 108, 112, and / or 116 in the visualization display 102 (e.g.. selected longitude-time points 462 on the longitude-time graph 204), the system 100 may highlight one or more the indicators corresponding to the locations of the orbital object data sources of the plurality of orbital object data sources 155 on the geographical map 464, from which the selected longitude-time points 462 or the corresponding orbital object data have been received. In some embodiments, user interface portion 466 and user interface portion 468 may present various additional information types. For example, the user interface portion 466 or user interface portion 468 may display, in any order, the analysis plot 452, scalar-time graph 208, longitude-latitude graph 212, longitudetime graph 204, or any other element of the visualization display described herein. Further, the information displayed by the user interface portion 466 or user interface portion 468 may be modified based on the user selection of one or more data points, or selected one or more indicators of the one or more indicators 465 corresponding to the locations of the orbital object data sources on the geographical map 464.

[0126] In various implementations, a user may select a track associated with a group of identifiers. In some examples, a track may represent a path that an orbital object takes in space. In some cases, a user may select an orbital object by selecting a track (e.g. a track in the longitude-time graph 204 or longitude-latitude graph 212) comprising identifiers associated with the orbital object. In some examples, a point or pixel in the longitude-time graph 204 (orlongitude-latitude graph 212) may be used to indicate data points (e.g., timepoints) associated with an object’s trajectory, position, time, etc. In some cases, in response to a user selection of a track representation, the display can indicate a selection (e.g., automatic, user-identified) of a different track representation corresponding to a second track associated with the same orbital object. The system may automatically determine that the second track representation based on a determination that the second track is associated with the same orbital object as the first track.

[0127] In some embodiments, the system 100 may receive a user selection of a plurality of timepoints corresponding to one or more orbital objects. Each timepoint may include sets of identifiers within a selected time period. For example, as shown in Figure 4B, the point marker 256 indicates that a user has selected the track representation associated with the collection 280. Based on these timepoints, the system 100 can determine an orbital path of an orbital object associated with the selected plurality of timepoints, wherein the orbital path is determined over an orbital time period that includes a time period that (i) overlaps the selected time period, (ii) precedes the selected time period, (iii) succeeds the selected time period, or (iv) any combination thereof. The selected time period generally spans from a lowertime limit to an upper-time limit that may be selected by a user or in certain implementations by the system automatically. The selected time period can determine one or more axes of one of more graphs displayed, such as any of the graphs described herein. The display can show an indication of the orbital path of the object spanning the selected time period. The selection of the timepoints may include a selection based on two or more identifiers of those timepoints. This selection may help the system identify an orbital object of interest. For example, the selection may be based on a selection of a time identifier and a name identifier, multiple time identifiers, multiple longitude identifiers, multiple latitude identifiers, a combination of these, or some other combination of identifiers.Maneuver Determination

[0128] Orbital objects may from time to time change their expected trajectory (e.g., an orbital path in the absence of forces and perturbations different from earth’s gravity). For example, altitude, longitude, latitude, and / or velocity of an orbital object may be altered (e.g., intentionally or unintentionally). This alteration may occur through short accelerations (e.g., generated by bums) and / or sustained (e.g., continuous) accelerations for a given period. Insome instances, the orbital path of an orbital object may be altered to adopt a new orbital path (e.g., the orbit of a target orbital object or some other orbit). In some examples, adopting a new orbit, such as the orbit of a target orbital object, may be called an orbit transfer. It may additionally or alternatively be desirable to not only adopt another orbit but to do so at the same or similar position of a target object (e.g., substantially along the same path as the other orbital object). In some examples, a maneuver may comprise transfer from a first orbit (or orbital path) to a second orbit different from the first orbit.

[0129] In one embodiment, orbital visualization and computing system 100, herein referred to as “system”, may be configured to receive orbital object data 147 comprising one or more of real-time data, historical telescope data and metadata, from the orbital object data sources 155 via the data network 144 and use the orbital object data 147 to assist a user with identifying a maneuver performed by the orbital object and determining (or estimating) a maneuver time, a characteristic of the maneuver, and a pre / post-maneuver orbital parameters for the orbital object via user’s interaction with a user interface of the system 100. In various implementations, user interaction with a user interface may include providing a user input using a textual user interface (e.g., the alternative user interface 163), a graphical user interface (e.g., the visualization display 102), or a combination thereof. In some examples, the graphical user interface may allow the user to select a data point (or a group of data points), provide a parameter value, or change a parameter value, using a pointing device (e.g., a mouse). Advantageously, providing or changing a parameter value, using a pointing device may facilitate an estimation process based on user input. For example, the graphical user interface may allow the user to change a parameter via interaction with an element (e.g., slider) close to or in the same portion of the display where the result(s) of an estimation based on the parameter are displayed (e.g., in real time or with a short delay).

[0130] In some embodiments, the orbital object data sources 155 may comprise the contemporary data server 150, the historical data server 140, the metadata server 154. In various implementations, that data stored in the historical data server 140, the metadata server 154, or the contemporary data server 150 may comprise data received from at least two ground- based telescopes 113-1, 113-2, placed at two different locations of on planet earth, received from at least two different spaced-based telescopes orbiting the earth, or from a space-based telescope and a ground-based telescope.

[0131] In some cases, the system 100 may directly receive at least a portion of the orbital object data from a telescope (e.g., telescope 113-1 - 113N), or another orbital data capturing device that optically or electromagnetically tracks the orbital object, e.g., via the data network 144 or a wireless link established between the system 100 and the orbital data capturing device. In some cases, orbital object data may be received from an orbital object data source 155 selected by the user via a user interface of the system 100 or determined by the system 100 based on a user input provided to the system 100. For example, orbital object data may comprise data collected during a period selected by the user via a user interface (e.g., visualization display 102) of the system 100. As another example, orbital object data 147 may comprise data collected during a period determined by the system 100 based on a user input provided to the system 100. In various implementations, the system 100 may select a data source (e.g., from the orbital object data sources 155) or an orbital data capturing device based on a time period selected by the user. For example, the system 100 may determine which data source or an orbital data capturing device includes orbital data captured during the selected time period or a time period that at least partially overlaps with the selected time period (e.g., where the overlap is longer than a threshold value).

[0132] As described above the orbital object data may comprise image data, and corresponding set of identifiers including but not being limited to a name identifier, a time identifier, a latitude identifier, a longitude identifier, an azimuth & elevation identifier, a right ascension identifier, and a declination identifier. In some cases, image data may comprise an image (e.g., a digital image), a photograph, or any data that can be converted to an organized arrangement point with respect to a coordinate system. In some examples, the time identifier, a latitude identifier, and a longitude identifier may be configured to allow the system or a user to determine a data capturing time and coordinate of the corresponding data points with respect to a selected coordinate system and reference time (e.g., a time zone).

[0133] In some embodiments, a user may use the system 100 and orbital object data received by system 100 to detect, identify, or analyze a maneuver performed by an orbital object based on at least a portion of the orbital object data received by the system (e.g., based on a user selected period). In some cases, the user may provide a lower time-limit (Tmin) 304 and an upper time-limit (Tmax) 308 to the system 100 (e.g., to the visualization display 102 of the system 100) to cause the visualization display 102 to display orbital object data collectedbetween the lower time-limit 304 and the upper-time limit 308 (e.g., a subset of orbital object data having time identifiers between the lower-time limit and an upper-time limit). In various implementations, one or both the lower-time limit 308 and the upper-time limit 308 may be received from the user via an interaction with the display interface of the visualization display 102.

[0134] In some cases, the display interface may comprise a longitude-time graph 204 a latitude-longitude graph, or another type of graph. For example, display interface may comprise a longitude-time graph having a longitude axis spanning from a lower-longitude limit 312 to an upper-longitude limit 316 and time-axis spanning the period from Tmin 304 to Tmax 308.

[0135] In some examples, the user may select a portion of displayed data associated with an orbital object to detect or identify a maneuver performed by the object, and estimate (or determine) a time at which the maneuver is initiated (herein referred to as maneuver time), characteristic of the maneuver, and the corresponding orbital parameters in a time period before or after the maneuver. In some such cases, the system may use at least the identifiers associated with the displayed portion of orbital object data to determine an orbital parameter or a maneuver characteristic for the orbital object.

[0136] In some embodiments, system 100 may be configured to detect and / or characterize a maneuver performed by an orbital object based on a portion of orbital object data captured during a time widow that at least partially overlaps with a maneuver time or a maneuver period. In some examples a maneuver may comprise a change of a value of a kinematic and / or dynamic parameter of an orbital object. For example, a maneuver may involve a velocity change denoted as a “delta V”.

[0137] In some examples maneuver may begin at a maneuver time where a kinematic and / or dynamic parameter of the orbital object deviates from a first value or a first vector associated with the first orbit to a second value or a second vector, e.g., due to a shortlived or transient force or perturbation. In some examples maneuver may begin at a maneuver time where a kinematic and / or dynamic parameter of the orbital object deviates from a value or a vector associated with the first orbit and last for maneuver period by the end of which the second orbit is adopted, e.g., due to a force or perturbation lasting during a portion of themaneuver period. In some cases, during a maneuver period the orbital object may complete at least two separate maneuvers, an initial maneuver and a final maneuver.

[0138] In some embodiments, a user interface of system 100 (e.g., GUI of the visual display 102) may be helpful in visualizing, identifying, and / or characterizing a maneuver performed by an orbital object. The user may use one or more features described above with respect to the visualization display 102, 200, to select orbital object data (e.g., the identifiers associated with the orbital object data), identify a maneuver (e.g., a maneuver period), and determine pre- and / or post-maneuver orbital parameters (e.g. pre- or post-maneuver orbits or orbital paths). For examples, the user ma use a zoom control interface (e.g., a time-axis zoom control interface, a longitude axis zoom control interface, etc.) and / or a pan control interface (e.g., a time-axis pan control interface, a longitude axis pan control interface, etc.) to select different portions of orbital object data displayed by the visual display 102. The zoom control interface can allow a user to select a scale factor for one or more axes of a graph (e.g., a longitude-time graph, a longitude-latitude graph, a magnitude-time graph, etc.). Additionally, or alternatively, the pan control interface can allow a user to move a lower and / or upper limit of a graph in the same direction.

[0139] In some embodiments, the user interface (e.g., the visual display 102) may include one or more indications of orbital paths that have been stored, received, and / or determined by system 100 and may allow a user to select an initial orbit or pre-maneuver orbit and a target or post-maneuver orbit of an orbital object. One or both of the initial and target orbits (or pre- and post-maneuver orbits) may be selected from stored, received, and / or determined orbits. The system may allow a user to quickly and easily toggle between which selected object corresponds to the initial orbit and which one corresponds to the target orbit, where applicable.

[0140] In some implementations, using the user interface, the user can select an orbit transfer or maneuver window (e.g., an orbit transfer time window, an orbit transfer longitude window, etc.). The orbit transfer window can set boundary conditions for when and / or where an orbit transfer is initiated, at least partially took place, and / or completed by an orbital object. For example, a “now” line on the user interface may serve as a minimum boundary condition on time. The transfer window can identify the duration of a maneuver or transfer period (e.g., when the transfer may have begun, and / or when it may have ended. Insome embodiments, based on the transfer window, the system may determine (e.g., automatically determine) a transfer duration, a transfer start position, a transfer end position, and / or a total transfer distance. Automatically may mean occurring without further input from a user (e.g., execution instruction, selection, etc.). The system may allow a user to set a maximum computation time that determines how long the system can strive to best approximate the calculated value(s) within the set time. For example, a user may set a maximum computation time of about 0.01 s, 0.1 s, 0.5 s, 1 s, 2 s, 5 s, 10 s, 25 s, 30 s, 45 s, 60 s, or any value therein or a range of values having any endpoints therein. The transfer window can determine in part based on efficiency of an energy expenditure by the selected object. For example, a larger time window may improve an efficiency of an energy expenditure of a selected orbital object.

[0141] Figure 5 shows an example maneuver determination process where an orbital object has moved from a first orbital path (first orbit) to a second orbital path. In some cases, an orbital object may have changed its trajectory, and the user may determine an estimated maneuver time or maneuver period based on orbital object data collected during a time window during which the maneuver may have occurred.

[0142] In some cases, a target or post-maneuver track identifier 1054 may show details related to the orbital object. As shown, a pre-maneuver orbit 1086 of an orbital object is displayed in the longitude-time graph 204 and the longitude-latitude graph 212. A corresponding post-maneuver orbit 1088 is also shown. When transferring between the premaneuver orbit 1086 and the post-maneuver orbit 1088, the orbital object may have undergone at least one maneuver 1090.

[0143] In some examples, the time window may at least partially overlap with a pre-maneuver and a post-maneuver period. In some embodiments, the system may use the estimated maneuver time to determine a post-maneuver parameter using a maneuver determination process. In some implementations, the accuracy of the post-maneuver parameter (e.g., a post-maneuver orbit or orbital path) determined using a given algorithm or method may change when an amount of post-maneuver orbital object data changes. In some various implementations, a lower limit for the amount of post-maneuver orbital object data used to determine the post-maneuver parameter with a given accuracy may change for different algorithms or methods used to determine the post-maneuver parameter. In some examples, theamount of post-maneuver orbital object data may comprise a number of data points associated with times after estimated maneuver time and used for determining the post-maneuver orbital parameter.

[0144] In some embodiments, system 100 may use one or more maneuver determination processes allow a user to quickly and / or automatically determine a maneuver or a transfer that has taken place. In various implementations, determining a maneuver may comprise one or more of detecting a maneuver, estimating a maneuver time or period, determining a post-maneuver parameter, determining a pre-maneuver parameter, determining a post-maneuver uncertainty parameter, determining a pre-maneuver uncertainty parameter, determining a maneuver characteristic, and the like.

[0145] In some embodiments, the user may provide an input to the system to activate a maneuver determination mode in the system. In various implementations, the user may activate the maneuver determination mode by selecting an option in the display interface (e.g„ pushing a button), providing a command via a text prompt, or other types of user interaction with a user input device or a user interface of the system. In some examples, activating the maneuver determination mode may comprise selecting a maneuver determination algorithm to be executed by a processor of system 100 to determine a maneuver performed by a selected orbital object.

[0146] In some embodiments, a maneuver determination mode may comprise a maneuver determination process configured to determine a post-maneuver parameter and analyze various aspects of a maneuver performed by the orbital object based at least in part on a portion of identifiers associated the selected and / or displayed data associated with an orbital object. In some cases, the identifiers may be included in the orbital object data received by the orbital visualization and computing system 100 from an orbital object data source of the orbital object data sources 155 via the orbital object data interface 185.

[0147] In some embodiments, when the maneuver determination mode is activated, the system may perform a selected maneuver determination process. In some cases, the selected maneuver determination process may comprise determining a post-maneuver orbital parameter and / or a pre-maneuver orbital parameter. In some examples, the post / pre-maneuver orbital parameter may comprise a position vector of the orbital object, a velocity vector of the orbital object, an orbital path of the orbital object comprising a plurality of data points (e.g.,longitude-time points), CrAM, CdAM, a plurality of velocity vectors at different positions along an orbital path, or any other kinematic or dynamic parameter (or series of kinematic or dynamic parameters) for the orbital object. In some examples, the pre-maneuver orbital parameter may be associated with a time before the maneuver time or period and the postmaneuver orbital parameter may be associated with a time after the maneuver time or period.

[0148] In some embodiments, when the maneuver determination process may determine a maneuver based at least in part on an estimated maneuver time determined by the system or received by the system (e.g., from a user, a memory, a data base or another system). In some embodiments, the system may receive or determine a time window during which the maneuver may have been performed and an estimated maneuver time within the time window. In some embodiments, a first plurality of data points (e.g., longitude-time points) that are within the time window and are associated with times (e.g., having time identifiers) before the estimated maneuver time may be considered as pre-maneuver data and may be used for determining one or both a pre-maneuver orbital parameter and a pre-maneuver uncertainty parameter. In some embodiments, a second plurality of data points (e.g., longitude-time points) that are within the time window and are associated with times after the estimated maneuver time may be considered as post-maneuver data and may be used for determining one or both a post-maneuver orbital parameter and a post-maneuver uncertainty parameter. Alternatively, in some embodiments, may receive a first user input comprising a selection of the first plurality of the data points and a second user input comprising a selection of the second plurality of the data points.

[0149] In some embodiments, the maneuver determination process may further comprise determining a maneuver characterization parameter based on one or both the premaneuver orbital parameter (e.g., the determined pre-maneuver orbital parameter) and the post-maneuver orbital parameter (e.g., the determined post-maneuver orbital parameter). In some embodiments, the maneuver characterization parameter may comprise one or more of characteristics of a maneuver (e.g.. a maneuver time, duration of a maneuver, a change of the velocity vector, and / or a change of the position vectors), a maneuver sequence, and postmaneuver data. In some embodiments, the maneuver characterization parameter may comprise a value or change of a kinematic and / or a dynamic parameter of the orbital object (e.g., the orbital object selected by the user), at or close to an initial or estimated maneuver time period.

[0150] In some embodiments, the system may comprise at least two types of maneuver determination modes: a manual maneuver determination mode and an automatic maneuver determination mode. Accordingly, the maneuver determination process may comprise different levels of user contribution including providing one or more maneuver times and evaluating the pre / post-maneuver orbital parameters determined by the system for a given maneuver time, e.g., based on auxiliary data (e.g., residual characteristics of a pre / post- maneuver orbital parameter) generated by the system during the process.

[0151] In some embodiments, a maneuver determination process or algorithm may comprise identification of a maneuver (e.g. maneuver 1090) by estimating a maneuver time or a maneuver period during which the maneuver is performed. In some cases, the maneuver time or the maneuver period may be estimated by the user, e.g., using the visualization display 102, or automatically by the system 100. In some cases, the maneuver 1090 may generally be difficult to detect by a user for a number of reasons. For example, photographic and / or other tracking data may not be available for a corresponding orbital object during maneuver 1090. Additionally, or alternatively, details of the orbital object may be incomplete during maneuver 1090. In some such cases, the maneuver time or period may be estimated by the system 100. In some implementations, the system may automatically identify the two orbits 1086, 1088 or receive a user selection of the two orbits 1086, 1088 and thus identify the intervening maneuver 1090. In this way, the system can automatically direct a user to find the maneuver 1090 within the user interface. The system may indicate or highlight the maneuver 1090 by, for example, displaying it using a different aspect (e.g., color, dot shape, shading, line dashing, etc.) from one or more of the initial orbit 1086 and / or the final orbit 1088.Single-maneuver determination process: cold start

[0152] In some cases, the maneuver determination process may comprise a cold start maneuver determination process for a single maneuver, herein referred to as singlemaneuver cold start process. In some embodiments the single-maneuver cold start process may comprise determining or receiving an estimated maneuver time, determining a pre-maneuver orbital parameter using identifiers associated with a time before the estimated maneuver time, and independently determining a post-maneuver orbital parameter using identifiers associated with a time after the estimated maneuver time. Additionally, the single-maneuver cold startprocess may comprise determining statistical characteristics (e.g., a covariant matrix) of the pre-maneuver orbital parameter and the post-maneuver orbital parameter, independent from each other.

[0153] FIG. 6A schematically illustrates an example of an orbit determined for a selected orbital object within a time window without considering a maneuver performed by the orbital object within the time window. In some examples, the longitude-time graph 604 shown in FIG. 6A may be displayed by the visualization display 102 and may comprise orbital object data received within a time interval between Tmin 304 and Tmax308 selected by the user. In some cases, the system 100 may display orbital object data (e.g., a plurality of longitude-time points) associated with multiple data objects on the longitude-time graph 604 and the user may select longitude- time points 551 (e.g., a track) associated with an orbital object. In some embodiments, may identify and manually select longitude-time points 551 points associated with the orbital object, e.g., using the identifiers associated with the longitude-time points 551.

[0154] In some embodiments, may the system 100 may assist the user with longitude-time points 551 associated with the orbital object via an automated or semiautomated process. Example methods for identifying and selecting the data points associated with an orbital object are described in U.S. patent No. 10467783 titled: Visualization Interfaces for Real-time Identification, Tracking, and Prediction of Space Objects, issued on November 5th, 2019, and U.S. patent No. 10976911 titled: Systems and Visualization Interfaces for Orbital Paths and Path Parameters of Space Objects, issued on April 13th, 2021, which are incorporated in its entirety by reference herein.

[0155] As described above, in some embodiments, the user may set the lower-time limit Tmin 304 and / or the upper-time limit Tmax 308 by panning and or zooming the first time-axis 220 or the second time-axis 244. Similarly, the user may set the lower-longitude limit 312 and the upper-longitude limit 316 by panning and or zooming the first time-axis 220 or the second time-axis 244. In some examples, in response to receiving the Tmin and Tmax from the user the system 100 may limit the data points (e.g., the longitude- time points) used for various calculation and processes (e.g., for determining orbital parameters for a selected orbital object), to the data points having time identifiers between Tmin and Tmax (e.g., the displayed data). For example, to determine an orbital parameter and / or maneuver determination for a selected orbital object within a specified time window, the user adjust Tmin and Tmax, e.g.,by panning and or zooming, to limit the data points used for orbital parameter and / or maneuver determination to the data points having time identifiers within the specified time window.

[0156] In some cases, the user selection can be based on a set of identifiers for the displayed orbital object data associated with the orbital object. In some cases, the user or system 100 may not identify a maneuver based on the longitude-time points 551 (e.g., a track) associated with the selected orbital object. In some such cases, the system 100 may automatically, or in response to a user command, determine an orbit 557 for the selected orbital object based on the longitude- time points 551 extending between Tmin 304 and Tmax308.

[0157] In some cases, system 100 may determine auxiliary data comprising of residual values indicative of differences between the determined orbit 557 and corresponding data points and display at least a portion of the auxiliary data to the user via the scalar-time graph 208 (inset of FIG. 6A). In some examples, when the selected orbital object has performed a maneuver during a maneuver period 553 between Tmin 304 and Tmax 308, the peak or mean values of the determined residual values associated with a portion of the determined orbit after the maneuver period 553 may deviate from the corresponding values before the maneuver period 553.

[0158] n some cases, the user or the system 100 may activate a maneuver determination mode and determine pre / post-maneuver orbital paths for the selected longitudetime points 551. For example, in response to observing or detecting the deviation in the residual values (shown in the inset of FIG. 6A), the user or the system 100, may activate a maneuver determination mode to take into account a possible maneuver during orbit determination. Alternatively or additionally, the user or the system 100 may activate a maneuver determination mode based on an anomalous or unexpected a behavior of the longitude-time points 551 (e.g., a sudden or unexpected change in latitude or longitude of the object based on the corresponding longitude-time points).

[0159] FIG. 6B schematically illustrates an example pre-maneuver orbital path 557a and a corresponding post-maneuver orbital path 557b determined for the selected orbital object data and time window shown in FIG. 6A using a single-maneuver cold start process and an estimated maneuver time provided by a user or determined by the system. In the example shown, longitude-time graph 605 comprises the user selected longitude-time points 551 (associated with the selected orbital object), the determined pre-maneuver and post-maneuverorbits 557a, 557b, for the orbital object, and the updated scalar-time graph 208 based on an estimated maneuver time Tmprovided by the user or determined by the system. In some cases, the estimated maneuver time Tmcan be within the maneuver period 553 during which the maneuver has been performed.

[0160] In some cases, the user or the system 100 may select the estimated maneuver time Tmbased on one or both the behavior of the longitude-time points 551 and previously calculated residual values (e.g., without considering the maneuver).

[0161] In various implementations, the user may provide the estimated maneuver time Tmvia a user interface of the system 100. In some embodiments, the orbital visualization and computing system 100 may generate a time slider on the longitude-time graph 605 and the user may use the time slider to provide the estimated maneuver time Tm(e.g., by adjusting the position of the time slider between Tmin 304 and Tmax308.)

[0162] In some embodiments, providing Tmmay comprise selection of first and second pluralities of longitude-time points of the longitude-time points displayed on the display interface, e.g., by dividing the longitude-time graph into a first time period (Tip) and a second time period (TzP), where the second time period includes longitude-time points having time identifiers indicative of times after those associated with the longitude-time points in the second time period.

[0163] In some cases, selection of the first and second pluralities of longitude-time points by the user may comprise selection a first portion of identifiers associated with the first plurality of longitude-time points and a second portion of identifiers associated with the second pluralities of longitude-time points. In embodiments, a portion of identifiers associated with a plurality of longitude-time points may comprise a plurality of identifier sets, where an individual identifier set comprises one or more of a name identifier, a time identifier, a latitude identifier, a longitude identifier, an azimuth & elevation identifier, a right ascension identifier, and a declination identifier. In some such cases, the corresponding plurality of longitude-time points may comprise at least the time identifiers and longitude identifiers of the plurality of identifiers.

[0164] In some embodiments, the first time period (Tip) may comprise a premaneuver period and the second time period (T2P) may comprise a post-maneuver time period.-M-

[0165] In some embodiments, when the cold start single-maneuver determination process is activated, after receiving or determining Tm, the system 100 may determine a premaneuver orbital parameter based on a first portion of identifiers associated with the first plurality of longitude-time points and a post-maneuver orbital parameter based on a second portion of the identifiers associated with the second plurality of longitude-time points. Additionally, in some cases, the system 100 may determine statistical characteristics (e.g., a covariant matrix) for the pre-maneuver orbital parameter and the post-maneuver orbital parameter.

[0166] In some embodiments, system 100 may determine first auxiliary data using the pre-maneuver orbital parameter and second auxiliary data using the post-maneuver orbital parameter. In some embodiments, the system 100 may determine the first auxiliary data based on one or both reference orbital object data and the first portion of identifiers and determine the second auxiliary data based one or both reference orbital object data and the second portion of identifiers. In some embodiments, the first auxiliary data may comprise a residual characteristic of the pre-maneuver orbital parameter with respect to one or both of the reference orbital object data and the first portion of identifiers. In some embodiments, the second auxiliary data may comprise a residual characteristic of the post-maneuver orbital parameter with respect to one or both of the reference orbital object data and the second portion of identifiers.

[0167] In some implementations, the pre-maneuver orbital parameter may comprise a pre-maneuver orbital path 557a, the post-maneuver orbital parameter may comprise a post-maneuver orbital path 557b, the reference orbital object data may comprise reference orbital path data from an orbital path data set, where the reference orbital path data comprises a first plurality of reference orbital paths associated with the orbital object. In various implementations, the first plurality of reference orbital paths may span one or both of the premaneuver time period (Tip) and the post-maneuver time period (Tip).

[0168] In some embodiments, the first auxiliary data may comprise a statistical characteristic of the pre-maneuver orbital parameter and the second auxiliary data may comprise a statistical characteristic of the post-maneuver orbital parameter. In some examples, the first auxiliary data may comprise a first covariant matrix determined for the pre-maneuver orbital parameter (e.g., a pre-maneuver orbital path) and the second auxiliary data maycomprise a second covariant matrix determined for the pre-maneuver orbital parameter (e.g., a post-maneuver orbital path).

[0169] In some cases, the first auxiliary data may comprise a first portion of residual values indicative of a difference between the first portion of identifiers and the premaneuver orbital path 557a, and the second auxiliary data may comprise a second portion of residual values indicative of differences between the reference orbital path and the first and second portions of the identifiers, respectively.

[0170] In some cases, the first auxiliary data may comprise first and second of residual values indicative of a difference between the first portion of identifiers and the premaneuver orbital path 557a, and the second auxiliary data may comprise a second portion of residual values indicative of difference between the second portion of identifiers and the postmaneuver orbital path 558a.

[0171] In some examples, system 100 may display the first portion of residual values 554a in a first section of the scalar-time graph 208 and the second portion of residual values 554b in a second section of the scalar-time graph 208, where the first and sections are non- overlapping sections associated with the pre- and post-maneuver periods, Tip, TzP, respectively. In some examples, the scalar-time graph 208 may comprise a scalar axis 248 spanning from a lower-scalar limit to an upper-scalar limit associated with lower and upper bounds of the determined residual values and a time-axis 244 spanning from a Tmin to Tmax. In some cases, the first and second portions of residual values 556a, 556b, may comprise a plurality of pixels where individual ones of pixels corresponds to a pair of identifiers having a time identifier between Tmin to Tmaxand the second upper-time limit and having a scalar identifier with lower and upper bounds of the determined residual values.

[0172] In some examples, system 100 may indicate first and second sections of the scalar-time graph 208 associated with pre- and post-maneuver time periods by generating the tracking line 260.Single-maneuver determination process: warm start

[0173] In some cases, the maneuver determination process may comprise a warm start maneuver determination process for a single maneuver, herein referred to as singlemaneuver warm start process. In some embodiments the single-maneuver warm start processmay comprise determining or receiving an estimated maneuver time, determining a premaneuver orbital parameter using identifiers associated with times (including time identifiers) before the estimated maneuver time, and determining a post-maneuver orbital parameter using identifiers associated with times after the estimated maneuver time and the pre-maneuver orbital parameter. Additionally, the single-maneuver warm start process may comprise determining a statistical characteristic (e.g., a covariant matrix) of the pre-maneuver orbital parameter and determining one or both the post-maneuver orbital parameter and a statistical characteristic (e.g., a covariant matrix) of the post-maneuver orbital parameter based at least in part on the determined statistical characteristic of the pre-maneuver orbital parameter.

[0174] Advantageously, by determining the post-maneuver parameter of the orbital object based on the determined pre-maneuver orbital parameter of the orbital object at or closely before the maneuver time period, the system may determine the post-maneuver orbital parameter using a small number of data points (longitude- time points) or data points associated with a short period after the maneuver time compared to the single-parameter cold start process (also referred to as initial orbit determination, IOD) described above (where post and premaneuver orbital parameters are determined independent of each other, based on the orbital object data associated with periods before and after the maneuver time, respectively). As such, a user may detect and characterize a maneuver shortly after the maneuver is performed. Further, determining the post-maneuver parameter of the orbital object determined based on the determined pre-maneuver orbital parameter, may improve the accuracy of the determined post-maneuver parameter compared to the single-maneuver cold start process. In some embodiments, the single-maneuver warm start process may determine the post-maneuver parameter with the same accuracy and / or level of uncertainty as the single-maneuver cold start process, with smaller number of post-maneuver data points. In other words, the warm start mode can reduce the number of post-maneuver data used for determining a post maneuver parameter with a given level of uncertainty. In various implementations, the uncertainty of the determined post maneuver parameter may comprise a level of residual(s), a variance, or another parameter or set parameters (e.g., a statistical parameter or a covariance matrix) that may quantify precision of the determined post maneuver parameter and / or the deviation of the determined post maneuver parameter from the corresponding post maneuver data points received from the orbital object data interface 185. In some cases, the residual(s) may comprisedifference between the orbital path and the data points (e.g., longitude-time points) associated with a time interval extending from pre-maneuver time period to the post-maneuver time period.

[0175] In some embodiments, the system 100 may modify the pre-maneuver uncertainty parameter and determine one or both the post-maneuver parameter and the postmaneuver uncertainty parameter based at least in part on the pre-maneuver parameter and the modified pre-maneuver uncertainty parameter.

[0176] In some implementations, the single-maneuver warm start process performed by the system 100 may allow a user to determine a post-maneuver orbital parameter (e.g., a post-maneuver orbital path) of an orbital object, using orbital object data collected in less than 1 hour, less than 30 minutes, less than 10 minutes, less than 5 minutes after the maneuver is performed. In contrast, in some cases, to determine the post-maneuver orbital parameter of the orbital object using the cold start maneuver determination process, the system may use orbital object data collected in more than 1 hour, more than 2 hours, more than 5 hours, or more than 10 hours after the maneuver is performed.

[0177] FIG. 7 schematically illustrates an example pre-maneuver orbital path 558a and a corresponding post-maneuver orbital path 558b determined for the selected orbital object data and time window shown in FIG. 6 A using a single-maneuver warm start process and an estimated maneuver time Tmprovided by a user or determined by the system. In some examples, the longitude-time graph 704 shown in FIG. 7 may comprise one or more features described above with respect to the longitude-time graph 605 shown in FIG. 6B. In some cases, the longitude-time graph 704 shown in FIG. 7 may comprise orbital object data 551 associated with an orbital object received within a time interval between Tmin 304 and Tmax308. In some examples, the orbital object, Tmin 304 and Tmax 308 can be selected by a user.

[0178] In some embodiments, the user may activate a maneuver determination mode of the system and initiate the single-maneuver warm start process for the orbital object associated with the selected of longitude-time points (e.g., a track) 551, at least partially, by providing an estimated maneuver time (Tm) 552 indicative of a maneuver time or maneuver time period corresponding to a maneuver performed by the orbital object.

[0179] In some examples, the user or the system may select a time window by providing or determining Tmin 304 and Tmax 308. In some such examples, Tmcan be within the time window.

[0180] In some embodiments, in response to receiving or determining the estimated Tm, the system 100 may divide the data points (e.g., longitude-time points) within the time window (e.g., between Tmin 304 and Tmax) into a first plurality of data points having time identifiers before Tmand a second plurality of data points having time identifiers after Tm.

[0181] In some embodiments, the orbital visualization and computing system 100 may generate a time slider 550 on the longitude-time graph 704 and the user may use the time slider 550 to provide the estimated maneuver time using the time slider 550.

[0182] In some embodiments, the time slider 550 may be configured to allow selection of the first and second pluralities of longitude-time points of the longitude-time points displayed on the display interface, e.g., by dividing the longitude-time graph into a first time period region (Tip) extending from Tmin to Tmand a second time period (T p) extending from TmtO Tmax.

[0183] In some embodiments, the time slider 550 may comprise a line substantially parallel to the latitude axis 224 indicating the pre-maneuver and the post-maneuver periods. In some such embodiments, time slider 550 may travers at least part of the longitude-time graph 704 and can be configured to separate the first and second pluralities of longitude-time points. In some embodiments, the system may receive the position of the time slider 550 along the time-axis as the estimate maneuver time (Tm).

[0184] In response to receiving Tm, the system 100 may determine pre-maneuver orbital parameter and a corresponding pre-maneuver uncertainty parameter based on the first portion of identifiers associated with the first plurality of longitude-time data points in the premaneuver period (Tip) and determine one or both a post-maneuver orbital parameter and a corresponding post-maneuver uncertainty parameter based at least in part on the determined pre-maneuver orbital parameter and the second portion of identifiers associated with the second plurality of longitude-time data points in the post-maneuver period (T2P). In some cases, the system 100 may determine the post-maneuver orbital parameter based at least in part the pre-maneuver uncertainty parameter.

[0185] In some embodiments, the system 100 may determine or estimate a maneuver characterization parameter based at least in part on one or both the pre-maneuver orbital parameter and the post-maneuver orbital parameter. In some cases, the system 100 may determine the maneuver characterization parameter based at least in part on one or both the pre-maneuver uncertainty parameter and the post-maneuver uncertainty parameter. In some such embodiments, the maneuver characterization parameter may comprise a maneuver initiating time (herein referred to as maneuver time), a maneuver time period 553, a velocity change during the maneuver time period 553, a maneuver sequence, or another parameter characterizing the maneuver.

[0186] In various implementations, when the single-maneuver warm start process is used, the post-maneuver period (TzP) can be less than 1 hour, less than 30 minutes, less than 10 minutes, less than 5 minutes.

[0187] In some embodiments, e.g., when the system 100 is operated in an automatic maneuver determination mode, at least a portion of the procedures described above with respect to FIGS 6A-6B and 7 associated with the user interaction with the system 100 (e.g., providing the estimated maneuver times) may be performed by the system 100. In these embodiments, system 100 may determine one or more of estimated maneuver time and pre / post-maneuver parameters, using an autonomous or semi-autonomous process.

[0188] In some embodiments, the maneuver detection and characterization process described above with respect to FIGS 6A-6B and 7 based on longitude-time data points displayed on the longitude-time graphs 604, 605, and 704 may be performed based on latitudelongitude data points displayed on the longitude-latitude graph 212.Warm multi-maneuver determination process

[0189] In some embodiments, the single-maneuver warm start and cold start processes may be used to determine post-maneuver parameters for two or more maneuvers performed by an orbital object at different times.

[0190] In some embodiments, when a single-maneuver determination process is used for determining two different maneuvers performed by the same object, the system 100 may determine first pre / post-maneuver parameters for a first maneuver and independently a second pre / post-maneuver parameters for a second maneuver performed after the firstmaneuver. As such, in some cases, determining multiple maneuvers performed by an orbital object may comprise performing multiple single-maneuver cold start or warm start processes independent of each other.

[0191] In contrast, in some embodiments, determining multiple maneuvers performed by an orbital object may comprise determining a maneuver of a plurality of maneuvers, based at least in part on one or more determined maneuvers performed by the orbital object prior to the maneuver. In some cases, such maneuver determination process may be referred to as a multi-maneuver warm start process. In some embodiments, a first maneuver of the plurality of maneuvers performed by an orbital object may be determined using the single-maneuver warm start process described above with respect to FIG. 7 and a subsequent maneuver may be determined based at least in part on post / pre-maneuver parameters determined for maneuvers performed before the maneuver. In some such embodiments, the subsequent maneuver may be determined based at least in part on post / pre-maneuver uncertainty parameters determined for maneuvers performed before the maneuver. For example, when a multi-maneuver warm start process is used for determining two maneuvers, the system 100 may use the single-maneuver warm start process to determine first pre / post- maneuver parameters and, in some cases, first pre / post-maneuver uncertainty parameters for a first maneuver, and use one or both pre / post-maneuver parameters and pre / post-maneuver uncertainty parameters to determine, one or both second pre / post-maneuver parameters and second pre / post-maneuver uncertainty parameters for a second maneuver performed after the first maneuver by the orbital object.

[0192] In some embodiments, the multi-maneuver warm start process may comprise determining one or of a second pre-maneuver orbital parameter, second postmaneuver orbital parameter, second pre-maneuver uncertainty parameter, and second postmaneuver uncertainty parameter, for a second maneuver performed by an orbital object based at least in part on one or of a first pre-maneuver orbital parameter, first post-maneuver orbital parameter, first pre-maneuver uncertainty parameter, and first post-maneuver uncertainty parameter, determined for a first maneuver performed by the orbital object. Advantageously, the multi-maneuver warm start process the system 100 may determine the second postmaneuver orbital parameter and the second post-maneuver uncertainty parameter using a smaller number of post-maneuver data points or longitude-time points having time identifiersafter an estimated maneuver time received determined for the second maneuver compared to case, where the second maneuver is determined independent of the first maneuver. As such, a user may detect and characterize multiple maneuvers using data collected shortly after each maneuver is performed. Further, determining the second maneuver based on the determined first maneuver may improve the accuracy of the parameters determined for the second maneuver.

[0193] In some implementations, the multi-maneuver warm start process performed by the system 100 may allow a user to determine a parameter of the second maneuver (e.g„ a post-maneuver orbital parameter) of an orbital object, using orbital object data collected in less than 1 hour, less than 30 minutes, less than 10 minutes, less than 5 minutes after the second maneuver is performed.

[0194] FIG. 8A illustrates an example of multiple pre-maneuver and postmaneuver orbits determined for a selected orbital object using a multi-maneuver warm start process. In some examples, the longitude-time graph 204 shown in FIG. 8A may comprise one or more features described above with respect to the longitude-time graph 204 shown in FIG. 6B. In some cases, the longitude-time graph 204 shown in FIG. 8 A may comprise orbital object data (the black dots) associated an orbital object received within a time interval defined by the lower and upper time limits Tniin304, and Tmax308. In some cases, after activating the warm start maneuver determination mode, the user may provide a first time window Ti and a first estimated maneuver time Tmiindicative of a first maneuver performed by the orbital object within the first time window Ti to divide Ti to first pre-maneuver and post-maneuver periods Tia , Tib. In some embodiments, the user may provide the first time window TI by zooming the time axis 220 to a first Tminl and a first Tmaxl, where Tmaxl-Tminl=Tl, and provide the first estimated maneuver time Tmiby adjusting the time slider 550 within TI.

[0195] In some embodiments, the system may use a single-maneuver warm start process to determine a first post maneuver orbital parameter (e.g., a first orbital path 802b) and, in some cases, a corresponding first post maneuver uncertainty parameter, using the orbital object data received during the first pre-maneuver and post-maneuver periods Tia, Tib. In some cases, the system 100 may determine a first maneuver characterization parameter based at least in part on the first pre-maneuver orbital parameter and the first post-maneuver orbital parameter.

[0196] Next, the user may provide a second time window T2 and a second estimated maneuver time Tm2 indicative of a second maneuver performed by the orbital object within the second time window T2 to divide T2 to second pre-maneuver and post-maneuver periods T2a, T2b. In some cases, T2 can be immediately after Ti. In some embodiments, the user may provide the second time window T2 by zooming the time axis 220 to a second Tmin2 and a second Tmax2, where Tmax2-Tmin2=T2, and provide the second estimated maneuver time Tm2 by adjusting the time slider 550 within T2.

[0197] In some embodiments, the system may determine a second post-maneuver orbital parameter (e.g., a second orbital path 802d) and, in some cases, a corresponding second post-maneuver uncertainty parameter, by determining a second pre-maneuver orbital parameter and, in some cases, a second pre-maneuver uncertainty parameter, using the orbital object data received during the second pre / post-maneuver periods T2a, T2b, and additionally one or more of a first pre-maneuver orbital parameter (e.g., a first orbital path 802a), first postmaneuver orbital parameter (e.g., a first orbital path 802b) and. in some cases, the first postmaneuver uncertainty, and the first post-maneuver uncertainty, determined for the first maneuver performed during Ti. In some cases, the system 100 may determine a second maneuver characterization parameter based at least in part on the second pre-maneuver orbital parameter and the second post-maneuver orbital parameter.

[0198] In some embodiments, the user may provide a third time window T3 after the first and second time windows and a third estimated maneuver time Tm3 indicative of a third maneuver performed by the orbital object within the third time window T3 to divide T3 to pre-maneuver and post-maneuver periods T3a, T3b. In some embodiments, the user may provide the third time window T3 by zooming the time axis 220 to a third Tmin3 and a third Tmax3, where Tmax3-Tmin3=T3, and provide the third estimated maneuver time Tm3 by adjusting the time slider 550 within T3.

[0199] In some embodiments, the system may determine a third post-maneuver orbital parameter (e.g., a second orbital path 802f) and, in some cases, a corresponding third post-maneuver uncertainty parameter, by determining a third pre-maneuver orbital parameter (e.g., a first orbital path 802e) and, in some cases, a third pre-maneuver uncertainty parameter, using the orbital object data received during the third pre / post-maneuver periods T2a, T2b, and additionally one or more of a pre-maneuver orbital parameter (e.g., first or second orbital paths802a, 802c), a post-maneuver orbital parameter (e.g., first or second orbital paths 802b, 802d), a pre-maneuver uncertainty parameter, and a post-maneuver uncertainty parameter determined for one or more maneuvers performed by the orbital object before the third time window T3. In some cases, the system 100 may determine a third maneuver characterization parameter based at least in part on the third pre-maneuver orbital parameter and the third post-maneuver orbital parameter.

[0200] In some embodiments, after determining the first, second, and third maneuvers, the user may adjust Tmin and Tmax to display the longitude-time points and determined orbital parameters (e.g., orbital paths) associated with the first, second, and third Tl, T2, and T3 time windows in a single longitude- time graph a shown in FIG. 8A.

[0201] In various embodiments, the user may use other methods for selecting a time window and proving the estimated maneuver time. For example, in some cases, the user may provide Tmin, Tmax, and Tmvia a text based used interface. In some examples, the user may select the pre-maneuver longitude-time points and post-maneuver longitude-time points on the longitude-time graph 204 by manually selecting using an input device (e.g., using a computer mouse).

[0202] Example methods for selecting and displaying longitude-time points and determining maneuvers for different time windows and displaying multiple determined maneuvers on a single display are described in U.S. patent No. 10976911 titled: Systems and Visualization Interfaces for Orbital Paths and Path Parameters of Space Objects, issued on April 13th, 2021, which is incorporated in its entirety by reference herein.

[0203] FIG. 8B is a flow diagram illustrating an example multi-maneuver warm start process 800 performed by a processor of system 100.

[0204] The process 800 begins at block 802 where system 100 receives a selection of orbital object data from a user. In some examples, the user may select one or more orbital object data sources from orbital object data sources 155. In some examples, the user may further provide lower and upper time limits upload a portion of orbital object data to system 100. In some examples, system 100 may receive orbital object data from the selected orbital object data sources via the orbital object data interface 185, upload at least a portion of the orbital object data received from the selected data sources and display the uploaded portion of the orbital object data in the visual display 102. In some examples, the uploaded portion of theorbital object data, herein referred to as uploaded orbital object data, may comprise observations collected during between the lower and upper time limits.

[0205] At block 804, system 100 may receive a selection of an orbital object from the user. In some examples, the user may select the orbital object using visual display 102, e.g., by selecting a plurality of longitude-time data points as described above with respect to FIG. 7. In some examples, in response to the selection of the orbital object, system 100 may use a portion of the uploaded orbital object data associated with the selected orbital object, herein referred to as active orbital object data, in the subsequent steps of the multi-maneuver warm start process.

[0206] At block 806, system 100 may receive a first time window comprising a first lower time limit and a first upper time limit from the user indicating a first portion of the active orbital object data. In some embodiments, the user may select the first time window by adjusting the lower and upper time limits Tmin 304 and Tmax 308, in the longitude-time display 204.

[0207] At block 808, system 100 may receive a first estimated maneuver time Timfrom the user indicative of a maneuver performed within the first time window. In some embodiments, the system may provide the time slider 550a in the longitude-time graph 204, and the user may select the first estimate maneuver time Timby adjusting the time slider 550.

[0208] At block 810, system 100 may divide the portion of active orbital object data displayed in the longitude-time display 204 to first pre-maneuver and first post-maneuver orbital object data associated with observations collected before and after the first estimated maneuver time Timand determine a first pre-maneuver orbital parameter and a first postmaneuver orbital parameter. Additionally, in some cases, the system 100 may determine a first pre-maneuver uncertainty parameter and a first post-maneuver uncertainty parameter. In some cases, system 100 may determine the first pre-maneuver orbital parameter and the first premaneuver uncertainty parameter using the pre-maneuver orbital object data. In some embodiments, system 100 may determine the first port-maneuver orbital parameter and the first post-maneuver uncertainty parameter using the cold start process described above with respect to FIG. 6B. For example, system 100 may determine the first port-maneuver orbital parameter and the first post-maneuver uncertainty parameter using the post-maneuver orbital object data. In some embodiments, system 100 may determine the first port-maneuver orbitalparameter and the first post-maneuver uncertainty parameter using the single-maneuver warm start process described above with respect to FIG. 7. For example, system 100 may determine the first port-maneuver orbital parameter and the first post-maneuver uncertainty parameter using the post-maneuver orbital object data and additionally the determined first pre-maneuver orbital parameter and the first pre-maneuver uncertainty parameter.

[0209] At block 812, system 100 may receive a second time window comprising a second lower time limit and a second upper time limit from the user indicating a second portion of the active orbital object data. In some embodiments, the user may select the second time window by adjusting the lower and upper time limits Tmin 304 and Tmax 308, in the longitudetime display 204.

[0210] At block 814, system 100 may receive a second estimated maneuver time T2m from the user indicative of a maneuver performed within the second time window. In some embodiments, the system may provide the time slider 550a in the longitude- time graph 204, and the user may select the first estimate maneuver time Tzm by adjusting the time slider 550.

[0211] At block 816, system 100 may divide the portion of active orbital object data displayed in the longitude-time display 204 to second pre-maneuver and second postmaneuver orbital object data associated with observations collected before and after the first estimated maneuver time Timand determine a second pre-maneuver orbital parameter and a second post-maneuver orbital parameter. Additionally, in some cases, the system 100 may determine a second pre-maneuver uncertainty parameter and a second post-maneuver uncertainty parameter. In some cases, system 100 may determine the second pre-maneuver orbital parameter and the second pre-maneuver uncertainty parameter using the pre-maneuver orbital object data. In some embodiments, system 100 may determine the second portmaneuver orbital parameter and the second post-maneuver uncertainty parameter using the cold start process described above with respect to FIG. 6B. For example, system 100 may determine the second port-maneuver orbital parameter and the second post-maneuver uncertainty parameter using the post-maneuver orbital object data. In some embodiments, system 100 may determine the second port-maneuver orbital parameter and the second postmaneuver uncertainty parameter using the single-maneuver warm start process described above with respect to FIG. 7. For example, system 100 may determine the second portmaneuver orbital parameter and the second post-maneuver uncertainty parameter using thepost-maneuver orbital object data and additionally the determined second pre-maneuver orbital parameter and the second pre-maneuver uncertainty parameter.Example Embodiments

[0212] In a 1st Example, a system is disclosed for determining and transmitting a post-maneuver orbital parameter of an orbital object: an orbital object data interface configured to receive orbital object data from an orbital object data source covering at least a selected time period, the orbital object data comprising identifiers corresponding to the orbital object; a non- transitory computer-readable storage storing instructions that are machine-executable; and a hardware processor in communication with the non-transitory computer-readable storage, wherein the instructions, when executed by the hardware processor, cause the system to: receive the identifiers; receive a lower- time limit and an upper-time limit within the selected time period; generate a display interface comprising: a longitude-time graph comprising: a longitude axis spanning from a lower-longitude limit to an upper-longitude limit; and a timeaxis spanning from the lower-time limit to the upper-time limit; generate data for displaying a plurality of longitude-time points based on the identifiers; determine an estimated maneuver time indicating a boundary dividing the plurality of longitude-time points into a pre-maneuver plurality of longitude-time points and a post-maneuver plurality of longitude-time points, wherein the pre-maneuver plurality of longitude-time points represents a pre-maneuver time period before the estimated maneuver time, and the post-maneuver plurality of longitude-time points represents a post-maneuver time period after the estimated maneuver time; determine a pre-maneuver orbital parameter using a first portion of the identifiers associated with the premaneuver plurality of longitude-time points; determine the post-maneuver orbital parameter using at least the pre-maneuver orbital parameter and a second portion of the identifiers associated with the post-maneuver plurality of longitude-time points; and transmit the determined post-maneuver orbital parameter.

[0213] In a 2nd Example, The system of Example 1, wherein execution of the instructions by the hardware processor further causes the system to: receive a second lowertime limit and a second upper-time limit within the selected time period; generate a second display interface comprising: a second longitude-time graph comprising: a second longitude axis spanning from a lower-longitude limit to an upper-longitude limit; and a second time-axisspanning from the lower-time limit to the upper-time limit; generate data for displaying a second plurality of longitude-time points based on the identifiers; determine a second estimated maneuver time indicating a boundary dividing the second plurality of longitude-time points into a second pre-maneuver plurality of longitude-time points and a second post-maneuver plurality of longitude-time points, wherein the second pre-maneuver plurality of longitudetime points represents a pre-maneuver time period before the second estimated maneuver time , and the second post-maneuver plurality of longitude-time points represents a second postmaneuver time period after the second estimated maneuver time; determine a second premaneuver orbital parameter using identifiers associated with the pre-maneuver plurality of longitude-time points; determine a second post-maneuver orbital parameter using at least one or both the pre-maneuver orbital parameter and the post-maneuver orbital parameter; and transmit the determined second post-maneuver orbital parameter.

[0214] In a 3rd Example, the system of Example 2, wherein execution of the instructions by the hardware processor further causes the system to determine the second postmaneuver orbital parameter using the second pre-maneuver orbital parameter and a portion of the identifiers associated with the second post-maneuver plurality of longitude-time points.

[0215] In a 4th Example, the system of any of any of Examples 1-3, wherein execution of the instructions by the hardware processor further causes the system to determine a maneuver characterization parameter using the pre-maneuver orbital parameter and the postmaneuver orbital parameter and transmit the maneuver characterization parameter.

[0216] In a 5th Example, the system of any of any of Examples 1-4, wherein the pre-maneuver orbital parameter comprises a pre-maneuver orbital path of the orbital object before the estimated maneuver time and the post-maneuver orbital parameter comprises a postmaneuver orbital path of the orbital object after the estimated maneuver time.

[0217] In a 6th Example, the system of any of any of Examples 1-5, wherein the pre-maneuver orbital parameter comprises a velocity of the orbital object.

[0218] In a 7th Example, the system of any of any of Examples 4-6, wherein the maneuver characterization parameter comprises one or more of characteristics of a maneuver or a maneuver sequence, and post-maneuver data.

[0219] In an 8th Example, the system of Example 7, wherein the maneuver characterization parameter comprises a velocity, a velocity change (delta V), or an estimated maneuver time.

[0220] In a 9th Example, the system of any of any of Examples 1-8, wherein the orbital object data comprises observations of the orbital object collected over the selected time period by at least two telescopes.

[0221] In a 10th Example, the system of any of any of Examples 1-9, wherein the identifiers comprise a plurality of identifier sets, each of the plurality of identifier sets comprising: a name identifier; a time identifier; a latitude identifier; a longitude identifier; an azimuth identifier; an elevation identifier; a right ascension identifier; and a declination identifier.

[0222] In a 11th Example, the system of any of any of Examples 1-10, wherein the lower-time limit and the upper-time limit are received from a user via an interaction with the display interface.

[0223] In a 12th Example, the system of any of any of Examples 1-11, wherein at least one of the lower-time limit and the upper-time limit are received from a user via an interaction with the display interface.

[0224] In a 13th Example, the system of Example 12, wherein the interaction with the display interface comprises one or both of panning and zooming of one or both of the timeaxis and the longitude axis.

[0225] In a 14th Example, the system of any of any of Examples 1-13, wherein the instructions, when executed by the hardware processor, cause the system to receive the identifiers in response to user selection of the orbital object via the display interface.

[0226] In a 15th Example, the system of Example 14, wherein the user selection of the orbital object comprises one or both of panning and zooming of one or both of the timeaxis and the longitude axis.

[0227] In a 16th Example, the system of any of Examples 4-15, wherein execution of the instructions by the hardware processor causes the system to transmit the determined maneuver characterization parameter and the determined post-maneuver orbital parameter to a computing system.

[0228] In a 17th Example, the system of any of Examples 4-16, wherein execution of the instructions by the hardware processor causes the system to transmit the determined maneuver characterization parameter and the determined post-maneuver orbital parameter to a data store for storage.

[0229] In an 18th Example, the system of any of Examples 4-17, wherein execution of the instructions by the hardware processor causes the system to transmit the determined maneuver characterization parameter and the determined post-maneuver orbital parameter to the display interface.

[0230] In a 19th Example, the system of any of Examples 1-18, wherein the postmaneuver plurality of longitude-time points corresponds a portion of the orbital object data collected during a time period of 4 hours or less.

[0231] In a 20th Example, the system of Example 19, wherein the time period is 1 hour or less.

[0232] In a 21st Example, the system of Example 20. wherein the time period is 10 minutes or less.

[0233] In a 22nd Example, the system of Example 21, wherein the time period is 1 minute or less.

[0234] In a 23rd Example, the system of any of Examples 1-22, wherein execution of the instructions by the hardware processor causes the system to determine the estimated maneuver time using the identifiers.

[0235] In a 24th Example, the system of any of Examples 1-23, wherein execution of the instructions by the hardware processor causes the system to determine the estimated maneuver time by receiving the estimated maneuver time from a user via a user interface.

[0236] In a 25th Example, the system of Example 24, wherein the user interface comprises the display interface.

[0237] In a 26th Example, the system of any of Examples 10-25, wherein execution of the instructions by the hardware processor causes the system to generate a time slider on the display interface, the time slider configured to allow selection of the pre-maneuver plurality of longitude-time points and the post-maneuver plurality of longitude-time points by dividing the longitude-time graph into pre-maneuver and post-maneuver regions corresponding to premaneuver and post-maneuver time periods, respectively.

[0238] In a 27th Example, the system of Example 26, wherein the time slider comprises a line substantially parallel to the time-axis, the line traversing at least part of the longitude-time graph.

[0239] In a 28th Example, the system of Example 27, wherein determining the estimated maneuver time comprises receiving an adjustment of the time slider by a user.

[0240] In a 29th Example, the system of any of Examples 1-28, wherein the premaneuver plurality of longitude-time points and the post-maneuver plurality of longitude-time points are between the lower-time limit and the upper-time limit.

[0241] In a 30th Example, the system of any of Examples 5-29, wherein the orbital object data interface is further configured to receive reference orbital data associated with the orbital object from a reference orbital data set.

[0242] In a 31st Example, the system of Example 30, wherein the reference orbital data set span one or both of a first time interval before the estimated maneuver time and a second time interval after the estimated maneuver time, and execution of the instructions by the hardware processor causes the system to determine a residual characteristic of one or both of the post-maneuver orbital parameter and the post-maneuver orbital parameter, indicating a difference between one or both the pre-maneuver orbital parameter and the post-maneuver orbital parameter, and corresponding portions of the reference orbital data.

[0243] In a 32nd Example, the system of any of Examples 1-32, wherein execution of the instructions by the hardware processor further causes the system to determine a residual characteristic, indicating differences between one or both the pre-maneuver orbital parameter and the post-maneuver orbital parameter, and portions of the identifiers associated with premaneuver and post-maneuver pluralities of the longitude-time points, respectively.

[0244] In a 33rd Example, the system of Example 32, wherein execution of the instructions by the hardware processor further causes the system to display the residual characteristic via a scalar-time graph in the display interface.

[0245] In a 34th Example, the system of Example 33, wherein the scalar-time graph comprises: a scalar axis spanning from a lower-scalar limit to an upper-scalar limit, a second time-axis spanning from a second lower-time limit to a second upper-time limit; and a plurality of pixels corresponding to scalar-time points within the scalar-time graph, individual ones of the scalar-time points corresponding to a pair of identifiers having a time identifier betweenthe second lower-time limit and the second upper-time limit and having a scalar identifier between the lower-scalar limit and the upper-scalar limit.

[0246] In a 35th Example, the system of Example 34, wherein execution of the instructions by the hardware processor further causes the system to identify a region of the scalar-time graph associated with longitude- time points and corresponding portion of the identifiers used to determined one or both the pre-maneuver orbital parameter and the postmaneuver orbital parameter.

[0247] In a 36th Example, the system of Example 35, wherein the system is configured to identify the region by highlighting corresponding scalar-time points or adding a background shading to the region.

[0248] In a 37th Example, the system of any of Examples 34-36, wherein execution of the instructions by the hardware processor further causes the scalar-time graph to be synchronously updated with respect to the longitude- time graph and a user selection of a longitude-time point.

[0249] In a 38th Example, the system of any of Examples 1-37, wherein the display interface further comprises a longitude-latitude graph comprising: a second longitude axis spanning from a second lower-longitude limit to a second upper-longitude limit; a latitude axis spanning from a lower-latitude limit to an upper-latitude limit; and a plurality of pixels corresponding to longitude-latitude points within the longitude-latitude graph, each of the longitude-latitude points corresponding to identifiers of a set of identifiers comprising a latitude identifier between the lower-latitude limit and the upper-latitude limit and having a longitude identifier between the second lower-longitude limit and the second upper-longitude limit.

[0250] In a 39th Example, the system of Example 38, wherein execution of the instructions by the hardware processor further causes the longitude-latitude graph to be synchronously updated with respect to the longitude-time graph and a user selection of a longitude-time point.

[0251] In a 40th Example, the system of any of Examples 1-39, wherein the display interface further comprises a scalar-time graph comprising: a scalar axis spanning from a lower-scalar limit to an upper-scalar limit, a second time-axis spanning from a second lowertime limit to a second upper-time limit; and a plurality of pixels corresponding to scalar-timepoints within the scalar-time graph, each of the scalar-time points corresponding to a set of identifiers including a time identifier between the second lower-time limit and the second upper-time limit and having a scalar identifier between the lower-scalar limit and the upperscalar limit.

[0252] In a 41st Example, the system of Example 40, wherein execution of the instructions by the hardware processor causes the system to provide an indication of longitudetime points associated with the identifiers used to determine the scalar identifier.

[0253] In a 42nd Example, the system of Example 41, wherein the indication comprises a shaded or highlighted region of the scalar-time graph corresponding to the longitude-time points associated with the identifiers used to determine the scalar identifier.

[0254] In a 43rd Example, the system of any of Examples 1-42, wherein the display interface further comprises an indicator of a current time.

[0255] In a 44th Example, the system of Example 43, wherein the indicator of the current time comprises a line traversing at least part of the longitude-time graph.

[0256] In a 45th Example, the system of any of Examples 9-44, wherein the display interface further comprises a portion of a geographical map indicating locations of a plurality of orbital object data sources on the geographical map.

[0257] In a 46th Example, the system of Example 45, wherein in response to a user selection of one or more longitude-time points, execution of the instructions by the hardware processor causes the system to highlight a location of the orbital object data source of the plurality of orbital object data sources associated with the selected one or more longitude-time points on the geographical map.

[0258] In a 47th Example, the system of Example 46, wherein the orbital object data source comprises one of the at least two telescopes.

[0259] In a 48th Example, the system of any of Examples 1-47, wherein the display interface further comprises an analysis plot comprising: a first scalar axis spanning from a first lower-scalar limit to a first upper-scalar limit, a second scalar axis spanning from a second lower-scalar limit to a second upper-scalar limit; and a plurality of pixels corresponding to analysis points within the analysis plot, individual ones of the analysis points corresponding to a pair of identifiers comprising a first identifier between the first lower-scalar limit to the firstupper-scalar limit and a second identifier between the second lower-scalar limit to the second upper- sc alar limit.

[0260] In a 49th Example, the system of Example 48, wherein the analysis points are associated with one or more longitude-time points.

[0261] In a 50th Example, the system of any of Examples 48-49, wherein execution of the instructions by the hardware processor causes the analysis plot to be synchronously updated with respect to the longitude-time graph and a user selection of a longitude-time point.

[0262] In a 51st Example, the system of any of Examples 48-50, wherein the first identifier comprises absolute visual magnitude (Mv) and the second identifier comprises a solar phase.

[0263] In a 52nd Example, the system of Example 51, wherein execution of the instructions by the hardware processor causes the system to provide a marker on the analysis plot, the marker indicating a value of the first identifier corresponding to a time point selected by a user on the longitude-time graph.

[0264] In a 53rd Example, the system of Example 52, wherein the system synchronously updates the analysis plot by determining the value of the first identifier based at least in part on the time point selected by the user and updating a position of the marker with respect to the first scalar axis.

[0265] In a 54th Example, the system of any of Examples 52-53, wherein the marker comprises a line substantially parallel to the second scalar axis, the line traversing at least part of the analysis plot.

[0266] In a 55th Example, a system is disclosed for determining and transmitting post-maneuver orbital parameters for an orbital object: an orbital object data interface configured to receive orbital object data from an orbital object data source covering at least a selected time period, the orbital object data comprising identifiers corresponding to the orbital object; a non-transitory computer-readable storage storing machine-executable instructions; and a hardware processor in communication with the non-transitory computer- readable storage, wherein the machine-executable instructions, when executed by the hardware processor, cause the system to: receive the identifiers from the orbital object data source via the orbital object data interface; determine a selection of at least some identifiers associated with the orbital object; determine a first time window; determine a first estimated maneuvertime within the first time window; determine a first pre-maneuver orbital parameter based on a first portion of the selection; determine a first post-maneuver orbital parameter based at least in part on the first pre-maneuver orbital parameter and a second portion of the selection; and transmit the first post-maneuver orbital parameter.

[0267] In a 56th Example, the system of Example 55, wherein execution of the machine-executable instructions by the hardware processor further causes the system to determine a first maneuver characterization parameter using the first pre-maneuver orbital parameter and the first post-maneuver orbital parameter.

[0268] In a 57th Example, the system of any of Examples 55-56, wherein execution of the machine-executable instructions by the hardware processor further causes the system to: receive a second time window; receive a second estimated maneuver time within the second time window; determine a second post-maneuver orbital parameter based at least in part on the first post-maneuver orbital parameter and the selected identifiers within the second time window; and transmit the second post-maneuver orbital parameter.

[0269] In a 58th Example, the system of any of Examples 55-57, wherein execution of the machine-executable instructions by the hardware processor causes the system to determine the selection of at least some identifiers associated with the orbital object by receiving a user input via user interface of the system.

[0270] In a 59th Example, the system of any of Examples 55-58, wherein execution of the machine-executable instructions by the hardware processor causes the system to determine the first time window by receiving a user input via a user interface of the system.

[0271] In a 60th Example, the system of Example 59, wherein the user interface comprise a display interface and the user input comprises zooming a time-axis of longitudetime graph in the display interface.

[0272] In a 61st Example, the system of any of Examples 55-60. wherein the first portion of the selection comprises identifiers associated with a pre-maneuver portion of the first time window before the first estimated maneuver time and second portion of the selection comprises identifiers associated with a post-maneuver portion of the first time window after the first estimated maneuver time.

[0273] In a 62nd Example, the system of any of Examples 55-61. wherein execution of the machine-executable instructions by the hardware processor causes the systemto determine the first pre-maneuver orbital parameter further based on the first estimated maneuver time.

[0274] In a 63rd Example, the system of any of Examples 55-62, wherein a postmaneuver portion of the second time window after the second estimated maneuver time is less than 4 hours.

[0275] In a 64th Example, the system of Example 63. wherein the post-maneuver portion is 1 hour or less.

[0276] In a 65th Example, the system of any of Examples 63-64, wherein the postmaneuver portion is 10 minutes or less.

[0277] In a 66th Example, the system of any of Examples 63-65, wherein postmaneuver portion is 1 minute or less.

[0278] In a 67th Example, the system of any of Examples 55-66, wherein execution of the machine-executable instructions by the hardware processor further causes the system to determine a second pre-maneuver orbital parameter using the identifiers received during the second time window and before the second estimated maneuver time and determine the second post-maneuver orbital parameter based at least in part on the second pre-maneuver orbital parameter.

[0279] In a 68th Example, the system of Example 67, wherein execution of the machine-executable instructions by the hardware processor further causes the system to determine a second maneuver characterization parameter using the second pre-maneuver orbital parameter and the second post-maneuver orbital parameter.

[0280] In a 69th Example, the system of Example 68, wherein the second maneuver characterization parameter comprises one or more of characteristics of a maneuver or a maneuver sequence performed within the second time window.

[0281] In a 70th Example, the system of Example 69 wherein the second maneuver characterization parameter comprises a velocity, a velocity change (delta V), or an estimated maneuver time.

[0282] In a 71st Example, the system of any of Examples 55-70, wherein the identifiers comprise a plurality of identifier sets, an individual identifier set comprising: a name identifier; a time identifier; a latitude identifier; a longitude identifier; an azimuth identifier; an elevation identifier; a right ascension identifier; and a declination identifier.

[0283] In a 72nd Example, the system of any of Examples 55-71 , wherein execution of the machine -executable instructions by the hardware processor causes the system to determine one or both the first time window and the second time window by receiving one or both the first time window and the second time window from a user via a user interface.

[0284] In a 73rd Example, the system of any of Examples 55-73, wherein execution of the machine-executable instructions by the hardware processor causes the system to determine one or both the first estimated maneuver time and the second estimated maneuver time by receiving one or both the first estimated maneuver time and the second estimated maneuver time from a user via a user interface.

[0285] In a 74th Example, the system of any of Examples 57-73, wherein execution of the machine-executable instructions by the hardware processor causes the system to transmit the second post-maneuver orbital parameter to a computing system.

[0286] In a 75th Example, the system of any of Examples 68-74, wherein execution of the machine-executable instructions by the hardware processor causes the system to transmit the second maneuver characterization parameter to a computing system.

[0287] In a 76th Example, the system of any of Examples 68-75, wherein execution of the machine-executable instructions by the hardware processor causes the system to transmit the second maneuver characterization parameter and the second post-maneuver orbital parameter to a data store for storage.

[0288] In a 77th Example, the system of any of Examples 68-76, wherein execution of the machine-executable instructions by the hardware processor causes the system to transmit the second maneuver characterization parameter and the second post-maneuver orbital parameter to a display interface.

[0289] In a 78th Example, the system of any of Examples 73-77, wherein execution of the machine-executable instructions by the hardware processor causes the system to: generate a display interface comprising a longitude-time graph comprising: a longitude axis spanning from a lower-longitude limit to an upper-longitude limit; and a time-axis spanning from a lower-time limit to an upper-time limit; and generate data for displaying, via the display interface, a plurality of longitude-time points based on the selected identifiers; wherein an individual longitude-time point represents an identifier set comprising a longitude identifierbetween the lower-longitude limit and the upper-longitude limit and a time identifier between the lower-time limit and the upper-time limit.

[0290] In a 79th Example, the system of Example 78, wherein execution of the machine-executable instructions by the hardware processor causes the system to generate a time slider on the display interface, the time slider configured to allow selection of one or both the first estimated maneuver time and the second estimated maneuver time.

[0291] In an 80th Example, the system of Example 79, wherein selection of the second estimated maneuver time comprises dividing a plurality of longitude- time points within the second time window to a pre-maneuver plurality of longitude-time points having time identifiers before the second estimated maneuver time and a post-maneuver plurality of longitude-time points having time identifiers after the second estimated maneuver time.

[0292] In an 81st Example, the system of Example 80, wherein execution of the machine-executable instructions by the hardware processor causes the system to determine a second pre-maneuver orbital parameter based on selected identifiers associated with the premaneuver plurality of longitude-time points and the second post-maneuver orbital parameter based at least in part on the selected identifiers associated with the post-maneuver plurality of longitude-time points.

[0293] In an 82nd Example, the system of any of Examples 79-81, wherein the time slider comprises a line substantially parallel to the time-axis, the line traversing at least part of the longitude-time graph.

[0294] In an 83rd Example, the system of any of Examples 55-82, wherein execution of the machine-executable instructions by the hardware processor further causes the system to: receive a third time window; receive a third estimated maneuver time within the third time window; and determine a third post-maneuver orbital parameter based at least in part on one or both the first and second post-maneuver orbital parameters and the identifiers within the third time window.

[0295] In an 84th Example, the system of any of Examples 55-83, wherein execution of the machine-executable instructions by the hardware processor further causes the system to generate a first pre-maneuver uncertainty parameter for the first pre-maneuver orbital parameter and a first post-maneuver uncertainty parameter for the first post-maneuver orbital parameter.

[0296] In an 85th Example, the system of Example 84, wherein execution of the machine-executable instructions by the hardware processor causes the system to generate the second post-maneuver orbital parameter based at least in part on one or both the first premaneuver uncertainty parameter and the first post-maneuver uncertainty parameter.

[0297] In an 86th Example, the system of any of any of Examples 84-85, wherein execution of the machine-executable instructions by the hardware processor causes the system to further generate a second pre-maneuver uncertainty parameter and a second post-maneuver uncertainty parameter based at least in part on one or both the first pre-maneuver uncertainty parameter and the first post-maneuver uncertainty parameter.Terminology

[0298] All of the methods and tasks described herein may be performed and fully automated by a computer system. The computer system may, in some cases, include multiple distinct computers or computing devices (e.g., physical servers, workstations, storage arrays, cloud computing resources, etc.) that communicate and interoperate over a network to perform the described functions. Each such computing device typically includes a processor (or multiple processors) that executes program instructions or modules stored in a memory or other non- transitory computer- readable storage medium or device (e.g., solid state storage devices, disk drives, etc.). The various functions disclosed herein may be embodied in such program instructions, or may be implemented in application-specific circuitry (e.g., ASICs or FPGAs) of the computer system. Where the computer system includes multiple computing devices, these devices may, but need not, be co-located. The results of the disclosed methods and tasks may be persistently stored by transforming physical storage devices, such as solid-state memory chips or magnetic disks, into a different state. In some embodiments, the computer system may be a cloud-based computing system whose processing resources are shared by multiple distinct business entities or other users.

[0299] Depending on the embodiment, certain acts, events, or functions of any of the processes or algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether (e.g., not all described operations or events are necessary for the practice of the algorithm). Moreover, in certain embodiments, operations or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, ormultiple processors or processor cores or on other parallel architectures, rather than sequentially.

[0300] The various illustrative logical blocks, modules, routines, and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, or combinations of electronic hardware and computer software. To clearly illustrate this interchangeability, various illustrative components, blocks, modules, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, or as software that runs on hardware, depends upon the particular application and design conditions imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.

[0301] Moreover, the various illustrative logical blocks and modules described in connection with the embodiments disclosed herein can be implemented or performed by a machine, such as a processor device, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A processor device can be a microprocessor, but in the alternative, the processor device can be a controller, microcontroller, or state machine, combinations of the same, or the like. A processor device can include electrical circuitry configured to process computer-executable instructions. In another embodiment, a processor device includes an FPGA or other programmable device that performs logic operations without processing computer-executable instructions. A processor device can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Although described herein primarily with respect to digital technology, a processor device may also include primarily analog components. For example, some or all of the algorithms described herein may be implemented in analog circuitry or mixed analog and digital circuitry. A computing environment can include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portablecomputing device, a device controller, or a computational engine within an appliance, to name a few.

[0302] The elements of a method, process, routine, or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor device, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of a non-transitory computer-readable storage medium. An exemplary storage medium can be coupled to the processor device such that the processor device can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor device. The processor device and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. In the alternative, the processor device and the storage medium can reside as discrete components in a user terminal.

[0303] Conditional language used herein, such as, among others, "can," "could," "might," "may," “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and / or steps. Thus, such conditional language is not generally intended to imply that features, elements and / or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without other input or prompting, whether these features, elements and / or steps are included or are to be performed in any particular embodiment. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list.

[0304] Disjunctive language such as the phrase “at least one of X, Y, Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y, and / or Z). Thus, such disjunctive language is not generally intended to, and should not,imply that certain embodiments require at least one of X, at least one of Y, or at least one of Z to each be present.

[0305] Unless otherwise explicitly stated, articles such as “a” or “an” should generally be interpreted to include one or more described items. Accordingly, phrases such as “a device configured to” are intended to include one or more recited devices. Such one or more recited devices can also be collectively configured to carry out the stated recitations. For example, “a processor configured to carry out recitations A, B and C” can include a first processor configured to carry out recitation A working in conjunction with a second processor configured to carry out recitations B and C.

[0306] While the above detailed description has shown, described, and pointed out novel features as applied to various embodiments, it can be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the spirit of the disclosure. As can be recognized, certain embodiments described herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others. The scope of certain embodiments disclosed herein is indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

[0307] Reference throughout this specification to “some embodiments” or “an embodiment” means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least some embodiments. Thus, appearances of the phrases “in some embodiments” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment and may refer to one or more of the same or different embodiments. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner, as would be apparent to one of ordinary skill in the art from this disclosure, in one or more embodiments.

Claims

WHAT TS CLAIMED TS:

1. A system for determining and transmitting a post-maneuver orbital parameter of an orbital object: an orbital object data interface configured to receive orbital object data from an orbital object data source covering at least a selected time period, the orbital object data comprising identifiers corresponding to the orbital object; a non-transitory computer-readable storage storing instructions that are machine-executable; and a hardware processor in communication with the non-transitory computer- readable storage, wherein the instructions, when executed by the hardware processor, cause the system to: receive the identifiers; receive a lower- time limit and an upper- time limit within the selected time period; generate a display interface comprising: a longitude-time graph comprising: a longitude axis spanning from a lower-longitude limit to an upper-longitude limit; and a time-axis spanning from the lower-time limit to the upper-time limit; generate data for displaying a plurality of longitude-time points based on the identifiers; determine an estimated maneuver time indicating a boundary dividing the plurality of longitude-time points into a pre-maneuver plurality of longitude-time points and a post-maneuver plurality of longitude-time points, wherein the pre-maneuver plurality of longitude-time points represents a premaneuver time period before the estimated maneuver time, and the postmaneuver plurality of longitude-time points represents a post-maneuver time period after the estimated maneuver time; determine a pre-maneuver orbital parameter using a first portion of the identifiers associated with the pre-maneuver plurality of longitude-time points;determine the post-maneuver orbital parameter using at least the premaneuver orbital parameter and a second portion of the identifiers associated with the post-maneuver plurality of longitude- time points; and transmit the determined post-maneuver orbital parameter.

2. The system of claim 1, wherein execution of the instructions by the hardware processor further causes the system to: receive a second lower-time limit and a second upper-time limit within the selected time period; generate a second display interface comprising: a second longitude-time graph comprising: a second longitude axis spanning from a lower-longitude limit to an upper-longitude limit; and a second time-axis spanning from the lower-time limit to the upper-time limit; generate data for displaying a second plurality of longitude-time points based on the identifiers; determine a second estimated maneuver time indicating a boundary dividing the second plurality of longitude-time points into a second pre-maneuver plurality of longitude-time points and a second post-maneuver plurality of longitude-time points, wherein the second pre-maneuver plurality of longitude-time points represents a premaneuver time period before the second estimated maneuver time , and the second post-maneuver plurality of longitude-time points represents a second post-maneuver time period after the second estimated maneuver time; determine a second pre-maneuver orbital parameter using identifiers associated with the pre-maneuver plurality of longitude-time points; determine a second post-maneuver orbital parameter using at least one or both the pre-maneuver orbital parameter and the post-maneuver orbital parameter; and transmit the determined second post-maneuver orbital parameter.

3. The system of claim 2, wherein execution of the instructions by the hardware processor further causes the system to determine the second post-maneuver orbital parameterusing the second pre-maneuver orbital parameter and a portion of the identifiers associated with the second post-maneuver plurality of longitude-time points.

4. The system of claim 1, wherein execution of the instructions by the hardware processor further causes the system to determine a maneuver characterization parameter using the pre-maneuver orbital parameter and the post-maneuver orbital parameter and transmit the maneuver characterization parameter.

5. The system of claim 1, wherein the pre-maneuver orbital parameter comprises a pre-maneuver orbital path of the orbital object before the estimated maneuver time and the post-maneuver orbital parameter comprises a post-maneuver orbital path of the orbital object after the estimated maneuver time.

6. The system of claim 1, wherein the pre-maneuver orbital parameter comprises a velocity of the orbital object.

7. The system of claim 4, wherein the maneuver characterization parameter comprises one or more of characteristics of a maneuver or a maneuver sequence, and postmaneuver data.

8. The system of claim 7, wherein the maneuver characterization parameter comprises a velocity, a velocity change (delta V), or an estimated maneuver time.

9. The system of claim 1, wherein the orbital object data comprises observations of the orbital object collected over the selected time period by at least two telescopes.

10. The system of claim 1, wherein the identifiers comprise a plurality of identifier sets, each of the plurality of identifier sets comprising: a name identifier; a time identifier; a latitude identifier; a longitude identifier; an azimuth identifier; an elevation identifier; a right ascension identifier; and a declination identifier.

11. The system of claim 1, wherein the lower- time limit and the upper-time limit are received from a user via an interaction with the display interface.

12. The system of claim 1 , wherein at least one of the lower-time limit and the upper-time limit are received from a user via an interaction with the display interface.

13. The system of claim 12, wherein the interaction with the display interface comprises one or both of panning and zooming of one or both of the time-axis and the longitude axis.

14. The system of claim 1, wherein the instructions, when executed by the hardware processor, cause the system to receive the identifiers in response to user selection of the orbital object via the display interface.

15. The system of claim 14, wherein the user selection of the orbital object comprises one or both of panning and zooming of one or both of the time-axis and the longitude axis.

16. The system of claim 4, wherein execution of the instructions by the hardware processor causes the system to transmit the determined maneuver characterization parameter and the determined post-maneuver orbital parameter to a computing system.

17. The system of claim 4, wherein execution of the instructions by the hardware processor causes the system to transmit the determined maneuver characterization parameter and the determined post-maneuver orbital parameter to a data store for storage.

18. The system of claim 4, wherein execution of the instructions by the hardware processor causes the system to transmit the determined maneuver characterization parameter and the determined post-maneuver orbital parameter to the display interface.

19. The system of claim 1, wherein the post-maneuver plurality of longitude-time points corresponds a portion of the orbital object data collected during a time period of 4 hours or less.

20. The system of claim 19, wherein the time period is 1 hour or less.

21. The system of claim 20, wherein the time period is 10 minutes or less.

22. The system of claim 21, wherein the time period is 1 minute or less.

23. The system of claim 1, wherein execution of the instructions by the hardware processor causes the system to determine the estimated maneuver time using the identifiers.

24. The system of claim 1, wherein execution of the instructions by the hardware processor causes the system to determine the estimated maneuver time by receiving the estimated maneuver time from a user via a user interface.

25. The system of claim 24, wherein the user interface comprises the display interface.

26. The system of claim 10, wherein execution of the instructions by the hardware processor causes the system to generate a time slider on the display interface, the time slider configured to allow selection of the pre-maneuver plurality of longitude-time points and the post-maneuver plurality of longitude-time points by dividing the longitude-time graph into premaneuver and post-maneuver regions corresponding to pre-maneuver and post-maneuver time periods, respectively.

27. The system of claim 26, wherein the time slider comprises a line substantially parallel to the time-axis, the line traversing at least part of the longitude-time graph.

28. The system of claim 27, wherein determining the estimated maneuver time comprises receiving an adjustment of the time slider by a user.

29. The system of claim 1, wherein the pre-maneuver plurality of longitude-time points and the post-maneuver plurality of longitude-time points are between the lower-time limit and the upper-time limit.

30. The system of claim 5, wherein the orbital object data interface is further configured to receive reference orbital data associated with the orbital object from a reference orbital data set.

31. The system of claim 30, wherein the reference orbital data set span one or both of a first time interval before the estimated maneuver time and a second time interval after the estimated maneuver time, and execution of the instructions by the hardware processor causes the system to determine a residual characteristic of one or both of the post-maneuver orbital parameter and the post-maneuver orbital parameter, indicating a difference between one or both the pre-maneuver orbital parameter and the post-maneuver orbital parameter, and corresponding portions of the reference orbital data.

32. The system of claim 1, wherein execution of the instructions by the hardware processor further causes the system to determine a residual characteristic, indicating differences between one or both the pre-maneuver orbital parameter and the post-maneuver orbital parameter, and portions of the identifiers associated with pre-maneuver and postmaneuver pluralities of the longitude-time points, respectively.-SO-33. The system of claim 32, wherein execution of the instructions by the hardware processor further causes the system to display the residual characteristic via a scalar-time graph in the display interface.

34. The system of claim 33, wherein the scalar-time graph comprises: a scalar axis spanning from a lower-scalar limit to an upper-scalar limit, a second time-axis spanning from a second lower-time limit to a second uppertime limit; and a plurality of pixels corresponding to scalar-time points within the scalar-time graph, individual ones of the scalar-time points corresponding to a pair of identifiers having a time identifier between the second lower-time limit and the second upper-time limit and having a scalar identifier between the lower-scalar limit and the upper-scalar limit.

35. The system of claim 34, wherein execution of the instructions by the hardware processor further causes the system to identify a region of the scalar-time graph associated with longitude-time points and corresponding portion of the identifiers used to determined one or both the pre-maneuver orbital parameter and the post-maneuver orbital parameter.

36. The system of claim 35, wherein the system is configured to identify the region by highlighting corresponding scalar-time points or adding a background shading to the region.

37. The system of claim 34, wherein execution of the instructions by the hardware processor further causes the scalar- time graph to be synchronously updated with respect to the longitude-time graph and a user selection of a longitude-time point.

38. The system of claim 1, wherein the display interface further comprises a longitude-latitude graph comprising: a second longitude axis spanning from a second lower-longitude limit to a second upper-longitude limit: a latitude axis spanning from a lower-latitude limit to an upper-latitude limit; and a plurality of pixels corresponding to longitude-latitude points within the longitude-latitude graph, each of the longitude-latitude points corresponding to identifiers of a set of identifiers comprising a latitude identifier between the lower-latitude limit and the upper- latitude limit and having a longitude identifier between the second lower-longitude limit and the second upper-longitude limit.

39. The system of claim 38, wherein execution of the instructions by the hardware processor further causes the longitude-latitude graph to be synchronously updated with respect to the longitude-time graph and a user selection of a longitude- time point.

40. The system of claim 1, wherein the display interface further comprises a scalartime graph comprising: a scalar axis spanning from a lower-scalar limit to an upper-scalar limit, a second time-axis spanning from a second lower-time limit to a second uppertime limit; and a plurality of pixels corresponding to scalar-time points within the scalar-time graph, each of the scalar-time points corresponding to a set of identifiers including a time identifier between the second lower-time limit and the second upper-time limit and having a scalar identifier between the lower-scalar limit and the upper-scalar limit.

41. The system of claim 40, wherein execution of the instructions by the hardware processor causes the system to provide an indication of longitude-time points associated with the identifiers used to determine the scalar identifier.

42. The system of claim 41, wherein the indication comprises a shaded or highlighted region of the scalar-time graph corresponding to the longitude-time points associated with the identifiers used to determine the scalar identifier.

43. The system of claim 1, wherein the display interface further comprises an indicator of a current time.

44. The system of claim 43, wherein the indicator of the current time comprises a line traversing at least part of the longitude-time graph.

45. The system of claim 9, wherein the display interface further comprises a portion of a geographical map indicating locations of a plurality of orbital object data sources on the geographical map.

46. The system of claim 45, wherein in response to a user selection of one or more longitude-time points, execution of the instructions by the hardware processor causes the system to highlight a location of the orbital object data source of the plurality of orbital objectdata sources associated with the selected one or more longitude-time points on the geographical map.

47. The system of claim 46, wherein the orbital object data source comprises one of the at least two telescopes.

48. The system of claim 1, wherein the display interface further comprises an analysis plot comprising: a first scalar axis spanning from a first lower-scalar limit to a first upper-scalar limit, a second scalar axis spanning from a second lower- scalar limit to a second upper-scalar limit; and a plurality of pixels corresponding to analysis points within the analysis plot, individual ones of the analysis points corresponding to a pair of identifiers comprising a first identifier between the first lower-scalar limit to the first upper-scalar limit and a second identifier between the second lower-scalar limit to the second upper-scalar limit.

49. The system of claim 48, wherein the analysis points are associated with one or more longitude- time points.

50. The system of claim 48, wherein execution of the instructions by the hardware processor causes the analysis plot to be synchronously updated with respect to the longitudetime graph and a user selection of a longitude-time point.

51. The system of claim 48, wherein the first identifier comprises absolute visual magnitude (Mv) and the second identifier comprises a solar phase.

52. The system of claim 51, wherein execution of the instructions by the hardware processor causes the system to provide a marker on the analysis plot, the marker indicating a value of the first identifier corresponding to a time point selected by a user on the longitudetime graph.

53. The system of claim 52, wherein the system synchronously updates the analysis plot by determining the value of the first identifier based at least in part on the time point selected by the user and updating a position of the marker with respect to the first scalar axis.

54. The system of claim 52, wherein the marker comprises a line substantially parallel to the second scalar axis, the line traversing at least part of the analysis plot.

55. A system for determining and transmitting post-maneuver orbital parameters for an orbital object: an orbital object data interface configured to receive orbital object data from an orbital object data source covering at least a selected time period, the orbital object data comprising identifiers corresponding to the orbital object; a non-transitory computer-readable storage storing machine-executable instructions; and a hardware processor in communication with the non-transitory computer- readable storage, wherein the machine-executable instructions, when executed by the hardware processor, cause the system to: receive the identifiers from the orbital object data source via the orbital object data interface; determine a selection of at least some identifiers associated with the orbital object; determine a first time window; determine a first estimated maneuver time within the first time window; determine a first pre-maneuver orbital parameter based on a first portion of the selection; determine a first post-maneuver orbital parameter based at least in part on the first pre-maneuver orbital parameter and a second portion of the selection; and transmit the first post-maneuver orbital parameter.

56. The system of claim 55, wherein execution of the machine-executable instructions by the hardware processor further causes the system to determine a first maneuver characterization parameter using the first pre-maneuver orbital parameter and the first postmaneuver orbital parameter.

57. The system of claim 55, wherein execution of the machine-executable instructions by the hardware processor further causes the system to: receive a second time window;receive a second estimated maneuver time within the second time window; determine a second post-maneuver orbital parameter based at least in part on the first post-maneuver orbital parameter and the selected identifiers within the second time window; and transmit the second post-maneuver orbital parameter.

58. The system of claim 55, wherein execution of the machine-executable instructions by the hardware processor causes the system to determine the selection of at least some identifiers associated with the orbital object by receiving a user input via user interface of the system.

59. The system of claim 55, wherein execution of the machine-executable instructions by the hardware processor causes the system to determine the first time window by receiving a user input via a user interface of the system.

60. The system of claim 59. wherein the user interface comprise a display interface and the user input comprises zooming a time-axis of longitude-time graph in the display interface.

61. The system of claim 55, wherein the first portion of the selection comprises identifiers associated with a pre-maneuver portion of the first time window before the first estimated maneuver time and second portion of the selection comprises identifiers associated with a post-maneuver portion of the first time window after the first estimated maneuver time.

62. The system of claim 55, wherein execution of the machine-executable instructions by the hardware processor causes the system to determine the first pre-maneuver orbital parameter further based on the first estimated maneuver time.

63. The system of claim 55, wherein a post-maneuver portion of the second time window after the second estimated maneuver time is less than 4 hours.

64. The system of claim 63, wherein the post-maneuver portion is 1 hour or less.

65. The system of claim 63, wherein the post-maneuver portion is 10 minutes or less.

66. The system of claim 63, wherein post-maneuver portion is 1 minute or less.

67. The system of claim 55, wherein execution of the machine-executable instructions by the hardware processor further causes the system to determine a second premaneuver orbital parameter using the identifiers received during the second time window andbefore the second estimated maneuver time and determine the second post-maneuver orbital parameter based at least in part on the second pre-maneuver orbital parameter.

68. The system of claim 67, wherein execution of the machine-executable instructions by the hardware processor further causes the system to determine a second maneuver characterization parameter using the second pre-maneuver orbital parameter and the second post-maneuver orbital parameter.

69. The system of claim 68, wherein the second maneuver characterization parameter comprises one or more of characteristics of a maneuver or a maneuver sequence performed within the second time window.

70. The system of claim 69 wherein the second maneuver characterization parameter comprises a velocity, a velocity change (delta V), or an estimated maneuver time.

71. The system of claim 55, wherein the identifiers comprise a plurality of identifier sets, an individual identifier set comprising: a name identifier; a time identifier; a latitude identifier; a longitude identifier; an azimuth identifier; an elevation identifier; a right ascension identifier; and a declination identifier.

72. The system of claim 55, wherein execution of the machine-executable instructions by the hardware processor causes the system to determine one or both the first time window and the second time window by receiving one or both the first time window and the second time window from a user via a user interface.

73. The system of claim 55, wherein execution of the machine-executable instructions by the hardware processor causes the system to determine one or both the first estimated maneuver time and the second estimated maneuver time by receiving one or both the first estimated maneuver time and the second estimated maneuver time from a user via a user interface.

74. The system of claim 57, wherein execution of the machine-executable instructions by the hardware processor causes the system to transmit the second post-maneuver orbital parameter to a computing system.

75. The system of claim 68, wherein execution of the machine-executable instructions by the hardware processor causes the system to transmit the second maneuver characterization parameter to a computing system.

76. The system of claim 68, wherein execution of the machine-executable instructions by the hardware processor causes the system to transmit the second maneuver characterization parameter and the second post-maneuver orbital parameter to a data store for storage.

77. The system of claim 68, wherein execution of the machine-executable instructions by the hardware processor causes the system to transmit the second maneuver characterization parameter and the second post-maneuver orbital parameter to a display interface.

78. The system of claim 73, wherein execution of the machine-executable instructions by the hardware processor causes the system to: generate a display interface comprising a longitude-time graph comprising: a longitude axis spanning from a lower-longitude limit to an upperlongitude limit; and a time-axis spanning from a lower-time limit to an upper-time limit; and generate data for displaying, via the display interface, a plurality of longitudetime points based on the selected identifiers; wherein an individual longitude-time point represents an identifier set comprising a longitude identifier between the lower-longitude limit and the upperlongitude limit and a time identifier between the lower-time limit and the upper-time limit.

79. The system of claim 78, wherein execution of the machine-executable instructions by the hardware processor causes the system to generate a time slider on the display interface, the time slider configured to allow selection of one or both the first estimated maneuver time and the second estimated maneuver time.

80. The system of claim 79, wherein selection of the second estimated maneuver time comprises dividing a plurality of longitude-time points within the second time window to a pre-maneuver plurality of longitude-time points having time identifiers before the second estimated maneuver time and a post-maneuver plurality of longitude-time points having time identifiers after the second estimated maneuver time.

81. The system of claim 80, wherein execution of the machine-executable instructions by the hardware processor causes the system to determine a second pre-maneuver orbital parameter based on selected identifiers associated with the pre-maneuver plurality of longitude-time points and the second post-maneuver orbital parameter based at least in part on the selected identifiers associated with the post-maneuver plurality of longitude-time points.

82. The system of claim 79, wherein the time slider comprises a line substantially parallel to the time-axis, the line traversing at least part of the longitude-time graph.

83. The system of claim 55, wherein execution of the machine-executable instructions by the hardware processor further causes the system to: receive a third time window; receive a third estimated maneuver time within the third time window; and determine a third post-maneuver orbital parameter based at least in part on one or both the first and second post-maneuver orbital parameters and the identifiers within the third time window.

84. The system of claim 55, wherein execution of the machine-executable instructions by the hardware processor further causes the system to generate a first pre-maneuver uncertainty parameter for the first pre-maneuver orbital parameter and a first post-maneuver uncertainty parameter for the first post-maneuver orbital parameter.

85. The system of claim 84, wherein execution of the machine-executable instructions by the hardware processor causes the system to generate the second post-maneuver orbital parameter based at least in part on one or both the first pre-maneuver uncertainty parameter and the first post-maneuver uncertainty parameter.

86. The system of claim 84, wherein execution of the machine-executable instructions by the hardware processor causes the system to further generate a second pre-maneuver uncertainty parameter and a second post-maneuver uncertainty parameter based at least in parton one or both the first pre-maneuver uncertainty parameter and the first post-maneuver uncertainty parameter.

Images