Opened 13 years ago

Closed 10 years ago

#444 closed defect/bug (Incomplete/Missing infos)

Text maps are too slow for showing track log

Reported by: Owned by: KaZeR
Priority: major Milestone: version 0.5.0
Component: core Version: git master
Severity: Keywords:
Cc: sybren@…


According to the documentation, it should be possible to do something like:

   <map type="textfile" ... data="/home/root/gpx/track.txt"/>
   <vehicle ...>
      <log type="textfile" data="/home/root/gpx/track.txt" flush_size="0" overwrite="1" />

However, enabling this track.txt map makes Navit become very, very slow when there is a considerable number of points in there.

It looks like the file is entirely re-parsed on every map position update, even though it is strictly only added to. This makes this feature unusable on my Neo Freerunner after only a few minutes of use. Imagine what happens when driving for a few hours...

Showing where a vehicle has been should be implemented in a different way, preferably by keeping a number of points RAM-only. Maybe some smart culling could be used to keep the used memory in check, such as showing only the last X points and/or not storing points when the user is standing (more or less) still.

My Magellan eXplorist 210 can show where I've been quite efficiently, and by the looks of it (and its age) it has way lower specs than a Freerunner - we should be able to get this right :)

To map an area it's quite useful to see where you've actually already been, so I feel that showing the track log is quite an important feature.

Change History (2)

comment:1 Changed 12 years ago by kazer

  • Milestone set to version 0.3.0

comment:2 Changed 10 years ago by usul

  • Resolution set to Incomplete/Missing infos
  • Status changed from new to closed

Can anybody still confirm this issue? Please reopen then and provide exact details (esp. a map test file and the part of your navit.xml)

Possible solutions:

  • Cache the paresed geometries
  • Reduce amount of geometries visualized (some tailing or clustering)
Note: See TracTickets for help on using tickets.