This file is indexed.

/usr/share/doc/grass-doc/html/d.out.gpsdrive.html is in grass-doc 6.4.3-3.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>GRASS GIS manual: d.out.gpsdrive</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link rel="stylesheet" href="grassdocs.css" type="text/css">
</head>
<body bgcolor="white">

<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>

<h2>NAME</h2>
<em><b>d.out.gpsdrive</b></em>  - Export display monitor to a GpsDrive compatible backdrop image
<h2>KEYWORDS</h2>
display, export, GPS
<h2>SYNOPSIS</h2>
<b>d.out.gpsdrive</b><br>
<b>d.out.gpsdrive help</b><br>
<b>d.out.gpsdrive</b> [-<b>j</b>] <b>output</b>=<em>string</em>  [--<b>verbose</b>]  [--<b>quiet</b>] 

<h3>Flags:</h3>
<DL>
<DT><b>-j</b></DT>
<DD>Make JPEG instead of PNG image</DD>

<DT><b>--verbose</b></DT>
<DD>Verbose module output</DD>
<DT><b>--quiet</b></DT>
<DD>Quiet module output</DD>
</DL>

<h3>Parameters:</h3>
<DL>
<DT><b>output</b>=<em>string</em></DT>
<DD>name for new map image (lives in ~/.gpsdrive/maps/)</DD>

</DL>
<h2>DESCRIPTION</h2>

<em>d.out.gpsdrive</em> exports the current GRASS display monitor to a 
<a href="http://www.gpsdrive.de">GpsDrive</a> compatible backdrop 
image and updates the GpsDrive image list with the appropriate geo-referencing
information.

<p>
<b><em>Use at your own risk. Do not use as a primary means of navigation.
This software comes with absolutely no warranty.</em></b>


<p>
<h2>NOTES</h2>

Maps are saved in the user's <tt>~/.gpsdrive/maps/</tt> directory.
Geo-referencing information is added to the user's
<tt>~/.gpsdrive/maps/map_koord.txt</tt> file.

<p>
JPEG output requires the <tt>pngtopnm</tt> and <tt>pnmtojpeg</tt> programs
from the <a href="http://netpbm.sourceforge.net">NetPBM tools</a>.

<p>
GpsDrive assumes northings are not rotated compared to true-geographic north.
If you are using a projection with significant curvature away from the central
meridian, or a map datum with a significant rotational component, then you will 
likely end up with a distorted or inexact background map!
Keeping the area small will lessen the error, but not eliminate it, if
necessary you could reproject the map into a custom projection (such as tmerc)
centered directly on the center of your map. You can check the local
convergence angle (difference between grid north and true north) with
"<tt>g.region -n</tt>".
<p>
To avoid distortion, anything more global than 1:150k to 1:500k
should come from a lat/lon location. Anything more local than that
will look better coming from a projected system such as UTM.
<p>
The extent of a map given a target scale can be calculated with 
<tt>x_ext=scale*(1280/2817.95)</tt>. e.g. 1:50,000 translates to approx
a 22.7km x 18.2km image window in the GIS.
<p>
For your convenience (calculations are rough, but nominal):
<div class="code"><pre>
1:50,000 uses a region 22.7km x 18.2km.
1:75,000 uses a region 34.1km x 27.3km.
1:100,000 uses a region  45.4km x 36.3km.
1:175,000 uses a region  79.5km x 63.6km.
</pre></div>
<br>


Maps exported from lat-lon locations will be given a "<tt>top_</tt>" prefix.
Maps exported from locations of other projections will be given a 
"<tt>map_</tt>" prefix. This is done so GpsDrive knows how to scale the 
image correctly.
<p>
GpsDrive requires backdrop images to be 1280x1024 pixels in size. While this
script takes care of that automatically, to avoid annoying bands on the sides
of your image you may want to set up your display monitor at half-scale (same
aspect ratio) and use d.zoom to select the full frame. For example:
<p>
<div class="code"><pre>
export GRASS_WIDTH=640
export GRASS_HEIGHT=512
d.mon x0
</pre></div>

<br>
Map scaling is set from the region settings so should work correctly even 
when the display's aspect ratio does not match that of the output image.


<h3>Batch export</h3>

It may be desirable to create a series of image tiles covering a large area.
An easy way to do this is to run <em>d.out.gpsdrive</em> in a shell loop.
Here is an example Bash script contributed by Manuel Morales:
<p>
<div class="code"><pre>
#!/bin/bash

# map scale is determined by "panels" by dividing the N-S
# region extent into that number of maps. Note that the
# generated maps overlap by 1/2 along the N-S axis and by
# approximately 1/2 along the E-W axis.
panels=3
iter=$((panels*2-1))

eval `g.region -eg`
eval `g.region -g`
north=$n
south=$s
west=$w
east=$e

unit_ns=$(echo "scale=8; $ns_extent / $panels" | bc)
unit_ew=$(echo "scale=8; $unit_ns * 4/3" | bc)

panels_ew=$(echo "((2*$ew_extent / $unit_ew +.5 ) -1) / 1" | bc)

for i in `seq 1 $panels_ew`;
do
  east=$(echo "scale=8; $west+$unit_ew" | bc)
  for j in `seq 1 $iter`;
    do
    g.region n=$(echo "scale=8; $north-($j-1) * $unit_ns/2" | bc)      \
        s=$(echo "scale=8; $north-($j-1) * $unit_ns/2-$unit_ns" | bc ) \
        w=$west e=$east ewres=$ewres nsres=$nsres
        d.redraw
        d.out.gpsdrive -j tile_${i}_${j}
    done
  shift_west=$(echo "scale=8; ($ew_extent-$unit_ew)/($panels_ew-1)" | bc)
  west=$(echo "scale=8; $west+$shift_west" | bc)
done
</pre></div>

<br>
Note that to get a smoother transition between backdrop maps this script
creates overlapping tiles. For best results at least 1/3rd overlap should
be maintained.


<br><br>
<h2>SEE ALSO</h2>

<em><a href="d.info.html">d.info</a></em>,
<em><a href="d.grid.html">d.grid</a></em>,
<em><a href="d.out.file.html">d.out.file</a></em>,
<em><a href="d.out.png.html">d.out.png</a></em>,
<em><a href="d.save.html">d.save</a></em>,
<em><a href="g.region.html">g.region</a></em>,
<em><a href="v.in.garmin.html">v.in.garmin</a></em>
<br><br>
The GRASS <a href="pngdriver.html">PNG driver</a><br>

The <a href="http://www.gpsdrive.de">GpsDrive</a> project<br>
The <a href="http://gpsd.berlios.de">gpsd</a> personal GPS server project
<br><br>

<h2>AUTHOR</h2>
Hamish Bowman<br> <i>
Department of Marine Science<br>
University of Otago<br>
New Zealand</i><br>
<br>

<p>
<i>Last changed: $Date: 2011-11-08 03:29:50 -0800 (Tue, 08 Nov 2011) $</i>
<HR>
<P><a href="index.html">Main index</a> - <a href="display.html">display index</a> - <a href="full_index.html">Full index</a></P>
<P>&copy; 2003-2013 <a href="http://grass.osgeo.org">GRASS Development Team</a></p>
</body>
</html>