Comment 2 for bug 484667

Revision history for this message
hopet (hopet) wrote :

The conversion would be needed of course - some comments are available, e.g., from here:
http://gpsinformation.net/main/epenew.txt
but as far as I know, we don't have have URA information available (except that some sources suggest URA < 10).
Btw, what's the meaning of MSVs_QCN and weight criteria? Couldn't that be used?

Another (and more clean) option would be to create extension like:
<extensions>
<ehpe unit="m">5</ehpe>
</extensions>
in analogy to what TrekBuddy does (GSM and NMEA extensions - but they also prefix it with their own namespace):

<?xml version='1.0' encoding='UTF-8' ?>
<gpx version="1.1" creator="TrekBuddy 0.9.89" xmlns="http://www.topografix.com/GPX/1/1" xmlns:nmea="http://trekbuddy.net/2009/01/gpx/nmea" xmlns:gsm="http://trekbuddy.net/2009/01/gpx/gsm">
  <trk>
    <trkseg>
      <trkpt lat="45.530174693" lon="-122.614001793">
        <ele>56.5</ele>
        <time>2009-11-15T16:48:16.431Z</time>
        <fix>3d</fix>
        <sat>4</sat>
        <extensions>
          <nmea:course>314.1</nmea:course>
          <nmea:speed>22.6</nmea:speed>
          <gsm:cellid>456</gsm:cellid>
        </extensions>
      </trkpt>