23 files changed, 3627 insertions, 0 deletions
diff --git a/Documentation/CREDITS b/Documentation/CREDITS
new file mode 100644
index 0000000..d3c83e2
--- /dev/null
+++ b/Documentation/CREDITS
@@ -0,0 +1,15 @@
+Thanks for translations:
+
+French:    Jacky Francois <jfrancois@free.fr>
+Dansk:     Andreas Hinz <news1@acci.dk>
+Spanish:   Félix Martos <pakito@asinkecualo.org>
+Dutch:     Dirk-Jan Faber <dirk-jan@selwerd.nl>
+Italian:   Manfred Caruso <bertoz@bertoz.com>
+German:    Fritz Ganter <ganter@ganter.at> :-)
+Hungarian: Emese Kovács <emese@gnome.hu>
+Slovak:    Zdeno Podobný <zdpo@mailbox.sk>
+Swedish:   Martin Sjögren <md9ms@mdstud.chalmers.se>
+Japanese:  <maruyama@sh.rim.or.jp>
+Greek:     Yiannis Pailas <johntop@pathfinder.gr>
+Norwegian: Alexander Wigen
+Turkish:   A. Burak Ilgicioglu <ilgici@ttnet.net.tr>
diff --git a/Documentation/FAQ.gpsdrive b/Documentation/FAQ.gpsdrive
new file mode 100644
index 0000000..1394f50
--- /dev/null
+++ b/Documentation/FAQ.gpsdrive
@@ -0,0 +1,260 @@
+This is the GpsDrive FAQ.
+This file is maintained by Fritz Ganter.
+
+Q: Why is this file so short?
+A: I'm still working on it.
+
+Q: GpsDrive 2.x: After compiling Gpsdrive from source, I have the
+   problem that GpsDrive will not display the map when it's running.
+   All of the graphics in the map area are blank. 
+A: Compile with gcc 3.x, this bug is know at least with debian and
+   slackware.
+
+Q: GpsDrive shows "Not enough satellites in view" in the statusbar and don't
+   display my position.
+A: You need at least 3 satellites in view to get a valid position. It may also
+   take some minutes to get a valid position. You have to be outside under
+   clear sky; GPS mostly doesn't work inside the house. Trees, houses or other 
+   barriers can prevent your GPS receiver getting a valid position.
+   Some GPS receivers have a "Simulation mode" which sends position 
+   signals, but with a "invalid position" flag. GpsDrive won't display
+   a position if this "invalid position" flag is set. To override this
+   (do it only for testing!!!) you can call GpsDrive with the 
+   "-F" command line parameter.
+   
+Q: I have a USB GPS receiver, it works fine with GpsDrive but if I
+   leave the program, Linux crashes.
+A: This is a bug of the "Prolific PL2303 USB to serial adaptor driver"
+   which is used. The crash happens if the serial device is
+   closed. This bug is kernel >=2.4.19
+   One solution is to use a kernel 2.6.x where this
+   bug is fixed, or 2.4.18 where it doesn't appear.
+
+Q: Why is there no street navigation which gives turn by turn
+   directions?
+A: Turn by turn directions are not possible with GpsDrive at the present
+   because no opensource data is available which represents the street
+   coordinates in a form usable for that purpose.  GpsDrive currently
+   works with bitmap images rather than vector data.
+   We are working together with the OpenStreetMap Project to get there.
+   As you can see the first attemts to use OpenStreetMap.org Data to 
+   do route finding (outside of GpsDrive) where already successfull.
+   So we can hope for this feature in the future.
+
+Q: What is GpsDrive?
+A: GpsDrive is an open source navigation system. It displays your current
+   position provided by an NMEA capable GPS receiver(connected to gpsd)
+   on a zoomable map.
+
+Q: How do I install GpsDrive on a Linux box?
+A: This depends on the Distribution you're using.
+   On Debian Systems you can use the debian repository at http://www.gpsdrive.de/debian/
+   On other Systems I recommend to use the source tarball. Download it from 
+   http://www.gpsdrive.de/.
+   Unpack the tarball with `tar xvzf gpsdrive-X.XX.tar.gz` where X.XX is the version
+   number. Now change into the directory gpsdrive-X.XX and run `./configure`.
+   Some people (including me, Sven) don't like the Garmin protocol. It can
+   be easily disabled with the option `--disable-garmin`. Now run `make`.
+   Depending on your CPU power this will take something between 4 seconds and
+   3 minutes. An Intel Celeron 1000 takes approximately 50 seconds to have
+   the version 1.28pre1 compiled. Now do a `su`, enter your root password and
+   continue with a final `make install`.
+
+Q: I am running FreeBSD. Can I use GpsDrive too?
+A: Yes. See the file README.FreeBSD for further information.
+
+Q: I'm trying to run GpsDrive on iPAQ, but I don't have /dev/ttyS0.
+A: You may want to use /dev/tts/0. When using gpsd, you will have to change
+   some parameters in /etc/gpsd.conf. Use -p /dev/tts/0 and -s4800.
+
+Q: I'm too lazy to get out of my bed, how can I test with my GARMIN GPS III?
+A: Your GARMIN has a built in simulator. Start it on the "satellite screen",
+   then go to setup and enter a speed in the simulator menu. Then
+   "goto" a stored waypoint and look how fine GpsDrive works. Don't forget 
+   to download your maps first.
+
+Q: How can I get detaled maps to be displayed?
+A: Either you use Openstreetmap Data with Mapnik in Combination.
+   or 
+   You Download PixelMaps with the "Download map" button located under
+       Options - Maps - Download.
+   After pressing it, a new window will appear. 
+
+
+Q: Can I download multiple maps covering a larger area?
+A: There is a script called "gpsfetchmap.pl" provided. Use the "-h" option
+   to get a help screen.
+
+Q: Can I use own maps?
+A: Yes. Of course you can use your own (self drawn, scanned...) maps. The
+   maps must be gif, jpeg, png or other common file formats (the format
+   must be recognized by the gdk-pixbuf library).  The lat/long coordinates
+   you write into the "map_koord.txt" file must be the center of the map.
+   The map must have a size of 1280x1024 pixels! Important! The maps must be
+   named map_* for streetmaps and top_* for topographical maps. If not,
+   GpsDrive won't display the maps. GpsDrive comes with an import assistant.
+   Simply use the Menu item Options->Maps->import and follow the instructions.
+
+Q: What is the mapnik?
+A: Manik is a renderer for Openstreetmap data. You can active the mapnik mode
+   by checking the mapnik option (map controls).
+
+Q: There is no mapnik option?
+A: It is only available if you have installed the mapnik packages. Have a look
+   at install-mapnik-osm.txt.
+
+Q: Which GPS receivers work with GpsDrive?
+A: Any receiver that is recognized by gpsd should work. 
+
+Q: Which receiver is the best one?
+A: This is a religious question, just like the one for the best editor or mail
+   client (which is vi and mutt).
+   Fritz: No, off course its emacs and evolution.
+   Joerg: Alsmost; is's emacs and kmail ;-)
+   
+Q: How can I use the Holux GM-200 USB with GpsDrive?
+A: This device has the Prolific PL-2303 chip in it for the USB => Serial
+   conversion.  The USB => Serial "pl2303.c" driver seems to work pretty
+   well!
+   
+   Quick Start:
+
+   Build GPSDrive (Requires GTK 2)
+   Build new kernel (or module) using "USB Prolific 2303 Single Port Serial
+   Driver (EXPERIMENTAL)" Load the new kernel || module
+   Do: `mknod /dev/ttyUSB0 c 180 0` (If it doesn't already exist)
+   Do: `chmod 666 /dev/ttyUSB0`
+   Do: `gpsd -p /dev/ttyUSB0`
+   Do: `gpsdrive`
+   (provided by Todd E. Johnson)
+   Hint: You want to use a kernel >= 2.4.18. ;)
+
+
+Q: Why is such funny english used in gpsdrive?
+A: Fritz is from Austria and speaks the same kind of "english" as Arnold
+   Schwarzenegger.
+
+Q: Can I use GpsDrive without a GPS receiver?
+A: Yes.  You might want to do this when you have a fast internet connection
+   for downloading maps etc.  Also, you can use it to review stored journey
+   tracks (see below).
+
+Q: Does GpsDrive handle 'tracks' saved in my GPS receiver?
+A: Yes.  You should save the tracks in the .gpsdrive directory (using
+   something like 'garble' or 'gpspoint')  - then you can load them into
+   GpsDrive from the GUI.
+
+Q: I know that we aren't supposed to use GpsDrive 'for navigaton purposes' -
+   but is it any use to (student) aviators?
+A: Certainly - pack your GPS unit in your flight bag (turned on of course!),
+   then download the tracks into GpsDrive when you get home.  It's a great way
+   to see exactly how good your navigational skills are - or maybe where you
+   busted airspace!  Flying schools could use this to analyse students' solo
+   navigational trips.
+   
+Q: I have also noticed that the unique ID sent to my Friendsd2 server from
+   my gpsdrive is not unique
+   Is there a way to manually set the unique ID to correct this problem?
+A: Have a look at ~/.gpsdrive/gpsdriverc:
+      friendsidstring = XXX
+   If you delete the key in the file or set it to XXX you should get a new 
+   FriendsID.
+
+Q: My gps seems like being always behind the actual position. It seems like 
+   I'm 13seconds behind.
+A: The problem isn't gpsd or gpsdrive, the problem is the SiRF firmware. Check
+   the gpsd mailinglist.
+   If the GPS device is in SiRF mode, gpsd translates SiRF binary mode to NMEA
+   mode and you'll get a lag of about 13 sec. But if you set the device to
+   NMEA mode, it will work just fine.
+   The question is if gpsd should provide the possibilty to start the GPS
+   device with NMEA mode or if there should be an option in gpsdrive. The
+   default is always the binary mode because it will provide more
+   informations.
+   Solution for gpsdrive users: 
+	gpsd_nmea.sh        
+
+Q: if i download 5m, 500k, 50k and 5k and open gpsdrive, i get
+   the smallest map that i can not zoom out at all.
+A: If you're using automap gpsdrive alway displays the map with 
+   the smallest resolution it can find. Changing the scale 
+   has no effect while autobestmap is on.
+
+Q: if 'auto best map' is disabled, i sort of can choose scale at the lower
+   right corner, but i can not zoom in from the biggest view and get small
+   scale maps automatically...
+A: If autobestmap is disabled gpsdrive should select the smallest-scale map
+   greater then your suggested scale.
+   With "Pref. scale" you tell gpsdrive which scale you'd prefer to have. 
+   Then gpsdrive has a look at every map in map_koord.txt to see which map 
+   is in sight with a map-scale >= pref-scale.
+
+Q: I also can not find a way to move the map (as i can see larger area in
+   lower left hand corner...)
+A: If you click on pos-mode. You can set your Car-Position in Gpsdrive to
+   any location on the map. If your car-position is in the outer ~10% of 
+   the map gpsdrive tries to see if there is a map available which 
+   would fit better for your Position.
+
+Q: What is the map projection GPSDrive uses?
+A: To be picky, as it is critical to be picky in order to get this stuff
+   working correctly:  (especially with gdalwarp & PROJ4 parameters)
+   WGS84 defines both a datum & an ellipsoid, but not a projection. The
+   projection is lat/lon (well, it's unprojected I guess).
+
+   Here are some links to primers on Geodesy (Projections and Datums):
+   http://grass.gdf-hannover.de/twiki/bin/view/GRASS/GisConcepts
+
+   To answer your question though,
+
+   If you title the image "map_*" the projection is assumed to be UTM-like
+   (preserves equal area); if the map is named "top_*" it is assumed to be
+   "Plate Carrée"*, ie equi-rectangular 1:1 lat to lon.
+
+   UTM-like will be scaled 1:cos(lat) in the x and y dir. If you can draw
+   grid or add test points to the image, you can check against grid lines
+   or self-entered waypoints in gpsdrive to make sure everything is
+   matching.
+
+   [*]  http://en.wikipedia.org/wiki/Plate_carr%C3%A9e_projection
+
+Q: Converting Old Maps
+A: If you have old expedia maps on your system and want 
+   to reuse them you should move them to a 
+   subdirectory ~/.gpsdrive/maps/expedia/ 
+   and add expedia/ before every map entry in map_koords.txt
+   then you can take map_koord.txt and move it one directory
+   down to  ~/.gpsdrive/maps/map_koord.txt
+
+   Any other map should be moved in a similar way.
+
+Q: What's this "no dir" checkbox in the maps Section 
+A: This is because of the change in the map directory structure. See below
+
+Q: I'm missing the "download map" button
+A: It was moved into the menu, since normally you don't need it while driving.
+
+Q: After Upgrading I don't see any maps. But the old .gpsdrive dir 
+   is still there with the maps.
+A: We have a new map directory structure.
+   You'll have to create a directory .gpsdrive/maps/... .
+   The tree then will look like:
+   ~/.gpsdrive/maps/mapservice-xy/...
+   And your map_koord.txt is now located in the 
+	~/.gpsdrive/maps/
+  Directory and look like this:
+ top_Africa.jpg         0.0     25.0     30000000
+ top_America.jpg       10.0    -90.0     40000000
+ top_Australia.jpg    -24.700  132.3     11651916
+ top_Europe.jpg        52.5     12.0     11000000
+ top_Germany.jpg       51.0     11.9      3500000
+ top_GPSWORLD.jpg       0.0      0.0     88067900
+ top_NorthAmerica.jpg  37.8167 144.9667  20000000
+ top_SouthAmerica.jpg -20.0    -80.0     20000000
+ top_WorldEast.jpg     30.0   -100.0     40000000
+ eniro/1000000/57/57.4/11/map_1000000-57.4-11.6666666666667.gif 57.4000000000000, 11.6666666666667, 592500
+ ...
+ landsat/500000/49/12/map_500000-49-12.8333333333333.gif  49.0000000000000  12.8333333333333    500000
+ ...
+
+  where the top_Africa.jpg maps come from the system directory.
diff --git a/Documentation/FAQ.gpsdrive.fr b/Documentation/FAQ.gpsdrive.fr
new file mode 100644
index 0000000..11d73b4
--- /dev/null
+++ b/Documentation/FAQ.gpsdrive.fr
@@ -0,0 +1,125 @@
+Ceci est la FAQ de GpsDrive.
+Ce fichier est maintenu par Sven Fichtner, traduit en français par Jacky Francois.
+
+Q: Pourquoi cette FAQ est-elle si courte?
+R: Parce que je suis encore en train de l'écrire.
+
+Q: Pourquoi GpsDrive ne me guide-t-il pas en m'indiquant oů tourner?
+R: Ce n'est pas possible pour le moment car il n'existe pas de plans vectoriels
+   opensource, c'est-ŕ-dire des plans contenant les coordonnées des rues.
+   
+   Si vous connaissez des plans vectoriels opensource faites-le savoir. Ces plans
+   doivent contenir le nom de l'agglomération, le nom des rues ainsi que leurs
+   coordonnées géographiques.
+
+Q: Qu'est-ce que GpsDrive?
+R: GpsDrive est un prgramme libre de navigation. Il affiche votre
+   position fournie par un récepteur GPS NMEA sur une carte zoomable.
+
+Q: Comment puis-je installer GpsDrive sous Linux?
+R: Je vous recommande de l'installer ŕ partir des sources. Téléchargez-les sur 
+   n'importe quel    miroir (http://gpsdrive.spoiledmeat.net/ est le plus
+   rapide en Europe). 
+   Décompressez l'archive en tapant `tar xvzf gpsdrive-X.XX.tar.gz` oů
+   X.XX est le numéro de version. Rendez vous maintenant dans le
+   répertoire gpsdrive-X.XX et lancez `./configure`. Certaines personnes 
+   (dont moi, Sven ) n'apprécient pas le protocole Garmin. Il peut
+   facilement ętre désactivé avec l'option `--disable-garmin`. Lancez
+   maintenant `make`. En fonction de la puissance de votre CPU la
+   compilation prendra entre 4 secondes et 3 minutes. Un Celeron 1000
+   d'Intel prendra approximativement 50 secondes pour compiler la version 
+   1.28pre1. Vous pouvez ŕ présent taper `su`, entrer votre mot de passe
+   root et terminer la procédure par `make install`. 
+
+Q: J'utilise FreeBSD. Est-ce que je peux y utiliser Gpsdrive?
+R: Oui. Consultez le fichier README.FreeBSD pour de plus amples informations.
+
+Q: Je tente de faire tourner GpsDrive sur un iPAQ mais je n'ai pas /dev/ttyS0.
+R: Utiliser /dev/tts/0 peut résoudre votre problčme. Avec gpsd vous
+   devez modifier certains paramčtres dans /etc/gpsd.conf. Utilisez -p
+   /dev/tts/0 et -s4800.
+
+Q: Je suis trop faignant pour sortir de mon lit, comment tester mon
+   GARMIN GPS III?
+R: Votre GARMIN a un simulateur intégré. Démarrez-le sur "l'écran
+   satellite", puis allez dans les paramčtres et entrez une vitesse dans
+   le menu simulation. Puis allez (goto) un waypoint en mémoire et
+   constatez comme GpsDrive marche bien. N'oubliez pas de télécharger vos
+   cartes au préalable.
+
+Q: Comment puis-je télécharger des cartes?
+A: Il y a un bouton "Télécharger". Appuyez sur ce bouton pour accéder
+   ŕ la fenętre dédiée. 
+
+Q: Est-ce que je peux télécharger plusieurs cartes pour couvrir une
+   zone plus grande?
+A: Le script "gpsfetchmap.pl" est fourni. Avec l'option "-h" un écran
+   d'aide s'affiche.
+
+Q: Est-ce que je peux utiliser mes propres cartes?
+A: Oui, vous pouvez bien évidemment utiliser vos propres cartes (
+   faites par vous-męmes, scannées... ). Les cartes doivent ętre au
+   format gif, jpeg, png ou tout autre format reconnu par la librairie 
+   gdk-pixbuf. Les latitude et longitude que vous entrez dans le
+   fichier "map_koord.txt" doivent ętre celles du centre de la
+   carte. La carte doit ętre au format 1280x1024! Important! Les
+   cartes doivent avoir pour noms map_* pour les plans et top_* pour
+   les cartes topographiques. Dans le cas contraire GpsDrive
+   n'affichera pas les cartes. GpsDrive dispose d'un assistant
+   d'importation. Appuyez simplement sur le bouton 'Importer' et
+   suivez les instructions.
+
+Q: Quels sont les récepteurs GPS qui fonctionnent avec GpsDrive?
+A: n'importe quel récepteur capable d'envoyer des informations NMEA
+   sur port serie ou USB devrait fonctionner. Le fichier GPS-receivers
+   contient les récepteurs qui ont été testés.
+
+Q: Quel est le meilleur récepteur?
+A: C'est le genre de question qui déchaine les passions, comme celle du meilleur 
+   éditeur ou client mail ( qui sont respectivement vi et mutt ).
+   Fritz: Bien sűr que non, c'est Emacs et Evolution.
+
+Q: Est-ce que je peux utiliser le Holux GM-200 USB avec GpsDrive?
+A: Ce périphérique intčgre le composant Prolific PL-2303 pour
+   l'adaptation USB => Série. Le driver USB => Serial "pl2303.c"
+   semble bien fonctionner!
+
+   Installation rapide:
+
+   Compilez GpsDrive (nécessite GTK 2)
+   Compilez un nouveau noyau (ou module) intégrant "USB Prolific 2303 
+   Single Port Serial Driver (EXPERIMENTAL)" 
+   Chargez le nouveau noyau/module.
+   Tapez: `mknod /dev/ttyUSB0 c 180 0` (si ce fichier n'est pas déjŕ présent)
+   Tapez: `chmod 666 /dev/ttyUSB0`
+   Tapez: `gpsd -serial /dev/ttyUSB0`
+   Tapez: `gpsdrive`
+   (procédure de Todd E. Johnson)
+
+Q: Pourquoi la version anglaise est-elle si étrange?
+R: Parce que Fritz est Autrichien et parle un anglais ŕ la Schwarzenegger.
+
+Q: Est-ce que je peux utiliser GpsDrive sans récepteur GPS?
+R: Oui. Ceci peut s'avérer utile pour télécharger des cartes lorsque vous disposez
+   d'une connexion internet rapide par exemple, ou pour consulter une route que vous
+   avez sauvegarder ( voir plus bas ).
+
+Q: GpsDrive est-il compatible avec les routes sauvegardées dans mon récepteur GPS?
+R: Oui. Vous devez placer les fichiers contenant les routes dans votre répertoire 
+   de configuration de gpsdrive (~/.gpsdrive), en utilisant 'garble' ou 'gpspoint'.
+   Vous pourrez alors les afficher dans le programme.
+
+Q: Je sais que GpsDrive n'est pas concu pour la navigation, mais peut-il ętre utile
+   pour des ( apprentis ) aviateurs?
+R: Bien sűr. Pendant le vol, enregistrez vos routes avec votre GPS. Aprčs le vol,
+   téléchargez ces routes dans GpsDrive. Ceci est un bon moyen d'évaluer vos
+   compétances, ou vos écrats par rapport ŕ la théorie! Les écoles de pilotage peuvent
+   avoir recours ŕ cette méthode pour analyser les vols en solitaire de leurs 
+   élčves.
+
+
+
+
+
+
+
diff --git a/Documentation/GPS-receivers b/Documentation/GPS-receivers
new file mode 100644
index 0000000..f14053e
--- /dev/null
+++ b/Documentation/GPS-receivers
@@ -0,0 +1,26 @@
+Those GPS receivers are known to work with gpsdrive:
+
+Magellan 310, 315, 320
+Garmin GPS III
+Garmin etrex
+GPS 45
+Crux II GPS PCMCIA card
+Holux GM-200 serial version
+Holux GM-200 USB (needs USB to serial support in kernel)
+Holux GM-210 USB (needs USB to serial support in kernel)
+Garmin eMap
+Garmin GPSMAP 295
+Garmin GNS 530
+Garmin GPS 12MAP
+EAGLE Expedition II
+DeLorme Earthmate
+Rayming TripNav, TN-200
+Haicom HI-203E
+GM-307 USB-Mouse
+Magellan Meridian Gold (works only with NMEA V2.1 GSA setting)
+NAVILock GPS Receiver (http://www.navilock.de)
+Haicom GPS HI204e
+Magellan Nav 6500 
+BendixKing KLX 100
+Motorola i58sr Cellular Phone w/built-in NMEA-compatible GPS
+Rikaline GPS-6010 USB (needs USB to serial support in kernel, pl2303)
diff --git a/Documentation/LEEME b/Documentation/LEEME
new file mode 100644
index 0000000..725ad37
--- /dev/null
+++ b/Documentation/LEEME
@@ -0,0 +1,344 @@
+GPSDRIVE (c) 2001 Fritz Ganter <ganter@ganter.at>
+
+-------------------------------------------------
+Sitio web: www.gpsdrive.de
+Advertencia: Por favor, no lo use para navegar. 
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version. 
+    
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details. 
+    
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+    *********************************************************************
+
+======================================================================          
+
+Por favor, lee la página de manual de gpsdrive. para ello, instala el
+programa y escribe 
+
+man gpsdrive
+
+en una ventana de terminal. Con Konqueror, de KDE también puedes verlo con 
+la URL:
+man:gpsdrive
+
+ˇLa mayoría de la información está ahora en la página de manual!                                        
+
+*************************************************
+
+Cómo instalar el programa:
+----------------------
+
+Desde el código fuente:
+
+Extráelo con tar -xvzf gpsdrive*tar.gz
+
+cd gpsdrive
+./configure --with-pentiumpro
+make
+
+Como root deberías hacer 
+
+make install
+
+Después de compilar e instalar (que es necesario para la
+internacionalización) lee la página de manual de gpsdrive, o inicia el
+programa si eres demasido vago como para leérte los manuales. ;-)
+
+También puedes descargar el archivo RPM e instalarlo mediante:
+
+rpm -Uvh gpsdrive*.rpm                                                          
+
+
+Uninstall:
+---------
+Si lo instalaste usando el código fuente en tarball:
+entra en el directorio de gpsdrive (no en el src), y entonces teclea
+
+make uninstall
+
+Si usaste el paquete RPM:
+
+rpm -e gpsdrive
+
+Usuarios de Comqaq iPaq:
+------------------------
+
+Es también recomendable usar el idioma
+xx, lo cual significa iniciar GpsDrive con:
+
+LANGUAGE=xx gpsdrive                                                            
+
+*************************************************
+
+Primer Uso:
+-----------
+
+Si no existe un directorio ".gpsdrive" en tu directorio home, GpsDrive
+lo creará por ti. E neste directorio se crea un archivo map_koord.txt que
+sirve para guardar la lista de mapas.                                              
+
+
+
+Iniciando el programa:
+----------------------
+
+Hay dos formas de comunicarse con el recptor GPS: modo NMEA y modo GARMIN. 
+
+El modo NMEA es el estándar de comunicación más usado. El modo GARMIN está 
+sólo disponible en algunos receptores GARMIN.
+
+El modo GARMIN es más rápido (varios paquetes de datos por segundo, en el modo 
+NMEA 1 paquete cada 2 segundos), pero los cálculos que realiza el programa 
+quizás no sean tan precisos. Tampoco se muestra el nivel de seńal de los 
+satélites (este dato no está soportado por el protocolo GARMIN). 
+
+Si quieres usar el modo GARMIN, asegúrate de no tener "gpsd" corriendo. En
+este caso el receptor GARMIN debe ser puesto en el modo de transferencia:
+"GARMIN host".
+
+En este modo, el programa sólo, recibe datos sobre latitud/longitud, la
+velocidad y la dirección la calcula él mismo.
+
+Después de compilar e instalar (que es requerido para la
+internacionalización) inicia el programa "gpsd" (que se proporciona con
+GpsDrive), si quieres usar el modo NMEA.
+
+gpsd es un demonio que lee datos NMEA del recptor GPS. Los ajustes
+/dev/ttyS0 y 4800 Baudios está precompilados.
+
+Hay otro gpsd de Remco Treffkorn que usa el puerto 2947. si inicias este
+gpsd, será encontrado automágicamente. Si quieres cambiar estos ajustes, por
+ejemplo al segundo puerto serie, inícialo con:
+
+gpsd -serial /dev/ttyS1 
+
+Cea un directorio ".gpsdrive" en tu directorio home. En este directorio
+colocarás primero tus archivos de mapas (ver má abajo).
+
+No olvides editar el archivo "map_koord.txt" en el directorio ~/.gpsdrive.
+Esto no es necesario si usas sólo mapas que descargas de Internet con
+GpsDrive o gpsfetchmap.
+
+Puedes bajar los mapas con el programa o bien con el script  "gpsfetchmap"
+
+Una vez que gpsd está corriendo puedes iniciar el progarma con 
+
+gpsdrive
+
+Para usar el modo GARMIN no debes iniciar gpsd.
+
+Si no tienes un enlace /dev/gps apuntando al puerto serie, o usas otro
+puerto que no sea ttyS0 inicia GpsDrive con
+
+./gpsdrive  -t /dev/ttyS1 
+
+para tu segundo puerto serie.
+
+Verás tu posición en el mapa y otros datos en la barra de estado. Puedes
+ampliar y reducir. Si te mueves fuera del mapa se muestra el siguiente, si
+hay alguno disponible, para tu posición.
+
+Si no tienes receptor GPS conectado:
+------------------------------------
+
+Hay implementado un simulador. Se utiliza automáticamente si no se detecta
+un GPS.
+
+Si has creado un archivo de waypoints y tienes los mapas adecuados, puedes
+hacer click en SELECCIONAR DESTINO. El marcador se moverá a este waypoint.
+
+Soy demasiado vago para salir de la cama, żcómo puedo probar mi GARMIN GPS III?
+-------------------------------------------------------------------------------
+
+Tu receptor GARMIN tiene un simulador interno. Inícialo en la "pantalla de
+satélltes", ve a la configuración e introduce una velocidad en el menú del
+simulador.  Entonces dirígete a un waypoint almacenado y comprueba lo bien
+que funciona GpsDrive.  No te olvides dedescargar los mapas primero.
+
+Control con el ratón:
+---------------------
+
+Si haces click con el botón izquierdo en el mapa en el "Modo Display", el cursor es 
+un rectángulo y no se muestra ninguna posición. Si amplías o seleccionas otra 
+escala para los mapas funcionará como si esta fuera tu posición real.
+
+Al botón central te devuelve al modo normal. Al igual que si seleccionas un destino 
+con el botón derecho del ratón.  Mayúsculas-botón izquierdo y Mayúsculas-botón 
+derecho cambia la escala del mapa.
+
+************************************************************************
+
+Cómo obtener tus propios mapas
+------------------------------
+
+Debe hacer un fichero llamado "map_koord.txt" en tu directorio ~/.gpsdrive . 
+Aquí hay un ejemplo:
+
+map_stmk.gif          47.08    15.45    300000
+map_austria.gif       48.0     14.0    1000000
+map_bruck-m-umgeb.gif 47.44    15.29    100000
+
+La primera columna es el nombre del archivo, después vienen la latitud, la
+longitud y la escala del mapa. LA escala 10000000 (1:10.000.000) es buena
+para Europe, y 100000 es para una ciudad como Viena.
+
+Para obtener un mapa debes ir a una URL lcomo esta:
+
+http://www.mapblast.com/gif?&CT=51.0:10.0:2500000&IC=&W=1280&H=1024&FAM=mblast&LB=
+
+Esta es la latitud -------------^^^^
+Esta es la longitud -----------------^^^^
+Esta es la escala -----------------------^^^^^^^^
+
+Toma la latitud, la longitud y la escala de la URL y ponlas en el archivo
+map_koord.txt junto con el nombre del archivo.
+
+GpsDrive selecciona el mapa con la mejor escala para tu posición. Así pues
+obtén mapas para, por ejemplo, Europa, Austria y Viena si quieres conducir
+hasta Viena.
+
+Es también importante dejar el tamańo de 1280x1024 puntos como en la URL
+de arriba.
+
+Para un uso fácil, proporciono un script llamado "gpsfetchmap" para
+obtener los mapas de internet y colocar la entrada correspondiente en el
+archivo map_koord.txt.
+
+Uso: 
+
+gpsfetchmap farchivo latitud longitud escala
+
+El nombre del archivo deberá tener extensión .gif.
+
+USO SENCILLO:
+
+Puedes hacer exactamente lo mismo usando el botón "Descargar mapa" en el
+programa.
+
+ATENCIÓN: Los mapas de Mapblast.com con una escala superior a 1:2 millones
+parecen tener otro sistema de proyección, GpsDrive muestra aquí una
+posición INCORRECTA.  żAlguien tiene información sobre esto?
+
+********************************************************
+ˇPor favor lee la nota de copyright de www.mapblast.com!
+********************************************************
+
+Internacionalización
+--------------------
+
+Si instalaste el programa verás motrarse los mensajes en inglés, alemán,
+francés, italiano o espańol, si tu lenguaje está definido con LANG o
+LANGUAGE. LANGUAGE ignora el resto de ajustes. Llama a "locale" para ver
+los ajustes y llama "set" si LANG o LANGUAGE está definido. Para espańol
+pon:
+
+export LANGUAGE=es
+
+y entonces inicia gpsdrive en esa shell.
+
+Formatos de archivos:
+
+Las comas decimales en way.txt deben tener siempre un punto ('.'), en
+map_koord.txt están permitidos '.' or ','. Si descargas los mapas con el
+programa, GpsDrive escribe el archivo map_koord.txt de acuerdo al ajuste
+de LC_NUMERIC en esa consola.
+
+żPuedo usar otros mapas?
+------------------------
+
+Puedes también usar tus propios mapas (dijudos, escaneados,...). Los mapas
+deben ser gif, jpeg, png o cualquier otro formato de archivo reconocido
+por la biblioteca gdk-pixbuf library.  Las coordenadas de latitud/longitud
+que escribes en el archivo "map_koord.txt" deben correspoder al centro del
+mapa. El mapa debe tener un tamańo de 1280x1024 pixels. Debes medir y
+calcular la escala tú mismo.
+
+Es importante que uses los nombres de archivo correctos. Deben comenzar con 
+"map_" para callejeros y con "top_" para topográficos.
+
+Importando waypoints:
+---------------------
+
+Debes crear un fichero "way.txt" en tu directorio ~/.gpsdrive parecido a este:
+
+DEFAULT  47.0792  15.4524
+KLGNFR   46.6315  14.3152
+MCDONA   47.0555  15.4488
+
+El waypoint llamado "DEFAULT" es el punto de inicio del programa,
+importante si comienzas en modo simulación. Así pues no todo el mundo
+necesita empezar en mi casa en Austria ;-) También sería correcto si el
+waypoint se llama DEFAUL porque mi GARMIN GPS III alamcena sólo 6
+caracteres para un waypoint.
+
+Las columnas se llaman etiqueta latitud longitud.
+
+Si el archivo no existe o no contiene datos válidos, no habrá botón "Ir a"
+disponible.
+
+Puedes usar el programa "garble" (incluido en el paquete) para leer tus
+waypoints del GPS Garmin (el modo de transferencia debe ser GARMIN aquí).
+
+La forma más sencilla de usar el script "wpget" que lo hace todo por ti.
+
+Asegúrate de tener "wpget", "wpcvt" y "garble" en tu path.
+
+Algunos comentarios sobre las fuentes: 
+--------------------------------------
+
+GpsDrive utiliza la fuente
+
+-monotype-arial-bold-r-normal-*-*-360-*-*-p-*-iso8859-15
+
+para las letras grandes. Si esta fuente no se encuentra, utilizará 
+
+-adobe-helvetica-bold-r-normal-*-*-240-*-*-p-*-iso8859-15
+
+que debería estar disponible en una instalación normal de XFree86.
+
+Si quieres cambiar la fuente, encuentra el define "FONT1" en el código
+fuente y sustitúye el nmbre de la fuente.
+
+Salida de voz:
+-------------
+
+Si quieres disponer de salida de voz debes instalar el software
+"festival". Mira en http://fife.speech.cs.cmu.edu/festival para
+informarte. Si tienes una instalación funcional de festival llámala como
+servidor con:
+
+festival --server
+
+Si inicias entonces GpsDrive, detectará el servidor en el puerto 1314 y 
+obtendrás algunas informaciones obre el estado mediante la voz. Dispondrás de 
+un botón (Mute) para detener la salida de voz.
+
+Hay una opción -l para cambiar el idioma de la voz de salida. Por el
+momento están disponibles inglés y alemán. GpsDrive no ajusta festival en
+el idioma adecuado, así pues debes hacerlo tú mismo. si deseas otro
+idioma, por favor, envíame las traducciones de los textos en gpsdrive.c y
+speech_out.c. Mira las cadenas que comienzan por "SayText".
+
+=======================================================================
+
+ˇSe admiten sugerencias!
+
+ˇDiviértete!
+
+Fritz Ganter <ganter@gpsdrive.de>
+
+http://www.gpsdrive.de
+
+Traducido por: Félix Martos <pakito@asinkecualo.org>
+Si observas algún error en la traducción, o en la expresión comunícamelo. 
+Gracias
+
diff --git a/Documentation/LISEZMOI b/Documentation/LISEZMOI
new file mode 100644
index 0000000..7a8492a
--- /dev/null
+++ b/Documentation/LISEZMOI
@@ -0,0 +1,277 @@
+GPSDRIVE (c) 2001 Fritz Ganter <ganter@ganter.at>
+-------------------------------------------------
+
+Version francaise: Jacky Francois <jfrancois@free.fr>
+
+Site web: www.gpsdrive.de
+
+Avertissement: n'utilisez pas GpsDrive pour la navigation. 
+
+    Ce programme est un logiciel libre; vous pouvez le distribuer et/ou 
+    le modifier comme le prévoit la GNU General Public License publiée par
+    la Free Software Foundation; soit la version 2 de la licence, ou
+    (ŕ votre convenance) toute version ultérieure. 
+    
+    Ce programme est distribué dans l'espoir qu'il sera utile, mais
+    SANS GARANTIE D'AUCUNE SORTE. Consultez la GNU General Public License
+    pour de plus amples renseignements. 
+    
+    Vous pouvez trouver la GPL en version française ŕ cette adresse:
+    http://www.april.org/gnu/gpl_french.html
+    
+    *********************************************************************
+    
+    
+
+*******************************************************************
+Veuillez consulter la manpage de gpsdrive. Pour ce faire, installer
+le programme et tapez 
+
+man gpsdrive
+
+dans la fenętre d'un terminal. Vous pouvez également entrer l'url
+suivante dans Konqueror:
+
+man:gpsdrive
+
+La manpage répond dorénavant ŕ la plupart des questions que vous vous posez!
+
+Consultez également le Changelog ŕ
+http://www.gpsdrive.de/Changelog.gpsdrive
+
+******************************************************************** 
+
+
+
+
+Comment installer le programme:
+----------------------
+
+Fichier Source:
+
+Extrayez-le en tapant tar -xvzf gpsdrive*tar.gz
+cd gpsdrive
+./configure 
+make
+
+Si vous n'avez pas besoin du support du protocole GARMIN (vous n'utilisez
+que le protocole NMEA) vous pouvez configurer GpsDrive en tapant:
+
+./configure --disable-garmin
+
+Vous pouvez également ajouter --with-pentiumpro, si votre CPU > PII.
+
+
+Sous le compte root tapez 
+make install
+
+pour installer le programme, le demon gpsd et les fichiers de localisation.
+
+Aprčs la compilation et l'installation (nécessaire pour la localisation) prenez
+connaissance de la manpage de gpsdrive ou lancez le programme si vous ętes trop
+trop faignant pour lire les manuels. ;-)
+
+Vous pouvez également télécharger le RPM and l'installé:
+
+rpm -Uvh gpsdrive*.rpm
+
+Désinstallation:
+---------------
+
+Si vous avez installé avec un tarball:
+
+aller dans le répertoire de gpsdrive (pas le src) et tapez
+
+make uninstall
+
+Si vous avez utilisé le rpm:
+
+rpm -e gpsdrive
+
+
+S'il n'y a pas de répertoire ".gpsdrive" dans votre répertoire personnel,
+GpsDrive le crée pour vous. Un fichier map_koord.txt contenant la liste des
+cartes est créé dans ce répertoire. 
+
+Vous pouvez laisser le programme télécharger les cartes. Le script
+"gpsfetchmap" permet également de télécharger les cartes.
+
+
+Pour le mode GARMIN vous ne devez pas lancer gpsd.
+
+Si vous n'avez pas de lien /dev/gps pointant vers votre récepteur, oů si vous
+utilisez un autre port que ttyS0 lancez
+GpsDrive en tapant
+
+./gpsdrive  -t /dev/ttyS1 
+
+pour votre second port série.
+
+Vous pouvez changer ce parmčtre dans le menu "Paramčtres".
+
+Cliquez sur le bouton "Lancer GPSD" pour lancer le demon gpsd pour le 
+support NMEA.
+
+Votre position est indiquée sur la carte et des infos dans la barre de statut.
+Vous pouvez faire des zooms avant et arričre. Si vous sortez de la carte la
+carte suivante est sélectionnée si l'une d'elles correspond ŕ votre position.
+
+Au début vous devriez télécharger une carte avec le bouton "Télécharger".
+
+De l'aide est disponible en tapant "gpsdrive -h".
+
+Comqaq iPaq:
+-----------
+Gpsdrive détecte l'affichage réduit et utlise des menus de taille réduite.
+
+Il est également recommendé de lancer GpsDrive dans la langue xx en tapant:
+
+LANGUAGE=xx gpsdrive
+
+
+
+Si vous n'avez pas de récepteur GPS connecté:
+--------------------------------------------
+Un simulateur est incorporé. Il est automatiquement activé si aucun récepteur
+GPS n'est déctecté.
+
+Si vous avez créé un fichier de waypoints et disposez des cartes adéquates, vous
+pouvez cliquer sur "Choix destination" pour choisir un waypoint. Le pointeur va
+se déplacer jusqu'ŕ ce waypoint. Vous pouvez créer une route dans de ce menu.
+
+
+Je suis trop faignant pour sortir de mon lit, comment tester mon GARMIN GPS III?
+-------------------------------------------------------------------------------
+
+Votre GARMIN ŕ un simulateur intégré. Démarrez-le sur "l'écran satellite",
+puis allez dans les paramčtres et entrer une vitesse dans le menu simulation.
+Puis allez (goto) un waypoint en mémoire et constatez comme GpsDrive marche bien.
+N'oubliez pas de télécharger vos cartes au préalable.
+
+
+
+************************************************************************
+
+Comment obtenir ses propres cartes?
+----------------------------------
+
+METHODE FACILE:
+Vous pouvez le faire avec le bouton "Télécharger" depuis le programme.
+ 
+Voici les fichiers dont vous devez disposer.
+
+Un fichier nommé "map_koord.txt" dans votre répertoire ~/.gpsdrive.
+Voici un exemple:
+
+map_stmk.gif          47.08    15.45    300000
+map_austria.gif       48.0     14.0    1000000
+map_bruck-m-umgeb.gif 47.44    15.29    100000
+
+Dans la premičre colone se trouvent les noms des fichiers cartes, puis viennent
+la latitude, la longitude et l'échelle de la carte. 10000000 est une bonne 
+échelle pour l'Europe, et 100000 convient pour une ville comme Vienne.
+
+GpsDrive sélectionne la carte avec l'échelle la plus petite possible pour votre
+position. Procurez vous donc par exemple une carte de l'Europe, de l'Autriche
+et de Vienne si vous voulez vous rendre ŕ Vienne.
+
+
+Pour vous faciliter la tâche, j'inclus le script "gpsfetchmap" qui télécharge
+une carte sur Interner et modifie en conséquence le fichier map_koord.txt.
+Utilisation: 
+
+gpsfetchmap nom_de_la_carte latitude longitude échelle
+
+Le nom de la carte doit avoir l'extension .gif.
+
+ATTENTION: Les cartes de Mapblast.com dont l'échelle est supérieure ŕ
+1:2 000 000 semblent utiliser un autre systčme de projection, GpsDrive affiche
+dans ce cas une position INCORRECTE.Quelqu'un a-t-il plus d'informations?
+
+***********************************************************
+Veuillez consulter les droits d'auteur de www.mapblast.com!
+***********************************************************
+
+Formats de fichier:
+
+le séparateur décimal dans way.txt doit toujours ętre un point ('.'), dans
+map_koord.txt '.' or ',' sont possibles. Si vous téléchargez des cartes depuis
+le programme, GpsDrive écrit dans map_koord.txt en respectant votre paramčtre
+LC_NUMERIC
+
+Puis-je utiliser d'autres cartes?
+--------------------------------
+
+Vous pouvez également utiliser vos propres cartes ( dessinées, scannées... )
+Les cartes doivent toujours ętre au format gif, jpeg, png ou tout autre format
+pourvu qu'il soit reconnu par la librairie gdk-pixbuf. Les coordonnées,
+latitude et longitude, que vous entrez dans le fichier "map_koord.txt" doivent
+ętre celles du centre de la carte. La carte doit ętre au format 1280x1024!
+
+Important! Les cartes doivent dorénavant avoir pour nom map_* pour les plans de
+ville et top_* pour les cartes topographiques. Si ca n'est pas le cas gpsdrive
+n'affichera pas les cartes.
+
+Un "assistant d'importation" est intégré. Utilisez-le pour importer vos cartes.
+
+Importer des waypoints:
+----------------------
+
+La méthode la plus simple est d'utiliser le script "wpget" qui s'occupe de
+tout si vous utilisez un recepteur GARMIN.
+Vous pouvez utiliser le programme "garble" (inclu dans le package) pour
+extraire vos waypoints du GPS Garmin (Le mode transfer doit ętre GARMIN dans
+ca cas, alors que GpsDrive utlise le mode NMEA!).
+
+"wpget" est un script qui fait appel ŕ "garble" de maničre adéquate.
+
+Assurez vous d'avoir "wpget", "wpcvt" et "garble" dans votre path. C'est le
+cas, si vous avez installé le programme sous le compte root et si
+/usr/local/bin est dans votre path.
+
+Méthode manuelle:
+
+Vous pouvez créer un fichier "way.txt" dans votre répertoire ~/.gpsdrive dont
+le contenu est le suivant:
+
+DEFAULT  47.0792  15.4524
+KLGNFR   46.6315  14.3152
+MCDONA   47.0555  15.4488
+
+
+Les colonnes sont: label latitude longitude.
+
+Vous n'avez pas besoin de créer way.txt vous-męmes, vous pouvez ajouter les
+waypoints dans GpsDrive avec la touche "x". Consulter également le menu d'aide.
+
+Commentaires sur les polices:
+----------------------------
+
+GpsDrive utilise la police 
+"-monotype-arial-bold-r-normal-*-*-360-*-*-p-*-iso8859-15"
+pour les gros caractčres. Si cette police n'est pas trouvée, il utilise  
+"-adobe-helvetica-bold-r-normal-*-*-240-*-*-p-*-iso8859-15"
+qui est fournie avec XFree86.
+
+Si vous voulez changer de police, rechercher "FONT1" dans le code source et
+modifiez-le en conséquence.
+
+
+Liste de diffusion:
+
+L'adresse de la liste de diffusion est gpsdrive@warbase.selwerd.nl
+
+L'inscription se fait en envoyant un email contenant "subscribe gpsdrive" ŕ
+majordomo@warbase.selwerd.nl
+
+
+=======================================================================
+
+Vos suggestions et raports de bug sont les bienvenus!
+
+
+Amusez-vous bien!
+
+Fritz Ganter <ganter@gpsdrive.de>
+http://www.gpsdrive.de
+
diff --git a/Documentation/LISEZMOI.FreeBSD b/Documentation/LISEZMOI.FreeBSD
new file mode 100644
index 0000000..75b4b6a
--- /dev/null
+++ b/Documentation/LISEZMOI.FreeBSD
@@ -0,0 +1,41 @@
+$Id: LISEZMOI.FreeBSD 2 1994-06-07 08:35:10Z tweety $
+Traduit en français par Jacky François <jfrancois@free.fr>
+
+                    INSTALLER GPSDRIVE SOUS FREEBSD
+
+
+La méthode la plus simple pour installer GpsDrive sous FreeBSD est d'utiliser
+le systčme de port de FreeBSD: rendez vous ŕ l'adresse:
+http://www.freebsd.org/astro.html et sélectionnez 'gpsdrive'.
+
+
+Pour installer un package binaire vous pouvez utiliser la fonction de téléchargement
+automatique de pkg_add:
+
+$ su -             [devenez root]
+# pkg_add -r gpsdrive
+# exit             [redevenez simple utilisateur]
+
+
+Pour une installation ŕ partir des sources assurez-vous d'avoir vos ports ŕ jour [1]
+et procédez comme ceci:
+
+$ su -             [devenez root]
+# cd /usr/ports/astro/gpsdrive
+# make
+# make install
+# make clean
+# exit             [redevenez simple utilisateur]
+
+
+Amusez-vous bien!
+
+N'hésitez pas ŕ me contacter si vous avez des questions ŕ propos du port sous FreeBSD
+ou si vous désirez une version plus récente.
+
+Marco Molteni <molter@gufi.org>
+http://www.gufi.org/~molter/
+
+[1] http://www.freebsd.org/handbook/ports-using.html. Pour mettre ŕ jour votre base
+    de ports utilisez CVSup comme indiqué sur ce site.
+    NdT: le handbook en français: http://www.freebsd-fr.org/doc/fr_FR.ISO8859-1/books/handbook
+\ No newline at end of file
diff --git a/Documentation/LISEZMOI.SQL b/Documentation/LISEZMOI.SQL
new file mode 100644
index 0000000..4f240c0
--- /dev/null
+++ b/Documentation/LISEZMOI.SQL
@@ -0,0 +1,112 @@
+Version pour gpsdrive-1.31
+Traduit en français par Jacky FRANCOIS <jfrancois@free.fr>
+
+Depuis la version 1.29 GpsDrive supporte les bases de données SQL.
+
+Bases de données supportées (October 2002): MySQL
+
+Compiler:
+---------
+Le suport pour MySQL ne peut compiler que si vous avez installer
+le package de dévelopement mysql-client et ne eut ętre utilisé
+que si libmysqlclient.so est présent.
+
+Si vous ne voulez pas compiler le support de MySQL, męme si les
+librairies et les headers sont installés, utilisez l'option 
+"--disable-mysql" au moment du configure.
+
+Exécution et initialisation:
+----------------------------
+Si ce n'est déjŕ fait, installez le package du serveur mysql pour
+votre distribution.
+
+o Démarrez le serveur, habituellement en tapant: /etc/init.d/mysql start
+
+o Pour créer une base de données initiale utilisez le fichier "geoinfo.pl" 
+  fourni. Assurez-vous que l'utilisateur choisi dispose des droits nécessaires
+  pour créer cette table.
+
+  geoinfo.pl  --create-db --fill-defaults --openstreetmap \
+              --db-user=root --db-password=<our mysql root password>
+  (ajoutez un nom d'utilisateur si besoin est)
+
+  Vous pouvez remplacer gast@localhost par gast@'%' si vous voulez utiliser
+  la base de données avec d'autres noms d'hôtes.
+
+
+Mise ŕ jour:
+------------
+Si vous avez déjŕ la base de données et que vous mettez GpsDrive ŕ jour,
+assurez-vous que la structure de votre table est bien comme celle du fichier
+create.sql (old). Now use 
+geoinfo.pl
+
+Gestion du serveur SQL:
+-----------------------
+
+mysqlcc est un bon outil, téléchargez-le ŕ cette adresse:
+
+http://www.mysql.com/downloads/gui-mycc.html
+
+Sécurité:
+---------
+GpsDrive accčde par défaut ŕ la table "waypoints" dans la base de données
+"geoinfo" avec le nom d'utilisateur "gast" dont le mot de passe est "gast". 
+Si vous voulez changer ces paramčtres dans la base de données, effectuez
+également la modification dans GpsDrive. Pour celŕ, éditez le fichier
+$HOME/.gpsdrive/gpsdriverc (dbuser,dbpass).
+
+Gardez ŕ l'esprit que le mot de passe pour cette base figure en clair dans
+gpsdriverc!!!
+
+
+Importer des fichiers de aypoints existants:
+--------------------------------------------
+Le script "wp2sql" permet de créer le fichier .sql ŕ partir des fichiers
+de waypoints de GpsDrive.
+
+Adaptez-le ŕ vos besoins!!!!
+
+Tapez ensuite:
+
+mysql -u gast -pgast <wp.sql
+
+Vous pouvez également importe des fichies ASCII avec "mysqlimport".
+
+=================================================================================
+IMPORTANT:
+
+Activez l'option 'Utiliser SQL' (dans le GUI) pour utiliser les waypoints de SQL.
+
+=================================================================================
+
+Catégories de waypoint:
+-----------------------
+
+Vous pouvez nommer vos catégories de waypoint comme vous l'entendez. Il existe
+cependant des catégories prédéfinies, auxquelles sont associés des icones dans
+GpsDrive.
+
+WLAN	     : point d'accčs WLAN ouvert
+WLAN-WEP     : point d'éccčs WLAN crypté
+Rest	     : un restaurant
+McDonalds    : un fast-food
+BurgerKing   : un autre fast-food
+Hotel	     : un hotel
+Shop	     : magasin
+Monu	     : Monument, attraction touristique
+Speedtrap    : Radar de contôle de vitesse, vous avertis quand vous allez passer 
+               devant lui
+Nightclub    : Pssst...
+Airport	     : Aéroport
+Golf	     : Cours de golf
+Gasstation   : Station essence
+Cafe	     : Café
+
+Les noms ne sont pas sensibles ŕ la casse.
+
+Sauvergarder et restaurer votre base de donnée
+----------------------------------------------
+
+Sven a conçu gpssql_backup.sh et gpssql_restore.sh. Ces deux scripts sont simples
+d'utilisation. Consultez simplement les commentaires dans ces scripts.
diff --git a/Documentation/LISEZMOI.kismet b/Documentation/LISEZMOI.kismet
new file mode 100644
index 0000000..e4972ab
--- /dev/null
+++ b/Documentation/LISEZMOI.kismet
@@ -0,0 +1,50 @@
+
+Traduit en francçais par Jacky FRANCOIS <jfrancois@free.fr>
+
+Attention!!!!
+
+Gpsdrive, ŕ partir de la version 1.31, n'est compatible qu'avec
+les versions >=2.8.0 de kismet car le format du serveur a changé.
+Les versions antérieures de GpsDrive ne fonctionnent qu'avec
+kismet 2.6.x
+=================================================================
+
+
+GpsDrive est compatible avec le sniffer wireless 'kismet'.
+
+Kismet est un sniffer de réseau wireless 802.11b. Il est compatible
+avec la plupart des cartes wireless supportées par Linux, en particulier
+les cartes basées sur Prism2 supportées par le projet Wlan-NG
+(Linksys, Dlink, Rangelan, etc) ainsi que les cartes compatibles avec la
+libpcap (Cisco). Certaines autres cartes sans RF Monitor sont également
+partiellement gérées.
+
+Plus d'info sur le site de kismet: http://www.kismetwireless.net
+
+Comment utiliser GpsDrive avec kismet?
+--------------------------------------
+
+Vous devez démarrer kismet en premier (gpsd doit tourner avant kismet,
+pour que ce dernier puisse détecter la présence du récepteur GPS ).
+Lorsque kismet tourne vous pouvez lancer GpsDrive. Si l'interface vocale
+est activée une annonce orale vous informe que kismet a été trouvé.
+
+Kismet ne communique avec GpsDrive que si celui-ci intčgre les fonctions 
+SQL et que l'option "utiliser SQL" est activée.
+
+Qu'apporte kismet ŕ GpsDrive?
+-----------------------------
+
+Lorsque kismet détecte un point d'accčs wireless, il l'inscrit dans la
+base SQL et un icone symbolise son emplacement ( un cadenas fermé si le
+point d'accčs est crypté par WEP, un cadenas ouvert dans le cas contraire).
+Il faut que cette catégorie de waypoint soit activée dans le menu
+paramčtres/SQL.
+
+Si l'interface vocale est activée vous entendrez une annonce indiquant 
+qu'un nouveau waypoint a été trouvé.
+
+GpsDrive n'enregistre que les nouveaux points d'accčs pour empecher qu'un
+męme point d'accčs ne soit inscrit de multiples fois dans la base de donnée.
+La vérification se fait en se basant sur l'adresse MAC dans la base de donnée,
+si celle-ci y figure déjŕ le point d'accčs est ignoré.
+\ No newline at end of file
diff --git a/Documentation/Makefile.am b/Documentation/Makefile.am
new file mode 100644
index 0000000..316abe2
--- /dev/null
+++ b/Documentation/Makefile.am
@@ -0,0 +1,26 @@
+# Makefile.am for Documentation
+
+documentationdir   = $(datadir)/gpsdrive/Documentation
+documentation_DATA = \
+	CREDITS \
+	FAQ.gpsdrive FAQ.gpsdrive.fr \
+	GPS-receivers \
+	LEEME \
+	LISEZMOI.FreeBSD\
+	LISEZMOI.SQL \
+	LISEZMOI.kismet \
+	LISEZMOI \
+	NMEA.txt \
+	README.Bluetooth \
+	README.Fedora \
+	README.FreeBSD \
+	README.OpenStreetMap-Vektordata \
+	README.SQL README.mysql \
+	README.gpspoint2gspdrive \
+	README.kismet \
+	README.lib_map \
+	README.nasamaps \
+	TODO
+
+
+EXTRA_DIST= $(documentation_DATA)
diff --git a/Documentation/Makefile.in b/Documentation/Makefile.in
new file mode 100644
index 0000000..56632bb
--- /dev/null
+++ b/Documentation/Makefile.in
@@ -0,0 +1,433 @@
+# Makefile.in generated by automake 1.9.6 from Makefile.am.
+# @configure_input@
+
+# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
+# 2003, 2004, 2005  Free Software Foundation, Inc.
+# This Makefile.in is free software; the Free Software Foundation
+# gives unlimited permission to copy and/or distribute it,
+# with or without modifications, as long as this notice is preserved.
+
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
+# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+# PARTICULAR PURPOSE.
+
+@SET_MAKE@
+
+# Makefile.am for Documentation
+
+srcdir = @srcdir@
+top_srcdir = @top_srcdir@
+VPATH = @srcdir@
+pkglibdir = $(libdir)/@PACKAGE@
+pkgincludedir = $(includedir)/@PACKAGE@
+top_builddir = ..
+am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
+INSTALL = @INSTALL@
+install_sh_DATA = $(install_sh) -c -m 644
+install_sh_PROGRAM = $(install_sh) -c
+install_sh_SCRIPT = $(install_sh) -c
+INSTALL_HEADER = $(INSTALL_DATA)
+transform = $(program_transform_name)
+NORMAL_INSTALL = :
+PRE_INSTALL = :
+POST_INSTALL = :
+NORMAL_UNINSTALL = :
+PRE_UNINSTALL = :
+POST_UNINSTALL = :
+build_triplet = @build@
+host_triplet = @host@
+subdir = Documentation
+DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in TODO
+ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
+am__aclocal_m4_deps = $(top_srcdir)/m4/ac_check_perl_modules.m4 \
+	$(top_srcdir)/m4/ac_check_socketlen_t.m4 \
+	$(top_srcdir)/m4/aq_check_gdal.m4 $(top_srcdir)/m4/gettext.m4 \
+	$(top_srcdir)/m4/iconv.m4 $(top_srcdir)/m4/lib-ld.m4 \
+	$(top_srcdir)/m4/lib-link.m4 $(top_srcdir)/m4/lib-prefix.m4 \
+	$(top_srcdir)/m4/nls.m4 $(top_srcdir)/m4/po.m4 \
+	$(top_srcdir)/m4/progtest.m4 $(top_srcdir)/configure.ac
+am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
+	$(ACLOCAL_M4)
+mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
+CONFIG_HEADER = $(top_builddir)/config.h
+CONFIG_CLEAN_FILES =
+SOURCES =
+DIST_SOURCES =
+am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`;
+am__vpath_adj = case $$p in \
+    $(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \
+    *) f=$$p;; \
+  esac;
+am__strip_dir = `echo $$p | sed -e 's|^.*/||'`;
+am__installdirs = "$(DESTDIR)$(documentationdir)"
+documentationDATA_INSTALL = $(INSTALL_DATA)
+DATA = $(documentation_DATA)
+DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
+pkgdatadir = @pkgdatadir@
+ACLOCAL = @ACLOCAL@
+AMAPNIK = @AMAPNIK@
+AMDEP_FALSE = @AMDEP_FALSE@
+AMDEP_TRUE = @AMDEP_TRUE@
+AMTAR = @AMTAR@
+AR = @AR@
+AUTOCONF = @AUTOCONF@
+AUTOHEADER = @AUTOHEADER@
+AUTOMAKE = @AUTOMAKE@
+AWK = @AWK@
+CC = @CC@
+CCDEPMODE = @CCDEPMODE@
+CFLAGS = @CFLAGS@
+CPP = @CPP@
+CPPFLAGS = @CPPFLAGS@
+CXX = @CXX@
+CXXCPP = @CXXCPP@
+CXXDEPMODE = @CXXDEPMODE@
+CXXFLAGS = @CXXFLAGS@
+CYGPATH_W = @CYGPATH_W@
+DBUS_CFLAGS = @DBUS_CFLAGS@
+DBUS_GLIB_LIBS = @DBUS_GLIB_LIBS@
+DBUS_LIBS = @DBUS_LIBS@
+DEFS = @DEFS@
+DEPDIR = @DEPDIR@
+DISABLEGARMIN_FALSE = @DISABLEGARMIN_FALSE@
+DISABLEGARMIN_TRUE = @DISABLEGARMIN_TRUE@
+DISABLEPLUGINS_FALSE = @DISABLEPLUGINS_FALSE@
+DISABLEPLUGINS_TRUE = @DISABLEPLUGINS_TRUE@
+ECHO = @ECHO@
+ECHO_C = @ECHO_C@
+ECHO_N = @ECHO_N@
+ECHO_T = @ECHO_T@
+EGREP = @EGREP@
+EXEEXT = @EXEEXT@
+F77 = @F77@
+FFLAGS = @FFLAGS@
+FRIENDSSERVERVERSION = @FRIENDSSERVERVERSION@
+GDAL_CFLAGS = @GDAL_CFLAGS@
+GDAL_CONFIG = @GDAL_CONFIG@
+GDAL_LDADD = @GDAL_LDADD@
+GETTEXT_PACKAGE = @GETTEXT_PACKAGE@
+GLIB_CFLAGS = @GLIB_CFLAGS@
+GLIB_GENMARSHAL = @GLIB_GENMARSHAL@
+GLIB_LIBS = @GLIB_LIBS@
+GLIB_MKENUMS = @GLIB_MKENUMS@
+GMSGFMT = @GMSGFMT@
+GMSGFMT_015 = @GMSGFMT_015@
+GOBJECT_QUERY = @GOBJECT_QUERY@
+GREP = @GREP@
+GTK_CFLAGS = @GTK_CFLAGS@
+GTK_LIBS = @GTK_LIBS@
+HAVE_DBUS_FALSE = @HAVE_DBUS_FALSE@
+HAVE_DBUS_TRUE = @HAVE_DBUS_TRUE@
+HAVE_GDAL_FALSE = @HAVE_GDAL_FALSE@
+HAVE_GDAL_TRUE = @HAVE_GDAL_TRUE@
+HAVE_GTK_FALSE = @HAVE_GTK_FALSE@
+HAVE_GTK_TRUE = @HAVE_GTK_TRUE@
+INSTALL_DATA = @INSTALL_DATA@
+INSTALL_PROGRAM = @INSTALL_PROGRAM@
+INSTALL_SCRIPT = @INSTALL_SCRIPT@
+INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
+INTLLIBS = @INTLLIBS@
+INTL_MACOSX_LIBS = @INTL_MACOSX_LIBS@
+LDFLAGS = @LDFLAGS@
+LIBADD_DL = @LIBADD_DL@
+LIBICONV = @LIBICONV@
+LIBINTL = @LIBINTL@
+LIBOBJS = @LIBOBJS@
+LIBS = @LIBS@
+LIBTOOL = @LIBTOOL@
+LN_S = @LN_S@
+LTLIBICONV = @LTLIBICONV@
+LTLIBINTL = @LTLIBINTL@
+LTLIBOBJS = @LTLIBOBJS@
+MAKEINFO = @MAKEINFO@
+MSGFMT = @MSGFMT@
+MSGFMT_015 = @MSGFMT_015@
+MSGMERGE = @MSGMERGE@
+NOGARMIN = @NOGARMIN@
+NOPLUGINS = @NOPLUGINS@
+OBJEXT = @OBJEXT@
+PACKAGE = @PACKAGE@
+PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
+PACKAGE_NAME = @PACKAGE_NAME@
+PACKAGE_STRING = @PACKAGE_STRING@
+PACKAGE_TARNAME = @PACKAGE_TARNAME@
+PACKAGE_VERSION = @PACKAGE_VERSION@
+PATH_SEPARATOR = @PATH_SEPARATOR@
+PCRE_CONFIG = @PCRE_CONFIG@
+PERL = @PERL@
+PERL_PACKAGE_DIR = @PERL_PACKAGE_DIR@
+PKGCONFIG_CFLAGS = @PKGCONFIG_CFLAGS@
+PKGCONFIG_LIBS = @PKGCONFIG_LIBS@
+PKG_CONFIG = @PKG_CONFIG@
+POSUB = @POSUB@
+POW_LIB = @POW_LIB@
+RANLIB = @RANLIB@
+SED = @SED@
+SET_MAKE = @SET_MAKE@
+SHELL = @SHELL@
+STRIP = @STRIP@
+USE_NLS = @USE_NLS@
+VERSION = @VERSION@
+WITH_MAPNIK_FALSE = @WITH_MAPNIK_FALSE@
+WITH_MAPNIK_TRUE = @WITH_MAPNIK_TRUE@
+XGETTEXT = @XGETTEXT@
+XGETTEXT_015 = @XGETTEXT_015@
+XML_CFLAGS = @XML_CFLAGS@
+XML_LIBS = @XML_LIBS@
+YACC = @YACC@
+YFLAGS = @YFLAGS@
+ac_ct_CC = @ac_ct_CC@
+ac_ct_CXX = @ac_ct_CXX@
+ac_ct_F77 = @ac_ct_F77@
+am__fastdepCC_FALSE = @am__fastdepCC_FALSE@
+am__fastdepCC_TRUE = @am__fastdepCC_TRUE@
+am__fastdepCXX_FALSE = @am__fastdepCXX_FALSE@
+am__fastdepCXX_TRUE = @am__fastdepCXX_TRUE@
+am__include = @am__include@
+am__leading_dot = @am__leading_dot@
+am__quote = @am__quote@
+am__tar = @am__tar@
+am__untar = @am__untar@
+bindir = @bindir@
+build = @build@
+build_alias = @build_alias@
+build_cpu = @build_cpu@
+build_os = @build_os@
+build_vendor = @build_vendor@
+datadir = @datadir@
+datarootdir = @datarootdir@
+docdir = @docdir@
+dvidir = @dvidir@
+exec_prefix = @exec_prefix@
+host = @host@
+host_alias = @host_alias@
+host_cpu = @host_cpu@
+host_os = @host_os@
+host_vendor = @host_vendor@
+htmldir = @htmldir@
+includedir = @includedir@
+infodir = @infodir@
+install_sh = @install_sh@
+libdir = @libdir@
+libexecdir = @libexecdir@
+localedir = @localedir@
+localstatedir = @localstatedir@
+mandir = @mandir@
+mkdir_p = @mkdir_p@
+oldincludedir = @oldincludedir@
+pdfdir = @pdfdir@
+prefix = @prefix@
+program_transform_name = @program_transform_name@
+psdir = @psdir@
+sbindir = @sbindir@
+sharedstatedir = @sharedstatedir@
+sysconfdir = @sysconfdir@
+target_alias = @target_alias@
+documentationdir = $(datadir)/gpsdrive/Documentation
+documentation_DATA = \
+	CREDITS \
+	FAQ.gpsdrive FAQ.gpsdrive.fr \
+	GPS-receivers \
+	LEEME \
+	LISEZMOI.FreeBSD\
+	LISEZMOI.SQL \
+	LISEZMOI.kismet \
+	LISEZMOI \
+	NMEA.txt \
+	README.Bluetooth \
+	README.Fedora \
+	README.FreeBSD \
+	README.OpenStreetMap-Vektordata \
+	README.SQL README.mysql \
+	README.gpspoint2gspdrive \
+	README.kismet \
+	README.lib_map \
+	README.nasamaps \
+	TODO
+
+EXTRA_DIST = $(documentation_DATA)
+all: all-am
+
+.SUFFIXES:
+$(srcdir)/Makefile.in:  $(srcdir)/Makefile.am  $(am__configure_deps)
+	@for dep in $?; do \
+	  case '$(am__configure_deps)' in \
+	    *$$dep*) \
+	      cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
+		&& exit 0; \
+	      exit 1;; \
+	  esac; \
+	done; \
+	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  Documentation/Makefile'; \
+	cd $(top_srcdir) && \
+	  $(AUTOMAKE) --gnu  Documentation/Makefile
+.PRECIOUS: Makefile
+Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
+	@case '$?' in \
+	  *config.status*) \
+	    cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
+	  *) \
+	    echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
+	    cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
+	esac;
+
+$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+
+$(top_srcdir)/configure:  $(am__configure_deps)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+$(ACLOCAL_M4):  $(am__aclocal_m4_deps)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+
+mostlyclean-libtool:
+	-rm -f *.lo
+
+clean-libtool:
+	-rm -rf .libs _libs
+
+distclean-libtool:
+	-rm -f libtool
+uninstall-info-am:
+install-documentationDATA: $(documentation_DATA)
+	@$(NORMAL_INSTALL)
+	test -z "$(documentationdir)" || $(mkdir_p) "$(DESTDIR)$(documentationdir)"
+	@list='$(documentation_DATA)'; for p in $$list; do \
+	  if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
+	  f=$(am__strip_dir) \
+	  echo " $(documentationDATA_INSTALL) '$$d$$p' '$(DESTDIR)$(documentationdir)/$$f'"; \
+	  $(documentationDATA_INSTALL) "$$d$$p" "$(DESTDIR)$(documentationdir)/$$f"; \
+	done
+
+uninstall-documentationDATA:
+	@$(NORMAL_UNINSTALL)
+	@list='$(documentation_DATA)'; for p in $$list; do \
+	  f=$(am__strip_dir) \
+	  echo " rm -f '$(DESTDIR)$(documentationdir)/$$f'"; \
+	  rm -f "$(DESTDIR)$(documentationdir)/$$f"; \
+	done
+tags: TAGS
+TAGS:
+
+ctags: CTAGS
+CTAGS:
+
+
+distdir: $(DISTFILES)
+	@srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`; \
+	topsrcdirstrip=`echo "$(top_srcdir)" | sed 's|.|.|g'`; \
+	list='$(DISTFILES)'; for file in $$list; do \
+	  case $$file in \
+	    $(srcdir)/*) file=`echo "$$file" | sed "s|^$$srcdirstrip/||"`;; \
+	    $(top_srcdir)/*) file=`echo "$$file" | sed "s|^$$topsrcdirstrip/|$(top_builddir)/|"`;; \
+	  esac; \
+	  if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
+	  dir=`echo "$$file" | sed -e 's,/[^/]*$$,,'`; \
+	  if test "$$dir" != "$$file" && test "$$dir" != "."; then \
+	    dir="/$$dir"; \
+	    $(mkdir_p) "$(distdir)$$dir"; \
+	  else \
+	    dir=''; \
+	  fi; \
+	  if test -d $$d/$$file; then \
+	    if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
+	      cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
+	    fi; \
+	    cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
+	  else \
+	    test -f $(distdir)/$$file \
+	    || cp -p $$d/$$file $(distdir)/$$file \
+	    || exit 1; \
+	  fi; \
+	done
+check-am: all-am
+check: check-am
+all-am: Makefile $(DATA)
+installdirs:
+	for dir in "$(DESTDIR)$(documentationdir)"; do \
+	  test -z "$$dir" || $(mkdir_p) "$$dir"; \
+	done
+install: install-am
+install-exec: install-exec-am
+install-data: install-data-am
+uninstall: uninstall-am
+
+install-am: all-am
+	@$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
+
+installcheck: installcheck-am
+install-strip:
+	$(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
+	  install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
+	  `test -z '$(STRIP)' || \
+	    echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
+mostlyclean-generic:
+
+clean-generic:
+
+distclean-generic:
+	-test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
+
+maintainer-clean-generic:
+	@echo "This command is intended for maintainers to use"
+	@echo "it deletes files that may require special tools to rebuild."
+clean: clean-am
+
+clean-am: clean-generic clean-libtool mostlyclean-am
+
+distclean: distclean-am
+	-rm -f Makefile
+distclean-am: clean-am distclean-generic distclean-libtool
+
+dvi: dvi-am
+
+dvi-am:
+
+html: html-am
+
+info: info-am
+
+info-am:
+
+install-data-am: install-documentationDATA
+
+install-exec-am:
+
+install-info: install-info-am
+
+install-man:
+
+installcheck-am:
+
+maintainer-clean: maintainer-clean-am
+	-rm -f Makefile
+maintainer-clean-am: distclean-am maintainer-clean-generic
+
+mostlyclean: mostlyclean-am
+
+mostlyclean-am: mostlyclean-generic mostlyclean-libtool
+
+pdf: pdf-am
+
+pdf-am:
+
+ps: ps-am
+
+ps-am:
+
+uninstall-am: uninstall-documentationDATA uninstall-info-am
+
+.PHONY: all all-am check check-am clean clean-generic clean-libtool \
+	distclean distclean-generic distclean-libtool distdir dvi \
+	dvi-am html html-am info info-am install install-am \
+	install-data install-data-am install-documentationDATA \
+	install-exec install-exec-am install-info install-info-am \
+	install-man install-strip installcheck installcheck-am \
+	installdirs maintainer-clean maintainer-clean-generic \
+	mostlyclean mostlyclean-generic mostlyclean-libtool pdf pdf-am \
+	ps ps-am uninstall uninstall-am uninstall-documentationDATA \
+	uninstall-info-am
+
+# Tell versions [3.59,3.63) of GNU make to not export all variables.
+# Otherwise a system limit (for SysV at least) may be exceeded.
+.NOEXPORT:
diff --git a/Documentation/NMEA.txt b/Documentation/NMEA.txt
new file mode 100644
index 0000000..40de51a
--- /dev/null
+++ b/Documentation/NMEA.txt
@@ -0,0 +1,1014 @@
+ AAM - Waypoint Arrival Alarm
+
+        1 2 3   4 5    6
+        | | |   | |    |
+ $--AAM,A,A,x.x,N,c--c*hh<CR><LF>
+
+ Field Number: 
+ 1) Status, BOOLEAN, A = Arrival circle entered
+ 2) Status, BOOLEAN, A = perpendicular passed at waypoint
+ 3) Arrival circle radius
+ 4) Units of radius, nautical miles
+ 5) Waypoint ID
+ 6) Checksum
+
+ ALM - GPS Almanac Data
+
+        1   2   3  4   5  6    7  8    9    10     11     12     13     14  15   16
+        |   |   |  |   |  |    |  |    |    |      |      |      |      |   |    |
+ $--ALM,x.x,x.x,xx,x.x,hh,hhhh,hh,hhhh,hhhh,hhhhhh,hhhhhh,hhhhhh,hhhhhh,hhh,hhh,*hh<CR><LF>
+
+ Field Number: 
+  1) Total number of messages
+  2) Message Number
+  3) Satellite PRN number (01 to 32)
+  4) GPS Week Number :
+	Date and time in GPS is computed as number of weeks from 6 January 1980 plus
+     	number of seconds into the week.
+  5) SV health, bits 17-24 of each almanac page
+  6) Eccentricity
+  7) Almanac Reference Time
+  8) Inclination Angle
+  9) Rate of Right Ascension
+ 10) Root of semi-major axis
+ 11) Argument of perigee
+ 12) Longitude of ascension node
+ 13) Mean anomaly
+ 14) F0 Clock Parameter
+ 15) F1 Clock Parameter
+ 16) Checksum
+
+ APA - Autopilot Sentence "A"
+
+        1 2  3   4 5 6 7  8  9 10    11
+        | |  |   | | | |  |  | |     |
+ $--APA,A,A,x.xx,L,N,A,A,xxx,M,c---c*hh<CR><LF>
+
+ Field Number: 
+  1) Status
+     V = LORAN-C Blink or SNR warning
+     V = general warning flag or other navigation systems when a reliable
+         fix is not available
+  2) Status
+     V = Loran-C Cycle Lock warning flag
+     A = OK or not used
+
+  3) Cross Track Error Magnitude
+  4) Direction to steer, L or R
+  5) Cross Track Units (Nautic miles or kilometers)
+  6) Status
+     A = Arrival Circle Entered
+  7) Status
+     A = Perpendicular passed at waypoint
+  8) Bearing origin to destination
+  9) M = Magnetic, T = True
+ 10) Destination Waypoint ID
+ 11) checksum
+
+ APB - Autopilot Sentence "B"
+                                         13    15
+        1 2 3   4 5 6 7 8   9 10   11  12|   14|
+        | | |   | | | | |   | |    |   | |   | |
+ $--APB,A,A,x.x,a,N,A,A,x.x,a,c--c,x.x,a,x.x,a*hh<CR><LF>
+
+ Field Number: 
+  1) Status
+     V = LORAN-C Blink or SNR warning
+     V = general warning flag or other navigation systems when a reliable
+         fix is not available
+  2) Status
+     V = Loran-C Cycle Lock warning flag
+     A = OK or not used
+  3) Cross Track Error Magnitude
+  4) Direction to steer, L or R
+  5) Cross Track Units, N = Nautical Miles
+  6) Status
+     A = Arrival Circle Entered
+  7) Status
+     A = Perpendicular passed at waypoint
+  8) Bearing origin to destination
+  9) M = Magnetic, T = True
+ 10) Destination Waypoint ID
+ 11) Bearing, present position to Destination
+ 12) M = Magnetic, T = True
+ 13) Heading to steer to destination waypoint
+ 14) M = Magnetic, T = True
+ 15) Checksum
+
+ ASD - Autopilot System Data
+ FORMAT UNKOWN
+
+ BEC - Bearing & Distance to Waypoint - Dead Reckoning
+                                                         12
+        1         2       3 4        5 6   7 8   9 10  11|    13
+        |         |       | |        | |   | |   | |   | |    |
+ $--BEC,hhmmss.ss,llll.ll,a,yyyyy.yy,a,x.x,T,x.x,M,x.x,N,c--c*hh<CR><LF>
+
+ Field Number: 
+  1) UTCTime
+  2) Waypoint Latitude
+  3) N = North, S = South
+  4) Waypoint Longitude
+  5) E = East, W = West
+  6) Bearing, True
+  7) T = True
+  8) Bearing, Magnetic
+  9) M = Magnetic
+ 10) Nautical Miles
+ 11) N = Nautical Miles
+ 12) Waypoint ID
+ 13) Checksum
+
+
+ BOD - Bearing - Waypoint to Waypoint
+
+        1   2 3   4 5    6    7
+        |   | |   | |    |    |
+ $--BOD,x.x,T,x.x,M,c--c,c--c*hh<CR><LF>
+
+ Field Number: 
+  1) Bearing Degrees, TRUE
+  2) T = True
+  3) Bearing Degrees, Magnetic
+  4) M = Magnetic
+  5) TO Waypoint
+  6) FROM Waypoint
+  7) Checksum
+
+ BWC - Bearing and Distance to Waypoint
+ Latitude, N/S, Longitude, E/W, UTC, Status
+                                                       11
+        1         2       3 4        5 6   7 8   9 10  | 12   13
+        |         |       | |        | |   | |   | |   | |    |
+ $--BWC,hhmmss.ss,llll.ll,a,yyyyy.yy,a,x.x,T,x.x,M,x.x,N,c--c*hh<CR><LF>
+
+ Field Number: 
+  1) UTCTime
+  2) Waypoint Latitude
+  3) N = North, S = South
+  4) Waypoint Longitude
+  5) E = East, W = West
+  6) Bearing, True
+  7) T = True
+  8) Bearing, Magnetic
+  9) M = Magnetic
+ 10) Nautical Miles
+ 11) N = Nautical Miles
+ 12) Waypoint ID
+ 13) Checksum
+
+ BWR - Bearing and Distance to Waypoint - Rhumb Line
+ Latitude, N/S, Longitude, E/W, UTC, Status
+                                                       11
+        1         2       3 4        5 6   7 8   9 10  | 12   13
+        |         |       | |        | |   | |   | |   | |    |
+ $--BWR,hhmmss.ss,llll.ll,a,yyyyy.yy,a,x.x,T,x.x,M,x.x,N,c--c*hh<CR><LF>
+
+ Field Number: 
+  1) UTCTime
+  2) Waypoint Latitude
+  3) N = North, S = South
+  4) Waypoint Longitude
+  5) E = East, W = West
+  6) Bearing, True
+  7) T = True
+  8) Bearing, Magnetic
+  9) M = Magnetic
+ 10) Nautical Miles
+ 11) N = Nautical Miles
+ 12) Waypoint ID
+ 13) Checksum
+
+ BWW - Bearing - Waypoint to Waypoint
+
+        1   2 3   4 5    6    7
+        |   | |   | |    |    |
+ $--BWW,x.x,T,x.x,M,c--c,c--c*hh<CR><LF>
+
+ Field Number: 
+  1) Bearing Degrees, TRUE
+  2) T = True
+  3) Bearing Degrees, Magnetic
+  4) M = Magnetic
+  5) TO Waypoint
+  6) FROM Waypoint
+  7) Checksum
+
+ DBK - Depth Below Keel
+
+        1   2 3   4 5   6 7
+        |   | |   | |   | |
+ $--DBK,x.x,f,x.x,M,x.x,F*hh<CR><LF>
+
+ Field Number: 
+  1) Depth, feet
+  2) f = feet
+  3) Depth, meters
+  4) M = meters
+  5) Depth, Fathoms
+  6) F = Fathoms
+  7) Checksum
+
+ DBS - Depth Below Surface
+
+        1   2 3   4 5   6 7
+        |   | |   | |   | |
+ $--DBS,x.x,f,x.x,M,x.x,F*hh<CR><LF>
+
+ Field Number: 
+  1) Depth, feet
+  2) f = feet
+  3) Depth, meters
+  4) M = meters
+  5) Depth, Fathoms
+  6) F = Fathoms
+  7) Checksum
+
+ DBT - Depth below transducer
+
+        1   2 3   4 5   6 7
+        |   | |   | |   | |
+ $--DBT,x.x,f,x.x,M,x.x,F*hh<CR><LF>
+
+ Field Number: 
+  1) Depth, feet
+  2) f = feet
+  3) Depth, meters
+  4) M = meters
+  5) Depth, Fathoms
+  6) F = Fathoms
+  7) Checksum
+
+ DCN - Decca Position
+                                      11  13      16
+        1  2  3   4 5  6   7 8  9   10| 12| 14  15| 17
+        |  |  |   | |  |   | |  |   | | | | |   | | |
+ $--DCN,xx,cc,x.x,A,cc,x.x,A,cc,x.x,A,A,A,A,x.x,N,x*hh<CR><LF>
+
+ Field Number: 
+  1) Decca chain identifier
+  2) Red Zone Identifier
+  3) Red Line Of Position
+  4) Red Master Line Status
+  5) Green Zone Identifier
+  6) Green Line Of Position
+  7) Green Master Line Status
+  8) Purple Zone Identifier
+  9) Purple Line Of Position
+ 10) Purple Master Line Status
+ 11) Red Line Navigation Use
+ 12) Green Line Navigation Use
+ 13) Purple Line Navigation Use
+ 14) Position Uncertainity
+ 15) N = Nautical Miles
+ 16) Fix Data Basis
+     1 = Normal Pattern
+     2 = Lane Identification Pattern
+     3 = Lane Identification Transmissions
+ 17) Checksum
+
+ DPT - Heading - Deviation & Variation
+
+        1   2   3
+        |   |   |
+ $--DPT,x.x,x.x*hh<CR><LF>
+
+ Field Number: 
+  1) Depth, meters
+  2) Offset from transducer, 
+     positive means distance from tansducer to water line
+     negative means distance from transducer to keel
+  3) Checksum
+
+ FSI - Frequency Set Information
+
+        1      2      3 4 5
+        |      |      | | |
+ $--FSI,xxxxxx,xxxxxx,c,x*hh<CR><LF>
+
+ Field Number: 
+  1) Transmitting Frequency
+  2) Receiving Frequency
+  3) Communications Mode (NMEA Syntax 2)
+  4) Power Level
+  5) Checksum
+
+ GGA - Global Positioning System Fix Data
+ Time, Position and fix related data fora GPS receiver.
+
+                                                      11
+        1         2       3 4        5 6 7  8   9  10 |  12 13  14   15
+        |         |       | |        | | |  |   |   | |   | |   |    |
+ $--GGA,hhmmss.ss,llll.ll,a,yyyyy.yy,a,x,xx,x.x,x.x,M,x.x,M,x.x,xxxx*hh<CR><LF>
+
+ Field Number: 
+  1) Universal Time Coordinated (UTC)
+  2) Latitude
+  3) N or S (North or South)
+  4) Longitude
+  5) E or W (East or West)
+  6) GPS Quality Indicator,
+     0 - fix not available,
+     1 - GPS fix,
+     2 - Differential GPS fix
+  7) Number of satellites in view, 00 - 12
+  8) Horizontal Dilution of precision
+  9) Antenna Altitude above/below mean-sea-level (geoid) 
+ 10) Units of antenna altitude, meters
+ 11) Geoidal separation, the difference between the WGS-84 earth
+     ellipsoid and mean-sea-level (geoid), "-" means mean-sea-level
+     below ellipsoid
+ 12) Units of geoidal separation, meters
+ 13) Age of differential GPS data, time in seconds since last SC104
+     type 1 or 9 update, null field when DGPS is not used
+ 14) Differential reference station ID, 0000-1023
+ 15) Checksum
+
+ GLC - Geographic Position, Loran-C
+                                           12    14
+        1    2   3 4   5 6   7 8   9 10  11|   13|
+        |    |   | |   | |   | |   | |   | |   | |
+ $--GLC,xxxx,x.x,a,x.x,a,x.x,a.x,x,a,x.x,a,x.x,a*hh<CR><LF>
+
+ Field Number: 
+  1) GRI Microseconds/10
+  2) Master TOA Microseconds
+  3) Master TOA Signal Status
+  4) Time Difference 1 Microseconds
+  5) Time Difference 1 Signal Status
+  6) Time Difference 2 Microseconds
+  7) Time Difference 2 Signal Status
+  8) Time Difference 3 Microseconds
+  9) Time Difference 3 Signal Status
+ 10) Time Difference 4 Microseconds
+ 11) Time Difference 4 Signal Status
+ 12) Time Difference 5 Microseconds
+ 13) Time Difference 5 Signal Status
+ 14) Checksum
+
+ GLL - Geographic Position - Latitude/Longitude
+
+	1       2 3        4 5         6 7
+	|       | |        | |         | |
+ $--GLL,llll.ll,a,yyyyy.yy,a,hhmmss.ss,A*hh<CR><LF>
+
+ Field Number: 
+  1) Latitude
+  2) N or S (North or South)
+  3) Longitude
+  4) E or W (East or West)
+  5) Universal Time Coordinated (UTC)
+  6) Status A - Data Valid, V - Data Invalid
+  7) Checksum
+
+ GSA - GPS DOP and active satellites
+
+	1 2 3                        14 15  16  17  18
+	| | |                         |  |   |   |   |
+ $--GSA,a,a,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x.x,x.x,x.x*hh<CR><LF>
+
+ Field Number: 
+  1) Selection mode
+  2) Mode
+  3) ID of 1st satellite used for fix
+  4) ID of 2nd satellite used for fix
+  ...
+  14) ID of 12th satellite used for fix
+  15) PDOP in meters
+  16) HDOP in meters
+  17) VDOP in meters
+  18) checksum
+
+ GSV - Satellites in view
+
+	1 2 3 4 5 6 7     n
+	| | | | | | |     |
+ $--GSV,x,x,x,x,x,x,x,...*hh<CR><LF>
+
+ Field Number: 
+  1) total number of messages
+  2) message number
+  3) satellites in view
+  4) satellite number
+  5) elevation in degrees
+  6) azimuth in degrees to true
+  7) SNR in dB
+  more satellite infos like 4)-7)
+  n) checksum
+
+ GTD - Geographic Location in Time Differences
+
+ 	 1   2   3   4   5  6
+	 |   |   |   |   |  |
+ $--GTD,x.x,x.x,x.x,x.x,x.x*hh<CR><LF>
+
+ Field Number: 
+  1) time difference
+  2) time difference
+  3) time difference
+  4) time difference
+  5) time difference
+  n) checksum
+
+ GXA - TRANSIT Position - Latitude/Longitude
+ Location and time of TRANSIT fix at waypoint
+
+        1         2       3 4        5 6    7 8
+        |         |       | |        | |    | |
+ $--GXA,hhmmss.ss,llll.ll,a,yyyyy.yy,a,c--c,X*hh<CR><LF>
+
+ Field Number: 
+ 1) UTC of position fix
+ 2) Latitude
+ 3) East or West
+ 4) Longitude
+ 5) North or South
+ 6) Waypoint ID
+ 7) Satelite number
+ 8) Checksum
+
+ HDG - Heading - Deviation & Variation
+
+        1   2   3 4   5 6
+        |   |   | |   | |
+ $--HDG,x.x,x.x,a,x.x,a*hh<CR><LF>
+
+ Field Number: 
+  1) Magnetic Sensor heading in degrees
+  2) Magnetic Deviation, degrees
+  3) Magnetic Deviation direction, E = Easterly, W = Westerly
+  4) Magnetic Variation degrees
+  5) Magnetic Variation direction, E = Easterly, W = Westerly
+  6) Checksum
+
+ HDM - Heading - Magnetic
+
+        1   2 3
+        |   | |
+ $--HDM,x.x,M*hh<CR><LF>
+
+ Field Number: 
+  1) Heading Degrees, magnetic
+  2) M = magnetic
+  3) Checksum
+
+ HDT - Heading - True
+
+        1   2 3
+        |   | |
+ $--HDT,x.x,T*hh<CR><LF>
+
+ Field Number: 
+  1) Heading Degrees, true
+  2) T = True
+  3) Checksum
+
+ HSC - Heading Steering Command
+
+        1   2 3   4  5
+        |   | |   |  |
+ $--HSC,x.x,T,x.x,M,*hh<CR><LF>
+
+ Field Number: 
+  1) Heading Degrees, True
+  2) T = True
+  3) Heading Degrees, Magnetic
+  4) M = Magnetic
+  5) Checksum
+
+ LCD - Loran-C Signal Data
+
+        1    2   3   4   5   6   7   8   9   10  11  12  13  14
+        |    |   |   |   |   |   |   |   |   |   |   |   |   |
+ $--LCD,xxxx,xxx,xxx,xxx,xxx,xxx,xxx,xxx,xxx,xxx,xxx,xxx,xxx*hh<CR><LF>
+
+ Field Number: 
+  1) GRI Microseconds/10
+  2) Master Relative SNR
+  3) Master Relative ECD
+  4) Time Difference 1 Microseconds
+  5) Time Difference 1 Signal Status
+  6) Time Difference 2 Microseconds
+  7) Time Difference 2 Signal Status
+  8) Time Difference 3 Microseconds
+  9) Time Difference 3 Signal Status
+ 10) Time Difference 4 Microseconds
+ 11) Time Difference 4 Signal Status
+ 12) Time Difference 5 Microseconds
+ 13) Time Difference 5 Signal Status
+ 14) Checksum
+
+ MTW - Water Temperature
+
+        1   2 3
+        |   | | 
+ $--MTW,x.x,C*hh<CR><LF>
+
+ Field Number: 
+  1) Degrees
+  2) Unit of Measurement, Celcius
+  3) Checksum
+
+ MWV - Wind Speed and Angle
+
+        1   2 3   4 5
+        |   | |   | |
+ $--MWV,x.x,a,x.x,a*hh<CR><LF>
+
+ Field Number: 
+  1) Wind Angle, 0 to 360 degrees
+  2) Reference, R = Relative, T = True
+  3) Wind Speed
+  4) Wind Speed Units, K/M/N
+  5) Status, A = Data Valid
+  6) Checksum
+
+ OLN - Omega Lane Numbers
+
+        1          2          3          4
+        |--------+ |--------+ |--------+ |
+ $--OLN,aa,xxx,xxx,aa,xxx,xxx,aa,xxx,xxx*hh<CR><LF>
+
+ Field Number: 
+  1) Omega Pair 1
+  2) Omega Pair 1
+  3) Omega Pair 1
+  4) Checksum
+
+ OSD - Own Ship Data
+
+        1   2 3   4 5   6 7   8   9 10
+        |   | |   | |   | |   |   | |
+ $--OSD,x.x,A,x.x,a,x.x,a,x.x,x.x,a*hh<CR><LF>
+
+ Field Number: 
+  1) Heading, degrees true
+  2) Status, A = Data Valid
+  3) Vessel Course, degrees True
+  4) Course Reference
+  5) Vessel Speed
+  6) Speed Reference
+  7) Vessel Set, degrees True
+  8) Vessel drift (speed)
+  9) Speed Units
+ 10) Checksum
+
+ R00 - Waypoints in active route
+
+        1                n
+        |                | 
+ $--R00,c---c,c---c,....*hh<CR><LF>
+
+ Field Number: 
+  1) waypoint ID
+  ...
+  n) checksum
+
+ RMA - Recommended Minimum Navigation Information
+                                                    12
+        1 2       3 4        5 6   7   8   9   10  11|
+        | |       | |        | |   |   |   |   |   | |
+ $--RMA,A,llll.ll,a,yyyyy.yy,a,x.x,x.x,x.x,x.x,x.x,a*hh<CR><LF>
+
+ Field Number: 
+  1) Blink Warning
+  2) Latitude
+  3) N or S
+  4) Longitude
+  5) E or W
+  6) Time Difference A, uS
+  7) Time Difference B, uS
+  8) Speed Over Ground, Knots
+  9) Track Made Good, degrees true
+ 10) Magnetic Variation, degrees
+ 11) E or W
+ 12) Checksum
+
+ RMB - Recommended Minimum Navigation Information
+                                                             14
+        1 2   3 4    5    6       7 8        9 10  11  12  13|
+        | |   | |    |    |       | |        | |   |   |   | |
+ $--RMB,A,x.x,a,c--c,c--c,llll.ll,a,yyyyy.yy,a,x.x,x.x,x.x,A*hh<CR><LF>
+
+ Field Number: 
+  1) Status, V = Navigation receiver warning
+  2) Cross Track error - nautical miles
+  3) Direction to Steer, Left or Right
+  4) TO Waypoint ID
+  5) FROM Waypoint ID
+  6) Destination Waypoint Latitude
+  7) N or S
+  8) Destination Waypoint Longitude
+  9) E or W
+ 10) Range to destination in nautical miles
+ 11) Bearing to destination in degrees True
+ 12) Destination closing velocity in knots
+ 13) Arrival Status, A = Arrival Circle Entered
+ 14) Checksum
+
+ RMC - Recommended Minimum Navigation Information
+                                                            12
+        1         2 3       4 5        6 7   8   9    10  11|
+        |         | |       | |        | |   |   |    |   | |
+ $--RMC,hhmmss.ss,A,llll.ll,a,yyyyy.yy,a,x.x,x.x,xxxx,x.x,a*hh<CR><LF>
+
+ Field Number: 
+  1) UTC Time
+  2) Status, V = Navigation receiver warning
+  3) Latitude
+  4) N or S
+  5) Longitude
+  6) E or W
+  7) Speed over ground, knots
+  8) Track made good, degrees true
+  9) Date, ddmmyy
+ 10) Magnetic Variation, degrees
+ 11) E or W
+ 12) Checksum
+
+ ROT - Rate Of Turn
+
+        1   2 3
+        |   | |
+ $--ROT,x.x,A*hh<CR><LF>
+
+ Field Number: 
+  1) Rate Of Turn, degrees per minute, "-" means bow turns to port
+  2) Status, A means data is valid
+  3) Checksum
+
+ RPM - Revolutions
+
+        1 2 3   4   5 6
+        | | |   |   | |
+ $--RPM,a,x,x.x,x.x,A*hh<CR><LF>
+
+ Field Number: 
+  1) Sourse, S = Shaft, E = Engine
+  2) Engine or shaft number
+  3) Speed, Revolutions per minute
+  4) Propeller pitch, % of maximum, "-" means astern
+  5) Status, A means data is valid
+  6) Checksum
+
+ RSA - Rudder Sensor Angle
+
+        1   2 3   4 5
+        |   | |   | |
+ $--RSA,x.x,A,x.x,A*hh<CR><LF>
+
+ Field Number: 
+  1) Starboard (or single) rudder sensor, "-" means Turn To Port
+  2) Status, A means data is valid
+  3) Port rudder sensor
+  4) Status, A means data is valid
+  5) Checksum
+
+ RSD - RADAR System Data
+                                                        14
+        1   2   3   4   5   6   7   8   9   10  11 12 13|
+        |   |   |   |   |   |   |   |   |   |   |   | | |
+ $--RSD,x.x,x.x,x.x,x.x,x.x,x.x,x.x,x.x,x.x,x.x,x.x,a,a*hh<CR><LF>
+
+ Field Number: 
+  9) Cursor Range From Own Ship
+ 10) Cursor Bearing Degrees Clockwise From Zero
+ 11) Range Scale
+ 12) Range Units
+ 14) Checksum
+
+ RTE - Routes
+
+        1   2   3 4	 5		       x    n
+        |   |   | |    |           |    |
+ $--RTE,x.x,x.x,a,c--c,c--c, ..... c--c*hh<CR><LF>
+
+ Field Number: 
+  1) Total number of messages being transmitted
+  2) Message Number
+  3) Message mode
+     c = complete route, all waypoints
+     w = working route, the waypoint you just left, the waypoint you're heading to then all the rest
+  4) Waypoint ID
+  x) More Waypoints
+  n) Checksum
+
+ SFI - Scanning Frequency Information
+
+        1   2   3      4                     x
+        |   |   |      |                     |
+ $--SFI,x.x,x.x,xxxxxx,c .......... xxxxxx,c*hh<CR><LF>
+
+ Field Number: 
+  1) Total Number Of Messages
+  2) Message Number
+  3) Frequency 1
+  4) Mode 1
+  x) Checksum
+
+ STN - Multiple Data ID
+
+        1   2
+        |   |
+ $--STN,x.x,*hh<CR><LF>
+
+ Field Number: 
+  1) Talker ID Number
+  2) Checksum
+
+ TRF - TRANSIT Fix Data
+                                                                    13
+        1         2      3       4 5        6 7   8   9   10  11  12|
+        |         |      |       | |        | |   |   |   |   |   | |
+ $--TRF,hhmmss.ss,xxxxxx,llll.ll,a,yyyyy.yy,a,x.x,x.x,x.x,x.x,xxx,A*hh<CR><LF>
+
+ Field Number: 
+  1) UTC Time
+  2) Date, ddmmyy
+  3) Latitude
+  4) N or S
+  5) Longitude
+  6) E or W
+  7) Elevation Angle
+  8) Number of iterations
+  9) Number of Doppler intervals
+ 10) Update distance, nautical miles
+ 11) Satellite ID
+ 12) Data Validity
+ 13) Checksum
+
+ TTM - Tracked Target Message
+
+                                         11     13
+        1  2   3   4 5   6   7 8   9   10|    12| 14
+        |  |   |   | |   |   | |   |   | |    | | |
+ $--TTM,xx,x.x,x.x,a,x.x,x.x,a,x.x,x.x,a,c--c,a,a*hh<CR><LF>
+
+ Field Number: 
+  1) Target Number
+  2) Target Distance
+  3) Bearing from own ship
+  4) Bearing Units
+  5) Target speed
+  6) Target Course
+  7) Course Units
+  8) Distance of closest-point-of-approach
+  9) Time until closest-point-of-approach "-" means increasing
+ 10) "-" means increasing
+ 11) Target name
+ 12) Target Status
+ 13) Reference Target
+ 14) Checksum
+
+ VBW - Dual Ground/Water Speed
+
+        1   2   3 4   5   6 7
+        |   |   | |   |   | |
+ $--VBW,x.x,x.x,A,x.x,x.x,A*hh<CR><LF>
+
+ Field Number: 
+  1) Longitudinal water speed, "-" means astern
+  2) Transverse water speed, "-" means port
+  3) Status, A = Data Valid
+  4) Longitudinal ground speed, "-" means astern
+  5) Transverse ground speed, "-" means port
+  6) Status, A = Data Valid
+  7) Checksum
+
+ VDR - Set and Drift
+
+        1   2 3   4 5   6 7
+        |   | |   | |   | |
+ $--VDR,x.x,T,x.x,M,x.x,N*hh<CR><LF>
+
+ Field Number: 
+  1) Degress True
+  2) T = True
+  3) Degrees Magnetic
+  4) M = Magnetic
+  5) Knots (speed of current)
+  6) N = Knots
+  7) Checksum
+
+ VHW - Water speed and heading
+
+        1   2 3   4 5   6 7   8 9
+        |   | |   | |   | |   | |
+ $--VHW,x.x,T,x.x,M,x.x,N,x.x,K*hh<CR><LF>
+
+ Field Number: 
+  1) Degress True
+  2) T = True
+  3) Degrees Magnetic
+  4) M = Magnetic
+  5) Knots (speed of vessel relative to the water)
+  6) N = Knots
+  7) Kilometers (speed of vessel relative to the water)
+  8) K = Kilometers
+  9) Checksum
+
+ VLW - Distance Traveled through Water
+
+        1   2 3   4 5
+        |   | |   | |
+ $--VLW,x.x,N,x.x,N*hh<CR><LF>
+
+ Field Number: 
+  1) Total cumulative distance
+  2) N = Nautical Miles
+  3) Distance since Reset
+  4) N = Nautical Miles
+  5) Checksum
+
+ VPW - Speed - Measured Parallel to Wind
+
+        1   2 3   4 5
+        |   | |   | |
+ $--VPW,x.x,N,x.x,M*hh<CR><LF>
+
+ Field Number: 
+  1) Speed, "-" means downwind
+  2) N = Knots
+  3) Speed, "-" means downwind
+  4) M = Meters per second
+  5) Checksum
+
+ VTG - Track made good and Ground speed
+
+        1   2 3   4 5	 6 7   8 9
+        |   | |   | |	 | |   | |
+ $--VTG,x.x,T,x.x,M,x.x,N,x.x,K*hh<CR><LF>
+
+ Field Number: 
+  1) Track Degrees
+  2) T = True
+  3) Track Degrees
+  4) M = Magnetic
+  5) Speed Knots
+  6) N = Knots
+  7) Speed Kilometers Per Hour
+  8) K = Kilometers Per Hour
+  9) Checksum
+
+ VWR - Relative Wind Speed and Angle
+
+         1  2  3  4  5  6  7  8 9
+         |  |  |  |  |  |  |  | |
+ $--VWR,x.x,a,x.x,N,x.x,M,x.x,K*hh<CR><LF>
+
+ Field Number: 
+  1) Wind direction magnitude in degrees
+  2) Wind direction Left/Right of bow
+  3) Speed
+  4) N = Knots
+  5) Speed
+  6) M = Meters Per Second
+  7) Speed
+  8) K = Kilometers Per Hour
+  9) Checksum
+
+ WCV - Waypoint Closure Velocity
+
+        1   2 3    4
+        |   | |    |
+ $--WCV,x.x,N,c--c*hh<CR><LF>
+
+ Field Number: 
+  1) Velocity
+  2) N = knots
+  3) Waypoint ID
+  4) Checksum
+
+ WNC - Distance - Waypoint to Waypoint
+
+        1   2 3   4 5    6    7
+        |   | |   | |    |    |
+ $--WNC,x.x,N,x.x,K,c--c,c--c*hh<CR><LF>
+
+ Field Number: 
+  1) Distance, Nautical Miles
+  2) N = Nautical Miles
+  3) Distance, Kilometers
+  4) K = Kilometers
+  5) TO Waypoint
+  6) FROM Waypoint
+  7) Checksum
+
+ WPL - Waypoint Location
+
+	1       2 3        4 5    6
+        |       | |        | |    |
+ $--WPL,llll.ll,a,yyyyy.yy,a,c--c*hh<CR><LF>
+
+ Field Number: 
+  1) Latitude
+  2) N or S (North or South)
+  3) Longitude
+  4) E or W (East or West)
+  5) Waypoint name
+  6) Checksum     
+
+ XDR - Cross Track Error - Dead Reckoning
+
+        1 2   3 4			    n
+        | |   | |            |
+ $--XDR,a,x.x,a,c--c, ..... *hh<CR><LF>
+
+ Field Number: 
+  1) Transducer Type
+  2) Measurement Data
+  3) Units of measurement
+  4) Name of transducer
+  x) More of the same
+  n) Checksum
+
+ XTE - Cross-Track Error, Measured
+
+        1 2 3   4 5  6
+        | | |   | |  |
+ $--XTE,A,A,x.x,a,N,*hh<CR><LF>
+
+ Field Number: 
+  1) Status
+     V = LORAN-C Blink or SNR warning
+     V = general warning flag or other navigation systems when a reliable
+         fix is not available
+  2) Status
+     V = Loran-C Cycle Lock warning flag
+     A = OK or not used
+  3) Cross Track Error Magnitude
+  4) Direction to steer, L or R
+  5) Cross Track Units, N = Nautical Miles
+  6) Checksum
+
+ XTR - Cross Track Error - Dead Reckoning
+
+        1   2 3 4
+        |   | | |
+ $--XTR,x.x,a,N*hh<CR><LF>
+
+ Field Number: 
+  1) Magnitude of cross track error
+  2) Direction to steer, L or R
+  3) Units, N = Nautical Miles
+  4) Checksum
+
+ ZDA - Time & Date
+ UTC, day, month, year and local time zone
+
+	1         2  3  4    5  6  7
+        |         |  |  |    |  |  |
+ $--ZDA,hhmmss.ss,xx,xx,xxxx,xx,xx*hh<CR><LF>
+
+ Field Number: 
+  1) Local zone minutes description, same sign as local hours
+  2) Local zone description, 00 to +- 13 hours
+  3) Year
+  4) Month, 01 to 12
+  5) Day, 01 to 31
+  6) Universal Time Coordinated (UTC)
+  7) Checksum
+
+ ZFO - UTC & Time from origin Waypoint
+
+        1         2         3    4
+        |         |         |    |
+ $--ZFO,hhmmss.ss,hhmmss.ss,c--c*hh<CR><LF>
+
+ Field Number: 
+  1) Universal Time Coordinated (UTC)
+  2) Elapsed Time
+  3) Origin Waypoint ID
+  4) Checksum
+
+ ZTG - UTC & Time to Destination Waypoint
+
+        1         2         3    4
+        |         |         |    |
+ $--ZTG,hhmmss.ss,hhmmss.ss,c--c*hh<CR><LF>
+
+ Field Number: 
+  1) Universal Time Coordinated (UTC)
+  2) Time Remaining
+  3) Destination Waypoint ID
+  4) Checksum
+
+****************************************************************
+
+New found in web: (data fields unknown)
+
+DSC - Digital Selective Calling Information
+DSE - Extended DSC
+DSI - DSC Transponder Initiate
+DSR - DSC Transponder Response
+DTM - Datum Reference
+GBS - GPS Satellite Fault Detection
+GRS - GPS Range Residuals
+GST - GPS Pseudorange Noise Statistics
+MSK - MSK Receiver Interface 
+MSS - MSK Receiver Signal Status 
+MWD - Wind Direction & Speed
+TLL - Target Latitude and Longitude
+WDC - Distance to Waypoint - Great Circle
+WDR - Distance to Waypoint - Rhumb Line
+ZDL - Time and Distance to Variable Point
+\ No newline at end of file
diff --git a/Documentation/README.Bluetooth b/Documentation/README.Bluetooth
new file mode 100644
index 0000000..42ad3ed
--- /dev/null
+++ b/Documentation/README.Bluetooth
@@ -0,0 +1,19 @@
+maybe you have to pair the devices first
+
+moby:~# hcitool scan
+Scanning ...
+        00:15:7F:00:51:08       Bluetooth GPS
+
+moby:~# hcitool cc      00:15:7F:00:51:08
+moby:~# hcitool con
+Connections:
+        < ACL 00:15:7F:00:51:08 handle 41 state 1 lm MASTER 
+
+moby:~# rfcomm bind /dev/rfcomm0 00:15:7F:00:51:08
+
+moby:~# cat /dev/rfcomm0 count=10
+
+moby:~# killall -9 gpsd
+
+moby:~# gpsd -p /dev/rfcomm0
+
diff --git a/Documentation/README.Fedora b/Documentation/README.Fedora
new file mode 100644
index 0000000..3e508dd
--- /dev/null
+++ b/Documentation/README.Fedora
@@ -0,0 +1,53 @@
+
+Installing GPSDRIVE on "Fedora Core release 5" 
+----------------------------------------------
+
+yum update
+
+yum -y install geos
+yum -y install hdf5
+yum -y install mysql
+yum -y install perl-DBI
+yum -y install unixODBC
+yum -y install e2fsprogs-devel
+yum -y install giflib-devel
+yum -y install hdf
+yum -y install hdf-devel
+yum -y install hdf5-devel
+yum -y install krb5-devel
+yum -y install libjpeg-devel
+yum -y install libtiff-devel
+yum -y install mysql-devel
+yum -y install mysql-server
+yum -y install netcdf
+yum -y install netcdf-devel
+yum -y install openssl-devel
+yum -y install postgresql
+yum -y install postgresql-devel
+yum -y install proj
+yum -y install proj-devel
+yum -y install shapelib
+yum -y install shapelib-devel
+yum -y install sqlite-devel
+yum -y install unixODBC-devel
+
+rpm -Uvh http://ftp.intevation.de/freegis/fedora/5/RPMS/gdal-1.3.1-2.i386.rpm
+rpm -Uvh http://ftp.intevation.de/freegis/fedora/5/RPMS/gdal-devel-1.3.1-2.i386.rpm
+
+yum -y install libart_lgpl
+yum -y install libart_lgpl-devel
+yum -y install ImageMagick-perl
+
+wget ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-6.7.tar.gz
+tar xzf pcre-6.7.tar.gz
+cd pcre-6.7 && ./configure && make && make install
+
+yum -y install gpsd gpsd-clients gpsd-devel
+
+perl -e shell -MCPAN
+
+	force install Date::Manip
+	force install WWW::Mechanize
+	force install Text::Query
+
+Enjoy!
+\ No newline at end of file
diff --git a/Documentation/README.FreeBSD b/Documentation/README.FreeBSD
new file mode 100644
index 0000000..7350559
--- /dev/null
+++ b/Documentation/README.FreeBSD
@@ -0,0 +1,38 @@
+$Id: README.FreeBSD 2 1994-06-07 08:35:10Z tweety $
+
+                    INSTALLING GPSDRIVE ON FREEBSD
+
+
+The easiest way to install Gpsdrive on FreeBSD is to use the FreeBSD port
+system: Go to http://www.freebsd.org/astro.html and search for "gpsdrive".
+
+
+To install a binary package, you can use the remote fetch capability of
+pkg_add:
+
+$ su -             [become root]
+# pkg_add -r gpsdrive
+# exit             [loose root]
+
+
+To install from source, make sure you have an updated ports tree [1] and then
+do the following:
+
+$ su -             [become root]
+# cd /usr/ports/astro/gpsdrive
+# make
+# make install
+# make clean
+# exit             [loose root]
+
+
+Enjoy!
+
+Feel free to contact me if you have questions regarding the FreeBSD port
+or if you want an updated version.
+
+Marco Molteni <molter@gufi.org>
+http://www.gufi.org/~molter/
+
+[1] http://www.freebsd.org/handbook/ports-using.html. To have an updated
+    ports collection you'll want to use CVSup, as described there.
diff --git a/Documentation/README.OpenStreetMap-Vektordata b/Documentation/README.OpenStreetMap-Vektordata
new file mode 100644
index 0000000..9cf0e10
--- /dev/null
+++ b/Documentation/README.OpenStreetMap-Vektordata
@@ -0,0 +1,18 @@
+Download and import Vektormaps from OSM:
+----------------------------------------
+The Vectormaps have to be downloaded from OpenStreetMap (planet.openstreetmap.org). 
+Normally you would do this by starting:
+
+ geoinfo.pl --db-user=root --db-password=<mysql-root-pwd> --create-db    --fill-defaults
+
+ geoinfo.pl --db-user=root --db-password=<mysql-root-pwd> --osm   
+
+The second would download the monthly snapshot 
+    Currently planet-2006-07.osm.bz2
+unpack it and import it to the mysql Database. 
+
+After installing the monthly snapshot you can use the point
+of interests from openstreetmap to search for a location.
+The Street Data is no longer imported this way. To see the 
+Street Data from OpenStreetMap in GpsDrive you'll have to 
+use the Mapnik Plugin
diff --git a/Documentation/README.SQL b/Documentation/README.SQL
new file mode 100644
index 0000000..137df30
--- /dev/null
+++ b/Documentation/README.SQL
@@ -0,0 +1,157 @@
+Version for gpsdrive-2.x
+
+Since version 1.29 GpsDrive supports SQL database support.
+
+Supported databases (September 2003): MySQL 
+
+Compiling:
+----------
+
+There is no MySQL needed for compiling, the needed library
+libmysqlclient.so.10 will be loaded at runtime, if found.
+
+Running and first initialization:
+---------------------------------
+
+If you have not already done, install the mysql server package for
+your distribution.
+
+o Start the server, mostly with: /etc/init.d/mysql start
+
+UPDATE:
+-------------------------------------------------------------------------------
+
+There is now a new way to create the initial database but you do need
+to have perl installed.  The new script is gpsdrive/bin/geoinfo.pl and
+the requierd command line is discussed below. Check out geoinfo --help
+to see all of its options.
+
+-------------------------------------------------------------------------------
+
+o To create a initial database with included Perl file 'geoinfo.pl'.
+  If this is a new database and you haven't created a root user yet
+  something like the following should do the trick.  Otherwise use the
+  MYSQL Administrator.
+
+  /usr/bin/mysqladmin -u root password 'enter-your-good-new-password-here'
+
+  Once you have done that run the perl script like this.
+  geoinfo.pl --db-user=root --db-password='enter-your-good-new-password-here'
+
+
+Update:
+-------
+
+If you already have the database and you update GpsDrive, make sure
+your table structure is updated with the above geoinfo.pl script.
+
+Security:
+---------
+
+GpsDrive uses the username 'gast' and the password 'gast' as default
+to access the table 'waypoints' in the database 'geoinfo'. If you want
+to change this in the SQL database, change this in GpsDrive also. Edit
+the file $HOME/.gpsdrive/gpsdriverc lines for dbuser and dbpass.
+
+Be aware that the MySQL password for this database is stored in
+cleartext in gpsdriverc!!!
+
+Importing existing waypoint files:
+----------------------------------
+I also provided the script 'convert-waypoints.pl', which creates a .gpx file
+from gpsdrive waypointfiles. 
+
+You then can import the created file into the database with:
+poi-manager.pl -i -f FILENAME
+
+
+=======================================================================
+IMPORTANT:
+
+The 'Use SQL' button currently selects only, if newly added waypoints
+are added to the database or to the waypointsfile.
+
+=======================================================================
+
+
+Backing up and restoring your database
+--------------------------------------
+
+Sven added the two shell scripts gpssql_backup.sh and
+gpssql_restore.sh for very simple use. Just read the comments within
+those scripts for usage information.
+
+Another new way to do this, is to use the script poi-manager.pl, which
+reads and creates .gpx files.
+
+
+Editing your waypoints:
+-----------------------
+
+You can use "mysqlcc" (http://www.mysql.com/downloads/gui-mycc.html),
+"phpmyadmin" or OpenOffice to edit the waypoints.
+
+Here is a little HowTo from Charles Curley <charlescurley@charlescurley.com>
+
+One of the really nice things about OpenOffice.org
+(http://OpenOffice.org/) is that you can use databases as data sources
+for documents and spreadsheets, rather like MS Access and MS Office. I
+just set up the GpsDrive waypoints MySQL database as a data source.
+
+I did it on Fedora Core Linux. This should work on other Linux disties
+as well.
+
+For Openoffice 1.x:
+
+First, get John McCreesh's "OpenOffice.org 1.0, ODBC, and MySQL
+'How-to'" (http://www.unixodbc.org/doc/OOoMySQL9.pdf), read it through
+page 7, then and do exactly what the man says, step by step. His
+instructions are for Red Hat 9, and I had no problems. His
+instructions are for OpenOffice.org 1.0, but I had no problems on
+OpenOffice.org 1.1.
+
+I used exactly his [MySQL] stanza in /etc/odbcinst.ini. For odbc.ini,
+I made two changes. First, I used ~/.odbc.ini instead of /etc/odbc.ini
+for tighter security. Second, I used a customized stanza for the
+geoinfo database:
+
+[geoinfo]
+Trace    = Off
+TraceFile= stderr
+Driver   = MySQL
+SERVER   = localhost
+Database = geoinfo
+USER     = gast
+PASSWORD = gast
+PORT     = 3306
+
+Third, in the ODBC tab of the Data Source Administration window, check
+"password required" and enter a user name of "gast".
+
+For OpenOffice.org 2.0.2:
+
+Follow this writeup:
+
+http://www.linuxgangster.org/modules.php?name=Content&file=viewarticle&id=10
+
+Then add the following to your odbc.ini:
+
+[MySQL-geoinfo]
+Description = MySQL geoinfo database
+Driver = MySQL
+Server = localhost
+Database = geoinfo
+Port = 3306
+
+Testing:
+
+To test the ODBC connection to MySQL, you run isql like so:
+
+isql <dbname> <user> <password>
+isql geoinfo gast gast
+
+and in isql, run:
+
+select * on waypoints
+
+The result is a nice GUI tool for editing one's waypoints.
diff --git a/Documentation/README.gpspoint2gspdrive b/Documentation/README.gpspoint2gspdrive
new file mode 100644
index 0000000..c699a7c
--- /dev/null
+++ b/Documentation/README.gpspoint2gspdrive
@@ -0,0 +1,37 @@
+NAME
+	gpspoint2gpsdrive.pl
+
+SYNOPSIS
+	gpspoint2gpsdrive -[vhf] [gpspoint-file]
+
+DESCRIPTION
+	Extract track information from a gpspoint file and write in 
+	gpsdrive format track files (track*.sav) for viewing tracks.
+
+	Using this script you can load tracks into gpsdrive and see where
+	you have been!  Useful if you have not been carrying your computer
+	around with you.
+
+COMMAND-LINE OPTIONS
+	-h	Display usage information.
+	
+	-v	Be verbose about the extraction.
+
+	-f 	Specify what file to get the data from.
+
+NOTES
+	Uses the names supplied by the GPS to form the names of the track 
+	files, will OVERWRITE any extant track files with the same names.
+	Although altitude information is converted, I don't think gpsdrive
+	makes any use of it (yet).
+
+SEE ALSO
+	gpspoint
+	gpsdrive
+
+AUTHOR
+	Steve Merrony (steve@cygnet.co.uk)
+
+	Please send bug reports to the above address.
+
+	
diff --git a/Documentation/README.kismet b/Documentation/README.kismet
new file mode 100644
index 0000000..da97472
--- /dev/null
+++ b/Documentation/README.kismet
@@ -0,0 +1,55 @@
+Attention!!!!
+
+Gpsdrive (starting with version 1.31) only supports the newer
+kismet version (>=2.8.0) because the server format has changed.
+Older versions of GpsDrive works only with kismet 2.6.x
+=================================================================
+
+
+GpsDrive supports the wireless sniffer 'kismet'.
+
+Kismet is a 802.11b wireless network sniffer. It is capable of
+sniffing using almost any wireless card supported in Linux, including
+Prism2 based cards supported by the Wlan-NG project (Linksys, Dlink,
+Rangelan, etc), cards which support standard packet capture via
+libpcap (Cisco), and limited support for cards without RF Monitor
+support.
+
+More info about kismet: http://www.kismetwireless.net
+
+How do I use GpsDrive with kismet?
+----------------------------------
+
+You have to start kismet first (gpsd must be running before kismet, so
+kismet can detect the presence of a gps receiver).
+After kismet is running, start GpsDrive. If you have speech output,
+you get a voice information that kismet was found.
+
+Kismet support of GpsDrive is only available if you use SQL-Support
+and 'use SQL' is selected in GpsDrive.
+
+What does GpsDrive do with kismet?
+----------------------------------
+
+If kismet detects a wireless accesspoint, it is stored in the SQL
+database and an icon is shown on the map (a open lock symbol for an
+uncrypted Network, a closed lock symbol for an accesspoint using WEP
+encryption). You have to enable the waypoints in Settings/SQL menu.
+
+If you have speech output, you hear a message about the new waypoint.
+
+
+since v2.04:
+============
+GpsDrive stores new accesspoints and updates them, if their position
+changed. If kismet gives "best" values for lat/lon, then this values
+are stored also all other parameter like encrypted or not.
+
+Important:
+==========
+Sometimes kismet detects a new AP, but GpsDrive don't stores it. This
+is because kismet provides no valid GPS position at this moment.
+
+
+
+
diff --git a/Documentation/README.lib_map b/Documentation/README.lib_map
new file mode 100644
index 0000000..acae83c
--- /dev/null
+++ b/Documentation/README.lib_map
@@ -0,0 +1,28 @@
+
+top_* world files use the following world file format:
+
+5.000000000000  (size of pixel in x direction)
+0.000000000000  (rotation term for row)
+0.000000000000  (rotation term for column)
+-5.000000000000  (size of pixel in y direction)
+492169.690845528910  (x coordinate of upper left of upper left pixel)
+5426523.318065105000  (y coordinate of upper left of upper left pixel)
+
+Projection is direct polar relative to lat/lon 0;0 but unit is meters.
+This gives sensible results if the map is used in e.g. qgis.
+
+circumference of the Earth at the equator = 40 075.017 km
+circumference of the Earth through the poles = 40 007.863 km
+
+map_* world files use the following world file format:
+
+5000.000000000  (scale)
+0.000000000000  (ignored)
+0.000000000000  (ignored)
+-5000.00000000  (-scale)
+49.690845528910  (longitude)
+26.318065105000  (latitude)
+
+latitude, longitude and scale taken from map_koord.txt
+The above world file does not give sensible results in other GDAL applications
+it uses a special hard coded case.
diff --git a/Documentation/README.mysql b/Documentation/README.mysql
new file mode 100644
index 0000000..e40b547
--- /dev/null
+++ b/Documentation/README.mysql
@@ -0,0 +1,140 @@
+                          GpsDrive MySQL README
+                          =====================
+Contents
+========
+* Introduction
+* Install
+* Initialise the Database
+* Insert Openstreetmap Data (Optional)
+* About Openstreetmap
+* Converting a track log ready for upload to Openstreetmap <TODO>
+* MySQL Options in GpsDrive <TODO>
+* Compile MySQL (if you must)
+
+<TODO> There is still some useful information in README.SQL but lots of it is out of date.
+       The relevant parts should be added to this file and README.SQL should be removed
+       to avoid confusion.
+
+Introduction
+============
+Firstly you don't absolutely need MySQL to use GpsDrive. It will happily 
+store the basic information it needs in flat files.  However if you want 
+to use some of the more advanced features then you will need MySQL.  
+Other databases may be supported in the future but at the moment they 
+aren't. GpsDrive automatically detects if MySQL is 
+running and if it is it running it will use it.  
+
+Install
+=======
+The best way to install MySQL is to use the package manager that comes with 
+your flavour of Linux.  If for some reason this isn't possible then the next 
+best thing is to download a ready made package file from the following 
+location http://dev.mysql.com/downloads/mysql/5.0.html.  
+
+Don't forget your copy of Linux may have come with MySQL pre-installed.
+
+If you still can't find what you need then download the source tar ball (at 
+the bottom of the page) and check out the compile instructions below. 
+(not for the faint hearted)
+
+<TODO> Minimum required version of MySQL.
+(I'm not sure of the minimum but I'm using 5.0.22)
+
+Initialise the Database
+=======================
+Once you have MySQL up and running you can use these scripts to initialise 
+the database for GpsDrive.  This task was previously performed by a script 
+called create.sql which is out of date and no longer being maintained.
+
+Change directory to GpsDrive's bin folder then run the following command.
+
+./geoinfo.pl -create-db -fill-defaults -openstreetmap \
+	-db-user=root -db-password=<yourpassword> 
+
+If you have installed GpsDrive into a directory other than the default you 
+may need to update the perl library path before running the command.  Change 
+the path depending on your installation.
+
+export PERL5LIB=/<your path>/gpsdrive/share/perl5
+
+if you have not set a root password for your mysql installation, you can reset 
+it with the following command:
+   echo " UPDATE user SET Password=PASSWORD('new_password') WHERE user='root'; FLUSH PRIVILEGES;" |mysql -u root mysql
+where new_password is the new password for root.
+
+Insert Openstreetmap Data (Optional)
+====================================
+The following command downloads and inserts the openstreetmap street 
+info for Earth! from planet.openstreetmap.org/ to you local mysql. 
+
+./geoinfo.pl --db-user=root --db-password=<yourpassword> --no-delete --osm
+
+Now that you have MySQL up and running and have some data in there you 
+should see extra options in the menu on the left hand side when you start up GpsDrive.
+
+About Openstreetmap
+===================
+Rather than me describe it here you are better off to go check it out here.
+http://openstreetmap.org.  In a line (or two), it is a free to use, user 
+updatable database containing vector bassed street maps covering the whole 
+world. Users like you and me upload their gps track information and then 
+draw the streets in over top of the tracks. It is fun once you start 
+seeing results.
+
+Converting a track log ready for upload to Openstreetmap
+=======================================================
+just use osmtrackfilter
+
+
+MySQL Options in Gpsdrive
+=========================
+<TODO>
+
+
+Compile MySQL (if you must)
+===========================
+There seems to be tons of options to compile mysql.
+I found a recommended set of options and then modified them until I
+managed a clean compile.  I just googled the errors and modified the options.
+
+I'd certainly recommend doing a 'make test' to ensure everything is ok.  The built in 
+tests are quite comprehensive.
+
+The only additional package you will need if you are compiling gpsdrive on the same system is.
+
+libcurses5-dev
+
+Below is the command I used to configure mysql on both debian and DSL.
+For the full script I used see  DSL/build-mysql.sh which worked on mysql version 5.0.22
+
+Set $DEST to what ever you want or leave --prefix out for a default install.
+
+CFLAGS="-O3 -DPIC -fPIC -DUNDEF_HAVE_INITGROUPS -fno-strict-aliasing" \
+CXXFLAGS="-O3 -fno-strict-aliasing -felide-constructors -fno-exceptions -fno-rtti -fPIC -DPIC -DUNDEF_HAVE_INITGROUPS" \
+    ./configure --prefix=$DEST \
+    --enable-thread-safe-client \
+    --enable-assembler \
+    --enable-local-infile \
+    --with-unix-socket-path=/var/run/mysqld/mysqld.sock \
+    --without-debug \
+    --without-yassl \
+    --without-bench \
+    --with-extra-charsets=complex 
+
+Don't be afraid to read the documentation on mysql.org.  It is quite extensive and will save you heaps of time trying to figure it all out your self.
+
+MySQL Password
+==============
+If you forgot or never set your mysql root password, try
+ mysqladmin -u root password "mynewpassword"
+
+If you compile it your self the password may be blank.
+
+Uninstall geoinfo in MySQL
+==========================
+
+Warning: This will really delete all modifications you 
+have made to the local geoinfo database.
+
+ echo "drop database geoinfo;"| mysql -uroot -pyour_mysql_root_password
+
diff --git a/Documentation/README.nasamaps b/Documentation/README.nasamaps
new file mode 100644
index 0000000..bcd04b3
--- /dev/null
+++ b/Documentation/README.nasamaps
@@ -0,0 +1,107 @@
+
+There is support for satellite images from the NASA now!
+You need GpsDrive version >=2.08
+
+To get the maps you have 2 choices:
+
+The new maps can be found at:
+21600x21600 East Hemisphere
+ftp://veftp.gsfc.nasa.gov/bluemarble/land_shallow_topo_east.tif
+21600x21600 West Hemisphere
+ftp://veftp.gsfc.nasa.gov/bluemarble/land_shallow_topo_west.tif
+  
+
+======================================================================
+1) From the original site (only gzip compressed)
+
+Goto 
+ftp://mitch.gsfc.nasa.gov/pub/stockli/bluemarble/
+
+If you are west, download 
+MOD09A1.W.interpol.cyl.retouched.topo.3x21600x21600.gz 
+
+if you are east, download
+MOD09A1.E.interpol.cyl.retouched.topo.3x21600x21600.gz 
+
+If you are in England or West Europe, you need both files, 
+because they have to overlap.
+
+
+
+2) Download it via ED2k Link (bzip2 compressed):
+
+ed2k://|file|top_nasamap_east.raw.bz2|379972653|7312437945bd47ccf0b2a0c3452d5836|/
+ed2k://|file|top_nasamap_west.raw.bz2|226307352|13ab6e8a6e014fa23bb83db25855bb71|/
+
+This files have a uncompressed size of 1.4GB each and are in raw RGB format.
+The bzip2 compressed files are 363MB (east) and 216MB (west) in size.
+
+
+======================================================================
+
+
+How to install the maps:
+
+create a directory ~/.gpsdrive/nasamaps
+unzip the files (gunzip filename)
+
+Move the file(s) into this directory and rename it
+
+rename MOD09A1.E.*   to top_nasamap_east.raw 
+and/or
+rename MOD09A1.W.*   to top_nasamap_west.raw
+
+You can use this maps with GpsDrive >=2.08pre7
+
+
+
+The smaller maps (1280x1024) which GpsDrive needs, are created on the
+fly from this maps (which have a resolution of 21600*21600). So you
+get a map for every position on the world.
+
+To see the map, you have to select "Topo map" in the "Shown map type"
+field and perhaps unselect "Street map".
+
+MAP OF THE WORLD
+================
+
+GpsDrive >=2.08 includes now the file top_GPSWORLD.jpg which is
+shown if you use GpsDrive the first time and no maps are downloaded
+yet.
+
+To use this map at a later time, copy it into your maps directory,
+
+RENAME it i.e to top_world.jpg
+and add this entry to your map_koord.txt file:
+
+top_world.jpg 0.00000 0.00000 88226037
+
+or for german locale (and all that have a koma as decimal point):
+top_world.jpg 0,00000 0,00000 88226037
+
+
+From the map source:
+====================
+
+You find the project page at
+http://earthobservatory.nasa.gov/Newsroom/BlueMarble/
+
+When using these datasets please give credits to:
+-------------------------------------------------
+Author: 
+Reto Stöckli, NASA/Goddard Space Flight Center, stockli@cyberlink.ch
+
+Address of correspondance:
+Reto Stöckli                    Phone:  +41 (0)1 271 8463
+NASA GSFC/ SSAI                 Email:  stockli@cyberlink.ch
+Landenbergstr. 16a              Web:    http://visibleearth.nasa.gov
+8037 Zürich Switzerland                 http://earthobservatory.nasa.gov
+
+Supervisors: 
+Fritz Hasler and David Herring, NASA/Goddard Space Flight Center
+
+Funding:
+This project was realized under the SSAI subcontract 2101-01-027 (NAS5-01070)
+
+
+last modification: 01/31/2004
diff --git a/Documentation/TODO b/Documentation/TODO
new file mode 100644
index 0000000..75b8735
--- /dev/null
+++ b/Documentation/TODO
@@ -0,0 +1,252 @@
+This is a (definitely incomplete) list of features/improvements for gpsdrive.
+This file helps us keep track of what can be done and who is interested in doing it.
+Everyone is invited to catch one of the tasks and start development.
+
+Currently Worked on for Release gpsdrive-2.10pre4:
+--------------------------------------------------
+- Vektor Maps with Mapnik and Data from OSM
+   - Integration of lib-mapnik (loom)
+   - Creating osm-data-mapnik debian Package (tweety)
+   - remove QT-Dependency
+- POI Management (D.S.E)
+   - POI GUI
+- GUI
+   - Make the Mapwindow resizable (maybe) (D.S.E)
+- Cleaning Up the debian package Content
+
+
+
+Ideas for gpsdrive improvement: (unassigned, unrated)
+-----------------------------------------------------
+- Documentation:
+    - writing lots of useful comments to the existing code.
+	- Writing/improving man Pages
+	- Translate man Pages
+	- Translate in Programm Text (translate in the po/*.po Files)
+    - writing and correcting text for the FAQ/man pages
+    - Better "hacking" documentation (e.g. documentation describing how to generate
+      a "GPSDrive-compliant" raster map from outside of GPSDrive, clear
+      documentation on the size and shape of custom icons, etc.).
+	- Help translate the gettext strings (po-Files) in to your native language
+
+- Makefiles/Distribution:
+	- include generation of icon Directory while installing gpsdrive
+	- update the distribution dependant Files (debian, suse, ...)
+
+- Modularising:
+	- Put every drawing layer into a seperate sourcefile.
+	- moving configuration Data into a structure (already started)
+	- moving actual settings into another structure (already started)
+	- move more stuff from gpsdrive.c into meaningful standalone Files
+		examples:
+		- poi.{c,h}
+		- gps_handling.{c.h}
+		- icons.{c.h}
+
+- Autosave Tracks periodically
+	- started: savetrack was seperated and got 
+	  option to save only aktual Track an not track_ALL.sav
+
+- Finding and correcting Bugs in the existing Code.
+
+- make the code more error resistant
+
+- Changing User Interface:
+	- move to setup menu:
+		save Track
+
+	- move to pulldown menu:
+		Start gpsd 
+		Download Map
+	- rewrite the UI using glade-2 (see above)
+	- include POI-Management
+
+- Point and measure Mode: Show the lat/lon of a point you clicked on. 
+  Click an another point and then show the distance between those two points.
+
+- write routines to import gps Tracks into the Database. The difficulty 
+  here is to classify the Data and find corresponding tracks and merge 
+  them together. Also to find gaps in the tracks and split them at 
+  this point.
+
+- make gpsdrive compile inside eclipse.
+  should work
+
+- refactor the variable names inside gpsdrive.
+
+- write an interface to use functions like gpsbabel gpstrans from inside
+  gpsdrive.
+
+- Move part of the user interface to a Pulldown menu.
+
+- write track data in smaller steps (every point comming from gps). This 
+  would enable us to use these tracks as a data Pool for gernerating our 
+  own vector maps
+
+- add an Mode for Displaying position under the cursor and measure distances
+
+- add support for moving the map with the cursor keys if in POS-Mode
+
+- Correct/complete/add-new translations in the po Files
+
+- Writing code for the handling the POI(Point Of Interest) Data 
+  inside the Database.
+     - this would be searching an point of interest in 
+       the Database and displaying it on the map
+     - having an interface to select what kind of POIs to 
+       display at the moment
+
+- Store poi-type-specific information in a separate poi_extra table
+  (e.g. macaddr, wep, etc. for wlan entries; classification, features, pricing,
+  rooms, etc. for hotels, etc.).
+  GPSDrive would only need to access the basic data in the core poi table for
+  search and display of pois, but when a poi is clicked, the additional data
+  can be displayed formatted in a (pop-up) window.
+  Also external programs could make use of the extra data.
+
+- Make it work with MySQL 4.1 (afore mentioned "select(): bad file descriptor" 
+  problem, plus see below).
+
+- Devise a "standard" set of tables for OpenGIS data (lines, polygons, etc) 
+  which can be drawn atop the existing raster maps if desired (or used to
+  populate a "blank" raster map.)  Someone could work up an import routine
+  from the US Census Bureau "TIGER/Line[1]" data, import from Shapefiles, etc.
+  [1] http://www.census.gov/geo/www/tiger/tiger2003/tgr2003.html  There's
+	  actually supposed to be a new release of this data sometime this month as
+ 	  well.  I personally have a sloppily-done but functional script that generates
+	  GPSDrive raster maps by rendering TIGER/Line "Type 1" (roads) data atop
+	  the satellite photo data at various scales.  I'll share it with anyone
+	  that wants it, if they promise not to laugh in my face at my really slovenly
+	  code.
+
+- Split the database backend out into "plugins" so that users of mapd
+  or people who just passionately hate MySQL for whatever reason can use
+  PostGRES instead (or maybe Oracle if they're wealthy).  (Presumably a bigger
+  challenge, but I think it'd be worthwhile, even if MySQL is plenty for my own
+  uses...)
+
+- Have the database fetch waypoints in order from nearest waypoint to current
+  location to furthest, and add a configurable limit to the number retrieved - 
+  should lighten the load on GPSDrive considerably for those of us with huge
+  waypoints tables... (I can supply a very crude patch for this, with a 
+  hard-coded limit of total waypoints fetched at any one time.  It has worked
+  fine for me and is a very small change to GPSDrive, but isn't very elegant).
+  I've been importing USGS GNIS data[2] as waypoints, so even with just a few
+  states worth of waypoints it's easy to end up with hundreds of thousands of
+  them.
+  [2] http://geonames.usgs.gov/geonames/stategaz/index.html  I have a script 
+	  to import these into GPSDrive's waypoint table (as modified by myself - see
+	  the suggestion about added fields...), and a start on custom waypoint icons
+	  for a few of the types.  Eventually I hope to have waypoint icons for all of
+	  them.  I'll share these if anyone wants them, too.  Note that the GNIS also
+	  has a link to "Foreign" (relative to the U.S.) names: I haven't looked too
+	  deeply into these yet, but the files do have a different structure than the
+	  GNIS datafiles last time I looked.  However, they should be pretty easy to
+	  reconcile with the GNIS waypoint types and write an import script for.  That's
+	  on my "to do" list sometime soon, and would give non-U.S. people a possibly
+	  useful source for some geographic waypoints.
+
+- Remove fetching of expedia maps (however, see below).  The terms of use 
+  for the expedia map servers appear to explicitly forbid what we do with
+  GPSDrive, and I'm a bit uncomfortable with what amounts to a "break the law" 
+  button built into the program...(see, told you at least one idea would
+  be downright blasphemous...)
+
+- HOWEVER...split map fetching out into external programs.  Even simply having
+  a field in the configuration to supply program names which get run (with 
+  environment variables for lat, lon, altitude, etc. set appropriately by
+  GPSDrive when it calls them.)  Anyone with the time, talent, and inclination
+  to do so can then easily contribute independent "fetch a map" programs for
+  various purposes, in whatever programming language they prefer, without
+  needing to mess with the core of GPSDrive itself.  No doubt some horrible, 
+  horrible person would make an expedia download program to replace the 
+  "built-in" function and thus allow people to commit the terrible sin of 
+  robbing Bill Gates of an uncountably-small fraction of a penny of profit by
+  downloading maps without permission once again, but what can you do? :-)
+
+- Increase the possible size of the waypoint labels on the map (minor cosmetic
+  issue, I just keep running into placenames that get cut off because they're
+  too long).
+
+
+- Make it easier to find waypoints that are not currently within the range
+  specified in preferences (i.e. if one is travelling a long way and wants to 
+  find and select the destination, while the range is set fairly low because 
+  there are a lot of waypoints in the area...)
+
+- ADD SUPPORT FOR UTM PROJECTION MAPS!  Possibly remove the "street" and "topo"
+  distinctions and instead have selections for UTM, ORTHO(?), and LATLON,
+  perhaps?
+  I've been trying for some time now to find out what projection the
+  Expedia(tm) maps are in, so that I can use gdalwarp to convert UTM maps
+  that will work correctly as "street"-type maps, but nobody seems to know.
+  Best guess I've heard so far is that they are an "Orthographic" projection.
+
+- Improve Kismet connection robustness.  GPSDrive still locks up for me
+  if Kismet dies while GPSDrive is connected to it.  Even better, add a
+  "check for Kismet" button and allow GPSDrive to connect to Kismet
+  AFTER being started - or to re-connect if Kismet gets stopped and restarted.
+
+- A function to overlay raster data atop the existing displayed map - for 
+  example if I find a way to fetch weather radar data while driving around, 
+  maybe I could have GPSDrive draw the weather activity atop the current
+  map, so I can tell if I'm going to outrun the storm...
+
+- Implement direct GPX support
+  - replace way.txt by way.gpx (or remove this file completely)
+  - support import of POIs/Waypoints in gpx format
+  - support also import/export of tracks and routes in gpx format
+
+-----------------------------------------------------------------------------
+D.S.E <d.s.e@sordidmusic.com>
+
+my personal TODO-List (for after the pre4 release) :-)
+
+- extend (poi-)databases to handle additional information for POIs.
+- add navigation mode (optimized gui for small car touchscreens)
+- make displayed map draggable with mouse
+
+-----------------------------------------------------------------------------
+Koji <koji@e-mail.jp>
+
+- making 2.10pre2's ja.po. 
+
+- Tokyo maps:
+  This URL contain the position (deg/mm/ss), map scale(1/7000) and 
+  map size(1280x1024). And a lot of scales can be obtained.
+  This is very convenient for me. :-) Only one probrem is not WGS84 position,
+  this positioning is named "Tokyo". So I need excange the position. :-(
+
+  http://www.mapion.co.jp/c/f?el=139/36/45.600&scl=70000&size=1280,1024&uc=1&grp=MapionBB&nl=35/31/36.300
+
+
+-----------------------------------------------------------------------------
+Rob Stewart <rob@groupboard.com>
+
+I've already looked at the festival speech stuff and I think I could 
+make a change for the better there. However, the biggest thing I would 
+suggest is setting a good coding standard, I think what currently exists 
+is a little scary! Here's my top suggestions...
+
+
+-----------------------------------------------------------------------------
+
+Old (has to be checked):
+------------------------
+
+Command line switch to set gpsd hostname and port for remote control.
+
+Add load of trackings (i.e. stored in the GPS and
+converted with a nice perl script anyone will write).
+
+Servermode to display different positions provided over Internet
+server.
+
+resizing of window
+centering of map to selected points
+
+render maps in greyscale
+
+create ~/.gpsdrive directory and files if missing.
+
+