

  {extends file="main.tpl"}
    <!DOCTYPE head PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><head xmlns="http://www.w3.org/1999/xhtml">
  {block name=title}GPSBabel development:GoPal GPS track log (.trk) (gopal){/block}
  {block name=body}
                       
  <div xmlns="http://www.w3.org/1999/xhtml" class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">GoPal GPS track log (.trk) (gopal)</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="fmt_gnav_trl.html">Prev</a> </td><th width="60%" align="center">Chapter 3. The Formats</th><td width="20%" align="right"> <a accesskey="n" href="fmt_land_air_sea.html">Next</a></td></tr></table><hr /></div><div xmlns="http://www.w3.org/1999/xhtml" class="section"><div class="titlepage"><div><div><h2 class="title" ><a id="fmt_gopal"></a>GoPal GPS track log (.trk) (gopal)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="fmt_gopal.html#fmt_gopal_o_date" title="date option">date</a>, <a class="link" href="fmt_gopal.html#fmt_gopal_o_maxspeed" title="maxspeed option">maxspeed</a>, <a class="link" href="fmt_gopal.html#fmt_gopal_o_minspeed" title="minspeed option">minspeed</a>, <a class="link" href="fmt_gopal.html#fmt_gopal_o_clean" title="clean option">clean</a> .</p><p>
  The gopal format is a track format written by the
 <a class="ulink" href="http://www.mediongopal.de/" target="_top">GoPal Navigation</a> program. 
</p><p>
  The format of the file itself is quite simple:</p><p>
      </p><pre class="programlisting">
        Fileformat GoPal
        TICK;   TIME UTC; LONG;    LAT;       HEIGHT; SPEED km/h;  FIX; HDOP;     SAT
        3801444, 080558, 2.944362, 43.262117, 295.28, 0.12964, 2, 2.900000, 3
      </pre><p>

Filenames are automatically created by the device as follows:
      </p><pre class="programlisting">
        trackYYYYMMDD_HHMMSS.trk  </pre><p>
      and/or, depending on software version and settings:
      </p><pre class="programlisting">
		A_YYYYMMDD_HHMMSS.trk
              </pre><p>
	with HHMMSS local time (not UTC!)
      </p><p> 
The file format lacks the correct date value for each trackpoint, so it has to be computed starting from the
date given in the filename. To handle files without a parsable date in the
name, the command line option 'date' is provided.
</p><p>
Conversions from gopal into any other format are a bit lossy concerning the first field of each line wich looks like an useless time tick value
and is simply discarded while reading. If written, there will be a time_t value from the current (computed) timestamp.
</p><p>
Somewhere around Gopal 4.8 or 5.0, Electrobit added three more fields to the end of this format.  They are, in order, date (which eliminates most of the silliness above), an unknown field, and a bearing.   GPSBabel now reads the date and ignores the other two.  We don't yet write these three fields for compatibility with earlier versions.
</p><p>

Filtering out invalid data points is handled by the options 'clean', 'minspeed' and 'maxspeed'.
For each datapoint the speed needed to come the from the last valid point is
calculated and compared with the limits.
Thus one cat easily discard unreliable points.

         </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gopal_o_date"></a><code class="option">date</code> option</h3></div></div></div><p>
      Complete date-free tracks with given date (YYYYMMDD)..
    </p><p>
  This option is useful if you have tracks from Gopal that have been renamed.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gopal_o_maxspeed"></a><code class="option">maxspeed</code> option</h3></div></div></div><p>
      The maximum speed (km/h) traveling from waypoint to waypoint..
    </p><p>
  This is useful for removing wildly erroneous data from your recorded track.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gopal_o_minspeed"></a><code class="option">minspeed</code> option</h3></div></div></div><p>
      The minimum speed (km/h) traveling from waypoint to waypoint. Set &amp;gt;0 to remove duplicate waypoints.
    </p><p>
  If this is greater than zero, duplicate waypoints will be removed.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gopal_o_clean"></a><code class="option">clean</code> option</h3></div></div></div><p>
      Cleanup common errors in trackdata.
    </p><p>
  Specifying the <code class="option">clean</code> flag makes the Gopal reader pass
  over the data and discard data that is probably incorrect such as the
  longitude and latitude of "0".
</p><p>
  If you happen to be a boater or pilot off the south short of Ghana,
  you may disagree that coordinates of "0, 0" are bad.
</p></div></div><div xmlns="http://www.w3.org/1999/xhtml" class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="fmt_gnav_trl.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="The_Formats.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="fmt_land_air_sea.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Google Navigator Tracklines (.trl) (gnav_trl) </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> GPS Tracking Key Pro text (land_air_sea)</td></tr></table></div>
  
      {/block}
  