| 38 | | The error margin is default 0,5%. This is 2 meters for a 400 meter radius tp. 200 meters for a 40km radius turnpoint. |
| 39 | | This is used because there are a number of different ways the GPS devices calculate distance which may give slightly different distance. If you do not believe this is necessary you should do a simple test - create the same two TP task of about 50-100km in a few different types of instruments, then look at the distance shown. We wish these differences could be documented by the makers of the instruments, but it have not been successful so far. |
| | 41 | The error margin is default 0,5%. This is 2 meters for a 400 meter radius turnpoint. 200 meters for a 40km radius turnpoint. |
| | 42 | This is used because there are a number of different ways the GPS devices calculate distance which may give slightly different distance. If you do not believe this is necessary you should do a simple test - create the same two turnpoint task of about 50-100km in a few different types of instruments, then look at the distance shown. We wish these differences could be documented by the makers of the instruments, but it have not been successful so far. |
| | 43 | |
| | 44 | === About !GpsDump === |
| | 45 | |
| | 46 | FS works well in combination with GpsDump when all communications with GPS devices is handled by !GpsDump. !FsComp and !FsFlight read the tracklog files saved by !GpsDump. !GpsDump can also convert a range of formats to KML, IGC files are for example very common and easily converted with !GpsDump. You are not locked to !GpsDump, and may use any software you like to get the tracklogs downloaded, just make sure it is stored in KML format and named correctly for !FsComp to read and process it. |
| | 47 | |
| | 48 | !GpsDump have a competition mode, where it relates to the participant list from FS. This makes it possible to register pilots GPS units by uploading a special ID waypoint to identify the GPS units. This saves a lot of time and avoids human errors when downloading tracklogs during the heat of the scoring. |
| | 49 | |
| | 50 | In competition mode !GpsDump will store tracklog files in the following format: '''[Pilot name].[Datetime].[CIVLID].[COMPID].kml''' This makes it possible for !FsComp to match the files to the participants, and automatically check the tracklogs. |
| | 51 | |
| | 52 | !GpsDump also have the option of applying a filter when downloading a tracklog. This filter is very useful with Garmin GPS units that sends the whole tracklog, as the filter keeps the tracklog files clean, and only stores points that apply to the relevant task. The tracklog filter works in UTC time as most GPS devices store tracklog in UTC, and it it recommended to set it to filter anything before the start window open time. Flytec/Brauniger integrated instruments will send only relevant data. |
| | 53 | |
| 89 | | |
| 90 | | FS will calculate the "shortest distance needed to take all turnpoints". |
| 91 | | |
| 92 | | Example 1: Two tp (incl. take off and goal) |
| 93 | | |
| 94 | | * At take off: tp1 radius 400meters |
| 95 | | * Goal 10km away: tp2 radius 400meters. |
| 96 | | |
| 97 | | Task distance will be 9,2km |
| 98 | | |
| 99 | | Example 2: Out and return (Three tp incl. take off and goal) |
| 100 | | |
| 101 | | * At take off: tp1 radius 400meters |
| 102 | | * 10km away: tp2 radius 400meters. |
| 103 | | * Back to take off: tp3 radius 400meters. |
| 104 | | |
| 105 | | Task distance will be 18,4km |
| 111 | | Race with a multiple startgates: Select task type "Race" and set which tp is start of speedsection (SS) and end of speedsection (ES) then add several start gates. |
| | 110 | 1. Race with a single start time: Select task type "Race" and set which turnpoint is start of speedsection (SS) and end of speedsection (ES) then add a single start time. |
| | 111 | 1. Race with a multiple start times: Select task type "Race" and set which turnpoint is start of speedsection (SS) and end of speedsection (ES) then add several start times. |
| | 112 | 1. Elapsed time: Select task type "Elapsed time" and set which turnpoint is start of speedsection (SS) and end of speedsection (ES) but do not add any start times. |
| | 113 | 1. Open distance: The task must have at least the take off waypoint. |
| | 114 | 1. Open distance via turnpoints: Add one or more turnpoints after the take off. The pilot who get furthest away in any direction from the last turnpoint win the task. |
| | 115 | 1. Open distance on a heading: Same as open distance above, but check the "Heading" checkbox and add an extra turnpoint at the end which gives the heading to fly. |
| | 116 | 1. Race to nowhere: Set startpoint, start cyl, and a larger goal cyl around same turnpoint. ES is when pilot cross out of goal cyl. |
| 113 | | Elapsed time race: Select task type "Elapsed time" and set which tp is start of speedsection (SS) and end of speedsection (ES) but do not add any start gates. |
| 114 | | |
| 115 | | Open distance: must have at least one tp. Can have more in which case it is "open dist via turnpoints". See futher description below. |
| 116 | | |
| 117 | | Open distance on a heading: Same as open distance above, but check the "Heading" checkbox and add an extra turnpoint at the end which gives the heading to fly. |
| 118 | | |
| 119 | | Race to nowhere: Set startpoint, start cyl, and a larger goal cyl around same TP. ES is when pilot cross out of goal cyl. |
| 120 | | |
| 121 | | Lots of other variants of tasks is possible, tps with big or small cylinders, tps inside/outside each other, f.ex. one can fly from start out the edge of a 50km cylinder then back to start again ("Race to nowhere and back"). |
| | 118 | Lots of other variants of tasks is possible, turnpoints with big or small cylinders, turnpoints inside/outside each other, f.ex. one can fly from start out the edge of a 50km cylinder then back to start again ("Race to nowhere and back"). |
