[DebianGIS-dev] r1721 - packages/mkgmap/trunk/debian

[nd-guest at alioth.debian.org]

Author: nd-guest
Date: 2008-07-14 13:52:33 +0000 (Mon, 14 Jul 2008)
New Revision: 1721

Removed:
   packages/mkgmap/trunk/debian/mkgmap.1
Modified:
   packages/mkgmap/trunk/debian/manpages
Log:
manpage included upstream.


Modified: packages/mkgmap/trunk/debian/manpages
===================================================================
--- packages/mkgmap/trunk/debian/manpages	2008-07-13 20:26:04 UTC (rev 1720)
+++ packages/mkgmap/trunk/debian/manpages	2008-07-14 13:52:33 UTC (rev 1721)
@@ -1 +1 @@
-debian/mkgmap.1
+doc/mkgmap.1

Deleted: packages/mkgmap/trunk/debian/mkgmap.1
===================================================================
--- packages/mkgmap/trunk/debian/mkgmap.1	2008-07-13 20:26:04 UTC (rev 1720)
+++ packages/mkgmap/trunk/debian/mkgmap.1	2008-07-14 13:52:33 UTC (rev 1721)
@@ -1,138 +0,0 @@
-.TH MKGMAP 1 "April 13, 2008"
-.\" Please adjust this date whenever revising the manpage.
-.SH NAME
-mkgmap \- Generate Garmin maps from OpenStreetMap data
-.SH SYNOPSIS
-.B mkgmap
-.RI [ options ] " files.osm " ...
-.SH DESCRIPTION
-This manual page documents briefly the
-.B mkgmap
-command.
-.PP
-\fBmkgmap\fP is a program that converts OpenStreetMap (OSM) data into a map that can be loaded onto 
-a Garmin GPS device. 
-.br
-The mapping between OSM features and the features in the map can be customized with a file.
-.SH OPTIONS
-.TP
-.B \-c <filename>
-The given file is opened and each line is an option setting of the form
-option=value, just like on the command line except that there is no leading '--'.
-.TP
-.B \-n, \-\-mapname=name
-Change the name of the map. Garmin maps are named by 8 digit numbers.
-The default ist 63240001. It is best to change the name if you are going 
-to be making a map for others to use so that it is unique and does not
-clash with others.
-.TP
-.B \-\-description=text
-Sets the descriptive text for the map. This may be displayed in 
-QLandkarte, MapSource or on a GPS etc.
-.TP
-.B \-\-map-features=file
-Use your own map features file. You can totally change which features
-are shown and at what levels. See 
-.SM 
-.B CUSTOMISING THE MAP
-below.
-.TP
-.B \-\-levels=levels code
-Change the way that the levels on the map correspond to the zoom levels
-in the device. See 
-.SM
-.B CUSTOMISING THE MAP
-below. The default is the equivalent of: "0=24, 1=22, 2=21, 3=19, 4=18, 5=16" although this may change.
-.TP
-.B \-\-latin1
-This option allows the use of non-ascii characters in street names. It 
-is hardware dependant what is actually supported on a particular
-device. Some devices can only do ascii characters for example.
-.br
-Mkgmap goes to some length to convert un-displayable characters however. It
-will convert accented characters that cannot be displayed in the chosen
-character set into unaccented characters.
-.SH CUSTOMISING THE MAP
-You can completely change which features are displayed and at what zoom levels.
-.PP
-There are two concepts 'resolution' and 'level'.
-.PP
-.SS Resolution
-is a number between 1 and 24 with 24 being the most detailed resolution and each number
-less is half as detailed.
-.br
-So for example if a road was 12 units long at resolution 24 it would be only 6 at resolution
-23 and just 3 at resolution 22.
-.br
-On a Garmin Legend Cx the resolution corresponds to these scales on the device:
-.RS
-16 30km-12km
-.br
-18 8km-3km
-.br
-20 2km-800m
-.br
-22 500m-200m
-.br
-23 300m-80m
-.br
-24 120m-50m
-.RE
-.br
-It may be slightly different on different devices.
-.SS Level
-.br
-is a number between 0 and 16 (although perhaps numbers above 10 are not usable), with
-0 corresponding to the most detailed view. The map consists of a number of levels starting
-(usually) with 0. For example 0, 1, 2, 3 and a different amount of detail is added 
-at each level.
-.br
-The map also contains a table to link the level to the resolution. So you can say
-that level 0 corresponds to resolution 24.
-.br
-You can specify this mapping on the command line, for example:
-.RS
-\-\-levels=0:24,1:22,2:20
-.RE
-This means that the map will have three levels. Level 0 in the map will
-correspond to resolution 24 (the most detailed), level 1 will show at
-resolution 22 (between scales of 500m and 200m) and so on.
-.SS Map features
-Custom map features can be applied using a delimeted file among with 
-the 
-.IR --map-features
-command line option.
-.br
-A typical line may look like this:
-.RS
-.PP
-point|amenity|grave_yard|0x64|0x03|23
-.RE
-.PP
-Column 1 is point, polyline or polygon, depending on whether the feature is a point of interest, 
-a line feature such as a road or an area such as a park.
-.br
-Column 2 and 3 are taken exactly from the key and value columns from the OSM map features.
-.br
-Column 4 is the garmin code that you want to use.
-.br
-Column 5 only applies to points and also determines the type of the object.
-.br
-Column 6 is the minimum resolution at which this feature will appear.
-.PP
-The file 
-.IR /usr/share/doc/mkgmap/garmin_features_list.csv
-has a list of known type values used by Garmin.
-
-.SH ACKNOWLEDGEMENTS
-This project is almost entirely based on the file format specification
-document written by John Mechalas at the SourceForge project at
-http://sourceforge.net/projects/garmin-img.
-.SH SEE ALSO
-.BR josm (1),
-.BR qlandkarte (1).
-.SH AUTHOR
-mkgmap was written by Steve Ratcliffe <sr at parabola.me.uk>.
-.PP
-This manual page was written by Andreas Putzo <andreas at putzo.net>,
-for the Debian project (but may be used by others).