NavIT
Navit is a open source (GPL) car navigation system with routing engine.
It's modular design is capable of using vector maps of various formats for routing and rendering of the displayed map. It's even possible to use multiple maps at a time.
The user interface is designed to work well with touch screen displays. Points of Interest of various formats are displayed on the map.
The current vehicle position is read from gps
The routing engine not only calculates an optimal route to your destination, but also generates directions and even speaks to you.
Navit currently speaks over 70 languages!
You can help translating via our web based translation page : http://translations.launchpad.net/navit/trunk/+pots/navit
For help or more information, please refer to the wiki : http://wiki.navit-project.org
Maps:
The best navigation system is useless without maps. While others are known to work too, the simplest solution is to use OpenStreetMaps by downloading prepared map from the navit planet extractor.
This release is preconfigured to expect a map file at /home/nemo/Documents/map.navit.bin
Older releases up to verion 0.5.6-1 were preconfigured to expect a map file at /home/nemo/Maps/map.navit.bin instead. Move map to newer locatuin if upgrading.
Routing algorithm
NavIt uses a Dijkstra algorithm for routing. The routing starts at the destination by assigning a value to each point directly connected to destination point. The value represents the estimated time needed to pass this distance.
Now the point with the lowest value is choosen using the Fibonacci heap and a value is assigned to connected points whos are unevaluated or whos current value ist greater than the new one.
The search is repeated until the origin is found.
Once the origin is reached, all that needs to be done is to follow the points with the lowest values to the destination.
User configuration
Navit can be fully customized by copying and editing some xml files. Up to version 0.6.6-1, the user configuration directory was configured to be /home/nemo/.navit/ . Due to sandboxing requirements this was changed to be /home/nemo/.config/org.navitproject/navit . The default configuration is located under /usr/share/harbour-navit/ for all versions. Simply copy over the .xml files and start customizing.
Screenshots:
Category:
Keywords:
Application versions:
| Attachment | Size | Date |
|---|---|---|
 harbour-navit-0.5.1-2.armv7hl.rpm | 4.33 MB | 08/05/2017 - 14:14 |
| harbour-navit-0.5.1-2.i586.rpm | 4.36 MB | 08/05/2017 - 14:22 |
| harbour-navit-0.5.1-3.armv7hl.rpm | 4.92 MB | 21/06/2017 - 23:50 |
| harbour-navit-0.5.1-3.i586.rpm | 4.95 MB | 21/06/2017 - 23:50 |
| harbour-navit-0.5.3-1.armv7hl.rpm | 5.43 MB | 02/10/2018 - 01:04 |
| harbour-navit-0.5.3-1.i586.rpm | 5.46 MB | 02/10/2018 - 01:04 |
| harbour-navit-0.5.6-1.armv7hl.rpm | 5.47 MB | 29/04/2021 - 17:15 |
| harbour-navit-0.5.6-2.aarch64.rpm | 5.49 MB | 24/05/2022 - 16:50 |
| harbour-navit-0.5.6-2.armv7hl.rpm | 5.47 MB | 24/05/2022 - 16:50 |
Changelog:
Hello Navitters,
Great news: Navit 0.5.6-2 is out now. Please read this changelog.
- Minimum required version is Sailfish 3.4.0.24. Should be good for Jolla1
- Enable sandboxing on Sailfish 4.4
- Default map location moved from /home/nemo/Maps/map.navit.bin to /home/nemo/Documents/map.navit.bin due to sandboxing requirements. Move maps if required.
- User configuration moved from /home/nemo/.navit to /home/nemo/.config/org.navitproject/navit due to sandboxing requirements. Ensure to move custom configuration and bookmarks to new location after update if required.
- aarch64 support (completely untested due to lack of device. Any donors?)
If you want to know about other changes see the Changelog at: https://github.com/navit-gps/navit/blob/v0.5.6/CHANGELOG.md
For the full list of commits, see: v0.5.5...v0.5.6
Please report issues at https://github.com/navit-gps/navit/issues/new
The documentation can be found at http://wiki.navit-project.org/ and https://navit.readthedocs.io/en/trunk/index.html
To get the latest builds, see: http://download.navit-project.org/
Happy routing!
Comments
NGC_Ollie
Wed, 2024/08/07 - 12:22
Permalink
Hi, are you still active here? Navit stopped starting on my device and IDK why. If anyone knows where to start I'd provide detailed information.
metalstrolch
Wed, 2024/08/21 - 22:36
Permalink
I've built latest navit using the latest Sailfish SDK 4.6.0.13 hopefully resolving the segfault. However I've run out of usable Sailfish devices right now since my Sony died. So I cannot test the thing any more. I myself are on UBTouch at the moment porting navit there. So gie it a try and report back.
NGC_Ollie
Sat, 2024/11/23 - 01:08
Permalink
Dear Metastrolch, Thanks for your reply, I'm so sorry, I simply missed your comment. I really would like to test your build, but where can I get it? I didn't find it anywhere, could you please provide a link? And if you are unable to test, I might be able to do so if you have any test cases or so.
ade
Wed, 2024/08/07 - 13:43
Permalink
FYI: I see a SFOS 4.6 bug report here from 2 weeks ago: https://github.com/navit-gps/navit/issues/1268, including a hacky workaround for the issue.
Meminga
Sat, 2022/06/25 - 20:25
Permalink
Thanks a lot for the app. A profile without "Autobahn/Kraftfahrstraße" (probably "express way" in english) for smaller motorbikes or scooter would be cool.
NGC_Ollie
Fri, 2022/05/13 - 00:17
Permalink
Sorry to bother you again, we now have a different problem: it seems that navit lost access to its own folders or to the SD card. I'm unable to get my world map on my external storage working. I guess it is because of the sailjail, but I'm really just guessing since i can access those symlinks by command line and they are working. Also the file manager is unable to find those folders like "~/Maps", "~/.navit" or ".local/share/navit" since the introduction of sailjail. Maybe you can help here? Thanks a lot!
metalstrolch
Wed, 2022/05/18 - 16:42
Permalink
This is unfortunately a currently known issue. I'm investigating how to correctly make navit fit into the sandboxing requirements. Unless there is a new release available fixing this you can temporarily disable Sailfish sandbox for NavIT by adding the following lines to navit's desktop file:
[X-Sailjail]
Sandboxing=Disabled
Unfortunately this requires developer console right now.
metalstrolch
Tue, 2022/05/24 - 16:52
Permalink
Now fixed. Please read changelog.
NGC_Ollie
Thu, 2022/06/09 - 08:37
Permalink
Thanks a lot it is working like a charm! Keep up the good work!
zipotron
Wed, 2021/05/05 - 08:24
Permalink
Thanks a lot for bringing last update of Navit! Just wanted to ask, looking forward the X 10 II, that will use the arm64, could you publish a compilation for it? I am one those waiting for flash a X 10II. Thanks!
metalstrolch
Tue, 2022/05/24 - 16:53
Permalink
aarch64 version available now although completely untested due to no device.
nephros
Fri, 2021/04/30 - 22:21
Permalink
The link to maps in the app description redirects to some weird video site.
Thanks for the bump though, I haven't been aware of this app until now.
metalstrolch
Sat, 2021/05/01 - 01:45
Permalink
Changed the link to the map downloader despite it was not wong. Guess this is a temporary problem on the downloader setup. I don't run that site though. Now it should work again. Thanks for spotting.
NGC_Ollie
Sat, 2021/05/01 - 23:17
Permalink
Since we are talking about the map extractor: it is kinda broken. I used to download the whole planet to my SD card, but the latest planet (26.03.21 with 40,4GB) seems to be broken. If I use my old map from 14. Th July 2020, navit starts smoothly, if I use 210326 it gets stuck a few times (watchdog dialog) and i have no map. Download of any European map fails as well. Read issue 1112 on github for more details. Are there other sources for maps?
NGC_Ollie
Tue, 2021/04/27 - 23:07
Permalink
Hi. Is this still active? On my XA2 plus with SailfishOS 4.0.1.48 I'm unable to use bin-maps on my sd-card. A map inside ~/.navit/map.bin works. My ~/.navit/navit.xml:
<?xml version="1.0"?>
config>
When I used the command line, it was complaining about the syntax, but the version above was without errors. Any suggestions?
metalstrolch
Thu, 2021/04/29 - 17:22
Permalink
This is more or less still active, however there is no special "Sailfsh" version any more. It is developed as part of the usual Navir release cycle. See https://github.com/navit-gps/navit/releases
Unfortunately the xml file you posted got eaten by html filter of this site, but if Navit complains about syntax errors in xml file, then those most likely caused the map to not be there.
If in doubt remove the entire ~/.navit directory. No "need" to configure the map in the xml file. Just put your map to /home/nemo/Maps/map.navit.bin and it should work. You may need to create the /home/nemo/Maps directory to do this. This is the default config in the rpm's for now.
metalstrolch
Thu, 2021/04/29 - 17:25
Permalink
Preferred solution to get the map on a sd card is to make /home/nemo/Maps/map.navit.bin a symlink to location on sd card. Navit cannot search for maps right now really.
NGC_Ollie
Thu, 2021/04/29 - 21:12
Permalink
Wow, twice thanks to you! Symlink was working out of the box with my running 0.5.3, nice. Then I did the upgrade of your package to 0.5.6. Runs smoothly and uses my map. Double win within a few hours. Top developer, would buy again (XML sucks anyways)
olf
Mon, 2018/09/03 - 22:47
Permalink
Thank you very much @metastrolch for continuously maintaining, contributing to and packaging the SailfishOS port of NavIt.
As updating NavIt 0.5.1-3 to 0.5.3-0 fails on my device, I filed NavIt issue #654.
Hopefully filing SFOS-specific issues at NavIt's Github-based issue tracker was your intention, it took me a little while to understand that no separate Source Code repository (and issue tracker) for NavIt for SFOS exists.
Hence I believe it would be helpful to clearly denote in the description of NavIt on this OpenRepos page (above), where issues ought to be filed, and to provide a web-link to that location (e.g. https://github.com/navit-gps/navit/issues ).
metalstrolch
Tue, 2018/10/02 - 01:05
Permalink
Fixed with 0.5.3-1
olf
Tue, 2018/10/02 - 01:27
Permalink
Thanks!
gaelic
Sun, 2017/06/25 - 10:51
Permalink
As Navit has not seen updates since 2015, are you considering changing the routing backend maybe to http://www.routino.org? Benefits: it supports different ways of travel like foot, bike, car.
metalstrolch
Sun, 2017/06/25 - 14:40
Permalink
???
NavIT is actively developed ever since, and can route for different Vehicles including pedestrian. So there is no need to replace its backend. What makes you think its outdated?
247
Thu, 2017/06/22 - 12:20
Permalink
hi there...a question and a little thing i would like to change... :)
the thing i would like to change is the keyboard...a qwerty qould be a lot better than an abcd etc etc
now for the question...i wanted to store the maps on the sd card and tried to edit the xml for doing that, but i cannot find the location where i can change the path...any help on this?
by the way do you plan to give the app a more sailfish look?
metalstrolch
Thu, 2017/06/22 - 12:13
Permalink
The internal keyboard layout is due to hardware with rotary encoders or just arrow buttons. But there are plans to use Sailfish native Keyboard instead. But this may take some time.
To 1: navit planet extractor maps are automatically created out of openstreetmap data. So feel free to enhance your city in openstreetmap. For other map options have a look at http://wiki.navit-project.org/index.php/Maps , but there are no really good alternatives to openstreetmap at the moment.
To 2: The "default" configuration is at /usr/share/harbour-navit/navit.xml Needs "root" rights to modify. But you can copy it to ~/.navit/navit.xml and adapt changes there. This overrides the default settings completely. Then your changes are not lost if you update navit later on.
Alter the "mapset" tag in navit.xml. Search for map.navit.bin in navit.xml to find it. Be careful with adding multiple maps at a time. Although NavIT supports this, this can break routing if the maps don't fit to each other.
Or the better and simpler solution: Symlink the map from where ever you want it to be to ~/Maps/map.navit.bin instead of just copying it there. This requires no change in configuration at all and is my preferred way in doing this.
To3. I myselve not. But someone else is working on a QML GUI which then may be adapted to Sailfish Silica easily. Unfortunately Sailfish Silica is compatible to nothing, and the focus is on portable QML.
247
Thu, 2017/06/22 - 12:24
Permalink
thanks for your fast reply...i'll update my questions since i solved some of them...now the app is correctly showing all the streets...maybe it was a corrupted download so downloaded maps again and now is working...
as for the xml file...i know but i can't find how to point navIT to search for maps in the sd card...i can't find any path to change in the xml file
hope anyway the new interface will be simpler to use :)
keep up the good work anyway :)
metalstrolch
Thu, 2017/06/22 - 16:45
Permalink
Navit cannot search for maps. All maps need to be enabled in navit.xml. See "mapset" tag.
DrYak
Fri, 2017/05/12 - 17:47
Permalink
Thank you very much for this port !
I used to enjoy Navit back on my Palm/HP Pre smartphones (also full GNU/Linux like Jolla, but HTML-based instead of QML).
I was hoping to find some free time to do a recompile myself but you beat me to it. :-P
Thank you again for your work !
paolomi
Fri, 2017/05/12 - 11:02
Permalink
I'm testing navit for some days, it's beautiful, many thanks for having ported it to sailfish os! I've 2 questions:
- how to save settings? now i change settings, then i close navit, but when I run navit again, there are always the default settings. It doesn't remember my settings.
- how to switch portrait / landscape?
Many thanks :)
ps: there is a bug with the button "Quit". If i run navit from command line, the button "quit" works properly, but if I run navit tapping the icon, the button "quit" doesn't work and i have to quit the app with the swipe (top-down).
Bye:)
metalstrolch
Fri, 2017/05/12 - 13:23
Permalink
NavIT right now is just a QT application. It doesn't cope for many Sailfish specialities yet.
About the quit button: Sailfish OS expects all applications not to quit on their own. So Sailfish does expect the applications to have no quit button. They are to be killed by the window manager (by down swipe or long press). NavIT is still a normal application. So it's quit button does exactly what it should. It quits the application. Unfortunately Sailfish's window manager then keeps the window and relaunches the app if pressed into it. If run from the command line everything behaves as usual. Im looking into how to tell the window manager to quit it as well, but for me this is less important right now.
About settings saving: This is a little bit tricky. While NavIT saves many things immediately when they happen (for example the routing target) other things are saved only when navit is quit (the last shown area on the map) , and again other things are not saved ever. This is not only a problem for Navit on Sailfish, but for navit with internal GUI anywhere. The things saved on navit quit are unfortunately NOT saved when NavIT gets killed by Sailfish window manager. This is the reason for not removing the quit button :).
About landscape mode: Navit does not yet support screen rotating. Since this should not bee too tricky on Qt5 backends, I plan on implementing this. Stay tuned.
Btw. You can set the defaults of most options in the navit.xml configuration file. No GUI for that.
Pages