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.
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.
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.


When an external file is uploaded, the route is automatically loaded from its data (see External file creation). If altitude information is not provided in the file, you may add altitude data to the waypoints manually (see 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.
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.
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 (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 <LineString>
, which is expected to include an altitude reference and coordinates of the route. A minimal example is given below.
Currently, NOVA supports relativeToGround
andabsolute
asaltitudeMode.
<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://www.opengis.net/kml/2.2">
<Document>
<Placemark>
<name>
UP Testflight
</name>
<LineString>
<altitudeMode>
relativeToGround
</altitudeMode>
<coordinates>
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
</coordinates>
</LineString>
</Placemark>
</Document>
</kml>
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 dialogLast updated
Was this helpful?