
GPS-
Ba-
bel
XCSV
Style
Files
107
LAT_HUMAN_READABLE
LAT_HUMAN_READABLE defines LATITUDE in a human-readable format. This format is probably
the most expressive format. It is similar to LAT_DECIMALDIR in that it requires multiple printf conver-
sions, but it is far more flexible as to the contents of those conversions. On read, the printf conversions are
ignored and GPSBabel attempts to determine the latitude and longitude based on what is in the file.
examples:
# (writes N 31 40.000)
IFIELD LAT_HUMAN_READABLE,"","%c %d %f"
# (writes "31 deg 40.000 min N")
IFIELD LAT_HUMAN_READABLE,"","%d deg %f min %c"
# Note that this string will confuse the reading routine due
# to the letter "n" in "min" and the letter "e" in "deg."
# (writes 31 40 00.000N)
IFIELD LAT_HUMAN_READABLE,"","%d %d %f%c"
MAP_EN_BNG
MAP_EN_BNG converts coordinates from/to British National Grid (BNG).
The only supported order of the items is: Map,Easting,Northing. During output all coordinates have to be
located within this limited area.
examples:
IFIELD MAP_EN_BNG,"","%s%5d %5d" # (writes i.e. "SJ00001 00001")
IFIELD MAP_EN_BNG,"","%s %d %d" # (writes i.e. "TQ 888 999")
LON_HUMAN_READABLE
See LAT_HUMAN_READABLE except LON_HUMAN_READABLE defines LONGITUDE.
LATLON_HUMAN_READABLE
LATLON_HUMAN_READABLE is like LAT_HUMAN_READABLE and
LON_HUMAN_READABLE except that it reads and writes both latitude and longitude as a single field.
On write, the same format specifier is used for both coordinates. On read, GPSBabel does exactly the same
thing it does for LAT_HUMAN_READABLE or LON_HUMAN_READABLE.
example:
IFIELD LATLON_HUMAN_READABLE,"","%c %d %f"
# (writes "N 31 40.126 W 85 09.62" as a single field)
LAT_NMEA
Defines the latitude in the format used by the NMEA standard which is degrees multiplied by 100 plus
decimal minutes.
example:
Kommentare zu diesen Handbüchern