# Welcome to Unisphere Product Documentation ## Hi, Welcome to the official Unisphere documentation hub! We’re excited to support you in maximizing the capabilities of our cutting-edge solutions for drone operations. Our platform is designed to simplify the complexities of flight operations, providing powerful tools to automate, simulate, and optimize your workflows. Whether you’re just getting started or you're an experienced user, this documentation will guide you through every step of the way. ### What You’ll Find Here * [**NOVA:** ](/nova)Our Web-application allowing you to access all our technologies to automated compliant flight operations. * [**API Documentation**](/unisphere-apis): Detailed guides on how to integrate Unisphere’s powerful APIs for flight trajectory simulations, weather data, and more. * **Step-by-Step Tutorials**: Walkthroughs to help you get up and running with our platform in no time. ### How to Get Started 1. **New to Unisphere?** Head over to the Quick Start Guide for a simple step-by-step process to get you up and running in [NOVA](/nova). 2. [**API Integration**](/unisphere-apis): If you're a developer looking to leverage our APIs, start with our API Overview to understand the basics, or dive straight into the API Reference. 3. **Need Help?** Our [FAQ](/faq) section and support resources are here to assist you with common questions and troubleshooting tips. ### Stay Connected We’re continuously improving and adding new features, so be sure to check back regularly for the latest updates. Feel free to drop feedback to - Any feedback is good feedback. # PRODUCT OVERVIEW What we offer Unisphere's **NOVA platform** streamlines operations management for professional drone airlines, enabling a shift from extensive planning to more flying. It caters to the evolving needs of flight organizations by simplifying the complexities associated with various drone types and operational limits. By centralizing and standardizing management processes, NOVA enhances safety, simplifies employee training, and ensures compliance with internal and regulatory requirements. **Key Benefits for Flight Operations Managers**\ The NOVA platform offers several advantages for flight operations managers. It features **smart dispatching**, which allows for efficient resource management based on automated weather assessments for the next seven days. Additionally, **asset management** is centralized, ensuring compliance across all aircraft types and operational limits. Managers can also easily assign teams by providing them with optimal weather data for their missions and sharing essential information. **Features for Flight Directors and Pilots**\ For flight directors and pilots, NOVA consolidates all necessary information in one place, facilitating fast, standardized, and reliable flight planning. It combines various weather data sources, such as high-resolution weather models, rain radar, METAR data, and information from onsite weather stations, into an intuitive evaluation format. Key features include: * **All-in-One Weather Tool:** Access to rain radar, weather observations, and high-resolution forecasts, all globally available in one location. * **Efficient Flight Planning:** Quick go/no-go decisions through automated evaluations of weather conditions tailored to specific missions. * **Weather Intelligence:** Automated identification of favorable flight windows with good weather conditions over the next 48 hours. **Enhanced Resource Management**\ NOVA simplifies complex tasks through intuitive visualizations, improving operational efficiency. It supports operations managers in responding to changes, informing stakeholders, and managing resources effectively. With centralized management of aircraft capabilities and operational constraints, setting up new missions becomes quick and seamless, maintaining professional and safe flight operations at scale. **Maximizing Productivity**\ As organizations expand their mission volume, NOVA provides a clear overview of potential weather impacts, enabling proactive resource planning and rapid adaptation to changes. This capability maximizes team productivity and helps scale operations efficiently. **Best-in-Class Weather Intelligence**\ NOVA employs automated evaluations of relevant weather parameters and limits, enhancing safety in flight planning through sophisticated weather risk assessments. By integrating high-resolution weather forecast data, rain radar, and METAR observations, it delivers exceptional situational awareness for drone missions globally. {% content-ref url="/pages/1SUGHxKSWLZbVHlYQskQ" %} [NOVA](/nova) {% endcontent-ref %} {% content-ref url="/pages/cKY61JzY8JriYKASXyQ2" %} [OPERATIONAL ANALYTICS](/operational-analytics) {% endcontent-ref %} {% content-ref url="/pages/9OmG7hLfoTPROuTESvMe" %} [WEATHER INFORMATION SERVICE for U-SPACE](/weather-information-service-for-u-space) {% endcontent-ref %} # NOVA What's NOVA and what does it offer? NOVA is a software solution designed to support professional drone operators in flight operations and weather management. It addresses the specific needs of these operators by integrating two key components: **weather insights** and **operational concepts.** NOVA provides comprehensive weather integration by sourcing data from high-resolution weather models, native precipitation radar, and official weather observations ([METAR](/nova/glossary#metar)/ [TAF](/nova/glossary#taf)). The platform also supports the integration of users' own weather stations, enhancing situational awareness for mission-specific needs. In addition to weather management, NOVA allows operators to manage all relevant aspects of their ConOps, which include various aircraft types, their performance characteristics and limitations as well as operational limitations related to weather conditions. This integration facilitates standardized and automated weather risk management, enabling fleet operators to conduct diverse drone missions safely.
NOVA Flight Management Platform shows an Evaluated Output for a Route Mission

NOVA - Evaluated Output for Route Missions

The platform is drone agnostic, meaning it can accommodate any type of operation, from [VLOS](/nova/glossary#vlos) to long-range [BVLOS](/nova/glossary#bvlos) flights. NOVA utilizes simulation technology to create a digital twin of each flight, accounting for current weather conditions and aircraft performance. This technology enables a detailed understanding of weather impacts along the flight path, including effects on flight time and battery levels at landing. This innovative approach supports future autonomous operations and multi-drone management while ensuring compliance with safety management systems and the requirements of a Light UAS Operator Certificate (LUC). NOVA is hosted on a secure cloud infrastructure and is accessible via a standard web browser. Its microservices architecture allows for flexible integration with other systems through [APIs](/unisphere-apis), adapting to specific operational needs. ## Key features & benefits
Best-in-Class Weather Data * Access to high-resolution weather models for enhanced forecast accuracy. * Redundancy through multiple weather model sources, including certified national providers like the German Weather Service (DWD). * Coverage of precipitation radar across Europe, along with additional mapping functionalities to support tactical decision-making. * Integration of global aviation-grade weather observations ([METAR](/nova/glossary#metar)/[TAF](/nova/glossary#taf)). * Custom weather sensors can be incorporated to improve mission-specific situational awareness.
Technology-Driven Flight Planning * Simulation-based flight planning for [BVLOS](/nova/glossary#bvlos) missions allows for comprehensive evaluation of weather conditions and their impact on sensitive drone operations. * Automated assessment of aircraft performance, payload, and operational limitations ensures compliance with ConOps and LUC requirements. * Future-ready design supports increasing automation and one-to-many flight operations. * Automated flight feasibility evaluations extend up to seven days ahead, facilitating efficient mission planning and resource allocation.
Agnostic Design * The [Asset Manager](/nova/assets#nova-asset-manager) feature allows the management of diverse missions, routes, drone types, and performance characteristics. * Users can set operational limits to cover specific weather conditions, regulatory requirements, and payload specifications. * Centralized asset management enables updates to limitations or performance data across all missions on the platform. * NOVA's design is tailored for drone fleet operators, supporting standardized flight planning and enhanced weather risk management.
Enhanced Compliance * The platform supports role-based management, ensuring users have access only to relevant information and can only perform actions within their assigned responsibilities. * Centralized role management ensures compliance with company procedures and LUC documentation during flight planning and take-off decisions.
# Get started Take you first steps in NOVA. This guide will assist you in getting started with NOVA. You will find instructions for creating and managing your account as well as utilizing the various tools. Learn how to configure your mission using the necessary parameters and how to create and manage your assets. {% content-ref url="/pages/Lw9b367RFznz96mXDRUX" %} [Create an account](/nova/get-started/create-an-account) {% endcontent-ref %} {% content-ref url="/pages/BcrlE6nKLQv0P0r4Q0oE" %} [Create a new mission](/nova/get-started/create-a-new-mission) {% endcontent-ref %} {% content-ref url="/pages/4H7OrxzZTTQ2scPD6dvE" %} [Create your assets](/nova/get-started/create-your-assets) {% endcontent-ref %} {% content-ref url="/pages/hMsk0WoTMkzf9xVOtleX" %} [Manage your profile](/nova/get-started/manage-your-profile) {% endcontent-ref %} # Create an account Create a NOVA account for your organization. The first time you access NOVA, you will see a registration window. Get there by using this link: {% embed url="" %} Link to NOVA {% endembed %} On the right side of the window, enter your registration information. After that, you can set a password of your choice. Finally, we ask you to read through our Terms and License Conditions as well as our Privacy Policy. You can then register with us by clicking "Sign Up".

Registration window

Afterward, we will send a confirmation email to the email address you provided. Open the email and complete your registration by clicking the "Confirm" button. {% hint style="info" %} If you haven't received an e-mail, please consider the following steps: * Click "SEND AGAIN" on the confirmation window * Check your spam folder * Make sure you're logged into the right account {% endhint %} After confirming, you will be redirected to our login window, where you’ll also find the patch notes for our latest releases on the left side. In this section, you can review newly added features, improvements, and bug fixes. Enter your login details on the right and press "Sign In."

Login window

After logging in, you will arrive on the NOVA menu. {% hint style="info" %} Forgot your login password? * Click "FORGOT YOUR PASSWORD?" on the login window * Enter your registered e-mail & press "SEND E-MAIL" * Find your NOVA password reset code in your mails and enter it in the "Reset your password" window. * Set a new password & press "RESET" {% endhint %} # Create a new mission Guide on how to create a new mission in NOVA. A mission in NOVA is a digital twin of your flight operation. To create a mission, you must first go to the missions tab in the NOVA main menu. In this window, your missions are listed, provided you have created any. To create a mission, click "New Mission" and complete the following 6 steps. {% stepper %} {% step %} ### Mission Type You can choose the appropriate mission type based on the deployment location of your drone. Currently, you can choose between three mission types: [Local flight](/nova/missions/types/local-flight), [Multi-location](/nova/missions/types/multi-location), and [Route](/nova/missions/types/route). Check the desired type and press "CONTINUE" {% endstep %} {% step %} ### Mission Information In the next step, you can add mission information. Enter a name for your mission under "Name" and provide a description of what the mission is about in the window beneath. Press "CONTINUE". {% endstep %} {% step %} ### Flight Location You can now plan your flight according to the previous selected mission type. The map will aid you in visualizing and selecting the location. #### Local-Flight Provide one location where your operations will take place. In the left panel, you can set a name for your flight location. In the right panel, "Search name / coordinates," you can specify your flight location. You can select the desired location by clicking on the map, searching for an address, using the current GPS location (if available on your device) or adding a previously created [location asset](/nova/assets/locations-and-routes) via the "ASSETS" button. #### Multi-Location Provide multiple locations for your flight.​ As with the local-flight mission type, you can name and set your flight locations. Additional locations can be added by clicking the "Add Another Location" button. {% hint style="warning" %} A maximum of 10 flight locations can be selected. All locations must fall within a 100 km radius, which is displayed on the map after selecting the first location. {% endhint %} #### Route Provide a route to be flown from take-off to landing. To define the flight route, provide waypoints by specifying coordinates, clicking on the map, or by uploading a KML file. In addition to the location, provide at each waypoint the [AGL](/nova/glossary#agl) altitude. The waypoints and the horizontal distance between them are indicated on the map. You may move the waypoints on the map and add intermediate waypoints by clicking on "ADD ANOTHER WAYPOINT" in between two waypoints in the list. Waypoints can be deleted by selecting the waypoint in the list and clicking on the trash can icon. The initial waypoint designates the take-off location, while the final waypoint designates the landing location. If needed, you may reverse the order of the waypoints by clicking "SWAP ORDER". To mimic vertical flight paths, it is also possible to have two waypoints on top of each other with the same coordinates but different altitudes. For more detailed instructions, watch our "Route Mission Feature" video. {% embed url="" fullWidth="true" %} Press "CONTINUE" to select your aircraft type. {% endstep %} {% step %} ### Aircraft type In the next step, you can select the [aircraft type](/nova/assets/aircraft-type) and [performance set](/nova/assets/performance-set). For the aircraft type, you can choose between Fixed-Wing/Hybrid and Multicopter, as well as select from the available assets. The performance set can be selected from your assets, created via the three-dot menu, or generated as an example set by pressing "CREATE EXAMPLE". Press "CONTINUE" to set your operational limits. {% endstep %} {% step %} ### Operational limits In this window, you can now enter your operational limits. Upload a [limit set](/nova/assets/limit-set) from your assets, create one or generate an example limit set. Press "CONTINUE" to access the summary of your mission. {% endstep %} {% step %} ### Mission summary In the summary, you will receive an overview of your mission. It includes the name, description, type, and location of your mission, as well as the aircraft type used, the performance set and limit set. By clicking the "CREATE MISSION" button, your mission will be generated. {% endstep %} {% endstepper %} {% hint style="info" %} A total of 20 missions can be created. {% endhint %} Once you've created your mission, it will appear in the missions list. Hovering over the mission reveals our three weather forecast evaluation options: "[NOW](/nova/missions/results/now)," "[AWARE](/nova/missions/results/aware)," and "[CAST](/nova/missions/results/cast)." You can access these options with a single click, or access "NOW" directly by double-clicking on the mission or the location icon on the left side. # Create your assets Create your custom NOVA assets. {% hint style="info" %} Assets are reusable components that define key mission parameters, ensuring consistency, adaptability, and streamlined updates of all missions. [Read more](/nova/assets) {% endhint %} ## 1. How to use the Asset Manager In this video, we provide an overview of the available asset types. {% embed url="" %} Guide on how to use the asset manager {% endembed %} ## 2. Create an asset Let us explain to you how [assets](/nova/assets) are created using the "Aircraft type limit set" as an example. {% embed url="" %} Aircraft type limit set guide {% endembed %} # Edit your Mission Adjust your mission after it's creation. The subsequent editing of a mission allows the user to make changes while the remaining conditions of the mission are preserved. To edit your mission, you must access the mission overview. It displays the mission name, aircraft name and type, operational limit set, along with the time it was last updated and details of the editor. The token icon in the top right corner tracks the number of created missions. At the bottom, you can choose how many projects to display per page and navigate between pages if needed.

Mission overview

Using the 3-dot menu to the right of your mission, a menu opens above the mission list. On the left side, you will see three icons from left to right: a pencil (edit), a trash can (delete), and a globe (update). In the editing window, you can adjust general flight details and choose from your created [assets](https://docs.unisphere.io/nova/get-started/pages/4H7OrxzZTTQ2scPD6dvE#id-2.-create-an-asset). You can update the mission name, description, mission type, aircraft type, and operational limit set.

Editing window

{% hint style="warning" %} The globe icon runs your mission with the changes. Only then will your mission be updated. {% endhint %} Using the trash can icon, you can delete your mission. On the right side, you can retrieve the mission ID and finalize the editing process by clicking on the cross. # Manage your profile Access and utilize the features of your profile. To access your user profile, you need to click on your profile icon in the top right corner of the screen. A menu will then open, where you can manage your organization and user settings.

User profile menu

Organization Under "Organizations," all the organizations you are a member of are displayed. If you are a member of multiple, you can switch between them by clicking on the corresponding one.
Settings The [settings](#settings) allow you to manage and customize NOVA.
Help / FAQ Through this tab, you can find our product documentation. Under [FAQ](/faq), you can find previously asked questions and their answers. If you need additional help, feel free to reach out to us at .
Logout Logout from your account. This will take you to the login screen, where you can switch accounts.
# Settings Adjust your NOVA settings.

NOVA settings

{% hint style="info" %} All changes that do not regard your organisation will apply only to you and not to other members. {% endhint %}
Account Under Account, you can currently change your first and last name as well as leave your organization (unless you are an administrator).
User units Under User Units, you can change the default units of the parameters in NOVA. The parameters are divided into General, Flight, and Weather, with units available in both the metric and imperial systems. Once adjusted your missions will automatically be updated and you see your weather evaluation in the units selected.
Security Under Security, you can change your password. To do so, enter your current password and set a new one.
Themes In Themes, you can change the appearance of NOVA. You can either sync the appearance with your operating system or manually choose between light and dark mode.
General Under General, you can view your NOVA subscriptions and usage.\ "Current Seat Overview" displays the total number of members in your organization, with a maximum of 20. Below that, the "Current Mission Overview" shows the total number of missions you have. Further down, your current plan is displayed, listing your bundles and add-ons.
API Integration Under API Integration, you can manage your API keys. You can create up to 5 keys at a time.
Users Under Users, you can access an overview of all members of your organization, including their name, email, and role. You can add members using the icon in the top-left corner and remove them via the three-dot menu and trash can icon. To add a user, you need to provide their account email and assign an organizational role. You must then send an invite, which the recipient will receive via email and must accept.
# Missions Why are missions needed in NOVA? What is a mission? How is a mission created and used in NOVA? **Missions are the foundation for flight planning and operational decision-making in NOVA.** They serve as structured digital plans for intended drone or air taxi operations. By defining a mission, users describe their planned drone operations. This description is the basis for the digital twin of the drone flight in NOVA which enables the trajectory simulations. ## What is a mission? A mission in NOVA is a virtual flight plan that describes how, where, and under what conditions an aircraft is expected to operate. The [mission type](/nova/missions/types) determines the structure of the planned operation: * A single location, e.g. for a single VLOS flight * Multiple locations, e.g. for inspection at different customer projects * Or a route from point A to B, e.g. for a BVLOS drone delivery mission The mission combines [**Assets**](/nova/assets) to collect all information needed to simulate and evaluate a planned flight. These Assets are: * [**Aircraft Type**](/nova/assets/aircraft-type)**:** The type of drone or air taxi that is used for the mission * [**Limit Set**](/nova/assets/limit-set)**:** The operational conditions under which the mission is allowed to start, including weather * [**Location or Route**](/nova/assets/locations-and-routes)**:** The location or route where the mission takes place * [**Weather Stations**](/nova/weather-stations)**:** Additional weather stations for local weather data access Once created, a mission becomes the basis for ongoing evaluation. NOVA continuously checks its feasibility using live environmental data and user-defined constraints, providing a current status and future outlook. *** ## NOVA Mission Overview The mission overview table lists all existing missions in your workspace and gives you quick access to key configuration and status information. Each row in the table includes: * **Name** – The mission title, with an optional description preview * **Aircraft type** – The selected aircraft or drone model for the mission * **Configuration tag** – A label indicating the aircraft class (e.g. Hybrid, Fixed-wing) * **Operational limit sets** – The applied limit set used to evaluate mission feasibility * **Modified** – The last modified date and the user who updated it The NOVA Mission Overview can be **filtered by teams**, making the most relevant missions quickly accessible to the user. See [Teams](/nova/missions/teams#mission-visibility-and-filtering) for more details.
NOVA Flight Management Platform Interface showing Missions Hub and Filtering Options
You can sort the list by name or modification date and use the search bar to quickly find a specific mission. The “...” menu on each row lets you access actions such as editing, duplicating, or deleting the mission. To create a new mission, click the **`+ New Mission`** button in the top right. Afterwards, follow the wizard [instructions](/nova/get-started/create-a-new-mission). # Types Get to know the different mission types in NOVA. In NOVA, there is a mission type for each flight operation: * Local Flight for a single location * Multi-Location for multiple locations * Route along a path. These mission types allow you to create a digital twin that aligns with your real mission, providing a customized and precise analysis of your flight operation. # Local-Flight The local flight mission type and its use cases. In Local-Flight, you can assess the feasibility of your missions at a specific location with the help of our evaluation tools: [NOW](/nova/missions/results/now) for real-time conditions, [AWARE](/nova/missions/results/aware) for a 2-day forecast, and [CAST](/nova/missions/results/cast) for a 1-week outlook. The evaluation analyzes flight feasibility based on the [limits](/nova/assets/limit-set) you have set for the specific mission and presents them in an overview. You will receive both a concrete, color-coded mission result as well as a summary of the evaluated limits, allowing you to determine whether and which values fall outside the tolerance range. Additionally, comprehensive weather information such as wind direction, temperature, air pressure, and cloud cover is provided to enable a well-informed and independent assessment of the weather conditions. When [setting up a local flight mission](/nova/get-started/create-a-new-mission), any location can be specified. All weather data is then taken from this exact location. ## Use cases Scenarios for which this mission type is suitable could include: * **Site Inspections**: Aerial inspections of infrastructure, construction sites, or agricultural areas to assess condition and progress. * **Aerial Imaging**: Capturing high-quality images and videos of a single location for inspections, marketing, or documentation. # Multi-Location The multi-location mission type and its use cases. For Multi-Location missions, our tools allow you to evaluate the flight feasibility across multiple locations. Using [NOW](/nova/missions/results/now) for current conditions, [AWARE](/nova/missions/results/aware) for the next 2 days, and [CAST](/nova/missions/results/cast) for a week-long forecast, you gain a comprehensive insight into the flight feasibility of your mission. Similar to a local flight mission, the flight feasiblity is assessed based on your set limitations, except that several locations are taken into account. Information on wind direction, temperature, pressure and cloud cover is also provided. Apart from the selection of several flight locations, the [creation of a multi-location](/nova/get-started/create-a-new-mission) is identical to a that of a local flight mission. {% hint style="info" %} When creating a multi-location mission, different operational boundaries cannot be set for multiple flight locations. For this, separate flight missions would need to be created under Local-Flight. {% endhint %} ## Use cases Scenarios for which this mission type is suitable could include. * **Surveillance and Monitoring**: Systematic monitoring of multiple sites for security, environmental, or operational oversight. * **Event Coverage**: Filming and photography for events or large venues that require aerial footage from different angles. # Route The route mission type and its use cases. In Routes, you can evaluate the feasibility of missions along a defined path. By leveraging the same evaluation tools—[NOW](/nova/missions/results/now), [AWARE](/nova/missions/results/aware), and [CAST](/nova/missions/results/cast)—you’ll receive an in-depth analysis of flight feasibility, along with an overview of your set limit parameters. In addition to weather parameters, the Route evaluation also provides information on the energy levels during each flight phase, as well as your height [AMSL](/nova/glossary#amsl) through an altitude profile. When [creating a Route mission](/nova/get-started/create-a-new-mission), you can set waypoints and altitudes as needed, allowing you to design complex flight paths that are perfectly tailored to your flight profile. {% hint style="info" %} Unlike Local-Flight and Multi-Location missions, where weather data is retrieved from predefined altitudes, in Route missions, the weather data is determined based on the flight altitude. {% endhint %} ## Use cases Scenarios for which this mission type is suitable could include: * **Infrastructure Inspections**: Inspections of power lines, pipelines, and other infrastructure along specific routes. * **Surveying**: Data collection along defined routes for mapping and planning purposes # Results NOVA's flight feasibility evaluation tools. The core functionality of NOVA is based on the automated evaluation of flight conditions for each mission. After setting up your mission, NOVA automatically assesses the flight feasibility of your mission based on the entered parameter limits and weather data. You then have access to our three weather evaluation methods—NOW, AWARE, and CAST—for real-time, 2-day, and 7-day assessments. The system presents the results through three dedicated interfaces using overviews, graphs, and charts. A traffic light system is deployed - indicators marked "red," "yellow," or "green" - providing pilots with essential decision-making information at a glance while keeping the data concise. All displayed information is continuously updated to ensure real-time accuracy.

Example results page for route missions

In the following section, we will take a closer look at each evaluation method. {% content-ref url="/pages/xtPPGbBrA1XQrb1dAsnK" %} [NOW](/nova/missions/results/now) {% endcontent-ref %} {% content-ref url="/pages/8bYsvvt1ZS8dqf3Q9E0t" %} [AWARE](/nova/missions/results/aware) {% endcontent-ref %} {% content-ref url="/pages/YK7mGIHVTj0HG81yK6Qj" %} [CAST](/nova/missions/results/cast) {% endcontent-ref %} # NOW Get to know our flight feasibility tool "NOW". NOVA NOW is dedicated to furnishing pilots with timely, real-time data essential for swift and informed flight decisions, effectively discerning between favorable ("go") or unfavorable ("no-go") conditions. By offering the most recent and precise meteorological insights, it serves as a valuable support tool for pilots in the critical moments preceding flight. Moreover, this view also integrates a real-time precipitation radar feature, providing updates at a rapid rate of every 5 minutes. {% content-ref url="/pages/0zDWzHL5LIoTdDFjJbJI" %} [Local-Flight](/nova/missions/results/now/local-flight) {% endcontent-ref %} {% content-ref url="/pages/8jagsukxMNkc7ljdCGn5" %} [Multi-Location](/nova/missions/results/now/multi-location) {% endcontent-ref %} {% content-ref url="/pages/EnULNy60n94TQY6RlOe5" %} [Route](/nova/missions/results/now/route) {% endcontent-ref %} # Local-Flight NOW evaluation for a Local-Flight mission. ## Parameter Overview The parameter overview displays a parameter summary, containing all parameter limits considered in the evaluation, as well as additional information on the current weather conditions, which allow the pilot to independently assess the weather situation. The evaluation, combined with the additional weather information, provide an accurate and reliable decision-making basis for the flight mission.

Parameter overview

Components that are part of the parameter overview are the following: a [parameter summary](#parameter-summary), a section for [wind direction](#wind-direction), [wind gusts](#wind-gust), [precipitation](#percipitation), [temperature and pressure](#temp-and-press), [cloud cover & visibility](#clouds-and-vis), and [METAR/TAF ](#metar-taf)data. These are explained in detail below. ## Parameter Sections {% tabs %} {% tab title="Parameter Summary" %}

Parameter Summary

This summary provides an overview of all limit parameters considered when assessing the flight capability of the mission. In this example, it includes precipitation, visibility, as well as wind gusts and wind speed, both measured at a standard height of 10 meters above ground level. Based on these parameters, the corresponding indication of flight capability is displayed in the window. {% hint style="info" %} The result of the flight capability analysis can also be seen directly below the displayed mission name and is highlighted in color: **GREEN - GOOD TO FLY (NOMINAL)**: All weather parameters lie within the nominal range. **YELLOW - CAUTION (MODERATE)**: At least one parameter lies within the moderate range. **RED - DO NOT FLY (SEVERE)**: At least one parameter lies within the critical range. {% endhint %} {% endtab %} {% tab title="Wind Direction" %}

Wind Direction

The "WIND DIRECTION" section shows wind direction and speed at the significant heights [AGL](/nova/glossary#agl). The wind-direction indicator on the left illustrates the wind direction at each altitude, with color-coded arrows corresponding to the heights listed on the right: * **10 meters AGL**: This is the standard height for wind measurements, as defined by the World Meteorological Organization (WMO). * **100 meters AGL**: This height is roughly above the atmospheric boundary layer, which typically extends up to about 60 meters AGL. At this level, wind is less affected by surface roughness. * **300 meters AGL**: Height which is just in the range of a typical flight altitude and wind conditions are more stable. {% hint style="info" %} Due to the logarithmic wind profile, wind speed increases with height. Close to the ground, wind speed is nearly zero because of surface friction, leading to different measurements depending on the height. {% endhint %} {% endtab %} {% tab title="Wind Gust" %}

Wind Gust

The "WIND GUST" section indicates wind gust speeds at the significant heights, similar to wind speed. A wind gust is referred to when the instantaneous wind speed exceeds the mean wind speed by at least 10 knots (5 m/s). It is therefore defined as a brief and sudden increase in wind speed. {% hint style="info" %} The averaging period for determining deviations from the mean wind speed is approx. 3 seconds. This period helps ensure accurate and consistent assessment of wind gusts. {% endhint %} {% endtab %} {% tab title="Precipitation" %}

Precipitation

This section provides key precipitation metrics: the precipitation rate in mm/h, the probability of precipitation, the probability of thunder strikes, and the probability of icing.
Precipitation **Accumulated Precipitation**: The total amount of moisture that has fallen over a specified period. Various types of precipitation are taken into account: rain, snow, sleet, and hail. Typical intensity ranges are: #### **Rain (in mm/h):** * **Light:** < 2.5 mm/h * **Moderate:** 2.5 mm/h to 10 mm/h * **Heavy:** > 10 mm/h #### **Sleet (in mm/h):** * **Light:** < 2.5 mm/h * **Moderate:** 2.5 mm/h to 5 mm/h * **Heavy:** > 5 mm/h
Precipitation Probability The likelihood of precipitation occurring within a given time frame, which is derived from complex modeling that incorporates factors such as humidity, temperature, and atmospheric pressure.
TS prob. **Definition** Thunderstorm probability quantifies the likelihood of thunderstorms occurring in a specific area. **Estimation Methodology** TS probability is provided by using estimations conducted by advanced models that analyze atmospheric parameters such as temperature, humidity, and wind patterns to predict the likelihood of thunderstorms. It's based on key indicators, including thermodynamic factors like high humidity (often exceeding 90%) and atmospheric instability, as well as meteorological indices such as the [Lifted Index](/nova/assets/limit-set/weather-and-operational-parameters#lifted-index) (LI) and [Convective Available Potential Energy](/nova/assets/limit-set/weather-and-operational-parameters#cape-index) (CAPE), which assess the potential for thunderstorm development. Additionally, the predictions are enhanced by integrating real-time data from Meteodrones, which provide detailed atmospheric profiles and improve the accuracy of thunderstorm forecasts.
Icing Icing is a critical concern in aviation as it can lead to severe safety hazards, including loss of control. Icing conditions typically arise when two specific criteria are met: air temperatures drop below 0 °C, and relative humidity exceeds 95%. These conditions can occur even at low altitudes, depending on temperature and moisture levels​.
{% endtab %} {% tab title="Temp & Press" %}

Temperature & Pressure

This section provides information on temperature, relative humidity, and dew point.
Rel. humidity Percentage of water vapor in the air compared to the maximum amount it can hold at a given temperature.
Dew Point Temperature at which air moisture condenses into liquid. High dew points indicate moist air, increasing the risk of fog, clouds, and precipitation, which can reduce visibility. Low dew points mean drier air, usually resulting in clearer skies.
{% endtab %} {% tab title="Clouds & VIS" %}

Clouds & Visibility

This section provides an overview of cloud cover and visibility conditions during the mission timeframe. It lists low cloud coverage, cloud base, cloud ceiling, and visibility.
Low Cloud Cover **Definition:** This parameter refers to the portion of the sky covered by low clouds (typically below 2,000 feet or approximately 600 meters). **Determination:** Data on low cloud cover is collected through satellite-based observations, radar, and automated weather stations, which analyze both the altitude and extent of the clouds. Numerical Weather Prediction (NWP) models are used to simulate precipitation and cloud formation, enabling accurate forecasts. The classification of "Low Cloud Cover" is expressed in percentages and divided into intervals, with the coverage reported in octas (1 octa represents 1/8 of the sky). **Classification** * **0-12.5%**: No to very little cloud cover (0 octas)) * **12.5-37.5%**: Slightly cloudy (1-3 octas) * **37.5-62.5%**: Moderately cloudy (4-5 octas) * **62.5-87.5%**: Heavily cloudy (6-7 octas) * **87.5-100%**: Overcast to completely cloudy (8 octas)
Cloud Base The cloud base refers to the height at which the lower boundary of the clouds begins, measured in feet or meters above sea level.
Cloud Ceiling The cloud ceiling is the height of the highest cloud base above the ground that causes visibility impairment. This is important for aviation and meteorological reporting.
Visibility Visibility refers to the distance at which an object can be clearly seen and identified through the atmosphere. Visibility measurements do not take terrain or day time into account; they focus solely on atmospheric clarity, considering factors such as haze, precipitation, fog, and other meteorological phenomena that can affect sightlines.
{% endtab %} {% tab title="METAR / TAF" %} Here, the [METAR](/nova/glossary#metar) and [TAF](/nova/glossary#taf) data for the surrounding airports around the flight location are illustrated, listed by airport designation, along with the distance to the flight location (horizontal arrow) and the altitude at which the METAR data is measured. Based on the latitude and longitude coordinates, a ranking is created with airports sorted by increasing distance. The first three airports from this list are selected.

METAR section

TAF section

Structure **METAR**: METAR \[Station Identifier] \[Date and Time of Observation] \[Wind] \[Visibility] \[Weather Conditions] \[Sky Condition] \[Temperature and Dew Point] \[Pressure] \[Other Remarks] **TAF**: TAF \[Station Identifier] \[Date and Time of Forecast] \[Wind] \[Visibility] \[Weather Conditions] \[Sky Condition] \[Forecast Changes] \[Other Remarks]
Common Abbreviations **Cloud Cover States:** 1. **SKC** – Sky Clear (no clouds). 2. **CLR** – Clear (no significant clouds). 3. **FEW** – Few clouds (1/8 to 2/8 of the sky covered). 4. **SCT** – Scattered clouds (3/8 to 4/8 of the sky covered). 5. **BKN** – Broken clouds (5/8 to 7/8 of the sky covered). 6. **OVC** – Overcast (8/8 of the sky covered). 7. **CB** – Cumulonimbus (thunderstorm clouds). 8. **TCU** – Towering Cumulus (potential for thunderstorms). #### Weather Conditions: 1. **-RA** – Light rain. 2. **RA** – Rain. 3. **+RA** – Heavy rain. 4. **-SN** – Light snow. 5. **SN** – Snow. 6. **+SN** – Heavy snow. 7. **SHRA** – Showers of rain. 8. **+SHRA** – Heavy showers of rain. 9. **SHSN** – Showers of snow. 10. **+SHSN** – Heavy snow showers. 11. **TS** – Thunderstorms. 12. **+TS** – Severe thunderstorms. 13. **SQ** – Squall (strong wind gusts). 14. **HZ** – Haze (reduces visibility). 15. **FG** – Fog (reduces visibility). 16. **BR** – Mist (light fog). 17. **DU** – Dust (reduces visibility). 18. **SA** – Sand (reduces visibility). 19. **VA** – Volcanic ash (reduces visibility). 20. **UP** – Unknown precipitation (precipitation not specified). #### Phenomena: 1. **FZFG** – Freezing fog. 2. **FZRA** – Freezing rain. 3. **G** – Gusts (wind gusts). 4. **LGT** – Light (used to describe light intensity of rain, snow, etc.). 5. **MOD** – Moderate (used for moderate intensity of rain, snow, etc.). 6. **HEAVY** – Heavy (used for intense weather conditions like heavy rain, snow, etc.). 7. **WVA** – Wind variable (wind direction is variable). 8. **RVR** – Runway Visual Range (visibility along a runway).
{% endtab %} {% endtabs %} # Multi-Location NOW evaluation for a Multi-Location mission. The evaluation of a multi-location mission in NOW works similarly to that of a local flight, except that multiple flight locations are taken into account. For information on the meaning of each parameter, please refer to [Local-Flight](/nova/missions/results/now/local-flight), parameter sections. Above the parameter overview, there is a tab section that allows switching between the different flight locations. The tabs display the coordinates or the name of the flight location. The currently active tab is highlighted.

Location tabs

# Route NOW evaluation for a Route mission. ## Parameter Overview The parameter overview of a route mission differs from that of a single or multi-location flight. At the top of the parameter overview is an energy display, divided into energy levels at takeoff and landing, as well as during flight. Within these sections, the considered parameters are displayed. Below the energy display, there is an altitude profile of the mission and a section with [METAR](/nova/glossary#metar)/[TAF](/nova/glossary#taf) data.

Route Mission Overview

## Parameter Sections {% tabs %} {% tab title="Energy usage" %}

Energy usage summary

These summaries offer an overview of the status of all mission limits during all flight phases (takeoff, enroute, and landing). Additionally, an energy display shows how much energy is available, how much is required, and how much will remain. The battery charge level is also taken into account for the evaluation. {% hint style="warning" %} In the route planner, wind speed and gusts are taken directly from the actual flight levels rather than relying on preselected heights, ensuring more accurate data for optimized planning. {% endhint %} {% endtab %} {% tab title="Altitude profile" %}

Altitude profile section

Located beneath the energy usage display, there's an altitude profile. The vertical axis represents the [AMSL](/nova/glossary#amsl) height, and the horizontal axis measures the distance. In the top left, along with the available energy, the flight duration and distance are shown. Below the altitude profile, there's also a [METAR](/nova/glossary#metar)/[TAF ](/nova/glossary#taf)display. More information on that can be found in the "Local-Flight" under Parameter sections. {% endtab %} {% endtabs %} # AWARE Get to know our 48 h flight feasibility tool "AWARE". With AWARE, users can access a detailed view of flight conditions, allowing for more tactical decision-making and enhanced situational awareness. Each hour's evaluation within the forecast is guided by the predefined limits established under the asset management mode by the user or organization. This ensures that the forecast aligns with the specific parameters and thresholds set by the user or organization, enhancing the accuracy and relevance of the projected operational conditions. NOVA AWARE provides a close-to-mission assessment and decision-making, determining the best places to fly within the next 48 hours. {% content-ref url="/pages/KwC20NAhLWVGSH4b7l8E" %} [Local-Flight](/nova/missions/results/aware/local-flight) {% endcontent-ref %} {% content-ref url="/pages/Yh75wjXRK3ytAR7Vxl5B" %} [Multi-Location](/nova/missions/results/aware/multi-location) {% endcontent-ref %} {% content-ref url="/pages/4DBfAat9YqgMPGuIHAhU" %} [Route](/nova/missions/results/aware/route) {% endcontent-ref %} # Local-Flight AWARE evaluation for a Local-Flight mission. ## Parameter Overview In AWARE, a 48-hour graphic showing the flight conditions is displayed. Each hour within this time window is individually assessed and represented using the color scheme. The graphic is divided into two 24-hour blocks for the current day and the following day. For easier reading, the date of each day is shown above the 24-hour block, with times indicated in 6-hour increments. This setup makes it immediately clear whether a flight is possible within the desired time window or at what times conditions are more favorable.

Weather condition summary

Clicking on the graphic, the relevant limit parameters along with their respective units are displayed in separate graphs. The hourly values of each parameter are connected by a line that moves within color-coded ranges representing nominal, moderate, or severe levels. The specific upper and lower limits to the left of the graph are based on the 2-day minimum and maximum values.

Parameter visualization

## Weather Icons Above the display, weather symbols are shown, representing the weather conditions for the respective time periods. Common weather symbols include:
SUNNY/files/aIloXWhAcM9rfwjV3Aee
CLOUDY/files/1gzyNGIESfzAjay08eJX
CLEAR NIGHT/files/eeoqrZ3MYNjd5c9ESbot
LIGHT CLOUDS/files/1QZWijYTqCgBw0xBobVk
RAIN/files/5s41uAm2Fl9Ocl2G9Osr
LIGHT CLOUDS (NIGHT)/files/xZCfF8imoMMAOepaxn02
LIGHT FOG/files/CakPrNp6LJTwffvLr50l
FOG/files/SRzagwPR6uJE1xW2Cqxl
LIGHT FOG (NIGHT)/files/gD1DwuRCzCIuapUEm96W
LIGHT CLOUDS WITH RAIN/files/NRvyT3UWYJRJvXUo5n0B
SNOW/files/FZ7zbcQzTfvNrX3vywQ9
LIGHT CLOUDS WITH RAIN (NIGHT)/files/uHxJlQbnJgJKpp3T3hfd
LIGHT CLOUDS WITH SNOW/files/JsrQM3Sw0XLws2LzziS6
SLEET/files/gZKq5ArWdHttcugPdmMF
# Multi-Location AWARE evaluation for a Multi-Location mission. In the evaluation window of a multi-location mission, the different flight locations are evaluated separately and listed one after the other.

Listed locations

The evaluation of the individual parameters at the respective location is the same as in a [local flight](/nova/missions/results/now/local-flight). # Route AWARE evaluation for a Route mission. In the route evaluation overview, the takeoff, en-route, and landing evaluations are listed one after the other.

Weather condition summary

In route missions, the weather data is displayed using bar charts. This is because the weather data needs to cover the entire flight time. Weather measurements are shown as value ranges, rather than measurements at specific points in time. In addition to the regular limit parameters, the flight duration and remaining energy, sourced from the aircraft's performace set, are also illustrated for route missions.

Parameter visualization

# CAST Get to know our 7- day flight feasibility tool "CAST". In CAST, users gain a comprehensive view of flight conditions for the next 7 days, broken down into hourly forecasts. This tool is ideal for long-term resource planning and the assignment of drone missions. Each hour's evaluation within the forecast is also guided by the predefined limits established under the asset management mode by the user or organization, ensuring that the forecast aligns with the specific parameters and thresholds set by the user or organization, thereby enhancing planning accuracy. {% content-ref url="/pages/eZPHUerv8lz5aKlXvp41" %} [Local-Flight](/nova/missions/results/cast/local-flight) {% endcontent-ref %} {% content-ref url="/pages/1KvDkbxZ8qUkZawf8Y5h" %} [Multi-Location](/nova/missions/results/cast/multi-location) {% endcontent-ref %} {% content-ref url="/pages/9YI7JgN5482O5SfDjBwh" %} [Route](/nova/missions/results/cast/route) {% endcontent-ref %} # Local-Flight CAST evaluation for a Local-Flight mission. In CAST, the weather conditions are displayed for a one-week period, with the visualization method remaining the same as in AWARE.

Weather condition summary

Clicking on the graphic leads to the parameter values, shown in corresponding graphs that are explained in more detail under [Local-Flight](/nova/missions/results/aware/local-flight) in AWARE. # Multi-Location CAST evaluation for a Multi-Location mission. In the case of multiple flight locations, flight locations are listet one below the other, just like in AWARE.

Listed locations

The evaluations also stays the [same as in AWARE](/nova/missions/results/aware/multi-location). # Route CAST evaluation for a Route mission. As with a route in AWARE, the takeoff, en-route, and landing evaluations are listed one after the other and the flight duration and remaining energy are displayed in charts.

Weather condition summary

How to interpret these has already been explained under [Local Flight](/nova/missions/results/aware/local-flight) in AWARE. # Maps Description of the NOVA maps and functions. NOVA's maps serve as a secondary reference for weather data in addition to the parameter overview and as a visual aid. The pilot/flight planner can: * Compare the sources and verify the information * Gain an almost real-time overview of weather conditions through radar and satellite data For all [mission types](/nova/missions) in the [NOW](/nova/missions/results/now) and [AWARE](/nova/missions/results/aware) evaluations, the map appears on the right side. It displays flight locations, routes, the nearest airports and can overlay various weather conditions within a set time frame. ## Icons [Flight locations](/nova/missions/types/local-flight) are displayed as blue waypoints, both in NOW and AWARE. When there are [multiple flight locations](/nova/missions/types/multi-location), they are numbered in sequence. [Routes](/nova/missions/types/route) are shown as green straight lines with matching-colored start and endpoints. Waypoints along a route are displayed in dark green. The nearest airports are also marked with an icon.
Single locationFlight locations are displayed as a blue dot./files/JezoelanXSrin5b0oDme
Multiple locationsMultiple flight locations are numbered in sequence. Selected locations will appear as big./files/m8lOtE6upxgkbjiIqu3q
Flight route with waypointFlight routes are shown as green lines with a start and end point. Waypoints along a route are displayed in dark green./files/oJd721hiITaAuZVkVQpa
Takeoff locationStarting point of a route./files/gtvI58JccX3rDUfTmYBT
Landing locationEndpoint of a route./files/tiplT5WXYxPzhsQmevRC
AirportThe nearest airports are marked with an icon and providing METAR/TAF information. Selected airports are displayed as dark./files/Sta0QeKESwhjzZbjhkXD
## Timeline / Slider The timeline at the bottom of the map allows weather conditions to be retrieved at various points in time. Selecting a specific time updates both the parameter overview values and the representation of weather conditions on the map. In [NOW](/nova/missions/results/now) and [AWARE](/nova/missions/results/aware), the timeline is accessible, but they differ in terms of the retrievable time frame. NOVA Now is designed to provide current data for making decisions about whether a flight can take place at that moment. Therefore, it is limited to a time frame of -1 to +2 hours.

NOW time window

AWARE focuses on a 2-day period, therefore the slider extends to a 48-hour time frame.

AWARE time window

## Weather layers Currently, six different layers are available: Radar, Total Cloud Cover, Temperature, Wind Barbs, Wind Speeds, and Precipitation. {% tabs %} {% tab title="Radar" %}

Radar view

The weather radar displays precipitation areas globally. From this, the intensity, type, and movement of precipitation can be determined. Depending on the type of precipitation, there are different intensity scales ranging from low (left) to high (right) values:

Rain [dbz]

Snow [dbz]

Ice [dbz]

{% endtab %} {% tab title="Total Cloud Cover" %}

Total cloud cover view

This layer displays the cloud cover. White areas represent clouds. The wind particles indicate the wind direction and turbulence. {% endtab %} {% tab title="Temperatures" %}

Temperature view

The temperature layer provides a visual representation of global temperatures using a gradient color scale.

Temperatures [°F]

{% endtab %} {% tab title="Wind Barbs" %}

Wind barb view

The wind barb layer provides a detailed view of wind dynamics by displaying wind direction, speed, and turbulence through overlaid wind particles and wind barbs. {% endtab %} {% tab title="Wind Speeds" %}

Wind speed view

The wind speed is represented using a color scale, ranging from dark blue for light breezes to red for strong winds.

Winds [mph]

{% endtab %} {% tab title="Precipitation" %}

Precipitation view

Precipitation from rainfall is depicted as light green areas. {% endtab %} {% endtabs %} ## Fullscreen map Using the fullscreen function of the map, you can get a better visual overview of your mission. You can find it via the arrow icon in the upper right corner of the map window.

Fullscreen Icon

Within the fullscreen view, you can switch between NOW and AWARE using the view tabs at the top center of the display.

View tabs

# Teams Why use the teams feature? How to create, edit, and delete teams. How to assign them to missions, and how filtering by team behaves across the platform. As your operations expand, clarity and efficient mission assignment become increasingly important. The **Teams Feature** helps to reduce complexity when dealing with a large number of concurrent missions. In environments where multiple flight departments, customers, or geographic regions are managed within the same NOVA organization, the mission list can grow quickly and become difficult to navigate. By assigning missions to teams, each user only sees the missions that are relevant to their specific responsibilities. This keeps the mission overview clean and manageable, avoids unnecessary distractions, and helps ensure that teams stay focused on what matters to them. NOVA's **Teams Feature** allows you to: * [Create](#creating-a-team) distinct teams within your organization. * [Assign](#assigning-a-team-to-a-mission) specific missions to these teams. This capability significantly improves operational clarity and simplifies the use of NOVA in dynamic environments, whether you have multiple flight operations across different geographies or various use cases. ## Managing Teams in NOVA To access the Teams management view, open Settings from your user profile in the top-right corner and select **Teams** under the User Management section.

Teams Management View

{% tabs %} {% tab title="Creating a Team" %} 1. Click **`+ NEW TEAM`**. 2. Enter a **name** for the team. This step is required. 3. Add users by clicking the plus icon next to their names. {% hint style="info" %} You can omit assigning members to a team. This can be useful for setup or automation purposes. {% endhint %} {% endtab %} {% tab title="Editing a Team" %} 1. Select the team to edit in the list by clicking on it. 2. Click the pencil icon to update the name or change its members. 3. Use the minus icons to remove users or add new ones from the available list. 4. Click Update to save your changes. {% endtab %} {% tab title="Deleting a Team" %} 1. Select the team to delete in the list by clicking on it. 2. Click the trashcan icon. 3. Confirm deletion in the dialog. {% hint style="info" %} When a team is deleted, Missions previously assigned to that team are automatically unassigned. {% endhint %} {% endtab %} {% endtabs %} ## Assigning a Team to a Mission Once teams are created, you can assign them to missions either during mission creation in the mission wizard or when editing an existing mission. ### Mission Wizard When you create a new mission using the [mission wizard](/nova/get-started/create-a-new-mission), the team can be assigned in the final step of the setup process. Use the **Team** dropdown to select the appropriate team before completing the wizard. ### Mission Edit Dialog To assign or update the team on an existing mission: 1. Open the [mission overview](/nova/missions#nova-mission-overview), select the appropriate mission and click the pencil button. 2. In the **Edit Mission** dialog, select the team you want to assign in the team selector. 3. Save the changes. ## Mission Visibility and Filtering The mission list in NOVA can be filtered to show only the missions relevant to a user's team. This helps reduce complexity on the missions view, especially in environments with many active missions or shared operations. The filter options are: * My Missions (default view): Shows all missions assigned to teams where the user is a member. * Team Views: Shows the missions from one team only. Only teams where the user is a member are selectable. * Unassigned Missions: Mission that have not been assigned to any team. * All Missions: All missions in the organisation. {% hint style="info" %} If you do not use teams and have no teams assigned to the current user, the "My Missions" filter will fallback to All Missions. {% endhint %} {% hint style="info" %} When a filter is cleared, the view returns to **My Missions**. This ensures users always see a relevant and scoped list by default. {% endhint %} # Assets What is the purpose of assets in NOVA? What asset types exist? How to use the asset manager? Assets in NOVA are reusable, configurable components that define key mission parameters such as aircraft type, aircraft performance, operational limits, and flight route. They form the foundation of the NOVA platform, enabling efficient flight operation management. Every mission in NOVA is built using assets, ensuring consistency and easy updating. This approach simplifies mission planning, ensures accuracy, and keeps your operations adaptable to changes. There are the following asset types:
Asset TypeDescription
Aircraft Type
Corresponds to the "model" or "type certificate" of the aircraft, like DJI Mavic Pro, Rigitech Eiger, or Airbus A320.
Read more
Performance Set
The performance of the aircraft type: speeds, climb rate, or endurance.
Read more
Aircraft Type Limit SetLimit sets that are specific to the capabilities of the aircraft type. These can be weather-related or performance-related factors.
Read more
Operational Limit SetParameters defined in the operational rules that specify the conditions under which the mission can take place.
Read more
RoutePlanned 3D flight route based on waypoints with defined latitude, longitude, and altitude above ground level.
Read more
LocationLocations (latitude and longitude) that generally define where the mission takes place without specifying an explicit route.
Read more
Sensor (Weather Station)Under Sensor you can add/remove weather stations to your organization and make their current observations visible in a mission. (Read more, soon)
## NOVA Asset Manager The NOVA Asset Manager organizes all you assets in a central place. The asset manager enables you to view, create, edit and remove assets. The asset manager shows a table of existing assets, grouped by asset type. The table includes the asset's name, its type, whether or not the asset is used in missions ("Assigned" column), and information about the latest modification of the asset. You can search for asset names through the search bar in the upper right corner. {% tabs %} {% tab title="NOVA Asset Manager" %}
A screenshot of NOVA Asset Manager within NOVA Operations Platform
{% endtab %} {% tab title="Groups collapsed" %}
A screenshot of NOVA Asset Manager with conveniently collapsed asset groups
{% endtab %} {% tab title="Asset selected" %}
A screenshot of NOVA Asset Manager with a specific asset selected from the list.
{% endtab %} {% tab title="Info Sidebar" %}
A screenshot of NOVA Asset Manager with a specific asset having all of its info details shown in the sidebar
{% endtab %} {% endtabs %} By clicking on an asset type group, it can be expanded or collapsed (see [screenshot](#groups-collapsed)). By clicking on an asset, it can be selected and then modified or deleted. (see [screenshot](#asset-selected)) To use the asset through the [Unisphere API](/unisphere-apis), copy its unique identifier. The information button on the top right opens the sidebar with more information about a selected asset (see [screenshot](#info-sidebar)). Clicking opens a dialog to create a new asset. The dialog guides you through the creation process based on the asset type you select.
A screenshot of NOVA Asset Manager when creating a new asset - a dialog with various asset options.

Create asset dialogue

# Aircraft Type Aircraft type used in the mission The aircraft type asset contains information needed to consider the aircraft in the flight simulation. The aircraft type asset represents an aircraft "model" or "type certificate", like a DJI Mavic Pro, Rigitech Eiger or Airbus A320. ## Aircraft Type Dialog You can create or modify aircraft type assets in the aircraft type dialog from the [NOVA Asset Manager](/nova/assets#nova-asset-manager). The dialog allows you to provide a name and to select the aircraft type ([Fixed-wing](#fixed-wing), [Multicopter](#multicopter), [Hybrid](#hybrid)).

Aircraft type dialog

Optionally, the dialog allows you to link the following assets to the aircraft type: * **Performance Set**\ The performance of the aircraft type: speeds, climb rate, or endurance. This is needed to perform flight simulations along a defined route.\ [Read More](/nova/assets/performance-set) * **Aircraft Type Limit Set**\ Limit sets that are specific to the capabilities of the aircraft type. These can be weather-related or performance-related factors.\ [Read more](/nova/assets/limit-set#aircraft-type-limit-set) *** ## Fixed-wing A fixed-wing aircraft that relies on aerodynamic wings for passive lift, e.g., a conventional airplane. They can stay in the air longer, carry heavier payloads, and exhibit better power efficiency.\ Control surfaces built into the wing (such as rudders, elevators, and ailerons) enable rotation around three perpendicular axes: vertical (yaw), lateral (pitch), and longitudinal (roll). ## Multicopter Multicopter, or Multi-Rotor, drones have more than two rotors (typically three, four, six, or eight). The most common types are: Quadcopters with four rotors, hexacopters with six rotors, and octocopters with eight rotors. Multi-rotor drones are versatile and widely used for various applications, including mapping, surveillance, and photography. ## Hybrid These aircraft feature a combination of rotors and fixed wing and thus merge the benefits of fixed-wing and multicopter designs, offering both endurance and vertical capabilities. This may be achieved by tilting rotors (“vectored thrust”) or independent sets of rotors that point in different directions (“lift and cruise”) *** You can find out more about drone types on the EASA website: {% embed url="" %} # Performance Set Description of the "performance set" asset. This asset provides data on the aircraft performance for the trajectory simulation. It is required to enable the simulation and evaluation of a route mission. {% hint style="success" %} For even higher simulation precision, Unisphere can provide fine-grained custom performance models based on flight telemetry data. For more information, contact our engineering team: {% endhint %} ## Performance Set Dialog You can create or modify performance sets in the corresponding dialog from the [NOVA Asset Manager](/nova/assets#nova-asset-manager).

Performance set dialog

*** The following parameters are taken into account:
Cruise speed [GS/EAS] The speed at which an aircraft operates most efficiently during the main phase of flight.
Max speed [EAS] The maximum speed an aircraft can safely reach under normal operational conditions.
Rate of climb The vertical speed at which an aircraft can ascend, typically measured in feet per minute (ft/min) or meters per second (m/s). It indicates how quickly an aircraft gains altitude and is vital for assessing the performance during takeoff and initial climb phases.
Rate of descent The vertical speed at which an aircraft descends, expressed in ft/min or m/s.
Endurance The total amount of time a drone can remain airborne, determined by battery capacity and power consumption rate under specific conditions.
{% hint style="info" %} **EAS (Equivalent Airspeed)**: The aircraft's speed relative to the air, corrected for altitude and temperature.\ **GS (Ground Speed)**: The aircraft's speed over the ground, affected by wind. {% endhint %} {% hint style="info" %} The performance set is considered only in the evaluation of route missions. Local and multi-location missions ignore the performance set. {% endhint %} # Limit Set Description of the "Aircraft type limit set" and "operational limit set". A limit set is a collection of weather parameters that define the operational boundaries for a mission. The limit sets are the basis for the evaluation of weather parameters within NOVA Now, Aware or Cast. There are two types of limit sets: [Aircraft Type Limit Sets](#aircraft-type-limit-set) for inherent aircraft limitations and [Operational Limit Sets](#operational-limit-set) for limits imposed by the operation. They have different uses, but the same setup process. ## Limit Set Dialog You can create or modify limit sets in the corresponding dialog from the [NOVA Asset Manager](/nova/assets#nova-asset-manager). Parameters considered in the limit set are shown on the left side of the dialog. A searchable selection of available [parameters ](/unisphere-apis/explanatory-notes/available-parameters)is given on the right side. You can add parameters to the limit set using the "+" button.

Limit set configuration

*** ## Aircraft Type Limit Set The aircraft type limit set defines operational boundaries based on the aircraft specifications (aircraft spec sheet). These limits apply to a specific aircraft type (e.g. "DJI Mavic 2 Pro") and include hardware, weather, and performance-related factors that determine the aircraft's operational capabilities. An aircraft type limit set can be assigned to an [aircraft type ](/nova/assets/aircraft-type)asset. ## Operational Limit Set The operational limit set defines boundaries based on operational considerations, typically outlined in the Concept of Operations (ConOps). These limits specify the conditions under which a mission can be performed. An operational limit set can be assigned to a [mission](/nova/missions). {% hint style="info" %} Operational limit sets may include the same parameters as aircraft type limit sets. In such cases, the NOVA evaluation algorithm automatically applies the most restrictive limits. {% endhint %} ## Parameter Thresholds Each weather parameter can be given thresholds that define **nominal**, **moderate**, or **severe** conditions. Nominal conditions are generally safe for flying. Moderate conditions are intermediate and require further assessment. Severe conditions are those where safe flights are not possible. Parameter limits can be configured using four different [limit thresholds](/nova/assets/limit-set/limit-thresholds-types) types: * High-red: high values are severe * Low-red: low values are severe * Middle-green: both extreme values are severe with a nominal window in the middle * Middle-red: extreme values are nominal, while a middle range is severe Thresholds with corresponding units can be set at the transitions between value ranges. {% hint style="warning" %} For each parameter, Unisphere provides initial suggestions for the threshold configuration. Make sure to update these values according to your aircraft specifications or concept of operations. {% endhint %} ## Parameter Altitude Most parameters can be evaluated at a specific altitude, for example wind speed at 10 m above ground level. The altitude for each parameter is configured in the [Limit Set dialog](#limit-set-dialog). To evaluate the same parameter at multiple altitudes, create separate entries for the parameter and assign a different altitude to each entry. Altitude definitions are used for [Single-Location](/nova/missions/types/local-flight) and [Multi-Location](/nova/missions/types/multi-location) mission types. For [Route](/nova/missions/types/route) missions, the altitudes in the limit set are ignored and the altitude is taken directly from the [Route](/nova/assets/locations-and-routes#route) asset.

Same parameter used two times at different heights

## Flight Phases You can define different limits for different flight phases. For example, you may want to provide stricter wind speed limits for takeoff and landing than during the cruise phase. A parameter that you add to your limit set can be assigned for the entire mission or specifically for each phase: takeoff, en-route, and landing by selecting the corresponding tab in the limit set dialog.

Applicable limits per phase of flight

# Limit thresholds types
Evaluation SchemeUsage
HIGH-REDCriticality in the upper value range. Typically used for wind speed, thunderstorm prob. and icing potential.
HIGH-GREENCriticality in the lower value range. Typically used for visibility and the lifted index.
MIDDLE-REDCriticality in the middle value range. E,g, avoiding low spread.
MIDDLE-GREENCriticality at the boundaries of the value range. Typically used for temperature.
# Weather and Operational Parameters Available parameters in NOVA. Limit parameters define the environmental and atmospheric conditions under which an operation can safely take place. They are used in **limit sets** to automatically evaluate weather conditions and determine whether a mission can be executed safely. Two types of limit sets exist:
Limit set typeDescription
Aircraft type limit setDefines the technical and physical limitations of the aircraft itself. These limits typically come from manufacturer specifications or certification documents.
Operational limit setDefines mission-specific operational rules. These limits may come from regulations, company procedures, payload constraints, or risk assessments such as SORA.
Some parameters can be used in **both** types of limit sets, while others are only relevant for **operational rules**. ## Wind | Parameter | Description | Aircraft type limit set | Operational limit set | | ----------- | ------------------------------------------------ | :---------------------: | :-------------------: | | Wind speed | Mean wind speed over a 1 hour interval | ✓ | ✓ | | Wind gusts | Maximum wind gusts within a 1 hour interval | ✓ | ✓ | | Gust factor | Difference between peak gust and mean wind speed | ✓ | ✓ | ## Temperature & Humidity | Parameter | Description | Aircraft type limit set | Operational limit set | | ----------------------- | -------------------------------------------------------- | :---------------------: | :-------------------: | | Outside air temperature | Mean outside air temperature over a 1 hour interval | ✓ | ✓ | | Dew point | Mean dew point temperature | ✓ | ✓ | | Relative humidity | Mean relative humidity within a 1 hour interval | | ✓ | | Spread | Difference between outside air temperature and dew point | ✓ | ✓ | ## Clouds & Visibility | Parameter | Description | Aircraft type limit set | Operational limit set | | ------------------ | ------------------------------------------------------------------- | :---------------------: | :-------------------: | | Visibility | Horizontal visibility at ground level | | ✓ | | Cloud ceiling | Height of the lowest cloud layer covering more than half of the sky | | ✓ | | Cloud base | Lowest altitude of the visible portion of a cloud | | ✓ | | Cloud cover low | Cloud coverage between 0–2 km above ground level | | ✓ | | Cloud cover medium | Cloud coverage between 2–7 km above ground level | | ✓ | | Cloud cover high | Cloud coverage between 7–10 km above ground level | | ✓ | | Cloud cover total | Fraction of the sky covered by all clouds | | ✓ | ## Precipitation & Snow | Parameter | Description | Aircraft type limit set | Operational limit set | | -------------------- | ----------------------------------------------------- | :---------------------: | :-------------------: | | Precipitation | Accumulated precipitation over a 1 hour interval | ✓ | ✓ | | Precipitation prob. | Probability of precipitation during a 1 hour interval | ✓ | ✓ | | Snow depth | Depth of snow on the ground | ✓ | ✓ | | Snowfall probability | Probability of snowfall | ✓ | ✓ | | Fresh snow 24h | Accumulated fresh snow within the last 24 hours | ✓ | ✓ | ## Atmospheric Stability | Parameter | Description | Aircraft type limit set | Operational limit set | | ------------------ | ------------------------------------------------------------------------------ | :---------------------: | :-------------------: | | CAPE index | Convective Available Potential Energy index indicating atmospheric instability | ✓ | ✓ | | Lifted index | Atmospheric instability indicator based on parcel lifting | ✓ | ✓ | | Thunderstorm prob. | Probability of thunderstorms within a 1 hour interval | | ✓ | ## Icing & Radiation | Parameter | Description | Aircraft type limit set | Operational limit set | | ---------------- | ------------------------------------------------------------------------- | :---------------------: | :-------------------: | | General icing | Indicator for possible icing conditions based on temperature and humidity | ✓ | ✓ | | Icing potential | Forecast probability and intensity of icing conditions | ✓ | ✓ | | Global radiation | Total solar radiation at ground level | ✓ | ✓ | ## Space Weather | Parameter | Description | Aircraft type limit set | Operational limit set | | --------- | ---------------------------------------------------------- | :---------------------: | :-------------------: | | KP index | Geomagnetic disturbance index that may affect GNSS signals | ✓ | ✓ | # Locations & Routes Description of the "Location" and "Route" asset. Location and route assets define where the mission takes place. Both types of assets can be created or edited through the [NOVA Asset Manager.](/nova/assets#nova-asset-manager-1) ## Location (Local Flight) Flight locations for creating a location asset can be defined by entering longitude and latitude coordinates or by clicking on the map and saving.
## Location (Analytics) Analytics locations are defined in the same way as locations for local flights and listed in the NOVA Asset Manager. These locations are used for [Operational Analytics](/operational-analytics). ## Route Route assets represent a 3D flight route defined by waypoints, each with a latitude, longitude, and altitude above ground level (AGL). Routes can be created by clicking on the map, or by uploading a file in **KML**, **PLAN** or **WAYPOINTS** format using the `UPLOAD FLIGHT PLAN` button. {% tabs %} {% tab title="New Route Dialog" %}
{% endtab %} {% tab title="Uploaded Route" %}
{% endtab %} {% endtabs %} When an external file is uploaded, the route is automatically loaded from its data (see [External file creation](#external-file-creation)). If altitude information is not provided in the file, you may add altitude data to the waypoints manually (see [Uploaded Route](#uploaded-route)). Other modifications of the uploaded route are prevented by NOVA. If you add waypoints manually, you may add waypoints at the start or the end of the route and also in between existing waypoints. You need to specify the altitude (AGL) at each waypoint, which is set to 0 initially. {% hint style="info" %} For convenience, the altitude provided for a waypoint is copied to following waypoints for which the altitude is not specified. {% endhint %} ### External file creation #### Within NOVA Routes created in NOVA can be downloaded in **KML**, **PLAN** or **WAYPOINTS** format. This is useful for re-creating the route in the future. This option is available when creating a mission and selecting an asset. {% tabs %} {% tab title="Download button" %}

Download file button within the route dialog

{% endtab %} {% tab title="Select file type" %}

Type selector within the Download file dialog

{% endtab %} {% endtabs %} #### External Tools External tools like Google Earth, Q Ground Control or Mission Planner can also be used to create route files. Instructions for Google Earth can be found [here](https://support.google.com/mapcontentpartners/answer/15179231) (external link). #### Custom Tools *KML format* If you create **KML** files via a custom tool, please make sure to follow the KML standard. We expect that the route waypoints are provided within a ``, which is expected to include an altitude reference and coordinates of the route. A minimal example is given below. Currently, NOVA supports `relativeToGround` and`absolute`as`altitudeMode.` ```xml UP Testflight relativeToGround 9.043341388041267,47.69550904610872,0 9.047137141960924,47.70110577505493,0 9.058338444737204,47.71563827282183,0 9.074422557057218,47.73446327224831,0 9.116350330267624,47.73941175803014,0 ``` *PLAN format* If you create **PLAN** files via a custom tool such as Q Ground Control, please make sure that the file includes at least the following structure: 
{
    "mission": {
        "globalPlanAltitudeMode": 1,
        "items": [
            {
                "command": 22,
                "params": [0, 0, 0, null, 47.677707517028885, 9.142380633125526, 50],
                "type": "SimpleItem"
            },
            {
                "command": 16,
                "params": [0, 0, 0, null, 47.6850874, 9.14829407, 50],
                "type": "SimpleItem"
            },
            {
                "command": 16,
                "params": [0, 0, 0, null, 47.67883124, 9.16569647, 50],
                "type": "SimpleItem"
            }
	]
    }
}
*WAYPOINTS format* If you create WAYPOINTS files via a custom tool such as Mission Planner, please make sure that the file includes at least the following structure: ``` QGC WPL 110 0 1 0 0 0 0 0 0 0 0 0 1 1 0 0 16 0 0 0 0 47.672 9.170 100.000 1 2 0 0 16 0 0 0 0 47.676 9.156 100.000 1 3 0 0 16 0 0 0 0 47.672 9.149 100.000 1 4 0 0 16 0 0 0 0 47.665 9.161 100.000 1 5 0 0 16 0 0 0 0 47.664 9.178 100.000 1 ``` #### Altitude conversion NOVA automatically detects if an uploaded file uses an altitude mode other than AGL. When detected, NOVA will offer to convert the altitude values from **AMSL** to **AGL**, which is the default mode for all routes.

Calculate altitudes button within the Upload Flight Plan dialog

# Weather Stations Weather station integration into NOVA The NOVA platform provides a robust **Weather Station Integration** feature designed to enhance situational awareness and decision-making capabilities for drone operators. This feature enables users to connect their own weather stations or utilize existing weather observation systems to gather real-time meteorological data critical for flight planning and operation. By integrating with various weather sensors, including aviation-grade and consumer-grade setups, the NOVA platform ensures accurate, up-to-date weather information is available for analysis. This integration supports better mission planning, operational safety, and compliance with regulatory requirements. **What Does the Weather Station Integration Do?** * [**Connect Weather Stations**](/nova/weather-stations/connect)\ Integrate weather stations for use in NOVA * [**Overview of Connected Weather Stations**](/nova/weather-stations/overview)\ NOVA displays connected weather stations as a list or on a map for a quick overview * [**Individual View of Weather Station**](/nova/weather-stations/individual-view)\ View live data streams from connected weather sensors * [**Mission Integration**](/nova/weather-stations/mission-integration)\ Get weather station data directly into the mission view The **Weather Station Integration** feature is part of NOVA’s commitment to providing the best-in-class weather data for safe and efficient drone operations. By leveraging this feature, users can enhance their ability to make informed flight decisions based on the most accurate weather data available. {% hint style="info" %} To integrate weather stations, the NOVA weather station addon needs to be purchased. Reach out to . {% endhint %} # Connect How to connect new weather stations to NOVA If you have the weather station addon for NOVA, you may add weather stations directly into NOVA and view them individually or from within missions. {% hint style="info" %} Currently, only **Tempest** weather stations can be added by the user. For other weather station types and aviation-grade solutions, contact {% endhint %} ## How to Connect a Tempest Weather Station {% hint style="info" %} Before adding the weather station, make sure you have your **Tempest access token**, which is needed to access the weather station. {% endhint %} {% stepper %} {% step %} Navigate to the **Assets** page in NOVA. {% endstep %} {% step %} Click the `+ New Asset` button in the top right corner. {% endstep %} {% step %} From the menu, select `New Weather Station`

Select 'New weather station' from the asset creation dialog

{% hint style="info" %} If `New weather station` is not visible in your asset creation dialog, you are missing the weather stations addon. Contact to activate it. {% endhint %} {% endstep %} {% step %} In the `New Weather Station` dialog: * Select `New Tempest ONE Weather Station`. * Enter your Tempest access token. * NOVA will retrieve a list of weather stations linked to your Tempest account.

Enter you Tempest API to see a list of available weather stations

{% endstep %} {% step %} From the **weather stations list**: * Select the weather stations you want to integrate into NOVA. * Optionally, provide: * A custom station name. * Latitude and longitude coordinates (for accurate map display and mission association). * A station-specific mission radius. Missions you create in the future will pre-select weather stations if the mission is within the *station-specific radius*. You may override this in the mission wizard. {% endstep %} {% endstepper %} # Overview Overview of all weather stations currently connected Users can access the Weather Stations Overview by clicking the `Weather Stations` button located on the left-side console of the NOVA platform.

Weather stations selector in left console

This overview provides both a **Table View** and a **Map View**, allowing users to monitor and interact with all connected weather stations efficiently.

Toggle between Table View and Map View

## Table View The table displays a comprehensive list of all weather stations connected to the NOVA platform. For each station, the following information is provided: * **Current Status**: Indicates whether the station is currently online or offline. * **Coordinates**: Latitude and longitude of the weather station. * **Altitude**: Installation altitude of the station above sea level. Users can double-click on any station in the table to open the [Individual Weather Station View](/nova/weather-stations/individual-view), where detailed data are available.

Table View for Weather Stations

## Map View A visualization of all connected weather stations on a global map. * Clicking on a weather station icon opens a *Quick View*, which displays the current readings from that station. * The *Quick View* can be expanded to access the [Individual Weather Station Page](/nova/weather-stations/individual-view) for more detailed insights, including historical data and sensor-specific readings.

Map View for Weather Stations with Quick View Dialog

# Individual View Live data for individual weather stations The Individual Weather Station View provides users with a detailed real-time snapshot of meteorological data from a selected station. This view is accessed either by double-clicking a station in the table view or expanding a station's quick view from the map. The page is split into two sections: * A **Data Panel** on the left, showing live or recorded sensor readings. * A **Map Panel** on the right, indicating the station’s location and surrounding area.

Individual View of a Weather Station in NOVA

## **Map Panel** The map on the right provides geographic context and helps visualize nearby stations and terrain. Users can zoom and pan to explore the environment around the selected station, aiding spatial awareness during flight planning. It includes all weather layers available in NOVA map views. ## **Data Panel** The data panel allows access to live or recorded sensor readings. Use the switch at the top of the Data Panel to access one or the other.

Switch between live (left) and recorded (right) weather readings

### Live Sensor Readings The data panel prominently displays all live sensor readings, including: * **Wind**: Direction and speed over different time intervals: * 2-minute average * 10-minute minimum and maximum * **Pressure**: Atmospheric pressure at station altitude * **Temperature**: Current temperature, dew point, and spread * **Relative Humidity** * **Precipitation**: Duration and accumulation stats The update frequency of this information complies with the standards outlined in ICAO Annex 3, section 4.1.3.1. The wind data is updated with a frequency of 10 s, and all other readings are updated at a rate of 60 s. Data retrieval can be paused and resumed again by clicking on the corresponding buttons on the top right of the data panel. ### Recorded Sensor Readings Historical data is available for the current day (24-hour period in UTC). The graphs indicate the respective values measured by the weather stations. Wind directions are indicated as arrows within the graph. Wind speed and wind direction data include the 10-minute maximum and minimum values. Historical data can be downloaded as JSON or CSV file by clicking in the download button. # Mission Integration Integration of weather station data into the NOW view in a mission The Mission Integration feature allows users to associate connected weather stations with flight missions in NOVA. This enables operators to compare live local weather data with model forecasts and radar data.

Live data from weather station shown within NOVA Now

## Assigning Weather Stations to a Mission Weather stations can be associated with a mission [during mission creation](#during-mission-creation) or by [editing an existing mission](#editing-an-existing-mission). ### During Mission Creation When creating a new mission through the [**Mission Wizard**](/nova/get-started/create-a-new-mission)**:** {% stepper %} {% step %} Proceed through the mission wizard until you reach the **Assign weather stations** section. {% endstep %} {% step %} NOVA will automatically pre-select weather stations that are close to the mission location based on the *station-specific radius*. The station-specific radius is selected when connecting the weather station.
You can manually override this pre-selection and select a specific weather station by clicking `SHOW ALL WEATHER STATIONS` and selecting weather stations that are further away. {% endstep %} {% endstepper %} ### Editing an Existing Mission To add a weather station to an existing mission: {% stepper %} {% step %} Locate the mission in your missions list. {% endstep %} {% step %} Select the mission and click **edit mission** to modify the mission settings. {% endstep %} {% step %} In the edit mission dialog, add a weather station in the corresponding select box.
{% endstep %} {% endstepper %} # Vertiport What is NOVA Vertiport? How can you integrate a Vertiport to NOVA? NOVA Vertiport is an application within the NOVA Platform to enable a centralized management of different Vertiports, designed for Remote Operations by combining local sensor and best-in-class weather forecast data. ### Real-Time Situational Awareness for Vertiports To provide you with a high level of situational awareness of the weather impact on your Vertiport network or individual vertiport, we combine the deployment of [weather sensors](/nova/weather-stations) with access to radar and lighting information in a single view. Automated interpretation allows monitoring multiple locations in parallel, eliminating cognitive overload. ### Learn from historical data aggregated at each vertiport location In addition to looking ahead, we collect and store the weather data collected by the deployed sensors. Combined with our experience in data analytics, we provide operational insights to optimize your operations and learn for future network expansion. **What Does NOVA Vertiport Do?** * [**Setup Vertiports**](/nova/vertiport/setup)\ Integrate your Vertiport for use in NOVA * [**Overview of Integrated Vertiports**](/nova/vertiport/overview)\ NOVA displays a list of your integrated Vertiports * [**Individual View of Vertiport**](/nova/weather-stations/individual-view)\ View historical, live and forecast data for your Vertiport {% hint style="info" %} To integrate weather stations, the NOVA weather station addon needs to be purchased. Contact . {% endhint %} # Setup How can you set up a vertiport and use it in NOVA? ## Add a new Vertiport to NOVA To add a new vertiport, navigate to the [Vertiport overview list](/nova/vertiport/overview) in the NOVA main menu. In this window, your Vertiports are listed, provided you have created any. To create a vertiport, click the `New Vertiport` button on the upper right corner of the page and complete the following 4 steps. {% stepper %} {% step %} ### Add General Vertiport Details ![](/files/G0H1nLkxeFI8pcO7lGWS) First, you can define the general vertiport details which include a Name, the coordinates and elevation (AGL) of the vertiport. Additionally if the Vertiport is part of a network, you can also assign the respective network via the dropdown menu or adding a new network by writing the name into the field. {% endstep %} {% step %} ### Define Tracks (optional) In the next step, which is optional, you can set up the different tracks for the vertiport. A track is defined with a type (approach or departure) and a direction. Two different references are available for the direction specification: Magnetic or True North. {% hint style="info" %} Magnetic North is the direction a compass points, shaped by Earth’s shifting magnetic field, while True North is the fixed geographic North Pole used for accurate mapping and navigation. Runway numbers are in general based on magnetic headings. To provide the values for the specified Vertiport location the **World Magnetic Model High Resolution (WMMHR)** of **NOAA** is used. {% endhint %}
{% endstep %} {% step %} ### Assign Sensors (Optional) In the following window weather stations can be associated with a Vertiport. NOVA will automatically preselect [weather stations](/nova/weather-stations) that are close to the mission location based on the *station-specific radius*. The station-specific radius is selected when [connecting](/nova/weather-stations/connect) the weather station. In addition, there is the option of integrating a METAR as a source of measurement data for the vertiport.
{% endstep %} {% step %} ### Define organisational operational limits (Optional) In this window, you can now enter your operational limits. For the vertiport application two different limits set types are available for assignment. On one hand, there are general operational limits; on the other, track-specific wind limitations (cross-, tail-, and headwind) applied for all tracks of the vertiport. In the respective tab you can upload a[ limit set ](/nova/assets/limit-set)from your [assets](/nova/assets). Additionally you can create a new limit set or generate an example limit set.
{% endstep %} {% step %} ### Create Vertiport By clicking the `CREATE Vertiport` button, your vertiport will be set up. {% endstep %} {% endstepper %} # Overview Overview of all Vertiports integrated in NOVA Users can access the Vertiport Overview by clicking the `Vertiport` button located on the left-side console of the NOVA platform.
## Table View The table displays a comprehensive list of all vertiports integrated into the NOVA platform. For each vertiport, the following information is provided: * **Name** – The vertiport title, with an optional description preview * **Network** – If the Vertiport is part of a Vertiport Network, the respective name is shown in the list * **Modified** – The last modified date and the user who updated it Users can double-click on any Vertiport in the table to open the [Individual Vertiport View](/nova/vertiport/individual-view), where detailed data are available.

Table View for Vertiports

# Individual View Historic, Live and Forecast data for individual Vertiports in one place ## General Information The individual Vertiport View provides users with detailed meteorological real-time data, but also with forecast and historical data from a selected vertiport. This view is accessed either by double-clicking a station in the [table view](/nova/vertiport/overview) or expanding a station's quick view from the map. The page can be split into two sections: * A **Data Panel** on the left, showing [live](#live-view) or [recorded](#historic-view) sensor readings. Furthermore in [Forecast View](#forecast-view) forecast model data can be accessed. * A **Map Panel** on the right, indicating the vertiport’s location and surrounding area. The Map panel can be enabled with the map button in the top-right corner of the page.

Individual view for Vertiports (Data Panel)

The slider at the bottom of the page allows weather conditions to be retrieved at various points in time. Selecting a specific time updates both the parameter overview values and the representation of weather conditions on the map. Depending on the adjustments with the slider the view is either in [live](#live-view), [historic](#historic-view) or [forecast](#forecast-view) mode. The filled green `live` button above the slider marks the current Live view. Pressing the button returns the view to live mode. ## Live View In the live view, weather sensor data streams are displayed on the left side of the application. When entering the Vertiport page by default the live mode is active. The parameters shown in the data panel depend on the availability provided by the connected weather sensor. The update frequency of this information complies with the standards outlined in ICAO Annex 3, specifically in section 4.1.3.1, ensuring accurate and timely data presentation. {% hint style="info" %} Wind directions are referenced to **True North** **True North** (also called geographic north) is the direction pointing toward the Earth’s geographic North pole {% endhint %} | Value Displayed | Description | Update Rate | | -------------------------------------------------- | ------------------------- | ----------- | | Wind direction and intensity information (min/max) | rolling 2-minute average | 10s | | Wind minimum / maximum | rolling 10-minute average | 10s | | Pressure | - | 60s | | Temperature | - | 60s | | Precipitation | - | 60s | | Hail | - | 60s | | Humidity | - | 60s | | Visibility | - | 60s | | METAR & TAF information | - | 60s | In the map section of the application, users can access real-time precipitation radar data. This radar information is augmented by current wind predictions, projecting conditions up to 120 minutes into the future at 15-minute intervals. Users can navigate through this forecast timeline using the slider located at the bottom of the interface, providing dynamic insights into upcoming weather patterns and conditions.

Live View NOVA Vertiport

## Historic View When the "24-Hour History" mode is selected, recorded weather observation data is accessible. These recorded parameters align with the information presented in the "live" mode, providing a comprehensive overview of past weather conditions within a 24-hour timeframe.

Historic View NOVA Vertiport

## Forecast View The 24-Hour Forecast offers insights into projected operational conditions for the upcoming 24 hours. Weather model data is used, providing a detailed overview of anticipated weather patterns and other relevant factors. Further details of each forecast period can be accessed by clicking the respective forecast bar.

Forecast View NOVA Vertiport

# Vertiport Meteorological Report (VMR) The VMR – Vertiport Meteorological Report is a METAR‑like, standardized weather report for vertiports. It is machine‑readable and designed to account for the fact that different vertiports operate with different [sensor tiers](/nova/vertiport/vertiport-meteorological-report-vmr/sensor-tiers). The VMR represents local, vertiport‑specific observational data and supplements METAR/TAF with precise vertiport information updated every 10 minutes starting on the hour (e.g 0600z). **VMR General Syntax** The VMR follows a similar METAR structure, and groups appear only if the respective [sensor tier](/nova/vertiport/vertiport-meteorological-report-vmr/sensor-tiers) provides them. {% code fullWidth="false" %} ``` // VMR [] [] [] [RMK] ``` {% endcode %} ## General Groups * **Product Name:** VMR (Vertiport Meteorological Report) * **Vertiport Id:** unique identifier for the Vertiport (e.g. VPBIC1) * **Date and Time** DDHHMMZ 061150Z 06 Day of month /11 hour/ 50 minute/ Z Identifier for UTC * **Further Abbreviation** **(AUTO)** Automated generated report ## Wind Group The structure of the wind group is the following: **dddffGggKT** The group consists of three elements: * **ddd** — Wind direction in degrees (000–360), indicating the direction *from which* the wind is blowing * **ff** — Mean wind speed in knots (10 minutes) * **Ggg** — Gust peak (gust), also in knots (published only when the maximum wind value exceeds the 10-minute mean wind speed by 5 knots) * **KT** — Unit “knots” **Example: 26010G18KT** * **260** → Wind is coming from 260° (west‑southwest) * **10** → Mean wind 10 kt * **G18** → Gust 18 kt * **KT** → Unit Knots ## Visibility Group Not available for TIER 1 Horizontal visibility in meters Value 9999 is shown if visibility is higher than 10 000m ## Cloud Group Not available for TIER 1 and TIER 2 ## Weather Codes TIER 1: WXT530 (Vaisala) Only the Rain (RA) weather code is available. ## Temperature and Dewpoint 03/02 03 Outside Air Temperature in °C /02 Dewpoint in °C 01/M02 01 Outside Air Temperature +1°C/M02 Dewpoint -2°C The following formula was implemented for the calculation:
## Calculated QNH This section explains how the sea‑level pressure value is derived from station pressure and elevation CALC Q1008 CALC Q Identifier for QNH in hPa Q1008 → QNH =1008 The following formula was applied for the calculation of the QNH: $$QNH \approx \left(QFE^{a} + b \cdot H\right)^{1/a}$$ $$a = 0.1902614$$ $$b = 8.417168 \times 10^{-5}\ \frac{hPa^{a}}{m}$$ ### Variables * **QFE** – Pressure at vertiport level * **H** – Vertiport elevation in meters $$QFE = P\_{0} + 0.034164 \cdot \Delta H \cdot \left(\frac{P\_{0}}{T}\right)$$ ### Variables * **ΔH** – Difference between the height of the barometer sensor \[m] and the aerodrome reference elevation (Aerodrome Elevation) \[m] (see AIP) * **P₀** – Measured air pressure at barometer height \[hPa] * **T** – Air temperature in Kelvin * T \[K]=273.15+t \[°C] ## Remarks Group The **Remarks** section provides **additional technical information** that does not fit into the standard METAR‑style groups. It uses a **structured key‑value format** to ensure the data remains machine‑readable and easy to parse. The published messages for TIER 1 are: NOT OFFICIAL NO\_VIS\_SENSOR; NO\_CLOUDS\_SENSOR; NO\_WX\_Codes; WX\_Code\_Rain\_Only # Sensor TIERS Vertiports differ in the type and number of meteorological sensors they install. To ensure consistent reporting across all configurations, the VMR uses a tiered sensor concept. Each tier defines which parameters are available and which VMR groups can be generated. Higher tiers extend lower ones by adding additional instruments and capabilities. This structure allows every vertiport—from minimal setups to fully equipped sites—to produce a standardized, aviation‑compatible weather report. ### **Tier 1 – WXT530 (Vaisala)** **Available parameters:** * Wind direction, wind speed, gusts * Temperature * Humidity (→ dew point can be derived) * Air pressure (QNH) * Precipitation intensity (no weather classification) ### **Tier 2 – WXT530 + PWD22** **Additionally available:** * Visibility (VIS) in meters * Weather codes (Present Weather) ### **Tier 3 – WXT530 + PWD22 + CL31** **Additionally available:** * Cloud bases and cloud cover (FEW/SCT/BKN/OVC) * Vertical visibility (VV) # Developers Guide Access vertiport sensor data programmatically via the NOVA REST API This guide is for developers who want to integrate NOVA vertiport data into external systems — for example, flight management software, analytics pipelines, or custom dashboards. ## Authentication All requests require a JWT bearer token issued. Contact your Unisphere representative to obtain credentials. Pass the token in the `Authorization` header: ```http Authorization: Bearer ``` ### Required Permissions | Goal | Permission | | --------------------------------- | -------------------------- | | List and read vertiports | `vertiport.vertiport.read` | | Read sensor data and observations | `vertiport.readings.read` | Contact your administrator if you receive `403 Forbidden` responses. ## Getting Sensor Data The typical workflow for reading sensor data from an external system: {% stepper %} {% step %} ### Find your vertiport ID List all vertiports in your organization to obtain the UUID of the target vertiport. ```http GET https://prod.unisphere.rocks/api/v1/vertiport/ Authorization: Bearer ``` ```json { "items": [ { "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6", "name": "Vertiport Berlin Mitte", "vertiport_code": "VPBIC1", "latitude": 52.520, "longitude": 13.405 } ], "total": 1 } ``` {% endstep %} {% step %} ### Discover available parameters Retrieve the metric keys available for your vertiport. The available parameters depend on which sensors are installed. ```http GET https://prod.unisphere.rocks/api/v1/vertiport/{vertiport_id}/parameters Authorization: Bearer ``` ```json [ { "sensor_id": "a1b2c3d4-...", "parameters": [ { "key": "air_temperature", "name": "Air Temperature", "unit": "°C" }, { "key": "wind_speed_average", "name": "Wind Speed (Average)", "unit": "m/s" }, { "key": "wind_direction_average", "name": "Wind Direction", "unit": "°" }, { "key": "air_pressure", "name": "Air Pressure", "unit": "Pa" }, { "key": "relative_humidity", "name": "Relative Humidity", "unit": "%" }, { "key": "rain_intensity", "name": "Rain Intensity", "unit": "mm/h" } ] } ] ``` Use the `key` values to filter responses in subsequent requests. {% endstep %} {% step %} ### Fetch data Choose the endpoint that fits your use case — see the sections below. {% endstep %} {% endstepper %} ## Data Endpoints ### Latest Observations Returns the most recent value for each metric across all sensors in the vertiport. Use this for live dashboards and status displays. ```http GET https://prod.unisphere.rocks/api/v1/vertiport/{vertiport_id}/latest-observations Authorization: Bearer ``` Filter to specific metrics using the `filter` query parameter: ```http GET .../latest-observations?filter=air_temperature,wind_speed_average ``` ```json [ { "sensor_id": "a1b2c3d4-...", "parameters": [ { "parameter": "air_temperature", "unit": "°C", "timestamp": "2026-05-27T12:00:00Z", "value": 18.4 } ] } ] ``` ### Historical Observations Returns raw time-series data. Defaults to the last 24 hours; maximum range is 30 days. ```http GET https://prod.unisphere.rocks/api/v1/vertiport/{vertiport_id}/observations ?start=2026-05-26T00:00:00Z &end=2026-05-27T00:00:00Z &filter=air_temperature,wind_speed_average Authorization: Bearer ``` ```json [ { "sensor_id": "a1b2c3d4-...", "parameters": [ { "parameter": "air_temperature", "unit": "°C", "observations": [ { "timestamp": "2026-05-26T00:00:10Z", "value": 14.2 }, { "timestamp": "2026-05-26T00:01:10Z", "value": 14.3 } ] } ] } ] ``` {% hint style="warning" %} For continuous data integration, poll on a **10–60 second interval** and request only the data since the last poll — for example, `?start=&end=`. The endpoint returns `416` if the requested range is too big. {% endhint %} {% hint style="info" %} There is currently no bulk data export endpoint. If you need a historical data export covering a larger time range, contact . {% endhint %} ### Aggregated Observations Returns time-bucketed statistics. Use this for trend charts, reports, or reduced-resolution data. ```http GET https://prod.unisphere.rocks/api/v1/vertiport/{vertiport_id}/aggregations ?start=2026-05-26T00:00:00Z &end=2026-05-27T00:00:00Z &bucket=1h &aggregation=avg,min,max &filter=air_temperature Authorization: Bearer ``` | Parameter | Required | Description | Examples | | --------------- | -------- | --------------------------------------- | ------------------------------------ | | `bucket` | Yes | Time bucket size | `15m`, `1h`, `1d` | | `aggregation` | Yes | Comma-separated functions | `avg`, `min`, `max`, `count`, `sum` | | `start` / `end` | No | ISO 8601 timestamps; default: last 24 h | — | | `filter` | No | Comma-separated metric keys | `air_temperature,wind_speed_average` | ```json [ { "sensor_id": "a1b2c3d4-...", "parameters": [ { "parameter": "air_temperature", "unit": "°C", "aggregations": [ { "timestamp": "2026-05-26T00:00:00Z", "avg": 14.5, "min": 13.1, "max": 16.2 } ] } ] } ] ``` ## Vertiport Meteorological Report (VMR) The VMR endpoint returns a structured aviation-compatible weather string (similar to METAR) for the vertiport. ```http GET https://prod.unisphere.rocks/api/v1/vertiport/{vertiport_id}/vmr Authorization: Bearer ``` ```json { "vmr": "VMR VPBIC1 270900Z AUTO 24006G12KT RA 08/04 CALC Q1016 RMK NOT_OFFICIAL;NO_VIS_SENSOR;NO_CLOUDS_SENSOR;WX_CODE_RAIN_ONLY", "tier": 1, "timestamp": "2026-05-27T09:00:00Z" } ``` The `tier` field indicates which sensor tier produced the report (see [Sensor Tiers](/nova/vertiport/vertiport-meteorological-report-vmr/sensor-tiers)). {% hint style="info" %} The VMR is computed once per 10-minute window. Subsequent calls within the same window return the cached result instantly. {% endhint %} {% hint style="warning" %} The endpoint returns `404` if the vertiport has no WXT536 sensor configured or if the vertiport elevation has not been set. Ensure both are configured before calling this endpoint. {% endhint %} See the [VMR reference](/nova/vertiport/vertiport-meteorological-report-vmr) for a full description of the string format and group definitions. ## Per-Sensor Access All data endpoints are also available scoped to a single sensor, useful when multiple sensors are installed at one vertiport and you need to distinguish between them. ```http GET .../vertiports/{vertiport_id}/sensors/{sensor_id}/latest-observations GET .../vertiports/{vertiport_id}/sensors/{sensor_id}/observations GET .../vertiports/{vertiport_id}/sensors/{sensor_id}/aggregations ``` These accept the same query parameters (`start`, `end`, `filter`, `bucket`, `aggregation`) as the vertiport-level endpoints. # Flight Log How to log flights in NOVA? How to view all logged flights? How to manage flight-related documents? For scaling organizations, maintaining rigorous compliance and standardized risk management is critical. Our new tamper-proof weather logging function in NOVA is engineered to support this imperative. It provides professional drone operators with a clear, verifiable record of the decision-making process for each takeoff. The Flight Log is a centralized place where all flights related to your organization are recorder and accessible. Each flight entry is linked to a specific mission and includes essential informations such as: * Flight number * Pilot * Take-off time Users can also upload and download relevant documents associated with each flight. This feature meticulously records: * The comprehensive weather data (three METARs near your operations, a high-resolution forecast along the flight path, and precipitation radar) considered at the time of the decision. * The specific weather parameters and operational limits factored in for the particular drone. * The exact timestamp of the takeoff decision and the person in charge for the take-off decision. This detailed logging ensures that you can always provide regulators with clear, empirical evidence of your flight planning and risk management protocols, reinforcing accountability and trust. {% content-ref url="/pages/HSLoAFXOyjI1YlzKKSIQ" %} [Logging a Flight](/nova/flight-log/logging-a-flight) {% endcontent-ref %} {% content-ref url="/pages/Hc8i0cdxYySX1GHpfgGI" %} [Accessing Logged Flights](/nova/flight-log/accessing-logged-flights) {% endcontent-ref %} {% content-ref url="/pages/wX8wOOdcIDiMFZWaUFWF" %} [Viewing a Flight Page](/nova/flight-log/viewing-a-flight-page) {% endcontent-ref %} {% content-ref url="/pages/lfhHtK1Z2W1Z4IA4EA9a" %} [Managing Attachments](/nova/flight-log/managing-attachments) {% endcontent-ref %} # Logging a Flight Log a Flight from a Mission {% stepper %} {% step %} Navigate to the Mission List and open the mission that you want to log a flight from. {% hint style="info" %} The logging function is available for existing missions. Refer to the [Create a new mission](/nova/get-started/create-a-new-mission) section for step-by-step instructions. {% endhint %} {% endstep %} {% step %} Click the **Flight Log** button at the top-right corner of the mission interface
{% endstep %} {% step %} Fill out the flight form with the necessary information * Take-off time * Flight number * Pilot responsible
{% endstep %} {% step %} Click on `LOG FLIGHT` to log the flight {% hint style="success" %} The flight will now be recorded under the mission and visible in the *Flight Log* section. {% endhint %} {% endstep %} {% endstepper %} # Accessing Logged Flights How to access flight logs that have already been recorded. To view all recorded flights in your company, go to the **Flight Log page** via the navigation bar.
The table will display all flights across the organization. Each row in the table includes: * Flight number * Status (Logged or Cancelled) * Take-off time * Mission name * Pilot name * Attachment indicator (shows if files are associated with the flight) {% hint style="info" %} You can sort the flight table by any column (default is take-off time) {% endhint %} *** ### Viewing more details Click the **Info icon** at the top right of the page to open a side panel with additional flight details. {% hint style="success" %} You can also double-click a row to open the flight’s detail page. {% endhint %}
### Cancelling a Flight To invalidate a flight: 1. Select the flight from the table 2. Click the **Cancel icon** 3. The flight status will be updated to **Cancelled** # Viewing a Flight Page Double-click a flight row to view its detailed page. This includes: ### General Information * Flight number * Mission name * Status Creator * Creation time * Aircraft type * Pilot * Take-off time ### Flight-Specific Data * Weather conditions at the time of the flight: * Take-off, en-route, and landing (if it is a route flight) * Location card (for local or multi-local flights) {% tabs %} {% tab title="Route flight" %}
{% endtab %} {% tab title="Local / Multi-local flight" %}
{% endtab %} {% endtabs %} * Aircraft details and operational limits {% tabs %} {% tab title="Aircraft details" %}
{% endtab %} {% tab title="Operational limits" %}
{% endtab %} {% endtabs %} * An interactive map showing the mission route or location points # Managing Attachments Each flight automatically includes a **JSON file** containing weather data recorded at the time of the flight. Users can upload additional documents (e.g., PDFs, images, reports) directly to each flight entry. ### Attachment Rules * Maximum of 3 files per flight * Maximum file size: 20 MB per file ### Uploading a File 1. Click the paperclip icon (either from the flights table or the flight's detail page) 2. Click on **Attach file** 3. Select a file from your device 4. The file will be uploaded and stored ### To view and download Files 1. Click the paperclip icon to view all uploaded files for a flight (either from the flights table or the flight's detail page) 2. A dialog box will open, displaying all attachments 3. Click any file to download it
{% hint style="info" %} Flights with attachments are marked with a paperclip icon in the log table {% endhint %}

Paperclip icon

Paperclip+ icon

# Glossary Definition of basic technical terms and abbreviations.
UTC UTC (Coordinated Universal Time): Standard time reference used for flight operations to ensure global consistency and avoid confusion across different time zones.
AGL AGL (Above Ground Level) refers to the altitude of the aircraft relative to the surface directly below it, rather than sea level.
AMSL **AMSL** stands for **meters above mean sea level**, indicating the height of a location relative to the average sea level.
VLOS **VLOS** (Visual Line of Sight) refers to drone operations where the operator can see the drone with the naked eye at all times during flight.
BVLOS **BVLOS** (Beyond Visual Line of Sight) refers to drone operations where the operator cannot see the drone and relies on technology (such as GPS, sensors, and cameras) to control and monitor it from a distance
METAR METAR data is a current weather report typically issued every hour. It describes the present weather conditions at an airport, including wind, visibility, clouds, temperature, and weather phenomena.
TAF TAF data is a forecast of expected weather conditions at an airport, usually issued four times a day (every 6 hours) and valid for 24 to 30 hours. It details expected changes in wind, visibility, clouds, and other relevant factors.
ConOps The Concept of Operations (CONOPS) outlines the intended use and operations of drones in various contexts, detailing how they are integrated into broader operational frameworks to achieve specific objectives. It encompasses aspects such as mission planning, flight operations, etc., aiming to maximize efficiency and safety in their deployment.
EAS Equivalent airspeed (EAS) is defined as the speed at sea level, under ISA conditions, that would produce the same incompressible dynamic pressure that is produced at the true airspeed and the altitude at which the vehicle is flying.
# Releases and Changes Content of our releases. Check out our previous releases with all the new features, bug fixes, and performance enhancements.
RELEASE 2.15.0 This update expands the Vertiport module with powerful new management tools, brings animated weather visualizations, and delivers a range of stability improvements. * **Vertiport - Network View** A new network view with an integrated map gives operators a clear overview of their vertiport networks, including the ability to manage and visualize connections between sites. * **Vertiport - Setup Wizard** Introduced a guided setup wizard for vertiport configuration, simplifying the onboarding of new vertiport sites with a step-by-step flow. * **Vertiport - METAR Card** A new dedicated METAR card is now available in the vertiport detail view, surfacing aviation weather report data directly alongside site-specific operational information. * **Vertiport - Status on Map** Vertiport online status is now displayed directly on the map, providing instant situational awareness without leaving the map view. * **Wind Rose - Animated Visualization** The wind rose needle and range arc now animate smoothly using shortest-path rotation, making wind direction changes easier to follow in real time. * **Wind - Gust Data** Wind gust information has been added to the wind card, giving a more complete picture of current wind conditions. * **Mission Wizard - Limit Validation** Improved validation of limit parameters during mission wizard setup to catch configuration issues earlier in the planning process. * **General - Bug Fixes & Stability** Multiple bug fixes across vertiport management, table reloading, live data updates, and form validation to improve overall reliability.
RELEASE 2.14.0 This update is centered around improving the experience for our Vertiport customers, new operational data for drone operations and major backend upgrades—along with performance boosts and many fixes. * **Vertiport - UI** Reworked UI for NOVA vertiport, including a new overview table, an improved map view, and a redesigned details view for clearer, faster operational insights. * **Vertiport - METAR Sensor** Introduced new virtual sensors powered by METAR data, enhancing environmental awareness and data accuracy. * **Vertiport - API** Released new Vertiport APIs to support stronger integrations and future feature development. * **Drone - Observed KP Index** Added the observed KP Index as additional mission data to support better planning and situational awareness. * **General - Backend Architecture** Implemented a new backend architecture to improve performance, scalability, and reliability. * **General - Performance** Added broad performance improvements across the platform. * **General - Bugfixes & Stability** Fixed some bugs to increase stability and overall user experience.
RELEASE 2.13.0 As we close out the year, we're delighted to present NOVA 2.13.0 — our final major release of 2025! With this update, we wish you a Merry Christmas and a Happy New Year! * **Predefined Drone Performance Sets** Jumpstart your mission planning with our new library of predefined drone performance sets. Choose from a selection of popular drone models with pre-configured performance parameters, making aircraft setup faster and more convenient. * **Optimized Logbook Dialog** The logbook dialog has been redesigned for improved usability and efficiency. Enhanced navigation, clearer presentation make logging of the weather conditions more intuitive. * **Persistent Table Filters** NOVA now remembers your selected filters across sessions. Your customized view settings are automatically saved, so you can pick up right where you left off without reconfiguring filters every time. * **Quality of Life Improvements** We've implemented numerous refinements throughout the application based on your feedback, focusing on small but impactful changes that make your daily workflows more efficient. * **Additional Bug Fixes** This release includes various bug fixes and stability improvements to ensure a reliable and seamless experience as you continue your operations into the new year.
RELEASE 2.12.0 We're pleased to introduce NOVA v2.12.0, a comprehensive update focused on personalization, visual improvements, and enhanced system performance. Here's what's new: * **New Customizable Dashboard for Home** Transform your NOVA experience with our brand new customizable dashboard! Personalize your home screen by arranging widgets, selecting your preferred data views, and creating a workspace that matches your operational needs. Tailor the interface to display the information most critical to your missions at a glance. * **New Colors for Better Contrast** We've introduced an updated color palette designed to improve readability and accessibility across all themes. The enhanced contrast ensures better visibility of critical information, reducing eye strain during extended use and improving overall user experience. * **Additional Bug Fixes** This release includes various bug fixes and stability improvements based on user feedback, ensuring a more reliable and seamless experience across all NOVA features.
RELEASE 2.11.0 We’re happy to roll out NOVA v2.11.0, a focused update designed to enhance user-platform interaction and introduce powerful new tools to support launch of ISR drones. Here's what’s new: * **New User Feedback / Bug Reporting Button**\ Easily share your experience and report issues! A new dedicated button makes providing feedback and bug reports quick and simple, helping us continuously improve NOVA. * **Custom Sorting of Limit Parameters in AWARE / CAST**\ Tailor NOVA to your needs - you can now customize the sorting of Limit Parameters within the AWARE and CAST modules, allowing you to prioritize the data most critical to your mission. * **NOVA Launchpad (Wind Direction Calculator)**\ Introducing a dedicated tool for launch precision. The new wind direction calculator helps determine optimal launch directions or catapult settings based on current wind data. * **UI Improvements for Better Contrast**\ We’ve implemented various User Interface enhancements to improve visual contrast, making the application cleaner, more legible, and easier to use in various lighting conditions.
RELEASE 2.10.0 This release introduces several functional enhancements designed to improve data handling, user interface clarity, and operational efficiency. Key updates include: * **New Data Filters**\ We have implemented advanced filtering options, enabling more precise data analysis and faster access to specific information sets. * **Redesigned Logbook**\ The logbook interface has been updated for improved readability and more efficient entry and review of operational data. * **Place Search Autocomplete**\ When entering a location name, the system will now provide automatic suggestions, streamlining the process of defining locations and routes. * **User Profile Management**\ A dedicated user profile section is now available, allowing for centralized management of your account settings. * **NOVA Launchpad (Test Version)**\ We are pleased to introduce an initial test version of the NOVA Launchpad, which supports crosswind checks and catapult direction searches. This new module is available as a beta version, and we welcome your feedback to help us develop it further.
RELEASE 2.9.0 Our latest update marks the exciting debut of Teams in NOVA, designed with simplicity and ease of use at its core. * **Teams (Beta)**\ Missions can now be assigned directly to teams for easier collaboration and selection. * **Map Refinements**\ Improved map performance and usability for a smoother experience. * **General Bug Fixes**\ Various under-the-hood improvements to ensure a better experience and increased stability.
RELEASE 2.8.0 We’ve introduced several powerful updates to NOVA, focused on improving usability, compliance, and mission planning accuracy. * **FlightLog (Beta)**\ Our new logging system supports compliance within Flight Operations Organizations by allowing users to document key flight details—including weather conditions and pilot decisions—directly in the flight log. * **Upload Your Flight Information to a Flight Log**\ Users can now upload autopilot (.ulog), telemetry (.tlog), and other relevant files directly to their flight logs. This makes it easier to locate, review, and analyze mission data—supporting long-term compliance and traceability. * **Vertical Flight Profile in Route Creation**\ When planning missions, users can now visualize the vertical profile of both imported and manually created routes in real time. This helps verify the accuracy and safety of the planned flight path. * **Asset Filtering**\ A refined filtering system enables users to quickly search for and locate specific assets—streamlining workflows and improving resource management. * **Mobile Experience Upgrades**\ The mobile version of NOVA has been enhanced for better responsiveness, usability, and functionality—ensuring a seamless experience across all devices.
RELEASE 2.7.0 We are excited to introduce a new release packed with valuable features and improvements to enhance your workflow and user experience. * **Duplicate Assets:** Easily create copies of existing assets to speed up your workflow. * **Weather Layers got legends:** Weather layers now display legends, making it easier to understand weather data. * **Route import of QGroundControl and MissionPlanner files:** Import routes directly from QGroundControl and MissionPlanner files for seamless mission integration. * **Changes in assets may now trigger a re-simulation of linked mission(s):** When assets are updated, linked missions may automatically re-simulate to reflect the changes. * **Greatly optimized overall user experience:** Enjoy a smoother, faster, and more intuitive interface throughout the application. * **Optimized Tablet experience:** The interface and controls have been refined for a better experience on tablets. * **NOVA works on Mobile:** NOVA is now fully compatible with mobile devices, allowing you to work on the go.
RELEASE 2.6.0 We are pleased to announce NOVA V2.6.0, focused on delivering enhanced asset management, improved weather data integration, and overall performance optimization. This update provides valuable tools for more efficient and safer mission operations. Here's what’s new: * Reworked and Optimized Asset Manager - The asset manager has been redesigned and optimized for improved efficiency and usability. * Weather Stations in Mission Planning - Weather stations are now available for integration into mission planning, providing more granular and real-time weather data. * Better Tempest Integration - Enhanced integration with Tempest for improved weather data accuracy and availability. * Reworked Weather Layers - Weather layers have been reworked to provide clearer and more actionable weather information. * Optimized Loading Times - Loading times across the platform have been optimized for a smoother and more responsive user experience. * General Bug Fixes - This release includes a variety of general bug fixes to improve overall stability and performance.
RELEASE 2.5.0 New week, new release. We are happy to introduce **NOVA 2.5.0**, bringing **enhanced weather awareness** to your flight operations. This update includes: 1. **Custom Weather Station Integration**\ Gain access to real-time weather data at your point of interest to improve situational awareness and covering micro weather effects. 2. **Additional Weather Parameters** * **Spread** – Improved visibility assessment. * **Snowfall 24h, Snow Depth, and Snow Probability** – Critical for operations in winter conditions.
RELEASE 2.4.0 We’re excited to introduce NOVA V2.4.0, featuring an optimized Asset Manager that enhances your workflow efficiency. Here's what’s new: 1. **Redesigned Asset Manager**\ Easily manage drone types, limit sets, flight routes, and soon, your own weather sensors— all in one place. 2. **Improved System Stability**\ We’ve fixed bugs and optimized performance for a smoother, more reliable experience.
RELEASE 2.3.0 We’re thrilled to present NOVA V2.3.0, bringing a series of enhancements to streamline your experience and provide more powerful tools for mission planning and management. Here's what’s new: 1. **New User Menu**\ A redesigned user menu is now available in the top-right corner, offering quick and intuitive access to account settings, preferences, and key tools. 2. **Popout Map for Missions**\ Planning missions is now even more interactive! The new **Popout Map** feature lets you expand the map to a larger, standalone view for detailed planning and visualization. 3. **Route Mission KML Downloads**\ Easily export route missions as KML files directly from the Asset Manager, providing seamless integration with external tools and systems. 4. **Navigation Cleanup**\ With the introduction of the new user menu, we’ve simplified the overall navigation structure, ensuring a cleaner and more efficient interface. 5. **Help & FAQ Overhaul**\ Need assistance? The Help & FAQ section has been revamped, now offering in-depth guidance for NOVA and Unisphere products, including detailed API documentation for developers. 6. **Settings View Rework**\ The settings view has been completely redesigned to enhance usability. It’s now easier than ever to configure and manage your preferences, improving your overall workflow. 7. **Custom UAS Performance Models**\ If your organization has engineered a customized UAS performance model with us, it can now be selected directly for a flight mission within the UI of NOVA.
RELEASE 2.2.0 Our latest release brings a range of updates to NOVA, adding enhanced tools, expanded features, and new customization options for a more dynamic experience. Check out what’s new this season: * **Expanded Map and Layer Options** The "NOWCASTING" section has received a significant update with additional data layers to boost planning capabilities. Beyond precipitation radar, users can now access: * Total Cloud Cover * Surface Temperatures * Wind Barbs * Wind Speeds * Accumulated Precipitation * **Extended Slider Range in AWARE** Look further ahead with an increased slider range of up to 48 hours in the AWARE feature. This extended forecasting empowers users to make more informed decisions with a broader time horizon and is synced with the hourly evaluation. * **User-Defined Map Sizing** Enjoy added flexibility with the new customizable map sizing option. Define your preferred map size to adapt the view to your workflow, creating a more personalized and functional user experience. * **Streamlined Flight Route Creation Tools** Flight planning just got simpler with improved route creation functionalities: * Reverse Route: Flip the direction of any route upon uploading a \*.kml file, making it easier to modify and adapt paths. * Uniform Waypoint Altitudes: Instantly apply a single altitude across all waypoints, ensuring smoother adjustments and quicker setup.
RELEASE 2.1.0 #### New in NOVA * **New performance models** New performance models to improve simulation accuracy for multi-copter and fixed-wing aircraft. * **Icing Potential** The "Icing Potential" parameter is now available for inclusion in your limit sets. New Icing parameters allow for gradations between 100% (severe icing) and 0% (no icing). #### Improved Features * **Wind impact calculations** More accurate wind impact calculations for BVLOS route simulation by incorporating our new performance models, which better reflect aircraft behavior in different flight phases. * **UI/UX for mobile devices** Improved UI/UX for mobile devices, making it easier to use NOVA on tablets and phones for in-field checks. * **Loading times for radar layer** Improved loading times for radar layer for smoother slider usage.
RELEASE 2.0.0 This update brings major improvements and new features for enhanced BVLOS flight planning and increased flight safety: With the update it is possible to create a new mission type "Route" which uses our simulation technology to check weather conditions and wind impact along the flight path for flight duration and battery impact. * **Improved Wind Impact Simulation** Accurately calculate the impact of wind on drone flights, including drift, speed variations, and accurate flight time predictions. * **Energy Impact Analysis** Gain timely insight into how wind conditions are impacting energy performance, and ensure takeoff only if predicted energy state of charge on landing is above safety thresholds. * **Comprehensive Weather Checks** Monitor all critical weather parameters incrementally along the flight path, taking into account altitude changes to account for variables such as outside air temperature (OAT) and wind variations. * **New Visualization** For route missions, the NOW function includes the altitude profile and a slider function that shows flight progress and the impact of wind on battery and flight progress. The AWARE & CAST function visualization has also been updated to provide users with an overview of the minimum and maximum values for each parameter the drone will encounter during the flight, up to 7 days into the future. These updates ensure safer and more efficient flight planning with detailed, data-driven insights in version 2.0!
RELEASE 1.6.0 In our latest release, we have added several new features to help you better use NOVA in flight operations. * **Improved UI for mobile devices** NOVA is now even easier to use on your mobile devices, especially tablets. The functionalities have been adapted to allow a better usability on touchscreens. * **Map layer functionality** The map layer functionality has been improved and now covers more countries with precipitation radar. In addition, it is now easier to add new map features that will be added in the coming months. * **Updated design** The design of NOVA has been updated to make it more intuitive and easier to use.
RELEASE 1.5.0 In our recent release, we added some new functions to increase compliance in your flight operations. * **New Role Function** Launch of Role Function in Release 1.5.0 * **Enhanced Compliance** Strengthens access right management for organizational roles. * **Specific Permissions** * ***Flight Operations Managers**:* Edit all aspects of the Asset Manager (Operational Limit Sets, Drone Types, Aircraft Performance Set). * ***Pilots**:* Create missions using available drones and limit sets; restricted from altering weather parameters or thresholds. * **Operational Efficiency** Ensures adherence to internal standards, improving mission planning and safety across the organization.
RELEASE 1.4.0 * **New Vertiport Module (BETA)** Introducing the new Vertiport module in NOVA: tailored for advanced air mobility (AAM) operations it integrates data from aviation-grade weather sensors, digitally and physically, ensuring precise weather evaluations. Plus, it enables centralized management of multiple vertiports, streamlining operations and enhancing safety. Experience enhanced vertiport management with NOVA's Vertiport module—unlocking the full potential of AAM operations. * **Enhanced Map Experience** We've improved the map interface to provide a more intuitive and user-friendly experience. * **Bug Fixes & Performance Enhancements:** We've resolved various bugs and made significant performance improvements to ensure a smoother and more reliable user experience.
RELEASE 1.3.0 * **Multi-Location:** **Compare multiple locations** Add multiple locations to your mission, enhancing your planning capabilities. This allows you to compare several locations and choose the one with the best weather conditions. * Up to 5 locations in a single mission * Up to 100km radius * **Enhanced UX Design: Experience a more intuitive user interface** With clear indicators for "Go," "Caution," and "Do Not Fly," you can quickly gauge the suitability of weather conditions and take decisive action. * **Bug Fixes & Performance Enhancements:** We've resolved various bugs and made significant performance improvements to ensure a smoother and more reliable user experience.
RELEASE 1.2.1 * **The KP Index: A Critical Metric for Aviation Professionals** The KP Index, a measure of geomagnetic activity, plays a critical role in ensuring the safety and efficiency of drone operations.\ \ The KP index ranges from 0 to 9 and represents the intensity of geomagnetic activity. A higher KP value indicates increased solar activity, which can potentially disrupt drone operations due to its effect on the Earth's magnetic field, in particular when the value is greater than 5.\ \ By closely monitoring the KP Index, professionals can: * Maintain navigational stability in the face of GPS signal interference * Ensure uninterrupted communication by implementing backup communication protocols * Protect drone electronics from damage caused by electrical currents in the atmosphere * **Performance Improvements and Bug Fixes** As always, we've fine-tuned NOVA for peak performance and addressed bugs thanks to your valuable feedback. Your experience is our priority, and we're committed to delivering excellence in precision aviation. **Our Upcoming Features** * **Multi-Location Mission Preparation** Prepare for more with our upcoming Multi-Location feature! Soon, you'll have the power to add multiple locations to your mission, enhancing your planning capabilities for diverse operational needs. * **Enhanced Safety with Team Roles** We have further developed our concept on strengthening safety and compliance with the introduction of Team Roles. This upcoming feature empowers administrators with control over critical functions in NOVA, ensuring compliance with internal safety standards. NOVA adapts based on your role, offering a tailored experience designed for your team's security and success.
RELEASE 1.2.0 * **Tablet Mode** NOVA is now available for tablet use * **Extended 7-Day Outlook** Get flight evaluations for the next 7 days * **Quick Function Switch** Switch quickly between Nowcasting, 48 hours evaluation and 7 day outlook * **Nowcasting and Rain Radar Connected** The Nowcasting feature adjusts in real-time to the selected radar time * **Parameter Alert in Nowcasting** We've added exclamation marks to highlight weather parameters to watch out for
# OPERATIONAL ANALYTICS What's NOVA OA and what does it offer? NOVA OA is a software solution designed for conducting in-depth weather analyses tailored to Innovative Air Mobility (IAM). It analyzes historical weather data over a selected period of time at locations relevant for the planned operations. The weather data is evaluated on an hourly basis considering the envisioned concept of operations. To create individual analyses, you may select one of four simulation types with varying levels of detail. OA-specific assets tailored to your needs can be created and re-used. Analyses can be edited and tweaked once they are finished. The difference compared to the NOVA simulations [NOW](/nova/missions/results/now), [AWARE](/nova/missions/results/aware), and [CAST](/nova/missions/results/cast) lies in the fact that OA focuses exclusively on weather data from the past enabling long-term, strategic business planning. As with the other simulation types, you can set limits in OA to analyze whether the weather data falls within the nominal, moderate, or critical range and draw conclusions regarding operational planning based on this. In contrast, however, you do not receive an automatic assessment of flight feasibility after the evaluation but a visualized historical dataset that allows you to estimate the likelihood of nominal, moderate, and critical weather conditions. ## Key features & benefits
Service Availability Insights * Predict uptime and downtime per year/ month and time of day, including causes of downtime. * Comparison of service availability across locations.
Wind Analysis * Comprehensive assessment of wind conditions, including wind strength, direction, and effects of day/ night. * Available for single or multiple locations with classifications of wind intensities and directions.
Track and Site Evaluation * In-depth evaluation of track availability at multiple heights and under specific limitations. * Support for site assessments with prioritization and visualizations for stakeholders.
Comparison and Benchmarking * Build a solid knowledge base for comparison and decision-making across different locations and conditions.
Detailed Analyses * Highest level of detail, including seasonal dependencies
# Create your analysis Guide on how to create a new Analysis in NOVA. Under NOVA Analytics, location-based weather data analyses can be conducted. This process involves considering historical weather data and making a one-year forecast. Click on the "NEW ANALYSIS" button, either in the center or at the top right of the screen, to create a new analysis. Next, you need to follow these six steps. {% stepper %} {% step %} #### Setup In the first step, you need to select how you want to set up your analysis. You can create a completely new analysis, copy an existing one, or upload an existing analysis file. The first step in creating a "NEW ANALYSIS" within the Operational Analytics in the NOVA Platform. Select the desired option and press "CONTINUE". {% endstep %} {% step %} #### Type You can choose between four types of analysis. Depending on how detailed you want your analysis to be, you can select between high level and detailed. In addition to these options, you can perform example analyses for all types. Analysis types are:
Cover image
/pages/NE5kunSfK0JTWmQqALSy/files/OrP8eOK1CfURpVnx1qvc
/pages/A1ZTORiSpdTGh32riazv/files/uTQ4zlQ2d7IdItwrdcAR
/pages/oQpkVpYqGbxNVUAVYLYF/files/kPQQHqYsqBeMQ1JRFpYk
Select the desired analysis type and press "CONTINUE". {% endstep %} {% step %} #### Name In the third step, you can choose a name and project name for your analysis. By assigning a project name, you can group your analyses together. Select the same project name when creating your analyses to have them listed under the same project. You can access your projects in the analysis overview. The third step in creating a "NEW ANALYSIS" within the Operational Analytics in the NOVA Platform is adding a name. Press "CONTINUE". {% endstep %} {% step %} #### Locations In the left panel, you can set a name for your analysis location. In the right panel, "Search name/coordinates," you can specify your analysis location. You can select the desired location by clicking on the map, searching for an address, using the current GPS location (if available on your device) or adding a previously created [location asset](/nova/assets/locations-and-routes) via the "ASSETS" button. You can also upload a CSV file. Next, you can choose the altitude at which your analysis should be taken. You can select between 10m (33ft), 152m (500ft), and 305m (1000ft). Additional locations can be added by clicking the "Add Another Location" button. The fourth step in creating a "NEW ANALYSIS" within the Operational Analytics in the NOVA Platform is adding locations. Press "CONTINUE". {% endstep %} {% step %} #### Time Under "Time," you can set the starting point and the time frame for your analysis. On the left, you can specify your start year, and on the right, your time frame: 1 year, 3 years, or 5 years. For each period, the analysis will be conducted up to the following year starting from the chosen year. Accordingly, a 3-year analysis will consider data from the last two years, and a 5-year analysis will consider data from the last four years relative to the start year. Below, you can set the time of day to be considered. You can choose between Day, Night, Day & Night, and Custom. For day and night the times are adjusted depending on the time of sunrise and sunset. Under Custom, a specific start and end time can be configured. Analyses can be conducted that consider data starting from the year 2015 at the earliest. The fifth step in creating a "NEW ANALYSIS" within the Operational Analytics in the NOVA Platform is setting up the time frame. Click "CONTINUE" next. {% endstep %} {% step %} #### Runway As part of track analyses, you can specify the runways to be analyzed. To do this, enter the name, orientation, and purpose of the runway (Approach/Departure). You can center the track in the map using the star icon and delete it using the trash icon. If you want to add multiple tracks, you can do so via the plus symbol in the top right corner.
The sixth step in creating a "NEW ANALYSIS" within the Operational Analytics in the NOVA Platform is The eighth step in creating a "NEW ANALYSIS" within the Operational Analytics in the NOVA Platform is specifying runways.
{% endstep %} {% step %} #### Track system In the next step of the track analysis, you can group your approach and departure runways into a track system. First, choose a name for the track system, then assign the previously created runways to the approach and departure sections. You can add multiple track systems using the plus icon or delete them using the trash icon.
The seventh step in creating a "NEW ANALYSIS" within the Operational Analytics in the NOVA Platform is grouping runways into a track system.
{% endstep %} {% step %} #### Limits You can define limits for each analysis type except for the wind analysis. Under "Accepted Operational Conditions", you can specify the conditions under which your track system may be used. These can be restricted to nominal values or to nominal and moderate values. The exact values can be entered below, next to the units.
The eighth step in creating a "NEW ANALYSIS" within the Operational Analytics in the NOVA Platform is defining limits.
In the Service Availability Analysis and Benchmark Analysis, pre-existing limit sets can be added via "Assets." Additionally, through the three-dot menu, you can create or edit these limit sets directly and generate an example limit set.
Rather than defining limits in step eight in creating a new analysis, you can choose from pre-existing limit sets.
{% endstep %} {% step %} #### Summary Before starting your analysis, you have the opportunity to review your information in the summary. You will get an overview of your analysis locations with a map, your time settings (year range, time of day), and additional information (data points and estimated duration). Depending on the analysis type, an overview of your limit sets and track systems will also be displayed. Under "Start Analysis," you can begin your analysis. The completion of your analysis may take a few minutes. Next to it, you can download your analysis setup in .json format. The last step in creating a "NEW ANALYSIS" within the Operational Analytics in the NOVA Platform is a summary before starting the analysis. {% endstep %} {% endstepper %} {% hint style="info" %} Once you have started your analysis, it will be displayed in the project overview. If you cannot access the analysis yet, it is still loading, and a circular loading icon will be displayed. {% endhint %} # Manage your analysis Manage your analysis after it's creation. Once you've created an analysis, you can manage it in the project overview.
Interface of project overview within the Operational Analytics to manage your analysis projects.

Project overview

In this view, you'll find all your projects and analyses, with details such as their name, type, subtype, the time of the last update, and the editor's information. The wallet icon in the top right corner tracks the number of created analyses, with a limit of 200. To the right, you'll also find a map icon that lets you view the analysis location on a map. At the bottom, you can select how many projects to display per page and navigate between pages if needed. To manage a specific analysis, click the on 3-dot menu to the right. A menu will appear above the mission list, where you'll find three icons on the left: a trash can (delete the analysis), an arrow ( download the analysis results as a zip file), and curly brackets (download the analysis setup as a .json file). On the right side, you can retrieve the mission ID and finalize the editing process by clicking the cross. # Analytics assets Analytics specific assets. ## Analytics limit sets For Service Availability and Benchmark Analyses, custom limit presets can be created. The process is the same as for the [regular limit assets](/nova/get-started/create-your-assets). The following assets are considered in the OA: cloud base, cloud ceiling, dangerous phenomena, dew point, general icing, gust factor, outside air temperature, precipitation, relative humidity, spread, visibility, wind gusts, and wind speed. ## Analytics locations Analytics location assets are [location assets](/nova/assets/locations-and-routes) for operational analyses. The process of creating them is the same as for regular location assets. # Analysis types Get to know the different analysis types in NOVA. In NOVA OA, four different types of analyses are available: Wind Analysis, Service Availability Analysis, Benchmark Analysis, and Track Analysis. Depending on the level of detail desired, a tailored type of analysis can be selected to provide the most essential information for each case. * [**Wind Analysis**](/operational-analytics/analysis-types/wind-analysis-overview) focuses on wind data only, with limited analysis of the concept of operations. * [**Service Availability Analysis**](/operational-analytics/analysis-types/service-availability) allows for conclusion on business viability of the planned operations, taking into account weather and operational considerations. * [**Benchmark Analysis**](/operational-analytics/analysis-types/benchmark-analysis) allows comparing different locations to establish the most suited ones for operations. * [**Track Analysis**](/operational-analytics/analysis-types/track-analysis) considers the planned approach and departure track configuration, yielding a very in-depth analysis. The following sections provide a details on the four types of analyses, focusing on their structure and applications. {% content-ref url="/pages/NE5kunSfK0JTWmQqALSy" %} [Wind Analysis](/operational-analytics/analysis-types/wind-analysis-overview) {% endcontent-ref %} {% content-ref url="/pages/A1ZTORiSpdTGh32riazv" %} [Service Availability](/operational-analytics/analysis-types/service-availability) {% endcontent-ref %} {% content-ref url="/pages/oQpkVpYqGbxNVUAVYLYF" %} [Benchmark Analysis](/operational-analytics/analysis-types/benchmark-analysis) {% endcontent-ref %} {% content-ref url="/pages/3SO1G7mQ8Nvg4JnU1Gj7" %} [Track Analysis](/operational-analytics/analysis-types/track-analysis) {% endcontent-ref %} # Wind Analysis: Overview The wind analysis and its use cases. The wind analysis evaluates historical wind data (wind speed and direction) at various altitudes and at one or more locations. It generates summarized monthly evaluations. Annual evaluations are also provided based on the aggregation of the monthly evaluations. During the creation of the analysis, you can choose whether to perform it as a high-level analysis (evaluation of a specific time of day) or as a detailed analysis (evaluation of all times of day at once). To gain a first impression of the results you can expect, a set of example results is provided within the analysis type selection wizard.
Benefits * Get an overview on the prevailing wind conditions * Grouping of intensities (5 classes) and directions (16) * Comprehensive assessment of wind conditions at highest quality * Detailed insights into wind strength and directions of a single location * Visualization of day and night effects
## High level The high-level analysis is used to evaluate wind speed and direction at a specific time of day (either day, night, day & night, or custom). #### Content
Wind roses Wind roses (monthly, yearly, summary)
Map overview Map overview of location (continent, world)
#### Creation {% hint style="success" %} Analysis at different altitudes simultaneously (10m (33ft), 152m (500ft), and 305m (1000ft)). {% endhint %} {% hint style="success" %} Analysis at multiple locations simultaneously. {% endhint %} {% hint style="success" %} Analysis of individual time frames and day times. {% endhint %} #### Use cases
Use cases * Useful if a flight mission is already scheduled for a specific time of day/time and only needs to be verified * For a quick analysis of a specific time of day (High level only analyzes the specified period and is therefore completed faster than the detailed analysis) * For planning wind speed and direction, if the flight date is outside the one-week evaluation range of NOVA
## Detailed The detailed analysis is used to evaluate wind speed and direction for day, night, and day & night simultaneously. #### Content
Detailed day Wind roses (monthly, summary, yearly)
Detailed day & night Wind speed heatmap (hourly per year, hourly per month, summary), wind direction heatmap (hourly per year, hourly per month, summary), wind roses (monthly, yearly, summary)
Detailed night Wind roses (monthly, yearly, summary)
Map overview Map overview of location (continent, world)
#### Creation {% hint style="success" %} Analysis at different altitudes simultaneously (10m (33ft), 152m (500ft), and 305m (1000ft)). {% endhint %} {% hint style="success" %} Analysis at multiple locations simultaneously. {% endhint %} {% hint style="success" %} Analysis of individual time frames and day times. {% endhint %} #### Use cases
Use cases * Useful if the flight time still needs to be chosen, as it offers an evaluation of all possible times at once * Likely faster than the high-level analysis if multiple day times need to be analyzed * For planning wind speed and direction, if the flight date is outside the one-week evaluation range of NOVA
# Service Availability The service availability and its use cases. The service availability analysis allows for the percentage calculation of how often good, moderate, and poor flight conditions occur. Specifically, it evaluates the proportion during which nominal, moderate, or severe weather conditions are present, based on selected parameter limits. Service availability is given when the analysis limits are met (nominal, if applicable, moderate values) and flight conditions allow operations. The analysis can be conducted simultaneously for multiple locations and at arbitrary times of the day. When creating a service availability analysis, a distinction is made between high level (evaluation of a specific time of day) and detailed (comprehensive evaluation of all times of day at once). In both analysis types, visual assessments of operational conditions per month and a corresponding summary of conditions per year are created. Additionally, the reasons for moderate and severe conditions are displayed. You also have the option to view a sample analysis for a quick overview.
Benefits * Know what is the expected up/down time of my service per year/month * What are the parameters causing the downtime per year * Build up profound knowledge as a baseline for comparison * What is the expected up/down time of my service per year/month/time of day * What are the parameters causing the downtime per year/month/time of day
## High level The high-level analysis is used to evaluate service availability at a specific time of day (day, night, day & night, or custom). #### Content
Operational Conditions Operational Conditions (yearly, operational conditions per month), reasons for severe conditions (per year), reasons for moderate conditions (per year)
Map Overview Map Overview of location (continent, world)
#### Creation {% hint style="success" %} Analysis at multiple locations simultaneously. {% endhint %} {% hint style="success" %} Analysis of individual time frames and day times. {% endhint %} #### Use cases
Use cases * Useful for a quick and broad monthly and annual assessment (faster than a detailed analysis) * For drone operations over extended periods – enables the highest possible availibility for deployment * As an addition to NOVA, which evaluates the period outside the one-week evaluation range
## Detailed The detailed analysis is used to evaluate service availability for day, night, and day & night simultaneously and provides hourly evaluations. #### Content
Detailed day Operational conditions (per year, per month), reasons for servere conditions (per year, per month), reasons for moderate conditions (per year, per month), operational conditions (per hour (nominal), per hour (nominal + moderate))
Detailed day and night Operational conditions (per year, per month), reasons for servere conditions (per year, per month), reasons for severe conditions (per hour per month), reasons for moderate conditions (per year, per month), operational conditions (per hour (nominal), per hour (nominal + moderate))
Detailed night Operational conditions (per year, per month), reasons for servere conditions (per year, per month), reasons for moderate conditions (per year, per month), operational conditions (per hour (nominal), per hour (nominal + moderate))
Map Overview Map Overview of location (continent, world)
#### Creation {% hint style="success" %} Analysis at multiple locations simultaneously. {% endhint %} {% hint style="success" %} Analysis of individual time frames and day times. {% endhint %} #### Use cases
Use cases * Useful for a broad and hourly evaluation * For drone operations over extended periods – enables the highest possible availibility for deployment * As an addition to NOVA, which evaluates the period outside the one-week evaluation range
# Benchmark Analysis The benchmark analysis and its use cases. The benchmark analysis, similar to the service availability analysis, allows for the evaluation of the proportion of ideal flight conditions and helps assess whether a flight location is suitable. The strength of the benchmark analysis lies in comparing locations regarding their suitability: {% hint style="success" %} Direct comparison of multiple locations in comparative benchmark charts. {% endhint %} {% hint style="success" %} Direct comparison of multiple locations with different limit sets. {% endhint %}
Benefits * Highest level of detail available * What is the expected up/down time of my service per year/month/time of day in comparison to other locations * What are the parameters causing the downtime per year/month/time of day in comparison to other locations
## Detailed The detailed analysis is used to evaluate operational conditions and their triggers for day, night, and day & night simultaneously. #### Content
Benchmark of Operational Conditions * Detailed day: Operational conditions (per year, per month (nominal), per month (nominal + moderate), reasons for severe conditions, reasons for moderate conditions) * Detailed day and night: Operational conditions (per year, per month (nominal), per month (nominal + moderate), reasons for severe conditions, reasons for moderate conditions) * Detailed night: Operational conditions (per year, per month (nominal), per month (nominal + moderate), reasons for severe conditions, reasons for moderate conditions)
Detailed Operational Conditions * er month), reasons for moderate conditions (per year, per month), operational conditions (per hour (nominal), per hour (nominal + moderate)) * Detailed day and night: Operational conditions (per year, per month), reasons for severe conditions (per year, per month, per hour per month), reasons for moderate conditions (per year, per month), operational conditions (per hour (nominal), per hour (nominal + moderate)) * Detailed night: Operational conditions (per year, per month), reasons for severe conditions (per year, per month), reasons for moderate conditions (per year, per month), operational conditions (per hour (nominal), per hour (nominal + moderate))
Map Overview Map Overview of location (continent, world)
#### Creation {% hint style="success" %} Analysis at different altitudes simultaneously (10m (33ft), 152m (500ft), and 305m (1000ft)). {% endhint %} {% hint style="success" %} Analysis of individual time frames and day times. {% endhint %} #### Use cases
Use cases * Finding an ideal airfield * comparing drone types at a location
# Track Analysis The track analysis and its use cases. The track analysis allows users to determine the usability of a runway or vertiport using individual parameter limits and provides monthly and yearly evaluations. It consists of a Track Usability Analysis and a Wind Component Analysis. In the Track Usability Analysis, the usability of a runway or vertiport is evaluated over a defined period. The Wind Component Analysis assesses wind conditions at one or more altitudes.
Benefits * Valuable input for site selection, procedure design & verification * Achieve EASA and FAA compliance * EASA states an overall track usability for a Vertiport of at least 95% should be fulfilled (Prototype Technical Specifications for the Design of VFR Vertiports) (PTS-VPT-DSN / March 2022) * Detailed understanding of required usage of prioritized and non-prioritized tracks * Certainty for stakeholders involved in the site assessment * Evaluation of track availability on given limitations * Assessment of track at multiple heights * Seasonal dependencies
## Usability The detailed analysis is used to evaluate the usability of tracks and vertiports as well as the wind conditions at the specified start and landing location. #### Content
Track Usability Analysis Detailed Track systems (monthly, yearly), overall vertiport (monthly, yearly)
Wind Component Analysis Track Direction 360 (wind conditions over altitude, detailed wind conditions over altitude, wind conditions per month)
#### Creation {% hint style="success" %} Analysis at different altitudes simultaneously (10m (33ft), 152m (500ft), and 305m (1000ft)). {% endhint %} {% hint style="success" %} Analysis of individual time frames and day times. {% endhint %} {% hint style="warning" %} Analysis at one location at a time. {% endhint %} #### Use cases
Use cases * Useful for identifying an ideal takeoff/landing point for drone operations * Serves as an addition to NOVA to further verify takeoff and landing conditions
## Advanced The detailed analysis is used to evaluate the usability of tracks and vertiports as well as the wind conditions at the specified start and landing location. #### Content
Track Usability Analysis Detailed track systems (monthly, yearly), overall vertiport (monthly, yearly)
Wind Cimponent Analysis Track direction 360 (Wind conditions over altitude, detailed wind conditions over altitude, wind conditions per month)
#### Creation {% hint style="success" %} Analysis at different altitudes simultaneously (10m (33ft), 152m (500ft), and 305m (1000ft)). {% endhint %} {% hint style="success" %} Analysis of individual time frames and day times. {% endhint %} {% hint style="warning" %} Analysis at one location at a time. {% endhint %} #### Use cases
Use cases * Useful for identifying an ideal takeoff/landing point for drone operations * Serves as an addition to NOVA to further verify takeoff and landing conditions
# Analysis results OA analysis results explained. The primary task of OA is to create detailed historical analyses and present the results clearly and precisely. This is made possible by the extensive data set and meaningful visualizations, which provide a reliable information base and support users in making informed decisions in flight operations. Currently, four different types of analyses are available, each differing in their structure and visualization. These will be explained in more detail below. {% content-ref url="/pages/3sJp5ALa4DxH9qosNwEC" %} [Wind Analysis](/operational-analytics/analysis-results/wind-analysis-results-interpretation) {% endcontent-ref %} {% content-ref url="/pages/L47pRhwI68TusqQntjyW" %} [Service Availability](/operational-analytics/analysis-results/service-availability) {% endcontent-ref %} {% content-ref url="/pages/oQpkVpYqGbxNVUAVYLYF" %} [Benchmark Analysis](/operational-analytics/analysis-types/benchmark-analysis) {% endcontent-ref %} {% content-ref url="/pages/9inOspnh0mhh6bTuALRX" %} [Track Analysis](/operational-analytics/analysis-results/track-analysis) {% endcontent-ref %} {% content-ref url="/pages/E7zAJXzeSazog684OUx6" %} [Map Overview](/operational-analytics/analysis-results/map-overview) {% endcontent-ref %} # Wind Analysis: Results Interpretation Understanding the Components of Wind Analysis results. ## Wind Roses Wind rose charts provide an effective way to represent wind speed and direction in a single diagram. They are created both in high-level and detailed analyses on a monthly basis, as well as in an annual summary, but do not display wind conditions by the hour.
Structure **Calm Sector:**\ The central circle of the wind rose, often referred to as the "calm sector," indicates the percentage of time (e.g., 39%) during which no wind or only minimal wind movement was recorded. **Wind Directions:**\ The wind rose diagram is divided into 16 segments, each representing a wind direction of 22.5°. Below is a description of the wind directions: * **0° - N (North):**\ -> Short bar, low wind frequency, primarily low wind speeds (3-6 knots) * **22.5° - NNE (North-Northeast):**\ -> Very short bar, almost no wind from this direction * **45° - NE (Northeast):**\ -> Barely any wind from this direction; the bar is almost invisible * **67.5° - ENE (East-Northeast):**\ -> Similar to NE, no significant wind frequency * **90° - E (East):**\ -> Slightly visible bar, low wind frequency (3-6 knots) * **112.5° - ESE (East-Southeast):**\ -> Almost no wind from this direction, very short bar * **135° - SE (Southeast):**\ -> Nearly no wind from this direction; bar is minimal * **157.5° - SSE (South-Southeast):**\ \- > Very short bars, minimal wind activity * **180° - S (South):**\ -> Few winds from this direction; bars visible for 3-6 knots * **202.5° - SSW (South-Southwest):**\ -> Slight activity, dominated by low wind speeds * **225° - SW (Southwest):**\ -> One of the dominant wind directions; longer bars with various speed ranges (up to 15-20 knots) * **247.5° - WSW (West-Southwest):**\ -> Noticeable activity, primarily low to moderate wind speeds (6-15 knots) * **270° - W (West):**\ -> Dominant direction, longer bars, with a concentration of 6-15 knots and some stronger winds * **292.5° - WNW (West-Northwest):**\ -> Significant wind frequency, bars with moderate speeds (up to 10-15 knots) * **315° - NW (Northwest):**\ -> Less wind from this direction, mainly low speeds (3-6 knots) * **337.5° - NNW (North-Northwest):**\ -> Low wind frequency, visible bars for low wind speeds **Wind Speed:**\ The wind intensity is illustrated by the color of the bars. Different colors represent various wind speed ranges: * Light gray: 3–6 knots * Dark gray: 6–10 knots * Light blue: 10–15 knots * Dark blue: 15–20 knots * Red: More than 20 knots **Percentage Frequency:**\ The length of the bars represents the percentage of time the wind came from a specific direction. Longer bars indicate higher frequency **Analysis Details:** * The location is displayed above the diagram, along with the height at which the wind analysis was conducted * The analysis period is shown at the bottom right, along with the coordinates of the analysis location
The wind rose overview is part of the analysis and, includes all monthly wind rose evaluations displayed together on a single page. The structure of the individual wind roses remains unchanged.
## Heatmaps {% hint style="info" %} Only available for detailed analyses. {% endhint %} The heatmaps display the average hourly wind conditions for the corresponding time frame. In this case, they summarize a one-year period and visualize the composition of wind speed and direction.
Structure **Y-Axis:** The Y-axis represents the percentage of time during which the wind speed/direction fell within a specific speed/direction range. **Speed Bins:** * 0–3 knots (light gray) * 3–6 knots (medium gray) * 6–10 knots (dark gray) * 10–15 knots (blue) * 15–20 knots (dark blue) * 20+ knots (red) **Direction Bins:** * 0° to 330° (in 30° increments) * Colors vary to clearly differentiate the individual directions, e.g.: * 0° (North) in blue * 90° (East) in green * 180° (South) in red * 270° (West) in brown **X-Axis (Hours in UTC):** Displays the hours of the day (in UTC) from 0 to 23. **Analysis Details:** The analysis location, time period, and the considered time of day are noted at the bottom of the diagram.
In addition to the annual evaluations, monthly evaluations are created. You will also receive a summary that displays all monthly evaluations, allowing you to quickly gain an overview.
# Service Availability Understanding the Components of Service Availability results. ## Operational Conditions per Year Operational conditions per year are visualized using pie charts. It shows the percentage distribution of operational conditions.
Structure **Pie Chart:** * The chart displays operational conditions in three categories, visualized using different colors. * The sections and percentage values of the chart represent the proportion of each operational condition over the course of the year. **Legend:** * The legend on the right explains the color coding: * Blue for nominal operating conditions * Dark blue for moderate operating conditions * Red for severe operating conditions **Analysis Details:** The analysis location, time period, and the considered time of day are noted at the bottom.
## Operational Conditions per Month Operational conditions per month are illustrated using column charts. These show the percentage distribution of operational conditions for each month individually, enabling a detailed temporal analysis of the conditions throughout the year.
Structure **Column Chart:** * The chart consists of 12 vertical bars, each representing a month from January to December. * The operational conditions for the respective months are color-coded. **Percentage Distribution:** * On the left side of the chart, a vertical scale from 0 to 100 is displayed, indicating the percentage distribution of operational conditions for each month. * The height of the bars corresponds to the respective percentage frequency of operational conditions in the corresponding month. **Legend:** * The legend below the chart explains the color coding: * Blue: Nominal operational conditions * Dark Blue: Moderate operational conditions * Red: Severe operational conditions **Analysis Details:** The analysis location, time period, and the considered time of day are noted at the bottom.
## Reasons for severe or moderate Condtions per Year Reasons for moderate and severe conditions are presented using bar charts to illustrate the ranking of the percentage distribution.
Structure **Bar Chart:** * The chart displays the causes of severe/moderate operational conditions, sorted in descending order by percentage share. * To the left of the bars, the respective parameters that cause severe conditions are named. * The altitude specification next to the designation of the parameter is the altitude at which the state of the operational conditions is evaluated. The altitude can be defined depending on the parameter when creating a limit set. **Analysis Details:** The analysis location, time period, and the considered time of day are noted at the bottom.
{% hint style="info" %} The sum of the shares of the causes for severe conditions can exceed 100% as these causes can occur simultaneously. {% endhint %} ## Reasons for severe or moderate Condtions per Month The reasons for moderate/severe conditions per month are illustrated using a line chart to highlight the development over time and between individual months. This allows for the quick identification of seasonal dependencies.
Structure **Line Chart:** * The chart consists of graphs that visualize how the percentage share of each cause contributing to severe operating conditions changes throughout the year. * The Y-axis shows the percentage of severe hours caused by each factor, and the X-axis represents the months from January to December. **Legend:** * Depending on the cause, the graphs are displayed in different colors: * Green (solid): General icing (at analysis altitude) * Orange (solid): General icing (at analysis altitude) * Purple (solid): Visibility * Pink (solid): Rain amount * Yellow (solid): Gust factor (at analysis altitude) * Dark green (solid): Wind speed (at analysis altitude) * Gray (solid): OAT (at analysis altitude) * Light blue (solid): General icing (at analysis altitude) * Teal (dashed): Cloud ceiling * Orange (dashed): Dangerous phenome **Analysis Details:** The analysis location, time period, and the considered time of day are noted at the bottom.
{% hint style="warning" %} Only available for detailed analyses. {% endhint %} {% hint style="info" %} If no severe conditions prevail in the month, the graph will be interrupted at that point. {% endhint %} {% hint style="info" %} The sum of the shares of the causes for severe conditions can exceed 100% as these causes can occur simultaneously. {% endhint %} ## Reasons for severe Condtions per Hour The line chart shows the average percentage shares of selected parameters contributing to severe weather conditions at each time of day within the corresponding month. The chart is created for each month in the detailed analysis, allowing for an in-depth examination of changes throughout the day.
Structure **Line Chart:** * Each line shows how the share of each cause contributing to severe operating conditions changes at different hours of the day.\ The Y-axis represents the percentage of severe operating conditions, and the X-axis represents the hours of the day from 0 to 23 UTC. **Legend:** * Depending on the cause, the graphs are displayed in different colors: * Green (solid): General icing (at analysis altitude) * Orange (solid): General icing (at analysis altitude) * Purple (solid): Visibility * Pink (solid): Rain amount * Yellow (solid): Gust factor (at analysis altitude) * Dark green (solid): Wind speed (at analysis altitude) * Gray (solid): OAT (at analysis altitude) * Light blue (solid): General icing (at analysis altitude) * Teal (dashed): Cloud ceiling * Orange (dashed): Dangerous phenomena **Analysis Details:** The analysis location, time period, and the considered time of day are noted at the bottom.
{% hint style="warning" %} Only available for detailed analyses. {% endhint %} {% hint style="warning" %} No hourly evaluation for moderate conditions. {% endhint %} ## Operational Conditions per Hour (Nominal / Nominal + Moderate) The heatmap chart shows the hourly distribution of nominal/nominal & moderate operational conditions as percentages for each month of the year. This chart is particularly useful when analyzing, for example, the time of day with the highest likelihood of nominal conditions over multiple months. It can also be used for seasonal and daily pattern analysis.
Structure **Legend:** * The values range from 0% to 100%, with the color scale visualizing the percentage magnitude. * Green represents higher percentages (close to 100%), while yellow to red indicates lower percentages. **Analysis Details:** The analysis location, time period, and the considered time of day are noted at the bottom.
{% hint style="warning" %} Only available for detailed analyses. {% endhint %} # Benchmark Analysis Understanding the Components of Benchmark Analysis results. {% hint style="info" %} The advantage of the benchmark analysis is the presentation of the results in bar charts, which allow for a quick and clear comparison of multiple locations. {% endhint %} ## Operational Conditions per Year The bar chart shows the annual percentage distribution of operational conditions in the categories nominal, moderate, and severe.
Structure **Horizontal Bar:** * Represents the operational conditions in blue, dark blue, and red colors. * The length of the sections corresponds to the occurrence of each condition. * A scale from 0 to 100 shows the percentage distribution. **Legend:** * Blue: Nominal operational conditions * Dark Blue: Moderate operational conditions * Red: Critical operational conditions **Analysis Details:** * The analysis location is specified to the left of the chart. * The analysis period and the considered time of day are noted at the bottom.
## Operational Conditions Months (Nominal / Nominal+Moderate) The bar charts show the monthly percentage distribution of nominal/nominal & moderate operational conditions, with a color scale visualizing the magnitude of the values.
Structure **Horizontal Bar:** * Colors range from green to yellow to red, depending on the occurrence of the analyzed operational conditions. * The values of nominal operational conditions are directly indicated for each month. * The months from January to December are listed below the corresponding section of the bar. **Legend:** * The scale ranges from 0 to 100 \[%]. * The legend is located to the right of the bar: * **Green:** High percentage of nominal/nominal & moderate operational conditions * **Yellow:** Medium percentage of nominal/nominal & moderate operational conditions * **Red:** Low percentage of nominal/nominal & moderate operational conditions **Analysis Details:** * The analysis location is specified to the left of the chart. * The analysis period and the considered time of day are noted at the bottom.
## Reasons for severe/moderate conditions The bar charts summarize the parameters contributing to moderate and severe conditions and display their percentage share of the total caused moderate and severe conditions.
Structure **Horizontal Bar:** * A color-coded bar representing the causes of severe/moderate operational conditions. * The respective parameters of the defined limit set are considered in the analysis. * Percentage values are directly indicated for each category on the bar. * The parameters are listed above their respective shares on the bar. **Legend:** * Red: High contribution to severe/moderate conditions * Blue: Moderate contribution to severe/moderate conditions * Gray: Low contribution to severe/moderate conditions **Analysis Details:** * The location is specified to the left of the chart. * The time period and time of day are noted at the bottom.
# Track Analysis Understanding the Components of Track Analysis results. {% hint style="info" %} The hourly weather data required for the evaluation of the track system are the average values of the weather data within a 1-hour interval. {% endhint %} dual, app, dep, general no avail? ## Monthly Track System Usability The diagrams display the monthly usability of a track system as a percentage, categorized by different availability types. The left chart represents track usability for standard take-off and landing routes, while the right chart focuses on vertiports (approach/departure route specified in degrees).
Structure **Balkendiagramm:** * Die Diagramm bestehen aus **12 vertikalen Balken**, die die Nutzbarkeit des Track-Systems für die Monate von **Januar bis Dezember** darstellen. * Jeder Balken zeigt die prozentuale Nutzbarkeit des Systems/der Strecke in einem bestimmten Monat. **Prozentuale Verteilung:** * Die Y-Achse zeigt den **Prozentsatz** der Nutzbarkeit, der von **0% bis 100%** reicht. **Legende:** * Dual (Dunkelblau): Nutzbarkeit beider Strecken * **App (Hellblau):** Nutzbarkeit der Anflugstrecke * Dep (Grau): Nutzbarkeit der Abflugstrecke * General No Avail (Rot): Keine Nutzbarkeit der Strecken **Analysedetails:** * Der Analysestandort, Zeitraum und der betrachtete Tagesabschnitt sind am unteren Rand vermerkt.
## Yearly Track System Usability The pie chart shows the annual distribution of system usability based on different categories. The left chart represents track usability for standard take-off and landing routes, while the right chart focuses on vertiports (approach/departure routes specified in degrees).
Structure **Kreisdiagramm (Tortendiagramm):** * Das Diagramm ist ein **Kreisdiagramm (Pie Chart)**, das die prozentuale Verteilung der Nutzbarkeit des Track Systems für das Jahr zeigt. * Linkeres zeigt die Track Usability für reguläre Start- und Landestrecken und rechtes für Vertiports an. * Da hier Approach und Departure zusammenfallen, wird bei der Analyse an einem Vertiport nur in zwei kategorien unterteilt **Legende:** * Dual (Dunkelblau): Nutzbarkeit beider Strecken * **App (Hellblau):** Nutzbarkeit der Anflugstrecke * Dep (Grau): Nutzbarkeit der Abflugstrecke * General No Avail (Rot): Keine Nutzbarkeit der Strecken **Analysedetails:** * Der Analysestandort, Zeitraum und der betrachtete Tagesabschnitt sind am unteren Rand vermerkt.
Alternative representation?: benchmark vergleich
Structure **Balkendiagramm:** * Das Diagramm besteht aus **einem einzigen Balken**, der die Nutzbarkeit des Systems für das gesamte Jahr darstellt. **Legende:** * Dual (Dunkelblau): Nutzbarkeit beider Strecken * **App (Hellblau):** Nutzbarkeit der Anflugstrecke * Dep (Grau): Nutzbarkeit der Abflugstrecke * General No Avail (Rot): Keine Nutzbarkeit der Strecken **Analysedetails:** * Der Analysestandort, Zeitraum und der betrachtete Tagesabschnitt sind am unteren Rand vermerkt.
## Wind Conditions over Altitude The diagram applies to a vertiport and shows the wind conditions related to the chosen altitude, classified for a specific location and period.
Structure **Balkendiagramm:** * Das Diagramm zeigt die Windbedingungen auf einer **vertikalen Achse**, die die analysierte Höhe angibt. * Für Vertiport Tracks Legende: * **Blau** für nominale Betriebsbedingungen. * **Dunkelblau** für moderate Betriebsbedingungen. * **Rot** für schwere Betriebsbedingungen. **Analysedetails:** * Der Analysestandort, Zeitraum und der betrachtete Tagesabschnitt sind am unteren Rand vermerkt.
## Detailed Wind Conditions over Altitude The diagram shows the distribution of different wind directions (crosswind left, crosswind right, tailwind, headwind) at a selected altitude, location, and time of day.
Structure **Balkendiagramm:** * Das Diagramm besteht aus **vier horizontalen Balken**, die jeweils eine Windrichtung repräsentieren: 1. **Cross Wind Left** (Wind von links) 2. **Cross Wind Right** (Wind von rechts) 3. **Tail Wind** (Rückenwind) 4. **Head Wind** (Gegenwind) **Prozentuale Verteilung:** * Jeder Balken zeigt den Prozentsatz der Windbedingungengrades für die entsprechende Windrichtung Legende: * **Blau** für nominale Betriebsbedingungen. * **Dunkelblau** für moderate Betriebsbedingungen. * **Rot** für schwere Betriebsbedingungen. **Analysedetails:** * Der Analysestandort, Zeitraum und der betrachtete Tagesabschnitt sind am unteren Rand vermerkt.
## Wind Conditions per Month The diagram shows the monthly usability of the vertiport based on the severity of weather conditions at a specific location and time of day.
Structure **Balkendiagramm:** * Das Diagramm besteht aus **12 vertikalen Balken**, die jeweils einen Monat des Jahres 2023 darstellen, von **Januar bis Dezember**.. **Prozentuale Verteilung:** * Auf der Y-Achse wird der **Prozentsatz** von **0% bis 100%** angezeigt. Legende: * **Blau** für nominale Betriebsbedingungen. * **Dunkelblau** für moderate Betriebsbedingungen. * **Rot** für schwere Betriebsbedingungen. **Analysedetails:** * Der Analysestandort, Zeitraum und der betrachtete Tagesabschnitt sind am unteren Rand vermerkt.
# Map Overview Understanding the Map Overview for Analysis results. The map overview is part of almost every type of analysis, it provides a spatial overview of the analyzed location. The location is displayed both on a map showing the continent where it is located and on a world map.

World map

Constance, Europe

The map is particularly useful when multiple locations need to be evaluated simultaneously. It provides a quick overview of the positions of all analysis locations and allows for the identification of potential geographical correlations.

World map

Constance, Europe

Singapore, Asia

Los Angeles, North America

# WEATHER INFORMATION SERVICE for U-SPACE # 1. Product Specification ## 1.1 Overall Description This document describes the Weather Information Service (WIS) for U-Space Applications by Unisphere. The WIS is a service in development at Unisphere providing EASA compliant weather and supplemental information and will be accessed by USSPs and UTMs via API. Although the WIS is not yet certified by EASA or any other regulatory body at the national level, Unisphere is working toward certification with continuous efforts applying aerospace standards for software development processes. The intention of the document is to describe the functionalities of the WIS. 1.2 Product Scope and References ### 1.2.1 General Scope and Timeline The scope of the WIS is to provide EASA compliant weather information for U-Space - as a service. The information will be provisioned via HTTP API through multiple endpoints at Unisphere. The product development process is performed to achieve compliance according to EASA regulation (EU) 2021/664 of 22 April 2021, Article 12. Independently of the actual certification the WIS will be operational before. The desired date for entry into service is 28.02.2023. ### 1.2.2 High Level Product Functions The WIS will provide basic weather information and forecasts, 1. to maintain safety and support operational decisions of other U-space services. 2. provide the UAS operator with weather forecasts and actual weather information either before or during the flight. The WIS will be based on authoritative weather sources. An authoritative source may be a Member State, or an organisation formally recognised by the Member State to originate and/or publish weather information which meets the data quality requirements in accordance with Annex III to the EASA regulation (2021/664). Even though non-authoritative sources may be used according to regulation, Unisphere at this stage does not intend to use non-authoritative sources for weather information. ## 1.3 Product Perspective Functions & EASA Compliance With the current regulation and todays´ technical means in place the WIS API will provide (weather) information of three types ways: 1. METAR / TAF information of nearby airports 2. Unaltered weather model data of from authoritative weather data service providers 3. Supplemental information (e.g. sunrise, sunset, elevation, kp-index) In order to assure compliance to EASA it is recommended to always provide access to nearby METAR observations to the downstream users of the WIS in clear text. # 2. Design Implementation Constraints ## 2.1 General Unisphere will provide weather information and observations through REST API to customers. Therefore, Unisphere integrates multiple weather service providers, extracts, transforms and provides data to USSP/UTM providers or other types of users conveniently.

Weather Information Service High Level Diagram

## 2.2 Data Quality & Obligations Unisphere guarantees that the weather information is UP-TO-DATE with latest available data of the source. * Upon receipt of updated weather information related to current weather, Unisphere assures to provides the data with within maximum 30 seconds. * Upon receipt of an updated weather forecast, the USSP should provide the information to the UAS operator within maximum 5 minutes from the time the data is being processed by the USSP. The USSP should inform the user when the information is not up to date. * Up-to-date weather information is considered as the last available data for the geographical point. * Unisphere is not responsible for ensuring that the data being exposed by the trusted source is effectively the last available data. Unisphere guarantees that the weather information is RELIABLE. * The source of the data at the request is documented in this document, chapter 3.4. * As long as not provided by the individual source of data Unisphere cannot provide a confidence level of the information and will not. Data will either be valid or not. * Unisphere assures to not tamper any information provided by the individual source. * The USSPs should ensure that the UAS operator is presented with accurate information that has not been tampered with information regarding the confidence level of the data where this is available at the source. # 3. Developers Guide For seamless integration work the WIS API is documented using Swagger accessible through the link below. {% embed url="" %} ## 3.1 Available Endpoints The WIS contain the following endpoints that deliver information based on the following categories: 1. Now – current weather values - how is the weather right now. 2. Forecast – weather data at a certain point in time in future (up to 24 hours). 3. Metar\_nearby – decoded METAR information and raw METAR of nearby station of requested location. 4. User & Subscription Information ## 3.2 Parameter Names in for NOW and FORECAST Endpoints
## 3.3 Parameter Names METAR\_NEARBY Endpoint
METAR information according ICAO Annex 3, July 2010. () ## 3.4 Data Sources If the API request is set to \ or not set at all the API response will return weather information from the best source available, the requested location (latitude/longitude). #### Weather information from authoritative sources Current implementation stage uses the WAWFOR GLOBAL or WAWFOR EU dataset provided by the German Weather Service (DWD). If the requested location is within the WAWFOR EU boundaries it will return the corresponding values. Else will respond in the WAWFOR global dataset. WAWFOR EU covers the following boundary box: Europe 23.5° W to 62.5° E / 29.5° N to 70.5° N WAWFOR GLO covers the following extensions: Global -180° to +180 / 80.0° N to 80.0° S #### METAR Information METAR information from nearby airports / weather observation stations will be provided as string through the API. It is recommended that METAR information always be displayed to the end user to ensure compliance due to the missing parameters of some authoritative weather sources. As a minimum (specified in paragraph 2. / EASA 2021/664 Article 12 Weather Information Service) the WIS will provide: 1. wind direction measured clockwise through the true north and speed in metres per second, including gusts; 2. the height of the lowest broken or overcast layer in hundreds of feet above ground level; 3. visibility in metres and kilometres; 4. temperature and dew point; 5. indicators of convective activity and precipitation; 6. the location and time of the observation, or the valid times and locations of the forecast; * (a) the location of the observation or forecast using: * (1) ICAO designator, where available; or * (2) the location expressed in WGS-84 coordinate. * (b) the validity of the observation or forecast by specifying: * (1) WGS-84 position or WGS-84 area of validity; and * (2) the time of the observation and/or the validity of the forecast in UTC time 7. appropriate QNH with geographical location of its applicability. 8. Other sources are named within the parameter table under chapter 3.2. Be aware that the provided METAR information can be multiple kilometres away from the requested location and therefore not sufficiently reflect the conditions on the requested location. ## 3.5 Performance ### 3.5.1 Software Interfaces The standards for communication interfaces with clients are: 1. REST API 2. Secured communication is achieved using the HTTPS protocol ### 3.5.2 Security Precautions 1. Authentication is managed through a dedicated API key for your organization (username & password). When subscribing to the WIS of Unisphere the API key will be shared through a secure channel. ### 3.5.3 Rate Limit 1. The initial rate limit of the WIS API is 1000 requests per minute for each endpoint 2. API response when reaching the rate limit: Response 429 - too many requests ### 3.5.4 Parallel Requests 1. The maximum number of parallel requests of the WIS API is 10 per minute and endpoint except not stated differently in the subscription. # 4. Subscription Plans ## 4.1 Overview The subscription model is a consumption-based model with pre-booked bundles of API calls per day. The available bundles are the following.
Subscription BundleAPI requests per daymonthly feeReference price per 100 API callsRate Limit (per min) / Parallel requests
Starter1.0001000 / 10
SME5.0001000 / 10
UTM10.0001000 / 10
Enterprise50.0005000 / 10
all prices excl. VAT. ### 4.1.1 Subscription duration Subscriptions are issued on an annual basis and are payable monthly or annually in advance. To ensure uninterrupted service and unless otherwise stated, the subscription will automatically renew for 12 months after expiration. You will receive an automatic notification to a specified email address of your choice when the subscription limit is reached. ### 4.1.2 Soft limit Exceeding the number of API requests per day over the number of calls included in the subscription is possible and does not lead to an interruption of the service. Excess requests will be charged quarterly for the exact number of calls exceeding the package volume at €X.XXX per call. ### 4.1.3 General Day is defined as day UTC. Unused API requests are not transferred to the next day. # 5. Other Terms ## 5.1 Unisphere Terms and Conditions Unisphere´s latest terms and license conditions apply. Please review for more information. ## 5.2 Service Level Agreement (SLA), Terms and Conditions If required, a service level agreement (SLA) will be established between the Unisphere and the customer and provided separately. ## 5.3 Quality Assurance In order to meet the data quality requirements, Unisphere ensures that: 1. data quality is maintained; 2. verification and validation techniques are employed to ensure that data is received without corruption and that corruption does not occur at any stage of the data process; 3. the metadata is collected and preserved. 4. the transfer of data is subject to a suitable authentication process such that recipients are able to confirm that the data or information has been transmitted by an authorised source. 5. error reporting, error measurement and corrective action mechanisms are established and maintained. ## 5.4 Data Protection In order to protect the data of our customers Unisphere 1. implements security policies, including data encryption and protection of critical data; 2. protects the open secure interoperable communication protocols from intentional unauthorised electronic interactions that may result in an unacceptable breakdown in communications; 3. identifies, assesses, and mitigates, as necessary, the security risks and vulnerabilities; 4. adheres to security standards and regulations regarding where data can be stored and ensure that third-party providers agree to follow security practices; 5. deploys solutions that augment threat detection and intelligence capabilities and ensure the use of technology safeguards. # UNISPHERE APIs This documentation provides a summary of the API services offered by Unisphere, detailing the ongoing developments and current state of the platform. It covers the core structure of Unisphere's APIs, high-level requirements, user stories, request and response schemas, and general guidelines. Updates will be made available regularly to reflect any changes or enhancements. # User Story & Requirements C1 – User Story * The flight operations manager of an organization has subscribed to NOVA. * He creates a route mission in NOVA web-application including all relevant assets. * After creation of a mission, he sees the ID of the mission. * He can copy the mission ID to further use it for programming. (To simplify this task of copying IDs from NOVA frontend the API provides an endpoint which lists all available assets, title and ID.) * The software engineer of the customer implements an internal software (The “external system” from Unisphere point of view) that allows its system to perform checks through the Unisphere API. * The external system sends a request and the API responds with a unique UUID which can be used to request the simulation result once it is ready. * Check my Flight validates the request and performs the flight check for the given mission ID, TO time and the battery SOC. * The API request performs basic validations of the input. * Once the simulation is finished, the result is available through the unique ID. * The output provides data only, no visualizations. * Requests and responses are archived and linked to organization (for tbd time) * * Basic and extended are archived * We store the first access time of request 2 (basic and extended), only the first, not all. * Usage counter per organization is integrated, to count checks executed per day. High Level Requirements 1. A check is defined as a flight path (vertical and lateral) with the help of simulation technology is evaluated (checked) against operational limits (e.g. flight time, maximum wind etc.). 2. A check is performed for a single flight with one specific TO time. 3. Check my Flight provides the functionality to do a check (one simulation) on the current (\~local) day until 7 days into future based on a given date and time as input. 4. No historic data will be able to be accessed. The takeoff-time shall be within today + 7 days 5. Even if the technology has no specific limit for simulation time, the following limits protect the system from massive API calls or long response times by erroneous input. 6. 1. The maximum flight duration time is 12 hours. Beyond a calculation of 12 hours the system aborts the simulation and reports maximum flight of X hours exceeded i. Response with ID, Response if too long, error message e.g. status code 5. 2. The maximum flight distance (great circle) allowed as an input is 2000km 3. If drift is observed in the simulation (aircraft speed against wind lower than wind speed) then simulation will abort and report a status code. 6. With the first request a UUID is created and responded. 7. Rate limits 8. 1. Requests per minute: 50 2. Parallel requests: 1 # Introduction to Unisphere APIs ## Unisphere API Philosophy Unisphere´s public APIs allow to use services/features / NOVA directly via API and provide direct access to technologies (Tech APIs). * NOVA API allows direct access to the same functionalities users will find on the NOVA Web application. E.g. CRUD operations for assets, operational limits, routes, missions etc. (non-exhaustive list). Some functionalities are not planned via public APIs at the moment e.g. user management, subscription management or similar. * Except for flight checks, anything created, updated or deleted in the NOVA frontend, or via a Unisphere API is synced. Factually there should be no difference whether an asset is created in the web app or via API. * Tech API allows direct access to technologies provided by Unisphere – e.g. Geo Information Service, or access to a trajectory simulation, services for U-Space Applications. They can, but must not be part of NOVA.
A scheme of Unisphere Public API that shows several levels: users → Public API → Web App Products

Unisphere Public API Scheme

## Product Hierarchy As part of our development roadmap, we are enhancing our technology by opening up multiple functionalities through a public REST API, making it accessible and integrate with external systems. The functionalities are categorized into three levels: missions, flights, and assets. Each functional level offers different granularity of requests. Initially, public API users will be able to interact with missions already available in NOVA. For example, users can request a check for a flight at a specific take-off time. In subsequent developments, the API will allow users of the API to include all necessary information to execute these checks directly without NOVA.
An overview of six API functions Unisphere offers

API Functions overview

# API Access ## General In order to access and make use of the API your organization must have a valid NOVA account, API bundle and API key. ## Main entry URL to API & Swagger The API can be accessed through: We also do public a dedicated swagger page acessible under: ## Creating an API key 1. Sign up your organization to NOVA. Skip if you already have an account. The detailed steps are listed [here](/nova/get-started). 2. Log into your [NOVA account](https://nova.unisphere.io/login). 3. Under “Settings” , create an API key for your organization.
API Integration as part of organization settings within NOVA account.

Browse to API Integration on the Account page

An example of three created API keys within NOVA Platform

Create a new API key

{% hint style="info" %} The number of API keys is limited 5. {% endhint %} ## Give it a try and check your account status With the API key you are all set to start using the Endpoints of Unisphere API. Give it a try here: {% content-ref url="/pages/d9ba9lSCyrpy6kIqgwjH" %} [Utilities & Health](/unisphere-apis/utilities-and-health) {% endcontent-ref %} # Limitations Available Timeframe Caching # Flight Trajectory Simulation - FTS ## Basics The Flight Trajectory Simulation allows users to request a flight simulation along a given 3D route to retrieve flight time, flight progress over time along the flight path, and energy information. The 3D route can be defined as 1. a route-asset within NOVA, or 2. is defined with LAT/LON/ALT and sent with the request. TO Time only current UTC day + 168h ## Simulation Modes **Without NOVA** {% tabs %} {% tab title="FTS2 – With an individual Route" %} {% endtab %} {% tab title="Advanced - With OEM performance model" %} **Note:** The option to simulated with an OEM owned performance model is only possible if the ID if the performance model is known by your organization. The OEM performance model is engineered by Unisphere based on flight telemetry data and then provision in the API.\ \ Same as basic except performance model ID is provided in the API request. {% endtab %} {% endtabs %} **With NOVA XXX** Speed command options * EAS (Equivalent Airspeed) or, * GS (Ground Speed) {% hint style="info" %} Ground Speed (GS) commands are often used by multicopter drones and is the speed relative to ground. When GS is commanded the autopilot (and the simulation) of the aircraft tries to reach the target ground speed whatever the wind conditions are. Equivalent Air Speed (EAS) commands the target speed of the aircraft relative to wind. EAS commands are often used by fixed-wing and hybrid drone systems on en-route flight where their speed is measured by a pitot tube. {% endhint %} # Flight Trajectory Simulation - FTS ## Basics The Flight Trajectory Simulation allows users to request a flight simulation along a given 3D route to retrieve flight time, flight progress over time along the flight path, and energy information.
A graphic showing an example of an FTS (Flight Trajectory Simulation)
## Input required ### Route Information The 3D route can be defined by 1. ~~Route asset as defined in NOVA~~ (foreseen as FTS1) 2. LAT/LON/ALT and sent with the request (FTS2) ### Aircraft Performance Information **Speeds** * Ground Speed or Air Speed Command & max speed * Rate of Climb (RoC) and Rate of Descent (RoD) * Endurance in seconds / minutes {% hint style="info" %} Ground Speed (GS) commands are often used by multicopter drones and is the speed relative to ground. When GS is commanded the autopilot (and the simulation) of the aircraft tries to reach the target ground speed whatever the wind conditions are. Equivalent Air Speed (EAS) commands the target speed of the aircraft relative to wind. EAS commands are often used by fixed-wing and hybrid drone systems on en-route flight where their speed is measured by a pitot tube. {% endhint %} ## Additional Information The trajectory simulation results can take up to **30 seconds**, depending on its path, length, and altitude. The available timeframe is UTC+00 today until UTC+168h. # FTS2 Endpoints {% openapi src="" path="/flight-trajectory/v1/fts2" method="post" %} {% endopenapi %} {% openapi src="" path="/flight-trajectory/v1/fts2/{simulation\_id}" method="get" %} {% endopenapi %} # Check My Flight - CMF The Check my Flight functionality allows the user to receive evaluated flight data for a simulated flight trajectory for a specific takeoff time up to 7 days into the future. {% hint style="info" %} **Use Case:** Automated flight window identification, Resource Planning & Scheduling for points / routes / areas / volumes. {% endhint %} ## Key functionalities * CMF performs a check for a single and unique flight for a certain takeoff time. * The check my flight functionality uses the latest information available to automatically decide for go or no go to an upcoming flight. * In general, a check consists of: * For route, a flight simulation is performed to retrieve the 4D-trajectory information * The 4D trajectory is the main source of information to be checked / evaluated. Depending on the length of the flight the time until the check is completed is expected to take about 30s. * Check my flight is only working with flights containing a route, not locations. * Each check requested is saved and archived.
Overview of Check my Flight Endpoints showing three modes: check my flight for 1) this mission in NOVA, 2) this route, 3) all information provided in the request.

Overview of Check my Flight Endpoints

### CMF 1 * User provides the UUIID of an existing mission in NOVA, the TO (take-off) time and BatSoc (Battery state of charge) ### **CMF 2** * User provides the UUIDs of the assets in NOVA, the route, the TO (take-off) time and BatSoc (Battery state of charge) ### **CMF 3** * User provides all information required to perform a check including the route, the aircraft, the performance model, the operational limits the TO (take-off) time and BatSoc (Battery state of charge). In this mode the NOVA UI is not required a such. ## Workflow Create Simulation using CMM1/2/3- Receive Simulation Id - Get results with simulation ID ## Request and Response Content {% hint style="info" %} Details for request and response schemes vary depending on the actual endpoint. Refer to the latest version ... {% endhint %} ### 1 - Check Request This request is required to trigger a trajectory simulation. It typically consists of: 1. ISO Time and date of the flight (TO time) 2. The mission ID 3. Battery State of Charge at TO in % 4. Metadata (dictionary) ### 2 - Response Simulation ID ### 3 - Results Request 1. Provide simulation ID 2. Select response type (basic/extended) ### 4 - Response **The basic response consists of:** * UUID for this flight check * Metadata * Date / Time of Request 1 * System Status (OK, NOK) * Check result, Flight Status: * Go (Green), * Conditional (yellow), Notification of why (List yellow parameters) * NoGo (Red), Reasons for NoGo (List red parameters and yellow parameters) * High Level (Flight) Information * The distance of the route along the horizontal path is calculated w/o weather * The flight time w/o weather. It is calculated based on the rough calculation using the target ground speed provided or the EAS provided. No atmospheric effects (e.g. TAS) to be covered. * TO Time (UTC) * Trip Duration calculated by simulation in seconds * LDG Time (UTC) * State of Charge at TO in % * State of Charge at LDG in % * Energy consumption in % * Endurance at TO in s * Remaining Endurance at LDG in s * Elevation of earth surface above SL at TO location (COPERNICUS COP DEM GLO) * Elevation of earth surface above SL at LDG location (COPERNICUS COP DEM GLO) * Min/max values of all weather (defined in limit sets) parameters along the flight path **The extended response consists of:** * LAT/LON of all points in sequence * Time at points Evaluation of segment after the given point (between current and next one) * GS (ground speed) * EAS (equivalent airspeed) * Weather parameter information along flight path, as defined in the assets # CMF Endpoints ## Simulation Creation {% openapi src="" path="/check-my-flight/v1/cmf1" method="post" %} {% endopenapi %} {% openapi src="" path="/check-my-flight/v1/cmf2" method="post" %} {% endopenapi %} {% openapi src="" path="/check-my-flight/v1/cmf3" method="post" %} {% endopenapi %} ## Retrieve Results {% openapi src="" path="/check-my-flight/v1/cmf/{simulation\_id}" method="get" %} {% endopenapi %} # CMF Supporting Functions This page is dedicated to resources you need to execute CMF. {% openapi src="" path="/check-my-flight/v1/mission\_ids" method="get" %} {% endopenapi %} {% openapi src="" path="/check-my-flight/v1/performance\_set\_ids" method="get" %} {% endopenapi %} {% openapi src="" path="/check-my-flight/v1/performance\_set\_ids/{performance\_set\_id}" method="get" %} {% endopenapi %} {% openapi src="" path="/check-my-flight/v1/limit\_set\_ids" method="get" %} {% endopenapi %} {% openapi src="" path="/check-my-flight/v1/limit\_set\_ids/{limit\_set\_id}" method="get" %} {% endopenapi %} # Examples Find below an example for CMF3 which you can use to build up your request structure. ## Scenario A - BVLOS Delivery Flight Route & Vertical Profile Aircraft Performance Aircraft Limitations Operational Limitations Takeoff Time Battery State of Charge at Takeoff ### Step 1 - Create a Flight Simulation ```javascript // Example Mission const response = await fetch('/check-my-flight/v1/cmf3', { method: 'POST', headers: { "Content-Type": "application/json" }, body: JSON.stringify({ "performance_parameters": [ { "name": "text", "type": "text", "unit": "text", "value": 0 } ], "limit_parameters": [ { "name": "text", "type": "text", "unit": "text", "altitude_type": "text", "altitude_unit": "text" } ], "route": [ { "latitude": 0, "longitude": 0, "altitude": 0, "altitude_type": "AGL" } ], "take_off": "2024-10-22T08:51:04.497Z", "battery_soc": 0 }), }); const data = await response.json(); ``` # Check My Mission - CMM ## Available Functions for Check My Mission CMM1 * User provides the UUIID of an existing mission in NOVA … and gets evaluations of … 1h- +168h CMM2 * User provides the UUIDs of the assets (**for a non-existing mission**) in NOVA, the route … and gets evaluations of … 1h- +168h CMM3 * User provides all information required to perform a check including the route, the aircraft, the performance model, the operational limits. In this mode the NOVA UI is not required a such. … and gets evaluations of … 1h- +168h ## Workflow Create Simulation using CMM1/2/3- Receive Simulation Id - Get results with simulation ID # CMM Endpoints {% openapi src="" path="/check-my-mission/v1/cmm1" method="post" %} {% endopenapi %} {% openapi src="" path="/check-my-mission/v1/cmm2" method="post" %} {% endopenapi %} {% openapi src="" path="/check-my-mission/v1/cmm3" method="post" %} {% endopenapi %} ## Get Results {% openapi src="" path="/check-my-mission/v1/cmm/{simulation\_id}" method="get" %} {% endopenapi %} ## Get Extended Results {% openapi src="" path="/check-my-mission/v1/cmm/{simulation\_id}/{take\_off\_time}" method="get" %} {% endopenapi %} # CMM Supporting Functions {% openapi src="" path="/check-my-mission/v1/mission\_ids" method="get" %} {% endopenapi %} {% openapi src="" path="/check-my-mission/v1/performance\_set\_ids" method="get" %} {% endopenapi %} {% openapi src="" path="/check-my-mission/v1/performance\_set\_ids/{performance\_set\_id}" method="get" %} {% endopenapi %} {% openapi src="" path="/check-my-mission/v1/limit\_set\_ids" method="get" %} {% endopenapi %} {% openapi src="" path="/check-my-mission/v1/limit\_set\_ids/{limit\_set\_id}" method="get" %} {% endopenapi %} # Data Storage & Logging In case you need to access your simulation results for storage or compliance purposes, the simulations IDs of all executed simulations are kept in our system for 14 days. Use the respective endpoints for CMF, CMM or Trajectory Simulation to request the simulation results. # Asset Management Endpoints {% openapi src="" path="/check-my-mission/v1/mission\_ids" method="get" %} {% endopenapi %} {% openapi src="" path="/check-my-flight/v1/performance\_set\_ids" method="get" %} {% endopenapi %} # API Key Management You can create an API key for your organization within NOVA. If you do not see the API button your organization has not acquired the API subscription. Please contact us under .
An interface screenshot of the API Key Management in NOVA

API Key Management in NOVA

# Utilities & Health {% openapi src="" path="/user\_stats" method="get" %} {% endopenapi %} {% openapi src="" path="/health" method="get" %} {% endopenapi %} {% openapi src="" path="/version" method="get" %} {% endopenapi %} # Explanatory Notes # Storage of Data All the flight trajectory simulations and checks performed are stored in our system for XX days. You can always access stored simulations using the simulation ID. You can find all your saved simulation IDs here. # Temporal Differentiation

Termporal Differntiation

# Available Parameters The following list shows the available parameters for operational and aircraft limit sets.
API_nameDescriptionDisplay Name
wind_speed_mean_1hThe mean wind speed within a 1 hour interval. Available altitude range: 10-20000mWindSpeedMean1h
wind_direction_mean_1hThe mean wind direction within a 1 hour interval. Available altitude range: 10-20000mWindDirectionMean1h
wind_gust_1hThe mean wind gusts within a 1 hour interval. Wind gust includes the mean wind. Available altitude range: 10-20000mWindGust1h
precip_1hAccumulated precipitation within a 1 hour interval. The following categories are used to classify rainfall intensity: < 2.5 mm/h Light rain 2.5-7.6 mm/h Moderate rain > 7.6 mm/h Heavy rainPrecip1h
precip_prob_1hProbability of rain within a 1 hour interval.PrecipProb1h
outside_air_temperature_mean_1hThe outside air temperature (OAT). Available altitude range: 2-20000mOutsideAirTemperatureMean1h
cloud_cover_low_percCloud coverage between 0-2 km above ground level. (0-100 %)CloudCoverLowPerc
cloud_cover_medium_percCloud coverage between 2-7 km above ground level. (0-100 %)CloudCoverMediumPerc
cloud_cover_high_percCloud coverage between 7-10 km above ground level. (0-100 %)CloudCoverHighPerc
cloud_cover_totalThe total cloud coverage is the fraction of the sky covered by all the visible clouds. (0-100 %)CloudCoverTotal
cloud_baseThe cloud base gives the lowest altitude of the visible portion of a cloud.CloudBase
cloud_ceilingThe cloud ceiling is defined as the height of the lowest cloud layer covering more than half of the sky. A value of -666 denotes that there is no ceiling. Still, clouds can be there, covering less than 50% of the sky. Refer to cloud base as parameter.CloudCeiling
visibilityVisibility on ground.Visibility
dew_point_mean_1hDew point temperature. Available altitude range: 2-20000mDewPointMean1h
relative_humidity_mean_1hRelative humidity within a 1 hour interval. Available altitude range: 2-20000mRelativeHumidityMean1h
lifted_indexThe lifted index is the difference between the temperature of the environment and that of an air parcel lifted adiabatically to a given pressure height in the troposphere, usually 500 hPa which is an index for instability in the air mass. The atmosphere at the given height is stable for positive values of the lifted index and unstable for negative values. When the value falls below -2, thunderstorms are anticipated and for lower values, especially those below -6, severe weather is expected.LiftedIndex
cape_indexThe convective available potential energy index (CAPE index) is the amount of energy a parcel of air would have if lifted a certain distance vertically through the atmosphere. Any value greater than 0 J/kg indicates instability and an increasing probability of thunderstorms and hail.CapeIndex
thunderstorm_prob_1hProbability of a thunderstorm to occur within a 1 hour interval. (0-100 %)ThunderstormProb1h
gust_factorThe gust factor is defined as the difference between the peak wind gust of a 1 hour interval and the mean wind speed in the same period of time. Available altitude range: 10-10000mGustFactor
spreadDifference between outside air temperature and the dew point temperature. Available altitude range: 2-20000mSpread
general_icingIcing conditions were identified based on the analysis of temperature and relative humidity combinations. This method represents a conservative approach since no droplet size or cloud data was considered. At some points, this more conservative approach might lead to overestimations.GeneralIcing
kp_indexThe KP-index gives a quantification of the disturbance of the magnetic field of the earth. Sun storms can disrupt GNSS (GPS) signals causing GNSS receivers to give misleading or wrong information. NOAA provides data for the period of 7 days. The Kp index is a quasi-logarithmic local index ranging from 0 to 9: 0-4 quiet period, 4-5 mild activity 5-9, high intensity storm.KPIndex
icing_potentialIcing is absolutely critical in aviation and in-flight icing on planes are the cause of multiple near-accidents or even crashes. Consequently, it is crucial for aviation to have reliable icing forecasts predicting the expected occurrence of icing on different altitudes and allowing for early circumnavigation. 0-0.2: No icing, 0.2-0.4: Traces of icing, 0.4-0.6: Light icing, 0.6-0.8: Moderate icing, 0.8-1: Heavy icing.IcingPotential
--- [Next Page](/llms-full.txt/1)