| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | <languages /> | ||
| + | <translate> | ||
| + | <!--T:1--> | ||
---- | ---- | ||
To import a list of waypoints with the '''embedded Webserver''', the data must be formatted as a tab separated text file, encoded as UTF8 to support special characters. | To import a list of waypoints with the '''embedded Webserver''', the data must be formatted as a tab separated text file, encoded as UTF8 to support special characters. | ||
| + | <!--T:2--> | ||
You can use your favorite spreadsheet application or convert waypoints from another database to match the structure described below. | You can use your favorite spreadsheet application or convert waypoints from another database to match the structure described below. | ||
| − | < | + | <!--T:3--> |
| + | '''We strongly recommend''' that you create a custom waypoint on the iPhone/iPod first and download it from the website to get the correct file structure, then you don’t have to type the columns names manually (which could result in typos and/or bad structure that would not be recognized as a valid file on importation). | ||
| − | ==== '''File structure for waypoints''' ==== | + | ==== '''File structure for waypoints''' ==== <!--T:4--> |
| + | <!--T:5--> | ||
To be valid, a waypoint file must start with a row listing the columns names separated by a tab character (TAB key). The other lines are the actual waypoints values (one line per waypoint). Values can be empty but they must be separated by a tab character. | To be valid, a waypoint file must start with a row listing the columns names separated by a tab character (TAB key). The other lines are the actual waypoints values (one line per waypoint). Values can be empty but they must be separated by a tab character. | ||
| + | <!--T:6--> | ||
The '''best would be''' to work on MS EXCEL and when having finished, then copy the columns and paste them into a TXT file with a program like «Notepad»: | The '''best would be''' to work on MS EXCEL and when having finished, then copy the columns and paste them into a TXT file with a program like «Notepad»: | ||
| + | <!--T:7--> | ||
[[File:filew.jpg]] | [[File:filew.jpg]] | ||
| Line 27: | Line 35: | ||
* main_runway_orientation (number 1 to 360) | * main_runway_orientation (number 1 to 360) | ||
<br/> | <br/> | ||
| − | ==== '''File structure for frequencies''' ==== | + | ==== '''File structure for frequencies''' ==== <!--T:8--> |
| + | <!--T:9--> | ||
To be valid, a frequencies file must start with a row listing the columns names separated by a tab character. The other lines are the actual frequencies values (1 line per frequency). Values can be empty but they must be separated by a tab character. | To be valid, a frequencies file must start with a row listing the columns names separated by a tab character. The other lines are the actual frequencies values (1 line per frequency). Values can be empty but they must be separated by a tab character. | ||
| + | <!--T:10--> | ||
[[File:filef.jpg]] | [[File:filef.jpg]] | ||
| Line 39: | Line 49: | ||
* '''frequency_mhz''' (number with decimal, the actual frequency). | * '''frequency_mhz''' (number with decimal, the actual frequency). | ||
<br/> | <br/> | ||
| − | ==== '''File structure for runways''' ==== | + | ==== '''File structure for runways''' ==== <!--T:11--> |
| + | <!--T:12--> | ||
To be valid, a runways file must start with a row listing the columns names separated by a tab character. The other lines are the actual runways values (1 line per runway). | To be valid, a runways file must start with a row listing the columns names separated by a tab character. The other lines are the actual runways values (1 line per runway). | ||
Values can be empty but they must be separated by a tab character. | Values can be empty but they must be separated by a tab character. | ||
| + | <!--T:13--> | ||
[[File:filerr.jpg]] | [[File:filerr.jpg]] | ||
| + | <!--T:14--> | ||
Columns names and definition are: | Columns names and definition are: | ||
* '''waypoint_id''' (text, must match a waypoint waypoint_id to be associated with it) | * '''waypoint_id''' (text, must match a waypoint waypoint_id to be associated with it) | ||
| Line 55: | Line 68: | ||
<br/> | <br/> | ||
---- | ---- | ||
| − | < | + | <u>'''Note:'''</u> remember that all the files described in this chapter will be '''imported''' into Air Navigation Pro through the embedded WebServer. |
---- | ---- | ||
<br /> | <br /> | ||
| − | Back to <u>[[ | + | Back to <u>[[Personal_data_management | previous page.]]</u> |
| + | </translate> | ||
Latest revision as of 13:42, 1 August 2017
To import a list of waypoints with the embedded Webserver, the data must be formatted as a tab separated text file, encoded as UTF8 to support special characters.
You can use your favorite spreadsheet application or convert waypoints from another database to match the structure described below.
We strongly recommend that you create a custom waypoint on the iPhone/iPod first and download it from the website to get the correct file structure, then you don’t have to type the columns names manually (which could result in typos and/or bad structure that would not be recognized as a valid file on importation).
File structure for waypoints
To be valid, a waypoint file must start with a row listing the columns names separated by a tab character (TAB key). The other lines are the actual waypoints values (one line per waypoint). Values can be empty but they must be separated by a tab character.
The best would be to work on MS EXCEL and when having finished, then copy the columns and paste them into a TXT file with a program like «Notepad»:
Columns names and definition are:
- waypoint_id (text, usually less than 6 characters, required value)
- waypoint_name (text, longer description of the waypoint)
- waypoint_type (number: 1=Airport, 2=fix, 3=waypoint, 4=Helipad, 5=seaplane base, 8=IFR waypoint, 10=DME, 11=NDB, 12=VOR, 13=NDB/DME, 14=VOR/DME, 15=TACAN, 16=VORTAC)
- waypoint_longitude (number with decimal)
- waypoint_latitude (number with decimal)
- waypoint_elevation (number, elevation in feet)
- waypoint_country (text)
- waypoint_state (text, example California)
- waypoint_channel (text)
- waypoint_frequency (number, for navaids only)
- main_runway_orientation (number 1 to 360)
File structure for frequencies
To be valid, a frequencies file must start with a row listing the columns names separated by a tab character. The other lines are the actual frequencies values (1 line per frequency). Values can be empty but they must be separated by a tab character.
Columns names and definition are:
- waypoint_id (text, must match a waypoint waypoint_id to be associated with it)
- type (text, short name of the frequency)
- description (text, long name of the frequency)
- frequency_mhz (number with decimal, the actual frequency).
File structure for runways
To be valid, a runways file must start with a row listing the columns names separated by a tab character. The other lines are the actual runways values (1 line per runway). Values can be empty but they must be separated by a tab character.
Columns names and definition are:
- waypoint_id (text, must match a waypoint waypoint_id to be associated with it)
- rw_id (text, name of the runway)
- rw_orientation (number 1-360)
- wid_ft (number, width in feet)
- len_ft (number, length in feet)
- sfc_ty (number, unknown=0, Asphalt=1, Concrete=2, Grass=3, Gravel=4, Dirt=5, Sand=6, Snow=7, Ice=8, Water=9)
Note: remember that all the files described in this chapter will be imported into Air Navigation Pro through the embedded WebServer.
Back to previous page.