Custom Query (1067 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (103 - 105 of 1067)

Ticket Resolution Summary Owner Reporter
#1148 fixed Backup / Restore Function for Android Devices cp15 kamikaaze
Description This Patch will add a Backup and Restore function to the Android Version.

This may be usefull for Users with many Bookmarks, that are trying to switch from Google Play Store to Navit, which forces them to uninstall Navit, because the Packages have been signed with different Keystores.

A Backup consists of the following Files:

- /data/data/org.navitproject.navit/home/bookmark.txt
- /data/data/org.navitproject.navit/home/destination.txt
- /data/data/org.navitproject.navit/home/gui_internal.txt
- The Android specific Shared Preferences

A folder in the Navit Folder on the Users SD-Card will be created where those files are then stored.
#876 worksforme Bad routing analysed: attached bookmarks and screenshots for debugging KaZeR joysfera
Description I was wondering why current SVN Navit, when asked to plan route using OSM map between Zlin and Plzen (=Pilsen, both in Czech Republic) plans out a route via Austria that is 2,5x longer than needed (840+ km instead of 340 km). I tried to pinpoint the problem and have come to the following:

From "Zlin" (exact point given in the attached bookmark.txt) up to "Lodenice" the route is correct - using the D1 and D5 highways. When going farther in the "Plzen/Pilsen" direction on the D5 highway Navit breaks and stops routing altogether. When one gets to the point of "Zdice" Navit suddenly starts routing via Austria, a trip 2,5x longer than necessary!

Please try out using the attached bookmark.txt - it has three bookmarks named Start, Good and Bad. Use Start as Position and Good/Bad as Destination. The Good and Bad are exact points on the D5 highway where Navit starts breaking - move 100 m farther and Navit doesn't route at all.

Attached are also two screenshots showing the correct route to "Lodenice" and completely bogus one to neighbor "Zdice".

"Beroun" (another town on the D5 highway sitting in between of "Lodenice" and "Zdice") is an example of Destination that Navit cannot route to at all.

Note that it is crucial to use the "Start" bookmark as Position. If you use "Zlin" as position the breakpoints are different (but close to what I pinpointed above).

I have used a clean svn checkout (revision 4510/26104), selfcompiled and run with config file from Ubuntu Lucid Lynx's Navit 0.2.0~svn2897+dfsg.1-1build1.
#551 fixed Bad time format in gpx output kazer mvglasow
Description The time format in GPX output does not conform to the xsd_dateTime format since the time is represented as hhmmss rather than hh:mm:ss. Strangely, the first waypoint (and only the first) has the correct format but all the following have the faulty one. For example:
{{{
<trkseg>
<trkpt lat="45.495918" lon="9.112960">
<time>2010-02-20T19:01:38Z</time>
<course>0.0</course>
<speed>0.00</speed>
<extensions>
<navit:profilename>car</navit:profilename>
</extensions>
</trkpt>
<trkpt lat="45.495792" lon="9.112985">
<time>2010-02-20T190148.052Z</time>
<course>0.0</course>
<speed>0.00</speed>
<extensions>
<navit:profilename>car</navit:profilename>
</extensions>
</trkpt>
<trkpt lat="45.495892" lon="9.112880">
<time>2010-02-20T190149.051Z</time>
<course>0.0</course>
<speed>0.00</speed>
<extensions>
<navit:profilename>car</navit:profilename>
</extensions>
</trkpt>
<!-- remaining trkpts omitted -->
</trkseg>
}}}
The resulting GPX file will work for JOSM but, when uploading to OSM, only the first waypoint will get imported while the others will be rejected due to the bad <time> (OSM will report it as missing).

References:
http://www.topografix.com/gpx/1/1/gpx.xsd
http://books.xmlschemata.org/relaxng/ch19-77049.html
Note: See TracQuery for help on using queries.