| 1 |
\ |
| 2 |
.\" This man page was generated by the Netpbm tool 'makeman' from HTML source. |
| 3 |
.\" Do not hand-hack it! If you have bug fixes or improvements, please find |
| 4 |
.\" the corresponding HTML page on the Netpbm website, generate a patch |
| 5 |
.\" against that, and send it to the Netpbm maintainer. |
| 6 |
.TH "Pamtosrf User Manual" 1 "27 May 2011" "netpbm documentation" |
| 7 |
|
| 8 |
.SH NAME |
| 9 |
pamtosrf - convert a sequence of Netpbm images to a SRF image file |
| 10 |
|
| 11 |
|
| 12 |
.UN synopsis |
| 13 |
.SH SYNOPSIS |
| 14 |
.PP |
| 15 |
\fBpamtosrf\fP |
| 16 |
[\fB-verbose\fP] |
| 17 |
[\fInetpbmfile\fP] |
| 18 |
|
| 19 |
|
| 20 |
.UN description |
| 21 |
.SH DESCRIPTION |
| 22 |
.PP |
| 23 |
This program is part of |
| 24 |
.BR "Netpbm" (1)\c |
| 25 |
\&. |
| 26 |
.PP |
| 27 |
\fBpamtosrf\fP reads a Netpbm image stream as input and produces a |
| 28 |
an SRF image file as output. I don't know exactly what SRF is, but on popular |
| 29 |
use of it is in Garmin vehicle information files, which tell a GPS receiver |
| 30 |
how to depict a vehicle on its display. |
| 31 |
.PP |
| 32 |
An SRF file can contain multiple images; each image in a multi-image |
| 33 |
Netpbm input stream becomes one image in the SRF. |
| 34 |
.PP |
| 35 |
\fBpamtosrf\fP does not care how many images there are or what their |
| 36 |
dimensions or content are. However, a Garmin vehicle information file has |
| 37 |
specific requirements, so if you don't make your Netpbm input conform, neither |
| 38 |
will your SRF output. For such a file, you should have two image: the first |
| 39 |
for 3D oblique views of the vehicle and the second for overhead views. Each |
| 40 |
image is a horizontal concatenation of 36 square images, each rotated 10 |
| 41 |
degrees from the previous, thereby covering the full 360 degree circle. |
| 42 |
You could create this concatenation with \fBpamcat -lr\fP and you could |
| 43 |
create the individual views with \fBpnmrotate\fP. |
| 44 |
.PP |
| 45 |
One way to use \fBpamtosrf\fP is to get an SRF file, convert it to PAM |
| 46 |
with \fBsrftopam\fP, manipulate it, then convert it back with |
| 47 |
\fBpamtosrf\fP. |
| 48 |
.PP |
| 49 |
\fInetpbmfile\fP is the input stream, which defaults to Standard Input. |
| 50 |
Output is always on Standard Output. |
| 51 |
|
| 52 |
|
| 53 |
.UN options |
| 54 |
.SH OPTIONS |
| 55 |
.PP |
| 56 |
In addition to the options common to all programs based on libnetpbm |
| 57 |
(most notably \fB-quiet\fP, see |
| 58 |
.UR index.html#commonoptions |
| 59 |
Common Options |
| 60 |
.UE |
| 61 |
\&), \fBpamtosrf\fP recognizes the following |
| 62 |
command line option: |
| 63 |
|
| 64 |
|
| 65 |
.TP |
| 66 |
\fB-verbose\fP |
| 67 |
Issue informational messages about the input and the conversion process. |
| 68 |
|
| 69 |
|
| 70 |
|
| 71 |
|
| 72 |
.UN seealso |
| 73 |
.SH SEE ALSO |
| 74 |
|
| 75 |
|
| 76 |
.IP \(bu |
| 77 |
.BR "srftopam" (1)\c |
| 78 |
\& |
| 79 |
.IP \(bu |
| 80 |
.BR "pamcat" (1)\c |
| 81 |
\& |
| 82 |
.IP \(bu |
| 83 |
.BR "pam" (1)\c |
| 84 |
\& |
| 85 |
|
| 86 |
|
| 87 |
.UN history |
| 88 |
.SH HISTORY |
| 89 |
.PP |
| 90 |
\fBsrftopam\fP was new in Netpbm 10.55 (June 2011). |
| 91 |
.PP |
| 92 |
It was contributed by Mike Frysinger. |
| 93 |
.SH DOCUMENT SOURCE |
| 94 |
This manual page was generated by the Netpbm tool 'makeman' from HTML |
| 95 |
source. The master documentation is at |
| 96 |
.IP |
| 97 |
.B http://netpbm.sourceforge.net/doc/pamtosrf.html |
| 98 |
.PP |