From Navit's Wiki
Jump to: navigation, search

There are the most common troubles and solutions for those. Please add your soluted problem here.

Run time[edit]

Flooded land[edit]

Sometimes areas appear to be covered with water, even if there is just land. This is a result of defective OpenStreetMap data, here esp. the coastline borders.

You can help to fix that problem:

Permanently wrong announcements[edit]

A strange bug, where you get every few seconds the direction to turn, even if there is no obvious reason to do so. This can happen, if you have (accidently?) multiple binfile maps enabled.

Tickets #1039, #1046

Address not found[edit]

Even if can has various reasons that a specific address isn't found (not at mapdata, wrong data/data format, internal bugs, ...), it is a specific behaviour, if Navit couldn't recognize any of your local addresses.
This is caused how maptool recognizes OpenStreetMap addresses and how they are modelled [2] [3] [4]. In short: we do a lot of postprocessing, that is country-specific and needs to be adapted to your country. Currently there are just a few countries enabled that way:

  • Germany
  • Swiss

Navit hangs at "failed to create gui"[edit]

Example :

o (process:12367): WARNING **: failed to create gui 'sdl'
Using '/home/kazer/.navit/navit.xml'

Most likely, your navit.xml file is incomplete / erroneous. The best thing to try, is to start navit with the default configuration file :

./navit navit.xml

if you're running it from the source directory.

If it loads, then your configuration file is broken. First, check if you have the <plugins> section at the beginning of the file.

The easiest thing to do to fix this is probably to overwrite your own config file with the one shipped with Navit. Don't forget to read Configuring navit for some tips about the config file, especially if you run the SDL gui (GTK gui should work fine out of the box).

Navit complains: Error parsing 'navit.xml'[edit]


o Error parsing 'navit.xml': Element 'plugins' within unexpected context '(null)'. Expected 'config' at line 4, char 1

In the example the <config> opening and closing tags were missing from the navit.xml file.

My position is reported incorrectly[edit]

Most of the time, this is caused by the decimal separator being incorrectly set. Navit tries to override the decimal separator at startup, but the LC_ALL environment variable can block this. You can check this easily : echo $LC_ALL

If it returns something, you can't override your locale settings. You should "unset LC_ALL" and try again. If it works, you got it :)

In gentoo, this is set in the /etc/env.d/<something>locales. You may want to remove or comment the LC_ALL line in that file.

In the GTK gui, accents are broken in the buttons, and i get blank entries in the menus[edit]

Same thing as previously. The LC_ALL blocks you from changing the charset.

Navit routes me off a highway and then immediately back with OSM[edit]

If OSM has an highway=motorway_link with same speed limit as the highway then navit uses the ramp if it is technically a few meters shorter route. You can avoid this by searching for "<vehicleprofile name="car"" in navit.xml and setting "maxspeed_handling="1"" to make navit ignore the speed limit given in OSM and to default to 40 km/h (or whatever your navit.xml says) for highway=motorway_link.

This has been discussed at least at https://sourceforge.net/projects/navit/forums/forum/512960/topic/3702652


Navit speaks! But it's all English...[edit]

How do you configure Navit to speak one of the other 22 languages? How do you do that on Windows? How on Linux?

espeak on Linux[edit]

To get Navit to speak with espeak you can add the following XML to your navit.xml file:

 <speech type="cmdline"
         data="espeak --stdout -ven+f4 '%s'| aplay -"
         cps="15" />

This tells espeak to output in the English language (-ven) using female voice #4 (+f4).

To change the spoken language - say to Dutch - there are two things that need to change: the words that are to be spoken need to be translated to Dutch, and the speech pronunciation has to change to Dutch too.

For the first, you can change the LANG variable but much better solution is to use language attribute of the config tag:

 <config xmlns:xi="http://www.w3.org/2001/XInclude" language="nl_NL">

Here "nl" tells Navit to display its interface and announce directions in Dutch and "NL" to default town searching to the Netherlands. Change "nl_NL" to your preferred locale if you want something else. Note that the country and language do not need to be the same so "de_FR" is a perfectly valid combination for German in France.

To change the pronunciation -- I'll use Dutch again as an example -- use this in your navit.xml instead:

 <speech type="cmdline"
         data="espeak --stdout -vnl+f4 '%s' | aplay -"
         cps="15" />

For different eSpeak language codes see the eSpeak language documentation.

Weird coordinates in bookmarks.txt and centre.txt[edit]

Internally, Navit uses hexadecimal values to represent latitude and longitude values (see Coordinate format for details). These values spill over to the outside world in bookmarks.txt and centre.txt, where points are saved as hexadecimal values by default.

Convert hex coordinates to decimal degrees[edit]

The following example entry from centre.txt will be used as our example:

 mg: 0x7c877 0x6496e5

The first set of numbers/letters is the longitude, the second the latitude.

Step 1: Convert hex to integer
The first step is to convert the strings to integer values. This can be done in a variety of ways:

1) Online
A variety of converters can be found by Googling "hex to decimal converter". One such is Wolfram Alpha, which provides the following results (http://www.wolframalpha.com/input/?i=0x7c877+to+decimal):

 0x7c877  -> 510071
 0x6496e5 -> 6592229

2) Command line
Using the printf command, hex can be converted to decimal using the following command:

 printf "%d" 0x7c877
 printf "%d" 0x6496e5

Step 2: Convert integer to decimal degrees
The integers are then converted to decimal degrees using the following formulae (from navit/transform.c):

 Longitude: INT/6371000.0/PI*180
 Latitude: atan(exp(INT/6371000.0))/PI*360-90

You can drop the calculation straight into Wolfram Alpha, as below:

 Longitude: 510071/6371000.0/PI*180 = 4.5871787
 Latitude: atan(exp(6592229/6371000.0))/PI*360-90 = 50.877276

So there we go:

 Longitude: 4.5871787
 Latitude: 50.877276

Which is here, just in case you wanted to know...

Converting in one commmand

 Longitude: http://www.wolframalpha.com/input/?i=0x7c877/6371000.0/PI*180
 Latitude: http://www.wolframalpha.com/input/?i=atan(exp(0x6496e5/6371000.0))/PI*360-90

Convert decimal degrees to hex coordinates[edit]

Using the same location as the previous example:

 Longitude: 4.5871787
 Latitude: 50.877276

Step 1: Convert decimal degrees to integer
From navit/transform.c:


Dropping into Wolfram Alpha:

 4.5871787*6371000.0*PI/180 = 510071
 ln(tan(((50.877276+90)*PI)/360))*6371000.0 = 6592229

Step 2: Convert integer to hex coordinate

 Longitude: 510071 -> 7c877
 Latitude: 6592229 -> 6496e5

Don't forget the leading 0x to finish it off:

 Longitude: 0x7c877
 Latitude: 0x6496e5

Converting in one command

 Longitude: http://www.wolframalpha.com/input/?i=round(4.5871787*6371000.0*PI/180)+to+hex
 Latitude: http://www.wolframalpha.com/input/?i=round(ln(tan(((50.877276%2B90)*PI)/360))*6371000.0)+to+hex

Negative coordinates[edit]

Sometimes the decimal or hex coordinate values have a negative sign in front of it. This will denote either a southern latitude or a western longitude. If you perform the transformation in one step using Wolfram Alpha, you can keep the negative sign in the formula without problems. If you're transforming by hand, it's probably easiest to forget about the sign whilst transforming, and just add it back in at the end.

An example in hex is:

mg: -0x1c766 0x6812ff

Which can be put straight into Wolfram Alpha as follows:

 Longitude: http://www.wolframalpha.com/input/?i=-0x1c766/6371000.0/PI*180
 Latitude: http://www.wolframalpha.com/input/?i=atan(exp(0x6812ff/6371000.0))/PI*360-90


Build Logs[edit]

Build logs of released and committed revisions are available.

My compilation fails, complaining about GL/glc.h[edit]

You are missing the quesoglc package. We may switch to another more common library at some point. It isn't widely used, so maybe it isn't available via your distro's repository. If you can't find it, try to compile it from sources, available on the quesoGLC website

If your running Gentoo, you can grab an ebuild for it here : http://www.kazer.org/navit/quesoglc-0.6.0.ebuild.

Can't exec "autopoint": No such file or directory[edit]

You're missing gettext-devel.

configure.in:21: error: possibly undefined macro: AC_DISABLE_STATIC[edit]

You're missing libtool.

configure.in:25: error: possibly undefined macro: AC_DEFINE[edit]

If autogen.sh complains about missing macro AC_DEFINE or AC_MSG_WARN: You're missing pkg-config

gui_sdl_window.cpp:23:19: error: CEGUI.h: No such file or directory[edit]

You need Crazy Eddie's GUI development files. Ususally called cegui-devel or libcegui-mk2-dev.

Navit can't find libgarmin, but i installed it![edit]

Try :

export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/local/lib/pkgconfig/

Then re-run navit's configure