forked from GlidingWeb/IGCWebView
-
Notifications
You must be signed in to change notification settings - Fork 0
/
igchelp.html
114 lines (102 loc) · 8.82 KB
/
igchelp.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="initial-scale=1, width=device-width">
<title>IGC Viewer help</title>
<link rel="stylesheet" href="igctext.css" />
</head>
<body>
<div id='titlediv'>
<h1>IGC Webview User Instructions</h1>
<p> © 2015 Alistair Malcolm Green and Richard Brisbourne </p>
</div>
<div class="content">
<p>
IGC Webview is a web based application for viewing logger traces in IGC format. Nearly all gliding loggers now either record
in that format or save files in it- for any others including those not originally designed for gliding purposes,
there are conversion programs out there; a popular example is <a href="http://www.gpsbabel.org">GPSBabel</a>.
Igc files can normally be identified by the extension ".igc".
</p>
<p>
IGCWebview runs on a wide range of devices and operating systems; all you need is an internet connection and a browser with
Javascript enabled. It uses world-wide mapping so can be used for flights made anywhere.
</p>
<p>
Although designed to be as intuitive as possible, the program has one or two features you might miss, so please read this
if you haven't used it before.
</p>
<h2>Getting started</h2>
<p>Simple. Ignore the "task" setting for now. Click the "Browse" button and select an igc file from
your local computer or device. On load a map will open up together with a barogram, and information from the
file header will be displayed. The map will also show the location of any controlled/special use airspace in
the area, if we have the data. If the file contains a task declaration this will also be shown on the map, together
waypoint observation zones as defined in the FAI Sporting Code.
</p>
<h2>Altering the display</h2>
<p>
You can move around and zoom in or out on the map- if you've ever used Google Earth it works the same way. Click and drag
to move; zoom in using the "+-" top left, scroll wheel, or on a tablet, "pinching". To reduce clutter you can
control the airspace clip altitude, or lose the airspace display altogether. Click on the icon top right on the
map to add or remove display of task or track, or to switch between map and satellite picture background.
</p>
<h2>Moving round the track</h2>
<p>
Use the slider control below the map to move the aircraft icon round the track. The text below the map will give the time
and your position and altitude, and the crosshairs on the barogram will also show altitude and time flight. Times
are time zone adjusted. If you find the aircraft is moving round too quickly for you and you have a keyboard,
you can move it using the arrow keys, but you need to click on the slider first to give it focus. You can also
click on the barogram; the glider will move to the point you've clicked on.
</p>
<h2>Tasks</h2>
<p>
By default, IGCWebview will look for a task declaration in the IGC file and load that (or leave the task section blank if there isn't one). However you will see a row of radio buttons under the heading "Select task source". If you select "User entry" a dialogue will appear- you can then enter start, finish and turning points from the BGA or Welt2000 lists, or simply enter as latitude and longitude. Alternatively you can select XCWebPlan; a copy of XCWebPlan will open and you can use that. This is a bit more complicated- see below. Either procedure will work whether or not you have an IGC file open. At any time you can select "IGC File" here, and the task will revert to the one in the currently loaded file.
</p>
<h2>Importing a task from XCWebPlan</h2>
<p>
Users in the UK will find it easy to enter BGA trigraphs to define a task; for users elsewhere entering latitudes and longitudes by hand will work, but is a pain. If you have a suitable waypoint file available (".cup" or ".dat" format), an easy alternative is to mark out your task in XCWebPlan, and import it. The process is simpler than it looks provided you do it as per instructions:
<ol>
<li>Click on the "Load" button in the "Task user entry" section. A copy of XCWebPlan will open in another tab in your browser.</li>
<li>In XCWebPlan accept the airspace disclaimer and then select the waypoint file of your choice.</li>
<li>Enter your task by clicking on the map. If you haven't used XCWebPlan before, consult the help file that comes with it.</li>
<li>Once you have entered the task a "Copy task" button will appear bottom right. Click on it and you should get a message saying the task has been copied over.</li>
<li>Switch back to the "XCWebView" tab, and you will see your new task entered.</li>
<li>You can repeat the process as often as you like by simply switching back to the same tab with XCWebPlan on it.</li>
</ol>
Please note the process will only work if done as above; because there are very reasonable limitations on interaction between web pages for security reasons, it's a bit fiddly. In particular, it will only work if you open the copy of XCWebPlan from the "Load" button- if it's opened by another route it won't recognise what it's supposed to be talking to (and you won't see the "copy task" button). Also you will have to switch between tabs manually; you won't see what's happening in the tab behind the current one, although we've provided messages which will hopefully tell you.</p>
</p>
<h2>Checking your performance</h2>
<p>
You can easily find out the speed you made around the task or how far short you were. If you have both a task and an IGC file entered, click on the "Analyse task" button below the map. If you completed the task it will show your speed; if you failed it will show your scoring distance (defined as the distance as far as the first failed turning point, minus the distance you were short of it). A pin image will appear on the map marking your nearest approach to the failed point.
</p>
<p>
Start, finish, and turning point sectors used in the calculation are defined as shown on the map. If you want to use something else, you can change these (see below).
</p>
<h2>Control sectors</h2>
<p>
The defaults in the program are as follows:
<ul>
<li>Start: A line radius 5 Km (ie: 10 Km long) centred at the start point, at right angle to the first leg.</li>
<li>Turning points: A circle 0.5 Km radius centred on the point, <b> plus</b> a sector 20 Km radius subtending an angle of 90° remote from and centred on the bisector of the tracks in and out (the "FAI thistle").</li>
<li>Finish: A line of 1 Km radius at right angles to the last leg centred on the finish point.</li>
</ul>
If you want something else you can click on the "Configure TP sectors" button make changes, then click "Apply". "Restore defaults" simply restores the values above, you still need to "apply" afterwards. The values entered will always stick until you make a further change or close the page. If you want them to apply next time you load the page, tick the "Save" box before "apply".
</p>
<h2>About IGCWebview</h2>
<p>
IGCWebview is an open source program. This means that the code is free for anyone to copy, modify and distribute, subject
to the terms of the <a href="LICENSE.txt" target="_blank">licence</a>. It makes substantial use of
other open source program code and libraries also data distributed under Creative Commons copyright arrangements.
For a full list of sources and contributors see our <a href="igcabout.html"> about</a> page.
</p>
<h2>Feedback</h2>
<p>
We're interested in how well this works for you. Any ideas, suggestions, and (particularly) bug reports should be added to
the <a href="https://github.com/GlidingWeb/IGCWebView/issues" target='_blank'>GitHub issue tracker</a> or e-mailed to <a href="mailto:igcwebview@glidingweb.org">igcwebview@glidingweb.org</a>. If you are a developer
interested in the program from a technical point of view, and maybe looking at the code and possibly contributing,
there's a lot more information on our <a href="igcabout.html" target="_blank">"about" page</a>.
</p>
<button onClick="window.close()">Close window</button>
</div>
</body>
</html>