Visit The New, Modern Unix Linux Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #140
Difficulty: Easy
Unix and the C programming language were both developed at AT&T.
True or False?
Linux & Unix Commands - Search Man Pages

gpspipe(1) [debian man page]

GPSPIPE(1)							GPSD Documentation							GPSPIPE(1)

NAME
gpspipe - tool to connect to gpsd and retrieve sentences SYNOPSIS
gpspipe [-h] [-d] [-l] [-o filename] [-n count] [-r] [-R] [-s serial-device] [-t] [-T timestamp-format] [-p] [-w] [-v] [-D debug-level] [server [:port [:device]]] DESCRIPTION
gpspipe is a tool to connect to gpsd and output the received sentences to stdout. This makes the program useful as a pipe from gpsd to another program or file. gpspipe does not require root privileges, and can be run concurrently with other tools connecting to the local gpsd without causing problems. The output will consist of one or both of the raw NMEA or native gpsd sentences. Each line can be optionally time stamped. There is also an option to exit gracefully after a given count of packets. Optionally a server, TCP/IP port number and remote device can be given. If omitted, gpspipe connects to localhost on the default port (2947) and watches all devices opened by gpsd. gpspipe may be run as a daemon, but requires the -o flag for writing the output to a file. OPTIONS
-h makes gpspipe print a usage message and exit. -d causes gpspipe to run as a daemon. -l causes gpspipe to sleep for ten seconds before attempting to connect to gpsd. This is very useful when running as a daemon, giving gpsd time to start before attempting a connection. -r causes raw NMEA sentences to be output. -R causes super-raw (gps binary) data to be output. This overrides NMEA and gpsd output modes. -s option causes the collected data to be written to the specified serial device with settings 4800 8N1. Thus gpspipe can be used with -s and -r options to emulate a serial port hardwired to a GPS that gpsd is managing. -o option causes the collected data to be written to the specified file. Use of this option is mandatory if gpspipe is run as a daemon. -w causes native gpsdsentences to be output. -t adds a timestamp to each sentence output. -T sets the format of the timestamp. See strftime(3) for the available placeholders. Setting this option implies -t. -p enables dumping of profiling information in JSON. -n [count] causes [count] sentences to be output. gpspipe will then exit gracefully. -v causes gpspipe to show a spinning activity indicator on stderr. This is useful if stdout is redirected into a file or a pipe. By default the spinner is advanced with every messages written; specifying -v more than once will double the number of messages required to rotate the spinner. -V prints the version, then exits. At least one of -R, -r or -w must be specified. EXAMPLE
When gpsd is running gpspipe -r -n 100 will send one hundred raw NMEA sentences to standard output, then exit. SEE ALSO
gpsd(8), gps(1), libgps(3), libgpsd(3), gpsprof(1), gpsfake(1), gpsctl(1), gpscat(1). gpsmon(1). AUTHOR
Gary E. Miller gem@rellim.com. The GPSD Project 03 Aug 2005 GPSPIPE(1)

Check Out this Related Man Page

GPSDECODE(1)							GPSD Documentation						      GPSDECODE(1)

NAME
gpsdecode - decode GPS, RTCM or AIS streams into a readable format SYNOPSIS
gpsdecode [-c] [-d] [-e] [-j] [-t typelist] [-u] [-v] [-D debuglevel] [-V] DESCRIPTION
This tool is a batch-mode decoder for NMEA and various binary packet formats associated with GPS, AIS, and differential-correction services. It produces a JSON dump on standard output from binary on standard input. The JSON is the same format documented in gpsd(8); this tool uses the same decoding logic as gpsd, but with a simpler interface intended for batch processing of data files. All sensor-input formats known to the GPSD project can be decoded by this tool. These include: NMEA, AIVDM (the NMEA-derived sentence format used by AIS, the marine Automatic Identification System), RTCM2, and all supported GPS binary formats (notably including SiRF). See gpsd(8) for applicable standards and known limitations of the decoding logic. You can use this tool with nc(1) to examine AIS feeds from AIS pooling services, RTCM feeds from RTCM receivers or NTRIP broadcasters. OPTIONS
The -d option tells the program to decode packets presented on standard input to standard output. This is the default behavior. The -j explicitly sets the output dump format to JSON (the default behavior). The -e option option tells the program to encode JSON on standard input to JSON on standard output. This option is only useful for regression-testing of the JSON dumping and parsing code. The -t accepts a comma-separated list of numeric types. Packets with a numeric AIS, RTCM2, or RTCM3 type are passed through and output only if they match a type in the list. Packets of other kinds (in particular GPS packets) are passed through unconditionally. The -u suppresses scaling of AIS data to float quantities and text expansion of numeric codes. A dump with this option is lossless. The -v enables dumping of textual packets to output as they are received on input, immediately preceding corresponding output. The -c sets the AIS dump format to separate fields with an ASCII pipe symbol. Fields are dumped in the order they occur in the AIS packet. Numerics are not scaled (-u is forced). Strings are unpacked from six-bit to full ASCII The -V option directs the program to emit its version number, then exit. The -D option sets a debug verbosity level. It is mainly of interest to developers. AIS DSV FORMAT
With the -c option, dump lines are values of AIS payload fields, pipe-separated, in the order that they occur in the payload. Spans of fields expressing a date are emitted as an ISO8601 timestamp (look for colons and the trailing Z indicating Zulu/UTC time), and the 19-bit group of TDMA status fields found at the end of message types 1-4 are are dumped as a single unsigned integer (in hex preceded by "0x"). Unused regional-authority fields are also dumped (in hex preceded by "0x"). Variable-length binary fields are dumped as an integer bit length, followed by a colon, followed by a hex dump. SEE ALSO
gpsd(8), gpsctl(1), gpsdctl(8), gps(1), libgps(3), libgpsd(3), gpsprof(1), gpsfake(1), AUTHOR
Eric S. Raymond esr@thyrsus.com. The GPSD Project 13 Jul 2005 GPSDECODE(1)

Featured Tech Videos