Recorded GPX files in Nav Free do not properly display route
  • Vote Up0Vote Down AlanAlan
    Using Navigator Free 6.0.205, I recorded several GPX files while hiking during the past week.  When I viewed the files in Navigator Free or on the OSM website, the files appear to be either are corrupt or were not recorded properly.  Instead of following a winding hiking trail, the trace shows a series of straight lines with many locations missing even though I passed by them.

    GPX files and screenshots are located here.

    GPX files recorded on 16-06 and 31-07 display routes properly.
  • 7 Comments sorted by
  • Vote Up0Vote Down MalaFiliMalaFili
    I think you have the same problem I "had" long years ago with IGO recordings...
    It records WAYPOINTS not routes. So depending on timeframe between recorded points you just have lines on surface, not following a streets. To see a route (must not be yours, depending on settings in routeplanner) you need  to import them to a routeplanner. Google Earth does not show routes from these waypoints.


  • Vote Up0Vote Down AlanAlan
    Since I was hiking while doing the recording, either the waypoints were spaced 10+ minutes in time, or I was walking at 100+ miles per hour ????. In 5+ years of recording GPX files, this was the first time I have encountered this issue. Tracks show up bad in Navigator, GPX Editor, OSM editor, etc.
  • Vote Up0Vote Down tomastomas
    your GPS is probably giving bad positions
    record NMEA and email it to supportt
  • Vote Up0Vote Down AlanAlan
    Tried saving other tracks.  They seem to be OK.  So not certain why there was an issue during those few days.  My phone is a Pixel 3a, so not a relatively old phone.  One of the tracks was walking around an open field, so hard to see how the GPS signals have been problematic.  Will keep monitoring.
  • Vote Up0Vote Down AlanAlan
    Hi Tomas,

    I have found a way to reproduce the behavior.

    I started the recording at 01:03, then switched to the home screen at 01:04, then locked the screen at 01:05, unlocked at 01:06 to the home screen, then switched to Navigator at 01:07 to stop the recording.  Here's the result (I've trimmed the ends of the NMEA file a bit for brevity):

    $GPGGA,010356,4200.3257,N,08813.4060,W,1,,,219,,,,,*70
    $GPRMC,010356,A,4200.3257,N,08813.4060,W,0.0,0,201020,,,*38
    $GPGGA,010357,4200.3256,N,08813.4060,W,1,,,219,,,,,*70
    $GPRMC,010357,A,4200.3256,N,08813.4060,W,0.0,0,201020,,,*38
    $GPGGA,010358,4200.3256,N,08813.4060,W,1,,,219,,,,,*7f
    $GPRMC,010358,A,4200.3256,N,08813.4060,W,0.0,0,201020,,,*37
    $GPGGA,010359,4200.3256,N,08813.4060,W,1,,,219,,,,,*7e
    $GPRMC,010359,A,4200.3256,N,08813.4060,W,0.0,0,201020,,,*36
    $GPGGA,010400,4200.3256,N,08813.4060,W,1,,,219,,,,,*75
    $GPRMC,010400,A,4200.3256,N,08813.4060,W,0.0,0,201020,,,*3d
    $GPGGA,010401,4200.3256,N,08813.4060,W,1,,,219,,,,,*74
    $GPRMC,010401,A,4200.3256,N,08813.4060,W,0.0,0,201020,,,*3c
    $GPGGA,010402,4200.3256,N,08813.4060,W,1,,,219,,,,,*77
    $GPRMC,010402,A,4200.3256,N,08813.4060,W,0.0,0,201020,,,*3f
    $GPGGA,010403,4200.3256,N,08813.4060,W,1,,,219,,,,,*76
    $GPRMC,010403,A,4200.3256,N,08813.4060,W,0.0,0,201020,,,*3e
    $GPGGA,010404,4200.3256,N,08813.4060,W,1,,,219,,,,,*71
    $GPRMC,010404,A,4200.3256,N,08813.4060,W,0.0,0,201020,,,*39
    $GPGGA,010405,4200.3256,N,08813.4060,W,1,,,219,,,,,*70
    $GPRMC,010405,A,4200.3256,N,08813.4060,W,0.0,0,201020,,,*38
    $GPGGA,010406,4200.3256,N,08813.4060,W,1,,,219,,,,,*73
    $GPRMC,010406,A,4200.3256,N,08813.4060,W,0.0,0,201020,,,*3b
    $GPGGA,010407,4200.3256,N,08813.4060,W,1,,,219,,,,,*72
    $GPRMC,010407,A,4200.3256,N,08813.4060,W,0.0,0,201020,,,*3a
    $GPGGA,010408,4200.3256,N,08813.4060,W,1,,,219,,,,,*7d
    $GPRMC,010408,A,4200.3256,N,08813.4060,W,0.0,0,201020,,,*35
    $GPGGA,010708,4200.3402,N,08813.4275,W,1,,,244,,,,,*77
    $GPRMC,010708,A,4200.3402,N,08813.4275,W,0.0,0,201020,,,*37
    $GPGGA,010709,4200.3349,N,08813.4211,W,1,,,233,,,,,*7c
    $GPRMC,010709,A,4200.3349,N,08813.4211,W,0.0,0,201020,,,*3c
    $GPGGA,010710,4200.3307,N,08813.4145,W,1,,,234,,,,,*7b
    $GPRMC,010710,A,4200.3307,N,08813.4145,W,0.5399568,158,201020,,,*3d

    Recording apparently only occurs when the app is the active screen.

    This was run on a Pixel 3A with Android 11.

    As I recollect with my old Samsung Galaxy S4, I could lock the screen and the recording would continue (I had to do that to keep the battery from draining too quickly).

    Alan
  • Vote Up0Vote Down tomastomas
    please check permissions in Android settings/location/navigator
    should be set to Allow all the time
  • Vote Up0Vote Down AlanAlan
    Hi Tomas,

    Checked the setting and found it was set to 'Allowed only while in use'.  Changed to 'Allowed all the time' as you suggested.  I reran the sequence described above, and the NMEA file shows no dropouts in the recording, even with the screen locked.  So issue is solved.  Thanks!

    My use case for recording track files while the screen is off is the scenario when I am walking on a footpath that doesn't exist in OSM.  I do the recording to be able to add to OSM after the walk.  Since the path is not on the map in Navigator, there's no need to have the screen on at all while I walk.

    I did not know about or change the location permissions in Android, so I would think that it's a default setting of Android 11.  There's no indication in Navigator's Recording menu tab that an Android setting can affect the recording.  Would be nice to have a pop-up (with a 'Don't show again' button) mentioning that, so users can know how to set the permission as they desire.

    Best regards,

    Alan
Add a Comment

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Apply for Membership

Categories

In this Discussion