diff --git a/docs/manual.epub b/docs/manual.epub index 4e18072d..7476356e 100644 Binary files a/docs/manual.epub and b/docs/manual.epub differ diff --git a/docs/manual.pdf b/docs/manual.pdf index 24e56474..cfa3ac2b 100644 Binary files a/docs/manual.pdf and b/docs/manual.pdf differ diff --git a/docs/manual/01-intro/01-think.html b/docs/manual/01-intro/01-think.html index b7328878..4eab6507 100644 --- a/docs/manual/01-intro/01-think.html +++ b/docs/manual/01-intro/01-think.html @@ -1 +1 @@ - Think before you fly Skip to content

Think before you fly

Enroute Flight Navigation is a free software product that has been published in the hope that it might be useful as an aid to prudent navigation. It comes with no guarantees. It may not work as expected. Data shown to you might be wrong. Your hardware may fail.

This app is no substitute for proper flight preparation or good pilotage. Any information must always be validated using an official navigation and airspace data source.

Warning

Always use official flight navigation data for flight preparation and navigate by officially authorized means. The use of non-certified navigation devices and software like Enroute Flight Navigation as a primary source of navigation may cause accidents leading to loss of lives.

We do not believe that the use of Enroute Flight Navigation fulfills the requirement of the EU Regulation No 923/2012:SERA.2010

Before beginning a flight, the pilot-in-command of an aircraft shall become familiar with all available information appropriate to the intended operation.

To put it simply: relying on Enroute Flight Navigation as a primary means of navigation is most likely illegal in your jurisdiction. It is most certainly stupid and potentially suicidal.

Software limitations

Enroute Flight Navigation is not an officially approved flight navigation software. It is not officially approved or certified in any way. The software comes with no guarantee and might contain bugs.

Operating system limitations

We expect that most users will run the software on mobile phones or tablet computers running the Android operating system. Android is not officially approved or certified for aviation. While we expect that the app will run fine for the vast majority of Android users, please keep the following in mind.

  • The Android operating system can decide at any time to terminate Enroute Flight Navigation or to slow it down to clear resources for other apps.

  • Other apps might interfere with the operation of Enroute Flight Navigation.

  • Many hardware vendors, most notably One Plus, Huawei and Samsung equip their phone with “battery saving apps” that randomly kill long-running processes. These apps cannot be uninstalled by the users, do not comply with Android standards and are often extremely buggy. At times, users can manually excempt apps from “battery saving mode”, but the settings are usually lost on system updates. Google’s own “Pixel” and “Nexus” devices do not have these problems. See the website Don’t kill my app for more information.

Hardware limitations

Enroute Flight Navigation runs on a variety of hardware platforms, but we expect that most users will run the software on mobile phones, tablet computers and comparable consumer electronic devices that are not certified to meet aviation standards. Keep the following in mind.

  • Your device might not be designed to operate continuously for extended periods of time, in particular if the display is on.

  • Your device can overheat. Batteries can catch fire.

  • Battery capacity is limited. Even if your device is connected to power via a USB cable, the display and/or CPU might use more energy than USB can deliver.

\ No newline at end of file + Think before you fly Skip to content

Think before you fly

Enroute Flight Navigation is a free software product that has been published in the hope that it might be useful as an aid to prudent navigation. It comes with no guarantees. It may not work as expected. Data shown to you might be wrong. Your hardware may fail.

This app is no substitute for proper flight preparation or good pilotage. Any information must always be validated using an official navigation and airspace data source.

Warning

Always use official flight navigation data for flight preparation and navigate by officially authorized means. The use of non-certified navigation devices and software like Enroute Flight Navigation as a primary source of navigation may cause accidents leading to loss of lives.

We do not believe that the use of Enroute Flight Navigation fulfills the requirement of the EU Regulation No 923/2012:SERA.2010

Before beginning a flight, the pilot-in-command of an aircraft shall become familiar with all available information appropriate to the intended operation.

To put it simply: relying on Enroute Flight Navigation as a primary means of navigation is most likely illegal in your jurisdiction. It is most certainly stupid and potentially suicidal.

Software limitations

Enroute Flight Navigation is not an officially approved flight navigation software. It is not officially approved or certified in any way. The software comes with no guarantee and might contain bugs.

Operating system limitations

We expect that most users will run the software on mobile phones or tablet computers running the Android operating system. Android is not officially approved or certified for aviation. While we expect that the app will run fine for the vast majority of Android users, please keep the following in mind.

  • The Android operating system can decide at any time to terminate Enroute Flight Navigation or to slow it down to clear resources for other apps.

  • Other apps might interfere with the operation of Enroute Flight Navigation.

  • Many hardware vendors, most notably One Plus, Huawei and Samsung equip their phone with “battery saving apps” that randomly kill long-running processes. These apps cannot be uninstalled by the users, do not comply with Android standards and are often extremely buggy. At times, users can manually excempt apps from “battery saving mode”, but the settings are usually lost on system updates. Google’s own “Pixel” and “Nexus” devices do not have these problems. See the website Don’t kill my app for more information.

Hardware limitations

Enroute Flight Navigation runs on a variety of hardware platforms, but we expect that most users will run the software on mobile phones, tablet computers and comparable consumer electronic devices that are not certified to meet aviation standards. Keep the following in mind.

  • Your device might not be designed to operate continuously for extended periods of time, in particular if the display is on.

  • Your device can overheat. Batteries can catch fire.

  • Battery capacity is limited. Even if your device is connected to power via a USB cable, the display and/or CPU might use more energy than USB can deliver.

\ No newline at end of file diff --git a/docs/manual/01-intro/02-installation.html b/docs/manual/01-intro/02-installation.html index 0b58d4a4..ebc50554 100644 --- a/docs/manual/01-intro/02-installation.html +++ b/docs/manual/01-intro/02-installation.html @@ -1 +1 @@ - Installation and setup Skip to content

Installation and setup

App installation

Installation on mobile devices

Enroute Flight Navigation is available for free on Google Play and on the App Store.

Installation on Linux desktop machines

Enroute Flight Navigation is available for free on flathub.org. Depending on your Linux distribution, you might also find the app in the software management application on your computer.

After installation, start the app. Depending on the platform, you might need to grant the necessary permissions. You will be asked to accept the terms and conditions.

Enroute Flight Navigation cannot be used without geographic maps. As the last step in the installation, the app will suggest downloading maps that are relevant for your current location. Once the map download has finished, Enroute Flight Navigation will process the map data and update the map display after a minute or so.

Set aircraft specifics

We recommend that you tell Enroute Flight Navigation a little about your aircraft before you fly.

  • Open the Menu by touching the menu button in the upper right side of the screen.

  • Choose the menu item Aircraft. The aircraft page will then open.

Aircraft settings

Aircraft specifics

Please fill in the relevant data. While not every data item is used in the present version of Enroute Flight Navigation, we expect that future versions of the app will use all the data that is requested on this page.

Tap or click on the arrow symbol ‘←’ or use the Android ‘Back’ button to leave the map page and return to the main screen.

Done.

You are now ready to go. There are many things that you could set up at this stage, but we recommend that you simply look around and play with the app. Continue with the next section and take it for your first flight.

\ No newline at end of file + Installation and setup Skip to content

Installation and setup

App installation

Installation on mobile devices

Enroute Flight Navigation is available for free on Google Play and on the App Store.

Installation on Linux desktop machines

Enroute Flight Navigation is available for free on flathub.org. Depending on your Linux distribution, you might also find the app in the software management application on your computer.

After installation, start the app. Depending on the platform, you might need to grant the necessary permissions. You will be asked to accept the terms and conditions.

Enroute Flight Navigation cannot be used without geographic maps. As the last step in the installation, the app will suggest downloading maps that are relevant for your current location. Once the map download has finished, Enroute Flight Navigation will process the map data and update the map display after a minute or so.

Set aircraft specifics

We recommend that you tell Enroute Flight Navigation a little about your aircraft before you fly.

  • Open the Menu by touching the menu button in the upper right side of the screen.

  • Choose the menu item Aircraft. The aircraft page will then open.

Aircraft settings

Aircraft specifics

Please fill in the relevant data. While not every data item is used in the present version of Enroute Flight Navigation, we expect that future versions of the app will use all the data that is requested on this page.

Tap or click on the arrow symbol ‘←’ or use the Android ‘Back’ button to leave the map page and return to the main screen.

Done.

You are now ready to go. There are many things that you could set up at this stage, but we recommend that you simply look around and play with the app. Continue with the next section and take it for your first flight.

\ No newline at end of file diff --git a/docs/manual/01-intro/03-firstFlight.html b/docs/manual/01-intro/03-firstFlight.html index 0ae54b6b..8706a8cb 100644 --- a/docs/manual/01-intro/03-firstFlight.html +++ b/docs/manual/01-intro/03-firstFlight.html @@ -1 +1 @@ - Before your first flight Skip to content

Before your first flight

Now you are ready for the first use of Enroute Flight Navigation. General operation is very intuitive. Still, we recommend that you take a minute to make yourself familiar with the moving map display and with the basic controls before you take the app on its first flight. The section Main Page and Moving Map covers the moving map in more detail.

The moving map

After startup, the app will show a moving map, similar in style to the standard ICAO maps that most pilots are used to. You can use the standard gestures to zoom and pan the map to your liking. The figures Moving map display on the ground and Moving map display in flight shows how the map will typically look.

Moving map display on the ground

Moving map display on the ground

Moving map display in flight

Moving map display in flight

Initially, your own position is shown as a blue circle (or gray if the system has not yet acquired a valid position). Once you are moving, your own position is shown as a blue arrow shape. The flight path vector shows the projected track for the next five minutes, sized so that each of the black and white segments corresponds to one minute.

Projected flight path for the next five minutes

Projected flight path for the next five minutes

Note

When you start the app for the first time, you will probably see a bright red aircraft symbol in the lower left corner of the map. This symbol indicates that the app is not connected to the traffic data receiver of your aircraft, so that traffic will not be shown on the moving map.

Once you are familiar with the app, please have a look at the Section Connect to your traffic receiver of this manual.

The Navigation Bar

The bottom of the display shows a little panel with the following information.

Code

Meaning

T.TALT

True altitude (=geometric altitude) above sea level.

FL

Flight level.

GS

Ground speed.

TT

True track.

UTC

Current time.

The flight level is only available if your device is connected to a traffic receiver (such as a PowerFLARM device) that reports the pressure altitude. Flight level and current time are hidden if the display is not wide enough.

Warning

Vertical airspace boundaries are defined by pressure altitudes (with respect to QNH or standard pressure). Depending on temperature and air density, the pressure altitude will differ from the true altitude that is shown by the app. Never use true altitude to judge vertical distances to airspaces.

Interactive controls

In addition to the pan and pinch gestures, you can use the following buttons to control the app.

Symbol

Function

../_images/ic_menu.png

Open main menu

../_images/NorthArrow.png

Switch between display modes north up and track up.

../_images/ic_my_location.png

Center map about own position.

../_images/ic_add.png

Zoom in

../_images/ic_remove.png

Zoom out

../_images/ic_airplanemode_active.png

This control is shown when the app is not connected to a traffic data receiver. A click opens the traffic receiver status page.

Information about airspaces, airfields and other facilities

Double tap or tap-and-hold anywhere in the map to obtain information about the airspace situation at that point. If you double tap or tap-and-hold on an airfield, navaid or reporting point, detailed information about the facility will be shown. The figure Information about EDFE airport shows how this will typically look.

Information about EDFE airport

Information about EDFE airport

Go flying!

Enroute Flight Navigation is designed to be simple. We think that you are now ready to take the app on its first flight. There are of course many more things that you can do. Play with the app and have a look at the next section Further Steps.

\ No newline at end of file + Before your first flight Skip to content

Before your first flight

Now you are ready for the first use of Enroute Flight Navigation. General operation is very intuitive. Still, we recommend that you take a minute to make yourself familiar with the moving map display and with the basic controls before you take the app on its first flight. The section Main Page and Moving Map covers the moving map in more detail.

The moving map

After startup, the app will show a moving map, similar in style to the standard ICAO maps that most pilots are used to. You can use the standard gestures to zoom and pan the map to your liking. The figures Moving map display on the ground and Moving map display in flight shows how the map will typically look.

Moving map display on the ground

Moving map display on the ground

Moving map display in flight

Moving map display in flight

Initially, your own position is shown as a blue circle (or gray if the system has not yet acquired a valid position). Once you are moving, your own position is shown as a blue arrow shape. The flight path vector shows the projected track for the next five minutes, sized so that each of the black and white segments corresponds to one minute.

Projected flight path for the next five minutes

Projected flight path for the next five minutes

Note

When you start the app for the first time, you will probably see a bright red aircraft symbol in the lower left corner of the map. This symbol indicates that the app is not connected to the traffic data receiver of your aircraft, so that traffic will not be shown on the moving map.

Once you are familiar with the app, please have a look at the Section Connect to your traffic receiver of this manual.

The Navigation Bar

The bottom of the display shows a little panel with the following information.

Code

Meaning

T.TALT

True altitude (=geometric altitude) above sea level.

FL

Flight level.

GS

Ground speed.

TT

True track.

UTC

Current time.

The flight level is only available if your device is connected to a traffic receiver (such as a PowerFLARM device) that reports the pressure altitude. Flight level and current time are hidden if the display is not wide enough.

Warning

Vertical airspace boundaries are defined by pressure altitudes (with respect to QNH or standard pressure). Depending on temperature and air density, the pressure altitude will differ from the true altitude that is shown by the app. Never use true altitude to judge vertical distances to airspaces.

Interactive controls

In addition to the pan and pinch gestures, you can use the following buttons to control the app.

Symbol

Function

../_images/ic_menu.png

Open main menu

../_images/NorthArrow.png

Switch between display modes north up and track up.

../_images/ic_my_location.png

Center map about own position.

../_images/ic_add.png

Zoom in

../_images/ic_remove.png

Zoom out

../_images/ic_airplanemode_active.png

This control is shown when the app is not connected to a traffic data receiver. A click opens the traffic receiver status page.

Information about airspaces, airfields and other facilities

Double tap or tap-and-hold anywhere in the map to obtain information about the airspace situation at that point. If you double tap or tap-and-hold on an airfield, navaid or reporting point, detailed information about the facility will be shown. The figure Information about EDFE airport shows how this will typically look.

Information about EDFE airport

Information about EDFE airport

Go flying!

Enroute Flight Navigation is designed to be simple. We think that you are now ready to take the app on its first flight. There are of course many more things that you can do. Play with the app and have a look at the next section Further Steps.

\ No newline at end of file diff --git a/docs/manual/02-advanced/airspace.html b/docs/manual/02-advanced/airspace.html index 6c8506a5..eb3f5c29 100644 --- a/docs/manual/02-advanced/airspace.html +++ b/docs/manual/02-advanced/airspace.html @@ -1 +1 @@ - Import airspace data Skip to content

Import airspace data

Enroute Flight Navigation comes with a set of aviation maps that cover large parts of the world and are updated frequently. In addition, users can import airspace data in standard OpenAir format. Aviation clubs and airfield operators use this feature to distribute OpenAir files to their members to highlight noise-sensitive areas or airspaces available by local agreement.

Import OpenAir files on Android devices

If you are using an Android device, you must transfer the OpenAir file to the device and open it there. There are many ways to transfer files, but most users will likely do one of the following.

  • Download the OpenAir file on the Android device with a web browser. The browser will then offer to open the file in Enroute Flight Navigation.

  • Download the OpenAir file to a desktop computer, connect the device to the desktop computer via USB, and then copy the file to the device. Afterward, open the file with a file management app on the Android device.

Import Maps on Linux Desktop

If you are running Enroute Flight Navigation on a Linux Desktop machine, use the file manager to drag and drop the file into the app’s main window.

\ No newline at end of file + Import airspace data Skip to content

Import airspace data

Enroute Flight Navigation comes with a set of aviation maps that cover large parts of the world and are updated frequently. In addition, users can import airspace data in standard OpenAir format. Aviation clubs and airfield operators use this feature to distribute OpenAir files to their members to highlight noise-sensitive areas or airspaces available by local agreement.

Import OpenAir files on Android devices

If you are using an Android device, you must transfer the OpenAir file to the device and open it there. There are many ways to transfer files, but most users will likely do one of the following.

  • Download the OpenAir file on the Android device with a web browser. The browser will then offer to open the file in Enroute Flight Navigation.

  • Download the OpenAir file to a desktop computer, connect the device to the desktop computer via USB, and then copy the file to the device. Afterward, open the file with a file management app on the Android device.

Import Maps on Linux Desktop

If you are running Enroute Flight Navigation on a Linux Desktop machine, use the file manager to drag and drop the file into the app’s main window.

\ No newline at end of file diff --git a/docs/manual/02-advanced/customMaps.html b/docs/manual/02-advanced/customMaps.html index 2466203c..713bc2ed 100644 --- a/docs/manual/02-advanced/customMaps.html +++ b/docs/manual/02-advanced/customMaps.html @@ -1 +1 @@ - Use your own maps Skip to content

Use your own maps

Enroute Flight Navigation comes with a set of base maps that cover large parts of the world and are updated frequently. Still, there might be situations where a user would like to use their own base maps.

  • Where available, some users might prefer to use official ICAO charts of their countries.

  • Some users might prefer raster maps that follow a different style.

  • Some users might prefer to install high-detail vector maps for particular regions of interest.

Enroute Flight Navigation is able to import MBTILES file containing raster or vector data. Vector data must follow the standard OpenMapTiles schema. Vector maps are rendered in the same style that Enroute Flight Navigation uses for its own maps. It is possible to install vector maps along with the maps provided by Enroute Flight Navigation, in order to provide higher detail for particular regions of interest.

Import Maps

Import Maps on Android devices

If you are using an Android device, you need to transfer the MBTILES file to the device, and open it there. There are many ways to transfer files, but most users will likely do one of the following.

  • Download the MBTILES file on the Android device with a web browser. The browser will then offer to open the file in Enroute Flight Navigation.

  • Download the MBTILES file to a desktop computer, connect the device to the desktop computer via USB and then copy the file to the device. Afterwards, the file can be opened by a file management app on the Android device.

Import Maps on Linux Desktop

If you are running Enroute Flight Navigation on a Linux Desktop machine, use the file manager to drag-and-drop the file into the main window of the app.

Note

MBTILES files are often extremely large. It is possible that your device becomes unresponsive for a few seconds while copying the file. Also, note that Enroute Flight Navigation will copy the file to its internal data directory. In order to save space, we recommend deleting the MBTILES file once it has been imported.

MBTILES Map Data Sources

We are aware of a few websites that offer vector or raster maps that can be used with Enroute Flight Navigation. Please let us know if you know of other map data sources!

  • The website maptiler data provides excellent vector maps that can be installed alongside the base maps provided by Enroute Flight Navigation, in order to provide high-detail maps for specific regions of interest.

  • The website open flightmaps provides excellent aviation maps in raster format for a variety of European countries, as well as South Africa and Namibia.

Raster Maps in GeoTIFF format

We are aware of websites that offer raster maps in GeoTIFF format. At present, Enroute Flight Navigation cannot handle GeoTIFF files, but there are tools that convert GeoTIFF to MBTILES.

Users have successfully used the free tool QGIS to convert GeoTIFF files to MBTILES, which can then be used with Enroute Flight Navigation.

../_images/QGIS-MainWindow.png

QGIS Main Window

Since QGIS is a powerful tool that is not always easy to use, one user has kindly provided the following short tutorial.

  • Install QGIS on your desktop computer. On Fedora Linux, we found that the packages provided by the default software repository were outdated and lacked the necessary functionality. We followed the installations instructions on the QGIS website to install a current and full-featured version of the program.

  • Open QGIS. Create a new project and open the GeoTIFF file in QGIS by dragging-and-dropping the GeoTIFF file into the QGIS window. The content of the GeoTIFF file should become visible.

  • Choose the menu item “Project/Properties…” to open the dialog window “Project Properties”. There, set the coordinate reference system to EPSG:3857. To locate the reference system, use the text field “Filter” and search for EPSG:3857.

  • Use the menu items under “View/Panels/…” to ensure that the panels “Layer” and “Layer Styling” are visible. Select the layer of your GeoTIFF file and in the “Layer” panel. Then, go to the “Layer Styling” panel and set “Resampling” to “Bilinear” for better image render quality.

  • Use the menu items under “View/Panels/…” to ensure that the panel “Processing Toolbox” is visible. Inside the “Processing Toolbox”, double-click on “Raster Tools→Generate XYZ Tiles (MBTILES)”. The dialog “Generate XYZ Tiles (MBTILES)” will open. Fill the necessary parameters, as seen in the image below. We found the function “Draw on Map Canvas” useful to specify the map extent. Pay attention to the maximum zoom level, as the time and file size increase significantly after zoom level 12. Depending on the size of your GeoTIFF and on the number of zoom levels you use, it may take a while to generate the MBTILES file.

../_images/QGIS-GenerateMBTILES.png

QGIS Generate Tiles Dialog

\ No newline at end of file + Use your own maps Skip to content

Use your own maps

Enroute Flight Navigation comes with a set of base maps that cover large parts of the world and are updated frequently. Still, there might be situations where a user would like to use their own base maps.

  • Where available, some users might prefer to use official ICAO charts of their countries.

  • Some users might prefer raster maps that follow a different style.

  • Some users might prefer to install high-detail vector maps for particular regions of interest.

Enroute Flight Navigation is able to import MBTILES file containing raster or vector data. Vector data must follow the standard OpenMapTiles schema. Vector maps are rendered in the same style that Enroute Flight Navigation uses for its own maps. It is possible to install vector maps along with the maps provided by Enroute Flight Navigation, in order to provide higher detail for particular regions of interest.

Import Maps

Import Maps on Android devices

If you are using an Android device, you need to transfer the MBTILES file to the device, and open it there. There are many ways to transfer files, but most users will likely do one of the following.

  • Download the MBTILES file on the Android device with a web browser. The browser will then offer to open the file in Enroute Flight Navigation.

  • Download the MBTILES file to a desktop computer, connect the device to the desktop computer via USB and then copy the file to the device. Afterwards, the file can be opened by a file management app on the Android device.

Import Maps on Linux Desktop

If you are running Enroute Flight Navigation on a Linux Desktop machine, use the file manager to drag-and-drop the file into the main window of the app.

Note

MBTILES files are often extremely large. It is possible that your device becomes unresponsive for a few seconds while copying the file. Also, note that Enroute Flight Navigation will copy the file to its internal data directory. In order to save space, we recommend deleting the MBTILES file once it has been imported.

MBTILES Map Data Sources

We are aware of a few websites that offer vector or raster maps that can be used with Enroute Flight Navigation. Please let us know if you know of other map data sources!

  • The website maptiler data provides excellent vector maps that can be installed alongside the base maps provided by Enroute Flight Navigation, in order to provide high-detail maps for specific regions of interest.

  • The website open flightmaps provides excellent aviation maps in raster format for a variety of European countries, as well as South Africa and Namibia.

Raster Maps in GeoTIFF format

We are aware of websites that offer raster maps in GeoTIFF format. At present, Enroute Flight Navigation cannot handle GeoTIFF files, but there are tools that convert GeoTIFF to MBTILES.

Users have successfully used the free tool QGIS to convert GeoTIFF files to MBTILES, which can then be used with Enroute Flight Navigation.

../_images/QGIS-MainWindow.png

QGIS Main Window

Since QGIS is a powerful tool that is not always easy to use, one user has kindly provided the following short tutorial.

  • Install QGIS on your desktop computer. On Fedora Linux, we found that the packages provided by the default software repository were outdated and lacked the necessary functionality. We followed the installations instructions on the QGIS website to install a current and full-featured version of the program.

  • Open QGIS. Create a new project and open the GeoTIFF file in QGIS by dragging-and-dropping the GeoTIFF file into the QGIS window. The content of the GeoTIFF file should become visible.

  • Choose the menu item “Project/Properties…” to open the dialog window “Project Properties”. There, set the coordinate reference system to EPSG:3857. To locate the reference system, use the text field “Filter” and search for EPSG:3857.

  • Use the menu items under “View/Panels/…” to ensure that the panels “Layer” and “Layer Styling” are visible. Select the layer of your GeoTIFF file and in the “Layer” panel. Then, go to the “Layer Styling” panel and set “Resampling” to “Bilinear” for better image render quality.

  • Use the menu items under “View/Panels/…” to ensure that the panel “Processing Toolbox” is visible. Inside the “Processing Toolbox”, double-click on “Raster Tools→Generate XYZ Tiles (MBTILES)”. The dialog “Generate XYZ Tiles (MBTILES)” will open. Fill the necessary parameters, as seen in the image below. We found the function “Draw on Map Canvas” useful to specify the map extent. Pay attention to the maximum zoom level, as the time and file size increase significantly after zoom level 12. Depending on the size of your GeoTIFF and on the number of zoom levels you use, it may take a while to generate the MBTILES file.

../_images/QGIS-GenerateMBTILES.png

QGIS Generate Tiles Dialog

\ No newline at end of file diff --git a/docs/manual/02-steps/donate.html b/docs/manual/02-steps/donate.html index 5edf42c2..bbf059ac 100644 --- a/docs/manual/02-steps/donate.html +++ b/docs/manual/02-steps/donate.html @@ -1,5 +1,5 @@ - Make a donation Skip to content

Make a donation

Enroute Flight Navigation is a non-commercial project of Akaflieg Freiburg, supported by the University of Freiburg. Flight enthusiasts have written the app in their spare time as a service to the community. The developers do not take donations.

If you appreciate the app, please consider donating to Akaflieg Freiburg, a tax-privileged, not-for-profit flight club of public utility in Freiburg, Germany. The club will use your donation to promote aviation as a recreational sport; this includes funding the further development of Enroute Flight Navigation and its infrastructure. Donations to Akaflieg Freiburg are tax-deductible in Germany. Contact info@akaflieg-freiburg.de for a tax statement.

PayPal

Donate with PayPal: click here or scan the QR code below.

Donate with PayPal

Bank Address

IBAN:    DE35 6809 0000 0027 6409 07
+                         Make a donation                      Skip to content  
  
 
  
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
 
 
Make a donation
 
Enroute Flight Navigation is a non-commercial project of Akaflieg Freiburg, supported by the University of Freiburg. Flight enthusiasts have written the app in their spare time as a service to the community. The developers do not take donations.
 
If you appreciate the app, please consider donating to Akaflieg Freiburg, a tax-privileged, not-for-profit flight club of public utility in Freiburg, Germany. The club will use your donation to promote aviation as a recreational sport; this includes funding the further development of Enroute Flight Navigation and its infrastructure. Donations to Akaflieg Freiburg are tax-deductible in Germany. Contact info@akaflieg-freiburg.de for a tax statement.
 
 
PayPal
 
Donate with PayPal: click here or scan the QR code below.
 
 Donate with PayPal 
 
 
 
Bank Address
 
IBAN:    DE35 6809 0000 0027 6409 07
 BIC:     GENODE61FR1
 Bank:    Volksbank Freiburg
 Message: Enroute Flight Navigation
-
 
 
 
 
 
 
 
 
   
\ No newline at end of file
+
\ No newline at end of file diff --git a/docs/manual/02-steps/nearby.html b/docs/manual/02-steps/nearby.html index 305fa9e3..542f200a 100644 --- a/docs/manual/02-steps/nearby.html +++ b/docs/manual/02-steps/nearby.html @@ -1 +1 @@ - Find nearby waypoints Skip to content

Find nearby waypoints

If the weather turns bad, Enroute Flight Navigation can help you find the best place to land. Open the main menu and choose the item “Nearby waypoints”. You will be presented with a list of the closest aerodromes, together with distances and directions. Click on any item to open a dialog with detailed information, including lists of runways and communications frequencies. The dialog has a button “Direct” the replaces the current route with a route that brings you directly to the aerodrome.

Airfields close to Freiburg

List of airfields close to the current position

Apart from aerodromes, there are additional tabs that list nearby navaids and reporting points.

\ No newline at end of file + Find nearby waypoints Skip to content

Find nearby waypoints

If the weather turns bad, Enroute Flight Navigation can help you find the best place to land. Open the main menu and choose the item “Nearby waypoints”. You will be presented with a list of the closest aerodromes, together with distances and directions. Click on any item to open a dialog with detailed information, including lists of runways and communications frequencies. The dialog has a button “Direct” the replaces the current route with a route that brings you directly to the aerodrome.

Airfields close to Freiburg

List of airfields close to the current position

Apart from aerodromes, there are additional tabs that list nearby navaids and reporting points.

\ No newline at end of file diff --git a/docs/manual/02-steps/plan.html b/docs/manual/02-steps/plan.html index 745f0c76..18fa8b5c 100644 --- a/docs/manual/02-steps/plan.html +++ b/docs/manual/02-steps/plan.html @@ -1 +1 @@ - Plan a Flight Skip to content

Plan a Flight

What to expect

Enroute Flight Navigation offers essential flight planning functionality: you can display the route on the moving map and compute travel time and fuel consumption estimates. The following image shows the Flight Route Window in a typical situation.

Flight route window, route set

Flight route window, route set

As soon as you are flying and following the route, the moving map will show additional items that help you navigate.

  • The moving map shows the intended flight as a magenta line.

  • The map shows the path from the current position to the next waypoint as a thin red line.

  • An infobox shows distance, ETE, and ETA for the flight to the next and the final waypoint.

The following image shows a typical situation.

Flight route window, route set

Moving map when following a flight route

Note

Enroute Flight Navigation shows the info box only when airborne, closer than three nautical miles to the intended route and further than three nautical miles from your destination.

Set up a route

This chapter will take you through the necessary steps to set up a route.

Step 1: Set aircraft characteristics

To compute travel time, Enroute Flight Navigation needs to know the cruise speed of your aircraft. If you have followed this manual, you have entered this piece of data after you downloaded the aviation map. If not, then please check the section Set aircraft specifics again.

Step 2: Specify wind

Enroute Flight Navigation also needs to know about the wind. If you are not on the page “Route and Wind,” open the main menu and choose the item “Route and Wind.” Select the tab “Wind” and enter an estimate for wind direction and speed that you expect to encounter during your flight.

Step 3: Specify waypoints

Enroute Flight Navigation needs to know where you want to go. There are several ways to specify the waypoints in your route.

  • Enter waypoints by name

  • Select waypoints in the moving map

  • Import a route from the route library

  • Import a GPX file from another program

Most users will enter the waypoints manually. Still, we explain all four methods in some detail.

Option 1: Enter waypoints by name

If you are not on the “Route and Wind” page, open the main menu and choose the item “Route and Wind.” On the page, select the “Route” tab. The page will initially look like this:

Flight route window, no route set

Flight route window, no route set

A tap on the field “Add Waypoint” at the bottom of the page will open a dialog window showing a long list with all waypoints from all aviation maps you have installed. Enter a few letters of the waypoint name (“Freiburg”) or ICAO code (“EDTF”) to narrow the list down. Once the desired waypoint becomes visible, a click will add it to the route.

Enter waypoints by name

Enter waypoints by name

Click on the field “Add Waypoint” again to enter more waypoints.

Option 2: Select waypoints in the moving map

It is possible to add waypoints directly from the moving map. Double-tap or tap-and-hold on any point of the moving map. The waypoint description dialog will open.

  • Tap on the “Plus” sign to append the waypoint to the current route.

  • Tap on “Direct to” to discard the current route and to add the current position and the given waypoint to your path.

  • If the waypoint is already present in your route, you can tap on the “Minus” sign to remove it.

Option 3: Import a route from the library

Section Optional: Save route for future use will show how to save a route to the library for future use. If you have already saved a route to the library, go to the open the main menu and choose the item “Library/Routes.” The route library page will open. Choose a route by tapping on the respective item in the list.

Option 4: Import a GPX file from another program

To prepare your flight, you might want to use full-featured flight preparation software or online services, such as FL95. Most (if not all) programs allow exporting the route in GPX format. Transfer the GPX file to your device (using Bluetooth file transfer, Google Drive, sending yourself an e-mail, or any other communication channel).

  • On Android devices, it suffices to open the file. Depending on the transfer mode, you can open the file after the Bluetooth transfer, in the Google Drive App, or perhaps in the e-mail client. Enroute Flight Navigation will automatically open and import the route. If more than one program on your device can handle GPX files, the system will ask you which program to use.

  • On the Linux desktop, drag-and-drop the GPX file to the Enroute Flight Navigation window.

Step 4: Edit the route if necessary

It might be necessary to edit the route. If you are not on the “Route and Wind” page, open the main menu and choose the item “Route and Wind.” On the page, select the “Route” tab.

Global functions

The three-dot-menu in the upper right corner of the screen allows reversing the route or deleting it entirely.

Waypoint-specific functions

The three-dot-menu to the right of each waypoint allows one to delete a specific waypoint or move it up and down in the list. You can edit waypoints that do not refer to pre-set airfields, navaids, or reporting points. Tap on the pencil symbol to open a dialog that allows you to set a name and edit the coordinates.

Optional: Save route for future use

Once you are happy with the route, you might want to save it for future use. If you are not on the “Route and Wind” page, open the main menu and choose the item “Route and Wind.” On the page, select the “Route” tab. The three-dot-menu in the upper right corner of the screen allows saving the route to the library.

Optional: Export and share the route

Enroute Flight Navigation can write the route to a file, which can then be transferred to other devices, or opened with other apps. Enroute Flight Navigation is able to write files in GeoJSON and GPX format. While GPX is understood by most programs, GeoJSON is the preferred format for sharing data between several instances of Enroute Flight Navigation.

  • On Android devices, choose the item “Share…” from the three-dot menu at the top right of the screen, and choose the appropriate file type from the submenu.

  • On the Linux desktop, choose the item “Export…” from the three-dot menu at the top right of the screen, and choose the appropriate file type from the submenu.

Optional: Open the route in another app

It is possible to open the route in another app. Choose the item “Open in other app…” from the three-dot menu at the top right of the screen, and choose the appropriate file type from the submenu.

\ No newline at end of file + Plan a Flight Skip to content

Plan a Flight

What to expect

Enroute Flight Navigation offers essential flight planning functionality: you can display the route on the moving map and compute travel time and fuel consumption estimates. The following image shows the Flight Route Window in a typical situation.

Flight route window, route set

Flight route window, route set

As soon as you are flying and following the route, the moving map will show additional items that help you navigate.

  • The moving map shows the intended flight as a magenta line.

  • The map shows the path from the current position to the next waypoint as a thin red line.

  • An infobox shows distance, ETE, and ETA for the flight to the next and the final waypoint.

The following image shows a typical situation.

Flight route window, route set

Moving map when following a flight route

Note

Enroute Flight Navigation shows the info box only when airborne, closer than three nautical miles to the intended route and further than three nautical miles from your destination.

Set up a route

This chapter will take you through the necessary steps to set up a route.

Step 1: Set aircraft characteristics

To compute travel time, Enroute Flight Navigation needs to know the cruise speed of your aircraft. If you have followed this manual, you have entered this piece of data after you downloaded the aviation map. If not, then please check the section Set aircraft specifics again.

Step 2: Specify wind

Enroute Flight Navigation also needs to know about the wind. If you are not on the page “Route and Wind,” open the main menu and choose the item “Route and Wind.” Select the tab “Wind” and enter an estimate for wind direction and speed that you expect to encounter during your flight.

Step 3: Specify waypoints

Enroute Flight Navigation needs to know where you want to go. There are several ways to specify the waypoints in your route.

  • Enter waypoints by name

  • Select waypoints in the moving map

  • Import a route from the route library

  • Import a GPX file from another program

Most users will enter the waypoints manually. Still, we explain all four methods in some detail.

Option 1: Enter waypoints by name

If you are not on the “Route and Wind” page, open the main menu and choose the item “Route and Wind.” On the page, select the “Route” tab. The page will initially look like this:

Flight route window, no route set

Flight route window, no route set

A tap on the field “Add Waypoint” at the bottom of the page will open a dialog window showing a long list with all waypoints from all aviation maps you have installed. Enter a few letters of the waypoint name (“Freiburg”) or ICAO code (“EDTF”) to narrow the list down. Once the desired waypoint becomes visible, a click will add it to the route.

Enter waypoints by name

Enter waypoints by name

Click on the field “Add Waypoint” again to enter more waypoints.

Option 2: Select waypoints in the moving map

It is possible to add waypoints directly from the moving map. Double-tap or tap-and-hold on any point of the moving map. The waypoint description dialog will open.

  • Tap on the “Plus” sign to append the waypoint to the current route.

  • Tap on “Direct to” to discard the current route and to add the current position and the given waypoint to your path.

  • If the waypoint is already present in your route, you can tap on the “Minus” sign to remove it.

Option 3: Import a route from the library

Section Optional: Save route for future use will show how to save a route to the library for future use. If you have already saved a route to the library, go to the open the main menu and choose the item “Library/Routes.” The route library page will open. Choose a route by tapping on the respective item in the list.

Option 4: Import a GPX file from another program

To prepare your flight, you might want to use full-featured flight preparation software or online services, such as FL95. Most (if not all) programs allow exporting the route in GPX format. Transfer the GPX file to your device (using Bluetooth file transfer, Google Drive, sending yourself an e-mail, or any other communication channel).

  • On Android devices, it suffices to open the file. Depending on the transfer mode, you can open the file after the Bluetooth transfer, in the Google Drive App, or perhaps in the e-mail client. Enroute Flight Navigation will automatically open and import the route. If more than one program on your device can handle GPX files, the system will ask you which program to use.

  • On the Linux desktop, drag-and-drop the GPX file to the Enroute Flight Navigation window.

Step 4: Edit the route if necessary

It might be necessary to edit the route. If you are not on the “Route and Wind” page, open the main menu and choose the item “Route and Wind.” On the page, select the “Route” tab.

Global functions

The three-dot-menu in the upper right corner of the screen allows reversing the route or deleting it entirely.

Waypoint-specific functions

The three-dot-menu to the right of each waypoint allows one to delete a specific waypoint or move it up and down in the list. You can edit waypoints that do not refer to pre-set airfields, navaids, or reporting points. Tap on the pencil symbol to open a dialog that allows you to set a name and edit the coordinates.

Optional: Save route for future use

Once you are happy with the route, you might want to save it for future use. If you are not on the “Route and Wind” page, open the main menu and choose the item “Route and Wind.” On the page, select the “Route” tab. The three-dot-menu in the upper right corner of the screen allows saving the route to the library.

Optional: Export and share the route

Enroute Flight Navigation can write the route to a file, which can then be transferred to other devices, or opened with other apps. Enroute Flight Navigation is able to write files in GeoJSON and GPX format. While GPX is understood by most programs, GeoJSON is the preferred format for sharing data between several instances of Enroute Flight Navigation.

  • On Android devices, choose the item “Share…” from the three-dot menu at the top right of the screen, and choose the appropriate file type from the submenu.

  • On the Linux desktop, choose the item “Export…” from the three-dot menu at the top right of the screen, and choose the appropriate file type from the submenu.

Optional: Open the route in another app

It is possible to open the route in another app. Choose the item “Open in other app…” from the three-dot menu at the top right of the screen, and choose the appropriate file type from the submenu.

\ No newline at end of file diff --git a/docs/manual/02-steps/safesky.html b/docs/manual/02-steps/safesky.html index 83174c1d..778526d0 100644 --- a/docs/manual/02-steps/safesky.html +++ b/docs/manual/02-steps/safesky.html @@ -1 +1 @@ - Connect to the SafeSky app Skip to content

Connect to the SafeSky app

SafeSky is an anti-collision app and a real-time flight information service for all pilots flying any type of aircraft. The commercial premium version of SafeSky integrates with Enroute Flight Navigation. Once set up, the moving map of Enroute Flight Navigation will show nearby traffic, similar to the map display when connected to a traffic receiver.

SafeSky integration at work

SafeSky integration at work

Note

To show only relevant traffic, Enroute Flight Navigation will display traffic factors only if the vertical distance is less than 1,500 m and the horizontal distance less than 20 nm. The moving map of Enroute Flight Navigation will therefore show substantially less traffic than the SafeSky app.

Warning

Enroute Flight Navigation does not issue traffic warnings. The app contains no collision avoidance algorithms.

Connect!

The following steps configure SafeSky to forward traffic information to Enroute Flight Navigation. In Enroute Flight Navigation, no configuration is required.

SafeSky configuration screens

SafeSky configuration screens

Step 0: Before you connect

Traffic sharing is a premium feature of SafeSky. Before you connect, make sure to have a valid premium subscription.

Step 1: Enable traffic sharing

In the main menu of Safe Sky, choose the box “Traffic Sharing”. The page “Traffic Sharing” will open.

  • Choose the option “Enable traffic sharing”

  • Touch the field below “Enable traffic sharing” to open the list of supported navigation apps. Choose “Enroute” from the list and touch the button “back” to close the list.

  • Touch the button “back” to close page “Traffic sharing”. Leave the main menu and return to the SafeSky main page.

That’s it. As soon as you choose “TAKE OFF” in SafeSky to start a flight, SafeSky will start a background process that shares traffic data with Enroute Flight Navigation.

To check the SafeSky integration, choose “TAKE OFF” in SafeSky. Then, go to Enroute Flight Navigation, open the main menu in Enroute Flight Navigation and navigate to the “Information” menu.

  • If the entry “Traffic Receiver” is highlighted in green, then Enroute Flight Navigation has connected to the SafeSky app. Congratulations, you are done!

  • If the entry “Traffic Receiver” is not highlighted in green, then select the entry. The “Traffic Receiver Status” page will open. The page explains the connection status in detail, and explains how to establish a connection manually.

\ No newline at end of file + Connect to the SafeSky app Skip to content

Connect to the SafeSky app

SafeSky is an anti-collision app and a real-time flight information service for all pilots flying any type of aircraft. The commercial premium version of SafeSky integrates with Enroute Flight Navigation. Once set up, the moving map of Enroute Flight Navigation will show nearby traffic, similar to the map display when connected to a traffic receiver.

SafeSky integration at work

SafeSky integration at work

Note

To show only relevant traffic, Enroute Flight Navigation will display traffic factors only if the vertical distance is less than 1,500 m and the horizontal distance less than 20 nm. The moving map of Enroute Flight Navigation will therefore show substantially less traffic than the SafeSky app.

Warning

Enroute Flight Navigation does not issue traffic warnings. The app contains no collision avoidance algorithms.

Connect!

The following steps configure SafeSky to forward traffic information to Enroute Flight Navigation. In Enroute Flight Navigation, no configuration is required.

SafeSky configuration screens

SafeSky configuration screens

Step 0: Before you connect

Traffic sharing is a premium feature of SafeSky. Before you connect, make sure to have a valid premium subscription.

Step 1: Enable traffic sharing

In the main menu of Safe Sky, choose the box “Traffic Sharing”. The page “Traffic Sharing” will open.

  • Choose the option “Enable traffic sharing”

  • Touch the field below “Enable traffic sharing” to open the list of supported navigation apps. Choose “Enroute” from the list and touch the button “back” to close the list.

  • Touch the button “back” to close page “Traffic sharing”. Leave the main menu and return to the SafeSky main page.

That’s it. As soon as you choose “TAKE OFF” in SafeSky to start a flight, SafeSky will start a background process that shares traffic data with Enroute Flight Navigation.

To check the SafeSky integration, choose “TAKE OFF” in SafeSky. Then, go to Enroute Flight Navigation, open the main menu in Enroute Flight Navigation and navigate to the “Information” menu.

  • If the entry “Traffic Receiver” is highlighted in green, then Enroute Flight Navigation has connected to the SafeSky app. Congratulations, you are done!

  • If the entry “Traffic Receiver” is not highlighted in green, then select the entry. The “Traffic Receiver Status” page will open. The page explains the connection status in detail, and explains how to establish a connection manually.

\ No newline at end of file diff --git a/docs/manual/02-steps/simulator.html b/docs/manual/02-steps/simulator.html index 08112b98..927a884a 100644 --- a/docs/manual/02-steps/simulator.html +++ b/docs/manual/02-steps/simulator.html @@ -1,3 +1,3 @@ - Connect your flight simulator Skip to content

Connect your flight simulator

Enroute Flight Navigation can connect to flight simulator software. When setup correctly, position and traffic information is sent from the flight simulator via WiFi to the device that runs Enroute Flight Navigation.

The author has tested Enroute Flight Navigation with the following flight simulator programs.

Users have reported success with the following programs.

Please contact us if you are aware of other programs that also work.

Note

Enroute Flight Navigation treats flight simulators as traffic receivers. To see the connection status, open the main menu and navigate to the “Information” menu.

Before you connect

This manual assumes a typical home setup, where both the computer that runs the flight simulator and the device that runs Enroute Flight Navigation are connected to a Wi-Fi network deployed by a home router. Make sure that the following conditions are met.

  • Open the “Settings” page in the main menu and tap on the entry “Primary position data source” and select the “Traffic data receiver” as the main source. As long as the built-in satnav receiver is selected, all position information provided by your flight simulator is ignored.

  • The computer that runs the flight simulator and the device that runs Enroute Flight Navigation are connected to the same Wi-Fi network. Some routers deploy two networks, often called “main network” and a “guest network”.

  • Make sure that the router allows data transfer between the devices in the Wi-Fi network. Some routers have “security settings” that disallow data transfer between the devices in the “guest network”

Set up your flight simulator

Your flight simulation software needs to broadcast position and traffic information over the Wi-Fi network. Once this is done, there is no further setup required. As soon as the flight simulator starts to broadcast information over the Wi-Fi network, the moving map of Enroute Flight Navigation will adjust accordingly. To end the connection to the flight simulator, simply leave the flight simulator’s Wi-Fi network.

Aerofly FS

Aerofly works well with Enroute Flight Navigation if the program is set to broadcast flight information via the network. Open the menu “Miscellaneous settings”, activate the option “Broadcast flight info to IP address” and enter the correct „Broadcast IP address“. The figure Aerofly Miscellaneous settings and shows the settings that work for one of our users.

../_images/Aerofly-1.png

Aerofly settings

../_images/Aerofly-2.png

Aerofly Miscellaneous settings

FlightGear

FlightGear works well, even though position information is only broadcast when the simulated aircraft is moving. The following two parameters in the text field of the settings dialog need to be set:

--generic=socket,out,1,255.255.255.255,49002,udp,foreflight-xgps
+                         Connect your flight simulator                      Skip to content  
  
 
  
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
 
 
Connect your flight simulator
 
Enroute Flight Navigation can connect to flight simulator software. When setup correctly, position and traffic information is sent from the flight simulator via WiFi to the device that runs Enroute Flight Navigation.
 
The author has tested Enroute Flight Navigation with the following flight simulator programs.
  
Users have reported success with the following programs.
  
Please contact us if you are aware of other programs that also work.
 
 
Note
 
Enroute Flight Navigation treats flight simulators as traffic receivers. To see the connection status, open the main menu and navigate to the “Information” menu.
 
 
 
Before you connect
 
This manual assumes a typical home setup, where both the computer that runs the flight simulator and the device that runs Enroute Flight Navigation are connected to a Wi-Fi network deployed by a home router. Make sure that the following conditions are met.
 
     
  • Open the “Settings” page in the main menu and tap on the entry “Primary position data source” and select the “Traffic data receiver” as the main source. As long as the built-in satnav receiver is selected, all position information provided by your flight simulator is ignored.
     
  • The computer that runs the flight simulator and the device that runs Enroute Flight Navigation are connected to the same Wi-Fi network. Some routers deploy two networks, often called “main network” and a “guest network”.
     
  • Make sure that the router allows data transfer between the devices in the Wi-Fi network. Some routers have “security settings” that disallow data transfer between the devices in the “guest network”
     
 
 
 
Set up your flight simulator
 
Your flight simulation software needs to broadcast position and traffic information over the Wi-Fi network. Once this is done, there is no further setup required. As soon as the flight simulator starts to broadcast information over the Wi-Fi network, the moving map of Enroute Flight Navigation will adjust accordingly. To end the connection to the flight simulator, simply leave the flight simulator’s Wi-Fi network.
 
 
Aerofly FS
 
Aerofly works well with Enroute Flight Navigation if the program is set to broadcast flight information via the network. Open the menu “Miscellaneous settings”, activate the option “Broadcast flight info to IP address” and enter the correct „Broadcast IP address“. The figure Aerofly Miscellaneous settings and shows the settings that work for one of our users.
 
 ../_images/Aerofly-1.png 
 
Aerofly settings
 
 
 
 ../_images/Aerofly-2.png 
 
Aerofly Miscellaneous settings
 
 
 
 
 
FlightGear
 
FlightGear works well, even though position information is only broadcast when the simulated aircraft is moving. The following two parameters in the text field of the settings dialog need to be set:
 
--generic=socket,out,1,255.255.255.255,49002,udp,foreflight-xgps
 --httpd=8080
-
 
 
The figure FlightGear settings shows settings window.
 
 ../_images/FlightGear.png 
 
FlightGear settings
 
 
 
 
 
MS Flight Simulator
 
In order to communicate with other programs, the MS Flight Simulator requires additional software. Users reported that Enroute Flight Navigation works well with the following EFB-connector programs.
 
     
  • fs2ff (free, open source)
     
  • XMapsy Essential (commercial, inexpensive, does not provide barometric altitude data).
     
  • XMapsy V3 (commercial, more expensive, provides barometric altitude data).
     
 
The web site of the commerical EFB program ForeFlight lists additional EFB-connector programs that might also work.
 
 
Note
 
In MSFS2020 cold and dark mode, traffic in the air will not been shown. You have to power on the avionics!
 
 
 
Note
 
At the time of writing (04Aug21), the MS Flight Simulator reports only traffic that has a tail number. This is likely due to a bug in the MS Flight Simulator software.
 
 
 
fs2ff
The program fs2ff does not require any complicated installation or setup, just download and run. The latest release of fs2ff can be downloaded here. Detailed instruction are found here. The figure fs2ff settings shows extremely simple settings window.
 
 ../_images/fs2ff.png 
 
fs2ff settings
 
 
 
XMapsy Essential
If you use XMapsy Essential, you need not to setup anything. Just start Xmapsy Essential and start MSFS2020. The broadcast address will be setup automatically. The figure XMapsy Essential settings shows the settings.
 
 ../_images/XMapsyEssential.png 
 
XMapsy Essential settings
 
 
 
XMapsy V3
If you use XMapsy V3, set the “Message-Format” to “ADS-B/GDL90” and the “Preferred Technology” to SIMCONNECT. To receive the correct altitude, be sure to check the box “GDL90 ownship geometric altitudes based on MSL”. The figure XMapsy V3 settings shows verified XMapsy V3 settings for proper work with MSFS2020. The Broadcast address will be determined by Xmapsy and should not be touched except you have extended network configuration experience.
 
 ../_images/XMapsyV3.png 
 
XMapsy V3 settings
 
 
 
 
 
 
X-Plane 11
 
Open the “Settings” window and choose the “Network” tab. Locate the settings group “This machine’s role” on the right-hand side of the tab. Open the section “iPHONE, iPAD, and EXTERNAL APPS” and select the item “Broadcast to all mapping apps on the network” under the headline “OTHER MAPPING APPS”.
 ../_images/X-Plane-11.png 
 
 
Other programs
 
The flight simulator needs to be set up to send UDP datagrams in one of the standard formats “GDL90” or “XGPS” to ports 4000 or 49002. Given the choice, GDL90 is generally the preferred format.
 
 
 
 
Troubleshooting
 
Enroute Flight Navigation treats flight simulators as traffic receivers. To see the connection status, open the main menu and navigate to the “Information” menu. If the entry “Traffic Receiver” is highlighted in green, then Enroute Flight Navigation has already found the program in the network and has connected to it. If not, then select the entry. The “Traffic Receiver Status” page will open, which explains the connection status in more detail.
 
 
 
 
 
 
 
   
\ No newline at end of file
+

The figure FlightGear settings shows settings window.

../_images/FlightGear.png

FlightGear settings

MS Flight Simulator

In order to communicate with other programs, the MS Flight Simulator requires additional software. Users reported that Enroute Flight Navigation works well with the following EFB-connector programs.

  • fs2ff (free, open source)

  • XMapsy Essential (commercial, inexpensive, does not provide barometric altitude data).

  • XMapsy V3 (commercial, more expensive, provides barometric altitude data).

The web site of the commerical EFB program ForeFlight lists additional EFB-connector programs that might also work.

Note

In MSFS2020 cold and dark mode, traffic in the air will not been shown. You have to power on the avionics!

Note

At the time of writing (04Aug21), the MS Flight Simulator reports only traffic that has a tail number. This is likely due to a bug in the MS Flight Simulator software.

fs2ff

The program fs2ff does not require any complicated installation or setup, just download and run. The latest release of fs2ff can be downloaded here. Detailed instruction are found here. The figure fs2ff settings shows extremely simple settings window.

../_images/fs2ff.png

fs2ff settings

XMapsy Essential

If you use XMapsy Essential, you need not to setup anything. Just start Xmapsy Essential and start MSFS2020. The broadcast address will be setup automatically. The figure XMapsy Essential settings shows the settings.

../_images/XMapsyEssential.png

XMapsy Essential settings

XMapsy V3

If you use XMapsy V3, set the “Message-Format” to “ADS-B/GDL90” and the “Preferred Technology” to SIMCONNECT. To receive the correct altitude, be sure to check the box “GDL90 ownship geometric altitudes based on MSL”. The figure XMapsy V3 settings shows verified XMapsy V3 settings for proper work with MSFS2020. The Broadcast address will be determined by Xmapsy and should not be touched except you have extended network configuration experience.

../_images/XMapsyV3.png

XMapsy V3 settings

X-Plane 11

Open the “Settings” window and choose the “Network” tab. Locate the settings group “This machine’s role” on the right-hand side of the tab. Open the section “iPHONE, iPAD, and EXTERNAL APPS” and select the item “Broadcast to all mapping apps on the network” under the headline “OTHER MAPPING APPS”.

../_images/X-Plane-11.png

Other programs

The flight simulator needs to be set up to send UDP datagrams in one of the standard formats “GDL90” or “XGPS” to ports 4000 or 49002. Given the choice, GDL90 is generally the preferred format.

Troubleshooting

Enroute Flight Navigation treats flight simulators as traffic receivers. To see the connection status, open the main menu and navigate to the “Information” menu. If the entry “Traffic Receiver” is highlighted in green, then Enroute Flight Navigation has already found the program in the network and has connected to it. If not, then select the entry. The “Traffic Receiver Status” page will open, which explains the connection status in more detail.

\ No newline at end of file diff --git a/docs/manual/02-steps/traffic.html b/docs/manual/02-steps/traffic.html index 05a5978f..65755076 100644 --- a/docs/manual/02-steps/traffic.html +++ b/docs/manual/02-steps/traffic.html @@ -1 +1 @@ - Connect to your traffic receiver Skip to content

Connect to your traffic receiver

Midair collisions are a major reason for loss of lives in general aviation. Collisions often happen near airfields or in the traffic circuit. In order to enhance security, Enroute Flight Navigation can connect to your aircraft’s traffic receiver, typically a FLARM device. Once connected, the moving map will show nearby traffic.

Approaching EDTF with traffic

Approaching EDTF with traffic

The figure Approaching EDTF with traffic shows what to expect. The figure shows two traffic factors. The section Main Page and Moving Map covers the traffic display in detail.

  • There is one aircraft in the downwind section of the traffic circuit. The traffic has approximately the same altitude as the own aircraft and is sinking. The green color indicates “no alarm”.

  • There is one aircraft nearby whose precise position is unknown to the traffic receiver; this is often the case with traffic that has only a Mode-S transponder. The traffic is most likely found within the yellow circle. The yellow color indicates that the traffic might be close enough to be dangerous.

Note

To show only relevant traffic, Enroute Flight Navigation will display traffic factors only if the vertical distance is less than 1,500 m and the horizontal distance less than 20 nm.

Warning

Enroute Flight Navigation does not issue traffic warnings. The app contains no collision avoidance algorithms. Color coding of traffic according to relevance works best with FLARM devices.

Compatibility

Enroute Flight Navigation should work with all modern, standard-compliant traffic receivers. The author has tested the following receivers.

Users reported success with the following traffic receivers.

Note

Most traffic data receivers can only handle one concurrent connection. If more devices connect, this might lead to frequent loss of connection or loss of data. To be on the safe side, it might be useful to ask your passengers to disable Wi-Fi on their phone before boarding.

Note

For best results, use FLARM compatible devices. If your traffic receiver supports FLARM/NMEA as well as GDL90 output, always use FLARM/NMEA. The GDL90 protocol has a number of shortcomings that Enroute Flight Navigation cannot always work around. See the Section Known issues with GDL90 for more details.

Connect!

It takes three steps to connect Enroute Flight Navigation to the traffic receiver for the first time. Once things are set up properly, your device should automatically detect the traffic receiver’s Wi-Fi network, enter the network and connect to the traffic data stream whenever you go flying.

Step 0: Before you connect

Before you try to connect this app to your traffic receiver, make sure that the following conditions are met.

  • Your traffic receiver has an integrated Wi-Fi interface that acts as a wireless access point. Bluetooth is currently not supported.

  • You know the network name (=SSID) of the Wi-Fi network deployed by your traffic receiver. If the network is encrypted, you also need to know the Wi-Fi password.

  • Some devices require an additional password in order to access traffic data. If this is the case, you will need to know this password.

Step 1: Enter the traffic receiver’s Wi-Fi network

  • Make sure that the traffic receiver has power and is switched on. In a typical aircraft installation, the traffic receiver is connected to the ‘Avionics’ switch and will automatically switch on. You may need to wait a minute before the Wi-Fi comes online and is visible to your device.

  • Enter the Wi-Fi network deployed by your traffic receiver. This is usually done in the “Wi-Fi Settings” of your device. Enter the Wi-Fi password if required. Some devices will issue a warning that the Wi-Fi is not connected to the internet. In this case, you might need to confirm that you wish to enter the Wi-Fi network.

Most operating systems will offer to remember the connection, so that your device will automatically connect to this Wi-Fi in the future. We recommend using this option.

Step 2: Connect to the traffic data stream

Open the main menu and navigate to the “Information” menu.

  • If the entry “Traffic Receiver” is highlighted in green, then Enroute Flight Navigation has already found the traffic receiver in the network and has connected to it. Congratulations, you are done!

  • If the entry “Traffic Receiver” is not highlighted in green, then select the entry. The “Traffic Receiver Status” page will open. The page explains the connection status in detail, and explains how to establish a connection manually.

Troubleshooting

The app cannot connect to the traffic data stream.

  • Check that your device is connected to the Wi-Fi network deployed by your traffic receiver.

The connection breaks down after a few seconds.

Most traffic receivers cannot serve more than one client and abort connections at random if more than one device tries to access.

  • Make sure that there no second device connected to the traffic receiver’s Wi-Fi network. The other device might well be in your friend’s pocket!

  • Make sure that there is no other app trying to connect to the traffic receiver’s data stream.

  • Many traffic receivers offer “configuration panels” that can be accessed via a web browser. Close all web browsers.

Flarmnet data

Enroute Flight Navigation is able to use the database from Flarmnet.org to identify aircraft and to show the aircraft registration in the moving map display. The process does not require user interaction: once the app connects to a FLARM device and receives traffic information, the Flarmnet database will automatically be downloaded and updated with every map update. If desired, the database can also be downloaded manually on the page “Maps and Data” (open the main menu and go to “Library/Maps and Data”).

\ No newline at end of file + Connect to your traffic receiver Skip to content

Connect to your traffic receiver

Midair collisions are a major reason for loss of lives in general aviation. Collisions often happen near airfields or in the traffic circuit. In order to enhance security, Enroute Flight Navigation can connect to your aircraft’s traffic receiver, typically a FLARM device. Once connected, the moving map will show nearby traffic.

Approaching EDTF with traffic

Approaching EDTF with traffic

The figure Approaching EDTF with traffic shows what to expect. The figure shows two traffic factors. The section Main Page and Moving Map covers the traffic display in detail.

  • There is one aircraft in the downwind section of the traffic circuit. The traffic has approximately the same altitude as the own aircraft and is sinking. The green color indicates “no alarm”.

  • There is one aircraft nearby whose precise position is unknown to the traffic receiver; this is often the case with traffic that has only a Mode-S transponder. The traffic is most likely found within the yellow circle. The yellow color indicates that the traffic might be close enough to be dangerous.

Note

To show only relevant traffic, Enroute Flight Navigation will display traffic factors only if the vertical distance is less than 1,500 m and the horizontal distance less than 20 nm.

Warning

Enroute Flight Navigation does not issue traffic warnings. The app contains no collision avoidance algorithms. Color coding of traffic according to relevance works best with FLARM devices.

Compatibility

Enroute Flight Navigation should work with all modern, standard-compliant traffic receivers. The author has tested the following receivers.

Users reported success with the following traffic receivers.

Note

Most traffic data receivers can only handle one concurrent connection. If more devices connect, this might lead to frequent loss of connection or loss of data. To be on the safe side, it might be useful to ask your passengers to disable Wi-Fi on their phone before boarding.

Note

For best results, use FLARM compatible devices. If your traffic receiver supports FLARM/NMEA as well as GDL90 output, always use FLARM/NMEA. The GDL90 protocol has a number of shortcomings that Enroute Flight Navigation cannot always work around. See the Section Known issues with GDL90 for more details.

Connect!

It takes three steps to connect Enroute Flight Navigation to the traffic receiver for the first time. Once things are set up properly, your device should automatically detect the traffic receiver’s Wi-Fi network, enter the network and connect to the traffic data stream whenever you go flying.

Step 0: Before you connect

Before you try to connect this app to your traffic receiver, make sure that the following conditions are met.

  • Your traffic receiver has an integrated Wi-Fi interface that acts as a wireless access point. Bluetooth is currently not supported.

  • You know the network name (=SSID) of the Wi-Fi network deployed by your traffic receiver. If the network is encrypted, you also need to know the Wi-Fi password.

  • Some devices require an additional password in order to access traffic data. If this is the case, you will need to know this password.

Step 1: Enter the traffic receiver’s Wi-Fi network

  • Make sure that the traffic receiver has power and is switched on. In a typical aircraft installation, the traffic receiver is connected to the ‘Avionics’ switch and will automatically switch on. You may need to wait a minute before the Wi-Fi comes online and is visible to your device.

  • Enter the Wi-Fi network deployed by your traffic receiver. This is usually done in the “Wi-Fi Settings” of your device. Enter the Wi-Fi password if required. Some devices will issue a warning that the Wi-Fi is not connected to the internet. In this case, you might need to confirm that you wish to enter the Wi-Fi network.

Most operating systems will offer to remember the connection, so that your device will automatically connect to this Wi-Fi in the future. We recommend using this option.

Step 2: Connect to the traffic data stream

Open the main menu and navigate to the “Information” menu.

  • If the entry “Traffic Receiver” is highlighted in green, then Enroute Flight Navigation has already found the traffic receiver in the network and has connected to it. Congratulations, you are done!

  • If the entry “Traffic Receiver” is not highlighted in green, then select the entry. The “Traffic Receiver Status” page will open. The page explains the connection status in detail, and explains how to establish a connection manually.

Troubleshooting

The app cannot connect to the traffic data stream.

  • Check that your device is connected to the Wi-Fi network deployed by your traffic receiver.

The connection breaks down after a few seconds.

Most traffic receivers cannot serve more than one client and abort connections at random if more than one device tries to access.

  • Make sure that there no second device connected to the traffic receiver’s Wi-Fi network. The other device might well be in your friend’s pocket!

  • Make sure that there is no other app trying to connect to the traffic receiver’s data stream.

  • Many traffic receivers offer “configuration panels” that can be accessed via a web browser. Close all web browsers.

Flarmnet data

Enroute Flight Navigation is able to use the database from Flarmnet.org to identify aircraft and to show the aircraft registration in the moving map display. The process does not require user interaction: once the app connects to a FLARM device and receives traffic information, the Flarmnet database will automatically be downloaded and updated with every map update. If desired, the database can also be downloaded manually on the page “Maps and Data” (open the main menu and go to “Library/Maps and Data”).

\ No newline at end of file diff --git a/docs/manual/02-steps/waypointLibrary.html b/docs/manual/02-steps/waypointLibrary.html index ee1419dd..282bd82a 100644 --- a/docs/manual/02-steps/waypointLibrary.html +++ b/docs/manual/02-steps/waypointLibrary.html @@ -1 +1 @@ - Manage a waypoint library Skip to content

Manage a waypoint library

What to expect

Enroute Flight Navigation allows you to build a small library of waypoints that can be used in flight routes and shared with others. For the typical user, the library might contain a list of touristic landmarks (“Hohenzollern Castle”), or perhaps a list of emergency landing fields. The waypoints from the library are shown in the moving map.

Note

The waypoint library has been designed with small libraries in mind. If you import files containing thousands of waypoints, you might find that the moving map of Enroute Flight Navigation slows down considerably.

Add waypoints to the library

To add a waypoint to the library, tap-and-hold onto the moving map, so that the waypoint description dialog opens. In that dialog, click on “Library/Add…” Before saving, it is possible to assign a name and to edit the coordinates of the waypoint.

Note

To avoid data duplication, it is not possible to add airfields, navaids or reporting points to the waypoint library. If you tap-and-hold onto an airfield, you will find that the Item “Library” is disabled in the waypoint description dialog.

View the waypoint library

To open the waypoint library, go to the main menu and choose the item “Library/Waypoints.”

Import waypoints

Enroute Flight Navigation is able to import waypoints from files in CUP, GeoJSON or GPX format.

  • On Android devices, transfer the file to your device and open it there. Depending on the transfer mode, you can open the file after the Bluetooth transfer, in the Google Drive App, or perhaps in the e-mail client.

  • On the Linux desktop, drag-and-drop the file to the Enroute Flight Navigation window. Alternatively, open the waypoint library by choosing “Library/Waypoints” from the main menu, and choose the item “Import” from the three-dot menu at the top right of the screen.

Export and share the waypoint library

Enroute Flight Navigation is can write the waypoint library to a file, which can then be transferred to other devices, or opened with other apps. Enroute Flight Navigation is able to write files in GeoJSON and GPX format. While GPX is understood by most programs, GeoJSON is the preferred format for sharing data between several instances of Enroute Flight Navigation.

To start, open the waypoint library by choosing “Library/Waypoints” from the main menu.

  • On Android devices, choose the item “Share…” from the three-dot menu at the top right of the screen, and choose the appropriate file type from the submenu.

  • On the Linux desktop, choose the item “Export…” from the three-dot menu at the top right of the screen, and choose the appropriate file type from the submenu.

Open the waypoint library in another app

It is possible to open the waypoint library in another app. To start, open the waypoint library by choosing “Library/Waypoints” from the main menu. Once the main library page is open, choose the item “Open in other app…” from the three-dot menu at the top right of the screen, and choose the appropriate file type from the submenu.

\ No newline at end of file + Manage a waypoint library Skip to content

Manage a waypoint library

What to expect

Enroute Flight Navigation allows you to build a small library of waypoints that can be used in flight routes and shared with others. For the typical user, the library might contain a list of touristic landmarks (“Hohenzollern Castle”), or perhaps a list of emergency landing fields. The waypoints from the library are shown in the moving map.

Note

The waypoint library has been designed with small libraries in mind. If you import files containing thousands of waypoints, you might find that the moving map of Enroute Flight Navigation slows down considerably.

Add waypoints to the library

To add a waypoint to the library, tap-and-hold onto the moving map, so that the waypoint description dialog opens. In that dialog, click on “Library/Add…” Before saving, it is possible to assign a name and to edit the coordinates of the waypoint.

Note

To avoid data duplication, it is not possible to add airfields, navaids or reporting points to the waypoint library. If you tap-and-hold onto an airfield, you will find that the Item “Library” is disabled in the waypoint description dialog.

View the waypoint library

To open the waypoint library, go to the main menu and choose the item “Library/Waypoints.”

Import waypoints

Enroute Flight Navigation is able to import waypoints from files in CUP, GeoJSON or GPX format.

  • On Android devices, transfer the file to your device and open it there. Depending on the transfer mode, you can open the file after the Bluetooth transfer, in the Google Drive App, or perhaps in the e-mail client.

  • On the Linux desktop, drag-and-drop the file to the Enroute Flight Navigation window. Alternatively, open the waypoint library by choosing “Library/Waypoints” from the main menu, and choose the item “Import” from the three-dot menu at the top right of the screen.

Export and share the waypoint library

Enroute Flight Navigation is can write the waypoint library to a file, which can then be transferred to other devices, or opened with other apps. Enroute Flight Navigation is able to write files in GeoJSON and GPX format. While GPX is understood by most programs, GeoJSON is the preferred format for sharing data between several instances of Enroute Flight Navigation.

To start, open the waypoint library by choosing “Library/Waypoints” from the main menu.

  • On Android devices, choose the item “Share…” from the three-dot menu at the top right of the screen, and choose the appropriate file type from the submenu.

  • On the Linux desktop, choose the item “Export…” from the three-dot menu at the top right of the screen, and choose the appropriate file type from the submenu.

Open the waypoint library in another app

It is possible to open the waypoint library in another app. To start, open the waypoint library by choosing “Library/Waypoints” from the main menu. Once the main library page is open, choose the item “Open in other app…” from the three-dot menu at the top right of the screen, and choose the appropriate file type from the submenu.

\ No newline at end of file diff --git a/docs/manual/02-steps/weather.html b/docs/manual/02-steps/weather.html index 2bea2c72..c6ab0bf8 100644 --- a/docs/manual/02-steps/weather.html +++ b/docs/manual/02-steps/weather.html @@ -1 +1 @@ - Check Weather Skip to content

Check Weather

Enroute Flight Navigation can show METAR reports and TAF forecasts from nearby airfields along your route. The data is updated frequently, provided that an internet connection is available. To check weather, open the main menu and choose the item “Weather”. The weather information comes from the “Aviation Weather Center”, a website of the US government. When you open the page for the first time, Enroute Flight Navigation asks for your permission to access that site.

Warning

The weather information shown by Enroute Flight Navigation might be outdated or otherwise wrong. Assessment of meteorological flight conditions has to be done via an officially approved source of flight weather.

As soon as weather information has been downloaded, the page will look like this.

Weather at airfields close to Freiburg

Weather information

The page body displays a list of stations that are within 85nm around your current position or your intended flight route. As you can see in the picture, the following information is shown.

  • ICAO identifier for Station and Airport name

  • Distance and QUJ

  • METAR summary

The entries are classified and colored according to the “aviation flight categories” typically used in the United States. The coding scheme is explained in the table below. Note that this color coding might be different from the scheme typically used in your country. Green color does certainly not imply that it is advisable (or legal) to fly.

Category

Color

Ceiling

Visibility

low IFR

Red

<500 feet AGL

or

<1 mile

IFR

Red

500 – 1,000 feet AGL

or

1 – 3 miles

marginal VFR

Yellow

1,000 – 3,000 feet AGL

or

3 – 5 miles

VFR

Green

>3,000 feet AGL

and

> 5 miles

no data

White

–

–

–

Touch any item in the list to open dialog window with more details. The dialog window will look like this.

Weather at airfields close to Freiburg

Detailed Weather Dialog

As you can see in the picture, the weather dialog shows the following information.

  1. Station data including bearing and distance

  2. METAR text (if available)

  3. Decoded and translated METAR text

  4. TAF text (if available)

  5. Decoded and translated TAF text

Depending on screen size, you might have to scroll down in order to read the full weather forecast.

Page footer

The footer of the page shows the following data.

  • QNH of the closest airfield, as well as location and time of the report

  • Time of next sunset or sunrise at current location

  • Remaining time until sunset

Three-dot menu

The three-dot menu at the top right of the page allows to do the following.

  • Check for updates of METAR and TAF data

  • Disallow the internet connection to the “Aviation Weather Center” in case of privacy concerns

\ No newline at end of file + Check Weather Skip to content

Check Weather

Enroute Flight Navigation can show METAR reports and TAF forecasts from nearby airfields along your route. The data is updated frequently, provided that an internet connection is available. To check weather, open the main menu and choose the item “Weather”. The weather information comes from the “Aviation Weather Center”, a website of the US government. When you open the page for the first time, Enroute Flight Navigation asks for your permission to access that site.

Warning

The weather information shown by Enroute Flight Navigation might be outdated or otherwise wrong. Assessment of meteorological flight conditions has to be done via an officially approved source of flight weather.

As soon as weather information has been downloaded, the page will look like this.

Weather at airfields close to Freiburg

Weather information

The page body displays a list of stations that are within 85nm around your current position or your intended flight route. As you can see in the picture, the following information is shown.

  • ICAO identifier for Station and Airport name

  • Distance and QUJ

  • METAR summary

The entries are classified and colored according to the “aviation flight categories” typically used in the United States. The coding scheme is explained in the table below. Note that this color coding might be different from the scheme typically used in your country. Green color does certainly not imply that it is advisable (or legal) to fly.

Category

Color

Ceiling

Visibility

low IFR

Red

<500 feet AGL

or

<1 mile

IFR

Red

500 – 1,000 feet AGL

or

1 – 3 miles

marginal VFR

Yellow

1,000 – 3,000 feet AGL

or

3 – 5 miles

VFR

Green

>3,000 feet AGL

and

> 5 miles

no data

White

–

–

–

Touch any item in the list to open dialog window with more details. The dialog window will look like this.

Weather at airfields close to Freiburg

Detailed Weather Dialog

As you can see in the picture, the weather dialog shows the following information.

  1. Station data including bearing and distance

  2. METAR text (if available)

  3. Decoded and translated METAR text

  4. TAF text (if available)

  5. Decoded and translated TAF text

Depending on screen size, you might have to scroll down in order to read the full weather forecast.

Page footer

The footer of the page shows the following data.

  • QNH of the closest airfield, as well as location and time of the report

  • Time of next sunset or sunrise at current location

  • Remaining time until sunset

Three-dot menu

The three-dot menu at the top right of the page allows to do the following.

  • Check for updates of METAR and TAF data

  • Disallow the internet connection to the “Aviation Weather Center” in case of privacy concerns

\ No newline at end of file diff --git a/docs/manual/03-reference/Airspace.html b/docs/manual/03-reference/Airspace.html index 43bf6715..34a49822 100644 --- a/docs/manual/03-reference/Airspace.html +++ b/docs/manual/03-reference/Airspace.html @@ -1 +1 @@ - Airspace Display Skip to content

Airspace Display

The display of airspace will generally follow the common ICAO symbology.

Note

The Airspace structure at an arbitrary point may be seen by double touching the point on the screen. This will select the point as a waypoint. The waypoint pop-up window shows the information on the waypoint including airspace structure. This technique is also helpful to view the data and vertical limits of special use airspace.

Restricted Airspace

Restricted airspace are surrounded by an intense red dashed line and a thick transparent red line inside the restricted area boundaries. When selecting a point inside the restricted area by double touching the screen the information to the related area is given with the waypoint pop-up window:

  • Area Name

  • Area altitude limits

  • Area activation time

Controlled Airspace

All boundaries of controlled airspace are indicated by a solid blue line and a thick transparent blue line inside the airspace. When selecting a point inside the controlled airspace by double touching the screen the information to the related area is given with the waypoint pop-up window:

  • Airspace designation

  • Vertical Limits

  • Other airspace at location

Note

Communication frequencies are shown in the pop-up window related to the station or aerodrome.

All controlled airspace (Class A – Class D) are shown in the same way even if different restrictions or ATC clearance requirements may be present.

Control Zone

The Control Zone of an airport is indicated by a dashed blue line filled in transparent red color. When selecting a point inside the Control Zone (CTR) by double touching the screen the CTR designation and vertical limit is given within the waypoint pop-up window.

Note

Communication frequencies are shown in the pop-up window related to the station or aerodrome.

Transponder Mandatory Zones

Transponder Mandatory Zones TMZ are indicated by a black dashed outline. When selecting a point inside the Transponder Mandatory Zone (TMZ) by double touching the screen the information to the related ares is given with the waypoint pop-up window:

  • Area Name

  • Area altitude limits

  • Monitoring Frequency

  • Mode 3 Squawk

Radio Mandatory Zone

Radio Mandatory Zones (RMZ) are indicated by a solid blue dashed outline and filled in transparent blue. When selecting a point inside the Radio Mandatory Zone (RMZ) by double touching the screen the information to the related area is given with the waypoint pop-up window:

  • Area Name

  • Area altitude limits

  • Radio Frequency

Parachute Jumping Areas

Parachute Jumping Exercise areas (PJE) are indicated with a solid red dashed outline. When selecting a point inside the PJE by double touching the screen the information to the related area is given with the waypoint pop-up window:

  • Area Name

  • Area altitude limits

  • Radio Frequency

Nature Reserve Areas

Nature Reserve Areas (NRA) are indicated with a solid green outline. When selecting a point inside the NRA by double touching the screen the information to the related area is given with the waypoint pop-up window:

  • Area Name

  • Area altitude limits

Caution

Check restrictions applicable for flying inside NRA when planning your flight. For example in Austria high fines are applicable when flying inside NRA.

Airfields

The symbology used to display airfields follows the ICAO rules. When selecting an airfield by double touching the screen the related Airfield Information is given in a pop-up window:

  • Airfield Name and Identifier

  • Radio Frequency including COM and Information frequencies

  • Navaid frequencies

  • Runway orientation, dimensions and surface

  • Field elevation

  • Data for associated airspace

  • Approach and Departure Routes

Approach routes to airfields are shown as solid blue lines. The designation of the route is written along the paths. The associated reporting points are shown as blue triangles with a dashed circle and the reporting point designation. Approach Routes will be shown by a solid line and Departure Routes will be shown as dashed lines.

Note

Approach Routes will only be displayed when zooming into the area.

Traffic Pattern

Traffic pattern for motorized aircraft are shown as blue lines. Traffic circuits for gliders or Ultralight aircraft are shown as red lines. Entry and exit routes to traffic pattern are indicated by open ends of the pattern. The traffic circuit will show the traffic circuit altitude when the information is available.

Note

Traffic pattern will only be displayed when zooming into the area.

\ No newline at end of file + Airspace Display Skip to content

Airspace Display

The display of airspace will generally follow the common ICAO symbology.

Note

The Airspace structure at an arbitrary point may be seen by double touching the point on the screen. This will select the point as a waypoint. The waypoint pop-up window shows the information on the waypoint including airspace structure. This technique is also helpful to view the data and vertical limits of special use airspace.

Restricted Airspace

Restricted airspace are surrounded by an intense red dashed line and a thick transparent red line inside the restricted area boundaries. When selecting a point inside the restricted area by double touching the screen the information to the related area is given with the waypoint pop-up window:

  • Area Name

  • Area altitude limits

  • Area activation time

Controlled Airspace

All boundaries of controlled airspace are indicated by a solid blue line and a thick transparent blue line inside the airspace. When selecting a point inside the controlled airspace by double touching the screen the information to the related area is given with the waypoint pop-up window:

  • Airspace designation

  • Vertical Limits

  • Other airspace at location

Note

Communication frequencies are shown in the pop-up window related to the station or aerodrome.

All controlled airspace (Class A – Class D) are shown in the same way even if different restrictions or ATC clearance requirements may be present.

Control Zone

The Control Zone of an airport is indicated by a dashed blue line filled in transparent red color. When selecting a point inside the Control Zone (CTR) by double touching the screen the CTR designation and vertical limit is given within the waypoint pop-up window.

Note

Communication frequencies are shown in the pop-up window related to the station or aerodrome.

Transponder Mandatory Zones

Transponder Mandatory Zones TMZ are indicated by a black dashed outline. When selecting a point inside the Transponder Mandatory Zone (TMZ) by double touching the screen the information to the related ares is given with the waypoint pop-up window:

  • Area Name

  • Area altitude limits

  • Monitoring Frequency

  • Mode 3 Squawk

Radio Mandatory Zone

Radio Mandatory Zones (RMZ) are indicated by a solid blue dashed outline and filled in transparent blue. When selecting a point inside the Radio Mandatory Zone (RMZ) by double touching the screen the information to the related area is given with the waypoint pop-up window:

  • Area Name

  • Area altitude limits

  • Radio Frequency

Parachute Jumping Areas

Parachute Jumping Exercise areas (PJE) are indicated with a solid red dashed outline. When selecting a point inside the PJE by double touching the screen the information to the related area is given with the waypoint pop-up window:

  • Area Name

  • Area altitude limits

  • Radio Frequency

Nature Reserve Areas

Nature Reserve Areas (NRA) are indicated with a solid green outline. When selecting a point inside the NRA by double touching the screen the information to the related area is given with the waypoint pop-up window:

  • Area Name

  • Area altitude limits

Caution

Check restrictions applicable for flying inside NRA when planning your flight. For example in Austria high fines are applicable when flying inside NRA.

Airfields

The symbology used to display airfields follows the ICAO rules. When selecting an airfield by double touching the screen the related Airfield Information is given in a pop-up window:

  • Airfield Name and Identifier

  • Radio Frequency including COM and Information frequencies

  • Navaid frequencies

  • Runway orientation, dimensions and surface

  • Field elevation

  • Data for associated airspace

  • Approach and Departure Routes

Approach routes to airfields are shown as solid blue lines. The designation of the route is written along the paths. The associated reporting points are shown as blue triangles with a dashed circle and the reporting point designation. Approach Routes will be shown by a solid line and Departure Routes will be shown as dashed lines.

Note

Approach Routes will only be displayed when zooming into the area.

Traffic Pattern

Traffic pattern for motorized aircraft are shown as blue lines. Traffic circuits for gliders or Ultralight aircraft are shown as red lines. Entry and exit routes to traffic pattern are indicated by open ends of the pattern. The traffic circuit will show the traffic circuit altitude when the information is available.

Note

Traffic pattern will only be displayed when zooming into the area.

\ No newline at end of file diff --git a/docs/manual/03-reference/about.html b/docs/manual/03-reference/about.html index 9d8a3b1a..d3cfd5a8 100644 --- a/docs/manual/03-reference/about.html +++ b/docs/manual/03-reference/about.html @@ -1 +1 @@ - About Enroute Flight Navigation Skip to content

About Enroute Flight Navigation

The page About Enroute Flight Navigation shows basic information about the app and the system. To access the page, open the main menu and choose “Information/About Enroute Flight Navigation.”

The page presents four tabs with information about the app, its authors, the software license, and the current system.

System information can be helpful to the developers Enroute Flight Navigation. The button “Share Info” at the bottom of the “System” Tab can be used to share the information with other apps, such as your e-mail program, and forward it to the developers.

\ No newline at end of file + About Enroute Flight Navigation Skip to content

About Enroute Flight Navigation

The page About Enroute Flight Navigation shows basic information about the app and the system. To access the page, open the main menu and choose “Information/About Enroute Flight Navigation.”

The page presents four tabs with information about the app, its authors, the software license, and the current system.

System information can be helpful to the developers Enroute Flight Navigation. The button “Share Info” at the bottom of the “System” Tab can be used to share the information with other apps, such as your e-mail program, and forward it to the developers.

\ No newline at end of file diff --git a/docs/manual/03-reference/mainPage.html b/docs/manual/03-reference/mainPage.html index 13af48d2..314c3fb5 100644 --- a/docs/manual/03-reference/mainPage.html +++ b/docs/manual/03-reference/mainPage.html @@ -1 +1 @@ - Main Page and Moving Map Skip to content

Main Page and Moving Map

The main page is the page that you will use the most often. This is also the page that opens when you start the app. The following image shows the Main Page in a typical flight situation.

Flight route window, route set

The Main Page of Enroute Flight Navigation

  • At the top of the screen, you see the Route Information Bar with information about the remaining flight route.

  • The page body shows a moving map with your current position and a number of interactive controls.

  • At the bottom, the Navigation Bar displays information about the current flight situation.

This manual uses the words “Bearing Mode” and “Autopan Mode” to describe two settings that govern the behavior of the map display.

Bearing Mode

The moving map can operate in two “bearing modes”. In the mode “north up”, the map is rotated so that the north direction is up, as you would expect from a paper map. In the mode “track up”, the map is rotated according to your direction of movement, so that your flight direction is up.

Autopan Mode

If the autopan mode is on, the map is automatically moved, so that the position you aircraft is near the center of the map display. If the autopan mode is off, the map is not moved and the position of your aircraft might not be visible on the map.

Route Information Bar

If you have defined a flight route following the steps outlined in the section Plan a Flight, then the top of the Main Page will show a tabular panel with one or two lines of information about the remaining route that you still have to fly. The first line of the table refers to the next waypoint, the second line to the final waypoint in your route.

Code

Meaning

—

Name of the waypoint.

TC

True course to the waypoint (only shown for course to next waypoint).

DIST

Distance to the waypoint.

ETE

Estimated Time Enroute to the waypoint.

ETA

Estimated Arrival Time at the waypoint, in UTC.

  • The units for the distance are chosen according to the settings on the Aircraft Page.

  • If the information cannot be computed (e.g. because the positions is unknown, or because you are flying too far away from the route), the panel shows a brief error message.

  • Close to the final destination, the panel shows the words “Near destination.”

Interactive Controls

The page body shows the following interactive control buttons that can be used together with the standard gestures to operate the app.

Symbol

Function

../_images/ic_menu.png

Opens main menu.

../_images/NorthArrow.png

Switches between modes north up and track up.

../_images/ic_my_location.png

Sets autopan mode to “on”.

../_images/ic_add.png

Zoom in.

../_images/ic_remove.png

Zoom out.

../_images/ic_airplanemode_active.png

This control is shown when the app is not connected to a traffic data receiver. A click opens the traffic receiver status page.

Moving Map

The moving map shows a physical map with shaded terrain relief, overlaid with aviation data. At low zoom values, the map looks similar to the standard 1:50.000 ICAO maps. At higher zoom value, the map will also show traffic circuits and control zone procedures, as you would expect from an approach chart.

Note

Traffic circuits and control zone procedures are available for select countries only. See the section Aeronautical maps for more details.

The moving map shows the following additional items

  • If you have set an Airspace Altitude Limit on the Settings Page, the map will show a little reminder at the top of the screen, with a text such as “Airspaces up to 9500 ft”.

  • To give you a rough estimate for the horizontal distances, the map features a scale. Depending on screen orientation, the scale is shown at the bottom or at the left of the screen.

  • At the very bottom of the screen, there is a copyright notice. Click on the notice to open a dialogue window with more detailed information.

Gesture Controls

The moving map can be controlled by standard gestures.

  • Mouse Wheel: On desktop computers, the mouse wheel zooms in and out.

  • Pinch Gesture: On touch-screen devices, the pinch gesture zooms in and out.

  • Pan Gesture: On touch-screen devices, the pinch the pan gesture moves the map and sets the autopan mode to “off”.

  • Tap-and-hold Gesture: Tap-and-hold anywhere in the map to open the waypoint description dialogue. This is the quickest way to obtain information about airfields, navaids, reporting points, terrain elevation and airspace. The figure Information about EDFE airport shows how this will typically look.

  • Double Tap Gesture: The double tap gesture is equivalent to tap-and-hold.

Information about EDFE airport

Information about EDFE airport

Ownship Position

The ownship position is shown prominently in the moving map, using one of the following symbols.

Symbol

Function

../_images/self-noPosition.png

SatNav is not working. The symbol shows the last known position.

../_images/self-noDirection.png

SatNav is working, and the aircraft is not moving. The symbol shows the current position.

../_images/self-withDirection.png

SatNav is working, and the aircraft is not moving. The symbol shows the current position. The arrow shows the direction of movement.

As soon as you are flying, the app shows the projected flight path for the next five minutes. The flight path vector is sized so that each of the black and white segments corresponds to one minute.

Projected flight path for the next five minutes

Projected flight path for the next five minutes

Traffic Information

Enroute Flight Navigation can connect to your aircraft’s traffic receiver (typically a FLARM device) and display nearby traffic on the moving map. The section Connect to your traffic receiver explains how to establish the connection. The figure Approaching EDTF with traffic shows a typical situation.

Approaching EDTF with traffic

Approaching EDTF with traffic

To show only relevant traffic, Enroute Flight Navigation will display traffic factors only if the vertical distance is less than 1.500m and the horizontal distance less than 20nm.

Warning

Enroute Flight Navigation shows traffic on the moving map, but does not issue traffic warnings. The app contains no collision avoidance algorithms.

Color Coding

Enroute Flight Navigation uses colors to indicate the potential danger of the traffic. This works best when the app is connected to a FLARM device. In this setting, the colors have the following precise meaning.

Color

Meaning

Green

No alarm.

Yellow

Alarm level 1. Collision predicted in 13-18 seconds.

Red

Alarm level 2 or higher. Collision predicted in less than 13 seconds.

Traffic Factors

The moving map display two kinds of traffic.

  • Traffic whose precise position is unknown to the traffic receiver; this is often the case with traffic that has only a Mode-S transponder. This kind of traffic is indicated in the moving map by a transparent circle around the ownship position. The traffic is likely to be found inside that circle.

  • Traffic whose position is precisely known. This traffic is typically equipped with a FLARM or ADS-B transmitter. The symbols used to display this traffic in the moving map are explained below. If the traffic is known to be moving, its projected flight path is indicated with a black-and-white flight vector, similar to the symbol shown in the Figure Projected flight path for the next five minutes for the ownship flight vector.

Symbol

Function

../_images/traffic-noDirection-green.png

The traffic is not moving, or its movement is unknown. No alarm.

../_images/traffic-noDirection-yellow.png

The traffic is not moving, or its movement is unknown. Alarm level 1. Collision predicted in 13-18 seconds.

../_images/traffic-noDirection-red.png

The traffic is not moving, or its movement is unknown. Alarm level 2 or higher. Collision predicted in less than 13 seconds.

../_images/traffic-withDirection-green.png

The traffic is moving, the arrow shows the direction of movement. No alarm.

../_images/traffic-withDirection-yellow.png

The traffic is moving, the arrow shows the direction of movement. Alarm level 1. Collision predicted in 13-18 seconds.

../_images/traffic-withDirection-red.png

The traffic is moving, the arrow shows the direction of movement. Alarm level 2 or higher. Collision predicted in less than 13 seconds.

Traffic labelling

The traffic is labelled with the following pieces of information about the traffic, to the extent known.

  • Traffic type. This is one of “Aircraft”, “Airship”, “Balloon”, “Copter”, “Drone”, “Glider”, “Hang Glider”, “Jet”, “Paraglider”, “Skydiver”, “Static Obstacle” and “Tow Plane”.

  • The traffic callsign.

  • The relative vertical distance, in the units for the distance chosen in the settings on the Aircraft Page. A positive value indicates that the traffic is above you.

  • An arrow symbols pointing upwards, downwards or sideways indicates the vertical speed of the traffic.

Note

Traffic callsigns are shown only if the “FLARM Database” has been installed in the page “Map and Data Library”.

\ No newline at end of file + Main Page and Moving Map Skip to content

Main Page and Moving Map

The main page is the page that you will use the most often. This is also the page that opens when you start the app. The following image shows the Main Page in a typical flight situation.

Flight route window, route set

The Main Page of Enroute Flight Navigation

  • At the top of the screen, you see the Route Information Bar with information about the remaining flight route.

  • The page body shows a moving map with your current position and a number of interactive controls.

  • At the bottom, the Navigation Bar displays information about the current flight situation.

This manual uses the words “Bearing Mode” and “Autopan Mode” to describe two settings that govern the behavior of the map display.

Bearing Mode

The moving map can operate in two “bearing modes”. In the mode “north up”, the map is rotated so that the north direction is up, as you would expect from a paper map. In the mode “track up”, the map is rotated according to your direction of movement, so that your flight direction is up.

Autopan Mode

If the autopan mode is on, the map is automatically moved, so that the position you aircraft is near the center of the map display. If the autopan mode is off, the map is not moved and the position of your aircraft might not be visible on the map.

Route Information Bar

If you have defined a flight route following the steps outlined in the section Plan a Flight, then the top of the Main Page will show a tabular panel with one or two lines of information about the remaining route that you still have to fly. The first line of the table refers to the next waypoint, the second line to the final waypoint in your route.

Code

Meaning

—

Name of the waypoint.

TC

True course to the waypoint (only shown for course to next waypoint).

DIST

Distance to the waypoint.

ETE

Estimated Time Enroute to the waypoint.

ETA

Estimated Arrival Time at the waypoint, in UTC.

  • The units for the distance are chosen according to the settings on the Aircraft Page.

  • If the information cannot be computed (e.g. because the positions is unknown, or because you are flying too far away from the route), the panel shows a brief error message.

  • Close to the final destination, the panel shows the words “Near destination.”

Interactive Controls

The page body shows the following interactive control buttons that can be used together with the standard gestures to operate the app.

Symbol

Function

../_images/ic_menu.png

Opens main menu.

../_images/NorthArrow.png

Switches between modes north up and track up.

../_images/ic_my_location.png

Sets autopan mode to “on”.

../_images/ic_add.png

Zoom in.

../_images/ic_remove.png

Zoom out.

../_images/ic_airplanemode_active.png

This control is shown when the app is not connected to a traffic data receiver. A click opens the traffic receiver status page.

Moving Map

The moving map shows a physical map with shaded terrain relief, overlaid with aviation data. At low zoom values, the map looks similar to the standard 1:50.000 ICAO maps. At higher zoom value, the map will also show traffic circuits and control zone procedures, as you would expect from an approach chart.

Note

Traffic circuits and control zone procedures are available for select countries only. See the section Aeronautical maps for more details.

The moving map shows the following additional items

  • If you have set an Airspace Altitude Limit on the Settings Page, the map will show a little reminder at the top of the screen, with a text such as “Airspaces up to 9500 ft”.

  • To give you a rough estimate for the horizontal distances, the map features a scale. Depending on screen orientation, the scale is shown at the bottom or at the left of the screen.

  • At the very bottom of the screen, there is a copyright notice. Click on the notice to open a dialogue window with more detailed information.

Gesture Controls

The moving map can be controlled by standard gestures.

  • Mouse Wheel: On desktop computers, the mouse wheel zooms in and out.

  • Pinch Gesture: On touch-screen devices, the pinch gesture zooms in and out.

  • Pan Gesture: On touch-screen devices, the pinch the pan gesture moves the map and sets the autopan mode to “off”.

  • Tap-and-hold Gesture: Tap-and-hold anywhere in the map to open the waypoint description dialogue. This is the quickest way to obtain information about airfields, navaids, reporting points, terrain elevation and airspace. The figure Information about EDFE airport shows how this will typically look.

  • Double Tap Gesture: The double tap gesture is equivalent to tap-and-hold.

Information about EDFE airport

Information about EDFE airport

Ownship Position

The ownship position is shown prominently in the moving map, using one of the following symbols.

Symbol

Function

../_images/self-noPosition.png

SatNav is not working. The symbol shows the last known position.

../_images/self-noDirection.png

SatNav is working, and the aircraft is not moving. The symbol shows the current position.

../_images/self-withDirection.png

SatNav is working, and the aircraft is not moving. The symbol shows the current position. The arrow shows the direction of movement.

As soon as you are flying, the app shows the projected flight path for the next five minutes. The flight path vector is sized so that each of the black and white segments corresponds to one minute.

Projected flight path for the next five minutes

Projected flight path for the next five minutes

Traffic Information

Enroute Flight Navigation can connect to your aircraft’s traffic receiver (typically a FLARM device) and display nearby traffic on the moving map. The section Connect to your traffic receiver explains how to establish the connection. The figure Approaching EDTF with traffic shows a typical situation.

Approaching EDTF with traffic

Approaching EDTF with traffic

To show only relevant traffic, Enroute Flight Navigation will display traffic factors only if the vertical distance is less than 1.500m and the horizontal distance less than 20nm.

Warning

Enroute Flight Navigation shows traffic on the moving map, but does not issue traffic warnings. The app contains no collision avoidance algorithms.

Color Coding

Enroute Flight Navigation uses colors to indicate the potential danger of the traffic. This works best when the app is connected to a FLARM device. In this setting, the colors have the following precise meaning.

Color

Meaning

Green

No alarm.

Yellow

Alarm level 1. Collision predicted in 13-18 seconds.

Red

Alarm level 2 or higher. Collision predicted in less than 13 seconds.

Traffic Factors

The moving map display two kinds of traffic.

  • Traffic whose precise position is unknown to the traffic receiver; this is often the case with traffic that has only a Mode-S transponder. This kind of traffic is indicated in the moving map by a transparent circle around the ownship position. The traffic is likely to be found inside that circle.

  • Traffic whose position is precisely known. This traffic is typically equipped with a FLARM or ADS-B transmitter. The symbols used to display this traffic in the moving map are explained below. If the traffic is known to be moving, its projected flight path is indicated with a black-and-white flight vector, similar to the symbol shown in the Figure Projected flight path for the next five minutes for the ownship flight vector.

Symbol

Function

../_images/traffic-noDirection-green.png

The traffic is not moving, or its movement is unknown. No alarm.

../_images/traffic-noDirection-yellow.png

The traffic is not moving, or its movement is unknown. Alarm level 1. Collision predicted in 13-18 seconds.

../_images/traffic-noDirection-red.png

The traffic is not moving, or its movement is unknown. Alarm level 2 or higher. Collision predicted in less than 13 seconds.

../_images/traffic-withDirection-green.png

The traffic is moving, the arrow shows the direction of movement. No alarm.

../_images/traffic-withDirection-yellow.png

The traffic is moving, the arrow shows the direction of movement. Alarm level 1. Collision predicted in 13-18 seconds.

../_images/traffic-withDirection-red.png

The traffic is moving, the arrow shows the direction of movement. Alarm level 2 or higher. Collision predicted in less than 13 seconds.

Traffic labelling

The traffic is labelled with the following pieces of information about the traffic, to the extent known.

  • Traffic type. This is one of “Aircraft”, “Airship”, “Balloon”, “Copter”, “Drone”, “Glider”, “Hang Glider”, “Jet”, “Paraglider”, “Skydiver”, “Static Obstacle” and “Tow Plane”.

  • The traffic callsign.

  • The relative vertical distance, in the units for the distance chosen in the settings on the Aircraft Page. A positive value indicates that the traffic is above you.

  • An arrow symbols pointing upwards, downwards or sideways indicates the vertical speed of the traffic.

Note

Traffic callsigns are shown only if the “FLARM Database” has been installed in the page “Map and Data Library”.

\ No newline at end of file diff --git a/docs/manual/03-reference/mapData.html b/docs/manual/03-reference/mapData.html index 0e02a668..bdd16391 100644 --- a/docs/manual/03-reference/mapData.html +++ b/docs/manual/03-reference/mapData.html @@ -1 +1 @@ - Map Data Skip to content

Map Data

Our maps available for offline use, so that the app does not require any internet connection in flight.

Base maps

Our base maps are generated from Open Streetmap data.

Terrain maps

Our terrain maps are derived from the Terrain Tiles Open Dataset on Amazon AWS. The underlying data sources are a mix of:

  • 3DEP (formerly NED and NED Topobathy) in the United States, 10 meters outside of Alaska, 3 meter in select land and territorial water areas

  • ArcticDEM strips of 5 meter mosaics across all of the land north of 60° latitude, including Alaska, Canada, Greenland, Iceland, Norway, Russia, and Sweden

  • CDEM (Canadian Digital Elevation Model) in Canada, with variable spatial resolution (from 20-400 meters) depending on the latitude.

  • data.gov.uk, 2 meters over most of the United Kingdom

  • data.gv.at, 10 meters over Austria

  • ETOPO1 for ocean bathymetry, 1 arc-minute resolution globally

  • EUDEM in most of Europe at 30 meter resolution, including Albania, Austria, Belgium, Bosnia and Herzegovina, Bulgaria, Croatia, Cyprus, Czechia, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Kosovo, Latvia, Liechtenstein, Lithuania, Luxembourg, Macedonia, Malta, Montenegro, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, and United Kingdom

  • Geoscience Australia’s DEM of Australia, 5 meters around coastal regions in South Australia, Victoria, and Northern Territory

  • GMTED globally, coarser resolutions at 7.5”, 15”, and 30” in land areas

  • INEGI’s continental relief in Mexico

  • Kartverket’s Digital Terrain Model, 10 meters over Norway

  • LINZ, 8 meters over New Zealand

  • SRTM globally except high latitudes, 30 meters (90 meters nominal quality) in land areas

Attributions

  • ArcticDEM terrain data DEM(s) were created from DigitalGlobe, Inc., imagery and funded under National Science Foundation awards 1043681, 1559691, and 1542736;

  • Australia terrain data © Commonwealth of Australia (Geoscience Australia) 2017;

  • Austria terrain data © offene Daten Österreichs – Digitales Geländemodell (DGM) Österreich;

  • Canada terrain data contains information licensed under the Open Government Licence – Canada;

  • Europe terrain data produced using Copernicus data and information funded by the European Union - EU-DEM layers;

  • Global ETOPO1 terrain data U.S. National Oceanic and Atmospheric Administration

  • Mexico terrain data source: INEGI, Continental relief, 2016;

  • New Zealand terrain data Copyright 2011 Crown copyright (c) Land Information New Zealand and the New Zealand Government (All rights reserved);

  • Norway terrain data © Kartverket;

  • United Kingdom terrain data © Environment Agency copyright and/or database right 2015. All rights reserved;

  • United States 3DEP (formerly NED) and global GMTED2010 and SRTM terrain data courtesy of the U.S. Geological Survey.

Aeronautical maps

Update policy

Our aeronautical maps are updated once per day, provided that new data is available. Note, however, that we do not guarantee regular updates.

Data origin

The aeronautical maps are compiled from databases provided by the openAIP and the open flightmaps projects. While openAIP covers most of the world, the open flightmaps cover fewer countries but contain more detailed information.

Map Feature

Data Origin

Airfields

openAIP

Airspace: Nature Preserve Areas

open flightmaps

Airspace: all other

openAIP

Navaids

openAIP

Procedures (Traffic Circuits, …)

open flightmaps

Reporting Points

open flightmaps

List of maps

For simplicity, our maps are divided in “Class 1” and “Class 2”.

  • Class 1 maps are compiled from openAIP and open flightmaps data. These maps contain complete information about airspaces, airfields and navaids. In addition, the maps contain (mandatory) reporting points. Some of our class 1 maps also show traffic circuits and flight procedures for control zones.

  • Class 2 maps are compiled from openAIP data only. They contain complete information about airspaces, airfields and navaids.

Below is a complete list of the maps that we offer.

Continent

Country

Class

Africa

Canary Islands

Class 1

Africa

Madagascar

Class 2

Africa

Namibia

Class 1

Africa

South Africa

Class 1

Asia

Bahrain

Class 2

Asia

Unit. Emirates

Class 2

Asia

Japan

Class 2

Asia

Qatar

Class 2

Australia Oceanica

Australia

Class 2

Australia Oceanica

New Zealand

Class 2

Europe

Austria

Class 1

Europe

Belgium

Class 1

Europe

Bulgaria

Class 1

Europe

Croatia

Class 1

Europe

Cyprus

Class 2

Europe

Czech Republic

Class 1

Europe

Denmark

Class 1

Europe

Estonia

Class 2

Europe

Finland

Class 1

Europe

France

Class 2

Europe

Germany

Class 1

Europe

Great Britain

Class 1

Europe

Greece

Class 1

Europe

Hungary

Class 1

Europe

Iceland

Class 2

Europe

Ireland

Class 2

Europe

Italy

Class 1

Europe

Latvia

Class 2

Europe

Liechtenstein

Class 2

Europe

Lithuania

Class 2

Europe

Luxembourg

Class 2

Europe

Malta

Class 2

Europe

Netherlands

Class 1

Europe

North. Ireland

Class 1

Europe

Norway

Class 2

Europe

Poland

Class 1

Europe

Portugal

Class 2

Europe

Romania

Class 1

Europe

Serbia

Class 2

Europe

Slovakia

Class 1

Europe

Slowenia

Class 1

Europe

Spain

Class 2

Europe

Sweden

Class 1

Europe

Switzerland

Class 1

North America

Canada

Class 2

North America

United States

Class 2

South America

Argentina

Class 2

South America

Brazil

Class 2, NavAids missing

South America

Colombia

Class 2

South America

Falkland Is.

Class 2

\ No newline at end of file + Map Data Skip to content

Map Data

Our maps available for offline use, so that the app does not require any internet connection in flight.

Base maps

Our base maps are generated from Open Streetmap data.

Terrain maps

Our terrain maps are derived from the Terrain Tiles Open Dataset on Amazon AWS. The underlying data sources are a mix of:

  • 3DEP (formerly NED and NED Topobathy) in the United States, 10 meters outside of Alaska, 3 meter in select land and territorial water areas

  • ArcticDEM strips of 5 meter mosaics across all of the land north of 60° latitude, including Alaska, Canada, Greenland, Iceland, Norway, Russia, and Sweden

  • CDEM (Canadian Digital Elevation Model) in Canada, with variable spatial resolution (from 20-400 meters) depending on the latitude.

  • data.gov.uk, 2 meters over most of the United Kingdom

  • data.gv.at, 10 meters over Austria

  • ETOPO1 for ocean bathymetry, 1 arc-minute resolution globally

  • EUDEM in most of Europe at 30 meter resolution, including Albania, Austria, Belgium, Bosnia and Herzegovina, Bulgaria, Croatia, Cyprus, Czechia, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Kosovo, Latvia, Liechtenstein, Lithuania, Luxembourg, Macedonia, Malta, Montenegro, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, and United Kingdom

  • Geoscience Australia’s DEM of Australia, 5 meters around coastal regions in South Australia, Victoria, and Northern Territory

  • GMTED globally, coarser resolutions at 7.5”, 15”, and 30” in land areas

  • INEGI’s continental relief in Mexico

  • Kartverket’s Digital Terrain Model, 10 meters over Norway

  • LINZ, 8 meters over New Zealand

  • SRTM globally except high latitudes, 30 meters (90 meters nominal quality) in land areas

Attributions

  • ArcticDEM terrain data DEM(s) were created from DigitalGlobe, Inc., imagery and funded under National Science Foundation awards 1043681, 1559691, and 1542736;

  • Australia terrain data © Commonwealth of Australia (Geoscience Australia) 2017;

  • Austria terrain data © offene Daten Österreichs – Digitales Geländemodell (DGM) Österreich;

  • Canada terrain data contains information licensed under the Open Government Licence – Canada;

  • Europe terrain data produced using Copernicus data and information funded by the European Union - EU-DEM layers;

  • Global ETOPO1 terrain data U.S. National Oceanic and Atmospheric Administration

  • Mexico terrain data source: INEGI, Continental relief, 2016;

  • New Zealand terrain data Copyright 2011 Crown copyright (c) Land Information New Zealand and the New Zealand Government (All rights reserved);

  • Norway terrain data © Kartverket;

  • United Kingdom terrain data © Environment Agency copyright and/or database right 2015. All rights reserved;

  • United States 3DEP (formerly NED) and global GMTED2010 and SRTM terrain data courtesy of the U.S. Geological Survey.

Aeronautical maps

Update policy

Our aeronautical maps are updated once per day, provided that new data is available. Note, however, that we do not guarantee regular updates.

Data origin

The aeronautical maps are compiled from databases provided by the openAIP and the open flightmaps projects. While openAIP covers most of the world, the open flightmaps cover fewer countries but contain more detailed information.

Map Feature

Data Origin

Airfields

openAIP

Airspace: Nature Preserve Areas

open flightmaps

Airspace: all other

openAIP

Navaids

openAIP

Procedures (Traffic Circuits, …)

open flightmaps

Reporting Points

open flightmaps

List of maps

For simplicity, our maps are divided in “Class 1” and “Class 2”.

  • Class 1 maps are compiled from openAIP and open flightmaps data. These maps contain complete information about airspaces, airfields and navaids. In addition, the maps contain (mandatory) reporting points. Some of our class 1 maps also show traffic circuits and flight procedures for control zones.

  • Class 2 maps are compiled from openAIP data only. They contain complete information about airspaces, airfields and navaids.

Below is a complete list of the maps that we offer.

Continent

Country

Class

Africa

Canary Islands

Class 1

Africa

Madagascar

Class 2

Africa

Namibia

Class 1

Africa

South Africa

Class 1

Asia

Bahrain

Class 2

Asia

Unit. Emirates

Class 2

Asia

Japan

Class 2

Asia

Qatar

Class 2

Australia Oceanica

Australia

Class 2

Australia Oceanica

New Zealand

Class 2

Europe

Austria

Class 1

Europe

Belgium

Class 1

Europe

Bulgaria

Class 1

Europe

Croatia

Class 1

Europe

Cyprus

Class 2

Europe

Czech Republic

Class 1

Europe

Denmark

Class 1

Europe

Estonia

Class 2

Europe

Finland

Class 1

Europe

France

Class 2

Europe

Germany

Class 1

Europe

Great Britain

Class 1

Europe

Greece

Class 1

Europe

Hungary

Class 1

Europe

Iceland

Class 2

Europe

Ireland

Class 2

Europe

Italy

Class 1

Europe

Latvia

Class 2

Europe

Liechtenstein

Class 2

Europe

Lithuania

Class 2

Europe

Luxembourg

Class 2

Europe

Malta

Class 2

Europe

Netherlands

Class 1

Europe

North. Ireland

Class 1

Europe

Norway

Class 2

Europe

Poland

Class 1

Europe

Portugal

Class 2

Europe

Romania

Class 1

Europe

Serbia

Class 2

Europe

Slovakia

Class 1

Europe

Slowenia

Class 1

Europe

Spain

Class 2

Europe

Sweden

Class 1

Europe

Switzerland

Class 1

North America

Canada

Class 2

North America

United States

Class 2

South America

Argentina

Class 2

South America

Brazil

Class 2, NavAids missing

South America

Colombia

Class 2

South America

Falkland Is.

Class 2

\ No newline at end of file diff --git a/docs/manual/03-reference/platform.html b/docs/manual/03-reference/platform.html index 0b76f718..0162c81d 100644 --- a/docs/manual/03-reference/platform.html +++ b/docs/manual/03-reference/platform.html @@ -1 +1 @@ - Platform notes Skip to content

Platform notes

Android

Network security problems

Like most other programs, Enroute Flight Navigation uses Transport Layer Security (TLS) for secure communication with servers on the internet. The technology relies on digital certificates that are built into the Android operating system and can only be updated by the device manufacturer through system security updates. Regretfully, manufacturers of Android devices are often not interested in after-sales support and provide updates only for a very short period of time, if at all.

If a device does not receive regular system updates, the certificates will expire after a while, and secure network connections are no longer possible. As covered in the media, many users of systems running Android 7.1 (or below) started to experience problems on 30. September 2021, when an important certificate expired.

When certificates expire, some apps will stop working. Other app authors prefer to hide the complexity of secure communication from their users and write apps that will silently revert to insecure communication. These apps appear to run as normal, but leave communication (and eventually the system) open to tampering and manipulation.

The author of Enroute Flight Navigation believes that pilots should be able to make an informed decision about the security of their systems. Enroute Flight Navigation will tell the user of any network security errors. Users can then decide to do one of the following.

  • Replace the device by a more recent model, preferably from one of the few manufacturers who offer long-time support for their products.

  • Accept the risk of insecure communication and ignore network security errors in the future.

Note

The author, who is concerned about short-lived digital products, uses a Fairphone personally. Fairphones are long-lasting, can be repaired easily and receive many years of security updates. Other brands might have similar offers.

Screen backlighting

Enroute Flight Navigation overrides the system settings of your device and ensures that the screen backlighting is always on. To save battery power, the screen can be switched off manually with the hardware “power button” of your device.

Screen locking

Enroute Flight Navigation stays on top of the lock screen of your device. It will therefore be shown immediately as soon as the screen is switched on. You can therefore use Enroute Flight Navigation without unlocking your device.

Wi-Fi locking

When running on Android, Enroute Flight Navigation acquires a Wi-Fi lock as soon as the app receives heartbeat messages from one of the channels where it listens for traffic receivers. The lock is released when the messages no longer arrive.

Linux desktop

File import by drag-and-drop

It is possible to import files by dragging and dropping then anywhere in the main window of Enroute Flight Navigation. The following file types are accepted.

Content

Format

File name

FLARM Test Data

Text

*.txt

Flight Route

GeoJSON

*.geojson

Flight Route

GPX

*.gpx

Command line

Rather than importing file by drag-and-drop, file names can also be given when starting Enroute Flight Navigation via the Unix command line. The following command line options are supported.

Option

Description

-h, –help

Displays help on commandline options.

–help-all

Displays help including Qt specific options.

-v, –version

Displays version information.

–sg

Run simulator and generate screenshots for Google Play

–sm

Run simulator and generate screenshots for the manual

\ No newline at end of file + Platform notes Skip to content

Platform notes

Android

Network security problems

Like most other programs, Enroute Flight Navigation uses Transport Layer Security (TLS) for secure communication with servers on the internet. The technology relies on digital certificates that are built into the Android operating system and can only be updated by the device manufacturer through system security updates. Regretfully, manufacturers of Android devices are often not interested in after-sales support and provide updates only for a very short period of time, if at all.

If a device does not receive regular system updates, the certificates will expire after a while, and secure network connections are no longer possible. As covered in the media, many users of systems running Android 7.1 (or below) started to experience problems on 30. September 2021, when an important certificate expired.

When certificates expire, some apps will stop working. Other app authors prefer to hide the complexity of secure communication from their users and write apps that will silently revert to insecure communication. These apps appear to run as normal, but leave communication (and eventually the system) open to tampering and manipulation.

The author of Enroute Flight Navigation believes that pilots should be able to make an informed decision about the security of their systems. Enroute Flight Navigation will tell the user of any network security errors. Users can then decide to do one of the following.

  • Replace the device by a more recent model, preferably from one of the few manufacturers who offer long-time support for their products.

  • Accept the risk of insecure communication and ignore network security errors in the future.

Note

The author, who is concerned about short-lived digital products, uses a Fairphone personally. Fairphones are long-lasting, can be repaired easily and receive many years of security updates. Other brands might have similar offers.

Screen backlighting

Enroute Flight Navigation overrides the system settings of your device and ensures that the screen backlighting is always on. To save battery power, the screen can be switched off manually with the hardware “power button” of your device.

Screen locking

Enroute Flight Navigation stays on top of the lock screen of your device. It will therefore be shown immediately as soon as the screen is switched on. You can therefore use Enroute Flight Navigation without unlocking your device.

Wi-Fi locking

When running on Android, Enroute Flight Navigation acquires a Wi-Fi lock as soon as the app receives heartbeat messages from one of the channels where it listens for traffic receivers. The lock is released when the messages no longer arrive.

Linux desktop

File import by drag-and-drop

It is possible to import files by dragging and dropping then anywhere in the main window of Enroute Flight Navigation. The following file types are accepted.

Content

Format

File name

FLARM Test Data

Text

*.txt

Flight Route

GeoJSON

*.geojson

Flight Route

GPX

*.gpx

Command line

Rather than importing file by drag-and-drop, file names can also be given when starting Enroute Flight Navigation via the Unix command line. The following command line options are supported.

Option

Description

-h, –help

Displays help on commandline options.

–help-all

Displays help including Qt specific options.

-v, –version

Displays version information.

–sg

Run simulator and generate screenshots for Google Play

–sm

Run simulator and generate screenshots for the manual

\ No newline at end of file diff --git a/docs/manual/03-reference/settings.html b/docs/manual/03-reference/settings.html index 066a08ba..1e9d2b94 100644 --- a/docs/manual/03-reference/settings.html +++ b/docs/manual/03-reference/settings.html @@ -1 +1 @@ - Settings Page Skip to content

Settings Page

Enroute Flight Navigation is designed to be simple. The number of user settings is deliberately small. To access the user settings, open the main menu and choose “Settings.”

Moving Map

The settings grouped under “Moving Map” change the appearance of the map display.

Airspace Altitude Limit

If you never fly higher than 5.000ft, you will probably not be interested in airspaces that begin above FL100. Enroute Flight Navigation allows you to set an altitude limit to improve the readability of the moving map. Once set, the app will show only airspaces below that limit. Tap on the entry “Airspace Altitude Limit” to set or unset the altitude limit.

Once you set an altitude limit, the moving map will display a little warning (“Airspaces up to 9,500 ft”) to remind you that the moving map does not show all airspaces. The app will automatically increase the limit when your aircraft approaches the altitude limit from below.

Warning

Airspace boundaries are often flight levels. The true altitude of a flight level depends on meteorological conditions (such as the temperature gradient) and is not known to Enroute Flight Navigation. When deciding which airspace to show, the app will use an approximation. The approximation might be off by 1,000ft or more in extreme weather. Always leave an ample safety margin when setting an airspace altitude limit.

Gliding Sectors

In regions with high glider traffic, local regulations often allow gliders to fly in airspaces that are otherwise difficult to access, such as control zones. The moving map displays these “Gliding Sectors” in bright yellow. If you are not flying a glider, the gliding sectors are probably not relevant. Hiding the gliding sectors might improve the readability of the moving map.

Hillshading

We have received a report from a user, who experienced issues with the hillshading graphics on a very old device, potentially because of buggy system libraries. If you experience problems, use this switch to disable the hillshading feature.

User Interface

Large Fonts

Use this option to enlarge fonts for improved readability.

Night mode

The “Night Mode” of Enroute Flight Navigation is similar to the “Dark Mode” found in many other apps. We designed the night mode for pilots performing VFR flights by night, whose eyes have adapted to the darkness. Compared with other apps, you will find that the display is quite dark indeed.

Voice Notifications

Pilots should not be looking at their mobile devices for extended periods of time. Enroute Flight Navigation is therefore able to read notification texts in addition to showing them on the screen. Since we expect that not everybody likes this feature, this setting item allows switching voice notification on and off.

System

Primary Position Data Source

Enroute Flight Navigation can either use the built-in satnav receiver of your device or a connected traffic receiver as a primary position data source. This setting is essential if your device has reception problems or if you use Enroute Flight Navigation together with a flight simulator.

  • You will most likely prefer the built-in satnav receiver for actual flight. The built-in receiver provides one position update per second on a typical Android system, while traffic receivers do not always provide timely position updates.

  • If you use Enroute Flight Navigation together with a flight simulator, you must choose the traffic receiver as a primary position data source. Flight simulators broadcast position information of simulated aircraft via Wi-Fi, using the same protocol that a traffic data receiver would use in a real plane. As long as the built-in satnav receiver is selected, all position information provided by your flight simulator is ignored.

Note

Setting a traffic receiver as a primary position data source is safe even when the app is not connected to a traffic receiver. When no traffic receiver is connected, Enroute Flight Navigation will automatically fall back using the built-in satnav receiver of your device.

Ignore network security errors

This entry is visible if you have asked the app to download data via insecure internet connections after a secure connection attempt failed. Uncheck this item to revert to the standard policy, which enforces secure connections.

Clear password storage

This entry is visible if you have connected to a traffic data receiver that requires a password in addition to the Wi-Fi password and if you have asked the app to remember the password. Tap on this entry to clear the password storage.

Help

The items grouped under “Help” refer the user to this manual.

\ No newline at end of file + Settings Page Skip to content

Settings Page

Enroute Flight Navigation is designed to be simple. The number of user settings is deliberately small. To access the user settings, open the main menu and choose “Settings.”

Moving Map

The settings grouped under “Moving Map” change the appearance of the map display.

Airspace Altitude Limit

If you never fly higher than 5.000ft, you will probably not be interested in airspaces that begin above FL100. Enroute Flight Navigation allows you to set an altitude limit to improve the readability of the moving map. Once set, the app will show only airspaces below that limit. Tap on the entry “Airspace Altitude Limit” to set or unset the altitude limit.

Once you set an altitude limit, the moving map will display a little warning (“Airspaces up to 9,500 ft”) to remind you that the moving map does not show all airspaces. The app will automatically increase the limit when your aircraft approaches the altitude limit from below.

Warning

Airspace boundaries are often flight levels. The true altitude of a flight level depends on meteorological conditions (such as the temperature gradient) and is not known to Enroute Flight Navigation. When deciding which airspace to show, the app will use an approximation. The approximation might be off by 1,000ft or more in extreme weather. Always leave an ample safety margin when setting an airspace altitude limit.

Gliding Sectors

In regions with high glider traffic, local regulations often allow gliders to fly in airspaces that are otherwise difficult to access, such as control zones. The moving map displays these “Gliding Sectors” in bright yellow. If you are not flying a glider, the gliding sectors are probably not relevant. Hiding the gliding sectors might improve the readability of the moving map.

Hillshading

We have received a report from a user, who experienced issues with the hillshading graphics on a very old device, potentially because of buggy system libraries. If you experience problems, use this switch to disable the hillshading feature.

User Interface

Large Fonts

Use this option to enlarge fonts for improved readability.

Night mode

The “Night Mode” of Enroute Flight Navigation is similar to the “Dark Mode” found in many other apps. We designed the night mode for pilots performing VFR flights by night, whose eyes have adapted to the darkness. Compared with other apps, you will find that the display is quite dark indeed.

Voice Notifications

Pilots should not be looking at their mobile devices for extended periods of time. Enroute Flight Navigation is therefore able to read notification texts in addition to showing them on the screen. Since we expect that not everybody likes this feature, this setting item allows switching voice notification on and off.

System

Primary Position Data Source

Enroute Flight Navigation can either use the built-in satnav receiver of your device or a connected traffic receiver as a primary position data source. This setting is essential if your device has reception problems or if you use Enroute Flight Navigation together with a flight simulator.

  • You will most likely prefer the built-in satnav receiver for actual flight. The built-in receiver provides one position update per second on a typical Android system, while traffic receivers do not always provide timely position updates.

  • If you use Enroute Flight Navigation together with a flight simulator, you must choose the traffic receiver as a primary position data source. Flight simulators broadcast position information of simulated aircraft via Wi-Fi, using the same protocol that a traffic data receiver would use in a real plane. As long as the built-in satnav receiver is selected, all position information provided by your flight simulator is ignored.

Note

Setting a traffic receiver as a primary position data source is safe even when the app is not connected to a traffic receiver. When no traffic receiver is connected, Enroute Flight Navigation will automatically fall back using the built-in satnav receiver of your device.

Ignore network security errors

This entry is visible if you have asked the app to download data via insecure internet connections after a secure connection attempt failed. Uncheck this item to revert to the standard policy, which enforces secure connections.

Clear password storage

This entry is visible if you have connected to a traffic data receiver that requires a password in addition to the Wi-Fi password and if you have asked the app to remember the password. Tap on this entry to clear the password storage.

Help

The items grouped under “Help” refer the user to this manual.

\ No newline at end of file diff --git a/docs/manual/04-appendix/authors.html b/docs/manual/04-appendix/authors.html new file mode 100644 index 00000000..781d031f --- /dev/null +++ b/docs/manual/04-appendix/authors.html @@ -0,0 +1 @@ + Authors Skip to content

Authors

The app Enroute Flight Navigation was written by Stefan Kebekus, flight enthusiast since 1986 and member of the Akaflieg Freiburg flight club. Stefan flies gliders and motor planes.

Address: Stefan Kebekus, Wintererstraße 77, 79104 Freiburg, Germany · stefan.kebekus@gmail.com

Contributions

iOS Version The app has been ported to iOS by Simon Schneider. Simon is currently student pilot (PPL) and member of the Akaflieg Freiburg flight club, just like Stefan.

Programming Heinz Blöchinger has helped us with OpenAir support. After 15 years of alpine gliding, Heinz has fulfilled a big dream and now flies helicopters.

Translations

  • French: Adrien Crovato and Luca Riva. Both are private pilots and aerospace engineers. Luca is also doing aerobatics.

  • German: Markus Sachs. Markus flies trikes and is an enthusiastic ‘Co’ on everyting else that flies.

  • Italian: Ivan Battistella and Antonio Fardella. Antonio is a naval aviator with a passion for everything challenging.

  • Polish: Sławek Mikuła.

  • Spanish: Luca Riva.

Alumni

  • Luca Bertoncello (Italian translation)

  • Adrien Crovato (Integration of weather information)

  • Michael Horbaschk (Manual)

  • Szymon Kocur (Polish translation)

  • Heiner Tholen (User interface)

  • Johannes Zellner (Geoid correction for altitude)

\ No newline at end of file diff --git a/docs/manual/04-appendix/license_3rdParty.html b/docs/manual/04-appendix/license_3rdParty.html index 5e7f517e..9e58a35d 100644 --- a/docs/manual/04-appendix/license_3rdParty.html +++ b/docs/manual/04-appendix/license_3rdParty.html @@ -1 +1 @@ - Third party software and data Skip to content

Third party software and data

Enroute Flight Navigation builds on numerours open-source software components and on open-source data.

Geographic maps

As a flight navigation program, Enroute Flight Navigation heavily relies on geographic map data. The geographic maps are not included in the program, but are downloaded at runtime. They are compiled from the following sources.

Software and data included in the program

Depending on platform and configuration, the following components might be included in the installation of Enroute Flight Navigation.

\ No newline at end of file + Third party software and data Skip to content

Third party software and data

Enroute Flight Navigation builds on numerours open-source software components and on open-source data.

Geographic maps

As a flight navigation program, Enroute Flight Navigation heavily relies on geographic map data. The geographic maps are not included in the program, but are downloaded at runtime. They are compiled from the following sources.

Software and data included in the program

Depending on platform and configuration, the following components might be included in the installation of Enroute Flight Navigation.

\ No newline at end of file diff --git a/docs/manual/04-appendix/license_enroute.html b/docs/manual/04-appendix/license_enroute.html index b4fe7267..35c7c1f0 100644 --- a/docs/manual/04-appendix/license_enroute.html +++ b/docs/manual/04-appendix/license_enroute.html @@ -1,4 +1,4 @@ - Software license Skip to content

Software license

The program Enroute Flight Navigation is licensed under the GNU General Public License V3 or, at your choice, any later version of this license.

 GNU GENERAL PUBLIC LICENSE
+                         Software license                      Skip to content  
  
 
  
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
 
 
Software license
 
The program Enroute Flight Navigation is licensed under the GNU General Public License V3 or, at your choice, any later version of this license.
 
 GNU GENERAL PUBLIC LICENSE
 
  Version 3, 29 June 2007
 
@@ -594,4 +594,4 @@
    waiver of all civil liability in connection with the Program, unless a
    warranty or assumption of liability accompanies a copy of the Program in
    return for a fee.
-
 
 
 
 
 
 
 
   
\ No newline at end of file
+
\ No newline at end of file diff --git a/docs/manual/04-appendix/licenses_overview.html b/docs/manual/04-appendix/licenses_overview.html index 521a6dd6..889f1d77 100644 --- a/docs/manual/04-appendix/licenses_overview.html +++ b/docs/manual/04-appendix/licenses_overview.html @@ -1 +1 @@ - <no title> Skip to content
\ No newline at end of file + <no title> Skip to content
\ No newline at end of file diff --git a/docs/manual/04-appendix/privacy.html b/docs/manual/04-appendix/privacy.html index 966d6067..6c5a9e87 100644 --- a/docs/manual/04-appendix/privacy.html +++ b/docs/manual/04-appendix/privacy.html @@ -1 +1 @@ - Privacy policies Skip to content

Privacy policies

We do not process any personal data from you. Data that you enter into the app (including routes, waypoints, and aircraft specifics) is stored locally on your device, is not transmitted to us, and is not processed by us.

However, to ensure the functionality, the app must transmit following data to servers on the internet.

  • The app regularly checks for updates and allows downloading maps and data from a server at the University of Freiburg to your device. In order to provide this functionality, your device’s IP address must be transmitted to the server. Knowledge of the IP address is necessary for the server to respond. However, the server does not store any personal data about you in its log files. In particular, it does not store the IP address of your device in its log files. We can assure this because the server is under our control.

  • The app shows METARs and TAFs for airfields near your current location and near your currently planned route. It also shows METARs and TAFs for all waypoints that you open in the app. In order to provide this functionality, your current location, your currently planned route, waypoint coordinates, and your device’s IP address must be transmitted to web services at the Aviation Weather Center. Knowledge of the IP address is necessary for the web services to respond. The web services cannot read any other data from your device in the process. However, you must expect that your device’s IP address will be stored together with the transmitted position data. The web services are operated by the US government and are beyond our control. Detailed information about these web services can be found at https://www.aviationweather.gov/dataserver.

  • The app shows NOTAMs for places near your current location and near your currently planned route. It also shows NOTAMs for all waypoints that you open in the app. In order to provide this functionality, your current location, your currently planned route, waypoint coordinates, and your device’s IP address must be transmitted to web services at the Federal Aviation Administration. Knowledge of the IP address is necessary for the web services to respond. The web services cannot read any other data from your device in the process. However, you must expect that the IP address of your device will be stored together with the transmitted position data. The web services are operated by the US government and are beyond our control. Detailed information about these web services can be found at https://api.faa.gov/s.

Responsible

Stefan Kebekus, Wintererstraße 77, 79104 Freiburg im Breisgau, Germany

\ No newline at end of file + Privacy Policies Skip to content

Privacy Policies

English

We do not process any personal data from you. Data that you enter into the app (including routes, waypoints, and aircraft specifics) is stored locally on your device. The data not transmitted to us and is not processed by us.

However, to ensure the functionality, the app must transmit following data to servers on the internet.

  • The app regularly checks for updates and allows downloading maps and data from a server at the University of Freiburg to your device. In order to provide this functionality, your device’s IP address must be transmitted to the server. Knowledge of the IP address is necessary for the server to respond. However, the server does not store any personal data about you in its log files. In particular, it does not store the IP address of your device in its log files. We can assure this because the server is under our control.

  • The app shows METARs and TAFs for airfields near your current location and near your currently planned route. It also shows METARs and TAFs for all waypoints that you open in the app. In order to provide this functionality, your current location, your currently planned route, waypoint coordinates, and your device’s IP address must be transmitted to web services at the Aviation Weather Center. Knowledge of the IP address is necessary for the web services to respond. The web services cannot read any other data from your device in the process. However, you must expect that your device’s IP address will be stored together with the transmitted position data. The web services are operated by the US government and are beyond our control. Detailed information about these web services can be found at https://www.aviationweather.gov/dataserver.

  • The app shows NOTAMs for places near your current location and near your currently planned route. It also shows NOTAMs for all waypoints that you open in the app. In order to provide this functionality, your current location, your currently planned route, waypoint coordinates, and your device’s IP address must be transmitted to web services at the Federal Aviation Administration. Knowledge of the IP address is necessary for the web services to respond. The web services cannot read any other data from your device in the process. However, you must expect that the IP address of your device will be stored together with the transmitted position data. The web services are operated by the US government and are beyond our control. Detailed information about these web services can be found at https://api.faa.gov/s.

Responsible: Stefan Kebekus, Wintererstraße 77, 79104 Freiburg im Breisgau, Germany

Deutsche Übersetzung

Wir verarbeiten keine personenbezogenen Daten von Ihnen. Daten, die Sie in dieser App eingeben (wie zum Beispiel Routen, Wegpunkte und Luftfahrzeugdaten), werden nur lokal auf dem Gerät abgelegt. Die Daten werden nicht an uns übermittelt und nicht von uns verarbeitet.

Um die Funktionalität der App gewährleisten zu können müssen allerdings folgende Daten an Server im Internet übermittelt werden.

  • Die App sucht regelmäßig nach Updates und bietet die Möglichkeit, Karten und Daten von einem Server der Universität Freiburg auf Ihr Gerät herunterzuladen. Um diese Funktionalität anzubieten, muss die IP-Adresse ihres Geräts an den Server übertragen werden. Der Server benötigt die IP-Adresse, um ihrem Gerät zu antworten. Der Server speichert aber keine personenbezogenen Daten von Ihnen in den Loggdateien. Dies gilt insbesondere für die IP-Adresse Ihres Geräts. Wir können dies zusichern, weil sich der Server unter unserer Kontrolle befindet.

  • Die App zeigt Ihnen METARs und TAFs für Landeplätze nahe Ihrem aktuellen Standort und Ihrer geplanten Route an. Die App zeigt zusätzlich METARs und TAFs für alle Wegpunkte an, die Sie in der App öffnen. Um diese Funktionalität anzubieten, muss die App Ihren aktuellen Standort, Ihre geplante Route, Wegpunktkoordinaten und die IP-Adresse Ihres Geräts an Webservices des Aviation Weather Center übermitteln. Die Webservices benötigen die IP-Adresse, um ihrem Gerät zu antworten. Die Webservices können keine weiteren Daten Ihres Gerätes auslesen. Allerdings müssen Sie damit rechnen, dass die IP-Adresse Ihres Gerätes zusammen mit den übermittelten Positionsdaten gespeichert wird. Die Webservices werden von der US-Regierung betrieben und entziehen sich unserer Kontrolle. Detaillierte Informationen zu den Webservices finden Sie unter https://www.aviationweather.gov/dataserver.

  • Die App zeigt Ihnen NOTAMs für Orte nahe Ihres aktuellen Standorts und Ihrer aktuell geplante Route an. Die App zeigt zusätzlich NOTAMs für alle Wegpunkte an, die Sie in der App öffnen. Um diese Funktionalität anzubieten, muss die App Ihren aktuellen Standort, Ihre aktuell geplante Route, Wegpunktkoordinaten und die IP-Adresse Ihres Geräts an Webservices der Federal Aviation Administration übermitteln. Die Webservices benötigen die IP-Adresse, um ihrem Gerät zu antworten. Die Webservices können keine weiteren Daten Ihres Gerätes auslesen. Allerdings müssen Sie damit rechnen, dass die IP-Adresse Ihres Gerätes zusammen mit den übermittelten Positionsdaten gespeichert wird. Die Webservices werden von der US-Regierung betrieben und entziehen sich unserer Kontrolle. Detaillierte Informationen zu den Webservices finden Sie unter https://api.faa.gov/s.

Verantwortlich: Stefan Kebekus, Wintererstraße 77, 79104 Freiburg im Breisgau, Germany

Traduction en français

Nous ne traitons aucune donnée personnelle vous concernant. Les données que vous entrez dans l’application (y compris les itinéraires, les waypoints et les spécificités de l’avion) sont stockées localement sur votre appareil. Les données ne nous sont pas transmises et ne sont pas traitées par nous.

Cependant, pour assurer la fonctionnalité, l’application doit transmettre les données suivantes aux serveurs sur Internet.

  • L’application vérifie régulièrement les mises à jour et permet de télécharger des cartes et des données depuis un serveur de l’Université de Fribourg sur votre appareil. Afin de fournir cette fonctionnalité, l’adresse IP de votre appareil doit être transmise au serveur. La connaissance de l’adresse IP est nécessaire pour que le serveur réponde. Cependant, le serveur ne stocke aucune donnée personnelle vous concernant dans ses fichiers journaux. En particulier, il ne stocke pas l’adresse IP de votre appareil dans ses fichiers journaux. Nous pouvons l’assurer car le serveur est sous notre contrôle.

  • L’application affiche les METAR et les TAF pour les aérodromes à proximité de votre position actuelle et à proximité de votre itinéraire actuellement planifié. Il affiche également les METAR et les TAF pour tous les waypoints que vous ouvrez dans l’application. Afin de fournir cette fonctionnalité, votre emplacement actuel, votre itinéraire actuellement planifié, les coordonnées du point de cheminement et l’adresse IP de votre appareil doivent être transmis aux services Web à l’adresse Aviation Weather Centre. La connaissance de l’adresse IP est nécessaire pour que les services Web répondent. Les services Web ne peuvent pas lire d’autres données de votre appareil au cours du processus. Cependant, vous devez vous attendre à ce que l’adresse IP de votre appareil soit stockée avec les données de position transmises. Les services Web sont exploités par le gouvernement américain et échappent à notre contrôle. Des informations détaillées sur ces services Web sont disponibles sur https://www.aviationweather.gov/dataserver.

  • L’application affiche les NOTAM des lieux proches de votre position actuelle et de votre itinéraire actuellement planifié. Il affiche également les NOTAM pour tous les waypoints que vous ouvrez dans l’application. Afin de fournir cette fonctionnalité, votre emplacement actuel, votre itinéraire actuellement planifié, les coordonnées du point de cheminement et l’adresse IP de votre appareil doivent être transmis aux services Web à l’adresse Federal Aviation Administratif. La connaissance de l’adresse IP est nécessaire pour que les services Web répondent. Les services Web ne peuvent pas lire d’autres données de votre appareil au cours du processus. Cependant, vous devez vous attendre à ce que l’adresse IP de votre appareil soit stockée avec les données de position transmises. Les services Web sont exploités par le gouvernement américain et échappent à notre contrôle. Des informations détaillées sur ces services Web sont disponibles sur https://api.faa.gov/s.

Responsable: Stefan Kebekus, Wintererstraße 77, 79104 Freiburg im Breisgau, Germany

Traduzione italiana

Non elaboriamo alcun dato personale da te. I dati che inserisci nell’app (incluse rotte, waypoint e specifiche del velivolo) vengono memorizzati localmente sul tuo dispositivo. I dati non ci vengono trasmessi e non li elaboriamo.

Tuttavia, per garantire la funzionalità, l’app deve trasmettere i seguenti dati ai server in Internet.

  • L’app controlla regolarmente la presenza di aggiornamenti e consente di scaricare mappe e dati da un server dell’Università di Freiburg sul tuo dispositivo. Per fornire questa funzionalità, l’indirizzo IP del tuo dispositivo deve essere trasmesso al server. La conoscenza dell’indirizzo IP è necessaria affinché il server risponda. Tuttavia, il server non memorizza alcun dato personale su di te nei suoi file di registro. In particolare, non memorizza l’indirizzo IP del tuo dispositivo nei suoi file di registro. Possiamo assicurarlo perché il server è sotto il nostro controllo.

  • L’app mostra METAR e TAF per gli aeroporti vicino alla tua posizione corrente e vicino al tuo percorso attualmente pianificato. Mostra anche METAR e TAF per tutti i waypoint che apri nell’app. Per fornire questa funzionalità, la tua posizione attuale, il tuo percorso attualmente pianificato, le coordinate del waypoint e l’indirizzo IP del tuo dispositivo devono essere trasmessi ai servizi web su Aviation Weather Centro. La conoscenza dell’indirizzo IP è necessaria affinché i servizi Web possano rispondere. I servizi Web non possono leggere altri dati dal tuo dispositivo durante il processo. Tuttavia, devi aspettarti che l’indirizzo IP del tuo dispositivo venga memorizzato insieme ai dati sulla posizione trasmessi. I servizi Web sono gestiti dal governo degli Stati Uniti e sono al di fuori del nostro controllo. Informazioni dettagliate su questi servizi Web sono disponibili all’indirizzo https://www.aviationweather.gov/dataserver.

  • L’app mostra i NOTAM per i luoghi vicini alla posizione corrente e al percorso attualmente pianificato. Mostra anche i NOTAM per tutti i waypoint che apri nell’app. Per fornire questa funzionalità, la tua posizione attuale, il tuo percorso attualmente pianificato, le coordinate del waypoint e l’indirizzo IP del tuo dispositivo devono essere trasmessi ai servizi web all’Federal Aviation Amministrazione. La conoscenza dell’indirizzo IP è necessaria affinché i servizi Web possano rispondere. I servizi Web non possono leggere altri dati dal tuo dispositivo durante il processo. Tuttavia, devi aspettarti che l’indirizzo IP del tuo dispositivo venga memorizzato insieme ai dati sulla posizione trasmessi. I servizi Web sono gestiti dal governo degli Stati Uniti e sono al di fuori del nostro controllo. Informazioni dettagliate su questi servizi Web sono disponibili all’indirizzo https://api.faa.gov/s.

Responsabile: Stefan Kebekus, Wintererstraße 77, 79104 Freiburg im Breisgau, Germany

Polskie tłumaczenie

Nie przetwarzamy żadnych danych osobowych użytkownika. Dane wprowadzane do aplikacji (w tym trasy, punkty trasy i dane samolotu) są przechowywane lokalnie na urządzeniu użytkownika. Dane te nie są przesyłane do nas i nie są przez nas przetwarzane.

Aby jednak zapewnić funkcjonalność, aplikacja musi przesyłać następujące dane do serwerów w Internecie.

  • Aplikacja regularnie sprawdza dostępność aktualizacji i umożliwia pobieranie map i danych z serwera Uniwersytetu we Fryburgu na urządzenie użytkownika. Aby zapewnić tę funkcję, adres IP urządzenia musi zostać przesłany do serwera. Znajomość adresu IP jest konieczna, aby serwer mógł odpowiedzieć. Serwer nie przechowuje jednak żadnych danych osobowych użytkownika w swoich plikach dziennika. W szczególności nie przechowuje adresu IP urządzenia użytkownika w swoich plikach dziennika. Możemy to zapewnić, ponieważ serwer jest pod naszą kontrolą.

  • Aplikacja pokazuje komunikaty METAR i TAF dla lotnisk znajdujących się w pobliżu Twojej aktualnej lokalizacji oraz aktualnie planowanej trasy. Pokazuje również komunikaty METAR i TAF dla wszystkich punktów trasy, które otworzysz w aplikacji. Aby zapewnić tę funkcję, Twoja bieżąca lokalizacja, aktualnie zaplanowana trasa, współrzędne punktu nawigacyjnego i adres IP Twojego urządzenia muszą zostać przesłane do usług sieciowych pod adresem Centrum pogody lotniczej. Znajomość adresu IP jest niezbędna, aby usługi sieciowe mogły odpowiedzieć. Usługi sieciowe nie mogą w tym czasie odczytywać żadnych innych danych z urządzenia. Musisz jednak liczyć się z tym, że adres IP Twojego urządzenia będzie przechowywany razem z przesyłanymi danymi o pozycji. Usługi internetowe są obsługiwane przez rząd Stanów Zjednoczonych i są poza naszą kontrolą. Szczegółowe informacje na temat tych usług internetowych można znaleźć na stronie https://www.aviationweather.gov/dataserver.

  • Aplikacja wyświetla NOTAMy dla miejsc w pobliżu Twojej aktualnej lokalizacji oraz w pobliżu aktualnie planowanej trasy. Pokazuje również NOTAMy dla wszystkich punktów trasy, które otwierasz w aplikacji. Aby zapewnić tę funkcję, Twoja bieżąca lokalizacja, aktualnie zaplanowana trasa, współrzędne punktu nawigacyjnego i adres IP Twojego urządzenia muszą zostać przesłane do usług sieciowych w Federalna administracja lotnicza. Znajomość adresu IP jest niezbędna, aby usługi sieciowe mogły odpowiedzieć. Usługi sieciowe nie mogą w tym czasie odczytywać żadnych innych danych z urządzenia. Musisz jednak liczyć się z tym, że adres IP Twojego urządzenia będzie przechowywany wraz z przesyłanymi danymi o pozycji. Usługi internetowe są obsługiwane przez rząd Stanów Zjednoczonych i są poza naszą kontrolą. Szczegółowe informacje o tych usługach internetowych można znaleźć na stronie https://api.faa.gov/s.

Odpowiedzialny: Stefan Kebekus, Wintererstraße 77, 79104 Freiburg im Breisgau, Germany

Traducción al español

No procesamos ningún dato personal suyo. Los datos que ingresa en la aplicación (incluidas las rutas, los waypoints y los detalles de la aeronave) se almacenan localmente en su dispositivo. Los datos no se transmiten a nosotros y no son procesados por nosotros.

Sin embargo, para garantizar la funcionalidad, la aplicación debe transmitir los siguientes datos a los servidores en Internet.

  • La aplicación comprueba periódicamente si hay actualizaciones y permite descargar mapas y datos desde un servidor de la Universidad de Friburgo ` <https://cplx.vm.uni-freiburg.de/storage>`__ a su dispositivo. Para proporcionar esta funcionalidad, la dirección IP de su dispositivo debe transmitirse al servidor. El conocimiento de la dirección IP es necesario para que el servidor responda. Sin embargo, el servidor no almacena ningún dato personal sobre usted en sus archivos de registro. En particular, no almacena la dirección IP de su dispositivo en sus archivos de registro. Podemos asegurar esto porque el servidor está bajo nuestro control.

  • La aplicación muestra METAR y TAF para aeródromos cerca de su ubicación actual y cerca de su ruta planificada actualmente. También muestra METAR y TAF para todos los waypoints que abra en la aplicación. Para proporcionar esta funcionalidad, su ubicación actual, su ruta planificada actualmente, las coordenadas de los puntos intermedios y la dirección IP de su dispositivo deben transmitirse a los servicios web en Aviation Weather Centro. El conocimiento de la dirección IP es necesario para que los servicios web respondan. Los servicios web no pueden leer ningún otro dato de su dispositivo en el proceso. Sin embargo, debe esperar que la dirección IP de su dispositivo se almacene junto con los datos de posición transmitidos. Los servicios web son operados por el gobierno de los EE. UU. y están fuera de nuestro control. Puede encontrar información detallada sobre estos servicios web en https://www.aviationweather.gov/dataserver.

  • La aplicación muestra NOTAM para lugares cercanos a su ubicación actual y cerca de su ruta planificada actualmente. También muestra los NOTAM de todos los waypoints que abra en la aplicación. Para proporcionar esta funcionalidad, su ubicación actual, su ruta planificada actualmente, las coordenadas de los puntos intermedios y la dirección IP de su dispositivo deben transmitirse a los servicios web en Federal Aviation Administración. El conocimiento de la dirección IP es necesario para que los servicios web respondan. Los servicios web no pueden leer ningún otro dato de su dispositivo en el proceso. Sin embargo, debe esperar que la dirección IP de su dispositivo se almacene junto con los datos de posición transmitidos. Los servicios web son operados por el gobierno de los EE. UU. y están fuera de nuestro control. Puede encontrar información detallada sobre estos servicios web en https://api.faa.gov/s.

Responsable: Stefan Kebekus, Wintererstraße 77, 79104 Freiburg im Breisgau, Germany

\ No newline at end of file diff --git a/docs/manual/04-appendix/technical.html b/docs/manual/04-appendix/technical.html index 44390eb6..a4626c11 100644 --- a/docs/manual/04-appendix/technical.html +++ b/docs/manual/04-appendix/technical.html @@ -1,7 +1,7 @@ - Technical Notes Skip to content

Technical Notes

Traffic Data Receiver support

Communication

Enroute Flight Navigation expects that the traffic receiver deploys a WLAN network via Wi-Fi and publishes traffic data via that network. In order to support a wide range of devices, including flight simulators, the app listens to several network addresses simultaneously and understands a variety of protocols.

Enroute Flight Navigation watches the following data channels, in order of preference.

  • A TCP connection to port 2000 at the IP addresses 192.168.1.1, where the app expects a stream of FLARM/NMEA sentences.

  • A TCP connection to port 2000 at the IP addresses 192.168.10.1, where the app expects a stream of FLARM/NMEA sentences.

  • A UDP connection to port 4000, where the app expects datagrams in GDL90 or XGPS format.

  • A UDP connection to port 49002, where the app expects datagrams in GDL90 or XGPS format.

Enroute Flight Navigation expects traffic data in the following formats.

Known issues with GDL90

The GDL90 protocol has a number of shortcomings, and we recommend to use FLARM/NMEA whenever possible. We are aware of the following issues.

Altitude measurements

According to the GDL90 Specification, the ownship geometric height is reported as height above WGS-84 ellipsoid. There are however many devices on the market that wrongly report height above main sea level. Different apps have different strategies to deal with these shortcomings.

  • Enroute Flight Navigation as well as the app Skydemon expect that traffic receivers comply with the GDL90 Specification.

  • ForeFlight has extended the GDL90 Specification so that traffic receivers can indicate if they comply with the specification or not.

  • Many other apps expect wrong GDL90 implementations and interpret the geometric height has height above main sea level.

MODE-S traffic

Most traffic receivers see traffic equipped with MODE-S transponders and can give an estimate for the distance to the traffic. They are, however, unable to obtain the precise traffic position. Unlike FLARM/NMEA, the GDL90 Specification does not support traffic factors whose position is unknown. Different devices implement different workarounds.

  • Stratux devices generate a ring of eight virtual targets around the own position. These targets are named “Mode S”.

  • Air Avioncs devices do the same, but only with one target.

  • Other devices create a virtual target, either at the ownship position or at the north pole and abuse the field “Navigation Accuracy Category for Position” to give the approximate position to the target.

Enroute Flight Navigation has special provisions for handling targets called “Mode S”, but users should expect that this workaround is not perfect.

ForeFlight Broadcast

Following the standards established by the app ForeFlight, Enroute Flight Navigation broadcasts a UDP message on port 63093 every 5 seconds while the app is running in the foreground. This message allows devices to discover Enroute’s IP address, which can be used as the target of UDP unicast messages. This broadcast will be a JSON message, with at least these fields:

{
+                         Technical Notes                      Skip to content  
  
 
  
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
 
 
Technical Notes
 
 
Traffic Data Receiver support
 
 
Communication
 
Enroute Flight Navigation expects that the traffic receiver deploys a WLAN network via Wi-Fi and publishes traffic data via that network. In order to support a wide range of devices, including flight simulators, the app listens to several network addresses simultaneously and understands a variety of protocols.
 
Enroute Flight Navigation watches the following data channels, in order of preference.
 
     
  • A TCP connection to port 2000 at the IP addresses 192.168.1.1, where the app expects a stream of FLARM/NMEA sentences.
     
  • A TCP connection to port 2000 at the IP addresses 192.168.10.1, where the app expects a stream of FLARM/NMEA sentences.
     
  • A UDP connection to port 4000, where the app expects datagrams in GDL90 or XGPS format.
     
  • A UDP connection to port 49002, where the app expects datagrams in GDL90 or XGPS format.
     
 
Enroute Flight Navigation expects traffic data in the following formats.
  
 
 
Known issues with GDL90
 
The GDL90 protocol has a number of shortcomings, and we recommend to use FLARM/NMEA whenever possible. We are aware of the following issues.
 
 
Altitude measurements
According to the GDL90 Specification, the ownship geometric height is reported as height above WGS-84 ellipsoid. There are however many devices on the market that wrongly report height above main sea level. Different apps have different strategies to deal with these shortcomings.
 
     
  • Enroute Flight Navigation as well as the app Skydemon expect that traffic receivers comply with the GDL90 Specification.
     
  • ForeFlight has extended the GDL90 Specification so that traffic receivers can indicate if they comply with the specification or not.
     
  • Many other apps expect wrong GDL90 implementations and interpret the geometric height has height above main sea level.
     
 
MODE-S traffic
Most traffic receivers see traffic equipped with MODE-S transponders and can give an estimate for the distance to the traffic. They are, however, unable to obtain the precise traffic position. Unlike FLARM/NMEA, the GDL90 Specification does not support traffic factors whose position is unknown. Different devices implement different workarounds.
 
     
  • Stratux devices generate a ring of eight virtual targets around the own position. These targets are named “Mode S”.
     
  • Air Avioncs devices do the same, but only with one target.
     
  • Other devices create a virtual target, either at the ownship position or at the north pole and abuse the field “Navigation Accuracy Category for Position” to give the approximate position to the target.
     
 
Enroute Flight Navigation has special provisions for handling targets called “Mode S”, but users should expect that this workaround is not perfect.
 
 
 
 
ForeFlight Broadcast
 
Following the standards established by the app ForeFlight, Enroute Flight Navigation broadcasts a UDP message on port 63093 every 5 seconds while the app is running in the foreground. This message allows devices to discover Enroute’s IP address, which can be used as the target of UDP unicast messages. This broadcast will be a JSON message, with at least these fields:
 
{
    "App":"Enroute Flight Navigation",
    "GDL90":{
       "port":4000
    }
 }
-
 
 
The GDL90 “port” field is currently 4000, but might change in the future.
 
 
 
Known issues with SkyEcho devices
 
Enroute Flight Navigation works fine with SkyEcho devices. There are, however, several shortcomings that users should be aware of.
 
 
Unidirectional FLARM
The SkyEcho can receive FLARM signals, but cannot send them. The SkyEcho device cannot be seen by other FLARM users. The author of Enroute Flight Navigation is not convinced that unidirectionl FLARM is a good idea.
 
FLARM Output
uAvionix follows an unusual business model. The FLARM/NMEA output of the SkyEcho is encrypted. To read the FLARM data, all apps need to include commercial, closed-source decryption libraries that must be purchased by the app users. The author of Enroute Flight Navigation feels that this is incompatible with the idea of free, open source software.
 
To communicate with SkyEcho devices, Enroute Flight Navigation will switch to the GDL90 protocol.
 
Altimeter readings
SkyEcho includes an integrated barometric altimeter, but does not have any access to static pressure. To estimate the barometric altitude, the SkyEcho correlates cabin pressure altitude to altitudes of nearby traffic. The author of Enroute Flight Navigation is not convinced that this method gives altimeter readings that are sufficiently reliable for aviation purposes.
 
 
 
 
Known issues with pingUSB devices
 
Enroute Flight Navigation works fine with pingUSB devices. There are, however, several shortcomings that users should be aware of.
 
 
Unidirectional ADS-B
The pingUSB can receive ADS-B signals, but cannot send them. The pingUSB device cannot be seen by other ADS-B users. The author of Enroute Flight Navigation is not convinced that unidirectional ADS-B is a good idea.
 
Altimeter readings
pingUSB reports the barometric altitude of traffic opponents, but does not include a static pressure sensor required to measure the barometric altitude of the own aircraft. As a result, Enroute Flight Navigation cannot compute the relative height between the traffic and the own aircraft. The author of Enroute Flight Navigation is aware of apps that compare the barometric altitude of traffic to the geometric altitude of the own aircraft (which can be measured via GPS), and hence show misleading traffic information. The author is not convinced that pingUSB should be used for aviation purposes.
 
 
 
 
 
 
 
 
 
   
\ No newline at end of file
+

The GDL90 “port” field is currently 4000, but might change in the future.

Known issues with SkyEcho devices

Enroute Flight Navigation works fine with SkyEcho devices. There are, however, several shortcomings that users should be aware of.

Unidirectional FLARM

The SkyEcho can receive FLARM signals, but cannot send them. The SkyEcho device cannot be seen by other FLARM users. The author of Enroute Flight Navigation is not convinced that unidirectionl FLARM is a good idea.

FLARM Output

uAvionix follows an unusual business model. The FLARM/NMEA output of the SkyEcho is encrypted. To read the FLARM data, all apps need to include commercial, closed-source decryption libraries that must be purchased by the app users. The author of Enroute Flight Navigation feels that this is incompatible with the idea of free, open source software.

To communicate with SkyEcho devices, Enroute Flight Navigation will switch to the GDL90 protocol.

Altimeter readings

SkyEcho includes an integrated barometric altimeter, but does not have any access to static pressure. To estimate the barometric altitude, the SkyEcho correlates cabin pressure altitude to altitudes of nearby traffic. The author of Enroute Flight Navigation is not convinced that this method gives altimeter readings that are sufficiently reliable for aviation purposes.

Known issues with pingUSB devices

Enroute Flight Navigation works fine with pingUSB devices. There are, however, several shortcomings that users should be aware of.

Unidirectional ADS-B

The pingUSB can receive ADS-B signals, but cannot send them. The pingUSB device cannot be seen by other ADS-B users. The author of Enroute Flight Navigation is not convinced that unidirectional ADS-B is a good idea.

Altimeter readings

pingUSB reports the barometric altitude of traffic opponents, but does not include a static pressure sensor required to measure the barometric altitude of the own aircraft. As a result, Enroute Flight Navigation cannot compute the relative height between the traffic and the own aircraft. The author of Enroute Flight Navigation is aware of apps that compare the barometric altitude of traffic to the geometric altitude of the own aircraft (which can be measured via GPS), and hence show misleading traffic information. The author is not convinced that pingUSB should be used for aviation purposes.

\ No newline at end of file diff --git a/docs/manual/04-appendix/tips.html b/docs/manual/04-appendix/tips.html index 4ee184ef..b78fc6f9 100644 --- a/docs/manual/04-appendix/tips.html +++ b/docs/manual/04-appendix/tips.html @@ -1 +1 @@ - Tips & Tricks Skip to content

Tips & Tricks

Display of recorded satnav tracks

We have been approached by users who recorded a flight and wished to show the recorded flight track in Enroute Flight Navigation, perhaps in order to confirm that they complied with all airspace restrictions. While Enroute Flight Navigation is able to import GPX tracks as a flight route, the program has been designed for flight planning purposes and is limited to tracks of no more than 100 data points. In comparison, typical GPS tracks contains thousands or tens of thousands data points.

One of our users suggested a solution using the mapping and navigation program Osmand, which is open source and available for a range of devices. We reproduce his suggestion below. Please let us know if you are aware of other good solutions!

Before you start

This text assumes that you have installed Osmand on your device, that you have installed maps for your region, and that you know how to import and display a GPS track with Osmand. In order to show aviation data, we are going to add the “open flightmaps” to Osmand as a map overlay. These maps are very complete and well-designed, but cover only select European and African countries. Visit the OFM web site to learn more.

Step 1: Install plugin

As a first step, ensure that the Osmand plugin “Online maps” is enabled. For this, open the main menu and choose “Plugins”. The page “Plugins” will open where the plugin “Online maps” can be selected. Once done, return to the main page.

Step 2: Enable the map overlay

Open the main menu, choose “Configure map” and select “Overlay map…”. Select the slider, which currently shows “Off”. In the dialogue window, choose “OpenFlightMaps” and move the slider for “Overlay transparency” to the right.

Step 3: Enjoy

Finally, open your track of your last flight in Osmand. Look at the track and reassure yourself that you have respectfully circumnavigated all restricted airspaces!

\ No newline at end of file + Tips & Tricks Skip to content

Tips & Tricks

Display of recorded satnav tracks

We have been approached by users who recorded a flight and wished to show the recorded flight track in Enroute Flight Navigation, perhaps in order to confirm that they complied with all airspace restrictions. While Enroute Flight Navigation is able to import GPX tracks as a flight route, the program has been designed for flight planning purposes and is limited to tracks of no more than 100 data points. In comparison, typical GPS tracks contains thousands or tens of thousands data points.

One of our users suggested a solution using the mapping and navigation program Osmand, which is open source and available for a range of devices. We reproduce his suggestion below. Please let us know if you are aware of other good solutions!

Before you start

This text assumes that you have installed Osmand on your device, that you have installed maps for your region, and that you know how to import and display a GPS track with Osmand. In order to show aviation data, we are going to add the “open flightmaps” to Osmand as a map overlay. These maps are very complete and well-designed, but cover only select European and African countries. Visit the OFM web site to learn more.

Step 1: Install plugin

As a first step, ensure that the Osmand plugin “Online maps” is enabled. For this, open the main menu and choose “Plugins”. The page “Plugins” will open where the plugin “Online maps” can be selected. Once done, return to the main page.

Step 2: Enable the map overlay

Open the main menu, choose “Configure map” and select “Overlay map…”. Select the slider, which currently shows “Off”. In the dialogue window, choose “OpenFlightMaps” and move the slider for “Overlay transparency” to the right.

Step 3: Enjoy

Finally, open your track of your last flight in Osmand. Look at the track and reassure yourself that you have respectfully circumnavigated all restricted airspaces!

\ No newline at end of file diff --git a/docs/manual/_sources/04-appendix/authors.rst.txt b/docs/manual/_sources/04-appendix/authors.rst.txt new file mode 100644 index 00000000..ec2ac530 --- /dev/null +++ b/docs/manual/_sources/04-appendix/authors.rst.txt @@ -0,0 +1,41 @@ +Authors +======= +The app **Enroute Flight Navigation** was written by Stefan Kebekus, +flight enthusiast since 1986 and member of the Akaflieg Freiburg flight +club. Stefan flies gliders and motor planes. + +**Address**: Stefan Kebekus, Wintererstraße 77, 79104 Freiburg, Germany +· stefan.kebekus@gmail.com + +Contributions +~~~~~~~~~~~~~ + +**iOS Version** The app has been ported to iOS by Simon Schneider. Simon +is currently student pilot (PPL) and member of the Akaflieg Freiburg +flight club, just like Stefan. + +**Programming** Heinz Blöchinger has helped us with OpenAir support. +After 15 years of alpine gliding, Heinz has fulfilled a big dream and +now flies helicopters. + +Translations +~~~~~~~~~~~~ + +- **French:** Adrien Crovato and Luca Riva. Both are private pilots and + aerospace engineers. Luca is also doing aerobatics. +- **German:** Markus Sachs. Markus flies trikes and is an enthusiastic + 'Co' on everyting else that flies. +- **Italian:** Ivan Battistella and Antonio Fardella. Antonio is a + naval aviator with a passion for everything challenging. +- **Polish:** Sławek Mikuła. +- **Spanish:** Luca Riva. + +Alumni +~~~~~~ + +- Luca Bertoncello (Italian translation) +- Adrien Crovato (Integration of weather information) +- Michael Horbaschk (Manual) +- Szymon Kocur (Polish translation) +- Heiner Tholen (User interface) +- Johannes Zellner (Geoid correction for altitude) diff --git a/docs/manual/_sources/04-appendix/privacy.rst.txt b/docs/manual/_sources/04-appendix/privacy.rst.txt index a65ba9be..4047545b 100644 --- a/docs/manual/_sources/04-appendix/privacy.rst.txt +++ b/docs/manual/_sources/04-appendix/privacy.rst.txt @@ -1,51 +1,333 @@ - -Privacy policies +Privacy Policies ================ -We do not process any personal data from you. Data that you enter into the app -(including routes, waypoints, and aircraft specifics) is stored locally on your -device, is not transmitted to us, and is not processed by us. - -However, to ensure the functionality, the app must transmit following data to -servers on the internet. - -- The app regularly checks for updates and allows downloading maps and data from - a `server at the University of Freiburg - `_ to your device. In order to - provide this functionality, your device's IP address must be transmitted to - the server. Knowledge of the IP address is necessary for the server to - respond. However, the server does not store any personal data about you in its - log files. In particular, it does not store the IP address of your device in - its log files. We can assure this because the server is under our control. - -- The app shows METARs and TAFs for airfields near your current location and - near your currently planned route. It also shows METARs and TAFs for all - waypoints that you open in the app. In order to provide this functionality, - your current location, your currently planned route, waypoint coordinates, and - your device's IP address must be transmitted to web services at the `Aviation - Weather Center `_. Knowledge of the IP - address is necessary for the web services to respond. The web services cannot - read any other data from your device in the process. However, you must expect - that your device's IP address will be stored together with the transmitted - position data. The web services are operated by the US government and are - beyond our control. Detailed information about these web services can be found - at https://www.aviationweather.gov/dataserver. - -- The app shows NOTAMs for places near your current location and near your - currently planned route. It also shows NOTAMs for all waypoints that you open - in the app. In order to provide this functionality, your current location, - your currently planned route, waypoint coordinates, and your device's IP - address must be transmitted to web services at the `Federal Aviation - Administration `_. Knowledge of the IP address is - necessary for the web services to respond. The web services cannot read any - other data from your device in the process. However, you must expect that the - IP address of your device will be stored together with the transmitted - position data. The web services are operated by the US government and are - beyond our control. Detailed information about these web services can be found - at https://api.faa.gov/s. - - -Responsible ------------ - -Stefan Kebekus, Wintererstraße 77, 79104 Freiburg im Breisgau, Germany +English +------- + +We do not process any personal data from you. Data that you enter into +the app (including routes, waypoints, and aircraft specifics) is stored +locally on your device. The data not transmitted to us and is not +processed by us. + +However, to ensure the functionality, the app must transmit following +data to servers on the internet. + +- The app regularly checks for updates and allows downloading maps and + data from a `server at the University of + Freiburg `__ to your device. + In order to provide this functionality, your device's IP address must + be transmitted to the server. Knowledge of the IP address is + necessary for the server to respond. However, the server does not + store any personal data about you in its log files. In particular, it + does not store the IP address of your device in its log files. We can + assure this because the server is under our control. +- The app shows METARs and TAFs for airfields near your current + location and near your currently planned route. It also shows METARs + and TAFs for all waypoints that you open in the app. In order to + provide this functionality, your current location, your currently + planned route, waypoint coordinates, and your device's IP address + must be transmitted to web services at the `Aviation Weather + Center `__. Knowledge of the IP + address is necessary for the web services to respond. The web + services cannot read any other data from your device in the process. + However, you must expect that your device's IP address will be stored + together with the transmitted position data. The web services are + operated by the US government and are beyond our control. Detailed + information about these web services can be found at + https://www.aviationweather.gov/dataserver. +- The app shows NOTAMs for places near your current location and near + your currently planned route. It also shows NOTAMs for all waypoints + that you open in the app. In order to provide this functionality, + your current location, your currently planned route, waypoint + coordinates, and your device's IP address must be transmitted to web + services at the `Federal Aviation + Administration `__. Knowledge of the IP address + is necessary for the web services to respond. The web services cannot + read any other data from your device in the process. However, you + must expect that the IP address of your device will be stored + together with the transmitted position data. The web services are + operated by the US government and are beyond our control. Detailed + information about these web services can be found at + https://api.faa.gov/s. + +**Responsible:** Stefan Kebekus, Wintererstraße 77, 79104 Freiburg im +Breisgau, Germany + +Deutsche Übersetzung +-------------------- + +Wir verarbeiten keine personenbezogenen Daten von Ihnen. Daten, die Sie +in dieser App eingeben (wie zum Beispiel Routen, Wegpunkte und +Luftfahrzeugdaten), werden nur lokal auf dem Gerät abgelegt. Die Daten +werden nicht an uns übermittelt und nicht von uns verarbeitet. + +Um die Funktionalität der App gewährleisten zu können müssen allerdings +folgende Daten an Server im Internet übermittelt werden. + +- Die App sucht regelmäßig nach Updates und bietet die Möglichkeit, + Karten und Daten von einem `Server der Universität + Freiburg `__ auf Ihr Gerät + herunterzuladen. Um diese Funktionalität anzubieten, muss die + IP-Adresse ihres Geräts an den Server übertragen werden. Der Server + benötigt die IP-Adresse, um ihrem Gerät zu antworten. Der Server + speichert aber keine personenbezogenen Daten von Ihnen in den + Loggdateien. Dies gilt insbesondere für die IP-Adresse Ihres Geräts. + Wir können dies zusichern, weil sich der Server unter unserer + Kontrolle befindet. +- Die App zeigt Ihnen METARs und TAFs für Landeplätze nahe Ihrem + aktuellen Standort und Ihrer geplanten Route an. Die App zeigt + zusätzlich METARs und TAFs für alle Wegpunkte an, die Sie in der App + öffnen. Um diese Funktionalität anzubieten, muss die App Ihren + aktuellen Standort, Ihre geplante Route, Wegpunktkoordinaten und die + IP-Adresse Ihres Geräts an Webservices des `Aviation Weather + Center `__ übermitteln. Die + Webservices benötigen die IP-Adresse, um ihrem Gerät zu antworten. + Die Webservices können keine weiteren Daten Ihres Gerätes auslesen. + Allerdings müssen Sie damit rechnen, dass die IP-Adresse Ihres + Gerätes zusammen mit den übermittelten Positionsdaten gespeichert + wird. Die Webservices werden von der US-Regierung betrieben und + entziehen sich unserer Kontrolle. Detaillierte Informationen zu den + Webservices finden Sie unter + https://www.aviationweather.gov/dataserver. +- Die App zeigt Ihnen NOTAMs für Orte nahe Ihres aktuellen Standorts + und Ihrer aktuell geplante Route an. Die App zeigt zusätzlich NOTAMs + für alle Wegpunkte an, die Sie in der App öffnen. Um diese + Funktionalität anzubieten, muss die App Ihren aktuellen Standort, + Ihre aktuell geplante Route, Wegpunktkoordinaten und die IP-Adresse + Ihres Geräts an Webservices der `Federal Aviation + Administration `__ übermitteln. Die Webservices + benötigen die IP-Adresse, um ihrem Gerät zu antworten. Die + Webservices können keine weiteren Daten Ihres Gerätes auslesen. + Allerdings müssen Sie damit rechnen, dass die IP-Adresse Ihres + Gerätes zusammen mit den übermittelten Positionsdaten gespeichert + wird. Die Webservices werden von der US-Regierung betrieben und + entziehen sich unserer Kontrolle. Detaillierte Informationen zu den + Webservices finden Sie unter https://api.faa.gov/s. + +**Verantwortlich:** Stefan Kebekus, Wintererstraße 77, 79104 Freiburg im +Breisgau, Germany + +Traduction en français +---------------------- + +Nous ne traitons aucune donnée personnelle vous concernant. Les données +que vous entrez dans l'application (y compris les itinéraires, les +waypoints et les spécificités de l'avion) sont stockées localement sur +votre appareil. Les données ne nous sont pas transmises et ne sont pas +traitées par nous. + +Cependant, pour assurer la fonctionnalité, l'application doit +transmettre les données suivantes aux serveurs sur Internet. + +- L'application vérifie régulièrement les mises à jour et permet de + télécharger des cartes et des données depuis un `serveur de + l'Université de Fribourg `__ + sur votre appareil. Afin de fournir cette fonctionnalité, l'adresse + IP de votre appareil doit être transmise au serveur. La connaissance + de l'adresse IP est nécessaire pour que le serveur réponde. + Cependant, le serveur ne stocke aucune donnée personnelle vous + concernant dans ses fichiers journaux. En particulier, il ne stocke + pas l'adresse IP de votre appareil dans ses fichiers journaux. Nous + pouvons l'assurer car le serveur est sous notre contrôle. +- L'application affiche les METAR et les TAF pour les aérodromes à + proximité de votre position actuelle et à proximité de votre + itinéraire actuellement planifié. Il affiche également les METAR et + les TAF pour tous les waypoints que vous ouvrez dans l'application. + Afin de fournir cette fonctionnalité, votre emplacement actuel, votre + itinéraire actuellement planifié, les coordonnées du point de + cheminement et l'adresse IP de votre appareil doivent être transmis + aux services Web à l'adresse `Aviation Weather + Centre `__. La connaissance de + l'adresse IP est nécessaire pour que les services Web répondent. Les + services Web ne peuvent pas lire d'autres données de votre appareil + au cours du processus. Cependant, vous devez vous attendre à ce que + l'adresse IP de votre appareil soit stockée avec les données de + position transmises. Les services Web sont exploités par le + gouvernement américain et échappent à notre contrôle. Des + informations détaillées sur ces services Web sont disponibles sur + https://www.aviationweather.gov/dataserver. +- L'application affiche les NOTAM des lieux proches de votre position + actuelle et de votre itinéraire actuellement planifié. Il affiche + également les NOTAM pour tous les waypoints que vous ouvrez dans + l'application. Afin de fournir cette fonctionnalité, votre + emplacement actuel, votre itinéraire actuellement planifié, les + coordonnées du point de cheminement et l'adresse IP de votre appareil + doivent être transmis aux services Web à l'adresse `Federal Aviation + Administratif `__. La connaissance de l'adresse + IP est nécessaire pour que les services Web répondent. Les services + Web ne peuvent pas lire d'autres données de votre appareil au cours + du processus. Cependant, vous devez vous attendre à ce que l'adresse + IP de votre appareil soit stockée avec les données de position + transmises. Les services Web sont exploités par le gouvernement + américain et échappent à notre contrôle. Des informations détaillées + sur ces services Web sont disponibles sur https://api.faa.gov/s. + +**Responsable:** Stefan Kebekus, Wintererstraße 77, 79104 Freiburg im +Breisgau, Germany + +Traduzione italiana +------------------- + +Non elaboriamo alcun dato personale da te. I dati che inserisci nell'app +(incluse rotte, waypoint e specifiche del velivolo) vengono memorizzati +localmente sul tuo dispositivo. I dati non ci vengono trasmessi e non li +elaboriamo. + +Tuttavia, per garantire la funzionalità, l'app deve trasmettere i +seguenti dati ai server in Internet. + +- L'app controlla regolarmente la presenza di aggiornamenti e consente + di scaricare mappe e dati da un `server dell'Università di + Freiburg `__ sul tuo + dispositivo. Per fornire questa funzionalità, l'indirizzo IP del tuo + dispositivo deve essere trasmesso al server. La conoscenza + dell'indirizzo IP è necessaria affinché il server risponda. Tuttavia, + il server non memorizza alcun dato personale su di te nei suoi file + di registro. In particolare, non memorizza l'indirizzo IP del tuo + dispositivo nei suoi file di registro. Possiamo assicurarlo perché il + server è sotto il nostro controllo. +- L'app mostra METAR e TAF per gli aeroporti vicino alla tua posizione + corrente e vicino al tuo percorso attualmente pianificato. Mostra + anche METAR e TAF per tutti i waypoint che apri nell'app. Per fornire + questa funzionalità, la tua posizione attuale, il tuo percorso + attualmente pianificato, le coordinate del waypoint e l'indirizzo IP + del tuo dispositivo devono essere trasmessi ai servizi web su + `Aviation Weather Centro `__. La + conoscenza dell'indirizzo IP è necessaria affinché i servizi Web + possano rispondere. I servizi Web non possono leggere altri dati dal + tuo dispositivo durante il processo. Tuttavia, devi aspettarti che + l'indirizzo IP del tuo dispositivo venga memorizzato insieme ai dati + sulla posizione trasmessi. I servizi Web sono gestiti dal governo + degli Stati Uniti e sono al di fuori del nostro controllo. + Informazioni dettagliate su questi servizi Web sono disponibili + all'indirizzo https://www.aviationweather.gov/dataserver. +- L'app mostra i NOTAM per i luoghi vicini alla posizione corrente e al + percorso attualmente pianificato. Mostra anche i NOTAM per tutti i + waypoint che apri nell'app. Per fornire questa funzionalità, la tua + posizione attuale, il tuo percorso attualmente pianificato, le + coordinate del waypoint e l'indirizzo IP del tuo dispositivo devono + essere trasmessi ai servizi web all'`Federal Aviation + Amministrazione `__. La conoscenza + dell'indirizzo IP è necessaria affinché i servizi Web possano + rispondere. I servizi Web non possono leggere altri dati dal tuo + dispositivo durante il processo. Tuttavia, devi aspettarti che + l'indirizzo IP del tuo dispositivo venga memorizzato insieme ai dati + sulla posizione trasmessi. I servizi Web sono gestiti dal governo + degli Stati Uniti e sono al di fuori del nostro controllo. + Informazioni dettagliate su questi servizi Web sono disponibili + all'indirizzo https://api.faa.gov/s. + +**Responsabile:** Stefan Kebekus, Wintererstraße 77, 79104 Freiburg im +Breisgau, Germany + +Polskie tłumaczenie +------------------- + +Nie przetwarzamy żadnych danych osobowych użytkownika. Dane wprowadzane +do aplikacji (w tym trasy, punkty trasy i dane samolotu) są +przechowywane lokalnie na urządzeniu użytkownika. Dane te nie są +przesyłane do nas i nie są przez nas przetwarzane. + +Aby jednak zapewnić funkcjonalność, aplikacja musi przesyłać następujące +dane do serwerów w Internecie. + +- Aplikacja regularnie sprawdza dostępność aktualizacji i umożliwia + pobieranie map i danych z `serwera Uniwersytetu we + Fryburgu `__ na urządzenie + użytkownika. Aby zapewnić tę funkcję, adres IP urządzenia musi zostać + przesłany do serwera. Znajomość adresu IP jest konieczna, aby serwer + mógł odpowiedzieć. Serwer nie przechowuje jednak żadnych danych + osobowych użytkownika w swoich plikach dziennika. W szczególności nie + przechowuje adresu IP urządzenia użytkownika w swoich plikach + dziennika. Możemy to zapewnić, ponieważ serwer jest pod naszą + kontrolą. +- Aplikacja pokazuje komunikaty METAR i TAF dla lotnisk znajdujących + się w pobliżu Twojej aktualnej lokalizacji oraz aktualnie planowanej + trasy. Pokazuje również komunikaty METAR i TAF dla wszystkich punktów + trasy, które otworzysz w aplikacji. Aby zapewnić tę funkcję, Twoja + bieżąca lokalizacja, aktualnie zaplanowana trasa, współrzędne punktu + nawigacyjnego i adres IP Twojego urządzenia muszą zostać przesłane do + usług sieciowych pod adresem `Centrum pogody + lotniczej `__. Znajomość adresu IP + jest niezbędna, aby usługi sieciowe mogły odpowiedzieć. Usługi + sieciowe nie mogą w tym czasie odczytywać żadnych innych danych z + urządzenia. Musisz jednak liczyć się z tym, że adres IP Twojego + urządzenia będzie przechowywany razem z przesyłanymi danymi o + pozycji. Usługi internetowe są obsługiwane przez rząd Stanów + Zjednoczonych i są poza naszą kontrolą. Szczegółowe informacje na + temat tych usług internetowych można znaleźć na stronie + https://www.aviationweather.gov/dataserver. +- Aplikacja wyświetla NOTAMy dla miejsc w pobliżu Twojej aktualnej + lokalizacji oraz w pobliżu aktualnie planowanej trasy. Pokazuje + również NOTAMy dla wszystkich punktów trasy, które otwierasz w + aplikacji. Aby zapewnić tę funkcję, Twoja bieżąca lokalizacja, + aktualnie zaplanowana trasa, współrzędne punktu nawigacyjnego i adres + IP Twojego urządzenia muszą zostać przesłane do usług sieciowych w + `Federalna administracja lotnicza `__. Znajomość + adresu IP jest niezbędna, aby usługi sieciowe mogły odpowiedzieć. + Usługi sieciowe nie mogą w tym czasie odczytywać żadnych innych + danych z urządzenia. Musisz jednak liczyć się z tym, że adres IP + Twojego urządzenia będzie przechowywany wraz z przesyłanymi danymi o + pozycji. Usługi internetowe są obsługiwane przez rząd Stanów + Zjednoczonych i są poza naszą kontrolą. Szczegółowe informacje o tych + usługach internetowych można znaleźć na stronie + https://api.faa.gov/s. + +**Odpowiedzialny:** Stefan Kebekus, Wintererstraße 77, 79104 Freiburg im +Breisgau, Germany + +Traducción al español +--------------------- + +No procesamos ningún dato personal suyo. Los datos que ingresa en la +aplicación (incluidas las rutas, los waypoints y los detalles de la +aeronave) se almacenan localmente en su dispositivo. Los datos no se +transmiten a nosotros y no son procesados por nosotros. + +Sin embargo, para garantizar la funcionalidad, la aplicación debe +transmitir los siguientes datos a los servidores en Internet. + +- La aplicación comprueba periódicamente si hay actualizaciones y + permite descargar mapas y datos desde un servidor de la Universidad + de Friburgo ` `__ a su + dispositivo. Para proporcionar esta funcionalidad, la dirección IP de + su dispositivo debe transmitirse al servidor. El conocimiento de la + dirección IP es necesario para que el servidor responda. Sin embargo, + el servidor no almacena ningún dato personal sobre usted en sus + archivos de registro. En particular, no almacena la dirección IP de + su dispositivo en sus archivos de registro. Podemos asegurar esto + porque el servidor está bajo nuestro control. +- La aplicación muestra METAR y TAF para aeródromos cerca de su + ubicación actual y cerca de su ruta planificada actualmente. También + muestra METAR y TAF para todos los waypoints que abra en la + aplicación. Para proporcionar esta funcionalidad, su ubicación + actual, su ruta planificada actualmente, las coordenadas de los + puntos intermedios y la dirección IP de su dispositivo deben + transmitirse a los servicios web en `Aviation Weather + Centro `__. El conocimiento de la + dirección IP es necesario para que los servicios web respondan. Los + servicios web no pueden leer ningún otro dato de su dispositivo en el + proceso. Sin embargo, debe esperar que la dirección IP de su + dispositivo se almacene junto con los datos de posición transmitidos. + Los servicios web son operados por el gobierno de los EE. UU. y están + fuera de nuestro control. Puede encontrar información detallada sobre + estos servicios web en https://www.aviationweather.gov/dataserver. +- La aplicación muestra NOTAM para lugares cercanos a su ubicación + actual y cerca de su ruta planificada actualmente. También muestra + los NOTAM de todos los waypoints que abra en la aplicación. Para + proporcionar esta funcionalidad, su ubicación actual, su ruta + planificada actualmente, las coordenadas de los puntos intermedios y + la dirección IP de su dispositivo deben transmitirse a los servicios + web en `Federal Aviation Administración `__. El + conocimiento de la dirección IP es necesario para que los servicios + web respondan. Los servicios web no pueden leer ningún otro dato de + su dispositivo en el proceso. Sin embargo, debe esperar que la + dirección IP de su dispositivo se almacene junto con los datos de + posición transmitidos. Los servicios web son operados por el gobierno + de los EE. UU. y están fuera de nuestro control. Puede encontrar + información detallada sobre estos servicios web en + https://api.faa.gov/s. + +**Responsable:** Stefan Kebekus, Wintererstraße 77, 79104 Freiburg im +Breisgau, Germany + diff --git a/docs/manual/_sources/index.rst.txt b/docs/manual/_sources/index.rst.txt index df2b5f29..48ff386a 100644 --- a/docs/manual/_sources/index.rst.txt +++ b/docs/manual/_sources/index.rst.txt @@ -112,6 +112,7 @@ Appendix :caption: Appendix :name: sec-appendix + 04-appendix/authors 04-appendix/license_enroute 04-appendix/license_3rdParty 04-appendix/technical diff --git a/docs/manual/_static/pygments.css b/docs/manual/_static/pygments.css index 22617bd0..53526e7a 100644 --- a/docs/manual/_static/pygments.css +++ b/docs/manual/_static/pygments.css @@ -1 +1 @@ -@charset "utf-8";pre{line-height:125%}td.linenos .normal{color:inherit;background-color:transparent;padding-left:5px;padding-right:5px}span.linenos{color:inherit;background-color:transparent;padding-left:5px;padding-right:5px}td.linenos .special{color:#000;background-color:#ffffc0;padding-left:5px;padding-right:5px}span.linenos.special{color:#000;background-color:#ffffc0;padding-left:5px;padding-right:5px}.highlight .hll{background-color:#ffc}.highlight{background:#f8f8f8}.highlight .c{color:#080;font-style:italic}.highlight .err{border:1px solid #F00}.highlight .k{color:#A2F;font-weight:bold}.highlight .o{color:#666}.highlight .ch{color:#080;font-style:italic}.highlight .cm{color:#080;font-style:italic}.highlight .cp{color:#080}.highlight .cpf{color:#080;font-style:italic}.highlight .c1{color:#080;font-style:italic}.highlight .cs{color:#080;font-weight:bold}.highlight .gd{color:#A00000}.highlight .ge{font-style:italic}.highlight .gr{color:#F00}.highlight .gh{color:#000080;font-weight:bold}.highlight .gi{color:#00A000}.highlight .go{color:#888}.highlight .gp{color:#000080;font-weight:bold}.highlight .gs{font-weight:bold}.highlight .gu{color:#800080;font-weight:bold}.highlight .gt{color:#04D}.highlight .kc{color:#A2F;font-weight:bold}.highlight .kd{color:#A2F;font-weight:bold}.highlight .kn{color:#A2F;font-weight:bold}.highlight .kp{color:#A2F}.highlight .kr{color:#A2F;font-weight:bold}.highlight .kt{color:#0B0;font-weight:bold}.highlight .m{color:#666}.highlight .s{color:#B44}.highlight .na{color:#B44}.highlight .nb{color:#A2F}.highlight .nc{color:#00F}.highlight .no{color:#800}.highlight .nd{color:#A2F}.highlight .ni{color:#999;font-weight:bold}.highlight .ne{color:#D2413A;font-weight:bold}.highlight .nf{color:#00A000}.highlight .nl{color:#A0A000}.highlight .nn{color:#00F;font-weight:bold}.highlight .nt{color:#008000;font-weight:bold}.highlight .nv{color:#B8860B}.highlight .ow{color:#A2F;font-weight:bold}.highlight .w{color:#bbb}.highlight .mb{color:#666}.highlight .mf{color:#666}.highlight .mh{color:#666}.highlight .mi{color:#666}.highlight .mo{color:#666}.highlight .sa{color:#B44}.highlight .sb{color:#B44}.highlight .sc{color:#B44}.highlight .dl{color:#B44}.highlight .sd{color:#B44;font-style:italic}.highlight .s2{color:#B44}.highlight .se{color:#B62;font-weight:bold}.highlight .sh{color:#B44}.highlight .si{color:#B68;font-weight:bold}.highlight .sx{color:#008000}.highlight .sr{color:#B68}.highlight .s1{color:#B44}.highlight .ss{color:#B8860B}.highlight .bp{color:#A2F}.highlight .fm{color:#00A000}.highlight .vc{color:#B8860B}.highlight .vg{color:#B8860B}.highlight .vi{color:#B8860B}.highlight .vm{color:#B8860B}.highlight .il{color:#666} \ No newline at end of file +@charset "utf-8";pre{line-height:125%}td.linenos .normal{color:inherit;background-color:transparent;padding-left:5px;padding-right:5px}span.linenos{color:inherit;background-color:transparent;padding-left:5px;padding-right:5px}td.linenos .special{color:#000;background-color:#ffffc0;padding-left:5px;padding-right:5px}span.linenos.special{color:#000;background-color:#ffffc0;padding-left:5px;padding-right:5px}.highlight .hll{background-color:#ffc}.highlight{background:#f8f8f8}.highlight .c{color:#080;font-style:italic}.highlight .err{border:1px solid #F00}.highlight .k{color:#A2F;font-weight:bold}.highlight .o{color:#666}.highlight .ch{color:#080;font-style:italic}.highlight .cm{color:#080;font-style:italic}.highlight .cp{color:#080}.highlight .cpf{color:#080;font-style:italic}.highlight .c1{color:#080;font-style:italic}.highlight .cs{color:#080;font-weight:bold}.highlight .gd{color:#A00000}.highlight .ge{font-style:italic}.highlight .ges{font-weight:bold;font-style:italic}.highlight .gr{color:#F00}.highlight .gh{color:#000080;font-weight:bold}.highlight .gi{color:#00A000}.highlight .go{color:#888}.highlight .gp{color:#000080;font-weight:bold}.highlight .gs{font-weight:bold}.highlight .gu{color:#800080;font-weight:bold}.highlight .gt{color:#04D}.highlight .kc{color:#A2F;font-weight:bold}.highlight .kd{color:#A2F;font-weight:bold}.highlight .kn{color:#A2F;font-weight:bold}.highlight .kp{color:#A2F}.highlight .kr{color:#A2F;font-weight:bold}.highlight .kt{color:#0B0;font-weight:bold}.highlight .m{color:#666}.highlight .s{color:#B44}.highlight .na{color:#B44}.highlight .nb{color:#A2F}.highlight .nc{color:#00F}.highlight .no{color:#800}.highlight .nd{color:#A2F}.highlight .ni{color:#999;font-weight:bold}.highlight .ne{color:#D2413A;font-weight:bold}.highlight .nf{color:#00A000}.highlight .nl{color:#A0A000}.highlight .nn{color:#00F;font-weight:bold}.highlight .nt{color:#008000;font-weight:bold}.highlight .nv{color:#B8860B}.highlight .ow{color:#A2F;font-weight:bold}.highlight .w{color:#bbb}.highlight .mb{color:#666}.highlight .mf{color:#666}.highlight .mh{color:#666}.highlight .mi{color:#666}.highlight .mo{color:#666}.highlight .sa{color:#B44}.highlight .sb{color:#B44}.highlight .sc{color:#B44}.highlight .dl{color:#B44}.highlight .sd{color:#B44;font-style:italic}.highlight .s2{color:#B44}.highlight .se{color:#B62;font-weight:bold}.highlight .sh{color:#B44}.highlight .si{color:#B68;font-weight:bold}.highlight .sx{color:#008000}.highlight .sr{color:#B68}.highlight .s1{color:#B44}.highlight .ss{color:#B8860B}.highlight .bp{color:#A2F}.highlight .fm{color:#00A000}.highlight .vc{color:#B8860B}.highlight .vg{color:#B8860B}.highlight .vi{color:#B8860B}.highlight .vm{color:#B8860B}.highlight .il{color:#666} \ No newline at end of file diff --git a/docs/manual/genindex.html b/docs/manual/genindex.html index 38e279d9..02ede546 100644 --- a/docs/manual/genindex.html +++ b/docs/manual/genindex.html @@ -1 +1 @@ - Index Skip to content

Index

\ No newline at end of file + Index Skip to content

Index

\ No newline at end of file diff --git a/docs/manual/index.html b/docs/manual/index.html index 9ff23053..79f1509a 100644 --- a/docs/manual/index.html +++ b/docs/manual/index.html @@ -1 +1 @@ - Enroute Flight Navigation Skip to content

Enroute Flight Navigation

Introduction

Enroute Flight Navigation is a free flight navigation app for Android and other devices. Designed to be simple, functional and elegant, it takes the stress out of your next flight. The program has been written by flight enthusiasts, as a project of Akaflieg Freiburg, a flight club based in Freiburg, Germany.

Enroute Flight Navigation features a moving map, similar in style to the official ICAO maps. Your current position and your flight path for the next five minutes are marked, and so is your intended flight route. A double tap on the display gives you all the information about airspaces, airfields and navaids – complete with frequencies, codes, elevations and runway information.

The free aeronautical maps can be downloaded for offline use. In addition to airspaces, airfields and navaids, selected maps also show traffic circuits as well as flight procedures for control zones. The maps receive daily updates and cover large parts of the world.

Enroute Flight Navigation includes flight weather data downloaded from the NOAA - Aviation Weather Center.

While Enroute Flight Navigation is no substitute for full-featured flight planning software, it allows you to quickly and easily compute distances, courses and headings, and gives you an estimate for flight time and fuel consumption. If the weather turns bad, the app will show you the closest airfields for landing, complete with distances, directions, runway information and frequencies.

This manual describes program version 2.27.1.

Getting Started

Further Steps

Advanced Use

Reference: Pages

Reference: Other

Appendix

\ No newline at end of file + Enroute Flight Navigation Skip to content

Enroute Flight Navigation

Introduction

Enroute Flight Navigation is a free flight navigation app for Android and other devices. Designed to be simple, functional and elegant, it takes the stress out of your next flight. The program has been written by flight enthusiasts, as a project of Akaflieg Freiburg, a flight club based in Freiburg, Germany.

Enroute Flight Navigation features a moving map, similar in style to the official ICAO maps. Your current position and your flight path for the next five minutes are marked, and so is your intended flight route. A double tap on the display gives you all the information about airspaces, airfields and navaids – complete with frequencies, codes, elevations and runway information.

The free aeronautical maps can be downloaded for offline use. In addition to airspaces, airfields and navaids, selected maps also show traffic circuits as well as flight procedures for control zones. The maps receive daily updates and cover large parts of the world.

Enroute Flight Navigation includes flight weather data downloaded from the NOAA - Aviation Weather Center.

While Enroute Flight Navigation is no substitute for full-featured flight planning software, it allows you to quickly and easily compute distances, courses and headings, and gives you an estimate for flight time and fuel consumption. If the weather turns bad, the app will show you the closest airfields for landing, complete with distances, directions, runway information and frequencies.

This manual describes program version 2.27.1.

Getting Started

Further Steps

Advanced Use

Reference: Pages

Reference: Other

Appendix

\ No newline at end of file diff --git a/docs/manual/objects.inv b/docs/manual/objects.inv index 64b6fe80..bf6bdb22 100644 Binary files a/docs/manual/objects.inv and b/docs/manual/objects.inv differ diff --git a/docs/manual/search.html b/docs/manual/search.html index c0334b3d..787277f5 100644 --- a/docs/manual/search.html +++ b/docs/manual/search.html @@ -1 +1 @@ - Search Skip to content

Search

Please activate JavaScript to enable the search functionality.

\ No newline at end of file + Search Skip to content

Search

Please activate JavaScript to enable the search functionality.

\ No newline at end of file diff --git a/docs/manual/searchindex.js b/docs/manual/searchindex.js index 9a3565af..e8ee986f 100644 --- a/docs/manual/searchindex.js +++ b/docs/manual/searchindex.js @@ -1 +1 @@ -Search.setIndex({"docnames": ["01-intro/01-think", "01-intro/02-installation", "01-intro/03-firstFlight", "02-advanced/airspace", "02-advanced/customMaps", "02-steps/donate", "02-steps/nearby", "02-steps/plan", "02-steps/safesky", "02-steps/simulator", "02-steps/traffic", "02-steps/waypointLibrary", "02-steps/weather", "03-reference/Airspace", "03-reference/about", "03-reference/mainPage", "03-reference/mapData", "03-reference/platform", "03-reference/settings", "04-appendix/license_3rdParty", "04-appendix/license_enroute", "04-appendix/licenses_overview", "04-appendix/privacy", "04-appendix/technical", "04-appendix/tips", "index"], "filenames": ["01-intro/01-think.rst", "01-intro/02-installation.rst", "01-intro/03-firstFlight.rst", "02-advanced/airspace.rst", "02-advanced/customMaps.rst", "02-steps/donate.rst", "02-steps/nearby.rst", "02-steps/plan.rst", "02-steps/safesky.rst", "02-steps/simulator.rst", "02-steps/traffic.rst", "02-steps/waypointLibrary.rst", "02-steps/weather.rst", "03-reference/Airspace.rst", "03-reference/about.rst", "03-reference/mainPage.rst", "03-reference/mapData.rst", "03-reference/platform.rst", "03-reference/settings.rst", "04-appendix/license_3rdParty.rst", "04-appendix/license_enroute.rst", "04-appendix/licenses_overview.rst", "04-appendix/privacy.rst", "04-appendix/technical.rst", "04-appendix/tips.rst", "index.rst"], "titles": ["Think before you fly", "Installation and setup", "Before your first flight", "Import airspace data", "Use your own maps", "Make a donation", "Find nearby waypoints", "Plan a Flight", "Connect to the SafeSky app", "Connect your flight simulator", "Connect to your traffic receiver", "Manage a waypoint library", "Check Weather", "Airspace Display", "About Enroute Flight Navigation", "Main Page and Moving Map", "Map Data", "Platform notes", "Settings Page", "Third party software and data", "Software license", "<no title>", "Privacy policies", "Technical Notes", "Tips & Tricks", "Enroute Flight Navigation"], "terms": {"enrout": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 15, 17, 18, 19, 20, 23, 24], "flight": [0, 1, 3, 4, 5, 6, 8, 10, 11, 12, 13, 15, 16, 17, 18, 19, 20, 23, 24], "i": [0, 1, 2, 4, 5, 7, 8, 9, 10, 11, 12, 13, 15, 16, 17, 18, 20, 22, 23, 24, 25], "free": [0, 1, 4, 9, 19, 20, 21, 23, 25], "product": [0, 17, 20], "ha": [0, 1, 2, 4, 6, 8, 9, 10, 11, 12, 15, 18, 20, 23, 24, 25], "been": [0, 4, 9, 11, 12, 15, 20, 24, 25], "publish": [0, 19, 20, 23], "hope": 0, "might": [0, 1, 4, 7, 9, 10, 11, 12, 15, 17, 18, 19, 23], "us": [0, 1, 2, 3, 5, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 20, 23, 24], "an": [0, 2, 3, 4, 7, 8, 10, 11, 12, 13, 15, 17, 18, 20, 23, 25], "aid": 0, "prudent": 0, "It": [0, 4, 7, 10, 11, 17, 22], "come": [0, 3, 4, 10, 12, 20], "guarante": [0, 16, 20], "mai": [0, 4, 10, 13, 20], "work": [0, 8, 9, 10, 15, 17, 20, 23], "expect": [0, 1, 10, 15, 18, 20, 22, 23], "shown": [0, 2, 9, 11, 12, 13, 15, 17, 18], "wrong": [0, 12, 23], "your": [0, 1, 5, 7, 11, 12, 13, 14, 15, 17, 18, 20, 22, 24, 25], "fail": [0, 18, 20], "thi": [0, 1, 2, 3, 5, 7, 9, 10, 12, 13, 15, 18, 20, 22, 23, 24, 25], "app": [0, 2, 3, 4, 5, 9, 10, 14, 15, 16, 17, 18, 22, 23, 25], "substitut": [0, 25], "proper": [0, 9], "prepar": [0, 7], "good": [0, 23, 24], "pilotag": 0, "ani": [0, 6, 7, 8, 9, 12, 16, 17, 20, 22, 23], "inform": [0, 6, 8, 9, 10, 12, 13, 14, 16, 17, 18, 20, 22, 23, 25], "must": [0, 3, 4, 18, 20, 22, 23], "alwai": [0, 4, 10, 17, 18], "valid": [0, 2, 8, 20], "offici": [0, 4, 12, 20, 25], "airspac": [0, 15, 16, 24, 25], "sourc": [0, 9, 12, 16, 19, 20, 23, 24], "author": [0, 9, 10, 14, 17, 20, 23], "mean": [0, 2, 15, 20], "The": [0, 1, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25], "non": [0, 5, 20], "certifi": 0, "devic": [0, 1, 2, 7, 9, 10, 11, 15, 17, 18, 20, 22, 24, 25], "like": [0, 2, 3, 4, 7, 9, 10, 12, 15, 17, 18, 20], "primari": [0, 9], "caus": [0, 20], "accid": 0, "lead": [0, 10], "loss": [0, 10, 20], "live": [0, 10, 17], "we": [0, 1, 2, 4, 7, 10, 16, 18, 20, 22, 23, 24], "do": [0, 2, 3, 4, 5, 7, 12, 16, 17, 18, 20, 22, 23], "believ": [0, 17, 20], "fulfil": [0, 20], "requir": [0, 8, 9, 10, 13, 16, 18, 20, 23], "eu": [0, 16], "regul": [0, 18], "No": [0, 15, 20], "923": 0, "2012": 0, "sera": 0, "2010": 0, "begin": [0, 18], "pilot": [0, 2, 8, 17, 18], "command": [0, 20], "aircraft": [0, 2, 8, 9, 10, 13, 15, 18, 22, 23, 25], "shall": [0, 20], "becom": [0, 4, 7], "familiar": [0, 2], "all": [0, 1, 7, 8, 9, 10, 13, 16, 17, 18, 20, 22, 23, 24, 25], "avail": [0, 1, 2, 3, 4, 12, 13, 15, 16, 18, 20, 24], "appropri": [0, 7, 11, 20], "intend": [0, 7, 12, 20, 25], "To": [0, 4, 7, 8, 9, 10, 11, 12, 14, 15, 17, 18, 20, 23], "put": 0, "simpli": [0, 1, 9], "reli": [0, 17, 19, 20], "most": [0, 2, 3, 4, 7, 10, 11, 15, 16, 17, 18, 20, 23], "illeg": 0, "jurisdict": 0, "certainli": [0, 12], "stupid": 0, "potenti": [0, 15, 18], "suicid": 0, "approv": [0, 12], "wai": [0, 3, 4, 7, 13, 15, 20], "contain": [0, 4, 8, 10, 11, 15, 16, 19, 20, 24], "bug": [0, 9], "includ": [0, 5, 6, 12, 13, 16, 17, 20, 22, 23, 25], "airfield": [0, 3, 6, 7, 10, 11, 12, 15, 16, 22, 25], "ar": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 15, 16, 17, 18, 19, 20, 22, 23, 24, 25], "provid": [0, 4, 9, 12, 16, 17, 18, 20, 22], "without": [0, 1, 17, 20], "certif": [0, 17], "warranti": [0, 20], "doe": [0, 8, 9, 10, 12, 15, 16, 17, 18, 20, 22, 23], "from": [0, 2, 4, 6, 7, 8, 9, 10, 11, 12, 15, 16, 17, 18, 19, 20, 21, 22, 25], "incomplet": 0, "outdat": [0, 4, 12], "otherwis": [0, 12, 18, 20], "incorrect": 0, "user": [0, 3, 4, 7, 9, 10, 11, 17, 19, 20, 23, 24], "run": [0, 3, 4, 9, 17, 20, 23], "mobil": [0, 1, 18], "phone": [0, 10], "tablet": 0, "comput": [0, 1, 3, 4, 7, 9, 15, 18, 20, 23, 25], "android": [0, 1, 7, 11, 18, 19, 21, 25], "while": [0, 1, 4, 7, 11, 16, 17, 18, 23, 24, 25], "fine": [0, 13, 23], "vast": 0, "major": [0, 10, 20], "pleas": [0, 1, 2, 4, 5, 7, 9, 24], "keep": [0, 20], "follow": [0, 2, 3, 4, 7, 8, 9, 10, 12, 13, 15, 17, 19, 20, 22, 23], "mind": [0, 11], "can": [0, 2, 3, 4, 6, 7, 9, 10, 11, 12, 14, 15, 17, 18, 20, 22, 23, 24, 25], "decid": [0, 17, 18, 20], "time": [0, 2, 4, 5, 7, 8, 9, 10, 12, 13, 15, 17, 18, 19, 20, 21, 25], "termin": [0, 20], "slow": [0, 11], "down": [0, 7, 10, 11, 12], "clear": [0, 20], "resourc": 0, "other": [0, 4, 7, 10, 11, 13, 14, 16, 17, 18, 20, 22, 23, 24], "interfer": 0, "mani": [0, 1, 2, 3, 4, 10, 17, 18, 23], "vendor": 0, "notabl": 0, "One": [0, 24], "plu": [0, 7, 20], "huawei": 0, "samsung": 0, "equip": [0, 15, 23], "batteri": [0, 17], "save": [0, 4, 11, 17], "randomli": 0, "kill": 0, "long": [0, 7, 9, 17, 18, 20], "process": [0, 1, 4, 8, 10, 22], "These": [0, 16, 17, 18, 20, 23, 24], "cannot": [0, 1, 4, 10, 15, 20, 22, 23], "uninstal": 0, "compli": [0, 20, 23, 24], "standard": [0, 2, 3, 4, 9, 10, 15, 18, 20, 23], "often": [0, 4, 9, 10, 15, 17, 18], "extrem": [0, 4, 9, 18], "buggi": [0, 18], "At": [0, 4, 9, 15], "manual": [0, 2, 7, 8, 9, 10, 15, 17, 18, 25], "excempt": 0, "mode": [0, 2, 7, 9, 10, 11, 13, 15, 20, 23], "set": [0, 3, 4, 8, 10, 15, 17, 25], "usual": [0, 10], "lost": 0, "updat": [0, 1, 3, 4, 10, 12, 17, 18, 20, 22, 25], "googl": [0, 1, 7, 11, 17, 19, 21], "": [0, 3, 8, 9, 15, 16, 19, 20, 21, 22, 23], "own": [0, 2, 10, 20, 23, 25], "pixel": 0, "nexu": 0, "have": [0, 2, 4, 5, 7, 8, 9, 12, 15, 17, 18, 20, 23, 24], "problem": [0, 18, 20], "see": [0, 2, 9, 10, 12, 15, 23], "websit": [0, 4, 12], "don": 0, "t": [0, 2, 10, 15], "my": 0, "more": [0, 2, 7, 9, 10, 12, 15, 16, 17, 18, 20, 24], "varieti": [0, 4, 23], "platform": [0, 1, 19, 21, 25], "compar": [0, 18, 23], "consum": [0, 20], "electron": 0, "meet": [0, 20], "design": [0, 2, 11, 13, 18, 19, 20, 21, 24, 25], "continu": [0, 1, 20], "extend": [0, 9, 18, 20, 23], "period": [0, 17, 18], "particular": [0, 4, 20, 22], "displai": [0, 1, 2, 7, 8, 10, 12, 15, 17, 18, 20, 25], "overheat": 0, "catch": 0, "fire": 0, "capac": 0, "even": [0, 9, 13, 18, 20], "connect": [0, 2, 3, 4, 12, 15, 16, 17, 18, 20, 23, 25], "power": [0, 4, 9, 10, 17, 20], "via": [0, 3, 4, 9, 10, 12, 17, 18, 23], "usb": [0, 3, 4], "cabl": 0, "cpu": 0, "energi": 0, "than": [0, 7, 8, 10, 15, 17, 18, 20, 24], "deliv": 0, "navig": [1, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 17, 19, 20, 23, 24], "plai": [1, 2, 17], "store": [1, 22], "linux": [1, 7, 11, 19, 21], "desktop": [1, 7, 9, 11, 15], "machin": [1, 3, 4, 9, 20], "flathub": 1, "org": [1, 10, 20], "depend": [1, 2, 4, 7, 11, 12, 15, 16, 18, 19], "distribut": [1, 3, 19, 20, 21], "you": [1, 2, 3, 4, 5, 6, 7, 11, 12, 15, 17, 18, 20, 22, 24, 25], "also": [1, 4, 7, 9, 10, 13, 15, 16, 17, 20, 22, 25], "find": [1, 11, 18, 20, 25], "softwar": [1, 4, 7, 9, 14, 21, 23, 25], "manag": [1, 3, 4, 25], "applic": [1, 13, 19, 20, 21], "after": [1, 2, 4, 7, 10, 11, 17, 18, 20], "start": [1, 2, 8, 9, 11, 15, 17, 24], "need": [1, 4, 7, 9, 10, 20, 23], "grant": [1, 20], "necessari": [1, 4, 20, 22], "permiss": [1, 12, 19, 20, 21], "ask": [1, 7, 10, 12, 18, 20], "accept": [1, 17, 20], "term": [1, 20], "condit": [1, 9, 10, 12, 18, 20], "geograph": 1, "map": [1, 7, 8, 9, 10, 11, 22, 24, 25], "As": [1, 7, 8, 9, 12, 15, 17, 18, 19, 23, 24], "last": [1, 15, 17, 24], "step": [1, 2, 15, 20, 24], "suggest": [1, 24], "download": [1, 3, 4, 7, 9, 10, 12, 18, 19, 22, 25], "relev": [1, 8, 10, 15, 18, 20], "current": [1, 2, 4, 6, 7, 10, 12, 14, 15, 22, 23, 24, 25], "locat": [1, 4, 9, 12, 13, 22], "onc": [1, 2, 4, 7, 8, 9, 10, 11, 16, 18, 24], "finish": 1, "data": [1, 2, 7, 8, 9, 11, 12, 13, 15, 17, 20, 21, 22, 24, 25], "minut": [1, 2, 10, 15, 16, 25], "so": [1, 2, 10, 11, 15, 16, 20, 23, 25], "recommend": [1, 2, 4, 10, 23], "tell": [1, 17, 20], "littl": [1, 2, 15, 18], "about": [1, 7, 15, 16, 17, 22, 25], "befor": [1, 11, 24, 25], "fly": [1, 7, 8, 10, 12, 13, 15, 18, 25], "open": [1, 2, 3, 4, 6, 8, 9, 10, 12, 13, 14, 15, 16, 17, 18, 19, 21, 22, 23, 24], "menu": [1, 2, 4, 6, 7, 8, 9, 10, 11, 14, 15, 18, 20, 24], "touch": [1, 8, 9, 12, 13, 15], "button": [1, 2, 6, 8, 14, 15, 17], "upper": [1, 7], "right": [1, 7, 9, 11, 12, 16, 20, 24], "side": [1, 9, 10], "screen": [1, 7, 8, 11, 12, 13, 15, 18], "choos": [1, 4, 6, 7, 8, 9, 11, 12, 14, 18, 20, 24], "item": [1, 4, 6, 7, 9, 11, 12, 15, 18, 20], "page": [1, 2, 7, 8, 9, 10, 11, 14, 24], "fill": [1, 4, 13], "everi": [1, 10, 20, 23], "present": [1, 4, 6, 7, 13, 14, 20], "version": [1, 4, 8, 9, 17, 19, 20, 21, 23, 25], "futur": [1, 10, 17, 20, 23], "request": 1, "tap": [1, 2, 7, 9, 11, 15, 18, 25], "click": [1, 2, 4, 5, 6, 7, 11, 15], "arrow": [1, 2, 15], "symbol": [1, 2, 7, 15], "back": [1, 8, 18], "leav": [1, 8, 9, 17, 18], "return": [1, 8, 20, 24], "main": [1, 2, 3, 4, 6, 7, 8, 9, 10, 11, 12, 14, 17, 18, 23, 24, 25], "now": [1, 2], "readi": [1, 2, 20], "go": [1, 4, 7, 8, 10, 11, 18, 24, 25], "There": [1, 2, 3, 4, 7, 10, 23], "thing": [1, 2, 10, 20], "could": [1, 20], "up": [1, 2, 8, 10, 13, 15, 18], "stage": 1, "look": [1, 2, 7, 12, 15, 18, 24], "around": [1, 10, 12, 15, 16, 23], "next": [1, 2, 7, 12, 15, 20, 25], "section": [1, 2, 7, 9, 10, 15, 20], "take": [1, 2, 4, 5, 7, 8, 10, 20, 25], "first": [1, 10, 12, 15, 20, 24, 25], "gener": [2, 4, 9, 10, 13, 16, 17, 19, 20, 21, 23], "oper": [2, 3, 10, 15, 17, 20, 22, 25], "veri": [2, 15, 17, 18, 24], "intuit": 2, "still": [2, 4, 7, 15], "make": [2, 8, 9, 10, 17, 20, 25], "yourself": [2, 7, 20, 24], "basic": [2, 14, 20], "its": [2, 4, 5, 14, 15, 20, 22], "cover": [2, 3, 4, 10, 16, 17, 20, 24, 25], "detail": [2, 4, 6, 7, 8, 9, 10, 12, 15, 16, 20, 22], "startup": 2, "show": [2, 7, 8, 9, 10, 12, 13, 14, 15, 16, 18, 20, 22, 23, 24, 25], "similar": [2, 8, 15, 17, 18, 20, 25], "style": [2, 4, 19, 21, 25], "icao": [2, 4, 7, 12, 13, 15, 25], "gestur": 2, "zoom": [2, 4, 13, 15], "pan": [2, 15], "figur": [2, 9, 10, 15], "ground": [2, 15, 18], "how": [2, 7, 8, 10, 15, 20, 24], "typic": [2, 7, 9, 10, 11, 12, 15, 18, 20, 24], "initi": [2, 7, 20], "posit": [2, 6, 7, 9, 10, 12, 22, 23, 25], "blue": [2, 13], "circl": [2, 10, 13, 15], "grai": 2, "system": [2, 4, 7, 10, 14, 17, 20, 25], "yet": 2, "acquir": [2, 17, 20], "shape": 2, "path": [2, 7, 13, 15, 25], "vector": [2, 4, 15], "project": [2, 4, 5, 15, 16, 19, 21, 25], "track": [2, 15], "five": [2, 15, 25], "size": [2, 4, 12, 15], "each": [2, 7, 15, 20], "black": [2, 13, 15], "white": [2, 12, 15], "segment": [2, 15], "correspond": [2, 15, 20], "one": [2, 3, 4, 7, 9, 10, 15, 17, 18, 20, 23], "when": [2, 7, 8, 9, 12, 13, 15, 17, 18, 20], "probabl": [2, 18], "bright": [2, 18], "red": [2, 7, 12, 13, 15], "lower": 2, "left": [2, 15], "corner": [2, 7], "indic": [2, 10, 13, 15, 20, 23], "traffic": [2, 9, 16, 17, 18, 25], "receiv": [2, 8, 9, 15, 17, 18, 20, 25], "bottom": [2, 7, 14, 15, 18], "panel": [2, 4, 10, 15], "code": [2, 5, 7, 10, 12, 20, 25], "talt": 2, "true": [2, 15, 18], "altitud": [2, 9, 10, 13, 15, 23], "geometr": [2, 9, 15, 23], "abov": [2, 15, 18, 20, 23], "sea": [2, 15, 18, 23], "level": [2, 4, 15, 18, 23], "fl": [2, 15], "g": [2, 15], "speed": [2, 7, 15], "tt": [2, 15], "utc": [2, 15], "onli": [2, 7, 8, 9, 10, 13, 15, 16, 17, 18, 19, 20, 21, 23, 24], "powerflarm": [2, 10, 15], "report": [2, 6, 7, 9, 10, 11, 12, 13, 15, 16, 18, 23], "pressur": [2, 15, 23], "hidden": [2, 15], "wide": [2, 15, 20, 23], "enough": [2, 10, 15], "vertic": [2, 8, 10, 13, 15], "boundari": [2, 13, 15, 18], "defin": [2, 15, 20], "respect": [2, 7, 15, 20], "qnh": [2, 12, 15], "temperatur": [2, 15, 18], "air": [2, 9, 10, 15, 23], "densiti": [2, 15], "differ": [2, 4, 12, 13, 15, 20, 23], "never": [2, 15, 18], "judg": [2, 15], "distanc": [2, 6, 7, 8, 10, 12, 15, 23, 25], "In": [2, 3, 4, 8, 9, 10, 11, 15, 16, 18, 19, 20, 21, 22, 23, 24, 25], "addit": [2, 3, 6, 7, 9, 10, 15, 16, 18, 20, 25], "pinch": [2, 15], "function": [2, 4, 7, 15, 20, 22, 25], "switch": [2, 10, 15, 17, 18, 23], "between": [2, 7, 9, 11, 15, 20, 23], "north": [2, 15, 16, 23], "center": [2, 12, 15, 22, 25], "out": [2, 9, 15, 20, 25], "A": [2, 7, 13, 15, 20, 23, 25], "statu": [2, 8, 9, 10, 15, 20], "doubl": [2, 4, 7, 13, 15, 19, 21, 25], "hold": [2, 7, 11, 15], "anywher": [2, 15, 17], "obtain": [2, 15, 23], "situat": [2, 4, 7, 15], "point": [2, 6, 7, 10, 11, 13, 15, 16, 24], "If": [2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 15, 17, 18, 20, 25], "navaid": [2, 6, 7, 11, 13, 15, 16, 25], "edf": [2, 15], "airport": [2, 12, 13, 15], "simpl": [2, 9, 18, 25], "think": [2, 25], "cours": [2, 15, 25], "further": [2, 5, 7, 9, 20], "aviat": [3, 4, 5, 7, 10, 12, 15, 19, 22, 23, 24, 25], "larg": [3, 4, 25], "part": [3, 4, 20, 25], "world": [3, 4, 16, 25], "frequent": [3, 4, 10, 12], "format": [3, 7, 9, 11, 17, 19, 20, 21, 23], "club": [3, 5, 25], "featur": [3, 4, 7, 8, 15, 16, 18, 20, 25], "member": 3, "highlight": [3, 8, 9, 10], "nois": 3, "sensit": 3, "area": [3, 16, 20], "local": [3, 18, 19, 20, 21, 22], "agreement": [3, 19, 20, 21], "transfer": [3, 4, 7, 9, 11, 20], "web": [3, 4, 9, 10, 22, 23, 24], "browser": [3, 4, 10], "offer": [3, 4, 7, 10, 16, 17, 20], "copi": [3, 4, 20], "afterward": [3, 4], "drag": [3, 4, 7, 11], "drop": [3, 4, 7, 11], "window": [3, 4, 7, 9, 11, 12, 13, 15, 17, 20, 24], "base": [4, 9, 19, 20, 25], "where": [4, 7, 9, 17, 20, 23, 24], "would": [4, 15, 18, 20], "some": [4, 7, 9, 10, 16, 17, 20], "prefer": [4, 7, 9, 11, 17, 18, 20, 23], "chart": [4, 15], "countri": [4, 12, 15, 16, 20, 24], "instal": [4, 7, 9, 10, 15, 18, 19, 20, 24, 25], "high": [4, 13, 16, 18], "region": [4, 16, 18, 24], "interest": [4, 17, 18, 20], "abl": [4, 7, 10, 11, 17, 18, 24], "file": [4, 7, 11, 19, 20, 21, 22], "openmaptil": [4, 19], "schema": 4, "render": [4, 20], "same": [4, 9, 10, 13, 18, 20, 23], "possibl": [4, 7, 11, 17, 20, 23], "along": [4, 12, 13, 20], "order": [4, 9, 10, 12, 18, 20, 22, 23, 24], "higher": [4, 15, 18], "unrespons": 4, "few": [4, 7, 10, 17], "second": [4, 10, 15, 18, 23], "note": [4, 12, 16, 19, 21, 25], "intern": [4, 19, 21], "directori": 4, "space": 4, "delet": [4, 7], "awar": [4, 9, 23, 24], "let": [4, 24], "u": [4, 9, 12, 16, 22, 24], "know": [4, 7, 10, 20, 24], "maptil": 4, "excel": 4, "alongsid": 4, "specif": [4, 7, 17, 19, 20, 21, 22, 23, 25], "flightmap": [4, 16, 19, 24], "european": [4, 16, 24], "well": [4, 9, 10, 12, 20, 23, 24, 25], "south": [4, 16], "africa": [4, 16], "namibia": [4, 16], "handl": [4, 7, 10, 19, 21, 23], "tool": [4, 20], "convert": 4, "denmark": [4, 16], "danish": 4, "aim": [4, 20], "naviair": 4, "spain": [4, 16], "spanish": 4, "insignia": 4, "servicio": 4, "de": [4, 5], "informaci\u00f3n": 4, "aeron\u00e1utica": 4, "switzerland": [4, 16], "swiss": 4, "feder": [4, 22], "offic": 4, "topographi": 4, "swisstopo": 4, "vfr": [4, 12, 18], "unit": [4, 12, 15, 16], "state": [4, 12, 16, 20], "administr": [4, 16, 22], "successfulli": 4, "qgi": 4, "which": [4, 7, 9, 11, 18, 20, 23, 24], "sinc": [4, 18], "easi": 4, "kindli": 4, "short": [4, 17], "tutori": 4, "On": [4, 7, 11, 15], "fedora": 4, "found": [4, 9, 10, 15, 18, 22], "packag": [4, 20], "default": 4, "repositori": [4, 19, 21], "were": [4, 16, 20], "lack": 4, "instruct": [4, 9], "full": [4, 7, 12, 25], "program": [4, 7, 11, 14, 17, 20, 24, 25], "creat": [4, 16, 23], "new": [4, 16, 19, 20, 21], "content": [4, 17, 20], "should": [4, 9, 10, 17, 18, 20, 23], "visibl": [4, 7, 10, 12, 15, 18, 20], "properti": [4, 20], "dialog": [4, 6, 7, 9, 11, 12], "coordin": [4, 7, 11, 22], "refer": [4, 7, 15, 18, 19, 20, 21], "epsg": 4, "3857": 4, "text": [4, 9, 12, 15, 17, 18, 24], "field": [4, 7, 8, 9, 11, 13, 15, 18, 23], "filter": 4, "search": 4, "under": [4, 9, 16, 18, 19, 20, 22], "view": [4, 13, 20], "ensur": [4, 17, 20, 22, 24], "layer": [4, 16, 17], "select": [4, 7, 8, 9, 10, 13, 15, 16, 18, 24, 25], "Then": [4, 8], "resampl": 4, "bilinear": 4, "better": 4, "imag": [4, 7, 15], "qualiti": [4, 16, 20], "toolbox": 4, "insid": [4, 13, 15, 20], "xyz": 4, "tile": [4, 16], "paramet": [4, 9], "seen": [4, 13, 23], "below": [4, 5, 8, 12, 15, 16, 17, 18, 20, 24], "draw": 4, "canva": 4, "specifi": [4, 20, 23], "extent": [4, 15, 20], "pai": 4, "attent": 4, "maximum": 4, "increas": [4, 18], "significantli": 4, "12": [4, 9, 20], "number": [4, 9, 10, 15, 18, 20, 23], "commerci": [5, 8, 9, 20, 23], "akaflieg": [5, 25], "freiburg": [5, 7, 22, 25], "support": [5, 8, 10, 17, 19, 20, 21], "univers": [5, 19, 21, 22], "enthusiast": [5, 25], "written": [5, 13, 20, 25], "spare": [5, 20], "servic": [5, 7, 8, 20, 22], "commun": [5, 6, 7, 9, 13, 17, 20], "develop": [5, 14, 20], "appreci": 5, "consid": [5, 20], "tax": 5, "privileg": 5, "profit": 5, "public": [5, 19, 20, 21], "util": 5, "germani": [5, 16, 22, 25], "promot": 5, "recreat": 5, "sport": 5, "fund": [5, 16], "infrastructur": 5, "deduct": 5, "contact": [5, 9], "info": [5, 7, 9, 14], "statement": [5, 20], "here": [5, 9], "scan": 5, "qr": 5, "iban": 5, "de35": 5, "6809": 5, "0000": 5, "0027": 5, "6409": 5, "07": 5, "bic": 5, "genode61fr1": 5, "volksbank": 5, "messag": [5, 9, 15, 17, 23], "weather": [6, 18, 19, 21, 22, 25], "turn": [6, 25], "bad": [6, 25], "help": [6, 7, 13, 14, 17], "best": [6, 10, 15], "place": [6, 20, 22], "land": [6, 11, 16, 25], "list": [6, 7, 8, 9, 11, 12, 19, 20, 21], "closest": [6, 12, 25], "aerodrom": [6, 13], "togeth": [6, 15, 18, 22], "direct": [6, 7, 15, 20, 25], "runwai": [6, 13, 25], "frequenc": [6, 13, 25], "replac": [6, 17], "rout": [6, 11, 12, 13, 17, 22, 24, 25], "bring": 6, "directli": [6, 7, 20], "close": [6, 8, 10, 15, 20, 23], "apart": 6, "tab": [6, 7, 9, 14], "essenti": [7, 9, 18, 20], "move": [7, 8, 9, 10, 11, 24, 25], "travel": 7, "fuel": [7, 25], "consumpt": [7, 25], "estim": [7, 15, 23, 25], "soon": [7, 8, 9, 12, 15, 17], "magenta": 7, "line": [7, 13, 15], "thin": 7, "infobox": 7, "et": [7, 15], "eta": [7, 15], "final": [7, 15, 20, 24], "box": [7, 8, 9], "airborn": 7, "closer": 7, "three": [7, 10, 11, 20], "nautic": 7, "mile": [7, 12], "destin": [7, 15], "chapter": 7, "through": [7, 17, 20], "cruis": 7, "enter": [7, 9, 20, 22], "piec": [7, 15, 20], "check": [7, 8, 9, 10, 13, 18, 22, 25], "again": 7, "encount": 7, "dure": 7, "want": [7, 20], "sever": [7, 11, 23], "name": [7, 10, 11, 12, 13, 15, 17, 20, 23], "import": [7, 20, 24, 25], "librari": [7, 10, 15, 18, 19, 20, 21, 23, 25], "gpx": [7, 11, 17, 24], "explain": [7, 8, 9, 10, 12, 15, 20], "four": [7, 14], "method": [7, 20, 23], "add": [7, 20, 24], "letter": 7, "edtf": [7, 10, 15], "narrow": 7, "desir": [7, 10], "descript": [7, 11, 15, 17], "sign": 7, "append": 7, "discard": 7, "given": [7, 9, 13, 17, 20], "alreadi": [7, 9, 10, 20], "minu": 7, "remov": [7, 20], "onlin": [7, 10, 24], "fl95": 7, "allow": [7, 9, 11, 12, 18, 20, 22, 23, 25], "bluetooth": [7, 10, 11], "drive": [7, 11], "send": [7, 9, 23], "e": [7, 11, 14, 15, 19, 20, 21], "mail": [7, 11, 14], "channel": [7, 17, 23], "suffic": [7, 20], "perhap": [7, 11, 24], "client": [7, 10, 11], "automat": [7, 9, 10, 15, 18, 20], "global": [7, 16], "dot": [7, 11], "revers": 7, "entir": [7, 20], "pre": 7, "pencil": 7, "happi": 7, "write": [7, 9, 11, 17, 20], "geojson": [7, 11, 17], "understood": [7, 11], "instanc": [7, 11, 19, 21], "top": [7, 11, 12, 15, 17], "type": [7, 8, 11, 15, 17], "submenu": [7, 11], "anti": [8, 19, 20, 21], "collis": [8, 10, 15], "real": [8, 18], "premium": 8, "integr": [8, 10, 23], "nearbi": [8, 10, 12, 15, 23, 25], "factor": [8, 10, 23], "less": [8, 10, 15, 19, 21], "500": [8, 10, 12, 18], "m": [8, 10], "horizont": [8, 10, 15], "20": [8, 10, 16, 20], "nm": [8, 10], "therefor": [8, 17, 18, 20], "substanti": [8, 20], "issu": [8, 10, 15, 18], "warn": [8, 10, 15, 18], "avoid": [8, 10, 11, 15, 20], "algorithm": [8, 10, 15, 19, 21], "configur": [8, 9, 10, 19, 24], "forward": [8, 14], "sure": [8, 9, 10, 20], "subscript": 8, "safe": [8, 10, 18], "sky": 8, "option": [8, 9, 10, 17, 18, 20], "That": 8, "off": [8, 15, 17, 18, 24], "background": 8, "entri": [8, 9, 10, 12, 13, 18], "green": [8, 9, 10, 12, 13, 15], "congratul": [8, 10], "done": [8, 9, 10, 12, 24, 25], "establish": [8, 10, 15, 23], "setup": [9, 25], "correctli": 9, "sent": 9, "wifi": 9, "test": [9, 10, 17], "success": [9, 10], "2": [9, 15, 16, 19, 20, 21, 24, 25], "4": [9, 19, 20, 21], "10": [9, 16, 20, 23], "treat": [9, 20], "assum": [9, 20, 24], "home": 9, "both": [9, 20], "wi": [9, 18, 23], "fi": [9, 18, 23], "network": [9, 20, 23], "deploi": [9, 10, 23], "router": 9, "met": [9, 10, 20], "built": [9, 17, 18], "satnav": [9, 15, 18], "ignor": [9, 17], "two": [9, 10, 15, 20], "call": [9, 20, 23], "guest": 9, "secur": [9, 10, 19, 21], "disallow": [9, 12], "broadcast": [9, 18], "over": [9, 16], "adjust": 9, "accordingli": 9, "end": [9, 13], "miscellan": 9, "activ": [9, 13, 20], "ip": [9, 22, 23], "address": [9, 20, 22, 23], "correct": [9, 20], "our": [9, 16, 20, 22, 24], "though": [9, 20], "socket": 9, "1": [9, 12, 15, 16, 17, 18, 19, 20, 21, 23, 24, 25], "255": 9, "49002": [9, 23], "udp": [9, 23], "foreflight": 9, "xgp": [9, 23], "httpd": 9, "8080": 9, "efb": 9, "connector": 9, "fs2ff": 9, "xmapsi": 9, "inexpens": 9, "barometr": [9, 23], "v3": [9, 19, 20, 21], "expens": 9, "site": [9, 12, 23, 24], "commer": 9, "msfs2020": 9, "cold": 9, "dark": [9, 18], "avion": [9, 10], "04aug21": 9, "tail": 9, "due": 9, "complic": 9, "just": [9, 19, 21], "latest": 9, "releas": [9, 17, 20], "anyth": [9, 20], "ad": [9, 15, 20, 23], "b": [9, 15, 20, 23], "gdl90": [9, 10], "technologi": [9, 10, 17, 23], "simconnect": 9, "ownship": [9, 23], "msl": 9, "verifi": 9, "determin": [9, 20], "except": [9, 16, 20], "experi": [9, 17, 18], "group": [9, 18, 19, 21], "role": 9, "hand": 9, "iphon": 9, "ipad": 9, "extern": 9, "headlin": 9, "datagram": [9, 23], "port": [9, 23], "4000": [9, 23], "choic": [9, 20], "midair": 10, "reason": [10, 20], "happen": 10, "circuit": [10, 13, 15, 16, 25], "enhanc": 10, "flarm": [10, 15, 17, 23], "approach": [10, 13, 15, 18, 24], "what": [10, 20], "downwind": 10, "approxim": [10, 18, 20, 23], "sink": 10, "color": [10, 12, 13, 19, 21], "alarm": [10, 15], "whose": [10, 15, 18, 20, 23], "precis": [10, 15, 20, 23], "unknown": [10, 15, 23], "case": [10, 12, 15, 20], "transpond": [10, 15, 23], "within": [10, 12, 13, 20], "yellow": [10, 12, 15, 18], "danger": [10, 15, 20], "accord": [10, 12, 15, 20, 23], "modern": 10, "compliant": 10, "AT": 10, "core": 10, "ltd": [10, 23], "adaptor": 10, "fusison": 10, "pilotawar": 10, "rosetta": 10, "skyecho2": 10, "known": [10, 15, 18], "skyecho": 10, "pingusb": 10, "stratux": [10, 23], "ttgo": 10, "beam": 10, "concurr": 10, "passeng": 10, "disabl": [10, 11, 18], "board": 10, "For": [10, 11, 13, 16, 19, 20, 21, 24], "result": [10, 20, 23], "nmea": [10, 23], "output": [10, 20, 23], "protocol": [10, 18, 20, 23], "shortcom": [10, 23], "properli": 10, "detect": 10, "whenev": [10, 23], "try": 10, "interfac": [10, 20, 23], "act": 10, "wireless": 10, "access": [10, 12, 14, 18, 20, 23], "ssid": 10, "encrypt": [10, 23], "password": [10, 20], "wait": 10, "internet": [10, 12, 16, 17, 18, 22], "confirm": [10, 24], "wish": [10, 20, 24], "rememb": [10, 18], "break": 10, "serv": [10, 20], "abort": 10, "random": 10, "tri": 10, "friend": 10, "pocket": 10, "databas": [10, 15, 16, 19, 21], "identifi": [10, 12, 13, 20], "registr": 10, "interact": [10, 20, 25], "build": [11, 19], "small": [11, 18], "tourist": 11, "landmark": 11, "hohenzollern": 11, "castl": 11, "emerg": 11, "thousand": [11, 24], "consider": 11, "onto": 11, "assign": 11, "edit": 11, "duplic": 11, "cup": 11, "altern": [11, 20], "metar": [12, 22], "taf": [12, 22], "forecast": 12, "govern": [12, 15, 16, 20, 22], "assess": 12, "meteorolog": [12, 18], "bodi": [12, 15, 20], "station": [12, 13], "85nm": 12, "pictur": 12, "quj": 12, "summari": 12, "classifi": 12, "categori": [12, 23], "scheme": 12, "tabl": [12, 15], "impli": [12, 20], "advis": [12, 20], "legal": [12, 20], "ceil": 12, "low": [12, 15], "ifr": 12, "feet": 12, "agl": [12, 15, 18], "000": [12, 15], "3": [12, 13, 16, 19, 20, 21, 24], "margin": [12, 18], "5": [12, 16, 18, 20, 23], "bear": [12, 15], "decod": 12, "translat": 12, "scroll": 12, "read": [12, 18, 20, 22, 23], "sunset": 12, "sunris": 12, "remain": [12, 15, 20], "until": [12, 20], "privaci": [12, 25], "concern": [12, 17, 20], "common": [13, 19, 20, 21], "symbologi": 13, "structur": 13, "arbitrari": 13, "waypoint": [13, 15, 22, 25], "pop": 13, "techniqu": 13, "limit": [13, 15, 20, 24, 25], "special": [13, 20, 23], "surround": 13, "intens": 13, "dash": 13, "thick": 13, "transpar": [13, 15, 24], "relat": 13, "solid": 13, "class": [13, 16, 19, 20, 21], "d": [13, 20], "atc": 13, "clearanc": 13, "ctr": 13, "tmz": 13, "outlin": [13, 15, 23], "monitor": 13, "squawk": 13, "rmz": 13, "exercis": [13, 20], "pje": 13, "nra": 13, "plan": [13, 15, 22, 24, 25], "exampl": [13, 20], "austria": [13, 16], "rule": [13, 20], "com": 13, "orient": [13, 15], "dimens": 13, "surfac": 13, "elev": [13, 15, 16, 25], "associ": [13, 20], "departur": 13, "triangl": 13, "motor": 13, "glider": [13, 15, 18], "ultralight": 13, "exit": 13, "licens": [14, 16, 19, 21, 25], "share": [14, 20], "word": 15, "autopan": 15, "describ": [15, 25], "behavior": 15, "rotat": 15, "paper": 15, "movement": 15, "tabular": 15, "tc": 15, "dist": 15, "arriv": [15, 17], "chosen": 15, "becaus": [15, 18, 20, 22], "too": [15, 20], "far": 15, "awai": [15, 20], "brief": 15, "error": [15, 17], "Near": 15, "physic": [15, 20], "shade": 15, "terrain": [15, 18], "relief": [15, 16], "overlaid": 15, "valu": [15, 19, 21], "50": 15, "zone": [15, 16, 18, 25], "procedur": [15, 16, 20, 25], "aeronaut": [15, 25], "remind": [15, 18], "9500": 15, "ft": [15, 18], "give": [15, 20, 23, 25], "rough": 15, "scale": [15, 19, 21], "copyright": [15, 16, 20], "notic": [15, 19, 20, 21], "dialogu": [15, 24], "mous": 15, "wheel": 15, "quickest": 15, "equival": [15, 20], "promin": [15, 20], "500m": 15, "20nm": 15, "predict": 15, "13": [15, 20, 23], "18": 15, "kind": [15, 20], "transmitt": 15, "airship": 15, "balloon": 15, "copter": 15, "drone": 15, "hang": 15, "jet": 15, "paraglid": 15, "skydiv": 15, "static": [15, 23], "obstacl": 15, "tow": 15, "plane": [15, 18], "callsign": 15, "rel": [15, 23], "upward": 15, "downward": 15, "sidewai": 15, "alt": 15, "made": [15, 20], "abbrevi": 15, "amsl": [15, 18], "offlin": [16, 25], "streetmap": 16, "deriv": 16, "dataset": 16, "amazon": 16, "aw": 16, "underli": 16, "mix": 16, "3dep": 16, "formerli": 16, "ned": 16, "topobathi": 16, "meter": 16, "outsid": [16, 20], "alaska": 16, "territori": 16, "water": 16, "arcticdem": 16, "strip": 16, "mosaic": 16, "across": [16, 20], "60": [16, 20], "latitud": 16, "canada": 16, "greenland": 16, "iceland": 16, "norwai": 16, "russia": 16, "sweden": 16, "cdem": 16, "canadian": 16, "digit": [16, 17], "model": [16, 17, 19, 20, 21, 23], "variabl": 16, "spatial": 16, "resolut": 16, "400": 16, "gov": [16, 22], "uk": 16, "kingdom": 16, "gv": 16, "etopo1": 16, "ocean": 16, "bathymetri": 16, "arc": 16, "eudem": 16, "europ": 16, "30": [16, 17, 20], "albania": 16, "belgium": 16, "bosnia": 16, "herzegovina": 16, "bulgaria": 16, "croatia": 16, "cypru": 16, "czechia": 16, "estonia": 16, "finland": 16, "franc": 16, "greec": 16, "hungari": 16, "ireland": 16, "itali": 16, "kosovo": 16, "latvia": 16, "liechtenstein": 16, "lithuania": 16, "luxembourg": 16, "macedonia": 16, "malta": 16, "montenegro": 16, "netherland": 16, "poland": 16, "portug": 16, "romania": 16, "serbia": 16, "slovakia": 16, "slovenia": 16, "geoscienc": 16, "australia": 16, "dem": 16, "coastal": 16, "victoria": 16, "northern": 16, "gmted": 16, "coarser": 16, "7": [16, 17, 20, 23], "15": [16, 20], "inegi": 16, "continent": 16, "mexico": 16, "kartverket": 16, "linz": 16, "8": [16, 20], "zealand": 16, "srtm": 16, "90": [16, 23], "nomin": 16, "digitalglob": 16, "inc": [16, 20], "imageri": 16, "nation": 16, "scienc": 16, "foundat": [16, 20], "award": 16, "1043681": 16, "1559691": 16, "1542736": 16, "commonwealth": 16, "2017": 16, "offen": 16, "daten": 16, "\u00f6sterreich": 16, "digital": 16, "gel\u00e4ndemodel": 16, "dgm": 16, "licenc": [16, 19, 21], "produc": [16, 20], "copernicu": 16, "union": 16, "atmospher": 16, "2016": [16, 19, 21], "2011": 16, "crown": 16, "c": [16, 19, 20, 21], "reserv": 16, "environ": 16, "agenc": 16, "2015": 16, "gmted2010": 16, "courtesi": 16, "geolog": 16, "survei": 16, "per": [16, 18], "dai": [16, 20], "howev": [16, 20, 22, 23], "regular": [16, 17], "compil": [16, 19, 20, 21], "openaip": [16, 19], "fewer": 16, "natur": [16, 20], "preserv": [16, 20], "simplic": 16, "divid": 16, "complet": [16, 24, 25], "mandatori": 16, "control": [16, 18, 20, 22, 23, 25], "thei": [16, 19, 20, 23, 24], "contin": 16, "canari": 16, "island": 16, "madagascar": 16, "asia": 16, "bahrain": 16, "emir": 16, "japan": 16, "qatar": 16, "oceanica": 16, "czech": 16, "republ": 16, "great": 16, "britain": 16, "slowenia": 16, "america": 16, "argentina": 16, "brazil": 16, "miss": 16, "colombia": 16, "falkland": 16, "transport": 17, "tl": 17, "server": [17, 19, 20, 21, 22], "manufactur": [17, 20], "regretfulli": 17, "sale": [17, 20], "expir": 17, "longer": 17, "media": 17, "septemb": 17, "2021": 17, "stop": 17, "hide": [17, 18], "complex": 17, "silent": 17, "revert": [17, 18], "insecur": [17, 18], "appear": [17, 18], "normal": [17, 20], "eventu": 17, "tamper": 17, "manipul": 17, "decis": 17, "recent": 17, "who": [17, 18, 20, 24], "risk": [17, 20], "fairphon": 17, "person": [17, 20, 22], "repair": [17, 20], "easili": [17, 25], "year": [17, 20], "brand": 17, "overrid": 17, "hardwar": [17, 25], "stai": 17, "immedi": 17, "unlock": 17, "heartbeat": 17, "listen": [17, 23], "txt": 17, "rather": 17, "unix": 17, "h": 17, "commandlin": 17, "qt": [17, 19, 21], "v": 17, "sg": 17, "simul": [17, 18, 23, 25], "screenshot": 17, "sm": 17, "deliber": 18, "chang": [18, 20, 23], "000ft": 18, "fl100": 18, "improv": 18, "readabl": [18, 20], "unset": 18, "9": [18, 20], "gradient": 18, "ampl": 18, "safeti": 18, "difficult": 18, "experienc": 18, "graphic": 18, "old": [18, 19, 21], "appli": [18, 20], "chose": 18, "height": [18, 23], "unsur": 18, "enlarg": 18, "perform": [18, 19, 20, 21], "ey": 18, "adapt": [18, 20], "quit": 18, "inde": 18, "them": [18, 20, 23], "everybodi": 18, "either": [18, 20, 23], "recept": 18, "actual": [18, 20], "fall": 18, "attempt": [18, 20], "uncheck": 18, "polici": [18, 19, 21, 25], "enforc": [18, 20], "numerour": 19, "compon": [19, 20], "heavili": 19, "runtim": 19, "modifi": [19, 20], "cc": 19, "BY": [19, 20], "0": [19, 20, 21], "nc": 19, "sa": 19, "ofma": 19, "adob": [19, 21], "glyph": [19, 21], "font": [19, 21], "bsd": [19, 21], "claus": [19, 21], "revis": [19, 20, 21], "alias": [19, 21], "raster": [19, 21], "freetyp": [19, 21], "gnu": [19, 20, 21], "v2": [19, 21], "bitstream": [19, 21], "vera": [19, 21], "blake2": [19, 21], "implement": [19, 20, 21, 23], "creativ": [19, 21], "zero": [19, 21], "v1": [19, 21], "apach": [19, 21], "catch2": [19, 21], "boost": [19, 21], "clip2tri": [19, 21], "polygon": [19, 21], "triangul": [19, 21], "mit": [19, 21], "clipper": [19, 21], "clip": [19, 21], "cocoa": [19, 21], "plugin": [19, 21, 24], "cycl": [19, 21], "compress": [19, 21], "zlib": [19, 21], "dejavu": [19, 21], "earcut": [19, 21], "isc": [19, 21], "earth": [19, 21], "gravit": [19, 21], "domain": [19, 20, 21], "eas": [19, 21], "equat": [19, 21], "robert": [19, 21], "penner": [19, 21], "effici": [19, 21], "binari": [19, 21], "decim": [19, 21], "convers": [19, 21], "routin": [19, 21], "ieee": [19, 21], "extra": [19, 21], "cmake": [19, 21], "modul": [19, 21], "fontawesom": [19, 21], "sil": [19, 21], "forkfd": [19, 21], "bitmap": [19, 21], "bdf": [19, 21], "portabl": [19, 21], "pcf": [19, 21], "variant": [19, 21], "geosimplifi": [19, 21], "j": [19, 21], "polylin": [19, 21], "simplif": [19, 21], "materi": [19, 20, 21], "icon": [19, 21], "gradl": [19, 21], "wrapper": [19, 21], "guidelin": [19, 21], "harfbuzz": [19, 21], "ng": [19, 21], "iaccessible2": [19, 21], "idl": [19, 21], "javascriptcor": [19, 21], "macro": [19, 21], "assembl": [19, 21], "simplifi": [19, 21], "jqueri": [19, 21], "kdab": [19, 21], "helper": [19, 21], "singl": [19, 20, 21], "kwin": [19, 21], "libdu": [19, 21], "header": [19, 21], "academ": [19, 21], "later": [19, 20, 21], "libjpeg": [19, 21], "turbo": [19, 21], "independ": [19, 20, 21], "jpeg": [19, 21], "libpng": [19, 21], "png": [19, 21], "libpsl": [19, 21], "suffix": [19, 21], "event": [19, 20, 21], "syscal": [19, 21], "lunr": [19, 21], "sphinx": [19, 21], "theme": [19, 21], "md4": [19, 21], "md4c": [19, 21], "md5": [19, 21], "metaf": [19, 21], "nativ": [19, 21], "opengl": [19, 21], "openssl": [19, 21], "osm": [19, 21], "liberti": [19, 21], "pcre2": [19, 21], "stack": [19, 21], "pixman": [19, 21], "poly2tri": [19, 21], "qeventdispatch": [19, 21], "maco": [19, 21], "qhttpengin": [19, 21], "toolkit": [19, 21], "hash": [19, 21], "sha": [19, 21], "brg_endian": [19, 21], "keccak": [19, 21], "384": [19, 21], "512": [19, 21], "shadow": [19, 21], "angular": [19, 21], "siphash": [19, 21], "smooth": [19, 21], "imlib2": [19, 21], "sqlite": [19, 21], "srgb": [19, 21], "profil": [19, 21], "icc": [19, 21], "consortium": [19, 21], "tango": [19, 21], "pack": [19, 21], "darkobra": [19, 21], "mozilla": [19, 21], "tiff": [19, 21], "libtiff": [19, 21], "tinycbor": [19, 21], "underscor": [19, 21], "unicod": [19, 21], "charact": [19, 21], "ucd": [19, 21], "cldr": [19, 21], "valgrind": [19, 21], "origin": [19, 20, 21], "vulkan": [19, 21], "api": [19, 21, 22], "registri": [19, 21], "memori": [19, 21], "alloc": [19, 21], "webgradi": [19, 21], "webp": [19, 21], "libwebp": [19, 21], "wintab": [19, 21], "lc": [19, 21], "telegraph": [19, 21], "x": [19, 21], "x11": [19, 21], "histor": [19, 21], "disclaim": [19, 20, 21], "xcb": [19, 21], "xinput": [19, 21], "xsvg": [19, 21], "sell": [19, 20, 21], "29": 20, "june": 20, "2007": 20, "http": [20, 22], "fsf": 20, "everyon": 20, "permit": 20, "verbatim": 20, "document": [20, 23], "preambl": 20, "copyleft": 20, "practic": 20, "freedom": 20, "By": 20, "contrast": 20, "speak": 20, "price": 20, "charg": 20, "get": 20, "protect": 20, "prevent": 20, "deni": 20, "surrend": 20, "certain": 20, "respons": 20, "whether": 20, "grati": 20, "fee": 20, "pass": 20, "recipi": 20, "And": 20, "gpl": 20, "assert": 20, "clearli": 20, "sake": 20, "mark": [20, 25], "attribut": 20, "erron": 20, "previou": 20, "although": 20, "fundament": 20, "incompat": [20, 23], "systemat": 20, "pattern": 20, "abus": [20, 23], "occur": 20, "individu": 20, "unaccept": 20, "prohibit": 20, "those": 20, "aris": 20, "stand": 20, "provis": [20, 23], "threaten": 20, "constantli": 20, "patent": 20, "restrict": [20, 24], "purpos": [20, 23, 24], "effect": 20, "proprietari": 20, "assur": [20, 22], "modif": 20, "AND": 20, "definit": 20, "law": 20, "semiconductor": 20, "mask": 20, "license": 20, "organ": 20, "fashion": 20, "exact": 20, "earlier": 20, "unmodifi": 20, "propag": 20, "secondarili": 20, "liabl": 20, "infring": 20, "execut": 20, "privat": 20, "convei": 20, "enabl": [20, 24], "parti": [20, 25], "mere": 20, "conveni": 20, "criterion": 20, "form": 20, "object": 20, "recogn": 20, "languag": 20, "among": 20, "whole": 20, "context": 20, "kernel": 20, "interpret": [20, 23], "script": 20, "dynam": 20, "link": 20, "subprogram": 20, "intim": 20, "flow": 20, "regener": 20, "irrevoc": 20, "explicitli": 20, "affirm": 20, "unlimit": 20, "constitut": 20, "acknowledg": 20, "fair": 20, "forc": 20, "sole": 20, "exclus": 20, "facil": [20, 25], "thu": 20, "behalf": 20, "relationship": 20, "circumst": 20, "sublicens": 20, "unnecessari": 20, "circumvent": 20, "deem": 20, "technolog": 20, "measur": [20, 23], "oblig": 20, "articl": 20, "11": 20, "wipo": 20, "treati": 20, "adopt": 20, "decemb": 20, "1996": 20, "waiv": 20, "forbid": 20, "intent": 20, "against": 20, "third": [20, 25], "medium": 20, "conspicu": 20, "intact": 20, "absenc": 20, "carri": 20, "date": 20, "anyon": 20, "possess": 20, "regardless": 20, "invalid": 20, "separ": 20, "extens": 20, "combin": 20, "larger": 20, "volum": 20, "storag": 20, "aggreg": 20, "beyond": [20, 22], "inclus": 20, "6": 20, "embodi": 20, "accompani": 20, "fix": 20, "durabl": 20, "customarili": 20, "interchang": 20, "least": [20, 23], "custom": 20, "cost": 20, "occasion": 20, "noncommerci": 20, "subsect": 20, "6b": 20, "maintain": 20, "sai": 20, "host": 20, "satisfi": 20, "peer": 20, "transmiss": 20, "being": 20, "6d": 20, "portion": 20, "exclud": 20, "tangibl": 20, "famili": 20, "household": 20, "sold": 20, "incorpor": 20, "dwell": 20, "doubt": 20, "resolv": 20, "favor": 20, "coverag": 20, "industri": 20, "unless": 20, "repres": 20, "signific": 20, "kei": 20, "interf": 20, "transact": 20, "perpetu": 20, "character": 20, "But": 20, "neither": 20, "nor": 20, "retain": 20, "abil": 20, "rom": 20, "itself": 20, "advers": 20, "affect": 20, "violat": 20, "publicli": 20, "unpack": 20, "supplement": 20, "regard": 20, "notwithstand": 20, "holder": 20, "liabil": 20, "16": 20, "misrepresent": 20, "licensor": 20, "declin": 20, "trademark": 20, "trade": 20, "f": 20, "indemnif": 20, "contractu": 20, "assumpt": 20, "impos": 20, "relicens": 20, "surviv": 20, "expressli": 20, "void": 20, "paragraph": 20, "ceas": 20, "reinstat": 20, "provision": 20, "perman": 20, "notifi": 20, "prior": 20, "cessat": 20, "moreov": 20, "cure": 20, "receipt": 20, "qualifi": 20, "Not": 20, "ancillari": 20, "consequ": 20, "likewis": 20, "noth": 20, "action": 20, "downstream": 20, "subject": 20, "complianc": 20, "entiti": 20, "asset": 20, "subdivid": 20, "merg": 20, "whatev": 20, "predecessor": 20, "had": 20, "effort": 20, "royalti": 20, "litig": 20, "cross": 20, "claim": 20, "counterclaim": 20, "lawsuit": 20, "alleg": 20, "contributor": 20, "hereaft": 20, "manner": 20, "consist": 20, "worldwid": 20, "express": 20, "commit": 20, "denomin": 20, "coven": 20, "sue": 20, "knowingli": 20, "readili": 20, "arrang": 20, "depriv": 20, "benefit": 20, "knowledg": [20, 22], "pursuant": 20, "procur": 20, "convey": 20, "discriminatori": 20, "scope": 20, "busi": [20, 23], "payment": 20, "primarili": 20, "wa": 20, "28": 20, "march": 20, "constru": 20, "defens": 20, "court": 20, "contradict": 20, "excus": 20, "simultan": [20, 23], "pertin": 20, "agre": 20, "collect": 20, "whom": 20, "refrain": 20, "affero": 20, "14": 20, "Such": 20, "spirit": 20, "distinguish": 20, "ever": 20, "proxi": 20, "THERE": 20, "NO": 20, "FOR": 20, "THE": 20, "TO": 20, "IN": 20, "OR": 20, "AS": 20, "OF": 20, "BUT": 20, "NOT": 20, "merchant": 20, "fit": 20, "WITH": 20, "prove": 20, "defect": 20, "WILL": 20, "BE": 20, "damag": 20, "incident": 20, "consequenti": 20, "inabl": 20, "BEING": 20, "inaccur": 20, "sustain": 20, "failur": 20, "IF": 20, "SUCH": 20, "17": 20, "review": 20, "absolut": 20, "waiver": 20, "civil": 20, "transmit": 22, "regularli": 22, "respond": 22, "log": 22, "www": 22, "aviationweath": 22, "dataserv": 22, "notam": 22, "faa": 22, "stefan": 22, "kebeku": 22, "wintererstra\u00df": 22, "77": 22, "79104": 22, "im": 22, "breisgau": 22, "wlan": 23, "rang": [23, 24], "understand": 23, "watch": 23, "tcp": 23, "2000": 23, "192": 23, "168": 23, "stream": 23, "sentenc": 23, "conform": 23, "ftd": 23, "012": 23, "icd": 23, "gdl": 23, "wg": 23, "84": 23, "ellipsoid": 23, "market": 23, "wrongli": 23, "strategi": 23, "deal": 23, "skydemon": 23, "unabl": 23, "unlik": 23, "workaround": 23, "ring": 23, "eight": 23, "virtual": 23, "target": 23, "avionc": 23, "pole": 23, "accuraci": 23, "perfect": 23, "63093": 23, "foreground": 23, "discov": 23, "unicast": 23, "json": 23, "unidirect": 23, "signal": 23, "convinc": 23, "unidirectionl": 23, "idea": 23, "uavionix": 23, "unusu": 23, "decrypt": 23, "purchas": 23, "feel": 23, "altimet": 23, "correl": 23, "cabin": 23, "suffici": 23, "reliabl": 23, "oppon": 23, "sensor": 23, "gp": [23, 24], "henc": 23, "mislead": 23, "100": 24, "comparison": 24, "ten": 24, "solut": 24, "osmand": 24, "reproduc": 24, "hi": 24, "overlai": 24, "african": 24, "visit": 24, "ofm": 24, "learn": 24, "slider": 24, "openflightmap": 24, "enjoi": 24, "reassur": 24, "respectfulli": 24, "circumnavig": 24, "eleg": 25, "stress": 25, "daili": 25, "noaa": 25, "quickli": 25, "head": 25, "27": 25, "bar": 25, "safeski": 25, "donat": 25, "technic": 25, "tip": 25, "trick": 25}, "objects": {}, "objtypes": {}, "objnames": {}, "titleterms": {"think": 0, "befor": [0, 2, 8, 9, 10], "you": [0, 8, 9, 10], "fly": [0, 2], "softwar": [0, 19, 20], "limit": [0, 18], "navig": [0, 2, 14, 15, 18, 25], "data": [0, 3, 4, 10, 16, 18, 19, 23], "aviat": 0, "oper": 0, "system": [0, 18], "hardwar": 0, "instal": 1, "setup": 1, "app": [1, 7, 8, 11], "set": [1, 7, 9, 18], "aircraft": [1, 7], "specif": 1, "done": 1, "your": [2, 4, 9, 10], "first": 2, "flight": [2, 7, 9, 14, 25], "The": 2, "move": [2, 15, 18], "map": [2, 3, 4, 15, 16, 18, 19], "bar": [2, 15, 18], "interact": [2, 15], "control": [2, 13, 15], "inform": [2, 15], "about": [2, 14], "airspac": [2, 3, 13, 18], "airfield": [2, 13], "other": [2, 9, 25], "facil": 2, "go": 2, "import": [3, 4, 11, 17], "openair": 3, "file": [3, 17], "android": [3, 4, 17], "devic": [3, 4, 23], "linux": [3, 4, 17], "desktop": [3, 4, 17], "us": [4, 7, 25], "own": 4, "mbtile": 4, "sourc": [4, 18], "raster": 4, "geotiff": 4, "format": 4, "make": 5, "donat": 5, "paypal": 5, "bank": 5, "address": 5, "find": 6, "nearbi": 6, "waypoint": [6, 7, 11], "plan": 7, "what": [7, 11], "expect": [7, 11], "up": [7, 9], "rout": [7, 15], "step": [7, 8, 10, 25], "1": [7, 8, 10], "characterist": 7, "2": [7, 10], "specifi": 7, "wind": 7, "3": 7, "4": 7, "edit": 7, "necessari": 7, "option": 7, "save": 7, "futur": 7, "export": [7, 11], "share": [7, 8, 11], "open": [7, 11], "anoth": [7, 11], "connect": [8, 9, 10], "safeski": 8, "0": [8, 10], "enabl": 8, "traffic": [8, 10, 13, 15, 23], "simul": 9, "aerofli": 9, "f": 9, "flightgear": 9, "m": 9, "x": 9, "plane": 9, "11": 9, "program": [9, 19], "troubleshoot": [9, 10], "receiv": [10, 23], "compat": 10, "enter": 10, "": 10, "wi": [10, 17], "fi": [10, 17], "network": [10, 17, 18], "stream": 10, "flarmnet": 10, "manag": 11, "librari": 11, "add": 11, "view": 11, "check": 12, "weather": 12, "page": [12, 15, 18, 25], "footer": 12, "three": 12, "dot": 12, "menu": 12, "displai": [13, 24], "restrict": 13, "zone": 13, "transpond": 13, "mandatori": 13, "radio": 13, "parachut": 13, "jump": 13, "area": 13, "natur": 13, "reserv": 13, "pattern": 13, "enrout": [14, 25], "main": 15, "gestur": 15, "ownship": 15, "posit": [15, 18], "color": 15, "code": 15, "factor": 15, "label": 15, "base": 16, "terrain": 16, "attribut": 16, "aeronaut": 16, "updat": 16, "polici": [16, 22], "origin": 16, "list": 16, "platform": 17, "note": [17, 23], "secur": [17, 18], "problem": 17, "screen": 17, "backlight": 17, "lock": 17, "drag": 17, "drop": 17, "command": 17, "line": 17, "altitud": 18, "glide": 18, "sector": 18, "hillshad": 18, "altimet": 18, "mode": 18, "user": 18, "interfac": 18, "larg": 18, "font": 18, "night": 18, "voic": 18, "notif": 18, "primari": 18, "ignor": 18, "error": 18, "clear": 18, "password": 18, "storag": 18, "help": 18, "third": 19, "parti": 19, "geograph": 19, "includ": 19, "licens": 20, "privaci": 22, "respons": 22, "technic": 23, "support": 23, "commun": 23, "known": 23, "issu": 23, "gdl90": 23, "foreflight": 23, "broadcast": 23, "skyecho": 23, "pingusb": 23, "tip": 24, "trick": 24, "record": 24, "satnav": 24, "track": 24, "introduct": 25, "get": 25, "start": 25, "further": 25, "advanc": 25, "refer": 25, "appendix": 25}, "envversion": {"sphinx.domains.c": 3, "sphinx.domains.changeset": 1, "sphinx.domains.citation": 1, "sphinx.domains.cpp": 9, "sphinx.domains.index": 1, "sphinx.domains.javascript": 3, "sphinx.domains.math": 2, "sphinx.domains.python": 4, "sphinx.domains.rst": 2, "sphinx.domains.std": 2, "sphinx": 58}, "alltitles": {"Think before you fly": [[0, "think-before-you-fly"]], "Software limitations": [[0, "software-limitations"]], "Navigational data and aviation data": [[0, "navigational-data-and-aviation-data"]], "Operating system limitations": [[0, "operating-system-limitations"]], "Hardware limitations": [[0, "hardware-limitations"]], "Installation and setup": [[1, "installation-and-setup"]], "App installation": [[1, "app-installation"]], "Set aircraft specifics": [[1, "set-aircraft-specifics"]], "Done.": [[1, "done"]], "Before your first flight": [[2, "before-your-first-flight"]], "The moving map": [[2, "the-moving-map"]], "The Navigation Bar": [[2, "the-navigation-bar"]], "Interactive controls": [[2, "interactive-controls"]], "Information about airspaces, airfields and other facilities": [[2, "information-about-airspaces-airfields-and-other-facilities"]], "Go flying!": [[2, "go-flying"]], "Import airspace data": [[3, "import-airspace-data"]], "Import OpenAir files on Android devices": [[3, "import-openair-files-on-android-devices"]], "Import Maps on Linux Desktop": [[3, "import-maps-on-linux-desktop"], [4, "import-maps-on-linux-desktop"]], "Use your own maps": [[4, "use-your-own-maps"]], "Import Maps": [[4, "import-maps"]], "Import Maps on Android devices": [[4, "import-maps-on-android-devices"]], "MBTILES Map Data Sources": [[4, "mbtiles-map-data-sources"]], "Raster Maps in GeoTIFF format": [[4, "raster-maps-in-geotiff-format"]], "Make a donation": [[5, "make-a-donation"]], "PayPal": [[5, "paypal"]], "Bank Address": [[5, "bank-address"]], "Find nearby waypoints": [[6, "find-nearby-waypoints"]], "Plan a Flight": [[7, "plan-a-flight"]], "What to expect": [[7, "what-to-expect"], [11, "what-to-expect"]], "Set up a route": [[7, "set-up-a-route"]], "Step 1: Set aircraft characteristics": [[7, "step-1-set-aircraft-characteristics"]], "Step 2: Specify wind": [[7, "step-2-specify-wind"]], "Step 3: Specify waypoints": [[7, "step-3-specify-waypoints"]], "Step 4: Edit the route if necessary": [[7, "step-4-edit-the-route-if-necessary"]], "Optional: Save route for future use": [[7, "optional-save-route-for-future-use"]], "Optional: Export and share the route": [[7, "optional-export-and-share-the-route"]], "Optional: Open the route in another app": [[7, "optional-open-the-route-in-another-app"]], "Connect to the SafeSky app": [[8, "connect-to-the-safesky-app"]], "Connect!": [[8, "connect"], [10, "connect"]], "Step 0: Before you connect": [[8, "step-0-before-you-connect"], [10, "step-0-before-you-connect"]], "Step 1: Enable traffic sharing": [[8, "step-1-enable-traffic-sharing"]], "Connect your flight simulator": [[9, "connect-your-flight-simulator"]], "Before you connect": [[9, "before-you-connect"]], "Set up your flight simulator": [[9, "set-up-your-flight-simulator"]], "Aerofly FS": [[9, "aerofly-fs"]], "FlightGear": [[9, "flightgear"]], "MS Flight Simulator": [[9, "ms-flight-simulator"]], "X-Plane 11": [[9, "x-plane-11"]], "Other programs": [[9, "other-programs"]], "Troubleshooting": [[9, "troubleshooting"], [10, "troubleshooting"]], "Connect to your traffic receiver": [[10, "connect-to-your-traffic-receiver"]], "Compatibility": [[10, "compatibility"]], "Step 1: Enter the traffic receiver\u2019s Wi-Fi network": [[10, "step-1-enter-the-traffic-receiver-s-wi-fi-network"]], "Step 2: Connect to the traffic data stream": [[10, "step-2-connect-to-the-traffic-data-stream"]], "Flarmnet data": [[10, "flarmnet-data"]], "Manage a waypoint library": [[11, "manage-a-waypoint-library"]], "Add waypoints to the library": [[11, "add-waypoints-to-the-library"]], "View the waypoint library": [[11, "view-the-waypoint-library"]], "Import waypoints": [[11, "import-waypoints"]], "Export and share the waypoint library": [[11, "export-and-share-the-waypoint-library"]], "Open the waypoint library in another app": [[11, "open-the-waypoint-library-in-another-app"]], "Check Weather": [[12, "check-weather"]], "Page footer": [[12, "page-footer"]], "Three-dot menu": [[12, "three-dot-menu"]], "Airspace Display": [[13, "airspace-display"]], "Restricted Airspace": [[13, "restricted-airspace"]], "Controlled Airspace": [[13, "controlled-airspace"]], "Control Zone": [[13, "control-zone"]], "Transponder Mandatory Zones": [[13, "transponder-mandatory-zones"]], "Radio Mandatory Zone": [[13, "radio-mandatory-zone"]], "Parachute Jumping Areas": [[13, "parachute-jumping-areas"]], "Nature Reserve Areas": [[13, "nature-reserve-areas"]], "Airfields": [[13, "airfields"]], "Traffic Pattern": [[13, "traffic-pattern"]], "About Enroute Flight Navigation": [[14, "about-enroute-flight-navigation"]], "Main Page and Moving Map": [[15, "main-page-and-moving-map"]], "Route Information Bar": [[15, "route-information-bar"]], "Interactive Controls": [[15, "interactive-controls"]], "Moving Map": [[15, "moving-map"], [18, "moving-map"]], "Gesture Controls": [[15, "gesture-controls"]], "Ownship Position": [[15, "ownship-position"]], "Traffic Information": [[15, "traffic-information"]], "Color Coding": [[15, "color-coding"]], "Traffic Factors": [[15, "traffic-factors"]], "Traffic labelling": [[15, "traffic-labelling"]], "Navigation Bar": [[15, "navigation-bar"], [18, "navigation-bar"]], "Map Data": [[16, "map-data"]], "Base maps": [[16, "base-maps"]], "Terrain maps": [[16, "terrain-maps"]], "Attributions": [[16, "attributions"]], "Aeronautical maps": [[16, "aeronautical-maps"]], "Update policy": [[16, "update-policy"]], "Data origin": [[16, "data-origin"]], "List of maps": [[16, "list-of-maps"]], "Platform notes": [[17, "platform-notes"]], "Android": [[17, "android"]], "Network security problems": [[17, "network-security-problems"]], "Screen backlighting": [[17, "screen-backlighting"]], "Screen locking": [[17, "screen-locking"]], "Wi-Fi locking": [[17, "wi-fi-locking"]], "Linux desktop": [[17, "linux-desktop"]], "File import by drag-and-drop": [[17, "file-import-by-drag-and-drop"]], "Command line": [[17, "command-line"]], "Settings Page": [[18, "settingspage"]], "Airspace Altitude Limit": [[18, "airspace-altitude-limit"]], "Gliding Sectors": [[18, "gliding-sectors"]], "Hillshading": [[18, "hillshading"]], "Altimeter Mode": [[18, "altimeter-mode"]], "User Interface": [[18, "user-interface"]], "Large Fonts": [[18, "large-fonts"]], "Night mode": [[18, "night-mode"]], "Voice Notifications": [[18, "voice-notifications"]], "System": [[18, "system"]], "Primary Position Data Source": [[18, "primary-position-data-source"]], "Ignore network security errors": [[18, "ignore-network-security-errors"]], "Clear password storage": [[18, "clear-password-storage"]], "Help": [[18, "help"]], "Third party software and data": [[19, "third-party-software-and-data"]], "Geographic maps": [[19, "geographic-maps"]], "Software and data included in the program": [[19, "software-and-data-included-in-the-program"]], "Software license": [[20, "software-license"]], "Privacy policies": [[22, "privacy-policies"]], "Responsible": [[22, "responsible"]], "Technical Notes": [[23, "technical-notes"]], "Traffic Data Receiver support": [[23, "traffic-data-receiver-support"]], "Communication": [[23, "communication"]], "Known issues with GDL90": [[23, "known-issues-with-gdl90"]], "ForeFlight Broadcast": [[23, "foreflight-broadcast"]], "Known issues with SkyEcho devices": [[23, "known-issues-with-skyecho-devices"]], "Known issues with pingUSB devices": [[23, "known-issues-with-pingusb-devices"]], "Tips & Tricks": [[24, "tips-tricks"]], "Display of recorded satnav tracks": [[24, "display-of-recorded-satnav-tracks"]], "Enroute Flight Navigation": [[25, "enroute-flight-navigation"]], "Introduction": [[25, "introduction"]], "Getting Started": [[25, "getting-started"]], "Further Steps": [[25, "further-steps"], [25, null]], "Advanced Use": [[25, "advanced-use"], [25, null]], "Reference: Pages": [[25, "reference-pages"], [25, null]], "Reference: Other": [[25, "reference-other"], [25, null]], "Appendix": [[25, "appendix"], [25, null]]}, "indexentries": {}}) \ No newline at end of file +Search.setIndex({"docnames": ["01-intro/01-think", "01-intro/02-installation", "01-intro/03-firstFlight", "02-advanced/airspace", "02-advanced/customMaps", "02-steps/donate", "02-steps/nearby", "02-steps/plan", "02-steps/safesky", "02-steps/simulator", "02-steps/traffic", "02-steps/waypointLibrary", "02-steps/weather", "03-reference/Airspace", "03-reference/about", "03-reference/mainPage", "03-reference/mapData", "03-reference/platform", "03-reference/settings", "04-appendix/authors", "04-appendix/license_3rdParty", "04-appendix/license_enroute", "04-appendix/licenses_overview", "04-appendix/privacy", "04-appendix/technical", "04-appendix/tips", "index"], "filenames": ["01-intro/01-think.rst", "01-intro/02-installation.rst", "01-intro/03-firstFlight.rst", "02-advanced/airspace.rst", "02-advanced/customMaps.rst", "02-steps/donate.rst", "02-steps/nearby.rst", "02-steps/plan.rst", "02-steps/safesky.rst", "02-steps/simulator.rst", "02-steps/traffic.rst", "02-steps/waypointLibrary.rst", "02-steps/weather.rst", "03-reference/Airspace.rst", "03-reference/about.rst", "03-reference/mainPage.rst", "03-reference/mapData.rst", "03-reference/platform.rst", "03-reference/settings.rst", "04-appendix/authors.rst", "04-appendix/license_3rdParty.rst", "04-appendix/license_enroute.rst", "04-appendix/licenses_overview.rst", "04-appendix/privacy.rst", "04-appendix/technical.rst", "04-appendix/tips.rst", "index.rst"], "titles": ["Think before you fly", "Installation and setup", "Before your first flight", "Import airspace data", "Use your own maps", "Make a donation", "Find nearby waypoints", "Plan a Flight", "Connect to the SafeSky app", "Connect your flight simulator", "Connect to your traffic receiver", "Manage a waypoint library", "Check Weather", "Airspace Display", "About Enroute Flight Navigation", "Main Page and Moving Map", "Map Data", "Platform notes", "Settings Page", "Authors", "Third party software and data", "Software license", "<no title>", "Privacy Policies", "Technical Notes", "Tips & Tricks", "Enroute Flight Navigation"], "terms": {"enrout": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 15, 17, 18, 19, 20, 21, 24, 25], "flight": [0, 1, 3, 4, 5, 6, 8, 10, 11, 12, 13, 15, 16, 17, 18, 19, 20, 21, 24, 25], "i": [0, 1, 2, 4, 5, 7, 8, 9, 10, 11, 12, 13, 15, 16, 17, 18, 19, 21, 23, 24, 25, 26], "free": [0, 1, 4, 9, 20, 21, 22, 24, 26], "product": [0, 17, 21], "ha": [0, 1, 2, 4, 6, 8, 9, 10, 11, 12, 15, 18, 19, 21, 24, 25, 26], "been": [0, 4, 9, 11, 12, 15, 19, 21, 25, 26], "publish": [0, 20, 21, 24], "hope": 0, "might": [0, 1, 4, 7, 9, 10, 11, 12, 15, 17, 18, 20, 24], "us": [0, 1, 2, 3, 5, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 21, 24, 25], "an": [0, 2, 3, 4, 7, 8, 10, 11, 12, 13, 15, 17, 18, 19, 21, 23, 24, 26], "aid": 0, "prudent": 0, "It": [0, 4, 7, 10, 11, 17, 23], "come": [0, 3, 4, 10, 12, 21], "guarante": [0, 16, 21], "mai": [0, 4, 10, 13, 21], "work": [0, 8, 9, 10, 15, 17, 21, 24], "expect": [0, 1, 10, 15, 18, 21, 23, 24], "shown": [0, 2, 9, 11, 12, 13, 15, 17, 18], "wrong": [0, 12, 24], "your": [0, 1, 5, 7, 11, 12, 13, 14, 15, 17, 18, 21, 23, 25, 26], "fail": [0, 18, 21], "thi": [0, 1, 2, 3, 5, 7, 9, 10, 12, 13, 15, 18, 21, 23, 24, 25, 26], "app": [0, 2, 3, 4, 5, 9, 10, 14, 15, 16, 17, 18, 19, 23, 24, 26], "substitut": [0, 26], "proper": [0, 9], "prepar": [0, 7], "good": [0, 24, 25], "pilotag": 0, "ani": [0, 6, 7, 8, 9, 12, 16, 17, 21, 23, 24], "inform": [0, 6, 8, 9, 10, 12, 13, 14, 16, 17, 18, 19, 21, 23, 24, 26], "must": [0, 3, 4, 18, 21, 23, 24], "alwai": [0, 4, 10, 17, 18], "valid": [0, 2, 8, 21], "offici": [0, 4, 12, 21, 26], "airspac": [0, 15, 16, 25, 26], "sourc": [0, 9, 12, 16, 20, 21, 24, 25], "author": [0, 9, 10, 14, 17, 21, 24, 26], "mean": [0, 2, 15, 21], "The": [0, 1, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26], "non": [0, 5, 21, 23], "certifi": 0, "devic": [0, 1, 2, 7, 9, 10, 11, 15, 17, 18, 21, 23, 25, 26], "like": [0, 2, 3, 4, 7, 9, 10, 12, 15, 17, 18, 19, 21], "primari": [0, 9], "caus": [0, 21], "accid": 0, "lead": [0, 10], "loss": [0, 10, 21], "live": [0, 10, 17], "we": [0, 1, 2, 4, 7, 10, 16, 18, 21, 23, 24, 25], "do": [0, 2, 3, 4, 5, 7, 12, 16, 17, 18, 19, 21, 23, 24], "believ": [0, 17, 21], "fulfil": [0, 19, 21], "requir": [0, 8, 9, 10, 13, 16, 18, 21, 24], "eu": [0, 16], "regul": [0, 18], "No": [0, 15, 21, 23], "923": 0, "2012": 0, "sera": 0, "2010": 0, "begin": [0, 18], "pilot": [0, 2, 8, 17, 18, 19], "command": [0, 21], "aircraft": [0, 2, 8, 9, 10, 13, 15, 18, 23, 24, 26], "shall": [0, 21], "becom": [0, 4, 7], "familiar": [0, 2], "all": [0, 1, 7, 8, 9, 10, 13, 16, 17, 18, 21, 23, 24, 25, 26], "avail": [0, 1, 2, 3, 4, 12, 13, 15, 16, 18, 21, 25], "appropri": [0, 7, 11, 21], "intend": [0, 7, 12, 21, 26], "To": [0, 4, 7, 8, 9, 10, 11, 12, 14, 15, 17, 18, 21, 24], "put": 0, "simpli": [0, 1, 9], "reli": [0, 17, 20, 21], "most": [0, 2, 3, 4, 7, 10, 11, 15, 16, 17, 18, 21, 24], "illeg": 0, "jurisdict": 0, "certainli": [0, 12], "stupid": 0, "potenti": [0, 15, 18], "suicid": 0, "approv": [0, 12], "wai": [0, 3, 4, 7, 13, 15, 21], "contain": [0, 4, 8, 10, 11, 15, 16, 20, 21, 25], "bug": [0, 9], "includ": [0, 5, 6, 12, 13, 16, 17, 21, 23, 24, 26], "airfield": [0, 3, 6, 7, 10, 11, 12, 15, 16, 23, 26], "ar": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 15, 16, 17, 18, 19, 20, 21, 23, 24, 25, 26], "provid": [0, 4, 9, 12, 16, 17, 18, 21, 23], "without": [0, 1, 17, 21], "certif": [0, 17], "warranti": [0, 21], "doe": [0, 8, 9, 10, 12, 15, 16, 17, 18, 21, 23, 24], "from": [0, 2, 4, 6, 7, 8, 9, 10, 11, 12, 15, 16, 17, 18, 20, 21, 22, 23, 26], "incomplet": 0, "outdat": [0, 4, 12], "otherwis": [0, 12, 18, 21], "incorrect": 0, "user": [0, 3, 4, 7, 9, 10, 11, 17, 19, 20, 21, 24, 25], "run": [0, 3, 4, 9, 17, 21, 24], "mobil": [0, 1, 18], "phone": [0, 10], "tablet": 0, "comput": [0, 1, 3, 4, 7, 9, 15, 18, 21, 24, 26], "android": [0, 1, 7, 11, 18, 20, 22, 26], "while": [0, 1, 4, 7, 11, 16, 17, 18, 24, 25, 26], "fine": [0, 13, 24], "vast": 0, "major": [0, 10, 21], "pleas": [0, 1, 2, 4, 5, 7, 9, 25], "keep": [0, 21], "follow": [0, 2, 3, 4, 7, 8, 9, 10, 12, 13, 15, 17, 20, 21, 23, 24], "mind": [0, 11], "can": [0, 2, 3, 4, 6, 7, 9, 10, 11, 12, 14, 15, 17, 18, 21, 23, 24, 25, 26], "decid": [0, 17, 18, 21], "time": [0, 2, 4, 5, 7, 8, 9, 10, 12, 13, 15, 17, 18, 20, 21, 22, 26], "termin": [0, 21], "slow": [0, 11], "down": [0, 7, 10, 11, 12], "clear": [0, 21], "resourc": 0, "other": [0, 4, 7, 10, 11, 13, 14, 16, 17, 18, 21, 23, 24, 25], "interfer": 0, "mani": [0, 1, 2, 3, 4, 10, 17, 18, 24], "vendor": 0, "notabl": 0, "One": [0, 25], "plu": [0, 7, 21], "huawei": 0, "samsung": 0, "equip": [0, 15, 24], "batteri": [0, 17], "save": [0, 4, 11, 17], "randomli": 0, "kill": 0, "long": [0, 7, 9, 17, 18, 21], "process": [0, 1, 4, 8, 10, 23], "These": [0, 16, 17, 18, 21, 24, 25], "cannot": [0, 1, 4, 10, 15, 21, 23, 24], "uninstal": 0, "compli": [0, 21, 24, 25], "standard": [0, 2, 3, 4, 9, 10, 15, 18, 21, 24], "often": [0, 4, 9, 10, 15, 17, 18], "extrem": [0, 4, 9, 18], "buggi": [0, 18], "At": [0, 4, 9, 15], "manual": [0, 2, 7, 8, 9, 10, 15, 17, 18, 19, 26], "excempt": 0, "mode": [0, 2, 7, 9, 10, 11, 13, 15, 21, 24], "set": [0, 3, 4, 8, 10, 15, 17, 26], "usual": [0, 10], "lost": 0, "updat": [0, 1, 3, 4, 10, 12, 17, 18, 21, 23, 26], "googl": [0, 1, 7, 11, 17, 20, 22], "": [0, 3, 8, 9, 15, 16, 20, 21, 22, 23, 24], "own": [0, 2, 10, 21, 24, 26], "pixel": 0, "nexu": 0, "have": [0, 2, 4, 5, 7, 8, 9, 12, 15, 17, 18, 21, 24, 25], "problem": [0, 18, 21], "see": [0, 2, 9, 10, 12, 15, 24], "websit": [0, 4, 12], "don": 0, "t": [0, 2, 10, 15], "my": 0, "more": [0, 2, 7, 9, 10, 12, 15, 16, 17, 18, 21, 25], "varieti": [0, 4, 24], "platform": [0, 1, 20, 22, 26], "compar": [0, 18, 24], "consum": [0, 21], "electron": 0, "meet": [0, 21], "design": [0, 2, 11, 13, 18, 20, 21, 22, 25, 26], "continu": [0, 1, 21], "extend": [0, 9, 18, 21, 24], "period": [0, 17, 18], "particular": [0, 4, 21, 23], "displai": [0, 1, 2, 7, 8, 10, 12, 15, 17, 18, 21, 26], "overheat": 0, "catch": 0, "fire": 0, "capac": 0, "even": [0, 9, 13, 18, 21], "connect": [0, 2, 3, 4, 12, 15, 16, 17, 18, 21, 24, 26], "power": [0, 4, 9, 10, 17, 21], "via": [0, 3, 4, 9, 10, 12, 17, 18, 24], "usb": [0, 3, 4], "cabl": 0, "cpu": 0, "energi": 0, "than": [0, 7, 8, 10, 15, 17, 18, 21, 25], "deliv": 0, "navig": [1, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 17, 19, 20, 21, 24, 25], "plai": [1, 2, 17], "store": [1, 23], "linux": [1, 7, 11, 20, 22], "desktop": [1, 7, 9, 11, 15], "machin": [1, 3, 4, 9, 21], "flathub": 1, "org": [1, 10, 21], "depend": [1, 2, 4, 7, 11, 12, 15, 16, 18, 20], "distribut": [1, 3, 20, 21, 22], "you": [1, 2, 3, 4, 5, 6, 7, 11, 12, 15, 17, 18, 21, 23, 25, 26], "also": [1, 4, 7, 9, 10, 13, 15, 16, 17, 19, 21, 23, 26], "find": [1, 11, 18, 21, 26], "softwar": [1, 4, 7, 9, 14, 22, 24, 26], "manag": [1, 3, 4, 26], "applic": [1, 13, 20, 21, 22, 23], "after": [1, 2, 4, 7, 10, 11, 17, 18, 19, 21], "start": [1, 2, 8, 9, 11, 15, 17, 25], "need": [1, 4, 7, 9, 10, 21, 24], "grant": [1, 21], "necessari": [1, 4, 21, 23], "permiss": [1, 12, 20, 21, 22], "ask": [1, 7, 10, 12, 18, 21], "accept": [1, 17, 21], "term": [1, 21], "condit": [1, 9, 10, 12, 18, 21], "geograph": 1, "map": [1, 7, 8, 9, 10, 11, 23, 25, 26], "As": [1, 7, 8, 9, 12, 15, 17, 18, 20, 24, 25], "last": [1, 15, 17, 25], "step": [1, 2, 15, 21, 25], "suggest": [1, 25], "download": [1, 3, 4, 7, 9, 10, 12, 18, 20, 23, 26], "relev": [1, 8, 10, 15, 18, 21], "current": [1, 2, 4, 6, 7, 10, 12, 14, 15, 19, 23, 24, 25, 26], "locat": [1, 4, 9, 12, 13, 23], "onc": [1, 2, 4, 7, 8, 9, 10, 11, 16, 18, 25], "finish": 1, "data": [1, 2, 7, 8, 9, 11, 12, 13, 15, 17, 21, 22, 23, 25, 26], "minut": [1, 2, 10, 15, 16, 26], "so": [1, 2, 10, 11, 15, 16, 21, 24, 26], "recommend": [1, 2, 4, 10, 24], "tell": [1, 17, 21], "littl": [1, 2, 15, 18], "about": [1, 7, 15, 16, 17, 23, 26], "befor": [1, 11, 25, 26], "fly": [1, 7, 8, 10, 12, 13, 15, 18, 26], "open": [1, 2, 3, 4, 6, 8, 9, 10, 12, 13, 14, 15, 16, 17, 18, 20, 22, 23, 24, 25], "menu": [1, 2, 4, 6, 7, 8, 9, 10, 11, 14, 15, 18, 21, 25], "touch": [1, 8, 9, 12, 13, 15], "button": [1, 2, 6, 8, 14, 15, 17], "upper": [1, 7], "right": [1, 7, 9, 11, 12, 16, 21, 25], "side": [1, 9, 10], "screen": [1, 7, 8, 11, 12, 13, 15, 18], "choos": [1, 4, 6, 7, 8, 9, 11, 12, 14, 18, 21, 25], "item": [1, 4, 6, 7, 9, 11, 12, 15, 18, 21], "page": [1, 2, 7, 8, 9, 10, 11, 14, 25], "fill": [1, 4, 13], "everi": [1, 10, 21, 24], "present": [1, 4, 6, 7, 13, 14, 21], "version": [1, 4, 8, 9, 17, 19, 20, 21, 22, 24, 26], "futur": [1, 10, 17, 21, 24], "request": 1, "tap": [1, 2, 7, 9, 11, 15, 18, 26], "click": [1, 2, 4, 5, 6, 7, 11, 15], "arrow": [1, 2, 15], "symbol": [1, 2, 7, 15], "back": [1, 8, 18], "leav": [1, 8, 9, 17, 18], "return": [1, 8, 21, 25], "main": [1, 2, 3, 4, 6, 7, 8, 9, 10, 11, 12, 14, 17, 18, 24, 25, 26], "now": [1, 2, 19], "readi": [1, 2, 21], "go": [1, 4, 7, 8, 10, 11, 18, 25, 26], "There": [1, 2, 3, 4, 7, 10, 24], "thing": [1, 2, 10, 21], "could": [1, 21], "up": [1, 2, 8, 10, 13, 15, 18], "stage": 1, "look": [1, 2, 7, 12, 15, 18, 25], "around": [1, 10, 12, 15, 16, 24], "next": [1, 2, 7, 12, 15, 21, 26], "section": [1, 2, 7, 9, 10, 15, 21], "take": [1, 2, 4, 5, 7, 8, 10, 21, 26], "first": [1, 10, 12, 15, 21, 25, 26], "gener": [2, 4, 9, 10, 13, 16, 17, 20, 21, 22, 24], "oper": [2, 3, 10, 15, 17, 21, 23, 26], "veri": [2, 15, 17, 18, 25], "intuit": 2, "still": [2, 4, 7, 15], "make": [2, 8, 9, 10, 17, 21, 26], "yourself": [2, 7, 21, 25], "basic": [2, 14, 21], "its": [2, 4, 5, 14, 15, 21, 23], "cover": [2, 3, 4, 10, 16, 17, 21, 25, 26], "detail": [2, 4, 6, 7, 8, 9, 10, 12, 15, 16, 21, 23], "startup": 2, "show": [2, 7, 8, 9, 10, 12, 13, 14, 15, 16, 18, 21, 23, 24, 25, 26], "similar": [2, 8, 15, 17, 18, 21, 26], "style": [2, 4, 20, 22, 26], "icao": [2, 4, 7, 12, 13, 15, 26], "gestur": 2, "zoom": [2, 4, 13, 15], "pan": [2, 15], "figur": [2, 9, 10, 15], "ground": [2, 15, 18], "how": [2, 7, 8, 10, 15, 21, 25], "typic": [2, 7, 9, 10, 11, 12, 15, 18, 21, 25], "initi": [2, 7, 21], "posit": [2, 6, 7, 9, 10, 12, 23, 24, 26], "blue": [2, 13], "circl": [2, 10, 13, 15], "grai": 2, "system": [2, 4, 7, 10, 14, 17, 21, 26], "yet": 2, "acquir": [2, 17, 21], "shape": 2, "path": [2, 7, 13, 15, 26], "vector": [2, 4, 15], "project": [2, 4, 5, 15, 16, 20, 22, 26], "track": [2, 15], "five": [2, 15, 26], "size": [2, 4, 12, 15], "each": [2, 7, 15, 21], "black": [2, 13, 15], "white": [2, 12, 15], "segment": [2, 15], "correspond": [2, 15, 21], "one": [2, 3, 4, 7, 9, 10, 15, 17, 18, 21, 24], "when": [2, 7, 8, 9, 12, 13, 15, 17, 18, 21], "probabl": [2, 18], "bright": [2, 18], "red": [2, 7, 12, 13, 15], "lower": 2, "left": [2, 15], "corner": [2, 7], "indic": [2, 10, 13, 15, 21, 24], "traffic": [2, 9, 16, 17, 18, 26], "receiv": [2, 8, 9, 15, 17, 18, 21, 26], "bottom": [2, 7, 14, 15, 18], "panel": [2, 4, 10, 15], "code": [2, 5, 7, 10, 12, 21, 26], "talt": 2, "true": [2, 15, 18], "altitud": [2, 9, 10, 13, 15, 19, 24], "geometr": [2, 9, 15, 24], "abov": [2, 15, 18, 21, 24], "sea": [2, 15, 18, 24], "level": [2, 4, 15, 18, 24], "fl": [2, 15], "g": [2, 15], "speed": [2, 7, 15], "tt": [2, 15], "utc": [2, 15], "onli": [2, 7, 8, 9, 10, 13, 15, 16, 17, 18, 20, 21, 22, 24, 25], "powerflarm": [2, 10, 15], "report": [2, 6, 7, 9, 10, 11, 12, 13, 15, 16, 18, 24], "pressur": [2, 15, 24], "hidden": [2, 15], "wide": [2, 15, 21, 24], "enough": [2, 10, 15], "vertic": [2, 8, 10, 13, 15], "boundari": [2, 13, 15, 18], "defin": [2, 15, 21], "respect": [2, 7, 15, 21], "qnh": [2, 12, 15], "temperatur": [2, 15, 18], "air": [2, 9, 10, 15, 24], "densiti": [2, 15], "differ": [2, 4, 12, 13, 15, 21, 24], "never": [2, 15, 18], "judg": [2, 15], "distanc": [2, 6, 7, 8, 10, 12, 15, 24, 26], "In": [2, 3, 4, 8, 9, 10, 11, 15, 16, 18, 20, 21, 22, 23, 24, 25, 26], "addit": [2, 3, 6, 7, 9, 10, 15, 16, 18, 21, 26], "pinch": [2, 15], "function": [2, 4, 7, 15, 21, 23, 26], "switch": [2, 10, 15, 17, 18, 24], "between": [2, 7, 9, 11, 15, 21, 24], "north": [2, 15, 16, 24], "center": [2, 12, 15, 23, 26], "out": [2, 9, 15, 21, 26], "A": [2, 7, 13, 15, 21, 24, 26], "statu": [2, 8, 9, 10, 15, 21], "doubl": [2, 4, 7, 13, 15, 20, 22, 26], "hold": [2, 7, 11, 15], "anywher": [2, 15, 17], "obtain": [2, 15, 24], "situat": [2, 4, 7, 15], "point": [2, 6, 7, 10, 11, 13, 15, 16, 23, 25], "If": [2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 15, 17, 18, 21, 26], "navaid": [2, 6, 7, 11, 13, 15, 16, 26], "edf": [2, 15], "airport": [2, 12, 13, 15], "simpl": [2, 9, 18, 26], "think": [2, 26], "cours": [2, 15, 26], "further": [2, 5, 7, 9, 21], "aviat": [3, 4, 5, 7, 10, 12, 15, 19, 20, 23, 24, 25, 26], "larg": [3, 4, 26], "part": [3, 4, 21, 26], "world": [3, 4, 16, 26], "frequent": [3, 4, 10, 12], "format": [3, 7, 9, 11, 17, 20, 21, 22, 24], "club": [3, 5, 19, 26], "featur": [3, 4, 7, 8, 15, 16, 18, 21, 26], "member": [3, 19], "highlight": [3, 8, 9, 10], "nois": 3, "sensit": 3, "area": [3, 16, 21], "local": [3, 18, 20, 21, 22, 23], "agreement": [3, 20, 21, 22], "transfer": [3, 4, 7, 9, 11, 21], "web": [3, 4, 9, 10, 23, 24, 25], "browser": [3, 4, 10], "offer": [3, 4, 7, 10, 16, 17, 21], "copi": [3, 4, 21], "afterward": [3, 4], "drag": [3, 4, 7, 11], "drop": [3, 4, 7, 11], "window": [3, 4, 7, 9, 11, 12, 13, 15, 17, 21, 25], "base": [4, 9, 20, 21, 26], "where": [4, 7, 9, 17, 21, 24, 25], "would": [4, 15, 18, 21], "some": [4, 7, 9, 10, 16, 17, 21], "prefer": [4, 7, 9, 11, 17, 18, 21, 24], "chart": [4, 15], "countri": [4, 12, 15, 16, 21, 25], "instal": [4, 7, 9, 10, 15, 18, 20, 21, 25, 26], "high": [4, 13, 16, 18], "region": [4, 16, 18, 25], "interest": [4, 17, 18, 21], "abl": [4, 7, 10, 11, 17, 18, 25], "file": [4, 7, 11, 20, 21, 22, 23], "openmaptil": [4, 20], "schema": 4, "render": [4, 21], "same": [4, 9, 10, 13, 18, 21, 24], "possibl": [4, 7, 11, 17, 21, 24], "along": [4, 12, 13, 21], "order": [4, 9, 10, 12, 18, 21, 23, 24, 25], "higher": [4, 15, 18], "unrespons": 4, "few": [4, 7, 10, 17], "second": [4, 10, 15, 18, 24], "note": [4, 12, 16, 20, 22, 26], "intern": [4, 20, 22], "directori": 4, "space": 4, "delet": [4, 7], "awar": [4, 9, 24, 25], "let": [4, 25], "u": [4, 9, 12, 16, 19, 23, 25], "know": [4, 7, 10, 21, 25], "maptil": 4, "excel": 4, "alongsid": 4, "specif": [4, 7, 17, 20, 21, 22, 23, 24, 26], "flightmap": [4, 16, 20, 25], "european": [4, 16, 25], "well": [4, 9, 10, 12, 21, 24, 25, 26], "south": [4, 16], "africa": [4, 16], "namibia": [4, 16], "handl": [4, 7, 10, 20, 22, 24], "tool": [4, 21], "convert": 4, "denmark": [4, 16], "danish": 4, "aim": [4, 21], "naviair": 4, "spain": [4, 16], "spanish": [4, 19], "insignia": 4, "servicio": [4, 23], "de": [4, 5, 23], "informaci\u00f3n": [4, 23], "aeron\u00e1utica": 4, "switzerland": [4, 16], "swiss": 4, "feder": [4, 23], "offic": 4, "topographi": 4, "swisstopo": 4, "vfr": [4, 12, 18], "unit": [4, 12, 15, 16], "state": [4, 12, 16, 21], "administr": [4, 16, 23], "successfulli": 4, "qgi": 4, "which": [4, 7, 9, 11, 18, 21, 24, 25], "sinc": [4, 18, 19], "easi": 4, "kindli": 4, "short": [4, 17], "tutori": 4, "On": [4, 7, 11, 15], "fedora": 4, "found": [4, 9, 10, 15, 18, 23], "packag": [4, 21], "default": 4, "repositori": [4, 20, 22], "were": [4, 16, 21], "lack": 4, "instruct": [4, 9], "full": [4, 7, 12, 26], "program": [4, 7, 11, 14, 17, 19, 21, 25, 26], "creat": [4, 16, 24], "new": [4, 16, 20, 21, 22], "content": [4, 17, 21], "should": [4, 9, 10, 17, 18, 21, 24], "visibl": [4, 7, 10, 12, 15, 18, 21], "properti": [4, 21], "dialog": [4, 6, 7, 9, 11, 12], "coordin": [4, 7, 11, 23], "refer": [4, 7, 15, 18, 20, 21, 22], "epsg": 4, "3857": 4, "text": [4, 9, 12, 15, 17, 18, 25], "field": [4, 7, 8, 9, 11, 13, 15, 18, 24], "filter": 4, "search": 4, "under": [4, 9, 16, 18, 20, 21, 23], "view": [4, 13, 21], "ensur": [4, 17, 21, 23, 25], "layer": [4, 16, 17], "select": [4, 7, 8, 9, 10, 13, 15, 16, 18, 25, 26], "Then": [4, 8], "resampl": 4, "bilinear": 4, "better": 4, "imag": [4, 7, 15], "qualiti": [4, 16, 21], "toolbox": 4, "insid": [4, 13, 15, 21], "xyz": 4, "tile": [4, 16], "paramet": [4, 9], "seen": [4, 13, 24], "below": [4, 5, 8, 12, 15, 16, 17, 18, 21, 25], "draw": 4, "canva": 4, "specifi": [4, 21, 24], "extent": [4, 15, 21], "pai": 4, "attent": 4, "maximum": 4, "increas": [4, 18], "significantli": 4, "12": [4, 9, 21], "number": [4, 9, 10, 15, 18, 21, 24], "commerci": [5, 8, 9, 21, 24], "akaflieg": [5, 19, 26], "freiburg": [5, 7, 19, 23, 26], "support": [5, 8, 10, 17, 19, 20, 21, 22], "univers": [5, 20, 22, 23], "enthusiast": [5, 19, 26], "written": [5, 13, 19, 21, 26], "spare": [5, 21], "servic": [5, 7, 8, 21, 23], "commun": [5, 6, 7, 9, 13, 17, 21], "develop": [5, 14, 21], "appreci": 5, "consid": [5, 21], "tax": 5, "privileg": 5, "profit": 5, "public": [5, 20, 21, 22], "util": 5, "germani": [5, 16, 19, 23, 26], "promot": 5, "recreat": 5, "sport": 5, "fund": [5, 16], "infrastructur": 5, "deduct": 5, "contact": [5, 9], "info": [5, 7, 9, 14], "statement": [5, 21], "here": [5, 9], "scan": 5, "qr": 5, "iban": 5, "de35": 5, "6809": 5, "0000": 5, "0027": 5, "6409": 5, "07": 5, "bic": 5, "genode61fr1": 5, "volksbank": 5, "messag": [5, 9, 15, 17, 24], "weather": [6, 18, 19, 20, 22, 23, 26], "turn": [6, 26], "bad": [6, 26], "help": [6, 7, 13, 14, 17, 19], "best": [6, 10, 15], "place": [6, 21, 23], "land": [6, 11, 16, 26], "list": [6, 7, 8, 9, 11, 12, 20, 21, 22], "closest": [6, 12, 26], "aerodrom": [6, 13], "togeth": [6, 15, 18, 23], "direct": [6, 7, 15, 21, 26], "runwai": [6, 13, 26], "frequenc": [6, 13, 26], "replac": [6, 17], "rout": [6, 11, 12, 13, 17, 23, 25, 26], "bring": 6, "directli": [6, 7, 21], "close": [6, 8, 10, 15, 21, 24], "apart": 6, "tab": [6, 7, 9, 14], "essenti": [7, 9, 18, 21], "move": [7, 8, 9, 10, 11, 25, 26], "travel": 7, "fuel": [7, 26], "consumpt": [7, 26], "estim": [7, 15, 24, 26], "soon": [7, 8, 9, 12, 15, 17], "magenta": 7, "line": [7, 13, 15], "thin": 7, "infobox": 7, "et": [7, 15, 23], "eta": [7, 15], "final": [7, 15, 21, 25], "box": [7, 8, 9], "airborn": 7, "closer": 7, "three": [7, 10, 11, 21], "nautic": 7, "mile": [7, 12], "destin": [7, 15], "chapter": 7, "through": [7, 17, 21], "cruis": 7, "enter": [7, 9, 21, 23], "piec": [7, 15, 21], "check": [7, 8, 9, 10, 13, 18, 23, 26], "again": 7, "encount": 7, "dure": 7, "want": [7, 21], "sever": [7, 11, 24], "name": [7, 10, 11, 12, 13, 15, 17, 21, 24], "import": [7, 21, 25, 26], "librari": [7, 10, 15, 18, 20, 21, 22, 24, 26], "gpx": [7, 11, 17, 25], "explain": [7, 8, 9, 10, 12, 15, 21], "four": [7, 14], "method": [7, 21, 24], "add": [7, 21, 25], "letter": 7, "edtf": [7, 10, 15], "narrow": 7, "desir": [7, 10], "descript": [7, 11, 15, 17], "sign": 7, "append": 7, "discard": 7, "given": [7, 9, 13, 17, 21], "alreadi": [7, 9, 10, 21], "minu": 7, "remov": [7, 21], "onlin": [7, 10, 25], "fl95": 7, "allow": [7, 9, 11, 12, 18, 21, 23, 24, 26], "bluetooth": [7, 10, 11], "drive": [7, 11], "send": [7, 9, 24], "e": [7, 11, 14, 15, 20, 21, 22, 23], "mail": [7, 11, 14], "channel": [7, 17, 24], "suffic": [7, 21], "perhap": [7, 11, 25], "client": [7, 10, 11], "automat": [7, 9, 10, 15, 18, 21], "global": [7, 16], "dot": [7, 11], "revers": 7, "entir": [7, 21], "pre": 7, "pencil": 7, "happi": 7, "write": [7, 9, 11, 17, 21], "geojson": [7, 11, 17], "understood": [7, 11], "instanc": [7, 11, 20, 22], "top": [7, 11, 12, 15, 17], "type": [7, 8, 11, 15, 17], "submenu": [7, 11], "anti": [8, 20, 21, 22], "collis": [8, 10, 15], "real": [8, 18], "premium": 8, "integr": [8, 10, 19, 24], "nearbi": [8, 10, 12, 15, 24, 26], "factor": [8, 10, 24], "less": [8, 10, 15, 20, 22], "500": [8, 10, 12, 18], "m": [8, 10], "horizont": [8, 10, 15], "20": [8, 10, 16, 21], "nm": [8, 10], "therefor": [8, 17, 18, 21], "substanti": [8, 21], "issu": [8, 10, 15, 18], "warn": [8, 10, 15, 18], "avoid": [8, 10, 11, 15, 21], "algorithm": [8, 10, 15, 20, 22], "configur": [8, 9, 10, 20, 25], "forward": [8, 14], "sure": [8, 9, 10, 21], "subscript": 8, "safe": [8, 10, 18], "sky": 8, "option": [8, 9, 10, 17, 18, 21], "That": 8, "off": [8, 15, 17, 18, 25], "background": 8, "entri": [8, 9, 10, 12, 13, 18], "green": [8, 9, 10, 12, 13, 15], "congratul": [8, 10], "done": [8, 9, 10, 12, 25, 26], "establish": [8, 10, 15, 24], "setup": [9, 26], "correctli": 9, "sent": 9, "wifi": 9, "test": [9, 10, 17], "success": [9, 10], "2": [9, 15, 16, 20, 21, 22, 25, 26], "4": [9, 20, 21, 22], "10": [9, 16, 21, 24], "treat": [9, 21], "assum": [9, 21, 25], "home": 9, "both": [9, 19, 21], "wi": [9, 18, 24], "fi": [9, 18, 24], "network": [9, 21, 24], "deploi": [9, 10, 24], "router": 9, "met": [9, 10, 21], "built": [9, 17, 18], "satnav": [9, 15, 18], "ignor": [9, 17], "two": [9, 10, 15, 21], "call": [9, 21, 24], "guest": 9, "secur": [9, 10, 20, 22], "disallow": [9, 12], "broadcast": [9, 18], "over": [9, 16], "adjust": 9, "accordingli": 9, "end": [9, 13], "miscellan": 9, "activ": [9, 13, 21], "ip": [9, 23, 24], "address": [9, 19, 21, 23, 24], "correct": [9, 19, 21], "our": [9, 16, 21, 23, 25], "though": [9, 21], "socket": 9, "1": [9, 12, 15, 16, 17, 18, 20, 21, 22, 24, 25, 26], "255": 9, "49002": [9, 24], "udp": [9, 24], "foreflight": 9, "xgp": [9, 24], "httpd": 9, "8080": 9, "efb": 9, "connector": 9, "fs2ff": 9, "xmapsi": 9, "inexpens": 9, "barometr": [9, 24], "v3": [9, 20, 21, 22], "expens": 9, "site": [9, 12, 24, 25], "commer": 9, "msfs2020": 9, "cold": 9, "dark": [9, 18], "avion": [9, 10, 23], "04aug21": 9, "tail": 9, "due": 9, "complic": 9, "just": [9, 19, 20, 22], "latest": 9, "releas": [9, 17, 21], "anyth": [9, 21], "ad": [9, 15, 21, 24], "b": [9, 15, 21, 24], "gdl90": [9, 10], "technologi": [9, 10, 17, 24], "simconnect": 9, "ownship": [9, 24], "msl": 9, "verifi": 9, "determin": [9, 21], "except": [9, 16, 21], "experi": [9, 17, 18], "group": [9, 18, 20, 22], "role": 9, "hand": 9, "iphon": 9, "ipad": 9, "extern": 9, "headlin": 9, "datagram": [9, 24], "port": [9, 19, 24], "4000": [9, 24], "choic": [9, 21], "midair": 10, "reason": [10, 21], "happen": 10, "circuit": [10, 13, 15, 16, 26], "enhanc": 10, "flarm": [10, 15, 17, 24], "approach": [10, 13, 15, 18, 25], "what": [10, 21], "downwind": 10, "approxim": [10, 18, 21, 24], "sink": 10, "color": [10, 12, 13, 20, 22], "alarm": [10, 15], "whose": [10, 15, 18, 21, 24], "precis": [10, 15, 21, 24], "unknown": [10, 15, 24], "case": [10, 12, 15, 21], "transpond": [10, 15, 24], "within": [10, 12, 13, 21], "yellow": [10, 12, 15, 18], "danger": [10, 15, 21], "accord": [10, 12, 15, 21, 24], "modern": 10, "compliant": 10, "AT": 10, "core": 10, "ltd": [10, 24], "adaptor": 10, "fusison": 10, "pilotawar": 10, "rosetta": 10, "skyecho2": 10, "known": [10, 15, 18], "skyecho": 10, "pingusb": 10, "stratux": [10, 24], "ttgo": 10, "beam": 10, "concurr": 10, "passeng": 10, "disabl": [10, 11, 18], "board": 10, "For": [10, 11, 13, 16, 20, 21, 22, 25], "result": [10, 21, 24], "nmea": [10, 24], "output": [10, 21, 24], "protocol": [10, 18, 21, 24], "shortcom": [10, 24], "properli": 10, "detect": 10, "whenev": [10, 24], "try": 10, "interfac": [10, 19, 21, 24], "act": 10, "wireless": 10, "access": [10, 12, 14, 18, 21, 24], "ssid": 10, "encrypt": [10, 24], "password": [10, 21], "wait": 10, "internet": [10, 12, 16, 17, 18, 23], "confirm": [10, 25], "wish": [10, 21, 25], "rememb": [10, 18], "break": 10, "serv": [10, 21], "abort": 10, "random": 10, "tri": 10, "friend": 10, "pocket": 10, "databas": [10, 15, 16, 20, 22], "identifi": [10, 12, 13, 21], "registr": 10, "interact": [10, 21, 26], "build": [11, 20], "small": [11, 18], "tourist": 11, "landmark": 11, "hohenzollern": 11, "castl": 11, "emerg": 11, "thousand": [11, 25], "consider": 11, "onto": 11, "assign": 11, "edit": 11, "duplic": 11, "cup": 11, "altern": [11, 21], "metar": [12, 23], "taf": [12, 23], "forecast": 12, "govern": [12, 15, 16, 21, 23], "assess": 12, "meteorolog": [12, 18], "bodi": [12, 15, 21], "station": [12, 13], "85nm": 12, "pictur": 12, "quj": 12, "summari": 12, "classifi": 12, "categori": [12, 24], "scheme": 12, "tabl": [12, 15], "impli": [12, 21], "advis": [12, 21], "legal": [12, 21], "ceil": 12, "low": [12, 15], "ifr": 12, "feet": 12, "agl": [12, 15, 18], "000": [12, 15], "3": [12, 13, 16, 20, 21, 22, 25], "margin": [12, 18], "5": [12, 16, 18, 21, 24], "bear": [12, 15], "decod": 12, "translat": 12, "scroll": 12, "read": [12, 18, 21, 23, 24], "sunset": 12, "sunris": 12, "remain": [12, 15, 21], "until": [12, 21], "privaci": [12, 26], "concern": [12, 17, 21, 23], "common": [13, 20, 21, 22], "symbologi": 13, "structur": 13, "arbitrari": 13, "waypoint": [13, 15, 23, 26], "pop": 13, "techniqu": 13, "limit": [13, 15, 21, 25, 26], "special": [13, 21, 24], "surround": 13, "intens": 13, "dash": 13, "thick": 13, "transpar": [13, 15, 25], "relat": 13, "solid": 13, "class": [13, 16, 20, 21, 22], "d": [13, 21, 23], "atc": 13, "clearanc": 13, "ctr": 13, "tmz": 13, "outlin": [13, 15, 24], "monitor": 13, "squawk": 13, "rmz": 13, "exercis": [13, 21], "pje": 13, "nra": 13, "plan": [13, 15, 23, 25, 26], "exampl": [13, 21], "austria": [13, 16], "rule": [13, 21], "com": [13, 19], "orient": [13, 15], "dimens": 13, "surfac": 13, "elev": [13, 15, 16, 26], "associ": [13, 21], "departur": 13, "triangl": 13, "motor": [13, 19], "glider": [13, 15, 18, 19], "ultralight": 13, "exit": 13, "licens": [14, 16, 20, 22, 26], "share": [14, 21], "word": 15, "autopan": 15, "describ": [15, 26], "behavior": 15, "rotat": 15, "paper": 15, "movement": 15, "tabular": 15, "tc": 15, "dist": 15, "arriv": [15, 17], "chosen": 15, "becaus": [15, 18, 21, 23], "too": [15, 21], "far": 15, "awai": [15, 21], "brief": 15, "error": [15, 17], "Near": 15, "physic": [15, 21], "shade": 15, "terrain": [15, 18], "relief": [15, 16], "overlaid": 15, "valu": [15, 20, 22], "50": 15, "zone": [15, 16, 18, 26], "procedur": [15, 16, 21, 26], "aeronaut": [15, 26], "remind": [15, 18], "9500": 15, "ft": [15, 18], "give": [15, 21, 24, 26], "rough": 15, "scale": [15, 20, 22], "copyright": [15, 16, 21], "notic": [15, 20, 21, 22], "dialogu": [15, 25], "mous": 15, "wheel": 15, "quickest": 15, "equival": [15, 21], "promin": [15, 21], "500m": 15, "20nm": 15, "predict": 15, "13": [15, 21, 24], "18": 15, "kind": [15, 21], "transmitt": 15, "airship": 15, "balloon": 15, "copter": 15, "drone": 15, "hang": 15, "jet": 15, "paraglid": 15, "skydiv": 15, "static": [15, 24], "obstacl": 15, "tow": 15, "plane": [15, 18, 19], "callsign": 15, "rel": [15, 24], "upward": 15, "downward": 15, "sidewai": 15, "alt": 15, "made": [15, 21], "abbrevi": 15, "amsl": [15, 18], "offlin": [16, 26], "streetmap": 16, "deriv": 16, "dataset": 16, "amazon": 16, "aw": 16, "underli": 16, "mix": 16, "3dep": 16, "formerli": 16, "ned": 16, "topobathi": 16, "meter": 16, "outsid": [16, 21], "alaska": 16, "territori": 16, "water": 16, "arcticdem": 16, "strip": 16, "mosaic": 16, "across": [16, 21], "60": [16, 21], "latitud": 16, "canada": 16, "greenland": 16, "iceland": 16, "norwai": 16, "russia": 16, "sweden": 16, "cdem": 16, "canadian": 16, "digit": [16, 17], "model": [16, 17, 20, 21, 22, 24], "variabl": 16, "spatial": 16, "resolut": 16, "400": 16, "gov": [16, 23], "uk": 16, "kingdom": 16, "gv": 16, "etopo1": 16, "ocean": 16, "bathymetri": 16, "arc": 16, "eudem": 16, "europ": 16, "30": [16, 17, 21], "albania": 16, "belgium": 16, "bosnia": 16, "herzegovina": 16, "bulgaria": 16, "croatia": 16, "cypru": 16, "czechia": 16, "estonia": 16, "finland": 16, "franc": 16, "greec": 16, "hungari": 16, "ireland": 16, "itali": 16, "kosovo": 16, "latvia": 16, "liechtenstein": 16, "lithuania": 16, "luxembourg": 16, "macedonia": 16, "malta": 16, "montenegro": 16, "netherland": 16, "poland": 16, "portug": 16, "romania": 16, "serbia": 16, "slovakia": 16, "slovenia": 16, "geoscienc": 16, "australia": 16, "dem": [16, 23], "coastal": 16, "victoria": 16, "northern": 16, "gmted": 16, "coarser": 16, "7": [16, 17, 21, 24], "15": [16, 19, 21], "inegi": 16, "continent": 16, "mexico": 16, "kartverket": 16, "linz": 16, "8": [16, 21], "zealand": 16, "srtm": 16, "90": [16, 24], "nomin": 16, "digitalglob": 16, "inc": [16, 21], "imageri": 16, "nation": 16, "scienc": 16, "foundat": [16, 21], "award": 16, "1043681": 16, "1559691": 16, "1542736": 16, "commonwealth": 16, "2017": 16, "offen": 16, "daten": [16, 23], "\u00f6sterreich": 16, "digital": 16, "gel\u00e4ndemodel": 16, "dgm": 16, "licenc": [16, 20, 22], "produc": [16, 21], "copernicu": 16, "union": 16, "atmospher": 16, "2016": [16, 20, 22], "2011": 16, "crown": 16, "c": [16, 20, 21, 22], "reserv": 16, "environ": 16, "agenc": 16, "2015": 16, "gmted2010": 16, "courtesi": 16, "geolog": 16, "survei": 16, "per": [16, 18, 23], "dai": [16, 21], "howev": [16, 21, 23, 24], "regular": [16, 17], "compil": [16, 20, 21, 22], "openaip": [16, 20], "fewer": 16, "natur": [16, 21], "preserv": [16, 21], "simplic": 16, "divid": 16, "complet": [16, 25, 26], "mandatori": 16, "control": [16, 18, 21, 23, 24, 26], "thei": [16, 20, 21, 24, 25], "contin": 16, "canari": 16, "island": 16, "madagascar": 16, "asia": 16, "bahrain": 16, "emir": 16, "japan": 16, "qatar": 16, "oceanica": 16, "czech": 16, "republ": 16, "great": 16, "britain": 16, "slowenia": 16, "america": 16, "argentina": 16, "brazil": 16, "miss": 16, "colombia": 16, "falkland": 16, "transport": 17, "tl": 17, "server": [17, 20, 21, 22, 23], "manufactur": [17, 21], "regretfulli": 17, "sale": [17, 21], "expir": 17, "longer": 17, "media": 17, "septemb": 17, "2021": 17, "stop": 17, "hide": [17, 18], "complex": 17, "silent": 17, "revert": [17, 18], "insecur": [17, 18], "appear": [17, 18], "normal": [17, 21], "eventu": 17, "tamper": 17, "manipul": 17, "decis": 17, "recent": 17, "who": [17, 18, 21, 25], "risk": [17, 21], "fairphon": 17, "person": [17, 21, 23], "repair": [17, 21], "easili": [17, 26], "year": [17, 19, 21], "brand": 17, "overrid": 17, "hardwar": [17, 26], "stai": 17, "immedi": 17, "unlock": 17, "heartbeat": 17, "listen": [17, 24], "txt": 17, "rather": 17, "unix": 17, "h": 17, "commandlin": 17, "qt": [17, 20, 22], "v": 17, "sg": 17, "simul": [17, 18, 24, 26], "screenshot": 17, "sm": 17, "deliber": 18, "chang": [18, 21, 24], "000ft": 18, "fl100": 18, "improv": 18, "readabl": [18, 21], "unset": 18, "9": [18, 21], "gradient": 18, "ampl": 18, "safeti": 18, "difficult": 18, "experienc": 18, "graphic": 18, "old": [18, 20, 22], "appli": [18, 21], "chose": 18, "height": [18, 24], "unsur": 18, "enlarg": 18, "perform": [18, 20, 21, 22], "ey": 18, "adapt": [18, 21], "quit": 18, "inde": 18, "them": [18, 21, 24], "everybodi": 18, "either": [18, 21, 24], "recept": 18, "actual": [18, 21, 23], "fall": 18, "attempt": [18, 21], "uncheck": 18, "polici": [18, 20, 22, 26], "enforc": [18, 21], "wa": [19, 21], "stefan": [19, 23], "kebeku": [19, 23], "1986": 19, "fli": 19, "wintererstra\u00df": [19, 23], "77": [19, 23], "79104": [19, 23], "gmail": 19, "io": 19, "simon": 19, "schneider": 19, "student": 19, "ppl": 19, "heinz": 19, "bl\u00f6chinger": 19, "openair": 19, "alpin": 19, "glide": 19, "big": 19, "dream": 19, "helicopt": 19, "french": 19, "adrien": 19, "crovato": 19, "luca": 19, "riva": 19, "privat": [19, 21], "aerospac": 19, "engin": 19, "aerobat": 19, "german": 19, "marku": 19, "sach": 19, "trike": 19, "co": 19, "everyt": 19, "els": 19, "italian": 19, "ivan": 19, "battistella": 19, "antonio": 19, "fardella": 19, "naval": 19, "passion": 19, "everyth": 19, "challeng": 19, "polish": 19, "s\u0142awek": 19, "miku\u0142a": 19, "bertoncello": 19, "michael": 19, "horbaschk": 19, "szymon": 19, "kocur": 19, "heiner": 19, "tholen": 19, "johann": 19, "zellner": 19, "geoid": 19, "numerour": 20, "compon": [20, 21], "heavili": 20, "runtim": 20, "modifi": [20, 21], "cc": 20, "BY": [20, 21], "0": [20, 21, 22], "nc": 20, "sa": 20, "ofma": 20, "adob": [20, 22], "glyph": [20, 22], "font": [20, 22], "bsd": [20, 22], "claus": [20, 22], "revis": [20, 21, 22], "alias": [20, 22], "raster": [20, 22], "freetyp": [20, 22], "gnu": [20, 21, 22], "v2": [20, 22], "bitstream": [20, 22], "vera": [20, 22], "blake2": [20, 22], "implement": [20, 21, 22, 24], "creativ": [20, 22], "zero": [20, 22], "v1": [20, 22], "apach": [20, 22], "catch2": [20, 22], "boost": [20, 22], "clip2tri": [20, 22], "polygon": [20, 22], "triangul": [20, 22], "mit": [20, 22, 23], "clipper": [20, 22], "clip": [20, 22], "cocoa": [20, 22], "plugin": [20, 22, 25], "cycl": [20, 22], "compress": [20, 22], "zlib": [20, 22], "dejavu": [20, 22], "earcut": [20, 22], "isc": [20, 22], "earth": [20, 22], "gravit": [20, 22], "domain": [20, 21, 22], "eas": [20, 22], "equat": [20, 22], "robert": [20, 22], "penner": [20, 22], "effici": [20, 22], "binari": [20, 22], "decim": [20, 22], "convers": [20, 22], "routin": [20, 22], "ieee": [20, 22], "extra": [20, 22], "cmake": [20, 22], "modul": [20, 22], "fontawesom": [20, 22], "sil": [20, 22], "forkfd": [20, 22], "bitmap": [20, 22], "bdf": [20, 22], "portabl": [20, 22], "pcf": [20, 22], "variant": [20, 22], "geosimplifi": [20, 22], "j": [20, 22], "polylin": [20, 22], "simplif": [20, 22], "materi": [20, 21, 22], "icon": [20, 22], "gradl": [20, 22], "wrapper": [20, 22], "guidelin": [20, 22], "harfbuzz": [20, 22], "ng": [20, 22], "iaccessible2": [20, 22], "idl": [20, 22], "javascriptcor": [20, 22], "macro": [20, 22], "assembl": [20, 22], "simplifi": [20, 22], "jqueri": [20, 22], "kdab": [20, 22], "helper": [20, 22], "singl": [20, 21, 22], "kwin": [20, 22], "libdu": [20, 22], "header": [20, 22], "academ": [20, 22], "later": [20, 21, 22], "libjpeg": [20, 22], "turbo": [20, 22], "independ": [20, 21, 22], "jpeg": [20, 22], "libpng": [20, 22], "png": [20, 22], "libpsl": [20, 22], "suffix": [20, 22], "event": [20, 21, 22], "syscal": [20, 22], "lunr": [20, 22], "sphinx": [20, 22], "theme": [20, 22], "md4": [20, 22], "md4c": [20, 22], "md5": [20, 22], "metaf": [20, 22], "nativ": [20, 22], "opengl": [20, 22], "openssl": [20, 22], "osm": [20, 22], "liberti": [20, 22], "pcre2": [20, 22], "stack": [20, 22], "pixman": [20, 22], "poly2tri": [20, 22], "qeventdispatch": [20, 22], "maco": [20, 22], "qhttpengin": [20, 22], "toolkit": [20, 22], "hash": [20, 22], "sha": [20, 22], "brg_endian": [20, 22], "keccak": [20, 22], "384": [20, 22], "512": [20, 22], "shadow": [20, 22], "angular": [20, 22], "siphash": [20, 22], "smooth": [20, 22], "imlib2": [20, 22], "sqlite": [20, 22], "srgb": [20, 22], "profil": [20, 22], "icc": [20, 22], "consortium": [20, 22], "tango": [20, 22], "pack": [20, 22], "darkobra": [20, 22], "mozilla": [20, 22], "tiff": [20, 22], "libtiff": [20, 22], "tinycbor": [20, 22], "underscor": [20, 22], "unicod": [20, 22], "charact": [20, 22], "ucd": [20, 22], "cldr": [20, 22], "valgrind": [20, 22], "origin": [20, 21, 22], "vulkan": [20, 22], "api": [20, 22, 23], "registri": [20, 22], "memori": [20, 22], "alloc": [20, 22], "webgradi": [20, 22], "webp": [20, 22], "libwebp": [20, 22], "wintab": [20, 22], "lc": [20, 22], "telegraph": [20, 22], "x": [20, 22], "x11": [20, 22], "histor": [20, 22], "disclaim": [20, 21, 22], "xcb": [20, 22], "xinput": [20, 22], "xsvg": [20, 22], "sell": [20, 21, 22], "29": 21, "june": 21, "2007": 21, "http": [21, 23], "fsf": 21, "everyon": 21, "permit": [21, 23], "verbatim": 21, "document": [21, 24], "preambl": 21, "copyleft": 21, "practic": 21, "freedom": 21, "By": 21, "contrast": 21, "speak": 21, "price": 21, "charg": 21, "get": 21, "protect": 21, "prevent": 21, "deni": 21, "surrend": 21, "certain": 21, "respons": [21, 23], "whether": 21, "grati": 21, "fee": 21, "pass": 21, "recipi": 21, "And": 21, "gpl": 21, "assert": 21, "clearli": 21, "sake": 21, "mark": [21, 26], "attribut": 21, "erron": 21, "previou": 21, "although": 21, "fundament": 21, "incompat": [21, 24], "systemat": 21, "pattern": 21, "abus": [21, 24], "occur": 21, "individu": 21, "unaccept": 21, "prohibit": 21, "those": 21, "aris": 21, "stand": 21, "provis": [21, 24], "threaten": 21, "constantli": 21, "patent": 21, "restrict": [21, 25], "purpos": [21, 24, 25], "effect": 21, "proprietari": 21, "assur": [21, 23], "modif": 21, "AND": 21, "definit": 21, "law": 21, "semiconductor": 21, "mask": 21, "license": 21, "organ": 21, "fashion": 21, "exact": 21, "earlier": 21, "unmodifi": 21, "propag": 21, "secondarili": 21, "liabl": 21, "infring": 21, "execut": 21, "convei": 21, "enabl": [21, 25], "parti": [21, 26], "mere": 21, "conveni": 21, "criterion": 21, "form": 21, "object": 21, "recogn": 21, "languag": 21, "among": 21, "whole": 21, "context": 21, "kernel": 21, "interpret": [21, 24], "script": 21, "dynam": 21, "link": 21, "subprogram": 21, "intim": 21, "flow": 21, "regener": 21, "irrevoc": 21, "explicitli": 21, "affirm": 21, "unlimit": 21, "constitut": 21, "acknowledg": 21, "fair": 21, "forc": 21, "sole": 21, "exclus": 21, "facil": [21, 26], "thu": 21, "behalf": 21, "relationship": 21, "circumst": 21, "sublicens": 21, "unnecessari": 21, "circumvent": 21, "deem": 21, "technolog": 21, "measur": [21, 24], "oblig": 21, "articl": 21, "11": 21, "wipo": 21, "treati": 21, "adopt": 21, "decemb": 21, "1996": 21, "waiv": 21, "forbid": 21, "intent": 21, "against": 21, "third": [21, 26], "medium": 21, "conspicu": 21, "intact": 21, "absenc": 21, "carri": 21, "date": 21, "anyon": 21, "possess": 21, "regardless": 21, "invalid": 21, "separ": 21, "extens": 21, "combin": 21, "larger": 21, "volum": 21, "storag": [21, 23], "aggreg": 21, "beyond": [21, 23], "inclus": [21, 23], "6": 21, "embodi": 21, "accompani": 21, "fix": 21, "durabl": 21, "customarili": 21, "interchang": 21, "least": [21, 24], "custom": 21, "cost": 21, "occasion": 21, "noncommerci": 21, "subsect": 21, "6b": 21, "maintain": 21, "sai": 21, "host": 21, "satisfi": 21, "peer": 21, "transmiss": 21, "being": 21, "6d": 21, "portion": 21, "exclud": 21, "tangibl": 21, "famili": 21, "household": 21, "sold": 21, "incorpor": 21, "dwell": 21, "doubt": 21, "resolv": 21, "favor": 21, "coverag": 21, "industri": 21, "unless": 21, "repres": 21, "signific": 21, "kei": 21, "interf": 21, "transact": 21, "perpetu": 21, "character": 21, "But": 21, "neither": 21, "nor": 21, "retain": 21, "abil": 21, "rom": 21, "itself": 21, "advers": 21, "affect": 21, "violat": 21, "publicli": 21, "unpack": 21, "supplement": 21, "regard": 21, "notwithstand": 21, "holder": 21, "liabil": 21, "16": 21, "misrepresent": 21, "licensor": 21, "declin": 21, "trademark": 21, "trade": 21, "f": 21, "indemnif": 21, "contractu": 21, "assumpt": 21, "impos": 21, "relicens": 21, "surviv": 21, "expressli": 21, "void": 21, "paragraph": 21, "ceas": 21, "reinstat": 21, "provision": 21, "perman": 21, "notifi": 21, "prior": 21, "cessat": 21, "moreov": 21, "cure": 21, "receipt": 21, "qualifi": 21, "Not": 21, "ancillari": 21, "consequ": 21, "likewis": 21, "noth": 21, "action": 21, "downstream": 21, "subject": 21, "complianc": 21, "entiti": 21, "asset": 21, "subdivid": 21, "merg": 21, "whatev": 21, "predecessor": 21, "had": 21, "effort": 21, "royalti": 21, "litig": 21, "cross": 21, "claim": 21, "counterclaim": 21, "lawsuit": 21, "alleg": 21, "contributor": 21, "hereaft": 21, "manner": 21, "consist": 21, "worldwid": 21, "express": 21, "commit": 21, "denomin": 21, "coven": 21, "sue": 21, "knowingli": 21, "readili": 21, "arrang": 21, "depriv": 21, "benefit": 21, "knowledg": [21, 23], "pursuant": 21, "procur": 21, "convey": 21, "discriminatori": 21, "scope": 21, "busi": [21, 24], "payment": 21, "primarili": 21, "28": 21, "march": 21, "constru": 21, "defens": 21, "court": 21, "contradict": 21, "excus": 21, "simultan": [21, 24], "pertin": 21, "agre": 21, "collect": 21, "whom": 21, "refrain": 21, "affero": 21, "14": 21, "Such": 21, "spirit": 21, "distinguish": 21, "ever": 21, "proxi": 21, "THERE": 21, "NO": 21, "FOR": 21, "THE": 21, "TO": 21, "IN": 21, "OR": 21, "AS": 21, "OF": 21, "BUT": 21, "NOT": 21, "merchant": 21, "fit": 21, "WITH": 21, "prove": 21, "defect": 21, "WILL": 21, "BE": 21, "damag": 21, "incident": 21, "consequenti": 21, "inabl": 21, "BEING": 21, "inaccur": 21, "sustain": 21, "failur": 21, "IF": 21, "SUCH": 21, "17": 21, "review": 21, "absolut": 21, "waiver": 21, "civil": 21, "transmit": 23, "regularli": 23, "respond": 23, "log": 23, "www": 23, "aviationweath": 23, "dataserv": 23, "notam": 23, "faa": 23, "im": 23, "breisgau": 23, "wir": 23, "verarbeiten": 23, "kein": 23, "personenbezogenen": 23, "von": 23, "ihnen": 23, "die": 23, "sie": 23, "dieser": 23, "eingeben": 23, "wie": 23, "zum": 23, "beispiel": 23, "routen": 23, "wegpunkt": 23, "und": 23, "luftfahrzeugdaten": 23, "werden": 23, "nur": 23, "lokal": 23, "auf": 23, "ger\u00e4t": 23, "abgelegt": 23, "nicht": 23, "un": 23, "\u00fcbermittelt": 23, "verarbeitet": 23, "um": 23, "funktionalit\u00e4t": 23, "der": 23, "gew\u00e4hrleisten": 23, "zu": 23, "k\u00f6nnen": 23, "m\u00fcssen": 23, "allerd": 23, "folgend": 23, "sucht": 23, "regelm\u00e4\u00dfig": 23, "nach": 23, "bietet": 23, "m\u00f6glichkeit": 23, "karten": 23, "einem": 23, "universit\u00e4t": 23, "ihr": 23, "herunterzuladen": 23, "dies": 23, "anzubieten": 23, "muss": 23, "adress": 23, "den": 23, "\u00fcbertragen": 23, "ben\u00f6tigt": 23, "ihrem": 23, "antworten": 23, "speichert": 23, "aber": 23, "loggdateien": 23, "di": 23, "gilt": 23, "insbesonder": 23, "f\u00fcr": 23, "zusichern": 23, "weil": 23, "sich": 23, "unter": 23, "unser": 23, "kontrol": 23, "befindet": 23, "zeigt": 23, "landepl\u00e4tz": 23, "nahe": 23, "aktuellen": 23, "standort": 23, "ihrer": 23, "geplanten": 23, "zus\u00e4tzlich": 23, "\u00f6ffnen": 23, "ihren": 23, "geplant": 23, "wegpunktkoordinaten": 23, "webservic": 23, "\u00fcbermitteln": 23, "ben\u00f6tigen": 23, "weiteren": 23, "auslesen": 23, "damit": 23, "rechnen": 23, "dass": 23, "zusammen": 23, "\u00fcbermittelten": 23, "positionsdaten": 23, "gespeichert": 23, "wird": 23, "regierung": 23, "betrieben": 23, "entziehen": 23, "detailliert": 23, "informationen": 23, "finden": 23, "ort": 23, "aktuel": 23, "verantwortlich": 23, "nou": 23, "ne": 23, "traiton": 23, "aucun": 23, "donn\u00e9": 23, "personnel": 23, "vou": 23, "le": 23, "que": 23, "entrez": 23, "dan": 23, "l": 23, "y": 23, "compri": 23, "itin\u00e9rair": 23, "sp\u00e9cificit\u00e9": 23, "sont": 23, "stock\u00e9": 23, "sur": 23, "votr": 23, "appareil": 23, "pa": 23, "transmis": 23, "trait\u00e9": 23, "par": 23, "cepend": 23, "pour": 23, "la": 23, "fonctionnalit\u00e9": 23, "doit": 23, "transmettr": 23, "suivant": 23, "aux": 23, "serveur": 23, "v\u00e9rifi": 23, "r\u00e9guli\u00e8r": 23, "mise": 23, "\u00e0": 23, "jour": 23, "permet": 23, "t\u00e9l\u00e9charger": 23, "cart": 23, "depui": 23, "universit\u00e9": 23, "fribourg": 23, "afin": 23, "fournir": 23, "cett": 23, "\u00eatre": 23, "au": 23, "connaiss": 23, "est": 23, "n\u00e9cessair": 23, "r\u00e9pond": 23, "stock": 23, "se": 23, "fichier": 23, "journaux": 23, "particuli": 23, "il": 23, "pouvon": 23, "car": 23, "sou": 23, "notr": 23, "contr\u00f4l": 23, "affich": 23, "a\u00e9rodrom": 23, "proximit\u00e9": 23, "actuel": 23, "planifi\u00e9": 23, "\u00e9galement": 23, "tou": 23, "ouvrez": 23, "emplac": 23, "coordonn\u00e9": 23, "du": 23, "chemin": 23, "doivent": 23, "transmi": 23, "centr": 23, "r\u00e9pondent": 23, "peuvent": 23, "lire": 23, "autr": 23, "cour": 23, "processu": 23, "devez": 23, "attendr": 23, "ce": 23, "soit": 23, "avec": 23, "exploit\u00e9": 23, "gouvern": 23, "am\u00e9ricain": 23, "\u00e9chappent": 23, "d\u00e9taill\u00e9": 23, "dispon": 23, "lieux": 23, "proch": 23, "administratif": 23, "elaboriamo": 23, "alcun": 23, "dato": 23, "personal": 23, "da": 23, "te": 23, "dati": 23, "che": 23, "inserisci": 23, "nell": 23, "rott": 23, "specifich": 23, "del": 23, "velivolo": 23, "vengono": 23, "memorizzati": 23, "localment": 23, "sul": 23, "tuo": 23, "dispositivo": 23, "ci": 23, "trasmessi": 23, "li": 23, "tuttavia": 23, "garantir": 23, "funzionalit\u00e0": 23, "deve": 23, "trasmetter": 23, "seguenti": 23, "ai": 23, "controlla": 23, "regolarment": 23, "presenza": 23, "aggiornamenti": 23, "consent": 23, "scaricar": 23, "mapp": 23, "dell": 23, "universit\u00e0": 23, "fornir": 23, "questa": 23, "indirizzo": 23, "esser": 23, "trasmesso": 23, "conoscenza": 23, "\u00e8": 23, "necessaria": 23, "affinch\u00e9": 23, "risponda": 23, "memorizza": 23, "su": 23, "nei": 23, "suoi": 23, "registro": 23, "particolar": 23, "possiamo": 23, "assicurarlo": 23, "perch\u00e9": 23, "sotto": 23, "nostro": 23, "controllo": 23, "mostra": 23, "gli": 23, "aeroporti": 23, "vicino": 23, "alla": 23, "tua": 23, "posizion": 23, "corrent": 23, "percorso": 23, "attualment": 23, "pianificato": 23, "anch": 23, "tutti": 23, "apri": 23, "attual": 23, "devono": 23, "servizi": 23, "centro": 23, "possano": 23, "risponder": 23, "possono": 23, "legger": 23, "altri": 23, "dal": 23, "durant": 23, "processo": 23, "devi": 23, "aspettarti": 23, "venga": 23, "memorizzato": 23, "insiem": 23, "sulla": 23, "sono": 23, "gestiti": 23, "governo": 23, "degli": 23, "stati": 23, "uniti": 23, "fuori": 23, "informazioni": 23, "dettagli": 23, "questi": 23, "disponibili": 23, "luoghi": 23, "vicini": 23, "amministrazion": 23, "responsabil": 23, "nie": 23, "przetwarzami": 23, "\u017cadnych": 23, "danych": 23, "osobowych": 23, "u\u017cytkownika": 23, "dane": 23, "wprowadzan": 23, "aplikacji": 23, "w": 23, "tym": 23, "trasi": 23, "punkti": 23, "samolotu": 23, "s\u0105": 23, "przechowywan": 23, "lokalni": 23, "na": 23, "urz\u0105dzeniu": 23, "przesy\u0142an": 23, "przez": 23, "przetwarzan": 23, "abi": 23, "jednak": 23, "zapewni\u0107": 23, "funkcjonalno\u015b\u0107": 23, "aplikacja": 23, "musi": 23, "przesy\u0142a\u0107": 23, "nast\u0119puj\u0105c": 23, "serwer\u00f3w": 23, "interneci": 23, "regularni": 23, "sprawdza": 23, "dost\u0119pno\u015b\u0107": 23, "aktualizacji": 23, "umo\u017cliwia": 23, "pobierani": 23, "z": 23, "serwera": 23, "uniwersytetu": 23, "fryburgu": 23, "urz\u0105dzeni": 23, "t\u0119": 23, "funkcj\u0119": 23, "adr": 23, "urz\u0105dzenia": 23, "zosta\u0107": 23, "przes\u0142ani": 23, "znajomo\u015b\u0107": 23, "adresu": 23, "jest": 23, "konieczna": 23, "serwer": 23, "m\u00f3g\u0142": 23, "odpowiedzie\u0107": 23, "przechowuj": 23, "swoich": 23, "plikach": 23, "dziennika": 23, "szczeg\u00f3lno\u015bci": 23, "mo\u017cemi": 23, "poniewa\u017c": 23, "pod": 23, "nasz\u0105": 23, "kontrol\u0105": 23, "pokazuj": 23, "komunikati": 23, "dla": 23, "lotnisk": 23, "znajduj\u0105cych": 23, "si\u0119": 23, "pobli\u017cu": 23, "twojej": 23, "aktualnej": 23, "lokalizacji": 23, "oraz": 23, "aktualni": 23, "planowanej": 23, "r\u00f3wnie\u017c": 23, "wszystkich": 23, "punkt\u00f3w": 23, "kt\u00f3re": 23, "otworzysz": 23, "twoja": 23, "bie\u017c\u0105ca": 23, "lokalizacja": 23, "zaplanowana": 23, "trasa": 23, "wsp\u00f3\u0142rz\u0119dne": 23, "punktu": 23, "nawigacyjnego": 23, "twojego": 23, "musz\u0105": 23, "przes\u0142an": 23, "us\u0142ug": 23, "sieciowych": 23, "adresem": 23, "centrum": 23, "pogodi": 23, "lotniczej": 23, "niezb\u0119dna": 23, "us\u0142ugi": 23, "sieciow": 23, "mog\u0142i": 23, "mog\u0105": 23, "czasi": 23, "odczytywa\u0107": 23, "innych": 23, "musisz": 23, "liczy\u0107": 23, "\u017ce": 23, "b\u0119dzie": 23, "przechowywani": 23, "razem": 23, "przesy\u0142anymi": 23, "danymi": 23, "o": 23, "pozycji": 23, "internetow": 23, "obs\u0142ugiwan": 23, "rz\u0105d": 23, "stan\u00f3w": 23, "zjednoczonych": 23, "poza": 23, "szczeg\u00f3\u0142ow": 23, "informacj": 23, "temat": 23, "tych": 23, "internetowych": 23, "mo\u017cna": 23, "znale\u017a\u0107": 23, "stroni": 23, "wy\u015bwietla": 23, "notami": 23, "miejsc": 23, "otwierasz": 23, "federalna": 23, "administracja": 23, "lotnicza": 23, "wraz": 23, "us\u0142ugach": 23, "odpowiedzialni": 23, "procesamo": 23, "ning\u00fan": 23, "suyo": 23, "lo": 23, "ingresa": 23, "aplicaci\u00f3n": 23, "incluida": 23, "ruta": 23, "detal": 23, "aeronav": 23, "almacenan": 23, "transmiten": 23, "nosotro": 23, "son": 23, "procesado": 23, "por": 23, "sin": 23, "embargo": 23, "para": 23, "garantizar": 23, "funcionalidad": 23, "debe": 23, "transmitir": 23, "siguient": 23, "servidor": 23, "comprueba": 23, "peri\u00f3dicament": 23, "si": 23, "hai": 23, "actualizacion": 23, "descargar": 23, "mapa": 23, "desd": 23, "universidad": 23, "friburgo": 23, "cplx": 23, "vm": 23, "uni": 23, "__": 23, "proporcionar": 23, "esta": 23, "direcci\u00f3n": 23, "transmitirs": 23, "el": 23, "conocimiento": 23, "necesario": 23, "responda": 23, "almacena": 23, "sobr": 23, "ust": 23, "archivo": 23, "podemo": 23, "asegurar": 23, "esto": 23, "porqu": 23, "est\u00e1": 23, "bajo": 23, "nuestro": 23, "muestra": 23, "aer\u00f3dromo": 23, "cerca": 23, "ubicaci\u00f3n": 23, "planificada": 23, "actualment": 23, "tambi\u00e9n": 23, "todo": 23, "abra": 23, "coordenada": 23, "punto": 23, "intermedio": 23, "deben": 23, "respondan": 23, "pueden": 23, "leer": 23, "otro": 23, "proceso": 23, "esperar": 23, "almacen": 23, "junto": 23, "con": 23, "posici\u00f3n": 23, "transmitido": 23, "operado": 23, "gobierno": 23, "ee": 23, "uu": 23, "est\u00e1n": 23, "fuera": 23, "pued": 23, "encontrar": 23, "detallada": 23, "lugar": 23, "cercano": 23, "administraci\u00f3n": 23, "wlan": 24, "rang": [24, 25], "understand": 24, "watch": 24, "tcp": 24, "2000": 24, "192": 24, "168": 24, "stream": 24, "sentenc": 24, "conform": 24, "ftd": 24, "012": 24, "icd": 24, "gdl": 24, "wg": 24, "84": 24, "ellipsoid": 24, "market": 24, "wrongli": 24, "strategi": 24, "deal": 24, "skydemon": 24, "unabl": 24, "unlik": 24, "workaround": 24, "ring": 24, "eight": 24, "virtual": 24, "target": 24, "avionc": 24, "pole": 24, "accuraci": 24, "perfect": 24, "63093": 24, "foreground": 24, "discov": 24, "unicast": 24, "json": 24, "unidirect": 24, "signal": 24, "convinc": 24, "unidirectionl": 24, "idea": 24, "uavionix": 24, "unusu": 24, "decrypt": 24, "purchas": 24, "feel": 24, "altimet": 24, "correl": 24, "cabin": 24, "suffici": 24, "reliabl": 24, "oppon": 24, "sensor": 24, "gp": [24, 25], "henc": 24, "mislead": 24, "100": 25, "comparison": 25, "ten": 25, "solut": 25, "osmand": 25, "reproduc": 25, "hi": 25, "overlai": 25, "african": 25, "visit": 25, "ofm": 25, "learn": 25, "slider": 25, "openflightmap": 25, "enjoi": 25, "reassur": 25, "respectfulli": 25, "circumnavig": 25, "eleg": 26, "stress": 26, "daili": 26, "noaa": 26, "quickli": 26, "head": 26, "27": 26, "bar": 26, "safeski": 26, "donat": 26, "technic": 26, "tip": 26, "trick": 26}, "objects": {}, "objtypes": {}, "objnames": {}, "titleterms": {"think": 0, "befor": [0, 2, 8, 9, 10], "you": [0, 8, 9, 10], "fly": [0, 2], "softwar": [0, 20, 21], "limit": [0, 18], "navig": [0, 2, 14, 15, 18, 26], "data": [0, 3, 4, 10, 16, 18, 20, 24], "aviat": 0, "oper": 0, "system": [0, 18], "hardwar": 0, "instal": 1, "setup": 1, "app": [1, 7, 8, 11], "set": [1, 7, 9, 18], "aircraft": [1, 7], "specif": 1, "done": 1, "your": [2, 4, 9, 10], "first": 2, "flight": [2, 7, 9, 14, 26], "The": 2, "move": [2, 15, 18], "map": [2, 3, 4, 15, 16, 18, 20], "bar": [2, 15, 18], "interact": [2, 15], "control": [2, 13, 15], "inform": [2, 15], "about": [2, 14], "airspac": [2, 3, 13, 18], "airfield": [2, 13], "other": [2, 9, 26], "facil": 2, "go": 2, "import": [3, 4, 11, 17], "openair": 3, "file": [3, 17], "android": [3, 4, 17], "devic": [3, 4, 24], "linux": [3, 4, 17], "desktop": [3, 4, 17], "us": [4, 7, 26], "own": 4, "mbtile": 4, "sourc": [4, 18], "raster": 4, "geotiff": 4, "format": 4, "make": 5, "donat": 5, "paypal": 5, "bank": 5, "address": 5, "find": 6, "nearbi": 6, "waypoint": [6, 7, 11], "plan": 7, "what": [7, 11], "expect": [7, 11], "up": [7, 9], "rout": [7, 15], "step": [7, 8, 10, 26], "1": [7, 8, 10], "characterist": 7, "2": [7, 10], "specifi": 7, "wind": 7, "3": 7, "4": 7, "edit": 7, "necessari": 7, "option": 7, "save": 7, "futur": 7, "export": [7, 11], "share": [7, 8, 11], "open": [7, 11], "anoth": [7, 11], "connect": [8, 9, 10], "safeski": 8, "0": [8, 10], "enabl": 8, "traffic": [8, 10, 13, 15, 24], "simul": 9, "aerofli": 9, "f": 9, "flightgear": 9, "m": 9, "x": 9, "plane": 9, "11": 9, "program": [9, 20], "troubleshoot": [9, 10], "receiv": [10, 24], "compat": 10, "enter": 10, "": 10, "wi": [10, 17], "fi": [10, 17], "network": [10, 17, 18], "stream": 10, "flarmnet": 10, "manag": 11, "librari": 11, "add": 11, "view": 11, "check": 12, "weather": 12, "page": [12, 15, 18, 26], "footer": 12, "three": 12, "dot": 12, "menu": 12, "displai": [13, 25], "restrict": 13, "zone": 13, "transpond": 13, "mandatori": 13, "radio": 13, "parachut": 13, "jump": 13, "area": 13, "natur": 13, "reserv": 13, "pattern": 13, "enrout": [14, 26], "main": 15, "gestur": 15, "ownship": 15, "posit": [15, 18], "color": 15, "code": 15, "factor": 15, "label": 15, "base": 16, "terrain": 16, "attribut": 16, "aeronaut": 16, "updat": 16, "polici": [16, 23], "origin": 16, "list": 16, "platform": 17, "note": [17, 24], "secur": [17, 18], "problem": 17, "screen": 17, "backlight": 17, "lock": 17, "drag": 17, "drop": 17, "command": 17, "line": 17, "altitud": 18, "glide": 18, "sector": 18, "hillshad": 18, "altimet": 18, "mode": 18, "user": 18, "interfac": 18, "larg": 18, "font": 18, "night": 18, "voic": 18, "notif": 18, "primari": 18, "ignor": 18, "error": 18, "clear": 18, "password": 18, "storag": 18, "help": 18, "author": 19, "contribut": 19, "translat": 19, "alumni": 19, "third": 20, "parti": 20, "geograph": 20, "includ": 20, "licens": 21, "privaci": 23, "english": 23, "deutsch": 23, "\u00fcbersetzung": 23, "traduct": 23, "en": 23, "fran\u00e7ai": 23, "traduzion": 23, "italiana": 23, "polski": 23, "t\u0142umaczeni": 23, "traducci\u00f3n": 23, "al": 23, "espa\u00f1ol": 23, "technic": 24, "support": 24, "commun": 24, "known": 24, "issu": 24, "gdl90": 24, "foreflight": 24, "broadcast": 24, "skyecho": 24, "pingusb": 24, "tip": 25, "trick": 25, "record": 25, "satnav": 25, "track": 25, "introduct": 26, "get": 26, "start": 26, "further": 26, "advanc": 26, "refer": 26, "appendix": 26}, "envversion": {"sphinx.domains.c": 3, "sphinx.domains.changeset": 1, "sphinx.domains.citation": 1, "sphinx.domains.cpp": 9, "sphinx.domains.index": 1, "sphinx.domains.javascript": 3, "sphinx.domains.math": 2, "sphinx.domains.python": 4, "sphinx.domains.rst": 2, "sphinx.domains.std": 2, "sphinx": 58}, "alltitles": {"Think before you fly": [[0, "think-before-you-fly"]], "Software limitations": [[0, "software-limitations"]], "Navigational data and aviation data": [[0, "navigational-data-and-aviation-data"]], "Operating system limitations": [[0, "operating-system-limitations"]], "Hardware limitations": [[0, "hardware-limitations"]], "Installation and setup": [[1, "installation-and-setup"]], "App installation": [[1, "app-installation"]], "Set aircraft specifics": [[1, "set-aircraft-specifics"]], "Done.": [[1, "done"]], "Before your first flight": [[2, "before-your-first-flight"]], "The moving map": [[2, "the-moving-map"]], "The Navigation Bar": [[2, "the-navigation-bar"]], "Interactive controls": [[2, "interactive-controls"]], "Information about airspaces, airfields and other facilities": [[2, "information-about-airspaces-airfields-and-other-facilities"]], "Go flying!": [[2, "go-flying"]], "Import airspace data": [[3, "import-airspace-data"]], "Import OpenAir files on Android devices": [[3, "import-openair-files-on-android-devices"]], "Import Maps on Linux Desktop": [[3, "import-maps-on-linux-desktop"], [4, "import-maps-on-linux-desktop"]], "Use your own maps": [[4, "use-your-own-maps"]], "Import Maps": [[4, "import-maps"]], "Import Maps on Android devices": [[4, "import-maps-on-android-devices"]], "MBTILES Map Data Sources": [[4, "mbtiles-map-data-sources"]], "Raster Maps in GeoTIFF format": [[4, "raster-maps-in-geotiff-format"]], "Make a donation": [[5, "make-a-donation"]], "PayPal": [[5, "paypal"]], "Bank Address": [[5, "bank-address"]], "Find nearby waypoints": [[6, "find-nearby-waypoints"]], "Plan a Flight": [[7, "plan-a-flight"]], "What to expect": [[7, "what-to-expect"], [11, "what-to-expect"]], "Set up a route": [[7, "set-up-a-route"]], "Step 1: Set aircraft characteristics": [[7, "step-1-set-aircraft-characteristics"]], "Step 2: Specify wind": [[7, "step-2-specify-wind"]], "Step 3: Specify waypoints": [[7, "step-3-specify-waypoints"]], "Step 4: Edit the route if necessary": [[7, "step-4-edit-the-route-if-necessary"]], "Optional: Save route for future use": [[7, "optional-save-route-for-future-use"]], "Optional: Export and share the route": [[7, "optional-export-and-share-the-route"]], "Optional: Open the route in another app": [[7, "optional-open-the-route-in-another-app"]], "Connect to the SafeSky app": [[8, "connect-to-the-safesky-app"]], "Connect!": [[8, "connect"], [10, "connect"]], "Step 0: Before you connect": [[8, "step-0-before-you-connect"], [10, "step-0-before-you-connect"]], "Step 1: Enable traffic sharing": [[8, "step-1-enable-traffic-sharing"]], "Connect your flight simulator": [[9, "connect-your-flight-simulator"]], "Before you connect": [[9, "before-you-connect"]], "Set up your flight simulator": [[9, "set-up-your-flight-simulator"]], "Aerofly FS": [[9, "aerofly-fs"]], "FlightGear": [[9, "flightgear"]], "MS Flight Simulator": [[9, "ms-flight-simulator"]], "X-Plane 11": [[9, "x-plane-11"]], "Other programs": [[9, "other-programs"]], "Troubleshooting": [[9, "troubleshooting"], [10, "troubleshooting"]], "Connect to your traffic receiver": [[10, "connect-to-your-traffic-receiver"]], "Compatibility": [[10, "compatibility"]], "Step 1: Enter the traffic receiver\u2019s Wi-Fi network": [[10, "step-1-enter-the-traffic-receiver-s-wi-fi-network"]], "Step 2: Connect to the traffic data stream": [[10, "step-2-connect-to-the-traffic-data-stream"]], "Flarmnet data": [[10, "flarmnet-data"]], "Manage a waypoint library": [[11, "manage-a-waypoint-library"]], "Add waypoints to the library": [[11, "add-waypoints-to-the-library"]], "View the waypoint library": [[11, "view-the-waypoint-library"]], "Import waypoints": [[11, "import-waypoints"]], "Export and share the waypoint library": [[11, "export-and-share-the-waypoint-library"]], "Open the waypoint library in another app": [[11, "open-the-waypoint-library-in-another-app"]], "Check Weather": [[12, "check-weather"]], "Page footer": [[12, "page-footer"]], "Three-dot menu": [[12, "three-dot-menu"]], "Airspace Display": [[13, "airspace-display"]], "Restricted Airspace": [[13, "restricted-airspace"]], "Controlled Airspace": [[13, "controlled-airspace"]], "Control Zone": [[13, "control-zone"]], "Transponder Mandatory Zones": [[13, "transponder-mandatory-zones"]], "Radio Mandatory Zone": [[13, "radio-mandatory-zone"]], "Parachute Jumping Areas": [[13, "parachute-jumping-areas"]], "Nature Reserve Areas": [[13, "nature-reserve-areas"]], "Airfields": [[13, "airfields"]], "Traffic Pattern": [[13, "traffic-pattern"]], "About Enroute Flight Navigation": [[14, "about-enroute-flight-navigation"]], "Main Page and Moving Map": [[15, "main-page-and-moving-map"]], "Route Information Bar": [[15, "route-information-bar"]], "Interactive Controls": [[15, "interactive-controls"]], "Moving Map": [[15, "moving-map"], [18, "moving-map"]], "Gesture Controls": [[15, "gesture-controls"]], "Ownship Position": [[15, "ownship-position"]], "Traffic Information": [[15, "traffic-information"]], "Color Coding": [[15, "color-coding"]], "Traffic Factors": [[15, "traffic-factors"]], "Traffic labelling": [[15, "traffic-labelling"]], "Navigation Bar": [[15, "navigation-bar"], [18, "navigation-bar"]], "Map Data": [[16, "map-data"]], "Base maps": [[16, "base-maps"]], "Terrain maps": [[16, "terrain-maps"]], "Attributions": [[16, "attributions"]], "Aeronautical maps": [[16, "aeronautical-maps"]], "Update policy": [[16, "update-policy"]], "Data origin": [[16, "data-origin"]], "List of maps": [[16, "list-of-maps"]], "Platform notes": [[17, "platform-notes"]], "Android": [[17, "android"]], "Network security problems": [[17, "network-security-problems"]], "Screen backlighting": [[17, "screen-backlighting"]], "Screen locking": [[17, "screen-locking"]], "Wi-Fi locking": [[17, "wi-fi-locking"]], "Linux desktop": [[17, "linux-desktop"]], "File import by drag-and-drop": [[17, "file-import-by-drag-and-drop"]], "Command line": [[17, "command-line"]], "Settings Page": [[18, "settingspage"]], "Airspace Altitude Limit": [[18, "airspace-altitude-limit"]], "Gliding Sectors": [[18, "gliding-sectors"]], "Hillshading": [[18, "hillshading"]], "Altimeter Mode": [[18, "altimeter-mode"]], "User Interface": [[18, "user-interface"]], "Large Fonts": [[18, "large-fonts"]], "Night mode": [[18, "night-mode"]], "Voice Notifications": [[18, "voice-notifications"]], "System": [[18, "system"]], "Primary Position Data Source": [[18, "primary-position-data-source"]], "Ignore network security errors": [[18, "ignore-network-security-errors"]], "Clear password storage": [[18, "clear-password-storage"]], "Help": [[18, "help"]], "Authors": [[19, "authors"]], "Contributions": [[19, "contributions"]], "Translations": [[19, "translations"]], "Alumni": [[19, "alumni"]], "Third party software and data": [[20, "third-party-software-and-data"]], "Geographic maps": [[20, "geographic-maps"]], "Software and data included in the program": [[20, "software-and-data-included-in-the-program"]], "Software license": [[21, "software-license"]], "Privacy Policies": [[23, "privacy-policies"]], "English": [[23, "english"]], "Deutsche \u00dcbersetzung": [[23, "deutsche-ubersetzung"]], "Traduction en fran\u00e7ais": [[23, "traduction-en-francais"]], "Traduzione italiana": [[23, "traduzione-italiana"]], "Polskie t\u0142umaczenie": [[23, "polskie-tlumaczenie"]], "Traducci\u00f3n al espa\u00f1ol": [[23, "traduccion-al-espanol"]], "Technical Notes": [[24, "technical-notes"]], "Traffic Data Receiver support": [[24, "traffic-data-receiver-support"]], "Communication": [[24, "communication"]], "Known issues with GDL90": [[24, "known-issues-with-gdl90"]], "ForeFlight Broadcast": [[24, "foreflight-broadcast"]], "Known issues with SkyEcho devices": [[24, "known-issues-with-skyecho-devices"]], "Known issues with pingUSB devices": [[24, "known-issues-with-pingusb-devices"]], "Tips & Tricks": [[25, "tips-tricks"]], "Display of recorded satnav tracks": [[25, "display-of-recorded-satnav-tracks"]], "Enroute Flight Navigation": [[26, "enroute-flight-navigation"]], "Introduction": [[26, "introduction"]], "Getting Started": [[26, "getting-started"]], "Further Steps": [[26, "further-steps"], [26, null]], "Advanced Use": [[26, "advanced-use"], [26, null]], "Reference: Pages": [[26, "reference-pages"], [26, null]], "Reference: Other": [[26, "reference-other"], [26, null]], "Appendix": [[26, "appendix"], [26, null]]}, "indexentries": {}}) \ No newline at end of file