Files Reference

      xxxTRK.csv
      xxx=Pilot Number
      For each pilot track download a file called pilotnumberTRK.csv gets created in the pilotdata subdirectory of a task.
      pilotnumber is a 3 digit filled with leading 0s.
      Example 001TRK.csv for pilot number 1.
      The format is
      -32.9052061680704,19.0384322404861,408880657,1,0
      -32.9052061680704,19.0384376049042,408880673,0,0
      -32.9052115324885,19.0384376049042,408880674,0,0
      -32.9051793459803,19.038410782814,408882959,1,0
      or
       -32.9051060881466,19.0385794267058,408877636,0,710
      or
       -32.9052277095616,19.0383870620281,408876158,0,720.1648

      NS coordinates ,
      EW coordinates,
      GPS UTC time in seconds ( Long Integer) ,
       0/1 new track segment flag  , 1 = start of a new track segment
       Altitude as floating point , or 0 if no altitude info is available

        COMP_ID.csv
      comp_id = 6 characters, like AA2002, or PG2003 or FUNCMP.
       comp_id.csv  is used when creating a task and uploading the  turnpoints into the  pilots GPS at registration.
      One can create an comp_id.csv file by downloading all the waypoints from a  GPS device.
      And then rename the WAYPOINT.csv to comp_id.csv.
      Or if you use the GARMIN download, apply the COPY button in the Garmin menu panel to create the comp_id.csv file.
      Or via the Menu Option RACE/UPLOAD/CSV>RACE or RACE>CSV to get the turnpoints to or from RACE.
      One can manually add turnpoints by using SETUP/TASK/MODIFY and use the ADD option button to add another turnpoint to comp_id.csv
      The comp_id.csv file can be hand edited with Notepad or any other editor.
      One record example from the AA2002.csv file .....
      "L01070",-32.9050333333333,19.0382333333333,705,"DASKLIP LAUNCH (PG)                     "
         6 character ID
         NS coordinates
         EW coordinates
         altitude in meters
         up to 20 character string with a long name describing the turnpoint
      Task.ini


        Task.ini file located  in a TASKxx directory
       

        TASK.csv
      Located in a TASKxx directory.
       TASK.csv  defines a days task. Can be hand edited if necessary.
      Contains the sequence, ES or SS, waypoint id, coordinates and a radius for the cylinder beercan.
       Example File
      "TO  ","  ","L01070",-32.9050333333333,19.0382333333333,.4,"DASKLIP LA"
      "1   ","SS","S07024",-33.0084,19.0246166666667,1,"VODACOM TO"
      "2   ","  ","S07024",-33.0084,19.0246166666667,.4,"VODACOM TO"
      "3   ","  ","N05029",-32.8202666666667,19.0290166666667,.4,"CARDOUW FA"
      "4   ","  ","N07017",-32.7765666666667,18.9244666666667,.4,"INTERSECTI"
      "5   ","  ","N13010",-32.6854166666667,18.8833666666667,.4,"EENDEKUIL "
      "GOAL","ES","N15027",-32.66485,18.95985,.4,"SORGVLIET "

        4 characters to identify the Task turnpoint sequence. Names are fixed.
        2 characters to identify an SS or ES
        6 characters from the turnpoint identification
         NS coordinates
         EW coordinates
         cylinder radius
         10 character description
       

      TP.ini
       TP.ini   is the first file read by the TP GPS code. It defines the directory where the competition data is located. ( C:\tp\code\tp.ini)
       COMP_ID.ini files are located in the inifiles directory where TP.exe is installed.  (C:\tp\code\inifiles\comp_id.ini)
      COMP_ID can be 6 character long and is the competition name/identifier that gets also put in the GPS along with the pilot identifier.
      The comp_id gets defined in SETUP/COMP.
       When loading a competition the comp_id.ini file gets copied to TP.ini and replaces/overwrites TP.ini.
        TP.ini example file
      Each PC that runs TP uses the TP.ini file from where the TP.exe is located.
      Means each PC should have its own TP.exe on a local drive. Do not use the TP.exe over a network drive.
      Otherwise everyone uses the same TP.ini file. Which will result in everyone using the same serial ports.
      TP.ini defines the serial ports and baud rate settings for Garmin, MLR, Compeo, Aircotec, Log_It....
      COMP.ini
      Located in the comp_id directory.

      COMP.ini file example in a Comp Directory

         [TPGPS]
      AUTO_TASK=05
      COMP_ID=AA2002
       

      PIILNRID.csv
        PILNRID.csv  is required for the cross reference between RACE Pilot ids and Pilot Numbers used. To create it, one hasa to have RACE setup and loaded with the pilots. And then use in TP the Menu Option RACE , either the menuoption XML>Pilot_ID or RACE>Pilot_ID to create a PILNRID.csv file.
       Example of a pilnrid.csv file located in the comp directory
          24,1
      means pilot number 24 has got in RACE pilot-id 1
       
      Temp.csv
      TEMP.csv  is used when a task gets defined the first time and is not saved yet
       
      pinfile.csv
      PINFILE.gd  is a file in Gardown format where each pilot landed
      PINFILE.csv is the same as Pinfile.gd in csv format , used by the PinMap Function to show where each pilot landed
       
      RACE.xml
      RACE.xml collects the RACE xml score for each pilot when you accept a score
       
      TPLOG.csv
      TPLOG.csv keeps track of which pilot got assigned which number, or if there was a problem with a GPS.
      Or when a track log got not accepted and a manual cursor postition was used.
      Whenever there was some interaction witha GPS device.
      One can see there which computer did what and when.
       
      GPS2DO.csv
      GPS2DO.txt lists GARMIN GPS devices that have not been defined in the Garmin interface code. If a Garmin is not defined then the code will try to establish from the Garmin the protocol interface. And if this fails a GPS 12  default interface gets used.
       
      XREF.csv
      XREF.csv cross reference between pilot number assigned and pilotname when you create a pilotid in a GPS , also which  GPS type was used
      It is used/read  to display the name of a pilot when a pilot number is located in a GPS.
      It gets created, appended each time a Pilotid gets created in a GPS device.
      PROBLEM.csv
      PROBLEM.csv in the task directory gets appended when a scorer presses the problem button in cylinder scoring. a new window opens where the operator can type in some extra info  and then press the add a problem button. A csv file gets appended with the pilot number and name and the text.
      Idea is to download and process pilots when they come in and look at problems later.. Once the rush is over one can go through those problem pilots tracks again. Or in case there was a code problem, inform the developer.
      Also gets appended when an operator decides to not accept the default score and opts to use a manual score from a cursor position.
       
      *.csv files
      csv files are comma seperated variable fromat files. Comes from the MS Visual Basic and Excel spreadsheet world.
      Can be hand edited with any plain editor.
      *.gd files
      gd files are Gardown format files. Gardown is an  interface code for Garmin GPS.
       
      *.igc files
      igc filea are International Gliding Comission files. Comes from the sailplane world to store track logs.
      *.ini files
      ini file format is MS Visual Basic defined. Can be hand edited with any plain editor
      *.wpt Aircotec TopNavigator Waypoint files
      To feed a TOPNAVIGATOR from Aircotec with turnpoints one creates a comp_id.wpt file ahd then used the TNCOMM software from Aircotec.
      wpt files are Aircotec TN waypoint format.


       

      How ini values get assigned and reading ini  files sequence

      1. first TP defines some default values inside the code
      2. then TP.ini is read first when the program gets started overwriting those defaults
      3. next the COMP.ini file in the competition directory gets read
      4. when you load a task, first some defaults values get assigned in the code
      5. and then the TASK.ini file in a TASKxx directory gets read
    Back to Index for TP Code