Custom Query (78 matches)
Results (37 - 39 of 78)
Ticket
|
Resolution
|
Summary
|
Owner
|
Reporter
|
#194 |
fixed
|
GTK UI:track logging broken
|
Martin Kolman
|
Martin Kolman
|
Description |
- logging trace is not shown on map until a color is selected
- if a tracklog detail has been visited, the logging menu "tools" goes to tracklog detail "tools"
- logging intervals seem to be ignored
- tracklogs that are created seem to be corrupted or in wrong format
|
#197 |
fixed
|
Routing : don't geocode start & destination when looking up route
|
Martin Kolman
|
Martin Kolman
|
Description |
- the two geocoding address lookups are slowing down re/routing
- most user also probably don't even check out the addresses in the route detail menu
- the geocoding should be thus triggered only when the user enters the route detail menu implemented
- or alternatively silently in the background once route lookup finishes
- there should be also an options to completely disable the routing related address geocoding - lower priority
|
#198 |
fixed
|
more efficient and robust track logging
|
Martin Kolman
|
Martin Kolman
|
Description |
- current setup
- currently the whole track is periodically dumped to a GPX file
- that means that the longer logging is running, the longer takes it takes to save the tracklog
- efficiency done
- just save the increment to a simple text file with one line per point (CSV)
- periodically save small increments (say 10 lines every 10 seconds for 1 point per second logging frequency)
- once logging is stopped, convert the simple text files to GPX
- check on startup if there are some files left from the last time (in case modRana couldn't exit cleanly)
- robustness done
- save to two files so that if one gets corrupted (eq. modRana or device crashing while the file is being written), there is still one left
|
Note: See
TracQuery
for help on using queries.