This file is indexed.

/usr/share/doc/gpsbabel/gpsbabel.html is in gpsbabel-doc 1.5.0-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
 192
 193
 194
 195
 196
 197
 198
 199
 200
 201
 202
 203
 204
 205
 206
 207
 208
 209
 210
 211
 212
 213
 214
 215
 216
 217
 218
 219
 220
 221
 222
 223
 224
 225
 226
 227
 228
 229
 230
 231
 232
 233
 234
 235
 236
 237
 238
 239
 240
 241
 242
 243
 244
 245
 246
 247
 248
 249
 250
 251
 252
 253
 254
 255
 256
 257
 258
 259
 260
 261
 262
 263
 264
 265
 266
 267
 268
 269
 270
 271
 272
 273
 274
 275
 276
 277
 278
 279
 280
 281
 282
 283
 284
 285
 286
 287
 288
 289
 290
 291
 292
 293
 294
 295
 296
 297
 298
 299
 300
 301
 302
 303
 304
 305
 306
 307
 308
 309
 310
 311
 312
 313
 314
 315
 316
 317
 318
 319
 320
 321
 322
 323
 324
 325
 326
 327
 328
 329
 330
 331
 332
 333
 334
 335
 336
 337
 338
 339
 340
 341
 342
 343
 344
 345
 346
 347
 348
 349
 350
 351
 352
 353
 354
 355
 356
 357
 358
 359
 360
 361
 362
 363
 364
 365
 366
 367
 368
 369
 370
 371
 372
 373
 374
 375
 376
 377
 378
 379
 380
 381
 382
 383
 384
 385
 386
 387
 388
 389
 390
 391
 392
 393
 394
 395
 396
 397
 398
 399
 400
 401
 402
 403
 404
 405
 406
 407
 408
 409
 410
 411
 412
 413
 414
 415
 416
 417
 418
 419
 420
 421
 422
 423
 424
 425
 426
 427
 428
 429
 430
 431
 432
 433
 434
 435
 436
 437
 438
 439
 440
 441
 442
 443
 444
 445
 446
 447
 448
 449
 450
 451
 452
 453
 454
 455
 456
 457
 458
 459
 460
 461
 462
 463
 464
 465
 466
 467
 468
 469
 470
 471
 472
 473
 474
 475
 476
 477
 478
 479
 480
 481
 482
 483
 484
 485
 486
 487
 488
 489
 490
 491
 492
 493
 494
 495
 496
 497
 498
 499
 500
 501
 502
 503
 504
 505
 506
 507
 508
 509
 510
 511
 512
 513
 514
 515
 516
 517
 518
 519
 520
 521
 522
 523
 524
 525
 526
 527
 528
 529
 530
 531
 532
 533
 534
 535
 536
 537
 538
 539
 540
 541
 542
 543
 544
 545
 546
 547
 548
 549
 550
 551
 552
 553
 554
 555
 556
 557
 558
 559
 560
 561
 562
 563
 564
 565
 566
 567
 568
 569
 570
 571
 572
 573
 574
 575
 576
 577
 578
 579
 580
 581
 582
 583
 584
 585
 586
 587
 588
 589
 590
 591
 592
 593
 594
 595
 596
 597
 598
 599
 600
 601
 602
 603
 604
 605
 606
 607
 608
 609
 610
 611
 612
 613
 614
 615
 616
 617
 618
 619
 620
 621
 622
 623
 624
 625
 626
 627
 628
 629
 630
 631
 632
 633
 634
 635
 636
 637
 638
 639
 640
 641
 642
 643
 644
 645
 646
 647
 648
 649
 650
 651
 652
 653
 654
 655
 656
 657
 658
 659
 660
 661
 662
 663
 664
 665
 666
 667
 668
 669
 670
 671
 672
 673
 674
 675
 676
 677
 678
 679
 680
 681
 682
 683
 684
 685
 686
 687
 688
 689
 690
 691
 692
 693
 694
 695
 696
 697
 698
 699
 700
 701
 702
 703
 704
 705
 706
 707
 708
 709
 710
 711
 712
 713
 714
 715
 716
 717
 718
 719
 720
 721
 722
 723
 724
 725
 726
 727
 728
 729
 730
 731
 732
 733
 734
 735
 736
 737
 738
 739
 740
 741
 742
 743
 744
 745
 746
 747
 748
 749
 750
 751
 752
 753
 754
 755
 756
 757
 758
 759
 760
 761
 762
 763
 764
 765
 766
 767
 768
 769
 770
 771
 772
 773
 774
 775
 776
 777
 778
 779
 780
 781
 782
 783
 784
 785
 786
 787
 788
 789
 790
 791
 792
 793
 794
 795
 796
 797
 798
 799
 800
 801
 802
 803
 804
 805
 806
 807
 808
 809
 810
 811
 812
 813
 814
 815
 816
 817
 818
 819
 820
 821
 822
 823
 824
 825
 826
 827
 828
 829
 830
 831
 832
 833
 834
 835
 836
 837
 838
 839
 840
 841
 842
 843
 844
 845
 846
 847
 848
 849
 850
 851
 852
 853
 854
 855
 856
 857
 858
 859
 860
 861
 862
 863
 864
 865
 866
 867
 868
 869
 870
 871
 872
 873
 874
 875
 876
 877
 878
 879
 880
 881
 882
 883
 884
 885
 886
 887
 888
 889
 890
 891
 892
 893
 894
 895
 896
 897
 898
 899
 900
 901
 902
 903
 904
 905
 906
 907
 908
 909
 910
 911
 912
 913
 914
 915
 916
 917
 918
 919
 920
 921
 922
 923
 924
 925
 926
 927
 928
 929
 930
 931
 932
 933
 934
 935
 936
 937
 938
 939
 940
 941
 942
 943
 944
 945
 946
 947
 948
 949
 950
 951
 952
 953
 954
 955
 956
 957
 958
 959
 960
 961
 962
 963
 964
 965
 966
 967
 968
 969
 970
 971
 972
 973
 974
 975
 976
 977
 978
 979
 980
 981
 982
 983
 984
 985
 986
 987
 988
 989
 990
 991
 992
 993
 994
 995
 996
 997
 998
 999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
4000
4001
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028
4029
4030
4031
4032
4033
4034
4035
4036
4037
4038
4039
4040
4041
4042
4043
4044
4045
4046
4047
4048
4049
4050
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
4074
4075
4076
4077
4078
4079
4080
4081
4082
4083
4084
4085
4086
4087
4088
4089
4090
4091
4092
4093
4094
4095
4096
4097
4098
4099
4100
4101
4102
4103
4104
4105
4106
4107
4108
4109
4110
4111
4112
4113
4114
4115
4116
4117
4118
4119
4120
4121
4122
4123
4124
4125
4126
4127
4128
4129
4130
4131
4132
4133
4134
4135
4136
4137
4138
4139
4140
4141
4142
4143
4144
4145
4146
4147
4148
4149
4150
4151
4152
4153
4154
4155
4156
4157
4158
4159
4160
4161
4162
4163
4164
4165
4166
4167
4168
4169
4170
4171
4172
4173
4174
4175
4176
4177
4178
4179
4180
4181
4182
4183
4184
4185
4186
4187
4188
4189
4190
4191
4192
4193
4194
4195
4196
4197
4198
4199
4200
4201
4202
4203
4204
4205
4206
4207
4208
4209
4210
4211
4212
4213
4214
4215
4216
4217
4218
4219
4220
4221
4222
4223
4224
4225
4226
4227
4228
4229
4230
4231
4232
4233
4234
4235
4236
4237
4238
4239
4240
4241
4242
4243
4244
4245
4246
4247
4248
4249
4250
4251
4252
4253
4254
4255
4256
4257
4258
4259
4260
4261
4262
4263
4264
4265
4266
4267
4268
4269
4270
4271
4272
4273
4274
4275
4276
4277
4278
4279
4280
4281
4282
4283
4284
4285
4286
4287
4288
4289
4290
4291
4292
4293
4294
4295
4296
4297
4298
4299
4300
4301
4302
4303
4304
4305
4306
4307
4308
4309
4310
4311
4312
4313
4314
4315
4316
4317
4318
4319
4320
4321
4322
4323
4324
4325
4326
4327
4328
4329
4330
4331
4332
4333
4334
4335
4336
4337
4338
4339
4340
4341
4342
4343
4344
4345
4346
4347
4348
4349
4350
4351
4352
4353
4354
4355
4356
4357
4358
4359
4360
4361
4362
4363
4364
4365
4366
4367
4368
4369
4370
4371
4372
4373
4374
4375
4376
4377
4378
4379
4380
4381
4382
4383
4384
4385
4386
4387
4388
4389
4390
4391
4392
4393
4394
4395
4396
4397
4398
4399
4400
4401
4402
4403
4404
4405
4406
4407
4408
4409
4410
4411
4412
4413
4414
4415
4416
4417
4418
4419
4420
4421
4422
4423
4424
4425
4426
4427
4428
4429
4430
4431
4432
4433
4434
4435
4436
4437
4438
4439
4440
4441
4442
4443
4444
4445
4446
4447
4448
4449
4450
4451
4452
4453
4454
4455
4456
4457
4458
4459
4460
4461
4462
4463
4464
4465
4466
4467
4468
4469
4470
4471
4472
4473
4474
4475
4476
4477
4478
4479
4480
4481
4482
4483
4484
4485
4486
4487
4488
4489
4490
4491
4492
4493
4494
4495
4496
4497
4498
4499
4500
4501
4502
4503
4504
4505
4506
4507
4508
4509
4510
4511
4512
4513
4514
4515
4516
4517
4518
4519
4520
4521
4522
4523
4524
4525
4526
4527
4528
4529
4530
4531
4532
4533
4534
4535
4536
4537
4538
4539
4540
4541
4542
4543
4544
4545
4546
4547
4548
4549
4550
4551
4552
4553
4554
4555
4556
4557
4558
4559
4560
4561
4562
4563
4564
4565
4566
4567
4568
4569
4570
4571
4572
4573
4574
4575
4576
4577
4578
4579
4580
4581
4582
4583
4584
4585
4586
4587
4588
4589
4590
4591
4592
4593
4594
4595
4596
4597
4598
4599
4600
4601
4602
4603
4604
4605
4606
4607
4608
4609
4610
4611
4612
4613
4614
4615
4616
4617
4618
4619
4620
4621
4622
4623
4624
4625
4626
4627
4628
4629
4630
4631
4632
4633
4634
4635
4636
4637
4638
4639
4640
4641
4642
4643
4644
4645
4646
4647
4648
4649
4650
4651
4652
4653
4654
4655
4656
4657
4658
4659
4660
4661
4662
4663
4664
4665
4666
4667
4668
4669
4670
4671
4672
4673
4674
4675
4676
4677
4678
4679
4680
4681
4682
4683
4684
4685
4686
4687
4688
4689
4690
4691
4692
4693
4694
4695
4696
4697
4698
4699
4700
4701
4702
4703
4704
4705
4706
4707
4708
4709
4710
4711
4712
4713
4714
4715
4716
4717
4718
4719
4720
4721
4722
4723
4724
4725
4726
4727
4728
4729
4730
4731
4732
4733
4734
4735
4736
4737
4738
4739
4740
4741
4742
4743
4744
4745
4746
4747
4748
4749
4750
4751
4752
4753
4754
4755
4756
4757
4758
4759
4760
4761
4762
4763
4764
4765
4766
4767
4768
4769
4770
4771
4772
4773
4774
4775
4776
4777
4778
4779
4780
4781
4782
4783
4784
4785
4786
4787
4788
4789
4790
4791
4792
4793
4794
4795
4796
4797
4798
4799
4800
4801
4802
4803
4804
4805
4806
4807
4808
4809
4810
4811
4812
4813
4814
4815
4816
4817
4818
4819
4820
4821
4822
4823
4824
4825
4826
4827
4828
4829
4830
4831
4832
4833
4834
4835
4836
4837
4838
4839
4840
4841
4842
4843
4844
4845
4846
4847
4848
4849
4850
4851
4852
4853
4854
4855
4856
4857
4858
4859
4860
4861
4862
4863
4864
4865
4866
4867
4868
4869
4870
4871
4872
4873
4874
4875
4876
4877
4878
4879
4880
4881
4882
4883
4884
4885
4886
4887
4888
4889
4890
4891
4892
4893
4894
4895
4896
4897
4898
4899
4900
4901
4902
4903
4904
4905
4906
4907
4908
4909
4910
4911
4912
4913
4914
4915
4916
4917
4918
4919
4920
4921
4922
4923
4924
4925
4926
4927
4928
4929
4930
4931
4932
4933
4934
4935
4936
4937
4938
4939
4940
4941
4942
4943
4944
4945
4946
4947
4948
4949
4950
4951
4952
4953
4954
4955
4956
4957
4958
4959
4960
4961
4962
4963
4964
4965
4966
4967
4968
4969
4970
4971
4972
4973
4974
4975
4976
4977
4978
4979
4980
4981
4982
4983
4984
4985
4986
4987
4988
4989
4990
4991
4992
4993
4994
4995
4996
4997
4998
4999
5000
5001
5002
5003
5004
5005
5006
5007
5008
5009
5010
5011
5012
5013
5014
5015
5016
5017
5018
5019
5020
5021
5022
5023
5024
5025
5026
5027
5028
5029
5030
5031
5032
5033
5034
5035
5036
5037
5038
5039
5040
5041
5042
5043
5044
5045
5046
5047
5048
5049
5050
5051
5052
5053
5054
5055
5056
5057
5058
5059
5060
5061
5062
5063
5064
5065
5066
5067
5068
5069
5070
5071
5072
5073
5074
5075
5076
5077
5078
5079
5080
5081
5082
5083
5084
5085
5086
5087
5088
5089
5090
5091
5092
5093
5094
5095
5096
5097
5098
5099
5100
5101
5102
5103
5104
5105
5106
5107
5108
5109
5110
5111
5112
5113
5114
5115
5116
5117
5118
5119
5120
5121
5122
5123
5124
5125
5126
5127
5128
5129
5130
5131
5132
5133
5134
5135
5136
5137
5138
5139
5140
5141
5142
5143
5144
5145
5146
5147
5148
5149
5150
5151
5152
5153
5154
5155
5156
5157
5158
5159
5160
5161
5162
5163
5164
5165
5166
5167
5168
5169
5170
5171
5172
5173
5174
5175
5176
5177
5178
5179
5180
5181
5182
5183
5184
5185
5186
5187
5188
5189
5190
5191
5192
5193
5194
5195
5196
5197
5198
5199
5200
5201
5202
5203
5204
5205
5206
5207
5208
5209
5210
5211
5212
5213
5214
5215
5216
5217
5218
5219
5220
5221
5222
5223
5224
5225
5226
5227
5228
5229
5230
5231
5232
5233
5234
5235
5236
5237
5238
5239
5240
5241
5242
5243
5244
5245
5246
5247
5248
5249
5250
5251
5252
5253
5254
5255
5256
5257
5258
5259
5260
5261
5262
5263
5264
5265
5266
5267
5268
5269
5270
5271
5272
5273
5274
5275
5276
5277
5278
5279
5280
5281
5282
5283
5284
5285
5286
5287
5288
5289
5290
5291
5292
5293
5294
5295
5296
5297
5298
5299
5300
5301
5302
5303
5304
5305
5306
5307
5308
5309
5310
5311
5312
5313
5314
5315
5316
5317
5318
5319
5320
5321
5322
5323
5324
5325
5326
5327
5328
5329
5330
5331
5332
5333
5334
5335
5336
5337
5338
5339
5340
5341
5342
5343
5344
5345
5346
5347
5348
5349
5350
5351
5352
5353
5354
5355
5356
5357
5358
5359
5360
5361
5362
5363
5364
5365
5366
5367
5368
5369
5370
5371
5372
5373
5374
5375
5376
5377
5378
5379
5380
5381
5382
5383
5384
5385
5386
5387
5388
5389
5390
5391
5392
5393
5394
5395
5396
5397
5398
5399
5400
5401
5402
5403
5404
5405
5406
5407
5408
5409
5410
5411
5412
5413
5414
5415
5416
5417
5418
5419
5420
5421
5422
5423
5424
5425
5426
5427
5428
5429
5430
5431
5432
5433
5434
5435
5436
5437
5438
5439
5440
5441
5442
5443
5444
5445
5446
5447
5448
5449
5450
5451
5452
5453
5454
5455
5456
5457
5458
5459
5460
5461
5462
5463
5464
5465
5466
5467
5468
5469
5470
5471
5472
5473
5474
5475
5476
5477
5478
5479
5480
5481
5482
5483
5484
5485
5486
5487
5488
5489
5490
5491
5492
5493
5494
5495
5496
5497
5498
5499
5500
5501
5502
5503
5504
5505
5506
5507
5508
5509
5510
5511
5512
5513
5514
5515
5516
5517
5518
5519
5520
5521
5522
5523
5524
5525
5526
5527
5528
5529
5530
5531
5532
5533
5534
5535
5536
5537
5538
5539
5540
5541
5542
5543
5544
5545
5546
5547
5548
5549
5550
5551
5552
5553
5554
5555
5556
5557
5558
5559
5560
5561
5562
5563
5564
5565
5566
5567
5568
5569
5570
5571
5572
5573
5574
5575
5576
5577
5578
5579
5580
5581
5582
5583
5584
5585
5586
5587
5588
5589
5590
5591
5592
5593
5594
5595
5596
5597
5598
5599
5600
5601
5602
5603
5604
5605
5606
5607
5608
5609
5610
5611
5612
5613
5614
5615
5616
5617
5618
5619
5620
5621
5622
5623
5624
5625
5626
5627
5628
5629
5630
5631
5632
5633
5634
5635
5636
5637
5638
5639
5640
5641
5642
5643
5644
5645
5646
5647
5648
5649
5650
5651
5652
5653
5654
5655
5656
5657
5658
5659
5660
5661
5662
5663
5664
5665
5666
5667
5668
5669
5670
5671
5672
5673
5674
5675
5676
5677
5678
5679
5680
5681
5682
5683
5684
5685
5686
5687
5688
5689
5690
5691
5692
5693
5694
5695
5696
5697
5698
5699
5700
5701
5702
5703
5704
5705
5706
5707
5708
5709
5710
5711
5712
5713
5714
5715
5716
5717
5718
5719
5720
5721
5722
5723
5724
5725
5726
5727
5728
5729
5730
5731
5732
5733
5734
5735
5736
5737
5738
5739
5740
5741
5742
5743
5744
5745
5746
5747
5748
5749
5750
5751
5752
5753
5754
5755
5756
5757
5758
5759
5760
5761
5762
5763
5764
5765
5766
5767
5768
5769
5770
5771
5772
5773
5774
5775
5776
5777
5778
5779
5780
5781
5782
5783
5784
5785
5786
5787
5788
5789
5790
5791
5792
5793
5794
5795
5796
5797
5798
5799
5800
5801
5802
5803
5804
5805
5806
5807
5808
5809
5810
5811
5812
5813
5814
5815
5816
5817
5818
5819
5820
5821
5822
5823
5824
5825
5826
5827
5828
5829
5830
5831
5832
5833
5834
5835
5836
5837
5838
5839
5840
5841
5842
5843
5844
5845
5846
5847
5848
5849
5850
5851
5852
5853
5854
5855
5856
5857
5858
5859
5860
5861
5862
5863
5864
5865
5866
5867
5868
5869
5870
5871
5872
5873
5874
5875
5876
5877
5878
5879
5880
5881
5882
5883
5884
5885
5886
5887
5888
5889
5890
5891
5892
5893
5894
5895
5896
5897
5898
5899
5900
5901
5902
5903
5904
5905
5906
5907
5908
5909
5910
5911
5912
5913
5914
5915
5916
5917
5918
5919
5920
5921
5922
5923
5924
5925
5926
5927
5928
5929
5930
5931
5932
5933
5934
5935
5936
5937
5938
5939
5940
5941
5942
5943
5944
5945
5946
5947
5948
5949
5950
5951
5952
5953
5954
5955
5956
5957
5958
5959
5960
5961
5962
5963
5964
5965
5966
5967
5968
5969
5970
5971
5972
5973
5974
5975
5976
5977
5978
5979
5980
5981
5982
5983
5984
5985
5986
5987
5988
5989
5990
5991
5992
5993
5994
5995
5996
5997
5998
5999
6000
6001
6002
6003
6004
6005
6006
6007
6008
6009
6010
6011
6012
6013
6014
6015
6016
6017
6018
6019
6020
6021
6022
6023
6024
6025
6026
6027
6028
6029
6030
6031
6032
6033
6034
6035
6036
6037
6038
6039
6040
6041
6042
6043
6044
6045
6046
6047
6048
6049
6050
6051
6052
6053
6054
6055
6056
6057
6058
6059
6060
6061
6062
6063
6064
6065
6066
6067
6068
6069
6070
6071
6072
6073
6074
6075
6076
6077
6078
6079
6080
6081
6082
6083
6084
6085
6086
6087
6088
6089
6090
6091
6092
6093
6094
6095
6096
6097
6098
6099
6100
6101
6102
6103
6104
6105
6106
6107
6108
6109
6110
6111
6112
6113
6114
6115
6116
6117
6118
6119
6120
6121
6122
6123
6124
6125
6126
6127
6128
6129
6130
6131
6132
6133
6134
6135
6136
6137
6138
6139
6140
6141
6142
6143
6144
6145
6146
6147
6148
6149
6150
6151
6152
6153
6154
6155
6156
6157
6158
6159
6160
6161
6162
6163
6164
6165
6166
6167
6168
6169
6170
6171
6172
6173
6174
6175
6176
6177
6178
6179
6180
6181
6182
6183
6184
6185
6186
6187
6188
6189
6190
6191
6192
6193
6194
6195
6196
6197
6198
6199
6200
6201
6202
6203
6204
6205
6206
6207
6208
6209
6210
6211
6212
6213
6214
6215
6216
6217
6218
6219
6220
6221
6222
6223
6224
6225
6226
6227
6228
6229
6230
6231
6232
6233
6234
6235
6236
6237
6238
6239
6240
6241
6242
6243
6244
6245
6246
6247
6248
6249
6250
6251
6252
6253
6254
6255
6256
6257
6258
6259
6260
6261
6262
6263
6264
6265
6266
6267
6268
6269
6270
6271
6272
6273
6274
6275
6276
6277
6278
6279
6280
6281
6282
6283
6284
6285
6286
6287
6288
6289
6290
6291
6292
6293
6294
6295
6296
6297
6298
6299
6300
6301
6302
6303
6304
6305
6306
6307
6308
6309
6310
6311
6312
6313
6314
6315
6316
6317
6318
6319
6320
6321
6322
6323
6324
6325
6326
6327
6328
6329
6330
6331
6332
6333
6334
6335
6336
6337
6338
6339
6340
6341
6342
6343
6344
6345
6346
6347
6348
6349
6350
6351
6352
6353
6354
6355
6356
6357
6358
6359
6360
6361
6362
6363
6364
6365
6366
6367
6368
6369
6370
6371
6372
6373
6374
6375
6376
6377
6378
6379
6380
6381
6382
6383
6384
6385
6386
6387
6388
6389
6390
6391
6392
6393
6394
6395
6396
6397
6398
6399
6400
6401
6402
6403
6404
6405
6406
6407
6408
6409
6410
6411
6412
6413
6414
6415
6416
6417
6418
6419
6420
6421
6422
6423
6424
6425
6426
6427
6428
6429
6430
6431
6432
6433
6434
6435
6436
6437
6438
6439
6440
6441
6442
6443
6444
6445
6446
6447
6448
6449
6450
6451
6452
6453
6454
6455
6456
6457
6458
6459
6460
6461
6462
6463
6464
6465
6466
6467
6468
6469
6470
6471
6472
6473
6474
6475
6476
6477
6478
6479
6480
6481
6482
6483
6484
6485
6486
6487
6488
6489
6490
6491
6492
6493
6494
6495
6496
6497
6498
6499
6500
6501
6502
6503
6504
6505
6506
6507
6508
6509
6510
6511
6512
6513
6514
6515
6516
6517
6518
6519
6520
6521
6522
6523
6524
6525
6526
6527
6528
6529
6530
6531
6532
6533
6534
6535
6536
6537
6538
6539
6540
6541
6542
6543
6544
6545
6546
6547
6548
6549
6550
6551
6552
6553
6554
6555
6556
6557
6558
6559
6560
6561
6562
6563
6564
6565
6566
6567
6568
6569
6570
6571
6572
6573
6574
6575
6576
6577
6578
6579
6580
6581
6582
6583
6584
6585
6586
6587
6588
6589
6590
6591
6592
6593
6594
6595
6596
6597
6598
6599
6600
6601
6602
6603
6604
6605
6606
6607
6608
6609
6610
6611
6612
6613
6614
6615
6616
6617
6618
6619
6620
6621
6622
6623
6624
6625
6626
6627
6628
6629
6630
6631
6632
6633
6634
6635
6636
6637
6638
6639
6640
6641
6642
6643
6644
6645
6646
6647
6648
6649
6650
6651
6652
6653
6654
6655
6656
6657
6658
6659
6660
6661
6662
6663
6664
6665
6666
6667
6668
6669
6670
6671
6672
6673
6674
6675
6676
6677
6678
6679
6680
6681
6682
6683
6684
6685
6686
6687
6688
6689
6690
6691
6692
6693
6694
6695
6696
6697
6698
6699
6700
6701
6702
6703
6704
6705
6706
6707
6708
6709
6710
6711
6712
6713
6714
6715
6716
6717
6718
6719
6720
6721
6722
6723
6724
6725
6726
6727
6728
6729
6730
6731
6732
6733
6734
6735
6736
6737
6738
6739
6740
6741
6742
6743
6744
6745
6746
6747
6748
6749
6750
6751
6752
6753
6754
6755
6756
6757
6758
6759
6760
6761
6762
6763
6764
6765
6766
6767
6768
6769
6770
6771
6772
6773
6774
6775
6776
6777
6778
6779
6780
6781
6782
6783
6784
6785
6786
6787
6788
6789
6790
6791
6792
6793
6794
6795
6796
6797
6798
6799
6800
6801
6802
6803
6804
6805
6806
6807
6808
6809
6810
6811
6812
6813
6814
6815
6816
6817
6818
6819
6820
6821
6822
6823
6824
6825
6826
6827
6828
6829
6830
6831
6832
6833
6834
6835
6836
6837
6838
6839
6840
6841
6842
6843
6844
6845
6846
6847
6848
6849
6850
6851
6852
6853
6854
6855
6856
6857
6858
6859
6860
6861
6862
6863
6864
6865
6866
6867
6868
6869
6870
6871
6872
6873
6874
6875
6876
6877
6878
6879
6880
6881
6882
6883
6884
6885
6886
6887
6888
6889
6890
6891
6892
6893
6894
6895
6896
6897
6898
6899
6900
6901
6902
6903
6904
6905
6906
6907
6908
6909
6910
6911
6912
6913
6914
6915
6916
6917
6918
6919
6920
6921
6922
6923
6924
6925
6926
6927
6928
6929
6930
6931
6932
6933
6934
6935
6936
6937
6938
6939
6940
6941
6942
6943
6944
6945
6946
6947
6948
6949
6950
6951
6952
6953
6954
6955
6956
6957
6958
6959
6960
6961
6962
6963
6964
6965
6966
6967
6968
6969
6970
6971
6972
6973
6974
6975
6976
6977
6978
6979
6980
6981
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>GPSBabel Documentation</title><link rel="stylesheet" type="text/css" href="docbook.css" /><link rel="stylesheet" type="text/css" href="http://www.gpsbabel.org/style3.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div class="book"><div class="titlepage"><div><div><h1 class="title"><a id="GPSBabel_Documentation_Book"></a>GPSBabel Documentation</h1></div></div><hr /></div><div class="toc"><div class="toc-title">Table of Contents</div><dl class="toc"><dt><span class="preface"><a href="#Introduction">Introduction to GPSBabel</a></span></dt><dd><dl><dt><span class="section"><a href="#The_Problem">The Problem: Too many incompatible GPS file formats</a></span></dt><dt><span class="section"><a href="#The_Solution">The Solution</a></span></dt></dl></dd><dt><span class="chapter"><a href="#Getting_and_Building">1. Getting or Building GPSBabel</a></span></dt><dd><dl><dt><span class="sect1"><a href="#Download">Downloading - the easy way.</a></span></dt><dt><span class="sect1"><a href="#Source">Building from source.</a></span></dt></dl></dd><dt><span class="chapter"><a href="#Usage">2. Usage</a></span></dt><dd><dl><dt><span class="sect1"><a href="#Invocation">Invocation</a></span></dt><dt><span class="sect1"><a href="#Suboptions">Suboptions</a></span></dt><dt><span class="sect1"><a href="#Advanced_Usage">Advanced Usage</a></span></dt><dt><span class="sect1"><a href="#Route_And_Track_Modes">Route and Track Modes</a></span></dt><dt><span class="sect1"><a href="#inifile">Working with predefined options</a></span></dt><dt><span class="sect1"><a href="#tracking">Realtime tracking</a></span></dt><dt><span class="sect1"><a href="#batchfile">Batch mode (command files)</a></span></dt><dt><span class="sect1"><a href="#all_options">List of Options</a></span></dt></dl></dd><dt><span class="chapter"><a href="#The_Formats">3. The Formats</a></span></dt><dd><dl><dt><span class="section"><a href="#fmt_xcsv">? Character Separated Values (xcsv)</a></span></dt><dt><span class="section"><a href="#fmt_alantrl">Alan Map500 tracklogs (.trl) (alantrl)</a></span></dt><dt><span class="section"><a href="#fmt_alanwpr">Alan Map500 waypoints and routes (.wpr) (alanwpr)</a></span></dt><dt><span class="section"><a href="#fmt_tabsep">All database fields on one tab-separated line (tabsep)</a></span></dt><dt><span class="section"><a href="#fmt_baroiq">Brauniger IQ Series Barograph Download (baroiq)</a></span></dt><dt><span class="section"><a href="#fmt_bushnell_trl">Bushnell GPS Trail file (bushnell_trl)</a></span></dt><dt><span class="section"><a href="#fmt_bushnell">Bushnell GPS Waypoint file (bushnell)</a></span></dt><dt><span class="section"><a href="#fmt_cambridge">Cambridge/Winpilot glider software (cambridge)</a></span></dt><dt><span class="section"><a href="#fmt_cst">CarteSurTable data file (cst)</a></span></dt><dt><span class="section"><a href="#fmt_v900">Columbus/Visiontac V900 files (.csv) (v900)</a></span></dt><dt><span class="section"><a href="#fmt_csv">Comma separated values (csv)</a></span></dt><dt><span class="section"><a href="#fmt_compegps">CompeGPS data files (.wpt/.trk/.rte) (compegps)</a></span></dt><dt><span class="section"><a href="#fmt_custom">Custom "Everything" Style (custom)</a></span></dt><dt><span class="section"><a href="#fmt_iblue747">Data Logger iBlue747 csv (iblue747)</a></span></dt><dt><span class="section"><a href="#fmt_iblue757">Data Logger iBlue757 csv (iblue757)</a></span></dt><dt><span class="section"><a href="#fmt_an1">DeLorme .an1 (drawing) file (an1)</a></span></dt><dt><span class="section"><a href="#fmt_gpl">DeLorme GPL (gpl)</a></span></dt><dt><span class="section"><a href="#fmt_delbin">DeLorme PN-20/PN-30/PN-40 USB protocol (delbin)</a></span></dt><dt><span class="section"><a href="#fmt_saplus">DeLorme Street Atlas Plus (saplus)</a></span></dt><dt><span class="section"><a href="#fmt_saroute">DeLorme Street Atlas Route (saroute)</a></span></dt><dt><span class="section"><a href="#fmt_xmap">DeLorme XMap HH Native .WPT (xmap)</a></span></dt><dt><span class="section"><a href="#fmt_xmap2006">DeLorme XMap/SAHH 2006 Native .TXT (xmap2006)</a></span></dt><dt><span class="section"><a href="#fmt_xmapwpt">DeLorme XMat HH Street Atlas USA .WPT (PPC) (xmapwpt)</a></span></dt><dt><span class="section"><a href="#fmt_destinator_itn">Destinator Itineraries (.dat) (destinator_itn)</a></span></dt><dt><span class="section"><a href="#fmt_destinator_poi">Destinator Points of Interest (.dat) (destinator_poi)</a></span></dt><dt><span class="section"><a href="#fmt_destinator_trl">Destinator TrackLogs (.dat) (destinator_trl)</a></span></dt><dt><span class="section"><a href="#fmt_easygps">EasyGPS binary format (easygps)</a></span></dt><dt><span class="section"><a href="#fmt_exif">Embedded Exif-GPS data (.jpg) (exif)</a></span></dt><dt><span class="section"><a href="#fmt_enigma">Enigma binary waypoint file (.ert) (enigma)</a></span></dt><dt><span class="section"><a href="#fmt_igc">FAI/IGC Flight Recorder Data Format (igc)</a></span></dt><dt><span class="section"><a href="#fmt_garmin_fit">Flexible and Interoperable Data Transfer (FIT) Activity file (garmin_fit)</a></span></dt><dt><span class="section"><a href="#fmt_flysight">FlySight GPS File (flysight)</a></span></dt><dt><span class="section"><a href="#fmt_gpssim">Franson GPSGate Simulation (gpssim)</a></span></dt><dt><span class="section"><a href="#fmt_fugawi">Fugawi (fugawi)</a></span></dt><dt><span class="section"><a href="#fmt_g7towin">G7ToWin data files (.g7t) (g7towin)</a></span></dt><dt><span class="section"><a href="#fmt_garmin301">Garmin 301 Custom position and heartrate (garmin301)</a></span></dt><dt><span class="section"><a href="#fmt_garmin_g1000">Garmin G1000 datalog input filter file (garmin_g1000)</a></span></dt><dt><span class="section"><a href="#fmt_glogbook">Garmin Logbook XML (glogbook)</a></span></dt><dt><span class="section"><a href="#fmt_gdb">Garmin MapSource - gdb (gdb)</a></span></dt><dt><span class="section"><a href="#fmt_mapsource">Garmin MapSource - mps (mapsource)</a></span></dt><dt><span class="section"><a href="#fmt_garmin_txt">Garmin MapSource - txt (tab delimited) (garmin_txt)</a></span></dt><dt><span class="section"><a href="#fmt_pcx">Garmin PCX5 (pcx)</a></span></dt><dt><span class="section"><a href="#fmt_garmin_poi">Garmin POI database (garmin_poi)</a></span></dt><dt><span class="section"><a href="#fmt_garmin_gpi">Garmin Points of Interest (.gpi) (garmin_gpi)</a></span></dt><dt><span class="section"><a href="#fmt_garmin">Garmin serial/USB protocol (garmin)</a></span></dt><dt><span class="section"><a href="#fmt_gtrnctr">Garmin Training Center (.tcx) (gtrnctr)</a></span></dt><dt><span class="section"><a href="#fmt_gtrnctr1">Garmin Training Center (.xml) (gtrnctr)</a></span></dt><dt><span class="section"><a href="#fmt_geo">Geocaching.com .loc (geo)</a></span></dt><dt><span class="section"><a href="#fmt_ggv_ovl">Geogrid-Viewer ascii overlay file (.ovl) (ggv_ovl)</a></span></dt><dt><span class="section"><a href="#fmt_ggv_log">Geogrid-Viewer tracklogs (.log) (ggv_log)</a></span></dt><dt><span class="section"><a href="#fmt_geonet">GEOnet Names Server (GNS) (geonet)</a></span></dt><dt><span class="section"><a href="#fmt_dg-100">GlobalSat DG-100/BT-335 Download (dg-100)</a></span></dt><dt><span class="section"><a href="#fmt_dg-200">GlobalSat DG-200 Download (dg-200)</a></span></dt><dt><span class="section"><a href="#fmt_googledir">Google Directions XML (googledir)</a></span></dt><dt><span class="section"><a href="#fmt_kml">Google Earth (Keyhole) Markup Language (kml)</a></span></dt><dt><span class="section"><a href="#fmt_google">Google Maps XML (google)</a></span></dt><dt><span class="section"><a href="#fmt_gnav_trl">Google Navigator Tracklines (.trl) (gnav_trl)</a></span></dt><dt><span class="section"><a href="#fmt_gopal">GoPal GPS track log (.trk) (gopal)</a></span></dt><dt><span class="section"><a href="#fmt_land_air_sea">GPS Tracking Key Pro text (land_air_sea)</a></span></dt><dt><span class="section"><a href="#fmt_gtm">GPS TrackMaker (gtm)</a></span></dt><dt><span class="section"><a href="#fmt_arc">GPSBabel arc filter file (arc)</a></span></dt><dt><span class="section"><a href="#fmt_gpsdrive">GpsDrive Format (gpsdrive)</a></span></dt><dt><span class="section"><a href="#fmt_gpsdrivetrack">GpsDrive Format for Tracks (gpsdrivetrack)</a></span></dt><dt><span class="section"><a href="#fmt_gpsman">GPSman (gpsman)</a></span></dt><dt><span class="section"><a href="#fmt_gpsutil">gpsutil (gpsutil)</a></span></dt><dt><span class="section"><a href="#fmt_gpx">GPX XML (gpx)</a></span></dt><dt><span class="section"><a href="#fmt_hiketech">HikeTech (hiketech)</a></span></dt><dt><span class="section"><a href="#fmt_holux">Holux (gm-100) .wpo Format (holux)</a></span></dt><dt><span class="section"><a href="#fmt_m241-bin">Holux M-241 (MTK based) Binary File Format (m241-bin)</a></span></dt><dt><span class="section"><a href="#fmt_m241">Holux M-241 (MTK based) download (m241)</a></span></dt><dt><span class="section"><a href="#fmt_vpl">Honda/Acura Navigation System VP Log File Format (vpl)</a></span></dt><dt><span class="section"><a href="#fmt_html">HTML Output (html)</a></span></dt><dt><span class="section"><a href="#fmt_humminbird_ht">Humminbird tracks (.ht) (humminbird_ht)</a></span></dt><dt><span class="section"><a href="#fmt_humminbird">Humminbird waypoints and routes (.hwr) (humminbird)</a></span></dt><dt><span class="section"><a href="#fmt_ignrando">IGN Rando track files (ignrando)</a></span></dt><dt><span class="section"><a href="#fmt_igo2008_poi">iGO2008 points of interest (.upoi) (igo2008_poi)</a></span></dt><dt><span class="section"><a href="#fmt_igo8">IGO8 .trk (igo8)</a></span></dt><dt><span class="section"><a href="#fmt_jtr">Jelbert GeoTagger data file (jtr)</a></span></dt><dt><span class="section"><a href="#fmt_jogmap">Jogmap.de XML format (jogmap)</a></span></dt><dt><span class="section"><a href="#fmt_kompass_tk">Kompass (DAV) Track (.tk) (kompass_tk)</a></span></dt><dt><span class="section"><a href="#fmt_kompass_wp">Kompass (DAV) Waypoints (.wp) (kompass_wp)</a></span></dt><dt><span class="section"><a href="#fmt_psitrex">KuDaTa PsiTrex text (psitrex)</a></span></dt><dt><span class="section"><a href="#fmt_lowranceusr">Lowrance USR (lowranceusr)</a></span></dt><dt><span class="section"><a href="#fmt_lowranceusr4">Lowrance USR version 4 (lowranceusr4)</a></span></dt><dt><span class="section"><a href="#fmt_maggeo">Magellan Explorist Geocaching (maggeo)</a></span></dt><dt><span class="section"><a href="#fmt_mapsend">Magellan Mapsend (mapsend)</a></span></dt><dt><span class="section"><a href="#fmt_magellanx">Magellan SD files (as for eXplorist) (magellanx)</a></span></dt><dt><span class="section"><a href="#fmt_magellan">Magellan SD files (as for Meridian) (magellan)</a></span></dt><dt><span class="section"><a href="#fmt_magellan1">Magellan serial protocol (magellan)</a></span></dt><dt><span class="section"><a href="#fmt_ik3d">MagicMaps IK3D project file (.ikt) (ik3d)</a></span></dt><dt><span class="section"><a href="#fmt_mainnav">Mainnav (mainnav)</a></span></dt><dt><span class="section"><a href="#fmt_tef">Map&amp;amp;Guide 'TourExchangeFormat' XML (tef)</a></span></dt><dt><span class="section"><a href="#fmt_mapasia_tr7">MapAsia track file (.tr7) (mapasia_tr7)</a></span></dt><dt><span class="section"><a href="#fmt_mapbar">Mapbar (China) navigation track for Sonim Xp3300 (mapbar)</a></span></dt><dt><span class="section"><a href="#fmt_mapfactor">Mapfactor Navigator (mapfactor)</a></span></dt><dt><span class="section"><a href="#fmt_mapconverter">Mapopolis.com Mapconverter CSV (mapconverter)</a></span></dt><dt><span class="section"><a href="#fmt_mxf">MapTech Exchange Format (mxf)</a></span></dt><dt><span class="section"><a href="#fmt_mtk_locus">MediaTek Locus (mtk_locus)</a></span></dt><dt><span class="section"><a href="#fmt_mmo">Memory-Map Navigator overlay files (.mmo) (mmo)</a></span></dt><dt><span class="section"><a href="#fmt_s_and_t">Microsoft Streets and Trips 2002-2007 (s_and_t)</a></span></dt><dt><span class="section"><a href="#fmt_miniHomer">MiniHomer, a skyTraq Venus 6 based logger (download tracks, waypoints and get/set POI) (miniHomer)</a></span></dt><dt><span class="section"><a href="#fmt_garmin_xt">Mobile Garmin XT Track files (garmin_xt)</a></span></dt><dt><span class="section"><a href="#fmt_motoactv">Motoactiv CSV (motoactv)</a></span></dt><dt><span class="section"><a href="#fmt_bcr">Motorrad Routenplaner (Map&amp;amp;Guide) .bcr files (bcr)</a></span></dt><dt><span class="section"><a href="#fmt_mtk-bin">MTK Logger (iBlue 747,...) Binary File Format (mtk-bin)</a></span></dt><dt><span class="section"><a href="#fmt_mtk">MTK Logger (iBlue 747,Qstarz BT-1000,...) download (mtk)</a></span></dt><dt><span class="section"><a href="#fmt_tpg">National Geographic Topo .tpg (waypoints) (tpg)</a></span></dt><dt><span class="section"><a href="#fmt_tpo2">National Geographic Topo 2.x .tpo (tpo2)</a></span></dt><dt><span class="section"><a href="#fmt_tpo3">National Geographic Topo 3.x/4.x .tpo (tpo3)</a></span></dt><dt><span class="section"><a href="#fmt_navicache">Navicache.com XML (navicache)</a></span></dt><dt><span class="section"><a href="#fmt_nmn4">Navigon Mobile Navigator .rte files (nmn4)</a></span></dt><dt><span class="section"><a href="#fmt_navigonwpt">Navigon Waypoints (navigonwpt)</a></span></dt><dt><span class="section"><a href="#fmt_navilink">NaviGPS GT-11/BGT-11 Download (navilink)</a></span></dt><dt><span class="section"><a href="#fmt_sbp">NaviGPS GT-31/BGT-31 datalogger (.sbp) (sbp)</a></span></dt><dt><span class="section"><a href="#fmt_sbn">NaviGPS GT-31/BGT-31 SiRF binary logfile (.sbn) (sbn)</a></span></dt><dt><span class="section"><a href="#fmt_naviguide">Naviguide binary route file (.twl) (naviguide)</a></span></dt><dt><span class="section"><a href="#fmt_navitel_trk">Navitel binary track (.bin) (navitel_trk)</a></span></dt><dt><span class="section"><a href="#fmt_dna">Navitrak DNA marker format (dna)</a></span></dt><dt><span class="section"><a href="#fmt_netstumbler">NetStumbler Summary File (text) (netstumbler)</a></span></dt><dt><span class="section"><a href="#fmt_nima">NIMA/GNIS Geographic Names File (nima)</a></span></dt><dt><span class="section"><a href="#fmt_nmea">NMEA 0183 sentences (nmea)</a></span></dt><dt><span class="section"><a href="#fmt_lmx">Nokia Landmark Exchange (lmx)</a></span></dt><dt><span class="section"><a href="#fmt_osm">OpenStreetMap data files (osm)</a></span></dt><dt><span class="section"><a href="#fmt_ozi">OziExplorer (ozi)</a></span></dt><dt><span class="section"><a href="#fmt_pocketfms_bc">PocketFMS breadcrumbs (pocketfms_bc)</a></span></dt><dt><span class="section"><a href="#fmt_pocketfms_fp">PocketFMS flightplan (.xml) (pocketfms_fp)</a></span></dt><dt><span class="section"><a href="#fmt_pocketfms_wp">PocketFMS waypoints (.txt) (pocketfms_wp)</a></span></dt><dt><span class="section"><a href="#fmt_raymarine">Raymarine Waypoint File (.rwf) (raymarine)</a></span></dt><dt><span class="section"><a href="#fmt_ricoh">Ricoh GPS Log File (ricoh)</a></span></dt><dt><span class="section"><a href="#fmt_cup">See You flight analysis data (cup)</a></span></dt><dt><span class="section"><a href="#fmt_skyforce">Skymap / KMD150 ascii files (skyforce)</a></span></dt><dt><span class="section"><a href="#fmt_skytraq">SkyTraq Venus based loggers (download) (skytraq)</a></span></dt><dt><span class="section"><a href="#fmt_skytraq-bin">SkyTraq Venus based loggers Binary File Format (skytraq-bin)</a></span></dt><dt><span class="section"><a href="#fmt_subrip">SubRip subtitles for video mapping (.srt) (subrip)</a></span></dt><dt><span class="section"><a href="#fmt_stmsdf">Suunto Trek Manager (STM) .sdf files (stmsdf)</a></span></dt><dt><span class="section"><a href="#fmt_stmwpp">Suunto Trek Manager (STM) WaypointPlus files (stmwpp)</a></span></dt><dt><span class="section"><a href="#fmt_xol">Swiss Map 25/50/100 (.xol) (xol)</a></span></dt><dt><span class="section"><a href="#fmt_openoffice">Tab delimited fields useful for OpenOffice, Ploticus etc. (openoffice)</a></span></dt><dt><span class="section"><a href="#fmt_teletype">Teletype [ Get Jonathon Johnson to describe (teletype)</a></span></dt><dt><span class="section"><a href="#fmt_text">Textual Output (text)</a></span></dt><dt><span class="section"><a href="#fmt_tomtom_itn">TomTom Itineraries (.itn) (tomtom_itn)</a></span></dt><dt><span class="section"><a href="#fmt_tomtom_itn_places">TomTom Places Itineraries (.itn) (tomtom_itn_places)</a></span></dt><dt><span class="section"><a href="#fmt_tomtom_asc">TomTom POI file (.asc) (tomtom_asc)</a></span></dt><dt><span class="section"><a href="#fmt_tomtom">TomTom POI file (.ov2) (tomtom)</a></span></dt><dt><span class="section"><a href="#fmt_tmpro">TopoMapPro Places File (tmpro)</a></span></dt><dt><span class="section"><a href="#fmt_dmtlog">TrackLogs digital mapping (.trl) (dmtlog)</a></span></dt><dt><span class="section"><a href="#fmt_tiger">U.S. Census Bureau Tiger Mapping Service (tiger)</a></span></dt><dt><span class="section"><a href="#fmt_unicsv">Universal csv with field structure in first line (unicsv)</a></span></dt><dt><span class="section"><a href="#fmt_vcard">Vcard Output (for iPod) (vcard)</a></span></dt><dt><span class="section"><a href="#fmt_vidaone">VidaOne GPS for Pocket PC (.gpb) (vidaone)</a></span></dt><dt><span class="section"><a href="#fmt_vitosmt">Vito Navigator II tracks (vitosmt)</a></span></dt><dt><span class="section"><a href="#fmt_vitovtt">Vito SmartMap tracks (.vtt) (vitovtt)</a></span></dt><dt><span class="section"><a href="#fmt_wfff">WiFiFoFum 2.0 for PocketPC XML (wfff)</a></span></dt><dt><span class="section"><a href="#fmt_wintec_tes">Wintec TES file (wintec_tes)</a></span></dt><dt><span class="section"><a href="#fmt_wbt-bin">Wintec WBT-100/200 Binary File Format (wbt-bin)</a></span></dt><dt><span class="section"><a href="#fmt_wbt">Wintec WBT-100/200 GPS Download (wbt)</a></span></dt><dt><span class="section"><a href="#fmt_wbt-tk1">Wintec WBT-201/G-Rays 2 Binary File Format (wbt-tk1)</a></span></dt><dt><span class="section"><a href="#fmt_itracku">XAiOX iTrackU Logger (itracku)</a></span></dt><dt><span class="section"><a href="#fmt_itracku-bin">XAiOX iTrackU Logger Binary File Format (itracku-bin)</a></span></dt><dt><span class="section"><a href="#fmt_yahoo">Yahoo Geocode API data (yahoo)</a></span></dt></dl></dd><dt><span class="chapter"><a href="#Data_Filters">4. Data Filters</a></span></dt><dd><dl><dt><span class="section"><a href="#filter_bend">Add points before and after bends in routes (bend)</a></span></dt><dt><span class="section"><a href="#filter_polygon">Include Only Points Inside Polygon (polygon)</a></span></dt><dt><span class="section"><a href="#filter_arc">Include Only Points Within Distance of Arc (arc)</a></span></dt><dt><span class="section"><a href="#filter_radius">Include Only Points Within Radius (radius)</a></span></dt><dt><span class="section"><a href="#filter_interpolate">Interpolate between trackpoints (interpolate)</a></span></dt><dt><span class="section"><a href="#filter_height">Manipulate altitudes (height)</a></span></dt><dt><span class="section"><a href="#filter_track">Manipulate track lists (track)</a></span></dt><dt><span class="section"><a href="#filter_sort">Rearrange waypoints by resorting (sort)</a></span></dt><dt><span class="section"><a href="#filter_nuketypes">Remove all waypoints, tracks, or routes (nuketypes)</a></span></dt><dt><span class="section"><a href="#filter_duplicate">Remove Duplicates (duplicate)</a></span></dt><dt><span class="section"><a href="#filter_position">Remove Points Within Distance (position)</a></span></dt><dt><span class="section"><a href="#filter_discard">Remove unreliable points with high hdop or vdop (discard)</a></span></dt><dt><span class="section"><a href="#filter_reverse">Reverse stops within routes (reverse)</a></span></dt><dt><span class="section"><a href="#filter_stack">Save and restore waypoint lists (stack)</a></span></dt><dt><span class="section"><a href="#filter_simplify">Simplify routes (simplify)</a></span></dt><dt><span class="section"><a href="#filter_swap">Swap latitude and longitude of all loaded points (swap)</a></span></dt><dt><span class="section"><a href="#filter_transform">Transform waypoints into a route, tracks into routes, ... (transform)</a></span></dt><dt><span class="section"><a href="#filter_validate">Validate internal data structures (validate)</a></span></dt></dl></dd><dt><span class="appendix"><a href="#Datums">A. Supported Datums</a></span></dt><dt><span class="appendix"><a href="#GarminIcons">B. Garmin Icons</a></span></dt><dt><span class="appendix"><a href="#Styles">C. GPSBabel XCSV Style Files</a></span></dt><dd><dl><dt><span class="section"><a href="#styles_intro">Introduction to GPSBabel Styles</a></span></dt><dt><span class="section"><a href="#style_intro2">Style file overview</a></span></dt><dt><span class="section"><a href="#styles_internal_const">Internal Constants</a></span></dt><dt><span class="section"><a href="#style_global">Global Properties of the File</a></span></dt><dt><span class="section"><a href="#style_behavior">GPSBabel Behavior Directives</a></span></dt><dt><span class="section"><a href="#style_layout">Defining the Layout of the File</a></span></dt><dt><span class="section"><a href="#style_define">Defining Fields Within the File</a></span></dt><dt><span class="section"><a href="#style_examples">Examples</a></span></dt><dt><span class="section"><a href="#style_notes">Miscellaneous Notes</a></span></dt></dl></dd><dt><span class="glossary"><a href="#Glossary">Glossary</a></span></dt></dl></div><div class="list-of-tables"><div class="toc-title">List of Tables</div><dl><dt>3.1. <a href="#garmin_grid">Grid values for garmin_txt</a></dt><dt>3.2. <a href="#distance_units">Supported distance units (garmin_gpi)</a></dt><dt>3.3. <a href="#garmin_gpi_speed_units">Supported speed units (garmin_gpi)</a></dt><dt>3.4. <a href="#structure">Track point structure (16 bytes)</a></dt><dt>3.5. <a href="#miniHomer_devices">Devices supported by miniHomer module</a></dt><dt>3.6. <a href="#mtk_devices">Devices supported by MTK module</a></dt><dt>3.7. <a href="#skytraq_devices">Devices supported by skytraq module</a></dt><dt>3.8. <a href="#vito_header">Vito SmartMap track file header (8 bytes)</a></dt><dt>3.9. <a href="#idp74670304">Vito SmartMap track point (32 bytes)</a></dt></dl></div><div class="list-of-examples"><div class="toc-title">List of Examples</div><dl><dt>2.1. <a href="#linux_download_from_magellan">Command showing Linux download from Magellan serial and writing to .loc file</a></dt><dt>2.2. <a href="#windows_download_from_magellan">Command showing Windows download from Magellan serial and writing to .loc file</a></dt><dt>2.3. <a href="#merging_files">Merging multiple files into one</a></dt><dt>2.4. <a href="#merging_different_types_of_files">Merging multiple files of differing types.</a></dt><dt>2.5. <a href="#multiple_writes">Writing the same data in multiple output formats.</a></dt><dt>2.6. <a href="#realtime_reading">Read realtime positioning from Garmin USB, write to Keyhole Markup</a></dt><dt>2.7. <a href="#realtime_reading_wintec">Read realtime positioning from Wintec WBT-201 via Bluetooth on Mac, write to Keyhole Markup</a></dt><dt>3.1. <a href="#bushnell-output">Command showing writing to Bushnell files</a></dt><dt>3.2. <a href="#v900_e1">Conversion of a v900 csv log file to a gpx format</a></dt><dt>3.3. <a href="#v900_e2">Conversion of a v900 csv log file to a gpx 1.1 format</a></dt><dt>3.4. <a href="#csv_example">Example 'csv' file</a></dt><dt>3.5. <a href="#pn-40-send">Command to send a pocket query (GPX) to a Delorme PN device </a></dt><dt>3.6. <a href="#gdb_bitscategory">Example for gdb bitcategory option to put all waypoints in categories 1 and 16.</a></dt><dt>3.7. <a href="#gdb_roadbook_option">Using gdb option <code class="option">roadbook</code> to create simple html roadbook</a></dt><dt>3.8. <a href="#all_garmin_txt_options">Command showing garmin_txt output with all options</a></dt><dt>3.9. <a href="#all_garmin_gpi_options">Command showing garmin_gpi output example</a></dt><dt>3.10. <a href="#garmin_gpi_speedcams">Read GPX file, create GPI to alert when you're 1/2 mile from a speed camera.</a></dt><dt>3.11. <a href="#garmin_bitcategory">Example for garmin bitcategory option to put all waypoints in categories 1 and 16.</a></dt><dt>3.12. <a href="#dg-100-on-linux">Command showing DG-100 download and erase on Linux</a></dt><dt>3.13. <a href="#dg-100-on-linux-erase_only">Command showing DG-100 erase_only option on Linux</a></dt><dt>3.14. <a href="#dg-200-on-linux">Command showing DG-200 download and erase on Linux</a></dt><dt>3.15. <a href="#dg-200-on-linux-erase_only">Command showing DG-200 erase_only option on Linux</a></dt><dt>3.16. <a href="#mmo_ver">Forcing creation of old Mobile Mapper files</a></dt><dt>3.17. <a href="#miniHomer-on-linux">Command showing miniHomer download of tracks and erasing the logger on Linux</a></dt><dt>3.18. <a href="#miniHomer-erase">Command showing miniHomer erasing the logger without download on Linux</a></dt><dt>3.19. <a href="#miniHomer-on-linux-poi">Command showing miniHomer setting Car and Home POI</a></dt><dt>3.20. <a href="#miniHomer-restore-erased">Command showing how to read data from an erased device</a></dt><dt>3.21. <a href="#miniHomer-Home">Set the target location of the miniHomer Home POI</a></dt><dt>3.22. <a href="#miniHomer-Car">Set the target location of the miniHomer Car POI</a></dt><dt>3.23. <a href="#miniHomer-Boat">Set the target location of the miniHomer Boat POI</a></dt><dt>3.24. <a href="#miniHomer-Heart">Set the target location of the miniHomer Heart POI</a></dt><dt>3.25. <a href="#miniHomer-Bar">Set the target location of the miniHomer Bar POI</a></dt><dt>3.26. <a href="#sample_bcr_command">Sample BCR command with all options</a></dt><dt>3.27. <a href="#mtk-bin-on-linux">Convert MTK binary trackpoints to GPX</a></dt><dt>3.28. <a href="#mtk-on-linux">Command showing MTK download track and waypoints and erase on Linux</a></dt><dt>3.29. <a href="#skytraq-on-linux">Command showing skytraq download of tracks and erasing the logger on Linux</a></dt><dt>3.30. <a href="#skytraq-erase">Command showing skytraq erasing the logger without download on Linux</a></dt><dt>3.31. <a href="#skytraq-on-linux-bt">Command showing skytraq download tracks via bluetooth on Linux</a></dt><dt>3.32. <a href="#skytraq-targetlocation">Set the target location of the Skytraq location finder</a></dt><dt>3.33. <a href="#skytraq-configulog">Set the logging parameters for Skytraq device</a></dt><dt>3.34. <a href="#skytraq-restore-erased">Command showing how to read data from an erased device</a></dt><dt>3.35. <a href="#text_splitoutput">Example for splitoutput option to text format</a></dt><dt>3.36. <a href="#unicsv_format">Example for unicsv format option to write names of input formats.</a></dt><dt>3.37. <a href="#unicsv_filename">Example for unicsv filename option to write filenames of input formats.</a></dt><dt>3.38. <a href="#wbt-bin-on-macos">Command showing conversion of a Wintec binary file to GPX</a></dt><dt>3.39. <a href="#wbt-on-macos">Command showing WBT-200 download and erase over Bluetooth on Mac OS X</a></dt><dt>3.40. <a href="#wbt-tk1">Command showing conversion of a Wintec binary file to GPX</a></dt><dt>3.41. <a href="#itracku-download">Command showing a download from itracku connected to com14.</a></dt><dt>3.42. <a href="#itracku-download-auto">Command showing a download from itracku with automatic port detection.</a></dt><dt>3.43. <a href="#itracku-backup">Download from the data logger while and append the new binary logger data to a backup file. Read the contents of the backup file.</a></dt><dt>3.44. <a href="#itracku-new">Download from the data logger and append the new logger data to a backup file. Output only the new 
  waypoints.</a></dt><dt>3.45. <a href="#itracku-bin">Command showing reading an itracku data file.</a></dt><dt>4.1. <a href="#example_polygon_filter">Using the polygon filter</a></dt><dt>4.2. <a href="#example_in_or_close_to">Using the polygon and arc filters to find points in or nearly in a 
polygon</a></dt><dt>4.3. <a href="#example_arc_filter">Using the arc filter</a></dt><dt>4.4. <a href="#radius_to_find_points_close">Using the radius filter to find points close to a given point</a></dt><dt>4.5. <a href="#example_interpolate_filter">Using the interpolate filter</a></dt><dt>4.6. <a href="#height_wgs84tomsl"> This option subtracts the WGS84 geoid height from every altitude. For GPS receivers like the iBlue747 the result is the height above mean see level.</a></dt><dt>4.7. <a href="#height_add"> This options adds a constant value to every altitude.</a></dt><dt>4.8. <a href="#ex_track_move">Time-shifting a track with the track filter</a></dt><dt>4.9. <a href="#ex_track_merge">Merging tracks with the track filter</a></dt><dt>4.10. <a href="#ex_track_startstop">Extracting a period of time with the track filter</a></dt><dt>4.11. <a href="#ex_track_faketime1">Replace time values of a track</a></dt><dt>4.12. <a href="#ex_track_faketime2">Add time values to a track</a></dt><dt>4.13. <a href="#ex_track_discard">Merging tracks with missing timestamps with the track filter</a></dt><dt>4.14. <a href="#example_nuketypes_filter">Filtering data types with nuketypes</a></dt><dt>4.15. <a href="#duplicate_to_suppress_points">Using the duplicate filter to suppress points with the same 
         name and location</a></dt><dt>4.16. <a href="#duplicate_to_ignore">Using the duplicate filter to implement an "ignore list."</a></dt><dt>4.17. <a href="#Correcting_Cache_Locations">Using the duplicate filter to correct the locations of "puzzle"
geocaches</a></dt><dt>4.18. <a href="#posn_to_suppress_close_points">Using the position filter to suppress close points</a></dt><dt>4.19. <a href="#example_discard_filter">Using the discard filter for HDOP and VDOP. </a></dt><dt>4.20. <a href="#example_discard_filter_sats">Using the discard filter to require at least three satellites. </a></dt><dt>4.21. <a href="#transform_to_wpt">Converting a track to a sequence of waypoints</a></dt><dt>4.22. <a href="#transform_to_rte">Converting a pile of waypoints to a GPX route</a></dt><dt>4.23. <a href="#transform_to_trk">Converting a pile of waypoints to a GPX track</a></dt><dt>4.24. <a href="#transform_rptdigits">Convert a GPX track to a GPX route, deleting the original track, using 2 digits for the generated numbers.</a></dt><dt>4.25. <a href="#transform_rptname">Convert a GPX track to a GPX route, deleting the original track, naming the generated points like the original track name.</a></dt><dt>4.26. <a href="#transform_del">Convert a GPX track to GPX waypoints, tossing the original track</a></dt></dl></div><div class="preface"><div class="titlepage"><div><div><h1 class="title"><a id="Introduction"></a>Introduction to GPSBabel</h1></div></div></div><div class="toc"><div class="toc-title">Table of Contents</div><dl class="toc"><dt><span class="section"><a href="#The_Problem">The Problem: Too many incompatible GPS file formats</a></span></dt><dt><span class="section"><a href="#The_Solution">The Solution</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="The_Problem"></a>The Problem: Too many incompatible GPS file formats</h2></div></div></div><p> There are simply too many gratuitously different file formats
to hold waypoint, track, and route information in various programs
used by computers and GPS receivers.  
<a class="ulink" href="http://www.topografix.com/gpx.asp" target="_top">GPX</a>  defines a
standard in XML to contain all the data, but there are too many
programs that don't understand it yet and too much data in 
alternate formats.
</p><p>
Perhaps you have an <a class="link" href="#fmt_magellanx" title="Magellan SD files (as for eXplorist) (magellanx)">Explorist 600</a> and your friend has a <a class="link" href="#fmt_garmin" title="Garmin serial/USB protocol (garmin)">StreetPilot 2720</a>.
You've collected a list of your favorite locations as waypoints and you'd
like to be able to share them.  Unfortunately, his copy of <a class="link" href="#fmt_gdb" title="Garmin MapSource - gdb (gdb)">Garmin Mapsource</a>
won't read data created by your copy of <a class="link" href="#fmt_mapsend" title="Magellan Mapsend (mapsend)">Magellan Mapsend DirectRoute</a>.  What you need
is a program that converts data bewteen the two programs.
</p><p>
GPSBabel actually solves that problem for you and much more...
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="The_Solution"></a>The Solution</h2></div></div></div><p> The original author of GPSBabel, <a class="ulink" href="/people/robertlipe.html" target="_top">Robert Lipe</a>, needed to convert waypoints between a couple of formats, so he
whipped up a converter and designed it upon an extensible foundation so
that it was easy to add new formats and made the program freely available. <a class="ulink" href="/people/index.html" target="_top">Many others</a> have contributed to the program since then.</p><p>  Most file formats added so far have taken under 200 
	lines of reasonable ISO C so they can be stamped
	out pretty trivially.  Formats that are ASCII text delimited in some
	fixed way can be added with no programming at all via our 
	<a class="link" href="#Styles" title="Appendix C. GPSBabel XCSV Style Files">style</a> mechanism.
	</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="Getting_and_Building"></a>Chapter 1. Getting or Building GPSBabel</h1></div></div></div><div class="toc"><div class="toc-title">Table of Contents</div><dl class="toc"><dt><span class="sect1"><a href="#Download">Downloading - the easy way.</a></span></dt><dt><span class="sect1"><a href="#Source">Building from source.</a></span></dt></dl></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="Download"></a>Downloading - the easy way.</h2></div></div></div><p> 
GPSBabel is distributed "ready to run" on most common 
operating systems via the 
<a class="ulink" href="http://www.gpsbabel.org/download.html" target="_top">download page</a>.
</p><p> As GPSBabel runs on a wide variety of operating systems,
be sure to visit the 
<a class="ulink" href="http://www.gpsbabel.org/osnotes.html" target="_top">OS-Specific notes</a> for
additional information.
</p></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="Source"></a>Building from source.</h2></div></div></div><p> 
 For operating systems where no binary is provided or if 
you want the latest development version, you will have to build it from
source.  The code should be compilable on any system with
ISO C++. It's tested on Linux, Mac OS/X, and Windows cross compilers.
Less frequently, someone will build on MSVC, FreeBSD, OpenBSD, Solaris, 
etc.   Both Clang/LLVM and GNU C++ are regularly exercised.
</p><p>
You can grab a release from the <a class="ulink" href="http://www.gpsbabel.org/download.html" target="_top">GPSBabel download page</a>, but if you're going to be doing any development, you'll find that working from the <a class="ulink" href="http://code.google.com/p/gpsbabel/source/checkout" target="_top">GPSBabel SVN tree</a> is easier.
</p><p>
For most cases, an anonymous checkout of the trunk is really all you need.
That can be done easily with the single command:
</p><p><strong class="userinput"><code>
  svn checkout http://gpsbabel.googlecode.com/svn/trunk/gpsbabel 
</code></strong></p><p>
  In most cases, the code is as simple to build as running:
</p><p><strong class="userinput"><code> ./configure &amp;&amp; make</code></strong></p><p><a class="ulink" href="http://qt-project.org" target="_top">Qt</a> 
is required for all builds.  Mac and Windows users can download
binaries from <a class="ulink" href="http://qt-project.org/downloads" target="_top">Qt Downloads</a>
CentOS users may need to 'yum install libqt4-core libqt4-dev'.
Fedora users may need to 'yum install qt4-devel'.
Ubuntu users may need to 'apt-get install libqt4-core libqt4-dev'.
</p><p><a class="ulink" href="http://libusb.sourceforge.net" target="_top">libusb</a> 
is recommended for OS/X and Linux if you want to use a USB Garmin or 
Delorme device.
Fedora users may need to 'yum install libusb-devel'.  Ubuntu users may
need to 'yum install libusb-dev'.
</p><p>There are additional flags that can be passed to configure to
 customize your build of GPSBabel.   
</p><p><strong class="userinput"><code>./configure --help</code></strong></p><p>
lists all the supported options, but of interest we have:</p><p>
 <code class="option">--disable-shapefile</code> Excludes the shapefile support.
</p><p>
  <code class="option">--disable-csv</code> Excludes all support for our something-separated formats.
</p><p>
  <code class="option">--disable-filters</code> Excludes all filter support.
</p><p>
  <code class="option">--enable-efence</code> Activate debugging mode for gpsbabel-debug.
</p><p>
  <code class="option">--with-doc=</code><code class="filename">dir</code> Specifies that the doc should be created and installed in <code class="filename">dir</code>.
</p><p>
  <code class="option">--without-libusb</code> Disables use of libusb, even it's it's available.
</p><p>
 <code class="option">--with-zlib=(included)|system|no</code> By default, we use our own version of zlib. If you specify <code class="option">system</code> the system zlib is used.  A value of <code class="option">no</code> (or --without-zlib) disables zlib.
</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="Usage"></a>Chapter 2. Usage</h1></div></div></div><div class="toc"><div class="toc-title">Table of Contents</div><dl class="toc"><dt><span class="sect1"><a href="#Invocation">Invocation</a></span></dt><dt><span class="sect1"><a href="#Suboptions">Suboptions</a></span></dt><dt><span class="sect1"><a href="#Advanced_Usage">Advanced Usage</a></span></dt><dt><span class="sect1"><a href="#Route_And_Track_Modes">Route and Track Modes</a></span></dt><dt><span class="sect1"><a href="#inifile">Working with predefined options</a></span></dt><dt><span class="sect1"><a href="#tracking">Realtime tracking</a></span></dt><dt><span class="sect1"><a href="#batchfile">Batch mode (command files)</a></span></dt><dt><span class="sect1"><a href="#all_options">List of Options</a></span></dt></dl></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="Invocation"></a>Invocation</h2></div></div></div><p>
If you're using GPSBabel, you will need to know how to do at least two things:
read data from a file, and write it to another file.  There are four basic
options you need to know to do those things:
</p><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Command</th><th>Meaning</th></tr></thead><tbody><tr class="seglistitem"><td class="seg"><code class="option">-i</code> <em class="parameter"><code>format</code></em></td><td class="seg">Set input format</td></tr><tr class="seglistitem"><td class="seg"><code class="option">-f</code> <em class="parameter"><code>filename</code></em></td><td class="seg">Read file</td></tr><tr class="seglistitem"><td class="seg"><code class="option">-o</code> <em class="parameter"><code>format</code></em></td><td class="seg">Set output format</td></tr><tr class="seglistitem"><td class="seg"><code class="option">-F</code> <em class="parameter"><code>filename</code></em></td><td class="seg">Write output file</td></tr></tbody></table></div><div class="important"><h3 class="title">Important</h3><p>
Case matters.  Notably <code class="option">-f</code> (lowercase) sets the <span class="emphasis"><em>input</em></span> file.  <code class="option"> -F</code> (uppercase) sets the <span class="emphasis"><em>output</em></span> file. 
</p></div><p>
The <em class="parameter"><code>format</code></em> parameters in the above list
refer to the names of formats or file types supported by GPSBabel. 
</p><p><strong class="userinput"><code>gpsbabel -? </code></strong></p><p>will always show you the supported file types.  In this document, the
various supported formats are listed in <a class="xref" href="#The_Formats" title="Chapter 3. The Formats">Chapter 3, <em>The Formats</em></a>.  The 
name that you would use on the command line follows the format name in 
parentheses.
</p><p>
Options are <span class="emphasis"><em>always</em></span> processed in order from left to right.
In practical terms, this means that things you want to read should appear
in the command before things you want to write.   This sometimes surprises
new users as adding options to turn on debugging at the end, for example, 
doesn't work as the debugging is turned on after all the interesting work is
done.   The reason for this strict ordering becomes more apparent once you
learn about mixing formats and filters.
</p><p>
The <em class="parameter"><code>filename</code></em> parameters specify the 
name of a file to be read or written.
</p><p>To use
         GPSBabel in its simplest form, just tell it what you're reading, where to read
         it from, what you're writing, and what to write it to.  For
         example:</p><p><strong class="userinput"><code>gpsbabel -i geo -f /tmp/geocaching.loc -o gpx -F /tmp/geocaching.gpx</code></strong></p><p>tells it to read the file <code class="filename">/tmp/geocaching.loc</code> in geocaching.com
         format and create a new file <code class="filename">/tmp/geocaching.gpx</code> in GPX format.   It's important to note that the names have nothing to do with the formats actually used.</p><p> This command will read from a Magellan unit attached
         to the first serial port on a Linux system (device names will
         vary on other OSes; typically COMx: on WIndows) and write them as a geocaching loc file.</p><div class="example"><a id="linux_download_from_magellan"></a><div class="example-title">Example 2.1. Command showing Linux download from Magellan serial and writing to .loc file</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i magellan -f /dev/ttyS0 -o geo -F mag.loc</code></strong></p></div></div><br class="example-break" /><p>This second command does the same on Microsoft Windows.</p><div class="example"><a id="windows_download_from_magellan"></a><div class="example-title">Example 2.2. Command showing Windows download from Magellan serial and writing to .loc file</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i magellan -f com1 -o geo -F mag.loc</code></strong></p></div></div><br class="example-break" /><p>Optionally, you may specify <em class="parameter"><code>-s</code></em> in any command line.  This
         causes the program to ignore any "short" names that may be
         present in the source data format and synthesize one from the
         long name.  This is particularly useful if you're writing to
         a target format that isn't the lowest common denominator but
         the source data was written for the lowest common
         denominator.  This is useful for writing data from geocaching.com
         to a GPS so my waypoints have "real" names instead of
         the 'GC1234' ones that are optimized for receivers of the lowest 
	common denominator.
         A geocacher using Linux with a Magellan receiver may thus find commands
         like this useful.</p><p><strong class="userinput"><code>gpsbabel -s -i geo -f geocaching.loc -o magellan -F /dev/ttyS0  </code></strong></p><p>His counterpart on Windows will find this equivalent</p><p><strong class="userinput"><code>gpsbabel -s -i geo -f geocaching.loc -o magellan -F com1</code></strong></p></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="Suboptions"></a>Suboptions</h2></div></div></div><p>
	  Many of the available format options in GPSBabel can themselves
	  take options.   While we try to make all the formats do the most
	  sensible thing possible without any extra options; this allows
	  great power and flexibility in the operation of the program.
	</p><p>
	  Suboptions are comma separated and immediately follow the option
	  itself. The available suboptions are listed on the individual 
	  format pages.  We'll make an example from <a class="xref" href="#fmt_kml" title="Google Earth (Keyhole) Markup Language (kml)">the section called “Google Earth (Keyhole) Markup Language (kml)”</a>:
	</p><p><strong class="userinput"><code>gpsbabel -i gpx -f file.gpx -o kml,deficon="file://myicon.png",lines=0 -F one.kml -o kml -F two.kml</code></strong></p><p>
	This command will read the GPX file <code class="filename">file.gpx</code>
	and create two KML files.    <code class="filename">one.kml</code> will
	have the given icon and no lines between track and routepoints.
	<code class="filename">two.kml</code> will be created with the defaults used
	in the KML writer.
	</p><p>
	Suboptions for the various formats allow you to change serial speeds,
	pass arguments to filters, change the type of file written, override
	icon defaults, and lots of other things.   The suboptions for each
	filetype are documented on the page in this document that describes
	the option itself.
	</p></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="Advanced_Usage"></a>Advanced Usage</h2></div></div></div><p>Argument are processed in the order they appear on the command
line and are translated internally into a pipeline that data flows
through when executed. Normally one would: </p><table border="0" summary="Simple list" class="simplelist"><tr><td>read from one input</td></tr><tr><td>optionally apply filters </td></tr><tr><td>write into one output</td></tr></table><p> but GPSBabel is flexible enough to allow more complicated
operations such as reading from several files (potentially of
different types), applying a filter, reading more data, then writing the
merged data to multiple destinations.
</p><p>The input file type remains unchanged until a new
         <em class="parameter"><code>-i</code></em> argument is seen.
         Files are read in the order they appear. So you could merge
         three input files into one output file with: </p><div class="example"><a id="merging_files"></a><div class="example-title">Example 2.3. Merging multiple files into one</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i geo -f 1.loc -f 2.loc -f 3.loc -o geo -F big.loc</code></strong></p></div></div><br class="example-break" /><p>You can merge files of different types:</p><div class="example"><a id="merging_different_types_of_files"></a><div class="example-title">Example 2.4. Merging multiple files of differing types.</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel  -i geo -f 1.loc -i gpx -f 2.gpx -i pcx 3.pcx  -o gpsutil -F big.gps</code></strong></p></div></div><br class="example-break" /><div class="example"><a id="multiple_writes"></a><div class="example-title">Example 2.5. Writing the same data in multiple output formats.</div><div class="example-contents"><p> You can write the same data in different output formats:</p><p><strong class="userinput"><code>gpsbabel -i geo -f 1.loc -o gpx -F 1.gpx -o pcx -F 1.wpt</code></strong></p></div></div><br class="example-break" /><p>If you want to change the character set of input or/and
         output side you can do this with the option <code class="option">-c
         &lt;character set&gt;</code>. You can get a complete list
         of supported character sets with "gpsbabel -l".  To change
         the character set on both sides you should do this:</p><p><strong class="userinput"><code>gpsbabel -i xcsv,style=foo.style -c latin1 -f foo -o xcsv,style=bar.style -c ms-ansi -F bar</code></strong></p><p>Note, that some formats have a fixed character set and ignore this option.</p></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="Route_And_Track_Modes"></a>Route and Track Modes</h2></div></div></div><p> Most formats supported by GPSBabel will make a reasonable attempt to work
         transparently with waypoints, tracks, and routes.  Some
         formats, like <a class="link" href="#fmt_garmin" title="Garmin serial/USB protocol (garmin)">garmin</a> and <a class="link" href="#fmt_magellan" title="Magellan SD files (as for Meridian) (magellan)">magellan</a> require the <em class="parameter"><code>-t</code></em> flag to work with tracks and
         <em class="parameter"><code>-r</code></em> to work with
         routes. <em class="parameter"><code>-w</code></em> is for
         waypoints, and is the default. So if you wanted to read all
         data from a Magellan Meridian GPS receiver into a gpx file, you might use a command
         like:</p><p><strong class="userinput"><code> gpsbabel -t -r -w -i magellan -f com1:  -o gpx -F backup.gpx</code></strong></p><p> Tracks and routes are advanced features and don't try
         to handle every possible hazard that can be encountered
         during a conversion.  If you're merging or converting files
         of similar limitations, things work very well.</p><p> Many of those hazards can be overcome with our filters
	 but there are often compromises to be made.  For example, if you
	 have a GPX route that contains  150 turn points but you're sending
	 the route to a GPS receiver that supports only 30 turnpoints, something has
	 to go.   One might use our 'simplify' filter to produce a route that
 	 retained the 30 most mathematically significant turnpoints but that
	 may not really be the route you had in mind.
	 </p><p> Tracks and routes will sometimes be converted to a
         list of waypoints when necessary, One example is when writing into one
         of the CSV formats. The inverse operation is not supported
         right now, so reading the converted track back from CSV will
         always result in a list of waypoints, not the original track.
</p><p> The presence of <em class="parameter"><code>-s</code></em> on the command line tends to
         creats havoc on tracks and routes since many of these formats
         rely on internal linkages between such points and renaming
         them may break those linkages.  In general, don't use
         <em class="parameter"><code>-s</code></em> when tracks or
         routes are present.
</p></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="inifile"></a>Working with predefined options</h2></div></div></div><p>
      GPSBabel can read a file on startup to set defaults for options. All
      module and filter options may be set this way. 
    </p><p>
      The format of the file is identical to the inifile-format often seen 
	on Windows.  Here is an example:
    </p><table border="0" summary="Simple list" class="simplelist"><tr><td>[Common format settings]</td></tr><tr><td>snupper=Y</td></tr><tr><td>snlen=10</td></tr><tr><td>[gpx]</td></tr><tr><td>gpxver=1.1</td></tr><tr><td>[magellan]</td></tr><tr><td>baud=115200</td></tr><tr><td>[tiger]</td></tr><tr><td>[Garmin categories]</td></tr><tr><td>; any # from 1 to 16</td></tr><tr><td>1=fixed waypoints</td></tr><tr><td>2=temporary waypoints</td></tr></table><p>
      Each section of the file starts with a '[section]' header followed by any
      number of lines formatted option=value. Leading and trailing whitespace
	will be
      automatically removed from header, option and value items. 

      Lines starting 
      with '#' or ';' will be treated as comments and ignored.
    </p><p>
	There are three optional sections.
	</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Common format settings.</p><p>  Any option from any of the formats listed here will be used by
		GPSBabel unless explicitly provided on the command line.
	</p></li><li class="listitem"><p>Common filter settings.</p><p>As above, but for filters.</p></li><li class="listitem"><p>Garmin categories</p><p>This allows you to give readable names to the numeric categories
	used internally in some Garmin devices and the Mapsource formats
	such as GDB and MPS.  This is information is also used by our GPX 
	and garmin_txt formats as well.</p></li></ul></div><p>
    </p><p>
      By default, GPSBabel tries at startup to load the file named 
	<code class="filename">gpsbabel.ini</code> from the following locations:
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>current working directory</p></li><li class="listitem"><p>Windows: all paths "APPDATA", "WINDIR", "SYSTEMROOT" declared in environment.</p></li><li class="listitem"><p>Unix like OS'ses: <code class="filename">${HOME}/.gpsbabel/</code>, <code class="filename">/usr/local/etc/</code> and <code class="filename">/etc/</code></p></li></ul></div><p>
      If the <code class="option">-p</code> option is specified, the above locations are not searched.
      Only the filename specified by that option will be used.
	</p><p>
      There may be situations where predefined values are not useable 
      (i.e. wrapper applications using GPSBabel in the background). 
       The inifile mechanism can be disabled with an empty filename.
    </p><p><strong class="userinput"><code>gpsbabel -p "" -i gpx -f something.gpx -o tiger -F -</code></strong></p></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tracking"></a>Realtime tracking</h2></div></div></div><p>
      Introduced in GPSBabel 1.3.1, we now have an <span class="emphasis"><em>experimental</em></span>  feature for realtime tracking via the new <code class="option">-T</code> option.  This reads position reports from selected formats and writes an output file when a position report is received. 
    </p><p>
      As of this writing, <a class="link" href="#fmt_garmin" title="Garmin serial/USB protocol (garmin)">Garmin's PVT
        protocol</a>  and 
      <a class="link" href="#fmt_nmea" title="NMEA 0183 sentences (nmea)">NMEA</a>  are supported 
	  inputs. KML, NMEA, and the various XCSV formats are supported on 
	  output.   Additional formats may be added by interested parties 
	  later.
    </p><div class="example"><a id="realtime_reading"></a><div class="example-title">Example 2.6. Read realtime positioning from Garmin USB, write to Keyhole Markup</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -T -i garmin -f usb: -o kml -F xxx.kml</code></strong></p><p>
   	  Will read the USB-connected Garmin and rewrite 'xxx.kml' atomically,
          suitable for a self-refreshing network link in Google Earth.
        </p></div></div><br class="example-break" /><div class="example"><a id="realtime_reading_wintec"></a><div class="example-title">Example 2.7. Read realtime positioning from Wintec WBT-201 via Bluetooth on Mac, write to Keyhole Markup</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -T -i nmea -f /dev/cu.G-Rays2-SPPslave-1 -o kml -F xxx.kml</code></strong></p><p>
    Will read the Wintec WBT-201 via Bluetooth, using the name that
    the Mac assigned it, and rewrite 'xxx.kml' atomically,
          suitable for a self-refreshing network link in Google Earth.
        </p></div></div><br class="example-break" /><p>
          Be sure to substitute an device name appropriate for your device
          and OS, such as <code class="filename">/dev/cu.usbserial</code> or
          <code class="filename">/dev/cu.BT-GPS-37A695-BT-GPSCOM-1</code>
          for Mac, <code class="filename">COM23:</code> for Windows, or
          <code class="filename">usb:</code> for
          <a class="link" href="#fmt_garmin" title="Garmin serial/USB protocol (garmin)">Garmin USB</a>.    These names
            (except the "usb:" parlance for Garmin USB) are assigned by
            your operating system.

        </p></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="batchfile"></a>Batch mode (command files)</h2></div></div></div><p>
	In addition to reading arguments from the command line, GPSBabel can
	read directions from batch (or command) files via the <code class="option">-b</code> option.
  </p><p>
    These files are ideal for holding long command lines, long file lists, complex filters 
    and so on. You can use all GPSBabel options and combinations when writing
    such files. Nesting batch files by using the <code class="option">-b</code> option within a batch file is supported.
  </p><p>
  Here is an example demonstrating segmenting a large command line
  by placing the input and filtering directives in a file called 'all_my_files'.
  </p><p><strong class="userinput"><code>gpsbabel -b all_my_files -o gdb -F all_my_tracks.gdb</code></strong></p><p>
    'all_my_files' could look like this:
  </p><table border="0" summary="Simple list" class="simplelist"><tr><td>-i gpx</td></tr><tr><td>-f saxony_in_summer_2004.gpx -f austria_2005.gpx</td></tr><tr><td>-i gdb</td></tr><tr><td>-f croatia_2006.gdb</td></tr><tr><td>-x nuketypes,waypoints,routes</td></tr><tr><td>-x track,pack,split,title="LOG # %Y%m%d"</td></tr></table></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="all_options"></a>List of Options</h2></div></div></div><p>
   The complete list of available options to GPSBabel can be obtained by
   running <span class="command"><strong>gpsbabel -h</strong></span>.  While there are a number of
   options, most people will not use most of them, so don't be intimidated.
  </p><p><code class="option">-p</code> Read preferences file.   On startup, GPSBabel will look for a file named <code class="filename">gpsbabel.ini</code> containing preferences you have provided.  This option lets you pick a different files.  See <a class="xref" href="#inifile" title="Working with predefined options">the section called “Working with predefined options”</a> for more info.</p><p><code class="option">-s</code> Write "smart" names.  This option influences some - but not all - of our writers to try to build "smart" waypoint names.   For example, in modules that know about geocaching, it may replace "GC1234" with the actual name of the geocache.</p><p><code class="option">-r</code> Work on routes.  This option has a subtly different meaning in different cases.  As the very first formats in GPSBabel were for serial GPSes and routes and tracks were large and thus time-consuming to transfer, the default was waypoints only with this option to turn on the extra data.   Some of our file formats use this option to mean "work only on routes, even if you have tracks/waypoints", but we're trying to discourage that behavior and in most cases, consider it a bug. </p><p><code class="option">-t</code> Work on tracks.  See <code class="option">-r</code> for excuses. </p><p><code class="option">-w</code> Work on waypoints.  This is the default. </p><p><code class="option">-T</code> Enable Realtime tracking. This option isn't supported by the majority of our file formats, but repeatedly reads location from a GPS and writes it to a file as described in <a class="xref" href="#tracking" title="Realtime tracking">the section called “Realtime tracking”</a></p><p><code class="option">-b</code> Process batch file. In addition to reading arguments from the command line, we can read them from files containing lists of commands as described in <a class="xref" href="#batchfile" title="Batch mode (command files)">the section called “Batch mode (command files)”</a> </p><p><code class="option">-c</code> Select character set. This option lets you chose the character set.  You can get a list of supported character sets via <code class="option">-l</code> </p><p><code class="option">-N</code> Control "smart" output.   The <code class="option">-N</code> actually has two subtoptions, <code class="option">-Ni</code> and <code class="option">-Ns</code>.   This lets you control whether a given writer will choose smart icons and names, respectively.   The option <code class="option">-N</code> by itself selects both.    </p><p><code class="option">-x filter</code> Run filter. This option lets use use one of of our many data filters. Position of this in the command line does matter - remember, we process left to right.</p><p><code class="option">-D</code> Enable debugging.   Not all formats support this.  It's typically better supported by the various protocol modules because they just plain need more debugging.   This option may be followed by a number.   Zero means no debugging.  Larger numbers mean more debugging. </p><p><code class="option">-l</code> Print character sets.   </p><p><code class="option">-h</code><code class="option">-?</code> Print help. </p><p><code class="option">-V</code> Print version number. </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="The_Formats"></a>Chapter 3. The Formats</h1></div></div></div><div class="toc"><div class="toc-title">Table of Contents</div><dl class="toc"><dt><span class="section"><a href="#fmt_xcsv">? Character Separated Values (xcsv)</a></span></dt><dt><span class="section"><a href="#fmt_alantrl">Alan Map500 tracklogs (.trl) (alantrl)</a></span></dt><dt><span class="section"><a href="#fmt_alanwpr">Alan Map500 waypoints and routes (.wpr) (alanwpr)</a></span></dt><dt><span class="section"><a href="#fmt_tabsep">All database fields on one tab-separated line (tabsep)</a></span></dt><dt><span class="section"><a href="#fmt_baroiq">Brauniger IQ Series Barograph Download (baroiq)</a></span></dt><dt><span class="section"><a href="#fmt_bushnell_trl">Bushnell GPS Trail file (bushnell_trl)</a></span></dt><dt><span class="section"><a href="#fmt_bushnell">Bushnell GPS Waypoint file (bushnell)</a></span></dt><dt><span class="section"><a href="#fmt_cambridge">Cambridge/Winpilot glider software (cambridge)</a></span></dt><dt><span class="section"><a href="#fmt_cst">CarteSurTable data file (cst)</a></span></dt><dt><span class="section"><a href="#fmt_v900">Columbus/Visiontac V900 files (.csv) (v900)</a></span></dt><dt><span class="section"><a href="#fmt_csv">Comma separated values (csv)</a></span></dt><dt><span class="section"><a href="#fmt_compegps">CompeGPS data files (.wpt/.trk/.rte) (compegps)</a></span></dt><dt><span class="section"><a href="#fmt_custom">Custom "Everything" Style (custom)</a></span></dt><dt><span class="section"><a href="#fmt_iblue747">Data Logger iBlue747 csv (iblue747)</a></span></dt><dt><span class="section"><a href="#fmt_iblue757">Data Logger iBlue757 csv (iblue757)</a></span></dt><dt><span class="section"><a href="#fmt_an1">DeLorme .an1 (drawing) file (an1)</a></span></dt><dt><span class="section"><a href="#fmt_gpl">DeLorme GPL (gpl)</a></span></dt><dt><span class="section"><a href="#fmt_delbin">DeLorme PN-20/PN-30/PN-40 USB protocol (delbin)</a></span></dt><dt><span class="section"><a href="#fmt_saplus">DeLorme Street Atlas Plus (saplus)</a></span></dt><dt><span class="section"><a href="#fmt_saroute">DeLorme Street Atlas Route (saroute)</a></span></dt><dt><span class="section"><a href="#fmt_xmap">DeLorme XMap HH Native .WPT (xmap)</a></span></dt><dt><span class="section"><a href="#fmt_xmap2006">DeLorme XMap/SAHH 2006 Native .TXT (xmap2006)</a></span></dt><dt><span class="section"><a href="#fmt_xmapwpt">DeLorme XMat HH Street Atlas USA .WPT (PPC) (xmapwpt)</a></span></dt><dt><span class="section"><a href="#fmt_destinator_itn">Destinator Itineraries (.dat) (destinator_itn)</a></span></dt><dt><span class="section"><a href="#fmt_destinator_poi">Destinator Points of Interest (.dat) (destinator_poi)</a></span></dt><dt><span class="section"><a href="#fmt_destinator_trl">Destinator TrackLogs (.dat) (destinator_trl)</a></span></dt><dt><span class="section"><a href="#fmt_easygps">EasyGPS binary format (easygps)</a></span></dt><dt><span class="section"><a href="#fmt_exif">Embedded Exif-GPS data (.jpg) (exif)</a></span></dt><dt><span class="section"><a href="#fmt_enigma">Enigma binary waypoint file (.ert) (enigma)</a></span></dt><dt><span class="section"><a href="#fmt_igc">FAI/IGC Flight Recorder Data Format (igc)</a></span></dt><dt><span class="section"><a href="#fmt_garmin_fit">Flexible and Interoperable Data Transfer (FIT) Activity file (garmin_fit)</a></span></dt><dt><span class="section"><a href="#fmt_flysight">FlySight GPS File (flysight)</a></span></dt><dt><span class="section"><a href="#fmt_gpssim">Franson GPSGate Simulation (gpssim)</a></span></dt><dt><span class="section"><a href="#fmt_fugawi">Fugawi (fugawi)</a></span></dt><dt><span class="section"><a href="#fmt_g7towin">G7ToWin data files (.g7t) (g7towin)</a></span></dt><dt><span class="section"><a href="#fmt_garmin301">Garmin 301 Custom position and heartrate (garmin301)</a></span></dt><dt><span class="section"><a href="#fmt_garmin_g1000">Garmin G1000 datalog input filter file (garmin_g1000)</a></span></dt><dt><span class="section"><a href="#fmt_glogbook">Garmin Logbook XML (glogbook)</a></span></dt><dt><span class="section"><a href="#fmt_gdb">Garmin MapSource - gdb (gdb)</a></span></dt><dt><span class="section"><a href="#fmt_mapsource">Garmin MapSource - mps (mapsource)</a></span></dt><dt><span class="section"><a href="#fmt_garmin_txt">Garmin MapSource - txt (tab delimited) (garmin_txt)</a></span></dt><dt><span class="section"><a href="#fmt_pcx">Garmin PCX5 (pcx)</a></span></dt><dt><span class="section"><a href="#fmt_garmin_poi">Garmin POI database (garmin_poi)</a></span></dt><dt><span class="section"><a href="#fmt_garmin_gpi">Garmin Points of Interest (.gpi) (garmin_gpi)</a></span></dt><dt><span class="section"><a href="#fmt_garmin">Garmin serial/USB protocol (garmin)</a></span></dt><dt><span class="section"><a href="#fmt_gtrnctr">Garmin Training Center (.tcx) (gtrnctr)</a></span></dt><dt><span class="section"><a href="#fmt_gtrnctr1">Garmin Training Center (.xml) (gtrnctr)</a></span></dt><dt><span class="section"><a href="#fmt_geo">Geocaching.com .loc (geo)</a></span></dt><dt><span class="section"><a href="#fmt_ggv_ovl">Geogrid-Viewer ascii overlay file (.ovl) (ggv_ovl)</a></span></dt><dt><span class="section"><a href="#fmt_ggv_log">Geogrid-Viewer tracklogs (.log) (ggv_log)</a></span></dt><dt><span class="section"><a href="#fmt_geonet">GEOnet Names Server (GNS) (geonet)</a></span></dt><dt><span class="section"><a href="#fmt_dg-100">GlobalSat DG-100/BT-335 Download (dg-100)</a></span></dt><dt><span class="section"><a href="#fmt_dg-200">GlobalSat DG-200 Download (dg-200)</a></span></dt><dt><span class="section"><a href="#fmt_googledir">Google Directions XML (googledir)</a></span></dt><dt><span class="section"><a href="#fmt_kml">Google Earth (Keyhole) Markup Language (kml)</a></span></dt><dt><span class="section"><a href="#fmt_google">Google Maps XML (google)</a></span></dt><dt><span class="section"><a href="#fmt_gnav_trl">Google Navigator Tracklines (.trl) (gnav_trl)</a></span></dt><dt><span class="section"><a href="#fmt_gopal">GoPal GPS track log (.trk) (gopal)</a></span></dt><dt><span class="section"><a href="#fmt_land_air_sea">GPS Tracking Key Pro text (land_air_sea)</a></span></dt><dt><span class="section"><a href="#fmt_gtm">GPS TrackMaker (gtm)</a></span></dt><dt><span class="section"><a href="#fmt_arc">GPSBabel arc filter file (arc)</a></span></dt><dt><span class="section"><a href="#fmt_gpsdrive">GpsDrive Format (gpsdrive)</a></span></dt><dt><span class="section"><a href="#fmt_gpsdrivetrack">GpsDrive Format for Tracks (gpsdrivetrack)</a></span></dt><dt><span class="section"><a href="#fmt_gpsman">GPSman (gpsman)</a></span></dt><dt><span class="section"><a href="#fmt_gpsutil">gpsutil (gpsutil)</a></span></dt><dt><span class="section"><a href="#fmt_gpx">GPX XML (gpx)</a></span></dt><dt><span class="section"><a href="#fmt_hiketech">HikeTech (hiketech)</a></span></dt><dt><span class="section"><a href="#fmt_holux">Holux (gm-100) .wpo Format (holux)</a></span></dt><dt><span class="section"><a href="#fmt_m241-bin">Holux M-241 (MTK based) Binary File Format (m241-bin)</a></span></dt><dt><span class="section"><a href="#fmt_m241">Holux M-241 (MTK based) download (m241)</a></span></dt><dt><span class="section"><a href="#fmt_vpl">Honda/Acura Navigation System VP Log File Format (vpl)</a></span></dt><dt><span class="section"><a href="#fmt_html">HTML Output (html)</a></span></dt><dt><span class="section"><a href="#fmt_humminbird_ht">Humminbird tracks (.ht) (humminbird_ht)</a></span></dt><dt><span class="section"><a href="#fmt_humminbird">Humminbird waypoints and routes (.hwr) (humminbird)</a></span></dt><dt><span class="section"><a href="#fmt_ignrando">IGN Rando track files (ignrando)</a></span></dt><dt><span class="section"><a href="#fmt_igo2008_poi">iGO2008 points of interest (.upoi) (igo2008_poi)</a></span></dt><dt><span class="section"><a href="#fmt_igo8">IGO8 .trk (igo8)</a></span></dt><dt><span class="section"><a href="#fmt_jtr">Jelbert GeoTagger data file (jtr)</a></span></dt><dt><span class="section"><a href="#fmt_jogmap">Jogmap.de XML format (jogmap)</a></span></dt><dt><span class="section"><a href="#fmt_kompass_tk">Kompass (DAV) Track (.tk) (kompass_tk)</a></span></dt><dt><span class="section"><a href="#fmt_kompass_wp">Kompass (DAV) Waypoints (.wp) (kompass_wp)</a></span></dt><dt><span class="section"><a href="#fmt_psitrex">KuDaTa PsiTrex text (psitrex)</a></span></dt><dt><span class="section"><a href="#fmt_lowranceusr">Lowrance USR (lowranceusr)</a></span></dt><dt><span class="section"><a href="#fmt_lowranceusr4">Lowrance USR version 4 (lowranceusr4)</a></span></dt><dt><span class="section"><a href="#fmt_maggeo">Magellan Explorist Geocaching (maggeo)</a></span></dt><dt><span class="section"><a href="#fmt_mapsend">Magellan Mapsend (mapsend)</a></span></dt><dt><span class="section"><a href="#fmt_magellanx">Magellan SD files (as for eXplorist) (magellanx)</a></span></dt><dt><span class="section"><a href="#fmt_magellan">Magellan SD files (as for Meridian) (magellan)</a></span></dt><dt><span class="section"><a href="#fmt_magellan1">Magellan serial protocol (magellan)</a></span></dt><dt><span class="section"><a href="#fmt_ik3d">MagicMaps IK3D project file (.ikt) (ik3d)</a></span></dt><dt><span class="section"><a href="#fmt_mainnav">Mainnav (mainnav)</a></span></dt><dt><span class="section"><a href="#fmt_tef">Map&amp;amp;Guide 'TourExchangeFormat' XML (tef)</a></span></dt><dt><span class="section"><a href="#fmt_mapasia_tr7">MapAsia track file (.tr7) (mapasia_tr7)</a></span></dt><dt><span class="section"><a href="#fmt_mapbar">Mapbar (China) navigation track for Sonim Xp3300 (mapbar)</a></span></dt><dt><span class="section"><a href="#fmt_mapfactor">Mapfactor Navigator (mapfactor)</a></span></dt><dt><span class="section"><a href="#fmt_mapconverter">Mapopolis.com Mapconverter CSV (mapconverter)</a></span></dt><dt><span class="section"><a href="#fmt_mxf">MapTech Exchange Format (mxf)</a></span></dt><dt><span class="section"><a href="#fmt_mtk_locus">MediaTek Locus (mtk_locus)</a></span></dt><dt><span class="section"><a href="#fmt_mmo">Memory-Map Navigator overlay files (.mmo) (mmo)</a></span></dt><dt><span class="section"><a href="#fmt_s_and_t">Microsoft Streets and Trips 2002-2007 (s_and_t)</a></span></dt><dt><span class="section"><a href="#fmt_miniHomer">MiniHomer, a skyTraq Venus 6 based logger (download tracks, waypoints and get/set POI) (miniHomer)</a></span></dt><dt><span class="section"><a href="#fmt_garmin_xt">Mobile Garmin XT Track files (garmin_xt)</a></span></dt><dt><span class="section"><a href="#fmt_motoactv">Motoactiv CSV (motoactv)</a></span></dt><dt><span class="section"><a href="#fmt_bcr">Motorrad Routenplaner (Map&amp;amp;Guide) .bcr files (bcr)</a></span></dt><dt><span class="section"><a href="#fmt_mtk-bin">MTK Logger (iBlue 747,...) Binary File Format (mtk-bin)</a></span></dt><dt><span class="section"><a href="#fmt_mtk">MTK Logger (iBlue 747,Qstarz BT-1000,...) download (mtk)</a></span></dt><dt><span class="section"><a href="#fmt_tpg">National Geographic Topo .tpg (waypoints) (tpg)</a></span></dt><dt><span class="section"><a href="#fmt_tpo2">National Geographic Topo 2.x .tpo (tpo2)</a></span></dt><dt><span class="section"><a href="#fmt_tpo3">National Geographic Topo 3.x/4.x .tpo (tpo3)</a></span></dt><dt><span class="section"><a href="#fmt_navicache">Navicache.com XML (navicache)</a></span></dt><dt><span class="section"><a href="#fmt_nmn4">Navigon Mobile Navigator .rte files (nmn4)</a></span></dt><dt><span class="section"><a href="#fmt_navigonwpt">Navigon Waypoints (navigonwpt)</a></span></dt><dt><span class="section"><a href="#fmt_navilink">NaviGPS GT-11/BGT-11 Download (navilink)</a></span></dt><dt><span class="section"><a href="#fmt_sbp">NaviGPS GT-31/BGT-31 datalogger (.sbp) (sbp)</a></span></dt><dt><span class="section"><a href="#fmt_sbn">NaviGPS GT-31/BGT-31 SiRF binary logfile (.sbn) (sbn)</a></span></dt><dt><span class="section"><a href="#fmt_naviguide">Naviguide binary route file (.twl) (naviguide)</a></span></dt><dt><span class="section"><a href="#fmt_navitel_trk">Navitel binary track (.bin) (navitel_trk)</a></span></dt><dt><span class="section"><a href="#fmt_dna">Navitrak DNA marker format (dna)</a></span></dt><dt><span class="section"><a href="#fmt_netstumbler">NetStumbler Summary File (text) (netstumbler)</a></span></dt><dt><span class="section"><a href="#fmt_nima">NIMA/GNIS Geographic Names File (nima)</a></span></dt><dt><span class="section"><a href="#fmt_nmea">NMEA 0183 sentences (nmea)</a></span></dt><dt><span class="section"><a href="#fmt_lmx">Nokia Landmark Exchange (lmx)</a></span></dt><dt><span class="section"><a href="#fmt_osm">OpenStreetMap data files (osm)</a></span></dt><dt><span class="section"><a href="#fmt_ozi">OziExplorer (ozi)</a></span></dt><dt><span class="section"><a href="#fmt_pocketfms_bc">PocketFMS breadcrumbs (pocketfms_bc)</a></span></dt><dt><span class="section"><a href="#fmt_pocketfms_fp">PocketFMS flightplan (.xml) (pocketfms_fp)</a></span></dt><dt><span class="section"><a href="#fmt_pocketfms_wp">PocketFMS waypoints (.txt) (pocketfms_wp)</a></span></dt><dt><span class="section"><a href="#fmt_raymarine">Raymarine Waypoint File (.rwf) (raymarine)</a></span></dt><dt><span class="section"><a href="#fmt_ricoh">Ricoh GPS Log File (ricoh)</a></span></dt><dt><span class="section"><a href="#fmt_cup">See You flight analysis data (cup)</a></span></dt><dt><span class="section"><a href="#fmt_skyforce">Skymap / KMD150 ascii files (skyforce)</a></span></dt><dt><span class="section"><a href="#fmt_skytraq">SkyTraq Venus based loggers (download) (skytraq)</a></span></dt><dt><span class="section"><a href="#fmt_skytraq-bin">SkyTraq Venus based loggers Binary File Format (skytraq-bin)</a></span></dt><dt><span class="section"><a href="#fmt_subrip">SubRip subtitles for video mapping (.srt) (subrip)</a></span></dt><dt><span class="section"><a href="#fmt_stmsdf">Suunto Trek Manager (STM) .sdf files (stmsdf)</a></span></dt><dt><span class="section"><a href="#fmt_stmwpp">Suunto Trek Manager (STM) WaypointPlus files (stmwpp)</a></span></dt><dt><span class="section"><a href="#fmt_xol">Swiss Map 25/50/100 (.xol) (xol)</a></span></dt><dt><span class="section"><a href="#fmt_openoffice">Tab delimited fields useful for OpenOffice, Ploticus etc. (openoffice)</a></span></dt><dt><span class="section"><a href="#fmt_teletype">Teletype [ Get Jonathon Johnson to describe (teletype)</a></span></dt><dt><span class="section"><a href="#fmt_text">Textual Output (text)</a></span></dt><dt><span class="section"><a href="#fmt_tomtom_itn">TomTom Itineraries (.itn) (tomtom_itn)</a></span></dt><dt><span class="section"><a href="#fmt_tomtom_itn_places">TomTom Places Itineraries (.itn) (tomtom_itn_places)</a></span></dt><dt><span class="section"><a href="#fmt_tomtom_asc">TomTom POI file (.asc) (tomtom_asc)</a></span></dt><dt><span class="section"><a href="#fmt_tomtom">TomTom POI file (.ov2) (tomtom)</a></span></dt><dt><span class="section"><a href="#fmt_tmpro">TopoMapPro Places File (tmpro)</a></span></dt><dt><span class="section"><a href="#fmt_dmtlog">TrackLogs digital mapping (.trl) (dmtlog)</a></span></dt><dt><span class="section"><a href="#fmt_tiger">U.S. Census Bureau Tiger Mapping Service (tiger)</a></span></dt><dt><span class="section"><a href="#fmt_unicsv">Universal csv with field structure in first line (unicsv)</a></span></dt><dt><span class="section"><a href="#fmt_vcard">Vcard Output (for iPod) (vcard)</a></span></dt><dt><span class="section"><a href="#fmt_vidaone">VidaOne GPS for Pocket PC (.gpb) (vidaone)</a></span></dt><dt><span class="section"><a href="#fmt_vitosmt">Vito Navigator II tracks (vitosmt)</a></span></dt><dt><span class="section"><a href="#fmt_vitovtt">Vito SmartMap tracks (.vtt) (vitovtt)</a></span></dt><dt><span class="section"><a href="#fmt_wfff">WiFiFoFum 2.0 for PocketPC XML (wfff)</a></span></dt><dt><span class="section"><a href="#fmt_wintec_tes">Wintec TES file (wintec_tes)</a></span></dt><dt><span class="section"><a href="#fmt_wbt-bin">Wintec WBT-100/200 Binary File Format (wbt-bin)</a></span></dt><dt><span class="section"><a href="#fmt_wbt">Wintec WBT-100/200 GPS Download (wbt)</a></span></dt><dt><span class="section"><a href="#fmt_wbt-tk1">Wintec WBT-201/G-Rays 2 Binary File Format (wbt-tk1)</a></span></dt><dt><span class="section"><a href="#fmt_itracku">XAiOX iTrackU Logger (itracku)</a></span></dt><dt><span class="section"><a href="#fmt_itracku-bin">XAiOX iTrackU Logger Binary File Format (itracku-bin)</a></span></dt><dt><span class="section"><a href="#fmt_yahoo">Yahoo Geocode API data (yahoo)</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_xcsv"></a>? Character Separated Values (xcsv)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is a very flexible module that can be used to read or write 
nearly any plain-text record-based waypoint file.  This flexibility is 
achieved by combining this format with "style" files that describe the 
format of the waypoint files.
</p><p>
There are several formats built in to GPSBabel that use the underlying xcsv 
machinery.  Each of those formats takes the same options as the xcsv format,
with the obvious exception of the <code class="option">style</code> option.  
Those formats are all based on style files that can be found in 
the "style" directory in the GPSBabel source distribution.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_xcsv_o_style"></a><code class="option">style</code> option</h3></div></div></div><p>
      Full path to XCSV style file.
    </p><p>
This option specifies the style file that defines the records to be read on
input or written on output.  This is not a valid option for the various
built-in xcsv-based styles; they have prebuilt style definitions.
</p><p>
For information on the format of xcsv style files, see 
<a class="xref" href="#Styles" title="Appendix C. GPSBabel XCSV Style Files">Appendix C, <em>GPSBabel XCSV Style Files</em></a>.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_xcsv_o_snlen"></a><code class="option">snlen</code> option</h3></div></div></div><p>
      Max synthesized shortname length.
    </p><p>
This option specifies the maximum allowable length for a short name on
output.  This option overrides the style file.
</p><p>
Valid values for this option are 0 (off) and 1 (on).
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_xcsv_o_snwhite"></a><code class="option">snwhite</code> option</h3></div></div></div><p>
      Allow whitespace synth. shortnames.
    </p><p>
When this option is specified, GPSBabel will allow whitespace (spaces or tabs)
in generated short names.  This option overrides the style file.
</p><p>
Valid values for this option are 0 (off) and 1 (on).
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_xcsv_o_snupper"></a><code class="option">snupper</code> option</h3></div></div></div><p>
      UPPERCASE synth. shortnames.
    </p><p>
When this option is specified, GPSBabel will make all short names contain
only UPPERCASE characters.  This option overrides the style file.
</p><p>
Valid values for this option are 0 (off) and 1 (on).
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_xcsv_o_snunique"></a><code class="option">snunique</code> option</h3></div></div></div><p>
      Make synth. shortnames unique.
    </p><p>
When this option is specified, GPSBabel will ensure that all short names are
unique within the output file.  This option overrides the style file.
</p><p>
Valid values for this option are 0 (off) and 1 (on).
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_xcsv_o_urlbase"></a><code class="option">urlbase</code> option</h3></div></div></div><p>
      Basename prepended to URL on output.
    </p><p>
This option specifies the base name to prepend to a URL on output.  This 
might be useful if an input file contains URLs in a relative format and you
need them to be in an absolute format.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_xcsv_o_prefer_shortnames"></a><code class="option">prefer_shortnames</code> option</h3></div></div></div><p>
      Use shortname instead of description.
    </p><p>
This option causes GPSBabel to use the short name of the waypoint instead
of the description.  This overrides the style file.
</p><p>
Valid values for this option are 0 (off) and 1 (on).
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_xcsv_o_datum"></a><code class="option">datum</code> option</h3></div></div></div><p>
      GPS datum (def. WGS 84).
    </p><p>
This option specifies the GPS datum to be used on read or write. Valid values for this 
option are listed in <a class="xref" href="#Datums" title="Appendix A. Supported Datums">Appendix A, <em>Supported Datums</em></a>.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_alantrl"></a>Alan Map500 tracklogs (.trl) (alantrl)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
GPSBabel supports .wpr and .trl files for Alan Map500 devices running operating 
system versions 2.xx.
</p><p>
.trl contain files tracklogs. If you use a CF-Card based
operating system, tracklog files must have a <code class="filename">.TRL</code> extension when
copied to the CF-Card. The default filename is <code class="filename">TEMP_TRK.TRL</code>.
Only one <code class="filename">.TRL</code> file may be present.
</p><p>
Alan's operating system 3.0 for Map500 is not supported yet.
At the time of this writing, OS3 is still beta.
Documentation on the new dataformats is sparse.
</p><p>
The Alan Map500 handheld GPSr is identical to the Holux GM101.
This GPSBabel module has only been tested against the Alan Map500.
Still, if you use a GM101, GPSBabel will probably be able to convert
your waypoints, routes and tracklogs.
</p><p>
For more information on the Alan Map500 visit
<a class="ulink" href="http://www.alan-electronics.de/gps/gpsuebersicht.php3" target="_top">Alan Germany</a>. There is very informative <a class="ulink" href="http://www.alan-germany.de/forum/index.php" target="_top">forum</a>, too. The forum language is German but posts in English will be answered, too.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_alanwpr"></a>Alan Map500 waypoints and routes (.wpr) (alanwpr)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>
GPSBabel supports .wpr and .trl files for Alan Map500 devices running operating 
system versions 2.xx.
</p><p>
.wpr files contain waypoints and routes. If you use a CF-Card based
operating system, waypoint files must have a <code class="filename">.WPR</code> extension when
copied to the CF-Card. The default filename is <code class="filename">TEMPWPRT.WPR</code>.
Only one <code class="filename">.WPR</code> file may be present.
</p><p>
Alan's operating system 3.0 for Map500 is not supported yet.
At the time of this writing, OS3 is still beta.
Documentation on the new dataformats is sparse.
</p><p>
The Alan Map500 handheld GPSr is identical to the Holux GM101.
This GPSBabel module has only been tested against the Alan Map500.
Still, if you use a GM101, GPSBabel will probably be able to convert
your waypoints, routes and tracklogs.
</p><p>
For more information on the Alan Map500 visit
<a class="ulink" href="http://www.alan-electronics.de/gps/gpsuebersicht.php3" target="_top">Alan Germany</a>. There is very informative <a class="ulink" href="http://www.alan-germany.de/forum/index.php" target="_top">forum</a>, too. Forum language is German but posts in English will be answered,
too.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_tabsep"></a>All database fields on one tab-separated line (tabsep)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
This format, like the <a class="link" href="#fmt_custom" title="Custom &quot;Everything&quot; Style (custom)">custom</a> format, is
mainly used for the purpose of testing GPSBabel.  It is supposed to contain
one field for each piece of information supported by the 
<a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a> format writer, but it may not be entirely
in sync with the documentation at <a class="xref" href="#Styles" title="Appendix C. GPSBabel XCSV Style Files">Appendix C, <em>GPSBabel XCSV Style Files</em></a>.
</p><p>
For a list of fields, see the style/tabsep.style file in the GPSBabel source
distribution.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_baroiq"></a>Brauniger IQ Series Barograph Download (baroiq)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>Serial download protocol for the <a class="ulink" href="http://www.brauniger.com" target="_top">Brauniger</a> IQ series of
barograph recording flight instruments.  This format creates a 
track of altitude vs time which can be merged with a GPS track 
of the same flight to create a three dimensional IGC file. </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_bushnell_trl"></a>Bushnell GPS Trail file (bushnell_trl)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
This format supports tracks from 
<a class="ulink" href="http://www.bushnell.com/products/gps/" target="_top">Bushnell GPS</a> 
receivers, notably the <span class="productname">Onix 400</span>™.
</p><p>
This format reads individual .trl files as written by the GPS.  As this is
a reverse-engineered format, it's not understood how (or even if) long 
tracks, in 
particular, span multiple files so initially this format is most effective
on tracks under a few thousand points.
</p><p>
  When writing tracks, a maximum of 4502 points is supported as this is the
  most we believe these units can represent in a track.
</p><p>
  The output base filename, converted to uppercase and stripped of 
  everything but letters and digits, is used for the trail name inside 
  the file itself.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_bushnell"></a>Bushnell GPS Waypoint file (bushnell)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format supports reading and writing wayponts to 
<a class="ulink" href="http://www.bushnell.com/products/gps/" target="_top">Bushnell GPS</a> 
receivers, notably the <span class="productname">Onix 400</span>™.
</p><p>
It's an oddity for many GPSBabel norms that this format requires each 
waypoint be in a separate file.   Our "output filename" argument, -F is 
modified to take an "output filename template".   The output filename
you specify will have a dash, and a sequentially increasing integer,
and the ".wpt" extension appended to it.  When the names are shown on
the GPS itself, the shortnames from the source format are used and not these
"made up" names.
</p><div class="example"><a id="bushnell-output"></a><div class="example-title">Example 3.1. Command showing writing to Bushnell files</div><div class="example-contents"><p>
Consider the case where 'whatever.gpx' holds three waypoints.
<strong class="userinput"><code>
  gpsbabel -i gpx -f whatever.gpx -o bushnell -F /Volumes/Bushnell/WAYPOINT/whatever
</code></strong>
will result in "whatever-0.wpt", "whatever-1.wpt", and "whatever-2.wpt" being
created in that directory.
Windows users may prefer the spelling:
<strong class="userinput"><code>
  gpsbabel -i gpx -f whatever.gpx -o bushnell -F e:/WAYPOINT/whatever
</code></strong>
</p><p>
At least for the 200CR, the directory name used by the device is "WAYPOINT"
in the root directory.  It's also worth mentioning that its USB Mass Storage
protocol appears to not work on (at least) Snow Leopard 10.6.2.  It's not 
known if other Onix models have a more compatible USB implementation.
</p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_cambridge"></a>Cambridge/Winpilot glider software (cambridge)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>Support for 
<a class="ulink" href="http://www.cambridge-aero.com/products.htm" target="_top">Cambridge</a> 
and <a class="ulink" href="http://www.winpilot.com" target="_top"> Winpilot</a> 
	flight analysis and planning software for glider pilots.  </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_cst"></a>CarteSurTable data file (cst)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read routes
        </p></li></ul></div><p> With this format we can read  <a class="ulink" href="http://phgiraud.free.fr/CarteSurTable/CarteSurTable.htm" target="_top">CarteSurTable</a> data files.
 <a class="ulink" href="http://phgiraud.free.fr/CarteSurTable/CarteSurTable.htm" target="_top">CarteSurTable</a> is a shareware program widely used in France. The data
inside have to be seen as a mixture of a waypoints list, one route and
several tracks.  
         </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_v900"></a>Columbus/Visiontac V900 files (.csv) (v900)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>Read-only support for the csv file format used by <span class="productname">Visiontac VGPS-900</span>™ and <span class="productname">Columbus V-900</span>™ GPS data loggers. These seem to be two brand names for the exact same product.</p><p>The the V-900 stores logs on a microSD card in a custom csv format. This format contains NULL characters and fixed length fields, and therefore can not  be handled by the normal csv module in GPSBabel.</p><p>
<a class="ulink" href="http://www.visiontac.com/v900_specs.htm" target="_top">Visiontac VGPS-900</a>
</p><div class="example"><a id="v900_e1"></a><div class="example-title">Example 3.2. Conversion of a v900 csv log file to a gpx format</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i v900 -f 09040400.csv -o gpx -F outfile.gpx</code></strong></p></div></div><br class="example-break" /><p>
The device support logging of trackpoints, waypoints, and voice recordings (.wav files).
</p><p>If you create voice recording waypoints, a link (url) to the corresponding wav file is added to the waypoint.
If you happen to use this for OpenStreetMap.org project, you can easily click on a waypoint and open the wav file from within JOSM. For this you must use gpx version 1.1 as the output file. The next example shows exactly how to do that.
</p><div class="example"><a id="v900_e2"></a><div class="example-title">Example 3.3. Conversion of a v900 csv log file to a gpx 1.1 format</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i v900 -f 09040400.csv -o gpx,gpxver=1.1 -F outfile.gpx</code></strong></p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_csv"></a>Comma separated values (csv)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p> There are a billion variants of Comma Separated Value
data.  This is the one specifically that makes <a class="ulink" href="http://www.delorme.com" target="_top">Delorme</a> <span class="productname">S&amp;A Deluxe 9</span>™ happy. It's
also a very simple program and useful for many other programs like
spreadsheets.</p><p> CSV is also the correct format for 
	<span class="productname">Lowrance MapCreate</span>™,
their commercial mapping program, or GDM6 (their free waypoint
manager) for iFinder which is available at <a class="ulink" href="http://www.lowrance.com/Software/GDM6/Default.asp" target="_top">lowrance.com</a>
         </p><p>
	On write, this format writes simple "latitude, longitude" pairs, but 
on read it  will read anything supported by our <a class="link" href="#style_def_lathuman" title="LAT_HUMAN_READABLE">human readable</a> definition.
    </p><p>
       For something-separated data that has headers identifying the various
	fields, see our <a class="link" href="#fmt_unicsv" title="Universal csv with field structure in first line (unicsv)">universal csv</a> format.
    </p><div class="example"><a id="csv_example"></a><div class="example-title">Example 3.4. Example 'csv' file</div><div class="example-contents"><pre class="programlisting">
35.97203, -87.13470, Mountain Bike Heaven by susy1313
36.09068, -86.67955, The Troll by a182pilot &amp; Family
35.99627, -86.62012, Dive Bomber by JoGPS &amp; family
36.03848, -86.64862, FOSTER by JoGPS &amp; Family
</pre></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_compegps"></a>CompeGPS data files (.wpt/.trk/.rte) (compegps)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_compegps_o_deficon" title="deficon option">deficon</a>, <a class="link" href="#fmt_compegps_o_index" title="index option">index</a>, <a class="link" href="#fmt_compegps_o_radius" title="radius option">radius</a>, <a class="link" href="#fmt_compegps_o_snlen" title="snlen option">snlen</a> .</p><p>
CompeGPS data files are those read and written by the
<span class="productname">CompeGPS</span>™ TwoNav software (running on a Mac, a PC,
or on select cell phones) as well as  CompeGPS Land, and CompeGPS Air.  
These files are also used by the CompeGPS TwoNav Aventura and TwoNav Sportiva GPS receivers when they are in mass storage mode.
</p><p>
Release 6.1 of CompeGPS Land and CompeGPS Air added GPX as an import export format for waypoints, routes, and tracks.   As GPX is a more heavily used format, you should probably use that for new applications.
</p><p> 
For more information please see
<a class="ulink" href="http://www.compegps.com" target="_top">http://www.compegps.com</a>
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_compegps_o_deficon"></a><code class="option">deficon</code> option</h3></div></div></div><p>
      Default icon name.
    </p><p>
This option specifies the default icon name on output.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_compegps_o_index"></a><code class="option">index</code> option</h3></div></div></div><p>
      Index of route/track to write (if more than one in source).
    </p><p>
Because this format supports only one route or track, this option may be used 
on output to select a single route or track from a collection of routes and
tracks read from a more expressive format.  If you have, say, a 
<a class="link" href="#fmt_gpx" title="GPX XML (gpx)">gpx</a> file that contains two routes, you may
use this option to write them one at a time to individual files.
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f routes.gpx -o compegps,index=1 -F route1.txt -o compegps,index=2 -F route2.txt</code></strong></p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_compegps_o_radius"></a><code class="option">radius</code> option</h3></div></div></div><p>
      Give points (waypoints/route points) a default radius (proximity).
    </p><p>
This option specifies the default proximity for waypoints and route points.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_compegps_o_snlen"></a><code class="option">snlen</code> option</h3></div></div></div><p>
      Length of generated shortnames (default 16).
    </p><p>
This option specifies the default length for short names generated on output.
The default length is 16.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_custom"></a>Custom "Everything" Style (custom)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
This format is not actually used by any real product.  It is most useful
for debugging purposes when developing a new format module for GPSBabel.
</p><p>
To understand the contents of this file, look at the 
<code class="filename">style/custom.style</code> file in the GPSBabel source
distribution as well as <a class="xref" href="#Styles" title="Appendix C. GPSBabel XCSV Style Files">Appendix C, <em>GPSBabel XCSV Style Files</em></a>.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_iblue747"></a>Data Logger iBlue747 csv (iblue747)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
  This is the format used by the software that comes with the <a class="ulink" href="http://www.semsons.com/i747bldalogp.html" target="_top">Transystem i-Blue747 GPS</a>.
</p><p>
  Notice that the iBlue 747 logs the sum of "height above sealevel" and "height of geoid above WGS84".   If precise altitude matters to you, check out the <a class="link" href="#filter_height" title="Manipulate altitudes (height)">height filter</a> which allows you to compensate for this.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_iblue757"></a>Data Logger iBlue757 csv (iblue757)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
  This is the format used by the software that comes with the 
   <a class="ulink" href="http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=81290" target="_top">
     Transystem i-Blue757 Pro GPS
   </a>.
   It is very similar to the <a class="link" href="#fmt_iblue747" title="Data Logger iBlue747 csv (iblue747)">iBlue747</a> 
   format, apart from the date format being reversed.
</p><p>
  The csv log file can be extracted from the GPS receiver using 
  the BT747 software available from <a class="ulink" href="http://www.bt747.org" target="_top">http://www.bt747.org</a>
</p><p>
Field definitions:
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="ib_index"></a>INDEX</h3></div></div></div><p>
A sequential integer which corresponds for each logged point in the file.
</p><p>example 3308
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="ib_rcr"></a>RCR</h3></div></div></div><p>
?
</p><p>example 1: T
</p><p>example 2: TD
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="ib_title"></a>DATE</h3></div></div></div><p>
Date that the point was recorded, in the format YYYY/MM/DD
</p><p>example: 2011/05/14
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="ib_time"></a>TIME</h3></div></div></div><p>
Time that the point was recorded, 24-hr format H:MM:SS. Unsure how fractions of a second are handled.
</p><p>example: 4:15:11
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="ib_valid"></a>VALID</h3></div></div></div><p>
?
</p><p>example 1: DGPS
</p><p>example 2: SPS
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="ib_lat"></a>LATITUDE</h3></div></div></div><p>
Degrees above the equator (use negative for south of the equator)
</p><p>example: -33.803645
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="ib_hemi"></a>N/S</h3></div></div></div><p>
North (N)or South (S) of the equator
</p><p>example: S
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="ib_lon"></a>LONGITUDE</h3></div></div></div><p>
Degrees east of the Prime Meridian (use negative for east of the Prime Meridian/Greenwich)
</p><p>example: 150.880499
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="ib_ewhemi"></a>E/W</h3></div></div></div><p>
East (E) or West (W) of Greenwich
</p><p>example: E
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="ib_height"></a>HEIGHT</h3></div></div></div><p>
Height above sea level in metres
</p><p>example: 99.859 m
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="ib_speed"></a>SPEED</h3></div></div></div><p>
Speed in km/h
</p><p>example: 0.302 km/h
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="ib_dist"></a>DISTANCE</h3></div></div></div><p>
Distance covered since last point in metres
</p><p>example: 0.30 m
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="ib_example"></a>Example File</h3></div></div></div><p>
Example 3.X. Example 'iBlue 757' file
</p><div class="literallayout"><p><br />
INDEX,RCR,DATE,TIME,VALID,LATITUDE,N/S,LONGITUDE,E/W,HEIGHT,SPEED,DISTANCE<br />
3308,T,2011/05/14,4:15:11,DGPS,-33.803645,S,150.880499,E,99.859 m,0.207 km/h, 0.28 m<br />
3309,T,2011/05/14,4:15:12,DGPS,-33.803645,S,150.880499,E,100.137 m,0.362 km/h, 0.28 m<br />
3310,T,2011/05/14,4:15:13,DGPS,-33.803644,S,150.8805,E,100.416 m,0.302 km/h, 0.30 m<br />
</p></div><p>
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_an1"></a>DeLorme .an1 (drawing) file (an1)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_an1_o_type" title="type option">type</a>, <a class="link" href="#fmt_an1_o_road" title="road option">road</a>, <a class="link" href="#fmt_an1_o_nogc" title="nogc option">nogc</a>, <a class="link" href="#fmt_an1_o_nourl" title="nourl option">nourl</a>, <a class="link" href="#fmt_an1_o_deficon" title="deficon option">deficon</a>, <a class="link" href="#fmt_an1_o_color" title="color option">color</a>, <a class="link" href="#fmt_an1_o_zoom" title="zoom option">zoom</a>, <a class="link" href="#fmt_an1_o_wpt_type" title="wpt_type option">wpt_type</a>, <a class="link" href="#fmt_an1_o_radius" title="radius option">radius</a> .</p><p> 
This format supports the <a class="ulink" href="http://www.delorme.com" target="_top">DeLorme</a> ".an1" drawing file format used by their desktop software like Topo USA.  It can 
currently be used to either read or write drawing files.  If you use 
this format to create drawing files with routes or waypoints from another 
source, by default it will create "Red Flag" symbols for waypoints, and 
thick red lines for routes or tracks.  It is possible to merge two drawing 
layers by doing something like this:
</p><p><strong class="userinput"><code>gpsbabel -i an1 -f one.an1 -f two.an1 -o an1 -F merged.an1</code></strong></p><p> 
In this case, the merged data will contain all of the
properties of the original data.
</p><p>
GPSBabel has a page describing <a class="ulink" href="/formats/delorme-new-interstate/" target="_top">creating routable onramps in Street Atlas with GPSBabel</a>.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_an1_o_type"></a><code class="option">type</code> option</h3></div></div></div><p>
      Type of .an1 file.
    </p><p> This option specifies the type of the drawing layer
to be created.  The supported values are "drawing", "road", "trail",
"waypoint", or "track".  If you do not specify a type, the default
will be either the type of the previous an1 file or "drawing" if there
is no previous file. This lets you merge, for example, two road layers
without having to specify "type=road" for the output.  </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_an1_o_road"></a><code class="option">road</code> option</h3></div></div></div><p>
      Road type changes.
    </p><p>
If you are creating a road layer, you may use the "road" option, which 
allows you to change the types of roads based on their names.  You can 
change multiple roads at the same time.  Currently supported types are 
</p><p>
</p><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Type</th><th>Meaning</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">limited</td><td class="seg">Limited-access freeways</td></tr><tr class="seglistitem"><td class="seg">toll</td><td class="seg">Limited-access toll highways</td></tr><tr class="seglistitem"><td class="seg">ramp</td><td class="seg">Access ramps for limited-access highways</td></tr><tr class="seglistitem"><td class="seg">us</td><td class="seg">National highways (e.g. US routes)</td></tr><tr class="seglistitem"><td class="seg">primary</td><td class="seg">Primary State/Provincial routes</td></tr><tr class="seglistitem"><td class="seg">state</td><td class="seg">State/Provincial routes</td></tr><tr class="seglistitem"><td class="seg">major</td><td class="seg">Major Connectors</td></tr><tr class="seglistitem"><td class="seg">ferry</td><td class="seg">Ferry Routes</td></tr><tr class="seglistitem"><td class="seg">local</td><td class="seg">Local Roads</td></tr><tr class="seglistitem"><td class="seg">editable</td><td class="seg">User-drawn Roads</td></tr></tbody></table></div><p>
</p><p>
GPSBabel defaults to creating editable roads.  These are routed just like 
local roads, but may be edited with the drawing tools in Street Atlas.
</p><p> 
This option has a special format that is best demonstrated by example:
</p><pre class="screen"> "road=I-599!limited!Beecher St.!major" </pre><p>
This option will cause any road named "I-599" to become a limited-access 
highway and any road named "Beecher St." to become a major connector.  Note 
that roads that have had their types changed in this way are not editable 
in Street Atlas, so make sure they are where you want them before you 
change them, and make sure to keep a backup of your original road layer.  
Note that the ! is a shell metacharacter in bash and possibly other shells, 
so you may have to use single quotes or some other escape mechanism.
</p><p>
There is a tutorial on 
<a class="ulink" href="http://www.gpsbabel.org/formats/delorme-new-interstate/" target="_top">how 
to create an onramp for a limited access highway in Street Atlas USA 
using GPSBabel.</a>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_an1_o_nogc"></a><code class="option">nogc</code> option</h3></div></div></div><p>
      Do not add geocache data to description.
    </p><p>
If your original data contains geocaching-specific information such as 
difficulty and terrain, GPSBabel will automatically include that information 
in the waypoint descriptions in the generated drawing file.  If you do not 
want that, specify the "nogc" option on the command line:
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f 12345.gpx -o an1,nogc -F 12345.an1</code></strong></p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_an1_o_nourl"></a><code class="option">nourl</code> option</h3></div></div></div><p>
      Do not add URLs to description.
    </p><p>
If your original waypoint data contains URLs, GPSBabel will include them as
links in the generated drawing file.  This causes the waypoint symbol to have
a blue border, and it causes the waypoint text to be drawn in blue with an 
underline.
</p><p>
If you do not want this behavior, specify the "nourl" option on the command
line:
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f 12345.gpx -o an1,nourl -F 12345.an1</code></strong></p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_an1_o_deficon"></a><code class="option">deficon</code> option</h3></div></div></div><p>
      Symbol to use for point data.
    </p><p>
This option allows you to specify which symbol to use for points that 
don't have a symbol already.  It defaults to "Red Flag" but it accepts 
any symbol name you can put in a DeLorme export file.  To find the name 
of a specific symbol in Street Atlas, let the mouse pointer hover over 
it for a few seconds and the name will be displayed.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_an1_o_color"></a><code class="option">color</code> option</h3></div></div></div><p>
      Color for lines or mapnotes.
    </p><p>This option allows you to specify the color for
line or mapnote data.  It accepts color names of the form "#FF0000" (red) or any
of the color names from the Cascading Style Sheets (CSS)
specification.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_an1_o_zoom"></a><code class="option">zoom</code> option</h3></div></div></div><p>
      Zoom level to reduce points.
    </p><p>
This option specifies at what zoom level Street Atlas will begin showing 
reduced versions of your symbols. The default is 10.  Setting zoom to 0 will 
disable this feature.  Setting it to anything but the default will override 
the zoom level specified on any waypoints that were read from an existing 
an1 file; this is by design.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_an1_o_wpt_type"></a><code class="option">wpt_type</code> option</h3></div></div></div><p>
      Waypoint type.
    </p><p>
This option specifies how to represent point data in the draw file.  
Valid waypoint types are "symbol", "text", "mapnote", "circle", and "image".  
The default is "symbol". 
</p><p>
If you specify a waypoint type of "image", you should make sure that the
icon descriptions of your waypoints are the full names, including drive letters
and full path, of image files in a format that works with your DeLorme 
product.  Note that this means that the .an1 file you generate will not work
on any computer that does not have those images in the same place; this is 
part of the design of the an1 format and cannot be avoided.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_an1_o_radius"></a><code class="option">radius</code> option</h3></div></div></div><p>
      Radius for circles.
    </p><p>
If the waypoint type is "circle", the "radius" option specifies
the radius of the circles.  By default, this is in miles, but it may be
specified in kilometers by adding a 'k'.  The default radius is 1/10 mile.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_gpl"></a>DeLorme GPL (gpl)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
  This is the 'gpl' format as used in Delorme mapping
  products.  It is a track format and contains little more than the
  tracklog of a GPS that was attached while driving. 
  <a class="ulink" href="http://www.frontiernet.net/~werner/gps/" target="_top">frontiernet.net</a>
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_delbin"></a>DeLorme PN-20/PN-30/PN-40 USB protocol (delbin)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_delbin_o_get_posn" title="get_posn option">get_posn</a>, <a class="link" href="#fmt_delbin_o_logs" title="logs option">logs</a>, <a class="link" href="#fmt_delbin_o_long_notes" title="long_notes option">long_notes</a>, <a class="link" href="#fmt_delbin_o_nukewpt" title="nukewpt option">nukewpt</a>, <a class="link" href="#fmt_delbin_o_nuketrk" title="nuketrk option">nuketrk</a>, <a class="link" href="#fmt_delbin_o_nukerte" title="nukerte option">nukerte</a>, <a class="link" href="#fmt_delbin_o_hint_at_end" title="hint_at_end option">hint_at_end</a>, <a class="link" href="#fmt_delbin_o_gcsym" title="gcsym option">gcsym</a> .</p><p>
  The 'delbin' module supports 
<span class="productname">DeLorme PN-20</span>™, 
<span class="productname">DeLorme PN-30</span>™, 
<span class="productname">DeLorme PN-40</span>™, 
<span class="productname">DeLorme PN-40 SE</span>™, and 
<span class="productname">DeLorme PN 60 </span>™receivers.
  </p><div class="important"><h3 class="title">Important</h3><p>
      Not all strains of Linux are supported.   Fedora 7 is known not to work, for example.
    </p></div><p>
</p><p>
  Only the 'usb:' device is supported.  If you're on Windows, do not attempt to
  run this through the serial driver.
</p><p>
  On Linux, a name of the form 'hid:path-to-hidraw,path-to-hiddev' is also supported.
  You will need to use this only if the HID device nodes on your system are not named
  /dev/hidrawN and /dev/hiddevN or /dev/usb/hiddevN.
</p><p>
  This module implements the (undocumented) waypoint extensions introduced
  for enhanced geocaching mode in 2.5 for PN-40 and 1.6 for PN-20.  As 
  these are reverse engineered, there may be issues with those modes 
  in particular.
</p><div class="example"><a id="pn-40-send"></a><div class="example-title">Example 3.5. Command to send a pocket query (GPX) to a Delorme PN device </div><div class="example-contents"><p>
    <strong class="userinput"><code>
      gpsbabel -i gpx -f "My Caches.gpx" -o delbin -F usb:
    </code></strong>
  </p></div></div><br class="example-break" /><p>
  If you receive a message that the device is busy, especially on Windows,
  that could be because another program, likely Delorme's own, has the 
  device open even though it's not actively interacting with the GPS.   In 
  Topo 8, on the GPS tab, look for GPS Options.  Uncheck "Start GPS" and 
  "Automatically detect GPS".   Then just click the Exchange button when
  you're ready for Topo to interact with the GPS.  Other Delorme software may
  be similar.
</p><p>
  The GPS should not be in 'map exchange' mode.   When in that mode, it appears
  as a disk to the USB system, thus GPSBabel will be unable to find the GPS.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_delbin_o_get_posn"></a><code class="option">get_posn</code> option</h3></div></div></div><p>
      Return current position as a waypoint.
    </p><p>This option returns the current position as a single waypoint.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_delbin_o_logs"></a><code class="option">logs</code> option</h3></div></div></div><p>
      Include groundspeak logs when writing.
    </p><p>
  When set to true, this includes Groundspeak logs from GPX pocket queries 
  when writing to Delorme devices that support the extended features introduced
  in firmware version 2.5 for the PN-40 and PN-30 and in 1.6 for the PN-20.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_delbin_o_long_notes"></a><code class="option">long_notes</code> option</h3></div></div></div><p>
      Use long waypoint notes regardless of PN version.
    </p><p>
  Use long waypoint notes, overriding the built-in version check (which is 
  reverse engineered) that tests if the unit can handle the waypoint comments
  longer than 800 bytes.
</p><p>
  This option will probably go away in time as most units get upgraded to
  the capabilities of the 2.5 version of the PN-40 and PN-30 or version 1.6 
  for the PN-20.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_delbin_o_nukewpt"></a><code class="option">nukewpt</code> option</h3></div></div></div><p>
      Delete all waypoints before sending.
    </p><p>
  When present on the command line and sending waypoints (either explicitly 
  via -w or as the default), this will erase
  all waypoints in the receiver before sending the new ones.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_delbin_o_nuketrk"></a><code class="option">nuketrk</code> option</h3></div></div></div><p>
      Delete all tracks before sending.
    </p><p>
  When present on the command line and sending tracks with -t, this will erase
  all tracks in the receiver before sending the new ones.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_delbin_o_nukerte"></a><code class="option">nukerte</code> option</h3></div></div></div><p>
      Delete all routes before sending.
    </p><p>
  When present on the command line and sending routes with -r, this will erase
  all routes in the receiver before sending the new ones.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_delbin_o_hint_at_end"></a><code class="option">hint_at_end</code> option</h3></div></div></div><p>
      If true, geocache hint at end of text.
    </p><p>
  When set to true, this places the "HINT:" entry from a geocaching.com 
   pocket query at the end of the screen (scroll up for quick access) like
   Cache Register and Topo7 do instead of at the top as Topo8 does.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_delbin_o_gcsym"></a><code class="option">gcsym</code> option</h3></div></div></div><p>
      If set to 0, prefer user-provided symbols over Groundspeaks ones for geocaches.
    </p><p>
This 1/0 option, defaulting to  if not provided, tells GPSBabel to 
use its own logic when sending data it can deduce is a geocache to 
the device. If false, any icon data present in the source data will
 be used instead. If you've taken control of the icon data, you are
 responsible for providing valid icons; GPSBabel will make no attempt 
to purify what gets sent.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_saplus"></a>DeLorme Street Atlas Plus (saplus)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p> This format is for Delorme Street Atlas USA 2004 Plus and later.
</p><p> For geocachers importing data from a tool like GSAK or
Spinner, import the file twice in XData.  One will create a file with
the Cache description as a hyperlink on the flag. This can clutter up
the screen and when you try to zoom in, it causes problems.  So the
second one will only have a flag. Thus you can turn off and on which
one you want to view.  The first time you import the file, in the
assign field types, check the circle above Full Name and then next.
The second time you import the file do not check any circle and in the
second to last column, change URL to none and then click next. Use the
same name you used the first time but add -Flag to it.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_saroute"></a>DeLorme Street Atlas Route (saroute)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_saroute_o_turns_important" title="turns_important option">turns_important</a>, <a class="link" href="#fmt_saroute_o_turns_only" title="turns_only option">turns_only</a>, <a class="link" href="#fmt_saroute_o_split" title="split option">split</a>, <a class="link" href="#fmt_saroute_o_controls" title="controls option">controls</a>, <a class="link" href="#fmt_saroute_o_times" title="times option">times</a> .</p><p> 
This format reads route files from many Delorme mapping products.
It supports the anr, rte, and rtd formats as either tracks or
routes.</p><p> All options only apply to route files from newer (anr)
versions of DeLorme software; older versions didn't store the turn
information with the route.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_saroute_o_turns_important"></a><code class="option">turns_important</code> option</h3></div></div></div><p>
      Keep turns if simplify filter is used.
    </p><p> This option only makes sense in
conjunction with the 'simplify' filter.  It ensures that the route
simplification process will remove the points corresponding to turns
only after it has removed all other route points.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_saroute_o_turns_only"></a><code class="option">turns_only</code> option</h3></div></div></div><p>
      Only read turns; skip all other points.
    </p><p> This option causes GPSBabel to read only the
waypoints associated with named turns.  This should create a list of
waypoints that correspond to the itinerary from Street Atlas.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_saroute_o_split"></a><code class="option">split</code> option</h3></div></div></div><p>
      Split into multiple routes at turns.
    </p><p>This option causes GPSBabel to create separate
routes for each street, creating a new route at each turn point.  For
obvious reasons, 'split' cannot be used at the same time as the
'turns_only' or 'turns_important' options.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_saroute_o_controls"></a><code class="option">controls</code> option</h3></div></div></div><p>
      Read control points as waypoint/route/none.
    </p><p>This option lets you read the control points
(start, end, vias, and stops) for your route as well as the route
itself.  The default for this option is 'none', which won't read the
control points.  You may also specify 'waypoints', which reads the
control points as waypoints, or 'route', which creates an extra route
named 'control points' containing just the control points in order.
Note that if your goal is to create an arc or other CSV file, you
should use 'none' (or not use this option, which is the same
thing.)</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_saroute_o_times"></a><code class="option">times</code> option</h3></div></div></div><p>
      Synthesize track times.
    </p><p>This option causes GPSBabel to read the route as if
it were a track, synthesizing times starting from the current time, using
the estimated travel times specified in your route file (you can change your
travel speeds in the DeLorme product you used to create the route file.)</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_xmap"></a>DeLorme XMap HH Native .WPT (xmap)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>Delorme TopoUSA/XMap Conduit is one of the bazillion 
<a class="link" href="#fmt_csv" title="Comma separated values (csv)">CSV variants</a> 
variants mentioned above.  It's just like Delorme Streets &amp; Atlas with the addition of
a completely pointless line at the beginning and end of the file. This
is the format used to hot-sync to XMap from withing TopoUSA. Done with
help of Dan Edwards.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_xmap2006"></a>DeLorme XMap/SAHH 2006 Native .TXT (xmap2006)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>Delorme XMap2006 Conduit is just like 
<a class="link" href="#fmt_xmap" title="DeLorme XMap HH Native .WPT (xmap)">XMap</a> 
, except there are 
	no spaces between fields and the coordinate format is slightly 
	different. The completely pointless header and footer lines 
	are the same, at least. Use this to create the XMapHHWptsSend.txt 
	file needed to sync to Street Atlas Handheld 2006.</p><p>Note that in order to keep from creating duplicates on your handheld, you must first remove the file "XMapWptsDB" from your handheld, restart SAHH2006 on the handheld to create an empty database, and THEN sync the new file. </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_xmapwpt"></a>DeLorme XMat HH Street Atlas USA .WPT (PPC) (xmapwpt)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
Delorme XMapHandHeld Street Atlas USA is another of the
billion <a class="link" href="#fmt_csv" title="Comma separated values (csv)"> CSV variants</a>.  
This is the format used by XmapHH SA USA on (at least) PocketPC O/S. 
</p><p> 
This XMap is not the same as the simpler 
<a class="link" href="#fmt_xmap" title="DeLorme XMap HH Native .WPT (xmap)">XMap</a> format, which is used with Topo USA 4.0
and XMapHH for Palm. 
</p><p>
Delorme XMap Handheld .WPT for PocketPC is a bit of a kludge.  This 
chapter covers XMap Handheld Street Atlas USA edition.
</p><p>
XMap on the PocketPC stores its waypoints in individual .wpt files.
For example, waypoints generated by XMap on the PocketPC are stored
by default in the "My Documents" folder using the sequential names
"XMap1.wpt", "XMap2.wpt", ad nauseum.  Needless to say, this is not very
efficient.
</p><p>
As writing multiple waypoint files is outside of the scope of GPSBabel,
GPSBabel chooses to write one big file, one waypoint per line.  
Extracting lines from this file is left as an exercise for the end user.  
A simple Perl script to handle this conversion is included at the end 
of this chapter.
</p><p>
It should also be noted that <span class="emphasis"><em>reading</em></span> multiple files 
is indeed possible, but if you have more than a few points, it can be a task. 
For example:
</p><p><strong class="userinput"><code>gpsbabel -i xmapwpt -f Xmap1.wpt -f Xmap2.wpt -o mapsend -F mapsend.wpt</code></strong></p><p>
will read the two Xmap .wpt files and write one mapsend file.  This
is fine for a small handful of points, but could be quite cumbersome
for folks like me who have 100+ waypoints loaded into XMap.  For *nix
folks, something as simple as:
</p><p><strong class="userinput"><code>cat *.wpt &gt; /tmp/foo.wpt</code></strong>
<strong class="userinput"><code>gpsbabel -i xmapwpt -f foo.wpt -o mapsend -F mapsend.wpt </code></strong></p><p>
will do the trick just fine.  
</p><pre class="programlisting">
#!/full/path/to/perl
$INPUTFILE = @ARGV[0];
$TARGETDIR = @ARGV[1];
$FILENAME  = @ARGV[2];

if (! $FILENAME) {
    print "Usage: xmap_split.pl " . 
	"INPUT_FILE OUTPUT_DIRECTORY FILENAME_BASE\n";
    print " (i.e. xmapl_split.pl points.wpt /tmp/points GPSB)\n";
    print " (created GPSB0001-GPSBXXXX " .
	" in /tmp/points/ from points.wpt)\n";
    exit;
}

open (INFILE, $INPUTFILE) || die "Cannot open $INPUTFILE for read!\n";

while (&lt;INFILE&gt;) {
    $lc++;
    $filename = sprintf("%s/Gpsb%04d.wpt", $TARGETDIR, $lc);

    open (OUTFILE, "&gt;$filename") || 
	die "Cannot open $filename for write!\n";

    print OUTFILE $_;

    close(OUTFILE);
}

exit;

</pre><p>Contributed to GPSBabel by Alex Mottram.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_destinator_itn"></a>Destinator Itineraries (.dat) (destinator_itn)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>
  Support for <span class="productname">Destinator</span>™ itinerary files.
</p><p>
  These have (mostly) extension .dat and are binary files. The file structure is undocumented
  and so this format was reverse engineered from some .dat files.
  At this time we can read and write name, comment and the coordinates of the route points.
</p><p>
  <span class="productname">Destinator</span>™ by
  <a class="ulink" href="http://www.destinatortechnologies.net" target="_top">Destinator Technologies</a>
  is a software for PNDs, Smartphones and PDAs.
</p><p>
  <strong class="userinput"><code>
      gpsbabel -i destinator_itn -f from_A_to_B.dat -o gpx -F from_A_to_B.gpx
  </code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_destinator_poi"></a>Destinator Points of Interest (.dat) (destinator_poi)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
  Support for <span class="productname">Destinator</span>™ binary POI files (.dat).
</p><p>
  The basic information was found at <a class="ulink" href="http://mozoft.com/d3log.html" target="_top">mozoft.com</a>.
  GPSBabel can read and write all fields described at this document. Please note that 'house number' isn't
  supported as a separate field. This field, if available in any source file, will be stored together with 'street'
  into GSPBabel's internal 'address' field.
</p><p>
  <span class="productname">Destinator</span>™ by
  <a class="ulink" href="http://www.destinatortechnologies.net" target="_top">Destinator Technologies</a>
  is a software for PNDs, Smartphones and PDAs.
</p><p>
  <strong class="userinput"><code>
      gpsbabel -i destinator_poi -f interesting_places.dat -o gpx -F interesting_places.gpx
  </code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_destinator_trl"></a>Destinator TrackLogs (.dat) (destinator_trl)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
  Support for <span class="productname">Destinator</span>™ binary tracklogs (.dat).
</p><p>
  The basic information was found at <a class="ulink" href="http://mozoft.com/d3log.html" target="_top">mozoft.com</a>.
  In addition to the standard GPS track data of coordinates and timestamp, this format also stores the 
  position fix and the number of satellites seen during recording. 
</p><p>
  <span class="productname">Destinator</span>™ by
  <a class="ulink" href="http://www.destinatortechnologies.net" target="_top">Destinator Technologies</a>
  is a software for PNDs, Smartphones and PDAs.
</p><p>
  <strong class="userinput"><code>
    gpsbabel -i destinator_trl -f last_trip.dat -o gpx -F last_trip.gpx
  </code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_easygps"></a>EasyGPS binary format (easygps)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
  This is the binary file format used by  <a class="ulink" href="http://www.easygps.com/" target="_top">EasyGPS</a>
  format is seemingly being phased out in favor of GPX in newer versions
  of EasyGPS, but this allows conversions to and from the old binary
  .loc format.
</p><p>
  Information about and sketchy code to implement this file
  format were provided by Eric Cloninger.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_exif"></a>Embedded Exif-GPS data (.jpg) (exif)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_exif_o_filename" title="filename option">filename</a>, <a class="link" href="#fmt_exif_o_frame" title="frame option">frame</a>, <a class="link" href="#fmt_exif_o_name" title="name option">name</a>, <a class="link" href="#fmt_exif_o_overwrite" title="overwrite option">overwrite</a> .</p><p>
  This format reads and writes GPS information embedded in 
   <a class="ulink" href="http://www.exif.org" target="_top">EXIF</a>, 
   the Exchangeable Image Format, data.  EXIF is a standardized method
  of encoding data in pictures such as JPEG, TIFF, and WAV and is frequently
  used by mobile phones with cameras and cameras with built-in GPS.
</p><p>
  EXIF is frequently used for Geolocating photographs so their images can be
  correlated with time and location.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_exif_o_filename"></a><code class="option">filename</code> option</h3></div></div></div><p>
      Set waypoint name to source filename.
    </p><p>
  With this default option waypoint names are generated from source filename.
</p><p>
  <strong class="userinput"><code>
     gpsbabel -i exif -f "C:\Pictures\IMG_1199.JPG",filename=Y -o gpx -F OUT.GPX
  </code></strong>
  The resulting waypoint in OUT.GPX has name IMG_1199.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_exif_o_frame"></a><code class="option">frame</code> option</h3></div></div></div><p>
      Time-frame (in seconds).
    </p><p>
   Frame means the maximum time difference that we accept between the EXIF time information
   of a picture and the timestamp of a track-, route- and waypoint used for tagging. 
   Without this option the maximum time frame is 10 seconds.
</p><p>
  <strong class="userinput"><code>gpsbabel -i gpx -f holiday.gpx -o exif,frame=60 -F IMG0784.JPG</code></strong>
</p><p>
   If the camera time wasn't adjusted, you should move the track(s) by the this difference.
   I.e. if the camera time is five minutes behind your time, the track(s) should be shifted
   five minutes back.
</p><p>
  <strong class="userinput"><code>gpsbabel -i gpx -f holiday.gpx -x track,move=-5m -o exif,frame=60 -F IMG0784.JPG</code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_exif_o_name"></a><code class="option">name</code> option</h3></div></div></div><p>
      Locate waypoint for tagging by this name.
    </p><p>
   When you specify a name with this option we're looking for a waypoint
   with this name. And, if found, the GPS information of this point is used
   for tagging the image file.
</p><p>
  <strong class="userinput"><code>gpsbabel -i gpx -f holiday.gpx -o exif,name="On the beach" -F IMG0786.JPG</code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_exif_o_overwrite"></a><code class="option">overwrite</code> option</h3></div></div></div><p>
      !OVERWRITE! the original file. Default=N.
    </p><p>
   In the default case GPSBabel reads the output file (the file that should be
   tagged with GPS information) and then creates a new file with an additional
   .JPG extension. With this option in a final step the original file will be
   deleted and the new file renamed as the original filename.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_enigma"></a>Enigma binary waypoint file (.ert) (enigma)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>
   This <a class="ulink" href="http://www.mglavionics.co.za/" target="_top">MGL Avionics</a> format holds waypoints or routes. This routes can be loaded by the MGL Stratomaster Enigma EFIS series (
<span class="productname">Enigma</span>™, 
<span class="productname">Odyssey</span>™, 
<span class="productname">Voyager</span>™, 
<span class="productname">Explorer</span>™).  
</p><p>
 The format is designed for microcontrollers. The use is free for any non-military 
 application. You can find a detailed description in the <a class="ulink" href="http://www.mglavionics.co.za/Docs/Enigma%20Waypoint%20format.pdf" target="_top">MGL Documentation</a>.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_igc"></a>FAI/IGC Flight Recorder Data Format (igc)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_igc_o_timeadj" title="timeadj option">timeadj</a> .</p><p>
FAI/IGC Data File -- Used by the international gliding
community to record gliding flights.  IGC files can be converted to
and from tracks representing recorded flights, and routes representing
task declarations in other formats.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_igc_notes"></a>IGC Data Format Notes</h3></div></div></div><p>
Refer to Appendix 1 of 
<a class="ulink" href="http://www.fai.org:81/gliding/gnss/tech_spec_gnss.asp" target="_top">http://www.fai.org:81/gliding/gnss/tech_spec_gnss.asp</a>
for the specification of the IGC data format.
</p><p>
A sample list of software applications that use data in IGC format can be
found at 
<a class="ulink" href="http://www.fai.org:81/gliding/gnss/gnss_analysis_software.pdf" target="_top">http://www.fai.org:81/gliding/gnss/gnss_analysis_software.pdf</a>
</p><p>
GPSBabel can be used to translate data in IGC format to and from various other
formats.
</p><p>
Routes in other formats are used to represent IGC task declarations.
</p><p>
Tracks in other formats are used to represent IGC recorded flights.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_igc_convto"></a>Converting to IGC format</h3></div></div></div><p>
IGC files generated by GPSBabel will NOT pass security validation tests since
the data they contain cannot be proven to originate from an approved flight
recorder.  For most software applications that use IGC files this is not an
issue but for competition scoring, record and badge claims the generated files
will not be accepted as proof of a flight.
</p><p>
A track stored in another format (GPX for example) representing a recorded
flight can be converted into an IGC file:
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f mytrk.gpx -o igc -F myflight.igc</code></strong></p><p>
If multiple track segments are provided in the input file, the one with the
most points will be used.
</p><p>
A route stored in another format representing a task declaration can be
converted into an IGC file:
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f myrte.gpx -o igc -F mytask.igc</code></strong></p><p>
A route and a track in other formats can be included into a single IGC file:
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f mytrk.gpx -f myrte.gpx -o igc -F myflight.igc</code></strong></p><p>
A similar result can be obtained by downloading the track log and routes
directly from a GPS device connected to a PC.  For example to create an IGC
file from data recorded in a Garmin GPS connected to the first serial port of
a PC running Linux:
</p><p><strong class="userinput"><code>gpsbabel -t -r -i garmin -f /dev/ttyS0 -o igc -F myflight.igc</code></strong></p><p>
For Windows operating systems:
</p><p><strong class="userinput"><code>gpsbabel -t -r -i garmin -f com1 -o igc -F myflight.igc</code></strong></p><p>
A waypoint file in another format containing a waypoint whose short name is
"PILOT" can be merged into an IGC file.  The description field of the waypoint
will be used for the pilot name in the IGC file header:
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f mytrk.gpx -f myrte.gpx -f mywpt.gpx -o igc -F myflight.igc
gpsbabel -w -t -r -i garmin -f /dev/ttyS0 -o igc -F myflight.igc</code></strong></p><p>
Some formats such as GPX allow routes, tracks and waypoints to exist in the
same file and can be used to fully populate an IGC file:
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f myall.gpx -o igc -F myflight.igc</code></strong></p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_igc_convfrom"></a>Converting from IGC format</h3></div></div></div><p>
Data in an IGC file can be converted into other formats.  For example to
generate OziExplorer files containing tracks representing the recorded
flight (myozi.plt) and routes representing declared tasks (myozi.rte):
</p><p><strong class="userinput"><code>gpsbabel -i igc -f myflight.igc -o ozi -F myozi</code></strong></p><p>
Or to GPX format:
</p><p><strong class="userinput"><code>gpsbabel -i igc -f myflight.igc -o gpx -F myflight.gpx</code></strong></p><p>
Header information from the IGC file will be written to the description field
of the track(s).
</p><p>
If both pressure altitude and GNSS altitude are recorded in the IGC file, two
tracks will be written to the new track file, representing the two altitude
tracks.  The latitude, longitude and timestamps in the tracks will be identical.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_igc_merge"></a>Merging into IGC format</h3></div></div></div><p>
A route stored in another format can be merged with an existing IGC file that
has no task declaration, to generate a new IGC file with a task declaration:
</p><p><strong class="userinput"><code>gpsbabel -i igc -f myflight.igc -i gpx -f myrte.gpx -o igc -F mynew.igc</code></strong></p><p>
A two dimensional (lat/lon) track recorded during a flight by a GPS receiver
can be merged with a one dimensional (altitude) track recorded during the same
flight by a barograph instrument.  The result is a three dimensional IGC file
representing the flight:
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc -F my3D.igc</code></strong></p><p>
The same can be achieved by downloading directly from a barograph instrument
supported by GPSBabel.  For example with a Brauniger IQ Comp GPS variometer:
</p><p><strong class="userinput"><code>gpsbabel -i baroiq -f /dev/ttyS0 -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc</code></strong></p><p>
or:
</p><p><strong class="userinput"><code>gpsbabel -i baroiq -f com1 -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc</code></strong></p><p>
(Documentation contributed by Chris Jones, Aug 2004)
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_igc_o_timeadj"></a><code class="option">timeadj</code> option</h3></div></div></div><p>
      (integer sec or 'auto') Barograph to GPS time diff.
    </p><p>
Sometimes there is a discrepancy between the internal clock in the barograph
instrument and GPS time which can result in the altitude and ground positions
not correlating correctly.  This can be corrected manually by passing the time
difference in seconds between the two time domains through the "timeadj"
parameter.  This can be any positive or negative integer:
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc,timeadj=27 -F my3D.igc</code></strong></p><p>
GPSBabel can also attempt to deduce the time difference automatically.  This
is done by comparing the time that it thinks that you landed on the GPS track
and the barograph and adjusting accordingly:
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc</code></strong></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_garmin_fit"></a>Flexible and Interoperable Data Transfer (FIT) Activity file (garmin_fit)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_flysight"></a>FlySight GPS File (flysight)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
This is the format used by the <a class="ulink" href="http://www.flysight.ca" target="_top">FlySight GPS</a> for wingsuit pilots.
</p><p>
Interfacing with the FlySight is pretty simple. FlySight acts like a USB disk when connected to a computer. Files are organized into folders by date, and individual files within the folder are named according to the time the log started (UTC). The files themselves are CSV text supported by this format.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_gpssim"></a>Franson GPSGate Simulation (gpssim)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_gpssim_o_wayptspd" title="wayptspd option">wayptspd</a>, <a class="link" href="#fmt_gpssim_o_split" title="split option">split</a> .</p><p>
        This is a write-only format used to feed waypoints, tracks, and routes
        into <a class="ulink" href="http://franson.com/" target="_top">Franson Technolgies'</a>
        <a class="ulink" href="http://franson.com/gpsgate/" target="_top">GpsGate simulator</a>.
  </p><p>
        To use these files in GpsGate, select 'Simulator' and then
        "File-&gt;Open".
  </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gpssim_o_wayptspd"></a><code class="option">wayptspd</code> option</h3></div></div></div><p>
      Default speed for waypoints (knots/hr).
    </p><p>
  This option specifies the speed of the simulation in knots.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gpssim_o_split"></a><code class="option">split</code> option</h3></div></div></div><p>
      Split input into separate files.
    </p><p>When this option is specified, GPSBabel will split 
        split the output into multiple files using the output filename
        as a base.  For example, if you specify an output file of 'mytrip',
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>mytrip-waypoints.gpssim - will contain the waypoints.</td></tr><tr><td>mytrip-track0000.gpssim - will contain the first track.</td></tr><tr><td>mytrip-track0001.gpssim - will contain the second track.</td></tr><tr><td>... and so on.</td></tr><tr><td>mytrip-route0000.gpssim - will contain the first route.</td></tr><tr><td>mytrip-route0001.gpssim - will contain the seconds route.</td></tr><tr><td>... and so on.</td></tr></table><p>
</p><p>
Valid values for this option are 0 (off) and 1 (on).  The default is '0'.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_fugawi"></a>Fugawi (fugawi)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p> This was a requested <a class="link" href="#fmt_csv" title="Comma separated values (csv)">CSV format</a>, and is <span class="emphasis"><em>not</em></span> the proprietary
binary format used by <a class="ulink" href="http://www.fugawi.com" target="_top">Fugawi</a>. Like any other CSV format, GPSBabel
cannot read tracks in this format, but converting a track into it and
then importing as track in Fugawi works.</p><p> It is known to work with Fugawi V3.1.4.635. When
importing/exporting waypoints, one has to specify the order of fields
as follows (names of fields may depend on the language used by
Fugawi):</p><table border="0" summary="Simple list" class="simplelist"><tr><td> - Name</td></tr><tr><td> - Comment</td></tr><tr><td> - Description</td></tr><tr><td> - Latidude</td></tr><tr><td> - Longitude</td></tr><tr><td> - Altitude (metres)</td></tr><tr><td> - Date (yyyymmdd/yymmdd)</td></tr><tr><td> - Time of day (hhmmss)</td></tr></table><p> When importing tracks, use "[ignore]" instead of "Name",
"Comment" and "Description".</p><p>
            <a class="ulink" href="http://www.fugawi.com/" target="_top">http://www.fugawi.com/</a>
         </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_g7towin"></a>G7ToWin data files (.g7t) (g7towin)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read routes
        </p></li></ul></div><p>
  Like GPSBabel, <a class="ulink" href="http://www.gpsinformation.org/ronh/g7towin.htm" target="_top">G7ToWin</a> is a program which allows uploading and
  downloading information from several GPS devices (Garmin, Lowrance/Eagle, Magellan).
  G7ToWin has its own data format, which is an enhanced format used in Gardown.
</p><p>
  This format can read both file types, G7ToWin (.g7t) and Gardown (.gdn).
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_garmin301"></a>Garmin 301 Custom position and heartrate (garmin301)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>This is a very simple format that
is most useful for exporting data from units that support heart rate
data such as
<span class="productname">Garmin Forerunner 301</span>™,
<span class="productname">Garmin Forerunner 305</span>™, and
<span class="productname">Garmin Edge 305</span>™, and
to other programs
for analysis.   It's a simple comma delimited format that includes the
timestamp, 3D position information and heart rate so you can pull it
into a spreadsheet or graphing program. </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_garmin_g1000"></a>Garmin G1000 datalog input filter file (garmin_g1000)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
Input format for Garmin G1000 integrated avionics system datalog generated by 
G1000 system software version 563.20 or later. This datalog is automatically 
generated and stored to a standard SD card if one is inserted in the *upper* 
SD card slot on the G1000's MFD (right-hand display on 2-screen installations, 
center display on 3-screen installations). 
</p><p>
Supports conversion of GPS track (including timestamp) and barometric altitude 
data to any of GPSBabel's output formats. Does not include support for G1000 
stored flight plan (.fpl) route files or user waypoints. Tested on datalogs 
from Cessna 182T and Turbo 182T, but it should accommodate G1000 datalogs 
from other airframes as well. If any conversion failures or errors occur, 
check datalog csv file for incomplete or corrupted records/rows, delete 
those records/rows from the datalog file and reattempt.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_glogbook"></a>Garmin Logbook XML (glogbook)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
  This is the XML format used by the Garmin Logbook product
  that ships with Forerunner and Foretrex.  
  As of early 2006, this program is apparently  been discontinued in favor of
  <a class="link" href="#fmt_gtrnctr" title="Garmin Training Center (.tcx) (gtrnctr)">Garmin Training Center</a>.

  See: <a class="ulink" href="http://www.garmin.com" target="_top">http://www.garmin.com</a>  
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_gdb"></a>Garmin MapSource - gdb (gdb)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_gdb_o_cat" title="cat option">cat</a>, <a class="link" href="#fmt_gdb_o_bitscategory" title="bitscategory option">bitscategory</a>, <a class="link" href="#fmt_gdb_o_ver" title="ver option">ver</a>, <a class="link" href="#fmt_gdb_o_via" title="via option">via</a>, <a class="link" href="#fmt_gdb_o_roadbook" title="roadbook option">roadbook</a> .</p><p> 
  Support for the "Garmin GPS Database" format used by
  default in <span class="productname">MapSource</span>™ versions since release 6.0 of 
  that product. By default GPSBabel creates
  gdb files of version 2.  Version 2 is used in Mapsource 6.3 and 6.5.   This format
  is also used by <span class="productname">Garmin BaseCamp</span>™ for Mac and Windows.
</p><p> 
  Garmin GPS database is an undocumented file format. The
  basic info for this module came from the existing MapSource
  conversion code.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gdb_o_cat"></a><code class="option">cat</code> option</h3></div></div></div><p>
      Default category on output (1..16).
    </p><p>
This option specifies the default category for gdb output.  It should be a 
number from 1 to 16.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gdb_o_bitscategory"></a><code class="option">bitscategory</code> option</h3></div></div></div><p>
      Bitmap of categories.
    </p><p>
 This option is closely related to the 'category' option.  While category 
 allows you to choose a single category that waypoints should appear in,
 this options allows you to specify a bitmask to be used for the category.
 Options may be specified in either decimal or hex.
</p><div class="example"><a id="gdb_bitscategory"></a><div class="example-title">Example 3.6. Example for gdb bitcategory option to put all waypoints in categories 1 and 16.</div><div class="example-contents"><p>
  The following two commands are equivalent.  They place a the point in both the first and last of the sixteen available categories.
  <strong class="userinput"><code>
	 gpsbabel -i gpx -f PocketQuery.gpx -o gdb,bitscategory=32769 -F foo.gdb
  </code></strong>
  <strong class="userinput"><code>
	 gpsbabel -i gpx -f PocketQuery.gpx -o gdb,bitscategory=0x8001 -F foo.gdb
  </code></strong>
  
</p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gdb_o_ver"></a><code class="option">ver</code> option</h3></div></div></div><p>
      Version of gdb file to generate (1..3).
    </p><p>
This option specifies the data format version for the output file.  Version
2 is the default.  Currently, the only other valid values for this option are
1 and 3.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gdb_o_via"></a><code class="option">via</code> option</h3></div></div></div><p>
      Drop route points that do not have an equivalent waypoint (hidden points).
    </p><p>
This option instructs GPSBabel to drop hidden (calculated) points from 
routes.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gdb_o_roadbook"></a><code class="option">roadbook</code> option</h3></div></div></div><p>
      Include major turn points (with description) from calculated route.
    </p><p>
  If this option is specified, GPSBabel drops all calculated route points, 
  with exception of points with a description (i.e. "Make U-turns until you know where you are.").
  The priority of this option is higher than of the <code class="option">via</code> option. 
  A value of 1 or y overwrites the <code class="option">via</code> settings.
</p><div class="example"><a id="gdb_roadbook_option"></a><div class="example-title">Example 3.7. Using gdb option <code class="option">roadbook</code> to create simple html roadbook</div><div class="example-contents"><p>
    <strong class="userinput"><code>
      gpsbabel -i gdb,roadbook -f sample.gdb -x nuketypes,waypoints,tracks -x transform,wpt=rte -o html -F roadbook.html
    </code></strong>
  </p><p>
    Because gdb internally creates a route AND a waypoint list, you have to drop all
    waypoints and transform the route into waypoints in order to get a well ordered
    html output. We suggest these steps for all waypoint-only formats as html. 
  </p></div></div><br class="example-break" /></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_mapsource"></a>Garmin MapSource - mps (mapsource)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_mapsource_o_snlen" title="snlen option">snlen</a>, <a class="link" href="#fmt_mapsource_o_snwhite" title="snwhite option">snwhite</a>, <a class="link" href="#fmt_mapsource_o_mpsverout" title="mpsverout option">mpsverout</a>, <a class="link" href="#fmt_mapsource_o_mpsmergeout" title="mpsmergeout option">mpsmergeout</a>, <a class="link" href="#fmt_mapsource_o_mpsusedepth" title="mpsusedepth option">mpsusedepth</a>, <a class="link" href="#fmt_mapsource_o_mpsuseprox" title="mpsuseprox option">mpsuseprox</a> .</p><p> 
  This format supports the Garmin <span class="productname">Mapsource</span>™ product family.
</p><p>
  This format is based on significant reverse-engineering and guesswork.
  GPSBabel's output appears to be compatible with the various versions of 
  MapSource.  Icon mapping is attempted between different MapSource versions.  
  Altitude is supported, but proximity and depth are not.  
</p><p>
  Naming files *.mps will allow file-&gt;open in Mapsource to find the files 
  more easily.  
</p><p>
  Versions 3, 4, and 5 of the Mapsource data format are handled automatically 
  on input.  By default the output is version 5.  (Until 3/2004, it was
  version 3, but since Mapsource updates are free, the convenience of
  having modern icon sets outweighs the backward compatibility concern.
  Users of other versions can either upgrade or specify the switches to
  get output in a compatible format.)  Waypoints, routes, and tracklogs are 
  all handled, but map sets are ignored.
</p><p> 
  Information on the Garmin Mapsource format was provided by Ian Cowley and 
  Mark Bradley.  The code was implemented by Robert Lipe and Mark Bradley.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mapsource_o_snlen"></a><code class="option">snlen</code> option</h3></div></div></div><p>
      Length of generated shortnames.
    </p><p>
This option specifies the length of generated short names on output.  The 
default is 10 characters.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mapsource_o_snwhite"></a><code class="option">snwhite</code> option</h3></div></div></div><p>
      Allow whitespace synth. shortnames.
    </p><p>
This option specifies whether to allow whitespace (space, tab, etc.) in 
generated short names on output.  The default is to not allow whitespace.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mapsource_o_mpsverout"></a><code class="option">mpsverout</code> option</h3></div></div></div><p>
      Version of mapsource file to generate (3,4,5).
    </p><p>
This option specifies the format version for the output file.  The default
is version 5, as noted above.  Supported versions are 3, 4, and 5.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mapsource_o_mpsmergeout"></a><code class="option">mpsmergeout</code> option</h3></div></div></div><p>
      Merge output with existing file.
    </p><p>
This option causes the output to be merged with a pre-existing output file.
This allows MapSource sections that aren't handled by GPSBabel (e.g. map sets)
to be preserved.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mapsource_o_mpsusedepth"></a><code class="option">mpsusedepth</code> option</h3></div></div></div><p>
      Use depth values on output (default is ignore).
    </p><p>
This option causes GPSBabel to write depth values for waypoints.  Most 
input formats do not support depth values, so the default is to not write
them.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mapsource_o_mpsuseprox"></a><code class="option">mpsuseprox</code> option</h3></div></div></div><p>
      Use proximity values on output (default is ignore).
    </p><p>
This option causes GPSBabel to write proximity values for waypoints.  Most 
input formats do not support proximity values, so the default is to not write
them.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_garmin_txt"></a>Garmin MapSource - txt (tab delimited) (garmin_txt)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_garmin_txt_o_date" title="date option">date</a>, <a class="link" href="#fmt_garmin_txt_o_datum" title="datum option">datum</a>, <a class="link" href="#fmt_garmin_txt_o_dist" title="dist option">dist</a>, <a class="link" href="#fmt_garmin_txt_o_grid" title="grid option">grid</a>, <a class="link" href="#fmt_garmin_txt_o_prec" title="prec option">prec</a>, <a class="link" href="#fmt_garmin_txt_o_temp" title="temp option">temp</a>, <a class="link" href="#fmt_garmin_txt_o_time" title="time option">time</a>, <a class="link" href="#fmt_garmin_txt_o_utc" title="utc option">utc</a> .</p><p>
This is a textual format that contains nearly all of the information 
contained in the <span class="productname">MapSource</span>™ main format, <a class="link" href="#fmt_gdb" title="Garmin MapSource - gdb (gdb)">GDB</a>.
This format also contains some computed values such as distances between 
routepoints and trackpoints, speed, and course (heading).
</p><p>
The main goal of garmin_txt is to make aviation data more available. Because 
<span class="productname">MapSource</span>™ supports only the export, GPSBabel gives you the possibility to 
bring aviation data into <span class="productname">MapSource</span>™.
</p><p>
During the export with <span class="productname">MapSource</span>™, some fields are written using local settings
of <span class="productname">MapSource</span>™ and Windows. These include grid format, gps datum, distance and
temperature units, and the representation of date and time fields. GPSBabel 
tries to read all items automatically. Problems with date and time format can 
be solved with the 'date' and 'time' options.
</p><div class="example"><a id="all_garmin_txt_options"></a><div class="example-title">Example 3.8. Command showing garmin_txt output with all options</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i garmin_txt,date="MM/DD/YYYY",time="hh:mm:ss xx" -f in.txt -o garmin_txt,date="DD.MM.YYYY",datum="WGS 72",dist=m,prec=6,temp=c,time="HH:mm:ss",utc=+2 -F out.txt</code></strong></p></div></div><br class="example-break" /><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_txt_o_date"></a><code class="option">date</code> option</h3></div></div></div><p>
      Read/Write date format (i.e. yyyy/mm/dd).
    </p><p>
This option specifies the input and output format for the date.  The format 
is written similarly to those in Windows.  An example format is "YYYY/MM/DD".
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_txt_o_datum"></a><code class="option">datum</code> option</h3></div></div></div><p>
      GPS datum (def. WGS 84).
    </p><p>
This option specifies the datum to be used on output.  Valid values for this 
option are listed in <a class="xref" href="#Datums" title="Appendix A. Supported Datums">Appendix A, <em>Supported Datums</em></a>.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_txt_o_dist"></a><code class="option">dist</code> option</h3></div></div></div><p>
      Distance unit [m=metric, s=statute].
    </p><p>
This option specifies the unit to be used when outputting distance
values.  Valid values are M for metric (m/km/kph) or S for statute
(ft/mi/mph).
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_txt_o_grid"></a><code class="option">grid</code> option</h3></div></div></div><p>
      Write position using this grid..
    </p><p>
  This value specifies the grid to be used on write.
</p><div class="table"><a id="garmin_grid"></a><div class="table-title">Table 3.1. Grid values for garmin_txt</div><div class="table-contents"><table summary="Grid values for garmin_txt" border="1"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th># idx</th><th>short</th><th>file-header</th><th>sample</th></tr></thead><tbody><tr><td>0</td><td>ddd</td><td>Lat/Lon hddd.ddddd</td><td>    S26.25333 E27.92333</td></tr><tr><td>1</td><td>dmm</td><td>Lat/Lon hddd°mm.mm</td><td>N33 56.539 W118 24.471</td></tr><tr><td>2</td><td>dms</td><td>Lat/Lon hddd°mm'ss.s</td><td>S25 25 26.8 E28 06 07.3</td></tr><tr><td>3</td><td>bng</td><td>British National Grid</td><td>TQ 18919 69392</td></tr><tr><td>4</td><td>utm</td><td>Universal Transverse Mercator</td><td>33 U 318293 5637154</td></tr><tr><td>5</td><td>swiss</td><td>Swiss grid</td><td>776519 167359</td></tr></tbody></table></div></div><br class="table-break" /><p>
  Idx or short are valid params for this option.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_txt_o_prec"></a><code class="option">prec</code> option</h3></div></div></div><p>
      Precision of coordinates.
    </p><p>
This option specifies the precision to be used when writing coordinate values.
Precision is the number of digits after the decimal point.  The default
precision is 3.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_txt_o_temp"></a><code class="option">temp</code> option</h3></div></div></div><p>
      Temperature unit [c=Celsius, f=Fahrenheit].
    </p><p>
This option specifies the unit to be used when writing temperature values.
Valid values are C for Celsius or F for Fahrenheit.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_txt_o_time"></a><code class="option">time</code> option</h3></div></div></div><p>
      Read/Write time format (i.e. HH:mm:ss xx).
    </p><p>
This option specifies the input and output format for the time.  The format 
is written similarly to those in Windows.  An example format is "hh:mm:ss xx".
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_txt_o_utc"></a><code class="option">utc</code> option</h3></div></div></div><p>
      Write timestamps with offset x to UTC time.
    </p><p>
This option specifies the local time zone to use when writing times.  It
is specified as an offset from Universal Coordinated Time (UTC) in hours.  
Valid values are from -23 to +23.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_pcx"></a>Garmin PCX5 (pcx)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_pcx_o_deficon" title="deficon option">deficon</a>, <a class="link" href="#fmt_pcx_o_cartoexploreur" title="cartoexploreur option">cartoexploreur</a> .</p><p> Garmin documents only PCX5, an older format limited to
the lame NMEA six-character waypoint names that's treated as a
second-class citizen in current versions of MapSource.  In Mapsource,
use file-&gt;import to read these files.  If you name the files *.wpt,
Mapsource will find them more easily.
</p><p> In general, you should prefer the "mapsource" file format
to this one.
</p><p>This format has been extended to handle many - but not all - 
	files from <a class="ulink" href="http://www.gpsu.co.uk/index.html" target="_top">GPS Utility</a>.  If you encounter something that GPSBabel does not handle well, use
the free version of GPSUtil to read it and save as something more common.
	</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_pcx_o_deficon"></a><code class="option">deficon</code> option</h3></div></div></div><p>
      Default icon name.
    </p><p>
  The deficon option is used to control the icon output when writing to this format.   It overrides any icon information that might be present in the source data.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_pcx_o_cartoexploreur"></a><code class="option">cartoexploreur</code> option</h3></div></div></div><p>
      Write tracks compatible with Carto Exploreur.
    </p><p>
  Carto Exploreur requires a slightly incompatible variation of the PCX format
when written.  Specifying this option on write tells us to create that strain of PCX.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_garmin_poi"></a>Garmin POI database (garmin_poi)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
  The <a class="ulink" href="http://www.garmin.com/support/agree.jsp?id=927" target="_top">Garmin POI loader</a> 
  loads custom points of interest into certain models of
  Garmin GPS receivers.  (As of this writing, only the models introduced
  in 2005 and later are supported.  See Garmin's site for more info.)
  The garmin_poi format produces csv files that can be
  converted into POI files by Garmin's POI loader.
</p><p>
  This format was mostly useful when POI Loader couldn't read GPX and we
  couldn't write GPI.  See <a class="link" href="#fmt_garmin_gpi" title="Garmin Points of Interest (.gpi) (garmin_gpi)">GPSBabel's GPI doc</a>.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_garmin_gpi"></a>Garmin Points of Interest (.gpi) (garmin_gpi)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_garmin_gpi_o_alerts" title="alerts option">alerts</a>, <a class="link" href="#fmt_garmin_gpi_o_bitmap" title="bitmap option">bitmap</a>, <a class="link" href="#fmt_garmin_gpi_o_category" title="category option">category</a>, <a class="link" href="#fmt_garmin_gpi_o_hide" title="hide option">hide</a>, <a class="link" href="#fmt_garmin_gpi_o_descr" title="descr option">descr</a>, <a class="link" href="#fmt_garmin_gpi_o_notes" title="notes option">notes</a>, <a class="link" href="#fmt_garmin_gpi_o_position" title="position option">position</a>, <a class="link" href="#fmt_garmin_gpi_o_proximity" title="proximity option">proximity</a>, <a class="link" href="#fmt_garmin_gpi_o_sleep" title="sleep option">sleep</a>, <a class="link" href="#fmt_garmin_gpi_o_speed" title="speed option">speed</a>, <a class="link" href="#fmt_garmin_gpi_o_unique" title="unique option">unique</a>, <a class="link" href="#fmt_garmin_gpi_o_units" title="units option">units</a> .</p><p>
   The format garmin_gpi supports the binary POI (.gpi) files that are useable
   on newer Garmin GPS receivers.  See <a class="link" href="#fmt_garmin_poi" title="Garmin POI database (garmin_poi)">garmin_poi</a> for additional information about Garmin's own Poiloader program.
   <a class="ulink" href="http://www.garmin.com/support/agree.jsp?id=927" target="_top">Garmin POI-Loader</a> is the standard application that creates GPI files
   with all possible features.
</p><p>
  Some of the third party and commercial GPI files are using some kind of
  encryption or compression that makes the file contents completely unreadable
  to us. If you get an error "Unsupported code page NNN. File is likely
   encrypted." means we could basically recognize it as a Garmin GPI file,
   but it's mangled beyond what we're likely to successfully read.
</p><p>
   The layout of GPI files isn't documented and our module was created
   via reverse engineering. If you get a problem on reading or writing 
   a GPI file, please provide that file (mailto:gpsbabel-misc@lists.sourceforge.net).
</p><p>
   At this time we don't support special features as "Tour-Guide" or links
   to sounds and pictures.
</p><div class="important"><h3 class="title">Important</h3><p>
   Creation timestamp issue: See the option <a class="link" href="#fmt_garmin_gpi" title="Garmin Points of Interest (.gpi) (garmin_gpi)">sleep</a> !!!
</p><p>
	This module does not support direct transfer of .GPI files to
	receivers in Garmin protocol mode.  For units like Nuvi, Zumo, or 
	Streetpilot, just choose a file that's on the drive where your
	GPS is mounted.   For units like the X series (GPSMap 60CSx, GPSMap 60Cx, Legend Hcx, etc.) 
	you must explictly put the unit in mass storage mode or mount
	the memory chip in an external reader and transfer the file 
	directly.
</p></div><div class="example"><a id="all_garmin_gpi_options"></a><div class="example-title">Example 3.9. Command showing garmin_gpi output example</div><div class="example-contents"><p>
    <strong class="userinput"><code>
      gpsbabel -i gpx -f "My Points.gpx" -o garmin_gpi,category="Nice Restaurants",bitmap=restaurant.bmp,notes -F "My Points.gpi"
    </code></strong>
  </p></div></div><br class="example-break" /><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_gpi_o_alerts"></a><code class="option">alerts</code> option</h3></div></div></div><p>
      Enable alerts on speed or proximity distance.
    </p><p>
   Because speed isn't a real member of a normal waypoint, you can put the speed values into
   the waypoint names. "Point@30" will result in a speed value of 30. By default we assume these
   values are in kilometers per hour.
</p><p>
   Proximity distance is also supported by <a class="link" href="#fmt_gpx" title="GPX XML (gpx)">GPX</a>, <a class="link" href="#fmt_gdb" title="Garmin MapSource - gdb (gdb)">Garmin GDB</a>, <a class="link" href="#fmt_ozi" title="OziExplorer (ozi)">OZI Explorer</a>, 
   <a class="link" href="#fmt_compegps" title="CompeGPS data files (.wpt/.trk/.rte) (compegps)">CompeGPS</a> and <a class="link" href="#fmt_unicsv" title="Universal csv with field structure in first line (unicsv)">Universal CSV</a>.
</p><p>
  <strong class="userinput"><code>
    gpsbabel -i gpx -f "warnings.gpx" -o garmin_gpi,alerts=1 -F "warnings.gpi"
  </code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_gpi_o_bitmap"></a><code class="option">bitmap</code> option</h3></div></div></div><p>
      Use specified bitmap on output.
    </p><p>
   The bitmap (BMP) should be 24x24 (or smaller) and can be in
   RGB-colors (24- and 32-bit) or 8-bit indexed color format.
</p><p>
  If you're starting from images in another format, you may need to
  use another tool like Gimp or ImageMagick's convert to get the imaga
  into oen of the above formats to avoid errors about "Unsupported color 
  depth".
</p><p>
  Not all devices can support all color depths.   GPSBabel (and its 
  developers) have no way of knowing what is supported on any given model
  so some experimentation may be necessary on your part.   It was reported
  that a Nuvi 3790, for example, will read the POIs only if they use 8BPP.
</p><p>
   A color value of 0xFF00FF (blue=255, green=0, red=255), 
   also called "Magenta", can be used for transparent areas.
</p><p>
  <strong class="userinput"><code>
    gpsbabel -i gpx -f "My Points.gpx" -o garmin_gpi,bitmap="tux.bmp" -F "My Points.gpi"
  </code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_gpi_o_category"></a><code class="option">category</code> option</h3></div></div></div><p>
      Default category on output.
    </p><p>
    With this option you can specify the category which is primary
    visible on the device (default is "My points").
</p><p>
  <strong class="userinput"><code>
    gpsbabel -i gpx -f "My Points.gpx" -o garmin_gpi,category="Best Restaurants" -F "My Points.gpi"
  </code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_gpi_o_hide"></a><code class="option">hide</code> option</h3></div></div></div><p>
      Don't show gpi bitmap on device.
    </p><p>
   For a large list of points (or whyever) it can be useful when
   no bitmaps are displayed on device. With this option no bitmap
   is stored and displayed.
</p><p>
  <strong class="userinput"><code>
    gpsbabel -i gpx -f "My Points.gpx" -o garmin_gpi,hide -F "My Points.gpi"
  </code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_gpi_o_descr"></a><code class="option">descr</code> option</h3></div></div></div><p>
      Write description to address field.
    </p><p>
   The GPI address field is often visible in lists on the device. Use this
   option if you want to see the waypoint description (which can be an address too)
   in this lists.
</p><p>
  <strong class="userinput"><code>
    gpsbabel -i gpx -f "My Points.gpx" -o garmin_gpi,descr -F "My Points.gpi"
  </code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_gpi_o_notes"></a><code class="option">notes</code> option</h3></div></div></div><p>
      Write notes to address field.
    </p><p>
   The GPI address field is often visible in lists on the device. Use this
   option if you want to see the waypoint notes (which can be an address too)
   in this lists.
</p><p>
  <strong class="userinput"><code>
    gpsbabel -i gpx -f "My Points.gpx" -o garmin_gpi,notes -F "My Points.gpi"
  </code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_gpi_o_position"></a><code class="option">position</code> option</h3></div></div></div><p>
      Write position to address field.
    </p><p>
   The GPI address field is often visible in lists on the device. Use this
   option if you want to see the waypoint position (coordinates) in this lists.
</p><p>
  <strong class="userinput"><code>
    gpsbabel -i gpx -f "My Points.gpx" -o garmin_gpi,position -F "My Points.gpi"
  </code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_gpi_o_proximity"></a><code class="option">proximity</code> option</h3></div></div></div><p>
      Default proximity.
    </p><p>
  When no proximity data is available in the source input, GPSBabel uses this as the default proximity value.
  The parameter has to be in meters, or, when units=s specified, in miles.
  <a class="link" href="#fmt_garmin_gpi_o_alerts" title="alerts option">alerts</a> are automatically enabled.
</p><div class="example"><a id="garmin_gpi_speedcams"></a><div class="example-title">Example 3.10. Read GPX file, create GPI to alert when you're 1/2 mile from a speed camera.</div><div class="example-contents"><p>
  <strong class="userinput"><code>
    gpsbabel -i gpx -f "SpeedCameras.gpx" -o garmin_gpi,units=s,proximity=0.5 -F "SpeedCameras.gpi"
  </code></strong>
</p></div></div><br class="example-break" /><p>
  Its also possible to append a specific distance unit to the parameter.
</p><p>
  <strong class="userinput"><code>
    gpsbabel -i gpx -f "SpeedCameras.gpx" -o garmin_gpi,proximity=500m -F "SpeedCameras.gpi"
  </code></strong>
</p><p>
  </p><div class="table"><a id="distance_units"></a><div class="table-title">Table 3.2. Supported distance units (garmin_gpi)</div><div class="table-contents"><table summary="Supported distance units (garmin_gpi)" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Unit</th><th>Description</th></tr></thead><tbody><tr><td>fa</td><td>Fathoms</td></tr><tr><td>feet</td><td>Feet</td></tr><tr><td>ft</td><td>Feet</td></tr><tr><td>km</td><td>Kilometers</td></tr><tr><td>m</td><td>Meters</td></tr><tr><td>mi</td><td>Miles</td></tr><tr><td>nm</td><td>Nautical miles</td></tr></tbody></table></div></div><p><br class="table-break" />
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_gpi_o_sleep"></a><code class="option">sleep</code> option</h3></div></div></div><p>
      After output job done sleep n second(s).
    </p><p>
  The Garmin units seem to use the creation timestamp of GPI files for internal purposes. 
  In other words,  if you load GPI files with same creation timestamp on your device, 
  strange things will happen,  such as having missing or repeated POIs. With the sleep option, GPSBabel waits a given
  number of seconds after the GPI file was written.
</p><p>
  In the normal case of using GPSBabel from the command line or from the GUI, the chance of creating files
  with the same timestamp is in the nearly ZERO. In scripts or batch files where you are writing multiple files - even from different GPSBabel instances - the odds of this happening is rather good.
  The sleep option forces GPSBabel to wait after creating a file to ensure the timestamps are unique. Values are specified in seconds and can be 1 or more.
</p><p>
  <strong class="userinput"><code>
    gpsbabel -i gpx -f "SpeedCameras.gpx" -o garmin_gpi,sleep=1 -F "SpeedCameras.gpi"
  </code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_gpi_o_speed"></a><code class="option">speed</code> option</h3></div></div></div><p>
      Default speed.
    </p><p>
  When no speed data is available in the source input, GPSBabel uses this as the default speed value.
  The parameter has to be in kilometers per hour, or, when units=s specified,
  in miles per hour. <a class="link" href="#fmt_garmin_gpi_o_alerts" title="alerts option">alerts</a> are
  automatically enabled.
</p><p>
  <strong class="userinput"><code>
    gpsbabel -i gpx -f "SpeedCameras.gpx" -o garmin_gpi,units=s,speed=30 -F "SpeedCameras.gpi"
  </code></strong>
</p><p>
  Its also possible to append a specific speed unit to the parameter.
</p><p>
  <strong class="userinput"><code>
    gpsbabel -i gpx -f "SpeedCameras.gpx" -o garmin_gpi,speed=30mph -F "SpeedCameras.gpi"
  </code></strong>
</p><p>
  </p><div class="table"><a id="garmin_gpi_speed_units"></a><div class="table-title">Table 3.3. Supported speed units (garmin_gpi)</div><div class="table-contents"><table summary="Supported speed units (garmin_gpi)" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Unit</th><th>Description</th></tr></thead><tbody><tr><td>km/h</td><td>Kilometers per hour</td></tr><tr><td>kmh</td><td>Kilometers per hour</td></tr><tr><td>kph</td><td>Kilometers per hour</td></tr><tr><td>kt</td><td>Knots</td></tr><tr><td>knot</td><td>Knots</td></tr><tr><td>m/s</td><td>Meters per second</td></tr><tr><td>mps</td><td>Meters per second</td></tr><tr><td>mi/h</td><td>Miles per hour</td></tr></tbody></table></div></div><p><br class="table-break" />
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_gpi_o_unique"></a><code class="option">unique</code> option</h3></div></div></div><p>
      Create unique waypoint names (default = yes).
    </p><p>
   Don't create unique names sample:
</p><p>
  <strong class="userinput"><code>
    gpsbabel -i gpx -f "My Points.gpx" -o garmin_gpi,unique=0 -F "My Points.gpi"
  </code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_gpi_o_units"></a><code class="option">units</code> option</h3></div></div></div><p>
      Units used for names with @speed ('s'tatute or 'm'etric).
    </p><p>
   Sample command tells GPSBabel to handle speed values in miles per hour:
  <strong class="userinput"><code>
    gpsbabel -i gpx -f "My Points.gpx" -o garmin_gpi,units=s -F "My Points.gpi"
  </code></strong>
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_garmin"></a>Garmin serial/USB protocol (garmin)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_garmin_o_snlen" title="snlen option">snlen</a>, <a class="link" href="#fmt_garmin_o_snwhite" title="snwhite option">snwhite</a>, <a class="link" href="#fmt_garmin_o_deficon" title="deficon option">deficon</a>, <a class="link" href="#fmt_garmin_o_get_posn" title="get_posn option">get_posn</a>, <a class="link" href="#fmt_garmin_o_power_off" title="power_off option">power_off</a>, <a class="link" href="#fmt_garmin_o_erase_t" title="erase_t option">erase_t</a>, <a class="link" href="#fmt_garmin_o_resettime" title="resettime option">resettime</a>, <a class="link" href="#fmt_garmin_o_category" title="category option">category</a>, <a class="link" href="#fmt_garmin_o_bitscategory" title="bitscategory option">bitscategory</a> .</p><p> 
	GPSBabel supports a wide variety of Garmin hardware via serial
	on most operating systems and USB on Windows, Linux, and OS X.
</p><p> 
	For serial models, be sure the GPS is set for "Garmin
	mode" in setup and that nothing else (PDA hotsync programs, gpsd,
	getty, pppd, etc.) is using the serial port.
</p><p> 
	Supported Garmin GPS receivers with USB include 
	</p><table border="0" summary="Simple list" class="simplelist"><tr><td>Astro</td><td>Forerunner 205</td><td>GPSMAP 60CSx</td><td>StreetPilot 2650</td></tr><tr><td>Edge 205</td><td>Forerunner 301</td><td>GPSMAP 60Cx</td><td>StreetPilot 2720</td></tr><tr><td>Edge 305</td><td>Forerunner 305</td><td>GPSMAP 76C</td><td>StreetPilot 2730</td></tr><tr><td>eTrex Legend C</td><td>Foretrex 201</td><td>GPSMAP 76CS</td><td>StreetPilot 2820</td></tr><tr><td>eTrex Legend Cx</td><td>Foretrex 301</td><td>GPSMAP 76CSX</td><td>StreetPilot 7200</td></tr><tr><td>eTrex Legend H</td><td>GPS 18<a href="#ftn.posnonly" class="footnote" id="posnonly"><sup class="footnote">[1]</sup></a></td><td>GPSMAP 76Cx</td><td>StreetPilot 7500</td></tr><tr><td>eTrex Legend HCx</td><td>GPSMAP 195</td><td>GPSMAP 96</td><td>StreetPilot c310</td></tr><tr><td>eTrex Summit Cx</td><td>GPSMAP 276C</td><td>GPSMAP 96C</td><td>StreetPilot c320</td></tr><tr><td>eTrex Summit HC</td><td>GPSMAP 295</td><td>Quest</td><td>StreetPilot c330</td></tr><tr><td>eTrex Venture C</td><td>GPSMAP 296C</td><td>Quest II</td><td>StreetPilot c340</td></tr><tr><td>eTrex Venture Cx</td><td>GPSMAP 378</td><td>Rhino 520</td><td>StreetPilot i2</td></tr><tr><td>eTrex Venture HC</td><td>GPSMAP 396</td><td>Rhino 530</td><td>StreetPilot i3</td></tr><tr><td>eTrex Vista C</td><td>GPSMAP 478</td><td>Rhino 520 HCx</td><td>StreetPilot i5</td></tr><tr><td>eTrex Vista Cx</td><td>GPSMAP 496</td><td>Rhino 530 HCx</td><td> </td></tr><tr><td>eTrex Vista H</td><td>GPSMAP 60C</td><td>StreetPilot 2610</td><td> </td></tr><tr><td>eTrex Vista HCx</td><td>GPSMAP 60CS</td><td>StreetPilot 2620</td><td> </td></tr></table><p>
</p><p>the following Bluetooth Garmin products:
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>GPS 10<a href="#ftn.posnonly" class="footnoteref"><sup class="footnoteref">[1]</sup></a></td><td> </td><td> </td><td> </td></tr></table><p>
</p><p>and most serial Garmin GPS receivers including:
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>eMap</td><td>eTrex H</td><td>GPS 12 </td><td>Rhino 110</td></tr><tr><td>eTrex Camo</td><td>Forerunner 201</td><td>GPS 12XL </td><td>Rhino 120</td></tr><tr><td>eTrex Legend</td><td>Foretrex 201</td><td>GPS III </td><td>Rhino 130</td></tr><tr><td>eTrex Summit</td><td>Geko 201</td><td>GPS III+ </td><td>StreetPilot III</td></tr><tr><td>eTrex Venture</td><td>Geko 301</td><td>GPS II </td><td>StreetPilot III+</td></tr><tr><td>eTrex Vista</td><td>GPS 12CX </td><td>GPS II+ </td><td> </td></tr><tr><td>eTrex (Basic Yellow)</td><td>GPS 12Map </td><td>GPS V</td><td> </td></tr></table><p>
</p><p>
The following Garmin GPS receivers are supported, but they do not
support Garmin communication protocol and don't work with the 
<code class="option">garmin</code> option.  To use these receivers, read or write
GPX files from the mass storage device as mounted on your computer.
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>eTrex 10<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 255<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 770<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 1690T<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>eTrex 20<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 250W<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 775T<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 3750<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>eTrex 30<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 255W<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 780<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 3760T<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>Colorado 300<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 260<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 785T<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 3790T<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>Colorado 400c<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 265T<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 880<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Oregon 200<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>Colorado 400i<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 265WT<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 885T<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Oregon 300<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>Colorado 400t<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 260W<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 1200<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Oregon 400c<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>Dakota 10<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 270<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 1250<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Oregon 400i<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>Dakota 20<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 275T<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 1260T<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Oregon 400t<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>GPSMap 62<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 300<a href="#ftn.gpx" class="footnote" id="gpx"><sup class="footnote">[2]</sup></a></td><td>Nuvi 1300<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Oregon 450<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>GPSMap 62sc<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 310<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 1350<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Oregon 450t<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>GPSMap 62stc<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 350<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 1370T<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Oregon 550<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>GPSMap 78<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 370<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 1390T<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Oregon 550t<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>GPSMap 78s<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 465T<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 1350<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>StreetPilot c510<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>GPSMap 78sc<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 500<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 1490T<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>StreetPilot c530<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>Montana 600<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 550<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 2250<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>StreetPilot c550<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>Montana 650<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 600<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 2250LT<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>StreetPilot c580<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>Montana 650t<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 650<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 2350<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Road Tech Zumo<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>Nuvi 30<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 650FM<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 2350LT<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Zumo 220<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>Nuvi 40<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 660<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 2360LT<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Zumo 450<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>Nuvi 50<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 670<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 2405<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Zumo 500<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>Nuvi 200<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 680<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 2450<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Zumo 550<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>Nuvi 205<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 750<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 2450LM<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Zumo 660<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>Nuvi 200W<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 755T<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 2450LT<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Zumo 665<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>Nuvi 205W<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 760<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 2450LMT<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Surely any Garmin product that Garmin actually sensibly designed after 2006 or so.<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td></tr><tr><td>Nuvi 250<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 765T<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td>Nuvi 2505<a href="#ftn.gpx" class="footnoteref"><sup class="footnoteref">[2]</sup></a></td><td> </td></tr></table><p>
</p><p>
	None of the GPSBabel developers has access to every model on that
	list, but we've received reports of success and/or have reasonable
	expectations that the above models work. If you succeed with
	a model that is not on that list, please send a message to the
	gpsbabel-misc mailing list with the details so that we may add it.
</p><p>
	Not every feature on every model is supported.  For example, 
	while we do extract data such as heart rate and temperature from
	tracks on the sporting models like Edge and Forerunner, GPSBabel
	is not a fitness program at its core and does not support features 
	like workouts or calorie/fitness zone data. Furthermore, sporting
	models don't support track upload. When trying to upload tracks to
	these devices, GPSBabel converts them to courses on the fly and
	uploads these instead. When uploading waypoints at the same
	time, these are converted to course points by mapping them to the
	nearest track point on the track/course (no matter how far away from
	the track they are). Since course point creation requires time
	stamps for the track points, they are created automatically assuming
	a speed of 10 km/h for tracks that lack them.
</p><p> 
	To communicate with a Garmin GPS serially, use the name of that
	serial port such as <code class="filename">COM1</code> or  <code class="filename">/dev/cu.serial</code>.  
</p><p>
	To communicate via USB use <code class="filename">usb:</code> as the filename on all OSes.   
	Thus, to read the waypoints from a Garmin USB receiver and write 
	them to a GPX file:
</p><p><strong class="userinput"><code>gpsbabel -i garmin -f usb: -o gpx -F blah.gpx</code></strong></p><p>
	If you have multiple units attached via USB, you may provide 
	a unit number, with zero being the implied default.  So if you 
	have three USB models on your system, they can be addressed as 
	<code class="filename">usb:0</code>, <code class="filename">usb:1</code>, and <code class="filename">usb:2</code>.  To get a list of recognized devices,
	specify a negative number such as:
</p><p><strong class="userinput"><code>gpsbabel -i garmin -f usb:-1</code></strong></p><p> 
When reporting problems with the Garmin format, be sure to include
the full unit model, firmware version, and be prepared to offer
debugging dumps by adding <code class="option">-D9</code> to the command line, like:
</p><p><strong class="userinput"><code> gpsbabel -D9 -i garmin -f usb: -o gpx -F blah.gpx</code></strong></p><p> 
Custom icons are supported on units that support that.
Neither GPSBabel nor your firmware know what is associated with any
given slot number.  They don't know that the picture you placed in the
first slot is a happy face, they only know they're in the lowest
numbered slot.  GPSBabel names the them consistently with Mapsource,
so they are named 'Custom 0' through 'Custom 511'.
</p><p>
	For models where the connection on the GPS is a serial interface, 
	be sure the GPS is set for "Garmin
	mode" in setup and that nothing else (PDA hotsync programs, gpsd,
	getty, pppd, etc.) is using the serial port.  
</p><p>
	For models connected via USB, we recommend use of the <code class="filename">usb:</code>
	filename.   For this to work on Windows, you must install
	the Garmin driver.  For Linux, this will fail if you have the garmin_gps
	kernel module loaded.  
	See the <a class="ulink" href="/osnotes.html" target="_top">Operating System Notes</a> for details.
</p><p>
This module also supports <a class="link" href="#tracking" title="Realtime tracking">realtime tracking</a> 
which allows realtime position reports from a Garmin GPS receiver over USB
or serial.  
</p><div class="important"><h3 class="title">Important</h3><p>The following Garmin units do not follow the standard Garmin 
communications protocol and are <span class="emphasis"><em>not supported</em></span> 
by GPSBabel.</p><p>
Marine plotters:
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>GPSMap 420</td><td>GPSMap 450</td><td>GPSMap 530</td><td>GPSMap 545</td></tr><tr><td>GPSMap 430</td><td>GPSMap 520</td><td>GPSMap 535</td><td>GPSMap 550</td></tr><tr><td>GPSMap 440</td><td>GPSMap 525</td><td>GPSMap 540</td><td>GPSMap 555</td></tr></table><p>
</p><p>The PDA products
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>iQue 3000</td></tr><tr><td>iQue 3200</td></tr><tr><td>iQue 3600</td></tr><tr><td>iQue M3</td></tr><tr><td>iQue M4</td></tr><tr><td>iQue M5</td></tr></table><p>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_o_snlen"></a><code class="option">snlen</code> option</h3></div></div></div><p>
      Length of generated shortnames.
    </p><p>This option overrides the internal logic to figure out how many
characters an addressed Garmin GPS will support when using the '-s' smartname
option.   This should be necessary only if you have a receiver type that
GPSBabel doesn't know about or if you want to "dumb down" one unit to match
another, such as wanting waypoint names in a StreetPilot 2720 (which supports
20 character names) to exactly match those in a 60CS (which supports 10).
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_o_snwhite"></a><code class="option">snwhite</code> option</h3></div></div></div><p>
      Allow whitespace synth. shortnames.
    </p><p>This options controls whether spaces are allowed in generated 
smart names when using the '-s' option.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_o_deficon"></a><code class="option">deficon</code> option</h3></div></div></div><p>
      Default icon name.
    </p><p>
This option specifies the icon or waypoint type to write for each waypoint on
output.
</p><p>
If this option is specified, its value will be used for all waypoints, not
just those that do not already have descriptions.  That is, this option
overrides any icon description that might be in the input file.
</p><p>
Value specified may be a number from the Garmin Protocol Spec or a name
as described in the <a class="xref" href="#GarminIcons" title="Appendix B. Garmin Icons">Appendix B, <em>Garmin Icons</em></a>.
</p><p>
This option has no effect on input.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_o_get_posn"></a><code class="option">get_posn</code> option</h3></div></div></div><p>
      Return current position as a waypoint.
    </p><p>This options gets the current longitude and latitude from the attached GPS device
and returns it as a single waypoint for further processing.  For example,
to return the current position from a USB Garmin to a KML file:
</p><p><strong class="userinput"><code>gpsbabel -i garmin,get_posn -f usb: -o kml -F myposition.kml</code></strong></p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_o_power_off"></a><code class="option">power_off</code> option</h3></div></div></div><p>
      Command unit to power itself down.
    </p><p>This command forces an immediate powerdown of the addressed Garmin
receiver.  It is ignored on hardware that does not support this command.
Obviously, further processing once you have sent a "power off" command to
a unit that supports it is rather futile, so place this option carefully
in your command.

</p><p><strong class="userinput"><code>gpsbabel -o garmin,power_off -F /dev/ttyS0</code></strong></p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_o_erase_t"></a><code class="option">erase_t</code> option</h3></div></div></div><p>
      Erase existing courses when writing new ones.
    </p><p>
By default, GPSBabel makes effort in order to keep courses already present on
the device, if any. This option allow to replace courses already present. If
you don't mind to keep old courses, this option is recommended because it
allows a faster transfer.
</p><p>
This option applies only to Garmin devices that support courses such as the Edge 305 or the Forerunner 305.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_o_resettime"></a><code class="option">resettime</code> option</h3></div></div></div><p>
      Sync GPS time to computer time.
    </p><p>
  This option is experimental and was added to solve a very specific problem.
  Certain Garmin units (the original black and white Vista is known to have 
  this) will sometimes scramble their clock crazy far into the future (like
  2066).  When this happens, the GPS itself may or may not work and 
  later conversations with GPSBabel may fail as the time overflows the
  documented range.  The use of <code class="option">resettime</code> brings the GPS's internal clock
  back close enough to reality that the GPS itself can then "fix" it when
  it has next a lock.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_o_category"></a><code class="option">category</code> option</h3></div></div></div><p>
      Category number to use for written waypoints.
    </p><p>This numeric option will force waypoints to be written with that
category number when sending to a Garmin receiver that has category
support. It is ignored on receivers without that capability. </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_o_bitscategory"></a><code class="option">bitscategory</code> option</h3></div></div></div><p>
      Bitmap of categories.
    </p><p>
 This option is closely related to the 'category' option.  While category 
 allows you to choose a single category that waypoints should appear in,
 this options allows you to specify a bitmask to be used for the category.
 Options may be specified in either decimal or hex.
</p><div class="example"><a id="garmin_bitcategory"></a><div class="example-title">Example 3.11. Example for garmin bitcategory option to put all waypoints in categories 1 and 16.</div><div class="example-contents"><p>
  The following two commands are equivalent.  They place a the point in both the first and last of the sixteen available categories.
  <strong class="userinput"><code>
	 gpsbabel -i gpx -f PocketQuery.gpx -o garmin,bitcategory=32769 -F usb:
  </code></strong>
  <strong class="userinput"><code>
	 gpsbabel -i gpx -f PocketQuery.gpx -o garmin,bitcategory=0x8001 -F usb:
  </code></strong>
  
</p></div></div><br class="example-break" /></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_gtrnctr"></a>Garmin Training Center (.tcx) (gtrnctr)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_gtrnctr_o_course" title="course option">course</a>, <a class="link" href="#fmt_gtrnctr_o_sport" title="sport option">sport</a>, <a class="link" href="#fmt_gtrnctr_o_course" title="course option">course</a>, <a class="link" href="#fmt_gtrnctr_o_sport" title="sport option">sport</a> .</p><p>
GPSBabel supports reading and writing of tracks in the .tcx 
format used by <span class="productname">Garmin Training Center</span>™ (GTC). GTC is the successor 
to Garmin's <span class="productname">Logbook</span>™ program for their workout units.  It is a 
free upgrade.
</p><p>
GPSBabel can read GTC v1 and v2 files, and can write v2 files. 
v2 files are most likely to have a .tcx extension. v1 files
typically have a .hst or .crs extension, depending on whether they
are in the "history" or "course" format.
</p><p>
There is a fundamental mismatch between this format and most of
what we support.  GPSBabel deals in waypoints, tracks, and routes.
While we do record things like heart rate and temperature when we know
it, the fundamentals of Training Center are different.  It deals in
concepts like laps and calories, which are rather alien to GPSBabel 
and most of the formats we support.  As such, while we can describe
the tracks pretty accurately, things like calories and heart zone
tracking are not supported. Some of the auxiliary data, such as
heart rate (not zone), cadence, and bicycling power are supported.
</p><p>
One of the most useful things you can do with this format is to send 
.tcx files found on the web or elsewhere to any supported GPS 
unit. You will probably want to include the transform (rte=trk) 
and simplify filters in this process. For example,
</p><p><strong class="userinput"><code>
gpsbabel -i gtrnctr -f somefile.tcx -x simplify,count=50 
-x transform,rte=trk -r -o garmin -F usb:
</code></strong></p><p>
where you select the count not to exceed the number of available
waypoints for routing on your device.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gtrnctr_o_course"></a><code class="option">course</code> option</h3></div></div></div><p>
      Write course rather than history, default yes.
    </p><p>
  This flag defaults to true; it must be turned off (course=0) if you want history instead of courses.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gtrnctr_o_sport"></a><code class="option">sport</code> option</h3></div></div></div><p>
      Sport: Biking (deflt), Running, MultiSport, Other.
    </p><p>
  Specify which sport is associated with this activity.  Valid values are Biking, Running, MultiSport, and Other.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_gtrnctr1"></a>Garmin Training Center (.xml) (gtrnctr)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gtrnctr1_o_course"></a><code class="option">course</code> option</h3></div></div></div><p>
      Write course rather than history, default yes.
    </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gtrnctr1_o_sport"></a><code class="option">sport</code> option</h3></div></div></div><p>
      Sport: Biking (deflt), Running, MultiSport, Other.
    </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_geo"></a>Geocaching.com .loc (geo)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_geo_o_deficon" title="deficon option">deficon</a>, <a class="link" href="#fmt_geo_o_nuke_placer" title="nuke_placer option">nuke_placer</a> .</p><p>
This format supports the <a class="ulink" href="http://www.geocaching.com" target="_top">Geocaching.com</a>/<a class="ulink" href="http://www.easygps.com" target="_top">EasyGPS</a> ".loc" format.  This format
was created specifically for Geocaching.com and is not the same as the 
standard EasyGPS .loc format.  See the <a class="link" href="#fmt_easygps" title="EasyGPS binary format (easygps)">EasyGPS</a> 
or <a class="link" href="#fmt_gpx" title="GPX XML (gpx)">GPX</a> formats for more general EasyGPS support.
</p><p>
This is a simple XML-based format containing only very basic information 
about geocaches.  If you can use the <a class="link" href="#fmt_gpx" title="GPX XML (gpx)">GPX</a> 
format from Pocket Queries instead, you should consider doing so as it is a much richer format.
</p><p>
We have a separate page describing how to <a class="ulink" href="/tips/browser.html" target="_top">send from Geocaching.com pages to GPS</a> 
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_geo_o_deficon"></a><code class="option">deficon</code> option</h3></div></div></div><p>
      Default icon name.
    </p><p>
This option specifies the icon or waypoint type to write for each waypoint on 
output.
</p><p>
If this option is specified, its value will be used for all waypoints, not 
just those that do not already have descriptions.  That is, this option 
overrides any icon description that might be in the input file.
</p><p>
There is no list of valid values for this option.
</p><p>
This option has no effect on input.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_geo_o_nuke_placer"></a><code class="option">nuke_placer</code> option</h3></div></div></div><p>
      Omit Placer name.
    </p><p>
If this option is specified, GPSBabel will not read geocache placer information
from a .loc file on input.  That is, it will ignore any placer names in the
input file.
</p><p>
This option has no effect on output.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_ggv_ovl"></a>Geogrid-Viewer ascii overlay file (.ovl) (ggv_ovl)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>
   Overlay files used by <span class="productname">Geogrid</span>™-Viewer has to be in ASCII format. 
   Make sure you save the files correctly.
</p><p>
   Lines or polygons within the <span class="productname">Geogrid</span>™-Viewer (type 3 and 4) will be
   converted to tracks, except they are grouped. In this case GPSBabel creates routes.
</p><p>
   During the creation of an overlay file, a circle will be added to each 
   position of a waypoint or a route.
</p><p>
  Sample layout of the ASCII overlay file
  </p><pre class="programlisting">
    [Symbol &lt;number # &gt;]
    Typ=&lt;1=picture,2=Text, 3=line, 4=area, 5=rectangle, 6=circle, 7=triangle&gt;
    Group=&lt;1=no group, number &gt; 1=group number&gt;
    Col=&lt;number of the line color&gt;
    Zoom=&lt;1=no zoom, 2=zoom&gt;
    Size=&lt;size can be between 101 and 118&gt;
    Art=&lt;style&gt;
    Punkte=&lt;number of XKoord&gt;
    XKoord0=&lt;decimal X coordinate (Longitude) of the waypoint&gt;
    YKoord0=&lt;decimal Y coordinate (Latitude) of the waypoint&gt;
    [MapLage]
    MapName=Top. Karte 1:50.000 Nieders.
    DimmFc=100
    ZoomFc=&lt;zoom level of the map&gt;
    CenterLat=&lt;map center in decimal Y coordinates&gt;
    CenterLong=&lt;map center in decimal X coordinates of &gt;
    RefOn=0
  </pre><p>
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_ggv_log"></a>Geogrid-Viewer tracklogs (.log) (ggv_log)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
   Binary track logs used by the <span class="productname">Geogrid</span>™-Viewer, a very
   popular product in Germany.
</p><p>
   GPSBabel has full support for version 1.0 of this file format. 
</p><p>
   We can also read some GPS data (including coordinates) from version 2.5. But 
   it seems, that this newer version no longer stores time stamps. This can be 
   a problem when converting to other formats or if you want to use our track filter.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_geonet"></a>GEOnet Names Server (GNS) (geonet)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
  Input support for the GEOnet Names Server (GNS) country
  file structure.  Export to this format is not possible, as this format
  has too many fields that we never get populated by any other
  format.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_dg-100"></a>GlobalSat DG-100/BT-335 Download (dg-100)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_dg-100_o_erase" title="erase option">erase</a>, <a class="link" href="#fmt_dg-100_o_erase_only" title="erase_only option">erase_only</a> .</p><p>
  Serial download protocol for the <span class="productname">GlobalSat DG-100</span>™, 
  <span class="productname"> GlobalSat BT-335</span>™, 
  and <span class="productname">GlboalSat BT-338X</span>™GPS data loggers.
</p><p>
  While the DG-100 has a button to record waypoints, they seem to be indistinguishable 
  from trackpoints. Therefore, all points will be presented as trackpoints, 
  regardless of whether they were recorded automatically or manually.
</p><p>
  <a class="ulink" href="http://www.globalsat.com.tw/eng/product_detail_00000090.htm" target="_top">GlobalSat DG-100</a>
</p><div class="example"><a id="dg-100-on-linux"></a><div class="example-title">Example 3.12. Command showing DG-100 download and erase on Linux</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -t -i dg-100,erase -o gpx /dev/ttyUSB0 outputfile.gpx</code></strong></p></div></div><br class="example-break" /><div class="example"><a id="dg-100-on-linux-erase_only"></a><div class="example-title">Example 3.13. Command showing DG-100 erase_only option on Linux</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -t -i dg-100,erase_only /dev/ttyUSB0</code></strong></p></div></div><br class="example-break" /><p>
  The DG-100 provides a physical USB interface to the host computer, but
  internally it uses a Prolific PL-2303 chip to do this.  So you must have
  drivers installed on your computer to recognize the PL-2303 and provide
  that data as a serial port to software like GPSBabel.   Such software
  comes with the unit for Windows.  Prolific provides software for Mac OS/X,
  but unfortunately their driver has a defect which makes it unstable with
  GPSBabel.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_dg-100_o_erase"></a><code class="option">erase</code> option</h3></div></div></div><p>
      Erase device data after download.
    </p><p>This option erases the track log from the device after download.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_dg-100_o_erase_only"></a><code class="option">erase_only</code> option</h3></div></div></div><p>
      Only erase device data, do not download anything.
    </p><p>
  Much like the <code class="option">erase</code> this optio erases the data in the GPS.
  It does not transfer data before doing so, making it much faster.  This may
  be handy in a work flow where you want to transfer the data from the GPS,
  check it on a map, and then remove it from the unit.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_dg-200"></a>GlobalSat DG-200 Download (dg-200)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_dg-200_o_erase" title="erase option">erase</a>, <a class="link" href="#fmt_dg-200_o_erase_only" title="erase_only option">erase_only</a> .</p><p>Serial download protocol for the <span class="productname">GlobalSat DG-200</span>™GPS data loggers.</p><p>
<a class="ulink" href="http://www.usglobalsat.com/p-677-dg-200-gps-data-logger.aspx" target="_top">GlobalSat DG-200</a>
</p><div class="example"><a id="dg-200-on-linux"></a><div class="example-title">Example 3.14. Command showing DG-200 download and erase on Linux</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -t -i dg-200,erase -o gpx /dev/ttyUSB0 outputfile.gpx</code></strong></p></div></div><br class="example-break" /><div class="example"><a id="dg-200-on-linux-erase_only"></a><div class="example-title">Example 3.15. Command showing DG-200 erase_only option on Linux</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -t -i dg-200,erase_only /dev/ttyUSB0</code></strong></p></div></div><br class="example-break" /><p>
  The DG-200 provides a physical USB interface to the host computer, but
  internally it uses a Prolific PL-2303 chip to do this.  So you must have
  drivers installed on your computer to recognize the PL-2303 and provide
  that data as a serial port to software like GPSBabel.   Such software
  comes with the unit for Windows.  Prolific provides software for Mac OS/X,
  but unfortunately their driver has a defect which makes it unstable with
  GPSBabel.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_dg-200_o_erase"></a><code class="option">erase</code> option</h3></div></div></div><p>
      Erase device data after download.
    </p><p>This option erases the track log from the device after download.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_dg-200_o_erase_only"></a><code class="option">erase_only</code> option</h3></div></div></div><p>
      Only erase device data, do not download anything.
    </p><p>
  Much like the <code class="option">erase</code> this optio erases the data in the GPS.
  It does not transfer data before doing so, making it much faster.  This may
  be handy in a work flow where you want to transfer the data from the GPS,
  check it on a map, and then remove it from the unit.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_googledir"></a>Google Directions XML (googledir)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p> This format is designed to read the XML emitted when you
use the <a class="ulink" href="https://developers.google.com/maps/documentation/directions/" target="_top">
	Google Directions API</a>.
</p><p>
If you use a Unix-compatible
operating system, this shell script might be useful:
</p><pre class="programlisting">
#!/bin/sh 
FROM="233 S. Upper Wacker Dr, Chicago, IL" 
TO="1060 W. Addison St, Chicago, IL" 
wget -O - "http://maps.googleapis.com/maps/api/directions/xml?origin=$FROM&amp;destination=$TO&amp;sensor=false" \
2&amp;amp;&amp;gt;/dev/null &amp;gt;google_map.js
gpsbabel -i google -f google_map.js -o gpx -F google_map.gpx
</pre></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_kml"></a>Google Earth (Keyhole) Markup Language (kml)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_kml_o_deficon" title="deficon option">deficon</a>, <a class="link" href="#fmt_kml_o_lines" title="lines option">lines</a>, <a class="link" href="#fmt_kml_o_points" title="points option">points</a>, <a class="link" href="#fmt_kml_o_line_width" title="line_width option">line_width</a>, <a class="link" href="#fmt_kml_o_line_color" title="line_color option">line_color</a>, <a class="link" href="#fmt_kml_o_floating" title="floating option">floating</a>, <a class="link" href="#fmt_kml_o_extrude" title="extrude option">extrude</a>, <a class="link" href="#fmt_kml_o_track" title="track option">track</a>, <a class="link" href="#fmt_kml_o_trackdata" title="trackdata option">trackdata</a>, <a class="link" href="#fmt_kml_o_trackdirection" title="trackdirection option">trackdirection</a>, <a class="link" href="#fmt_kml_o_units" title="units option">units</a>, <a class="link" href="#fmt_kml_o_labels" title="labels option">labels</a>, <a class="link" href="#fmt_kml_o_max_position_points" title="max_position_points option">max_position_points</a>, <a class="link" href="#fmt_kml_o_rotate_colors" title="rotate_colors option">rotate_colors</a> .</p><p> 
KML, the Keyhole Markup Language format, was used by Keyhole and is used by 
<a class="ulink" href="http://earth.google.com" target="_top">Google Earth</a>.  
</p><p>There are concepts in KML that GPSBabel can't support very well on 
read because they don't map well into other programs.  For example, KML has
ideas of camera views and names and descriptions can have arbitrarily 
complicated HTML in them.   KML files may have tiered "Styles" which
can identify sizing info and URLs of associated icons.   Reading such
files with GPSBabel - even if your goal it to write it back out as KML - can often
have surprising results.  Simple files with waypoints and paths (which
GPSBabel represents internally as tracks) work fine.
</p><p>
Google Earth also uses GPSBabel internally for receiver communications
and several file format imports and exports.
</p><p>
In general, GPSBabel's KML writer is relatively strong.  GPSBabel handles simple KML on read fairly well, but if you're dealing with handcrafted KML that uses extensive features that have no analog in other formats like nested folders, ringgeometry, camera angles, and such, don't expect GPSBabel to do well with them on read.
</p><p>
  Google Earth 4.0 and later have a feature that can surprise users of this 
  format.   Earth's "time slider" feature controls what timestamped data
  gets displayed.  If you're using data that has timestampes (e.g. GPX 
  points that contain time or almost any track data) this will be important
  to you.  The time slider defaults to the far left position and fully closed.
  This means that only the first data point will be displayed.  You can
  tweak Earth's settings to "view-&gt;show time-&gt;never" or
  you can widen the time slider to show the range of data of interest.
</p><p>
  See <a class="ulink" href="http://earth.google.com/userguide/v4/ug_gps.html#timeline" target="_top">Google Earth's documentation on timelines</a> for more info.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_kml_o_deficon"></a><code class="option">deficon</code> option</h3></div></div></div><p>
      Default icon name.
    </p><p>
This option specifies the default name for waypoint icons
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_kml_o_lines"></a><code class="option">lines</code> option</h3></div></div></div><p>
      Export linestrings for tracks and routes.
    </p><p>
When this option is nonzero, GPSBabel draws lines between points in
tracks and routes.  The default value for this option is 1, which causes
lines to be drawn by default.  To disable line-drawing, specify 
<code class="option">lines=0</code>.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_kml_o_points"></a><code class="option">points</code> option</h3></div></div></div><p>
      Export placemarks for tracks and routes.
    </p><p>
When this option is nonzero, GPSBabel draws placemarks for tracks and routes.
The default value for this option is 1, which causes placemarks to be drawn.
To disable drawing of placemarks, specify <code class="option">points=0</code>.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_kml_o_line_width"></a><code class="option">line_width</code> option</h3></div></div></div><p>
      Width of lines, in pixels.
    </p><p>
This option specifies the width of the drawn lines in pixels.  The default
value is six pixels.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_kml_o_line_color"></a><code class="option">line_color</code> option</h3></div></div></div><p>
      Line color, specified in hex AABBGGRR.
    </p><p>
This option specifies the line color as a hexadecimal number in 
AABBGGRR format, where A is alpha, B is blue, G is green, and R is red.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_kml_o_floating"></a><code class="option">floating</code> option</h3></div></div></div><p>
      Altitudes are absolute and not clamped to ground.
    </p><p>
When this option is nonzero, altitudes are allowed to float above or below
the ground surface.  By default, this option is zero so that altitudes are
clamped to the ground.  Specify <code class="option">floating=1</code> to allow them to
float.
</p><p>
This option is more useful to pilots than to hikers.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_kml_o_extrude"></a><code class="option">extrude</code> option</h3></div></div></div><p>
      Draw extrusion line from trackpoint to ground.
    </p><p>
This option is a boolean flag to specify whether Google Earth should
draw lines from trackpoints to the ground.   It defaults to '0', which
means no extrusion lines are drawn.   The option of '1' is, of course,
most useful for points that aren't actually on the ground such as those
be captured from planes.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_kml_o_track"></a><code class="option">track</code> option</h3></div></div></div><p>
      Write KML track (default = 0).
    </p><p>
  This is a boolean flag, defaulting to '0', that controls whether GPSBabel
  writes the &lt;Track&gt; tag that Google introduced in Earth 5.2 for tracks. You
    may need to turn this off if you have a KML reader that's confused by new
    tags or if size is critical.
</p><p>
  Routes and tracks without sufficient time data are always drawn as
  Linestrings and never Tracsks.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_kml_o_trackdata"></a><code class="option">trackdata</code> option</h3></div></div></div><p>
      Include extended data for trackpoints (default = 1).
    </p><p>
This is a boolean flag that controls
whether GPSBabel writes extensive data for each trackpoint generated.
By default computed speed, timestamps, and so on are written with the default
of '1' for this option.   If you are writing large tracks and do not value
this information, you can reduce the size of the generated file substantially
by turning this flag off by setting it to '0'.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_kml_o_trackdirection"></a><code class="option">trackdirection</code> option</h3></div></div></div><p>
      Indicate direction of travel in track icons (default = 0).
    </p><p>
  If set, this options creates directional icons for trackpoints.   Arrows 
  will show the direction of travel on drawn tracks and routes.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_kml_o_units"></a><code class="option">units</code> option</h3></div></div></div><p>
      Units used when writing comments ('s'tatute, 'm'etric,' 'n'autical, 'a'viation).
    </p><p>
Units is a simple option.  Specify 's' for "statute" (miles, feet, and 
other things that don't sensibly convert to each other, but are craved
by Americans), 'm' for "metric", 'n' for "nautical" or 'a' for "aviation". Default is 's'.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_kml_o_labels"></a><code class="option">labels</code> option</h3></div></div></div><p>
      Display labels on track and routepoints  (default = 1).
    </p><p>
When this option is zero, no labels are added for track and route points.
This option defaults to one, so labels are added by default.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_kml_o_max_position_points"></a><code class="option">max_position_points</code> option</h3></div></div></div><p>
      Retain at most this number of position points  (0 = unlimited).
    </p><p>
	This option allows you to specify the number of points kept
	in the 'snail trail' generated in the realtime tracking mode.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_kml_o_rotate_colors"></a><code class="option">rotate_colors</code> option</h3></div></div></div><p>
      Rotate colors for tracks and routes (default automatic).
    </p><p>
With this option GPSBabel uses different colors for each track or route.
If this option is used without a value then the colors are automatically selected such
that the spectrum will be rotated through once for all the tracks and once for all the routes.
If this option is used with a positive value then the value is interpreted as the number of degrees
in the color circle between adjacent tracks or routes. 
This option takes precedence over line_color.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_google"></a>Google Maps XML (google)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p> This format is designed to read the XML emitted when you
tack "&amp;output=js" onto the end of a <a class="ulink" href="http://maps.google.com" target="_top">Google Maps</a> route URL (use
the "link to this page" option to get a usable URL.)  This allows you
to plan a route using Google Maps, then download it and use it in your
own mapping program or GPS receiver.   To get a file suitable for use
with GPSBabel, plan your route as usual with Google Maps.  Once you've 
got it the way you want it, click the "Link to this page" link in the
upper right-hand corner of the Google Maps page.  Then, edit the URL 
that appears in your address bar by adding "&amp;output=js" (without
the quotes) onto the end.  Hit enter, and the resulting page will be
mostly empty.  It doesn't look like much, but it contains exactly what 
GPSBabel needs.  Save it to disk using whatever menu option your web 
browser provides.
</p><p>
Note that if you are using Microsoft Internet Explorer, you should make sure
to save the web page as "Web Page, HTML Only".  If you save it as "Web Page,
Complete", it will be reformatted into a non-XHTML format that GPSBabel 
cannot read.
</p><p>
If you use a Unix-compatible
operating system, this shell script might be useful:
</p><pre class="programlisting">
#!/bin/sh 
FROM="233 S. Upper Wacker Dr, Chicago, IL" 
TO="1060 W. Addison St, Chicago, IL" 
wget -O - "http://maps.google.com/maps?q=$FROM to $TO&amp;output=js" \
2&amp;&gt;/dev/null &gt;google_map.js
gpsbabel -i google -f google_map.js -o gpx -F google_map.gpx
</pre></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_gnav_trl"></a>Google Navigator Tracklines (.trl) (gnav_trl)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
   Binary (little endian) tracklogs containing coordinates, timestamps and altitude values.
</p><p>
   <a class="ulink" href="http://www.pdafun.net/" target="_top">Google Navigator</a> is an application for PDAs
   running under Windows Mobile 5.0 or 6.0.
</p><p>
  </p><div class="table"><a id="structure"></a><div class="table-title">Table 3.4. Track point structure (16 bytes)</div><div class="table-contents"><table summary="Track point structure (16 bytes)" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Position</th><th>Data type</th><th>Field info</th></tr></thead><tbody><tr><td>0</td><td>32-bit signed int</td><td>Unix timestamp</td></tr><tr><td>4</td><td>32-bit float</td><td>Latitude</td></tr><tr><td>8</td><td>32-bit float</td><td>Longitude</td></tr><tr><td>12</td><td>32-bit float</td><td>Altitude (!rotated left by eight bits!)</td></tr></tbody></table></div></div><p><br class="table-break" />
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_gopal"></a>GoPal GPS track log (.trk) (gopal)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_gopal_o_date" title="date option">date</a>, <a class="link" href="#fmt_gopal_o_maxspeed" title="maxspeed option">maxspeed</a>, <a class="link" href="#fmt_gopal_o_minspeed" title="minspeed option">minspeed</a>, <a class="link" href="#fmt_gopal_o_clean" title="clean option">clean</a> .</p><p>
  The gopal format is a track format written by the
 <a class="ulink" href="http://www.mediongopal.de/" target="_top">GoPal Navigation</a> program. 
</p><p>
  The format of the file itself is quite simple:</p><p>
      </p><pre class="programlisting">
        Fileformat GoPal
        TICK;   TIME UTC; LONG;    LAT;       HEIGHT; SPEED km/h;  FIX; HDOP;     SAT
        3801444, 080558, 2.944362, 43.262117, 295.28, 0.12964, 2, 2.900000, 3
      </pre><p>

Filenames are automatically created by the device as follows:
      </p><pre class="programlisting">
        trackYYYYMMDD_HHMMSS.trk  </pre><p>
      and/or, depending on software version and settings:
      </p><pre class="programlisting">
		A_YYYYMMDD_HHMMSS.trk
              </pre><p>
	with HHMMSS local time (not UTC!)
      </p><p> 
The file format lacks the correct date value for each trackpoint, so it has to be computed starting from the
date given in the filename. To handle files without a parsable date in the
name, the command line option 'date' is provided.
</p><p>
Conversions from gopal into any other format are a bit lossy concerning the first field of each line wich looks like an useless time tick value
and is simply discarded while reading. If written, there will be a time_t value from the current (computed) timestamp.
</p><p>
Somewhere around Gopal 4.8 or 5.0, Electrobit added three more fields to the end of this format.  They are, in order, date (which eliminates most of the silliness above), an unknown field, and a bearing.   GPSBabel now reads the date and ignores the other two.  We don't yet write these three fields for compatibility with earlier versions.
</p><p>

Filtering out invalid data points is handled by the options 'clean', 'minspeed' and 'maxspeed'.
For each datapoint the speed needed to come the from the last valid point is
calculated and compared with the limits.
Thus one cat easily discard unreliable points.

         </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gopal_o_date"></a><code class="option">date</code> option</h3></div></div></div><p>
      Complete date-free tracks with given date (YYYYMMDD)..
    </p><p>
  This option is useful if you have tracks from Gopal that have been renamed.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gopal_o_maxspeed"></a><code class="option">maxspeed</code> option</h3></div></div></div><p>
      The maximum speed (km/h) traveling from waypoint to waypoint..
    </p><p>
  This is useful for removing wildly erroneous data from your recorded track.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gopal_o_minspeed"></a><code class="option">minspeed</code> option</h3></div></div></div><p>
      The minimum speed (km/h) traveling from waypoint to waypoint. Set &amp;gt;0 to remove duplicate waypoints.
    </p><p>
  If this is greater than zero, duplicate waypoints will be removed.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gopal_o_clean"></a><code class="option">clean</code> option</h3></div></div></div><p>
      Cleanup common errors in trackdata.
    </p><p>
  Specifying the <code class="option">clean</code> flag makes the Gopal reader pass
  over the data and discard data that is probably incorrect such as the
  longitude and latitude of "0".
</p><p>
  If you happen to be a boater or pilot off the south short of Ghana,
  you may disagree that coordinates of "0, 0" are bad.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_land_air_sea"></a>GPS Tracking Key Pro text (land_air_sea)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
Read-only support for the text format exported by Land Air Sea's (Windows only) Past-Track software. This may also work for importing text formatted files from Victoria GPS Tracking, GPS Tracking Key and Land Air Sea's other devices.
</p><p>
Implementation
</p><p>
The text format of the GPS Tracking Key Pro contains one route coordinate per line and is of the format:
</p><p>
01-24-2011,09:12:30,N 48°51'57.9738",W 123°11'48.1354",20.5mph,83.8°,357ft
</p><p>
GPS Babel style file correctly imports all data except for bearing (which is un-needed). Since there is no way to create waypoints or routes on the device itself, the text file is read in as one large track.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_gtm"></a>GPS TrackMaker (gtm)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>Input and output support for waypoints, tracks and routes in
             the <a class="ulink" href="http://www.gpstm.com" target="_top">GPS TrackMaker </a>
              binary format.</p><p>Code implemented by Gustavo Niemeyer.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_arc"></a>GPSBabel arc filter file (arc)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
This format is used by GPSBabel itself as the input to the 
<a class="link" href="#filter_arc" title="Include Only Points Within Distance of Arc (arc)">arc</a> and 
<a class="link" href="#filter_polygon" title="Include Only Points Inside Polygon (polygon)">polygon</a> filters.  See those filters
for more information.
</p><p>
The arc format reads two numeric fields, a latitude and a longitude, 
in any format recognized as <a class="link" href="#style_def_lathuman" title="LAT_HUMAN_READABLE">human 
readable</a> and writes as simple degrees decimal.  It really is
intended for GPSBabel's own internal use more than general use, though
it turns out to be a convenient way of expressing simple polylines and 
polygons.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_gpsdrive"></a>GpsDrive Format (gpsdrive)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>GpsDrive way.txt file format. A space separated format
file. Tested against GpsDrive v 1.30 found at <a class="ulink" href="http://www.gpsdrive.de" target="_top">gpsdrive.de</a>.
Contributed by Alan Curry.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_gpsdrivetrack"></a>GpsDrive Format for Tracks (gpsdrivetrack)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>Format used by GpsDrive to save tracks. Like GPSDRIVE a
space separated format file. See above for a link to GpsDrive.
Contributed by Tobias Minich.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_gpsman"></a>GPSman (gpsman)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p> <a class="ulink" href="http://www.ncc.up.pt/gpsman/" target="_top">GPS Manager</a> 
can read and write formats GPSBabel doesn't understand.  The format defaults
(WGS84, DDD) work reliably.  Tracks, routes, and non-default format options
are not supported.
	</p><p>This format is documented at the GPS Manager 
	<a class="ulink" href="http://www.ncc.up.pt/gpsman/gpsmanhtml/manual/html/GPSMandoc_30.html" target="_top">doc site</a>.
	</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_gpsutil"></a>gpsutil (gpsutil)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>The format we call <a class="ulink" href="http://www.cs.uakron.edu/~hennings/gpsutil" target="_top">gpsutil</a> is a simple file format used by a program that runs
on POSIX- compliant OSes like UNIX and Linux.  Reads and writes of
this format are very reliable.  (<a class="ulink" href="/people/robertlipe.html" target="_top">The lead
developer of GPSBabel</a> also contributed to this that 'gpsutil' 
the early days.)</p><p>
	Note that 'gpsutil' is a different format - and program - than the one called <a class="ulink" href="http://www.gpsu.co.uk/index.html" target="_top">GPS Utility</a>; for that one, you should probably use our  <a class="link" href="#fmt_pcx" title="Garmin PCX5 (pcx)">PCX module</a>.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_gpx"></a>GPX XML (gpx)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_gpx_o_snlen" title="snlen option">snlen</a>, <a class="link" href="#fmt_gpx_o_suppresswhite" title="suppresswhite option">suppresswhite</a>, <a class="link" href="#fmt_gpx_o_logpoint" title="logpoint option">logpoint</a>, <a class="link" href="#fmt_gpx_o_urlbase" title="urlbase option">urlbase</a>, <a class="link" href="#fmt_gpx_o_gpxver" title="gpxver option">gpxver</a>, <a class="link" href="#fmt_gpx_o_humminbirdextensions" title="humminbirdextensions option">humminbirdextensions</a>, <a class="link" href="#fmt_gpx_o_garminextensions" title="garminextensions option">garminextensions</a> .</p><p>This is one of the most capable and expressive formats of all the file
formats supported by GPSBabel.  It is described at <a class="ulink" href="http://www.topografix.com/gpx.asp" target="_top">topografix.com</a> and is
supported by EasyGPS, ExpertGPS, and many other programs described at
<a class="ulink" href="http://www.topografix.com/gpx_resources.asp" target="_top">topografix.com</a>
</p><p>
GPSBabel's reader of this module attempts to preserve tags it doesn't
really understand.   It also tries to glean interesting data from
</p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="ulink" href="http://www.geocaching.com" target="_top">pocket queries from Geocaching.com,</a></td></tr><tr><td>Garmin's "gpxx" GPX extensions,</td></tr><tr><td>Humminbird's "h" GPX extensions.</td></tr></table><p>
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gpx_o_snlen"></a><code class="option">snlen</code> option</h3></div></div></div><p>
      Length of generated shortnames.
    </p><p>
  When used with the <code class="option"> -s </code> to control shortnames, the snlen suboption to GPX controls how long the generated smartname will be.  This can be useful for cases like writing GPX files to a GPS that has a fixed waypoint name length.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gpx_o_suppresswhite"></a><code class="option">suppresswhite</code> option</h3></div></div></div><p>
      No whitespace in generated shortnames.
    </p><p>
When used with the <code class="option">-s</code> to generate smart shortnames, this suboption controls whether whitespace is allowed in the generated shortnames.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gpx_o_logpoint"></a><code class="option">logpoint</code> option</h3></div></div></div><p>
      Create waypoints from geocache log entries.
    </p><p>
	When reading <a class="ulink" href="http://www.geocaching.com" target="_top"> Groundspeak Pocket Queries </a>, the <code class="option">logpoint</code> option creates additional waypoints from the log entries.
</p><p>
 	A typical use for this is to get coordinates read from "corrected coordinates" logs.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gpx_o_urlbase"></a><code class="option">urlbase</code> option</h3></div></div></div><p>
      Base URL for link tag in output.
    </p><p>
  This is a fairly esoteric option.  If the GPX file you are reading has only base pathnames (e.g "foo.html") the value you specify to this argument will be prepended to that.  For example, "-o gpx,urlbase=c:\My Documents\Whatever" would result in the link to that waypoint being written to refer to <code class="filename">c:\My Document\WHatever\foo.html</code>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gpx_o_gpxver"></a><code class="option">gpxver</code> option</h3></div></div></div><p>
      Target GPX version for output.
    </p><p>
This option specifies the version of the GPX specification to use for 
output.  The default version is 1.0.  The only other valid value for this
option is 1.1.
</p><p>
Notice that this is not a full scale XML schema conversion.  In particular,
if you have a GPX 1.0 file that has extended namespaces in it (such as a 
pocket query from Geocaching.com) just writing it with this option will
result in a horribly mangled GPX file as we can't convert the schema data.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gpx_o_humminbirdextensions"></a><code class="option">humminbirdextensions</code> option</h3></div></div></div><p>
      Add info (depth) as Humminbird extension.
    </p><p>
Implies <code class="option">gpxver=1.1</code>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_gpx_o_garminextensions"></a><code class="option">garminextensions</code> option</h3></div></div></div><p>
      Add info (depth) as Garmin extension.
    </p><p>
Implies <code class="option">gpxver=1.1</code>
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_hiketech"></a>HikeTech (hiketech)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
  This is the .gps format used by the Mac OS X applications
  written by HikeTech. These include TopoDraw, Link2GPS, and GPSWrite.
  More information about these products can be found at 
  <a class="ulink" href="http://www.hiketech.com" target="_top">hiketech.com</a>
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_holux"></a>Holux (gm-100) .wpo Format (holux)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p> The Holux gm-100 (e-fox) gps receiver uses standard
compact flash cards.  File formats were provided by Holux-Taiwan
<a class="ulink" href="http://www.holux.com.tw" target="_top">holux.com</a> to the author.
The code was tested against version 2.27E1; other versions and
receivers may work but have not been explicitly tested.  Anyone with
information on other Holux receivers is encouraged to contact
jochen@bauerbahn.net.
</p><p> When copying the .wpo file to a flash card, the file must
be named <code class="filename">tempwprt.wpo</code> as the
receiver will ignore all other files.
</p><p> Comparing the waypoints of a .wpo files against other
formats like .gpx you may notice a small difference in the latitude
and longitude values.  The reason is the low resolution of the
coordinates in the wpo file format.  In a .wpo file the resolution is
1/10"; in gpx for example it is 1/100".  A a practical matter, this
loss is only about 1.7 meters (5 feet).
</p><p> The generated waypoint failes can also be used by MapShow
version 1.14.  This program is free of charge from the Holux web site.
</p><p> This format was contributed by Jochen Becker.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_m241-bin"></a>Holux M-241 (MTK based) Binary File Format (m241-bin)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_m241-bin_o_csv" title="csv option">csv</a> .</p><p>
	The Holux m241 is a small datalogger using the MTK chipset, with 
	a couple small differences in the binary format. In its default 
	configuration, it can store ~100000 trackpoints with very limited
	 data; to configure extended logging you can use the BT747 open 
	source software 
         <a class="ulink" href="http://bt747.wiki.sourceforge.net" target="_top">bt747</a>
	 Waypoint storage is possible only if "recording reason" (RCR) is enabled in the settings.
</p><p>
	Holux GPSport 245 is a datalogger with display suitable for cycling, walking and running. 
        It can store ~200k trackpoints with limited data. The m241 and m241-bin format is 
        able to automatically detect GPSport 245 data and handle the differences from Holux M-241 devices.
        Note: GP245 does not log any quality of the position.
</p><p>
	Use the m241 format to connect with the unit serially and m241-bin to read files saved by the device.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_m241-bin_o_csv"></a><code class="option">csv</code> option</h3></div></div></div><p>
      MTK compatible CSV output file.
    </p><p>
  Specifies a filename into which  MTK-compatible CSV output will be written.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_m241"></a>Holux M-241 (MTK based) download (m241)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_m241_o_erase" title="erase option">erase</a>, <a class="link" href="#fmt_m241_o_erase_only" title="erase_only option">erase_only</a>, <a class="link" href="#fmt_m241_o_log_enable" title="log_enable option">log_enable</a>, <a class="link" href="#fmt_m241_o_csv" title="csv option">csv</a> .</p><p>
	The Holux m241 is a small datalogger using the MTK chipset, with 
	a couple small differences in the binary format. In its default 
	configuration, it can store ~100000 trackpoints with very limited
	 data; to configure extended logging you can use the BT747 open 
	source software 
         <a class="ulink" href="http://bt747.wiki.sourceforge.net" target="_top">bt747</a>
	 Waypoint storage is possible only if "recording reason" (RCR) is enabled in the settings.
</p><p>
	Holux GPSport 245 is a datalogger with display suitable for cycling, walking and running. 
        It can store ~200k trackpoints with limited data. The m241 and m241-bin format is 
        able to automatically detect GPSport 245 data and handle the differences from Holux 241 devices.
        Note: GP245 does not log any quality of the position.
</p><p>
	Use the m241 format to connect with the unit serially and m241-bin to read files saved by the device.
</p><p>
  This module is also reported to handle the Holux M1000c.
</p><p>
  Most of the loggers cannot receive bluetooth commands, they can only send
  data. Since GPSBabel needs to send commands to the GPS device it won't
  work. Download the data using the USB cable instead.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_m241_o_erase"></a><code class="option">erase</code> option</h3></div></div></div><p>
      Erase device data after download.
    </p><p>This option erases the track log from the device after download.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_m241_o_erase_only"></a><code class="option">erase_only</code> option</h3></div></div></div><p>
      Only erase device data, do not download anything.
    </p><p>This option will only erase the logger data. No data is downloaded.</p><p>This option is typically used as a second step after the data has been downloaded and verified.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_m241_o_log_enable"></a><code class="option">log_enable</code> option</h3></div></div></div><p>
      Enable logging after download.
    </p><p>This option will enable the logger after download.</p><p>By default the logger is re-enabled when download is finished if previously were enabled.
But if the download is aborted or failed the log functionality won't be enabled again.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_m241_o_csv"></a><code class="option">csv</code> option</h3></div></div></div><p>
      MTK compatible CSV output file.
    </p><p>
  Note that this option is a bit of an oddity in the GPSBabel arsenal.  This
  should probably be a "real" output type of its own instead of being bolted
  onto an input type.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_vpl"></a>Honda/Acura Navigation System VP Log File Format (vpl)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>
	This is the log format output by factory-installed Honda/Acura (Alpine) Navigation Systems 
	in (at least) 2006 models and newer.  (Though I've seen indirect data that says that Acura 
	nav systems at least as far back as 2004 use it too)
</p><p>
	This format is definitely known to work with the following model cars specifically:
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>
	2006 Honda Civic Hybrid
</td></tr></table><p>
	Logging may be enabled by simultaneously holding down the MAP/GUIDE, MENU, and CANCEL
	buttons for 3-5 seconds, then selecting "Functional Setup", "Log Data".  A PCMCIA card
	must be inserted into the system (behind the Nav LCD) for logging to work.  (The system
	can read MP3/WMA files on this card and will also write logs to it.  Generally, a
	PCMCIA to CF or PCMCIA to SD adapter is used with a corresponding CF/SD card)  With
	logging successfully set up, the system will create a directory named "VPlog" off the
	root of the card.  Inside this directory, files will be created with names corresponding
	to the date and time of engine start, in GMT.  (YYMMDD_HHMM.vpl)
</p><p>
	The VPL format contains quite a bit of data, much of which remains undecoded.  This format
	currently reads only lat/lon, altitude, speed, heading, date/time, visible sats, HDOP and
	VDOP.
</p><p>
	Generally, the layout of the format seems similar to NMEA, with discrete sentences
	containing different fields of data, followed by a 1-byte XOR'd checksum.  Some sentences
	are generated only once per engine start, others every few seconds, many every second,
	and a few on the order of five and in one case, up to twenty five times per second.  All data in
	the file is written in ASCII; most of it simply as hexadecimal characters.  Most
	fields are fixed width, though a few can be variable.  (Those that are variable
	have a field count as the first field after their sentence identifier)  Currently,
	only the '75'-sentence is processed (and only about 70% of it), though this provides all
	the data necessary for position information.

	Some fields in other sentences have been decoded, but they are not currently processed.
	Information on the data in these fields can be found in vpl.c.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_html"></a>HTML Output (html)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          write waypoints
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_html_o_stylesheet" title="stylesheet option">stylesheet</a>, <a class="link" href="#fmt_html_o_encrypt" title="encrypt option">encrypt</a>, <a class="link" href="#fmt_html_o_logs" title="logs option">logs</a>, <a class="link" href="#fmt_html_o_degformat" title="degformat option">degformat</a>, <a class="link" href="#fmt_html_o_altunits" title="altunits option">altunits</a> .</p><p> 
  GPSBabel's HTML output generates a single HTML file of all of the
  waypoints in the input file.  It supports a number of Groundspeak GPX
  extensions and filters out potentially harmful HTML from the
  input file while maintaining almost all of the source HTML formatting.   
  This makes this format well suited for generating HTML to hand to programs
  like Plucker for putting in a PDA and especially so for "paperless caching"
  for Geocachers with pocket queries.
</p><p>
  This format is similar to the <a class="link" href="#fmt_text" title="Textual Output (text)">text</a> format.
</p><p>
  The following command line reads a GPX file with
  Groundspeak extensions and writes an HTML file with encrypted hints
  that is rendered using a custom stylesheet:
</p><p>
  <strong class="userinput"><code>gpsbabel -i gpx -f 12345.gpx -o html,stylesheet=green.css,encrypt -F 12345.html</code></strong>
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_html_o_stylesheet"></a><code class="option">stylesheet</code> option</h3></div></div></div><p>
      Path to HTML style sheet.
    </p><p>
Use this option to specify a CSS style sheet to be used with the
resulting HTML file.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_html_o_encrypt"></a><code class="option">encrypt</code> option</h3></div></div></div><p>
      Encrypt hints using ROT13.
    </p><p>
Use this option to encrypt hints from Groundspeak GPX files.  
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_html_o_logs"></a><code class="option">logs</code> option</h3></div></div></div><p>
      Include groundspeak logs if present.
    </p><p>
Use this option to include Groundspeak cache logs in the created document.  
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_html_o_degformat"></a><code class="option">degformat</code> option</h3></div></div></div><p>
      Degrees output as 'ddd', 'dmm'(default) or 'dms'.
    </p><p>
When GPSBabel writes coordinates, this option is consulted to see if it
should write decimal degrees ('ddd') decimal minutes ('dmm') or degrees,
minutes, seconds ('dms').  The default is 'dmm'.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_html_o_altunits"></a><code class="option">altunits</code> option</h3></div></div></div><p>
      Units for altitude (f)eet or (m)etres.
    </p><p>
This option should be 'f' if you want the altitude expressed in feet and
'm' for meters.  The default is 'f'.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_humminbird_ht"></a>Humminbird tracks (.ht) (humminbird_ht)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read routes
        </p></li></ul></div><p>See the <a class="link" href="#fmt_humminbird" title="Humminbird waypoints and routes (.hwr) (humminbird)">Humminbird</a>
format for docs on this.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_humminbird"></a>Humminbird waypoints and routes (.hwr) (humminbird)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>
  This format supports:
  </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="ulink" href="http://www.humminbird.com" target="_top">Humminbird</a>
       waypoints and routes (<code class="filename">.hwr</code> files)</td></tr><tr><td><a class="ulink" href="http://www.humminbird.com" target="_top">Humminbird</a>
       tracks (<code class="filename">.ht</code> files)</td></tr><tr><td><a class="ulink" href="http://www.humminbird.com" target="_top">Humminbird</a>
       <code class="filename">.dat</code> files. (These accompany the
       <code class="filename">.png</code> files you get when you take snapshots.
       There are also <code class="filename">.dat</code> files generated when making
       recordings, but those are not supported here.)</td></tr></table><p>
</p><p>
  If you do "save all nav data" on the device, you'll get a 
  <code class="filename">data.hwr</code> and a <code class="filename">000.ht</code> file on the
  flash card (on a 797 in the <code class="filename">matrix</code> directory).
</p><p>
  The humminbird module can read all of these file formats, but you need to
  tell it which ones to write. By default, you get a <code class="filename">.hwr</code>
  file, to get a track (<code class="filename">.ht</code> file), use the
  "humminbird-track" format.
</p><p>
  </p><div class="informalfigure"><div class="mediaobject"><img src="humminbird.png" /></div></div><p> 
</p><p>
Note:<code class="filename">.dat</code> files are read-only, they only make sense
together with their images.
</p><p>
  Supported models:
  </p><table border="0" summary="Simple list" class="simplelist"><tr><td>797c2i SI</td></tr></table><p>
 (They should all work, but this is the only one tested so far.)
 </p><p>
  Known limits:
  </p><table border="0" summary="Simple list" class="simplelist"><tr><td>max 12 characters for waypoint names.</td></tr><tr><td>max 20 characters for route and track names.</td></tr><tr><td>max 50 points per route. Use <a class="link" href="#filter_simplify" title="Simplify routes (simplify)">simplify</a> filter (count=50 or less) if you have routes with more points!</td></tr><tr><td>max 21835 points per track.</td></tr></table><p>
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_ignrando"></a>IGN Rando track files (ignrando)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_ignrando_o_index" title="index option">index</a> .</p><p>
This format supports IGN Rando track files. IGN Rando is a program mainly 
used in France for Topo maps. The files are XML based and are "windows-1252" 
encoded. Trackpoints do not have time stamps.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_ignrando_o_index"></a><code class="option">index</code> option</h3></div></div></div><p>
      Index of track to write (if more than one in source).
    </p><p>
Because the format supports only one track, this option may be used 
on output to select a single track from a collection of 
tracks read from a more expressive format.  If you have, say, a 
<a class="link" href="#fmt_gpx" title="GPX XML (gpx)">gpx</a> file that contains two tracks, you may
use this option to write them one at a time to individual files.
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f tracks.gpx -o ignrando,index=1 -F track1.txt -o ignrando,index=2 -F track2.txt</code></strong></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_igo2008_poi"></a>iGO2008 points of interest (.upoi) (igo2008_poi)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
   igo2008_poi supports POI files from <span class="productname">Nav N Go iGO 8 Europe</span>™.
   This is a GPS Navigation Software for <span class="productname">Windows Mobile</span>™ based 
   PDA devices and Smartphones.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_igo8"></a>IGO8 .trk (igo8)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_igo8_o_tracknum" title="tracknum option">tracknum</a>, <a class="link" href="#fmt_igo8_o_title" title="title option">title</a>, <a class="link" href="#fmt_igo8_o_description" title="description option">description</a> .</p><p>
  iGo8 is the successor to the "iGo My way" software package that is reasonably
  prolific for GPS devices manufactured by Mio, Sony, LG, as well as many other
  small manufacturers.  iGo8 is notable in that it has full 3D rendering of
  terrain as well as buildings and landmarks for most large cities.  The
  software can also be bought pre-loaded on a mico-SD card for use in many PPC
  phones that are GPS enabled.
</p><p>
  The track format used by iGo8 is rather rudimentary, consisting of a list of
  coordinates and a time resolution of 1 second.  While iGo8 supports exporting
  tracks to GPX format, importing tracks is not natively supported.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_igo8_o_tracknum"></a><code class="option">tracknum</code> option</h3></div></div></div><p>
      Track identification number.
    </p><p>
  This option isn't entirely clear.  It appears to be a unique number
  for each track that is used for coloring on the main display.  So if you
  want two tracks to have different colors, set the track numbers to 
  different values.
</p><p>
  If you can provide a better description of this option, please do contact
  us.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_igo8_o_title"></a><code class="option">title</code> option</h3></div></div></div><p>
      Track title.
    </p><p>
  Use this option to set the title of the track.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_igo8_o_description"></a><code class="option">description</code> option</h3></div></div></div><p>
      Track description.
    </p><p>
Use this option to the description of the track which is text appears just below the track title in the track list on the device.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_jtr"></a>Jelbert GeoTagger data file (jtr)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
   From the <a class="ulink" href="http://www.geotagger.co.uk/files/JTR_Format.pdf" target="_top">file format description</a>:
</p><p>
   The JTR file format is used by the Jelbert GeoTagger device to record
   location information relating to where photographs have been taken.
   One record entry is created for each press of the shutter on the
   camera.
</p><p>
   The JTR file format will be updated in the future so it is important to
   check for the current version ID within the file that is present at the
   beginning of each line of data. It is currently “GEOTAG2”
</p><p>
   Each line of the JTR file currently starts with the word “GEOTAG2”
   followed by a comma and then two NMEA sentences separated by a
   comma character with a CR at the end. The $GPRMC (date, time and
   position) data is followed by the $HCHDG (magnetic compass) data.
</p><p>
   Although the $GPRMC data segment contains a compass bearing, this
   should be ignored unless the $HCHDG compass direction is null which
   can happen if the electronic compass is switched off. Use the magnetic
   compass bearing in preference to the GPS derived compass.
   The two NMEA checksums can be ignored for the time being.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_jogmap"></a>Jogmap.de XML format (jogmap)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>
 This read-only format reads the XML marker files from <a class="ulink" href="http://jogmap.de" target="_top"> Jogmap</a> as tracks.  Each "markers" entry is a new track with each "marker" entry being a trackpoint.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_kompass_tk"></a>Kompass (DAV) Track (.tk) (kompass_tk)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
  This module supports track files used by Kompass and DAV "Deutscher Alpenverein".
</p><p>
  <a class="ulink" href="http://www.kompass.at" target="_top">Kompass</a> is a publishing company from Austria.
  If you want to get more information about DAV, the German alpine association, 
  and if you are familiar with the german language, please have a look at their <a class="ulink" href="http://www.alpenverein.de" target="_top">homepage</a>.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_kompass_wp"></a>Kompass (DAV) Waypoints (.wp) (kompass_wp)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
  This module supports waypoint files used by Kompass and DAV "Deutscher Alpenverein".
</p><p>
  Some more information under <a class="link" href="#fmt_kompass_tk" title="Kompass (DAV) Track (.tk) (kompass_tk)">kompass_tk</a> format.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_psitrex"></a>KuDaTa PsiTrex text (psitrex)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This is a text format created by KuDaTa's PsiTrex program
for the Psion PDAs. The format can't be readily handled by XCSV, so
this format is handled explicitly. Waypoints, routes and tracks are
all handled, with icon names used corresponding to version 1.13 of
PsiTrex. This module was contributed to GPSBabel by Mark
Bradley.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_lowranceusr"></a>Lowrance USR (lowranceusr)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_lowranceusr_o_ignoreicons" title="ignoreicons option">ignoreicons</a>, <a class="link" href="#fmt_lowranceusr_o_writeasicons" title="writeasicons option">writeasicons</a>, <a class="link" href="#fmt_lowranceusr_o_merge" title="merge option">merge</a>, <a class="link" href="#fmt_lowranceusr_o_break" title="break option">break</a>, <a class="link" href="#fmt_lowranceusr_o_wversion" title="wversion option">wversion</a> .</p><p> 
The <a class="ulink" href="http://www.lowrance.com" target="_top">Lowrance iFinder GPS</a> series has the unique capability within the Lowrance models
to output its data to an MMC card.  The data is saved to the card as a
.USR file and can be read by your computer using a card reader.
Waypoints, icons, routes, tracks are supported.   Event marker icons contain a symbol, name, latitude and longitude
only. By default, Event marker
icons are converted to waypoints on read.  On write, you are able to create icons from waypoints.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_lowranceusr_o_ignoreicons"></a><code class="option">ignoreicons</code> option</h3></div></div></div><p>
      Ignore event marker icons on read.
    </p><p>
This option instructs GPSBabel to not convert icons to waypoints on input,
but to instead disregard them altogether 
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_lowranceusr_o_writeasicons"></a><code class="option">writeasicons</code> option</h3></div></div></div><p>
      Treat waypoints as icons on write.
    </p><p>
(USR output) This option converts the waypoint information to an event marker icon.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_lowranceusr_o_merge"></a><code class="option">merge</code> option</h3></div></div></div><p>
      (USR output) Merge into one segmented track.
    </p><p>
(USR output) This option merges all tracks into a single track with multiple segments.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_lowranceusr_o_break"></a><code class="option">break</code> option</h3></div></div></div><p>
      (USR input) Break segments into separate tracks.
    </p><p>
(USR input) Break track segments into separate tracks.
file.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_lowranceusr_o_wversion"></a><code class="option">wversion</code> option</h3></div></div></div><p>
      (USR output) Write version.
    </p><p>
  Newer (post 2006 or so) Lowrance devices added a version three of their
  .usr file format that adds depth.   Specify "3" here to use that format
  on write.  
</p><p>
<strong class="userinput"><code>
 gpsbabel ... -o lowranceusr,wversion=2 -F blah.usr
</code></strong>
is exactly the same as
<strong class="userinput"><code>
 gpsbabel ... -o lowranceusr -F blah.usr
</code></strong>
</p><p>
To create a file that contains depth but therefore isn't usable
on older Lowrance products, use this:
<strong class="userinput"><code>
 gpsbabel ... -o lowranceusr,wversion=3 -F blah.usr
</code></strong>

</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_lowranceusr4"></a>Lowrance USR version 4 (lowranceusr4)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_lowranceusr4_o_title" title="title option">title</a>, <a class="link" href="#fmt_lowranceusr4_o_serialnum" title="serialnum option">serialnum</a>, <a class="link" href="#fmt_lowranceusr4_o_description" title="description option">description</a> .</p><p> Newer <a class="ulink" href="http://www.lowrance.com" target="_top">Lowrance</a> HDS
series units use a new format, USR version 4.  Waypoints, routes,
tracks are supported.  The format is not completely understood, so
certain extended data is ignored, but basic waypoint, route, and track
details are all present.  Icons are not currently deciphered.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_lowranceusr4_o_title"></a><code class="option">title</code> option</h3></div></div></div><p>
      (output) Output title string.
    </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_lowranceusr4_o_serialnum"></a><code class="option">serialnum</code> option</h3></div></div></div><p>
      (output) Device serial number.
    </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_lowranceusr4_o_description"></a><code class="option">description</code> option</h3></div></div></div><p>
      (output) Content description.
    </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_maggeo"></a>Magellan Explorist Geocaching (maggeo)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p> 
  This format supports the on-card format used by the 
  <a class="ulink" href="http://www.magellangps.com" target="_top">Magellan</a> Explorist 400,
  Explorist 500, Explorist 600, Explorist 210, and Explorist XL 
  to describe geocaches.  Notice what while the format can
  hold an infinite number of geocaches, the unit will read and silently
  discard all but 200 geocache POIs at a time.</p><p>
  You should name any file created with this format with a ".gs" extension 
  so the firmware can read it.
</p><p>
  This format does support reading .gs files, but it's kind of a 
  pointless operation as the units can't create or edit these files.  
  Round-tripped data is lossy for all but the most trivial cases as
  many fields are shortened or discarded on write.  "Date last found" is
  discarded on read as there are no logs stored on the device in which to
  store the date last found.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_mapsend"></a>Magellan Mapsend (mapsend)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_mapsend_o_trkver" title="trkver option">trkver</a> .</p><p>
  This format supports the 
  <a class="ulink" href="http://www.magellangps.com" target="_top">Magellan</a>
  <span class="productname">MapSend</span>™ native file format.
</p><p>
  Kudos to Magellan for having the foresight to document their file formats,
  making software like this possible.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mapsend_o_trkver"></a><code class="option">trkver</code> option</h3></div></div></div><p>
      MapSend version TRK file to generate (3,4).
    </p><p>
This option sets the MapSend version to generate TRK files, 
since new MapSend versions can't open version 3 files. 
Valid values are 3 (MapSend v3.0) or 4 (MapSend v4.0 and v4.1).
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_magellanx"></a>Magellan SD files (as for eXplorist) (magellanx)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_magellanx_o_deficon" title="deficon option">deficon</a>, <a class="link" href="#fmt_magellanx_o_maxcmts" title="maxcmts option">maxcmts</a> .</p><p>
	This is the SD card format used by the <a class="ulink" href="http://www.magellangps.com" target="_top">Magellan</a> Explorist 400,
	Explorist 500, Explorist 600, and Explorist XL and internally on those devices plus the 
	Explorist 210.  Stored waypoints are identical to the <a class="link" href="#fmt_magellan" title="Magellan SD files (as for Meridian) (magellan)">Magellan SD format</a>
	used by Meridian, but the newer models allow longer waypoint names.  Routes are 
	subtly different.
</p><p> 	
	You should name any file containing waypoints created with 
	this format with a ".upt" extension so the firmware can read it.
	Similarly, routes should be named ".rte" and tracks should be
	named ".log".
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_magellanx_o_deficon"></a><code class="option">deficon</code> option</h3></div></div></div><p>
      Default icon name.
    </p><p>
  The deficon option is used to control the icon output when writing to this format.   It overrides any icon information that might be present in the source data.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_magellanx_o_maxcmts"></a><code class="option">maxcmts</code> option</h3></div></div></div><p>
      Max number of comments to write (maxcmts=200).
    </p><p>
The maxcmts option allows you to specify the number comments that will
be sent to the unit.
</p><p>
Magellan receivers allow a maximum of 200 waypoint comments.  Unfortunately,
DirectRoute uses waypoint comments to provide next turn directions for
navigation pop-ups and that comes from that pool of 200 comments.  It
is therefore sometimes convenient to limit the number of waypoint 
comments written to the receiver.   For example, a geocacher might want
to upload 400 waypoints, but only 190 with comments so that DirectRoute
could provide driving directions for the next ten turns.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_magellan"></a>Magellan SD files (as for Meridian) (magellan)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_magellan_o_deficon" title="deficon option">deficon</a>, <a class="link" href="#fmt_magellan_o_maxcmts" title="maxcmts option">maxcmts</a> .</p><p>GPSBabel supports the following <a class="ulink" href="http://www.magellangps.com" target="_top">Magellan</a> receivers:
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>310</td><td>Meridian Color</td></tr><tr><td>315</td><td>Explorist 100 (with aftermarket cable)</td></tr><tr><td>Map330</td><td>Explorist 200 (with aftermarket cable)</td></tr><tr><td>SporTrak Map Color</td><td>Explorist 300 (with aftermarket cable)</td></tr><tr><td>SporTrak Map</td><td>Explorist 210</td></tr><tr><td>SporTrak Map Pro</td><td>Explorist 300</td></tr><tr><td>SporTrak Map Topo</td><td>Explorist 400</td></tr><tr><td>Meridian (green or yellow)</td><td>Explorist 500</td></tr><tr><td>Meridian Gold</td><td>Explorist 600</td></tr><tr><td>Meridian Platinum</td><td>Explorist XL</td></tr></table><p>
</p><p>
	This format is used for both the serial protocol used on the
	devices with serial ports such as Map330 and Meridian and for
	the files stored either in either the unit's internal memory 
	(Explorist 210, Explorist 400, Explorist 500, Explorist 600, 
	Explorist XL) or on removable memory.
</p><p>
	If you specify a serial port for the file (.e.g. "COM1", "/dev/ttyS0")
	to be read or written, GPSBabel will use serial protocol.   Specifying
	a file, either on local filesystem or on a mounted flash card reader,
	will results in the file-based format being used.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_magellan_o_deficon"></a><code class="option">deficon</code> option</h3></div></div></div><p>
      Default icon name.
    </p><p>
  The deficon option is used to control the icon output when writing to this format.   It overrides any icon information that might be present in the source data.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_magellan_o_maxcmts"></a><code class="option">maxcmts</code> option</h3></div></div></div><p>
      Max number of comments to write (maxcmts=200).
    </p><p>
The maxcmts option allows you to specify the number comments that will
be sent to the unit.
</p><p>
Magellan receivers allow a maximum of 200 waypoint comments.  Unfortunately,
DirectRoute uses waypoint comments to provide next turn directions for
navigation pop-ups and that comes from that pool of 200 comments.  It
is therefore sometimes convenient to limit the number of waypoint 
comments written to the receiver.   For example, a geocacher might want
to upload 400 waypoints, but only 190 with comments so that DirectRoute
could provide driving directions for the next ten turns.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_magellan1"></a>Magellan serial protocol (magellan)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_magellan1_o_deficon" title="deficon option">deficon</a>, <a class="link" href="#fmt_magellan1_o_maxcmts" title="maxcmts option">maxcmts</a>, <a class="link" href="#fmt_magellan1_o_baud" title="baud option">baud</a>, <a class="link" href="#fmt_magellan1_o_noack" title="noack option">noack</a>, <a class="link" href="#fmt_magellan1_o_nukewpt" title="nukewpt option">nukewpt</a> .</p><p>GPSBabel supports the following <a class="ulink" href="http://www.magellangps.com" target="_top">Magellan</a> receivers:
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>310</td><td>Meridian Color</td></tr><tr><td>315</td><td>Explorist 100 (with aftermarket cable)</td></tr><tr><td>Map330</td><td>Explorist 200 (with aftermarket cable)</td></tr><tr><td>SporTrak Map Color</td><td>Explorist 300 (with aftermarket cable)</td></tr><tr><td>SporTrak Map</td><td>Explorist 210</td></tr><tr><td>SporTrak Map Pro</td><td>Explorist 300</td></tr><tr><td>SporTrak Map Topo</td><td>Explorist 400</td></tr><tr><td>Meridian (green or yellow)</td><td>Explorist 500</td></tr><tr><td>Meridian Gold</td><td>Explorist 600</td></tr><tr><td>Meridian Platinum</td><td>Explorist XL</td></tr></table><p>
</p><p>
The RoadMate family of products is not supported.
</p><p>
	This format is used for both the serial protocol used on the
	devices with serial ports such as Map330 and Meridian and for
	the files stored either in either the unit's internal memory 
	(Explorist 210, 400, 500, 600, XL) or on removable memory.
</p><p>
	If you specify a serial port for the file (.e.g. "COM1", "/dev/ttyS0")
	to be read or written, GPSBabel will use serial protocol.   Specifying
	a file, either on local filesystem or on a mounted flash card reader,
	will result in the file-based format being used.
</p><p>
	Users of the Explorist generation of receivers should probably
	prefer to use the <a class="link" href="#fmt_magellan" title="Magellan SD files (as for Meridian) (magellan)">magellanx</a>
	format over this one.

</p><div class="important"><h3 class="title">Important</h3><p>
This module does not support the units that do not follow Magellan's
documented communications protocols including:</p><table border="0" summary="Simple list" class="simplelist"><tr><td>Maestro 3100</td><td> RoadMate 800</td></tr><tr><td>Maestro 3140</td><td> RoadMate 860T</td></tr><tr><td>Maestro 3200</td><td> RoadMate 1200 </td></tr><tr><td>Maestro 3210</td><td> RoadMate 1400 </td></tr><tr><td>Maestro 3220</td><td> RoadMate 1412 </td></tr><tr><td>Maestro 3225</td><td> RoadMate 1430 </td></tr><tr><td>Maestro 3250</td><td> RoadMate 2000 </td></tr><tr><td>Maestro 4000</td><td> RoadMate 2000 </td></tr><tr><td>Maestro 4040</td><td> RoadMate 2200T</td></tr><tr><td>Maestro 4050</td><td> RoadMate 3000T</td></tr><tr><td>Maestro 4200</td><td> RoadMate 3050T</td></tr><tr><td>Maestro 4210</td><td> RoadMate 6000T</td></tr><tr><td>Maestro 4220</td><td> RoadMate AAA </td></tr><tr><td>Maestro 4250</td><td> Triton 200 </td></tr><tr><td>Maestro 5310</td><td> Triton 300 </td></tr><tr><td> RoadMate 300 </td><td> Triton 400 </td></tr><tr><td> RoadMate 360 </td><td> Triton 500 </td></tr><tr><td> RoadMate 500</td><td> Triton 1500 </td></tr><tr><td> RoadMate 700 </td><td> Triton 2000 </td></tr><tr><td> RoadMate 760</td><td> </td></tr></table></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_magellan1_o_deficon"></a><code class="option">deficon</code> option</h3></div></div></div><p>
      Default icon name.
    </p><p>
This option specifies the icon or waypoint type to write for each waypoint on
output.
</p><p>
If this option is specified, its value will be used for all waypoints, not
just those that do not already have descriptions.  That is, this option
overrides any icon description that might be in the input file.
</p><p>
This option has no effect on input.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_magellan1_o_maxcmts"></a><code class="option">maxcmts</code> option</h3></div></div></div><p>
      Max number of comments to write (maxcmts=200).
    </p><p>
The maxcmts option allows you to specify the number comments that will
be sent to the unit.
</p><p>
Magellan receivers allow a maximum of 200 waypoint comments.  Unfortunately,
DirectRoute uses waypoint comments to provide next turn directions for
navigation pop-ups and that comes from that pool of 200 comments.  It
is therefore sometimes convenient to limit the number of waypoint 
comments written to the receiver.   For example, a geocacher might want
to upload 400 waypoints, but only 190 with comments so that DirectRoute
could provide driving directions for the next ten turns.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_magellan1_o_baud"></a><code class="option">baud</code> option</h3></div></div></div><p>
      Numeric value of bitrate (baud=4800).
    </p><p>
  This option causes GPSBabel to use the given baud rate for serial
  communications.  It must match the given baud rate on the receiver.  The 
  default value matches the default on the receiver, 4800.
</p><p>
  Valid options are 1200, 2400, 4800, 9600, 19200, 57600, and 115200.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_magellan1_o_noack"></a><code class="option">noack</code> option</h3></div></div></div><p>
      Suppress use of handshaking in name of speed.
    </p><p>
Magellan's protocol specification strongly encourages the use of software
acknowledgements on every packets.   This is a simple "this is what I think
I heard.  If you agree that I heard it correctly, let's go to the next packet"
handshake that is used to ensure the integrity of the data transfer.
</p><p>
Certain firmware versions have problems handling this which makes transfers
unnecessarily slow.  Transfers on all units at high serial speeds  are also
severely restricted by this process. 
</p><p>
In controlled environments (good cables, low electrical noise, receiving
from the unit, not doing donuts with the unit set to "track up" at a 150
mile scale with 500 waypoints on the screen) it is sometimes useful to 
release that safety belt by using the "noack" suboption.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_magellan1_o_nukewpt"></a><code class="option">nukewpt</code> option</h3></div></div></div><p>
      Delete all waypoints.
    </p><p>
This option erases all waypoints in the receiver before doing a transfer.
</p><p>
This is a convenient option to use in automated processes where you want
to ensure the units starts with a clean state before sending waypoints to
it.   Using this option on transmit is a better idea than doing it on 
receive since the latter would erase all the waypoints before asking the
unit to send all the waypoints.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_ik3d"></a>MagicMaps IK3D project file (.ikt) (ik3d)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>
  This is the format for <a class="ulink" href="http://www.magicmaps.de" target="_top">MagicMaps</a> project (.ikt) files.
</p><p>
  <a class="ulink" href="http://www.magicmaps.de" target="_top">MagicMaps</a> <span class="productname">"Das interaktive Kartenwerk"</span>™ is a Software from Germany. It's a
  route-planning software with a 3-dimensional environment.
</p><p>
  The project files are XML based and we can read the main GPS items (names and coordinates). 
  For an output these files are too complex.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_mainnav"></a>Mainnav (mainnav)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
This is the format used by the <a class="ulink" href="http://www.mainnav.com" target="_top">Mainnav</a> MG-950d data logger.  It may work with other Mainnav devices.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_tef"></a>Map&amp;amp;Guide 'TourExchangeFormat' XML (tef)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_tef_o_routevia" title="routevia option">routevia</a> .</p><p>
TEF, internally called "TourExchangeFormat", is an XML based export format 
used by Map&amp;Guide <span class="productname">Motorrad-Routenplaner 2005/06</span>™.
</p><p>
Because this is only an export format, GPSBabel does not support writing to
this format.
</p><p>
GPSBabel also supports the <a class="link" href="#fmt_bcr" title="Motorrad Routenplaner (Map&amp;amp;Guide) .bcr files (bcr)">bcr</a> format, which 
may also be used with this program and supports both reading and writing.
</p><p><strong class="userinput"><code> gpsbabel -r -i tef,routevia -f in.xml -o gpx -F out.gpx</code></strong></p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_tef_o_routevia"></a><code class="option">routevia</code> option</h3></div></div></div><p>
      Include only via stations in route.
    </p><p>
This option may be used to eliminate calculated route points from the route.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_mapasia_tr7"></a>MapAsia track file (.tr7) (mapasia_tr7)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
   <a class="ulink" href="http://www.mapking.com/en/" target="_top">Mapking</a> provides a set of tools for GPS 
   navigation.  The location of distributed maps is mainly in Asia, so the software seems 
   not (yet) well known in Europe or US.  Some of the GPS tools (e.g. Mapking 2007 for Windows Mobile) 
   can also be used to write waypoints and save them under the .tr7 format which can be translated by GPSBabel.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_mapbar"></a>Mapbar (China) navigation track for Sonim Xp3300 (mapbar)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>
  This format is the Mapbar navigation programs used on phones such as
  the Sonim XP3300 popular in China.
  The files are found on the sd card in /mapbar/userdata/tracks.
  This format just logs track point by latitude and longitude; no time 
  information is available.
</p><p>
This was implemented by analyzing data from a Sonin SoninXp3300,
software version: 3.73.47.39836, data version: B29.
</p><p>
The following devices of using mapbar navigation are supported. Other
devices with using mapbar navigation maybe be supported, but not have 
not been tested:
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>Sonim Xp3300(China version)</td></tr></table><p>
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_mapfactor"></a>Mapfactor Navigator (mapfactor)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format can write a favourites.xml file that stores the waypoints in the Mapfactor Navigator street navigation program for Windows and Android OS. The waypoints are listed in the My places menu option. The favourites.xml file are stored in the Navigator directory.
</p><p>
This format can read waypoints from the favourites.xml file to use in other programs.
</p><p>
The format has been tested with Windows 8, Navigator version 12.3 and Android OS, v4.2.2, Navigator version 1.1.5.
</p><p>
The format has been tested with Windows 8, Navigator version 12.3 and Android OS, v4.2.2, Navigator version 1.1.5.
</p><p>
Groups are not supported, as they don't map well to other more common
file formats.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_mapconverter"></a>Mapopolis.com Mapconverter CSV (mapconverter)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
Mapconverter is a format that is read by Mapopolis.com's
mapconverter application.
</p><p>
Mapconverter is an application used to create userland maps and map data for 
Mapopolis.com's Mapopolis program.  The mapconverter format is essentially
waypoint data prepared in a format that the mapconverter application will
accept.
</p><p>
The steps for using GPSBabel and Mapconverter go something like this:
</p><p>
Step 1: Create a mapconverter file using gpsbabel.
</p><p><strong class="userinput"><code>gpsbabel -i geo -f geocaching.loc -o mapconverter -F foo.txt</code></strong></p><p>
Step 2: Launch mapconverter.exe and choose foo.txt as your input file.
	Click the begin button to have mapconverter process foo.txt.
</p><p>
If all goes successfully, you should have a file called "foo.pdb" ready
for syncing with your PDA.  Put it wherever Mapopolis thinks it should be
on your PDA.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mapconverter_notes"></a>Notes</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
GPSBabel will write the name of its own output file in the output file
  it creates as the input for Mapconverter.   Mapconverter will replace 
  the extension of this filename with ".pdb".
</p></li><li class="listitem"><p>
The PocketPC version of Mapopolis doesn't notice files with the ".pdb"
  extension.  To make this work, change the extension to ".mlp" when
  copying the mapconverter output to your PocketPC PDA.
</p></li><li class="listitem"><p>
Mapconverter only works with Mapopolis version 3.x.  Mapopolis version
  4 will refuse to load mapconverter maps.  There is no known work-around
  for this at the time of this writing.
</p></li><li class="listitem"><p>
Mapconverter is no longer available from the Mapopolis website.  If you
  need a copy of mapconverter, ask on your local GPS Software discussion
  forum and I'm sure someone will have it.  As far as I know, It was never 
  actually acknowledged/supported by Mapopolis to begin with.
</p></li></ul></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_mxf"></a>MapTech Exchange Format (mxf)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>Maptech Exchange Format - Another CSV format file.  This
format complies with (at least) Maptech Terrain Navigator, Terrain
Professional, Take a Hike, and ExpertGPS import/export MFX.
Contributed by Alex Mottram.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_mtk_locus"></a>MediaTek Locus (mtk_locus)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_mtk_locus_o_baudrate" title="baudrate option">baudrate</a>, <a class="link" href="#fmt_mtk_locus_o_download" title="download option">download</a>, <a class="link" href="#fmt_mtk_locus_o_erase" title="erase option">erase</a>, <a class="link" href="#fmt_mtk_locus_o_status" title="status option">status</a>, <a class="link" href="#fmt_mtk_locus_o_enable" title="enable option">enable</a> .</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mtk_locus_o_baudrate"></a><code class="option">baudrate</code> option</h3></div></div></div><p>
      Speed in bits per second of serial port (autodetect=0).
    </p><p>The default is to autodetect the baudrate, but that can take a few seconds.  If you know the baudrate of the device it is faster to specify it explicitly.</p><p>Only valid when using a USB device as input.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mtk_locus_o_download"></a><code class="option">download</code> option</h3></div></div></div><p>
      Download logged fixes.
    </p><p>This option processes a set of Locus fixes, by downloading it from an 
attached USB device or by reading records stored in a normal file.</p><p>You might want to disable this option if all you want to do is erase the memory 
or display the device status.  Downloading a large dataset can take several minutes
and while that is happening no other device commands can be executed.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mtk_locus_o_erase"></a><code class="option">erase</code> option</h3></div></div></div><p>
      Erase device data after download.
    </p><p>This option erases the track log from the device after download.</p><p>Only valid when using a USB device as input.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mtk_locus_o_status"></a><code class="option">status</code> option</h3></div></div></div><p>
      Show device status.
    </p><p>This option displays the status of the device after the download is complete.  Status includes firmware version, number of log records in memory, interval between fixes, etc.</p><p>Only valid when using a USB device as input.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mtk_locus_o_enable"></a><code class="option">enable</code> option</h3></div></div></div><p>
      Enable logging after download.
    </p><p>This option sets logging on the device to on or off.  Setting the logging off does not erase the saved fixes.</p><p>Only valid when using a USB device as input.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_mmo"></a>Memory-Map Navigator overlay files (.mmo) (mmo)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_mmo_o_locked" title="locked option">locked</a>, <a class="link" href="#fmt_mmo_o_visible" title="visible option">visible</a>, <a class="link" href="#fmt_mmo_o_ver" title="ver option">ver</a> .</p><p>
   The 'mmo' format provides support for binary .mmo files used by the
   Memory-Map Navigator software.
</p><p>
   Our module was reverse engineered from a couple of .mmo files found
   in the www. The results of the writing code have been tested with a current
   Memory-Map Navigator trial ('Viewer') release.
</p><p>
   Because of different file versions and sometimes slightly different file structure
   we cannot ensure, that every .mmo file is loadable at this time. If you have one,
   which causes errors, please provide it [mailto:gpsbabel-misc@lists.sourceforge.net].
</p><p>
   More information can be found at the 
   <a class="ulink" href="http://www.memory-map.com/" target="_top">Memory-Map</a> site.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mmo_o_locked"></a><code class="option">locked</code> option</h3></div></div></div><p>
      Write items 'locked' [default no].
    </p><p>
   By default GPSBabel creates only 'un-locked' items.
</p><p>
   Sample command to write an mmo file with 'locked' items:
</p><p>
   <strong class="userinput"><code>
      gpsbabel -i gpx -f in.gpx -o mmo,locked=y -F out.mmo
   </code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mmo_o_visible"></a><code class="option">visible</code> option</h3></div></div></div><p>
      Write items 'visible' [default yes].
    </p><p>
   This option can be useful, if you want to convert a big file with a lot of entries.
   By default GPSBabel creates only 'visible' items.
</p><p>
   Sample command to write an mmo file with 'invisible' items:
</p><p>
   <strong class="userinput"><code>
      gpsbabel -i gpx -f in.gpx -o mmo,visible=n -F out.mmo
   </code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mmo_o_ver"></a><code class="option">ver</code> option</h3></div></div></div><p>
      Write files with internal version [n].
    </p><p>
Two major strains of Mobile Mapper files have been identified in the wild.  Version 17 is reported as "Memory Map OS Edition 2004, Versio 4.2.3 Build 432" and version 18 is used by the large majority of current files.   We can read either and when writing, we write version 18 by default.  
</p><p>
If you have a particularly old Mobile Mapper installation, it may complain "This file was created with a newer version of the Software" when reading our output.You can get around this if force GPSBabel to create the old format with this option.   
</p><div class="example"><a id="mmo_ver"></a><div class="example-title">Example 3.16. Forcing creation of old Mobile Mapper files</div><div class="example-contents"><p>
  gpsbabel -i gpx -f whaetever.gpx -o mmo,ver=17 -F whatever.mmo
</p></div></div><br class="example-break" /></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_s_and_t"></a>Microsoft Streets and Trips 2002-2007 (s_and_t)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p> This is a format for creating data to be read by
  <a class="ulink" href="http://www.microsoft.com/streets/default.mspx" target="_top"> Microsoft Streets and
  Trips</a>.  It's been exercised on versions from 2003 through 2008. Detailed
  instructions on how to use it, including preserving hyperlinks, are at
  <a class="ulink" href="/formats/s_and_t/Importing_into_Microsoft_Streets_and_Trips_2003.html" target="_top">gpsbabel.org</a>
</p><p>
  We have an additional page describing how to solve the 
  <a class="ulink" href="/formats/s_and_t/TripPlanning.html" target="_top">traveling salesman problem with 
  Streets &amp; Trips</a> to efficiently optimize a trip with many stops, such as 
  is often made by geocachers.
</p><p>
  Since modern versions of Streets and Trips support reading GPX, this format is probably
  not so useful.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_miniHomer"></a>MiniHomer, a skyTraq Venus 6 based logger (download tracks, waypoints and get/set POI) (miniHomer)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_miniHomer_o_baud" title="baud option">baud</a>, <a class="link" href="#fmt_miniHomer_o_dump-file" title="dump-file option">dump-file</a>, <a class="link" href="#fmt_miniHomer_o_erase" title="erase option">erase</a>, <a class="link" href="#fmt_miniHomer_o_first-sector" title="first-sector option">first-sector</a>, <a class="link" href="#fmt_miniHomer_o_initbaud" title="initbaud option">initbaud</a>, <a class="link" href="#fmt_miniHomer_o_last-sector" title="last-sector option">last-sector</a>, <a class="link" href="#fmt_miniHomer_o_no-output" title="no-output option">no-output</a>, <a class="link" href="#fmt_miniHomer_o_read-at-once" title="read-at-once option">read-at-once</a>, <a class="link" href="#fmt_miniHomer_o_Home" title="Home option">Home</a>, <a class="link" href="#fmt_miniHomer_o_Car" title="Car option">Car</a>, <a class="link" href="#fmt_miniHomer_o_Boat" title="Boat option">Boat</a>, <a class="link" href="#fmt_miniHomer_o_Heart" title="Heart option">Heart</a>, <a class="link" href="#fmt_miniHomer_o_Bar" title="Bar option">Bar</a> .</p><p>
Serial download protocol for GPS data loggers called "miniHomer". 
These loggers are based on Skytraq Venus 5 and Venus 6 chipsets, but with modified firmware.
The miniHomer logger has five POI (or better: Point-to-Return, PTR?), which can be set programatically. The miniHomer module in gpsbabel is an extension of the skytraq module. 
</p><p>
Following a list of devices which should be supported by this module
(Note that not all of them have actually been tested, so if you can confirm that additional models work, please mail the gpsbabel-misc group with your success, tips, and any pertinent links for your model.)
</p><div class="table"><a id="miniHomer_devices"></a><div class="table-title">Table 3.5. Devices supported by miniHomer module</div><div class="table-contents"><table summary="Devices supported by miniHomer module" border="1"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Manufacturer</th><th>Model</th><th>USB (baud)</th><th>Bluetooth (baud)</th></tr></thead><tbody><tr><td>
  	<a class="ulink" href="http://navin.com.tw/miniHomer.htm" target="_top"> Navin </a>
  	<a class="ulink" href="http://www.znex.de/minihomer-details.html" target="_top">Z:NEX</a>
  </td><td>miniHomer</td><td>up to 230400</td><td>this device does not have bluetooth</td></tr></tbody></table></div></div><br class="table-break" /><div class="example"><a id="miniHomer-on-linux"></a><div class="example-title">Example 3.17. Command showing miniHomer download of tracks and erasing the logger on Linux</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i miniHomer,erase -f /dev/ttyUSB0 -o gpx -F out.gpx</code></strong></p></div></div><br class="example-break" /><div class="example"><a id="miniHomer-erase"></a><div class="example-title">Example 3.18. Command showing miniHomer erasing the logger without download on Linux</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i miniHomer,erase,no-output -f /dev/ttyUSB0</code></strong></p></div></div><br class="example-break" /><p>miniHomer has five POI called Home, <span class="emphasis"><em>Car</em></span>, <span class="emphasis"><em>Boat</em></span>, <span class="emphasis"><em>Heart</em></span>, <span class="emphasis"><em>Bar</em></span>. You can set the lla 
(Latitude, Longitude, Altitude) for each of the POI. The format is 
<span class="emphasis"><em>&lt;name&gt;=&lt;lat&gt;:&lt;lng&gt;[:&lt;alt&gt;]</em></span>
Once the according POI symbol is selected on miniHomer, the display shows you the direction and distance to the POI.
</p><div class="example"><a id="miniHomer-on-linux-poi"></a><div class="example-title">Example 3.19. Command showing miniHomer setting Car and Home POI</div><div class="example-contents"><p>
  	<strong class="userinput"><code>
  	   gpsbabel -i miniHomer,Car=36.790145:-6.352898,Home=-3.066667:37.359167:5895 -f /dev/ttyUSB0 -o gpx -F out.gpx
  	</code></strong>
       Sets the Car/Home symbols' latitude longitude and altitude.
       If you select the Car/Home symbol on miniHomer, the display will show the direction and distance to 
       this location as soon as it has a satellite fix.
	</p></div></div><br class="example-break" /><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_miniHomer_o_baud"></a><code class="option">baud</code> option</h3></div></div></div><p>
      Baud rate used for download.
    </p><p>The following baud rates can be used: 4800, 9600, 19200, 38400, 57600, 115200, 230400.
Note that your logger might not support all of them (especially 230400 which isn't documented
in the chipset manual, though there are known devices that are capable of this speed).
</p><p>If <strong class="userinput"><code>baud=0</code></strong> (zero) download takes place at the baud rate the
device is currently set to. This is especially useful for Bluetooth connections (if available) since they
often don't allow changing the baud rate.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_miniHomer_o_dump-file"></a><code class="option">dump-file</code> option</h3></div></div></div><p>
      Dump raw data to this file.
    </p><p>
This function is identical to the dump-file function of skytraq module:
Writes raw data as it is read from the logger to the file given as this option's argument
(additional to decoding it as usual). The resulting binary files can be read and decoded by the skytraq-bin format.
Mainly useful for debugging/development purposes.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_miniHomer_o_erase"></a><code class="option">erase</code> option</h3></div></div></div><p>
      Erase device data after download.
    </p><p>
Erase log buffer.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_miniHomer_o_first-sector"></a><code class="option">first-sector</code> option</h3></div></div></div><p>
      First sector to be read from the device.
    </p><p>
This function is identical to the first-sector function of skytraq module.
</p><p>The logger's memory is organized in sectors, serially numbered starting at 0. Each sector takes 4096 bytes of data.
Typical devices hold about 250 sectors. The memory is always filled from sector 0 on, until it is full or the device being
erased again by the user.</p><p>Normally you can safely omit this option. However, it might be useful to read data from erased devices: we observed
that on erase, only the first two sectors are actually cleared. The following example shows how to read the remaining data:
</p><div class="example"><a id="miniHomer-restore-erased"></a><div class="example-title">Example 3.20. Command showing how to read data from an erased device</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i miniHomer,first-sector=2 -f /dev/ttyUSB0 -o gpx -F out.gpx</code></strong></p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_miniHomer_o_initbaud"></a><code class="option">initbaud</code> option</h3></div></div></div><p>
      Baud rate used to init device (0=autodetect).
    </p><p>
This function is identical to the init-baud file function of skytraq module. 
</p><p>The "initbaud" option might be helpful if autodetection fails or takes too long. With this option you
can tell GPSBabel the baud rate the device is currently set to. In contrast, the option "baud" specifies
the rate at which the actual download should take place. If it is different than "initbaud" (or the autodetected
rate, if initbaud wasn't given), the initial setting will be restored after finishing the download.
</p><p>
Please note that miniHomer by default uses 38400bps and does not autodetect the port speed. If you need autodetect, start as
<strong class="userinput"><code>gpsbabel -i miniHomer,initbaud=0 -f /dev/ttyUSB0 -o gpx -F out.gpx</code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_miniHomer_o_last-sector"></a><code class="option">last-sector</code> option</h3></div></div></div><p>
      Last sector to be read from the device (-1: smart read everything).
    </p><p>A value of -1 (the default) enables automatic mode, i.e. reading is stopped when an empty sector is
encountered.
We observed that sometimes the device doesn't report the correct number of used sectors, which confuses the Windows
software, so that it might not get all trackpoints.
In contrast, our algorithm ensures that everything is being read (please report if it doesn't work for you).</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_miniHomer_o_no-output"></a><code class="option">no-output</code> option</h3></div></div></div><p>
      Disable output (useful with erase).
    </p><p>If this option is given, no GPS log data will be read from the device
(unless "dump-file" is given too; in that case only decoding will be disabled).</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_miniHomer_o_read-at-once"></a><code class="option">read-at-once</code> option</h3></div></div></div><p>
      Number of sectors to read at once (0=use single sector mode).
    </p><p>If <strong class="userinput"><code>read-at-once</code></strong> &gt;= 1, batch mode is enabled with that many sectors being read at a time.
A value of zero disables batch mode and switches to single read mode. Not all devices support batch mode; in that case
gpsbabel automatically switches to single read mode.</p><p>Under normal circumstances, the larger this number the faster the transfer.
Reducing <strong class="userinput"><code>read-at-once</code></strong> or even switching to single sector mode might help when you get
transmission errors/aborts.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_miniHomer_o_Home"></a><code class="option">Home</code> option</h3></div></div></div><p>
      POI for Home Symbol as lat:lng[:alt].
    </p><p>
  The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar". 
  You can program the location of each either by a keypress on the device (which uses the actual position) 
  or with GPSBabel (which lets you use any position)
  You can set the location of "Home" with the 'Home' option.  Use ':' as the delimiter between latitude, longitude and altitude. 
  You can leave altitude out, in which case it is assumed to be zero.
  Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it.
</p><div class="example"><a id="miniHomer-Home"></a><div class="example-title">Example 3.21. Set the target location of the miniHomer Home POI</div><div class="example-contents"><p>
       <strong class="userinput"><code>gpsbabel -i miniHomer,Home=-3.066667:37.359167:5895 -f /dev/ttyUSB0 -o unicsv -F -</code></strong>
  </p><p>
       Sets the Home symbols' latitude to 3.066667S longitude to 37.359167E and altitude to 5895m.
       If you select the Home symbol on miniHomer, the display will show the direction and distance to 
       this location as soon as it has a satellite fix.
 </p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_miniHomer_o_Car"></a><code class="option">Car</code> option</h3></div></div></div><p>
      POI for Car Symbol as lat:lng[:alt].
    </p><p>
  The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar". 
  You can program the location of each either by a keypress on the device (which uses the actual position) 
  or with GPSBabel (which lets you use any position)
  You can set the location of "Car" with the 'Car' option.  Use ':' as the delimiter between latitude, longitude and altitude. 
  You can leave altitude out, in which case it is assumed to be zero.
  Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it.
</p><div class="example"><a id="miniHomer-Car"></a><div class="example-title">Example 3.22. Set the target location of the miniHomer Car POI</div><div class="example-contents"><p>
       <strong class="userinput"><code>gpsbabel -i miniHomer,Car=-25.272309:153.235330 -f /dev/ttyUSB0 -o unicsv -F -</code></strong>
  </p><p>
       Sets the Car symbols' latitude to 25.272309S longitude to 153.235330E and altitude to 0m.
       If you select the Car symbol on miniHomer, the display will show the direction and distance to 
       this location as soon as it has a satellite fix.
 </p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_miniHomer_o_Boat"></a><code class="option">Boat</code> option</h3></div></div></div><p>
      POI for Boat Symbol as lat:lng[:alt].
    </p><p>
  The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar". 
  You can program the location of each either by a keypress on the device (which uses the actual position) 
  or with GPSBabel (which lets you use any position)
  You can set the location of "Boat" with the 'Boat' option.  Use ':' as the delimiter between latitude, longitude and altitude. 
  You can leave altitude out, in which case it is assumed to be zero.
  Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it.
</p><div class="example"><a id="miniHomer-Boat"></a><div class="example-title">Example 3.23. Set the target location of the miniHomer Boat POI</div><div class="example-contents"><p>
       <strong class="userinput"><code>gpsbabel -i miniHomer,Boat=32.29287:-64.77527 -f /dev/ttyUSB0 -o unicsv -F -</code></strong>
  </p><p>
       Sets the Boat symbols' latitude to 32.29287N longitude to 64.77527E and altitude to 0m.
       If you select the Home symbol on miniHomer, the display will show the direction and distance to 
       this location as soon as it has a satellite fix.
 </p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_miniHomer_o_Heart"></a><code class="option">Heart</code> option</h3></div></div></div><p>
      POI for Heart Symbol as lat:lng[:alt].
    </p><p>
  The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar". 
  You can program the location of each either by a keypress on the device (which uses the actual position) 
  or with GPSBabel (which lets you use any position)
  You can set the location of "Heart" with the 'Heart' option.  Use ':' as the delimiter between latitude, longitude and altitude. 
  You can leave altitude out, in which case it is assumed to be zero.
  Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it.
</p><div class="example"><a id="miniHomer-Heart"></a><div class="example-title">Example 3.24. Set the target location of the miniHomer Heart POI</div><div class="example-contents"><p>
       <strong class="userinput"><code>gpsbabel -i miniHomer,Heart=36.1269:-115.1698 -f /dev/ttyUSB0 -o unicsv -F -</code></strong>
  </p><p>
       Sets the Heart symbols' latitude to 36.1269N longitude to 115.1698W and altitude to 0m.
       If you select the Heart symbol on miniHomer, the display will show the direction and distance to 
       this location as soon as it has a satellite fix.
 </p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_miniHomer_o_Bar"></a><code class="option">Bar</code> option</h3></div></div></div><p>
      POI for Bar Symbol as lat:lng[:alt].
    </p><p>
  The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar". 
  You can program the location of each either by a keypress on the device (which uses the actual position) 
  or with GPSBabel (which lets you use any position)
  You can set the location of "Bar" with the 'Bar' option.  Use ':' as the delimiter between latitude, longitude and altitude. 
  You can leave altitude out, in which case it is assumed to be zero.
  Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it.
</p><div class="example"><a id="miniHomer-Bar"></a><div class="example-title">Example 3.25. Set the target location of the miniHomer Bar POI</div><div class="example-contents"><p>
       <strong class="userinput"><code>gpsbabel -i miniHomer,Bar=38.99809:-86.34662 -f /dev/ttyUSB0 -o unicsv -F -</code></strong>
  </p><p>
       Sets the Bar symbols' latitude to 38.99809N longitude to 86.34662W and altitude to 0m.
       If you select the Bar symbol on miniHomer, the display will show the direction and distance to 
       this location as soon as it has a satellite fix.
 </p></div></div><br class="example-break" /></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_garmin_xt"></a>Mobile Garmin XT Track files (garmin_xt)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_garmin_xt_o_ftype" title="ftype option">ftype</a>, <a class="link" href="#fmt_garmin_xt_o_trk_header" title="trk_header option">trk_header</a> .</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_xt_o_ftype"></a><code class="option">ftype</code> option</h3></div></div></div><p>
      Garmin Mobile XT ([ATRK]/STRK).
    </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_garmin_xt_o_trk_header"></a><code class="option">trk_header</code> option</h3></div></div></div><p>
      Track name processing option ([0]-nrm/1-ign).
    </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_motoactv"></a>Motoactiv CSV (motoactv)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
The <span class="productname">MotoACTV</span>™ smart watch creates csv
format files. GPSBabel can read and write these files through
the xcsv format when using the included motoactv.style specification. 
</p><p>
The specific format of the csv file has changed over time, to
add new data fields. The current version of the GPSBabel style
specification expects to work with this ordered set of fields:
</p><p>
"DISTANCE","activity_id","HEARTRATE","SPEED","STEPS_PER_MINUTE",
"LATITUDE","repetitions","temperature","INSTANT_TORQUE_CRANK",
"timestamp_epoch","ELEVATION","POWER","STRIDES","wheel_torque",
"CALORIEBURN","LONGITUDE","CADENCE","heading","STEP_RATE"
</p><p><strong class="userinput"><code>
gpsbabel -i xcsv,style=motoactv.style -f rawDataCsv.csv
-x transform,trk=wpt -o gtrnctr,course=0 -F outfile.tcx
</code></strong></p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_bcr"></a>Motorrad Routenplaner (Map&amp;amp;Guide) .bcr files (bcr)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_bcr_o_index" title="index option">index</a>, <a class="link" href="#fmt_bcr_o_name" title="name option">name</a>, <a class="link" href="#fmt_bcr_o_radius" title="radius option">radius</a>, <a class="link" href="#fmt_bcr_o_prefer_shortnames" title="prefer_shortnames option">prefer_shortnames</a> .</p><p> 
This file format (extension .bcr) is used in Map&amp;Guide 
<span class="productname">Motorrad Routenplaner 2002</span>™ and later versions. 
BCR is a route-only format. If you own a newer release (2005 or later) you 
may also use the XML export with GPSBabel's <a class="link" href="#fmt_tef" title="Map&amp;amp;Guide 'TourExchangeFormat' XML (tef)">tef</a> 
input format.  
</p><p>
There may be other products from Map&amp;Guide that use this format as well.
</p><p> 
Coordinates are stored in a BCR file in a Mercator projection. The
conversion from the Mercator projection to polar (latitude/longitude) 
coordinates and back again may result in visible differences.  Experience 
reports are welcome.
</p><div class="example"><a id="sample_bcr_command"></a><div class="example-title">Example 3.26. Sample BCR command with all options</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -r -i gpx -f in.gpx -o bcr,index=1,name="From A to B",radius=6371012 -F a_to_b.bcr</code></strong></p></div></div><br class="example-break" /><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_bcr_o_index"></a><code class="option">index</code> option</h3></div></div></div><p>
      Index of route to write (if more than one in source).
    </p><p>
Because the format supports only one route, this option may be used 
on output to select a single route from a collection of 
routes read from a more expressive format.  If you have, say, a 
<a class="link" href="#fmt_gpx" title="GPX XML (gpx)">gpx</a> file that contains two routes, you may
use this option to write them one at a time to individual files.
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f routes.gpx -o bcr,index=1 -F route1.bcr -o bcr,index=2 -F route2.bcr</code></strong></p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_bcr_o_name"></a><code class="option">name</code> option</h3></div></div></div><p>
      New name for the route.
    </p><p>
This route specifies the name of the route.  This is particularly useful if
the route came from an input format that did not support named routes, but 
it may also be used to rename a route.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_bcr_o_radius"></a><code class="option">radius</code> option</h3></div></div></div><p>
      Radius of our big earth (default 6371000 meters).
    </p><p>
This option instructs GPSBabel to use a different value for the radius of 
the earth when converting between the Mercator projection and geographic 
coordinates.  The default value is 6371000.0 meters.
</p><p>
Careful experimentation with this value may help to reduce conversion
errors.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_bcr_o_prefer_shortnames"></a><code class="option">prefer_shortnames</code> option</h3></div></div></div><p>
      Use shortname instead of description.
    </p><p>
This option causes GPSBabel to use the short name of the waypoint instead
of the description.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_mtk-bin"></a>MTK Logger (iBlue 747,...) Binary File Format (mtk-bin)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_mtk-bin_o_csv" title="csv option">csv</a> .</p><p>Binary file protocol converter for MTK based GPS loggers.
This format reads the raw binary format created by the MTK Windows application
and outputs to other formats  supported by GPSBabel
When using the csv option a MTK application compatible output file will also be created.</p><p>
It has been tested with <span class="productname">Transystem i-Blue 747</span>™ but other devices should
work as well (Qstarz BT-Q1000, iTrek Z1, ...)
</p><p>
All position items (including button push) will be listed as trackpoints in the output. 
Log items due to button push are presented as waypoints. 
In theory we would not add waypoints to the list of trackpoints. But as the MTK logger restart the 
log session from the button press we would loose a trackpoint unless we include/duplicate it.

</p><p>
<a class="ulink" href="http://www.transystem.com.tw/p-gps-iblue747.htm" target="_top">Transystem i-Blue 747</a>
</p><div class="example"><a id="mtk-bin-on-linux"></a><div class="example-title">Example 3.27. Convert MTK binary trackpoints to GPX</div><div class="example-contents"><p>
  <strong class="userinput"><code>gpsbabel -t -i mtk-bin,csv=extra.csv -f data.bin -o gpx -F out.gpx</code></strong>
   Additionally a CSV output file is created.
  </p></div></div><br class="example-break" /><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mtk-bin_o_csv"></a><code class="option">csv</code> option</h3></div></div></div><p>
      MTK compatible CSV output file.
    </p><p>
  Specifies a filename into which  MTK-compatible CSV output will be written.
</p><p>
  Note that this option is a bit of an oddity in the GPSBabel arsenal.  This
  should probably be a "real" output type of its own instead of being bolted
  onto an input type.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_mtk"></a>MTK Logger (iBlue 747,Qstarz BT-1000,...) download (mtk)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_mtk_o_erase" title="erase option">erase</a>, <a class="link" href="#fmt_mtk_o_erase_only" title="erase_only option">erase_only</a>, <a class="link" href="#fmt_mtk_o_log_enable" title="log_enable option">log_enable</a>, <a class="link" href="#fmt_mtk_o_csv" title="csv option">csv</a> .</p><p>
  This format is the serial download protocol for the MTK chips.   
  Mediatek's MT3301/3179 (MTKv1) and MT3318 (MTKv2) chips are used 
  in a large number of products sold under different names.  
</p><p>
  Many GPS products, especially of the data logger variety, expose 
  the Mediatek protocol to the user via USB.  Some modify Mediatek's 
  protocol in minor ways, but the core protocol is very commonly 
  seen in loggers.   
</p><p>
  The <a class="link" href="#fmt_m241" title="Holux M-241 (MTK based) download (m241)">Holux M-241 and GPSport 245</a> 
  are examples of a device using an incompatible variation of the MTK 
  protocol.
</p><p>
The following products are known or are expected to work with this module.
As the products are typically very low cost, they tend to have a short 
product life cycle and are often imported to different areas under 
different names.  Keeping
track of the list is difficult.   Often the "same" GPS is sold in different
plastic or with different Windows software or different options such as 
compass or motion sensors or charging cables with different model numbers.
If you can confirm success with others, please share with us.
</p><div class="table"><a id="mtk_devices"></a><div class="table-title">Table 3.6. Devices supported by MTK module</div><div class="table-contents"><table summary="Devices supported by MTK module" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Product</th><th>Confirmed to work</th><th>Notes</th></tr></thead><tbody><tr><td>iBlue 821</td><td>Yes</td><td>Available from <a class="ulink" href="http://www.semsons.com/i821ulblgpsr.html" target="_top">Semsons</a></td></tr><tr><td>iBlue 747, 747A+</td><td>Yes</td><td>Available from <a class="ulink" href="http://www.semsons.com/i74blgpsdalo.html" target="_top">Semsons</a></td></tr><tr><td>QStarz BT-1000, BT-Q1000X, BT-1000eX</td><td>Yes</td><td> </td></tr><tr><td>iTrek Z1</td><td> </td><td> </td></tr></tbody></table></div></div><br class="table-break" /><p>
  The Mediatek chip offers a native serial port.   Data logger designers
  frequently pair this with commodity USB/Serial converter internally.  So
  these devices typically look like Prolific, FTDI, or Silab usb/serial 
  devices to the host OS.  You'll need drivers for that whatever chip 
  your product uses for your operating system.
</p><p>
  Downloaded data will be stored in data.bin file in the current 
  directory together with the choosen output format.  This is a rather
  uncommon feature in GPSBabel's formats and is likely to change in future
  versions.
</p><p>See <a class="link" href="#fmt_mtk-bin" title="MTK Logger (iBlue 747,...) Binary File Format (mtk-bin)">mtk-bin</a> on how trackpoints/waypoints are handled</p><div class="example"><a id="mtk-on-linux"></a><div class="example-title">Example 3.28. Command showing MTK download track and waypoints and erase on Linux</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -t -w -i mtk,erase -f /dev/ttyUSB0 -o gpx -F out.gpx</code></strong></p></div></div><br class="example-break" /><p>
  For more info and tweaks on MTK based loggers: 
   <a class="ulink" href="http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=81990" target="_top">MTK Tips and Tweaks</a> and
   <a class="ulink" href="http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=81315" target="_top">iBlue 747 Logger</a>
 For info about the used log format, see
  <a class="ulink" href="http://spreadsheets.google.com/pub?key=pyCLH-0TdNe-5N-5tBokuOA&amp;gid=5" target="_top">MTK binary format</a>
</p><p>
Most of the loggers cannot receive bluetooth commands; they can only send 
  data. Since GPSBabel needs to send commands to the GPS device it won't
  work. Download the data using the USB cable instead.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mtk_o_erase"></a><code class="option">erase</code> option</h3></div></div></div><p>
      Erase device data after download.
    </p><p>This option erases the track log from the device after download.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mtk_o_erase_only"></a><code class="option">erase_only</code> option</h3></div></div></div><p>
      Only erase device data, do not download anything.
    </p><p>This option will only erase the logger data. No data is downloaded.</p><p>This option is typically used as a second step after the data has been downloaded and verified.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mtk_o_log_enable"></a><code class="option">log_enable</code> option</h3></div></div></div><p>
      Enable logging after download.
    </p><p>This option will enable the logger after download.</p><p>By default the logger is re-enabled when download is finished if previously were enabled.
But if the download is aborted or failed the log functionality won't be enabled again.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mtk_o_csv"></a><code class="option">csv</code> option</h3></div></div></div><p>
      MTK compatible CSV output file.
    </p><p>This option will create an additional CSV output file.
The CSV file is compatible with the original MTK logger application.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_tpg"></a>National Geographic Topo .tpg (waypoints) (tpg)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_tpg_o_datum" title="datum option">datum</a> .</p><p>National Geographic Topo! Waypoint and Route Format.  This module
reads and writes .TPG files created by various editions of NG Topo!
Reading/writing of route data is not supported yet.</p><p>Contributed by Alex Mottram.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_tpg_o_datum"></a><code class="option">datum</code> option</h3></div></div></div><p>
      Datum (default=NAD27).
    </p><p>The option 'datum="datum name"' can be used to override
the default of NAD27 ("N. America 1927 mean") which is correct for the
continental U.S.</p><p>Any legal <a class="link" href="#Datums" title="Appendix A. Supported Datums">datum supported
by GPSBabel</a> may be used.  For example, points in Hawaii should 
use "Old Hawaiian_mean".</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_tpo2"></a>National Geographic Topo 2.x .tpo (tpo2)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>
	This module reads tracks from .TPO files created by 
	National Geographic Topo! version 2.x
</p><p>
	Contributed by Steve Chamberlin.  
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_tpo3"></a>National Geographic Topo 3.x/4.x .tpo (tpo3)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read routes
        </p></li></ul></div><p>This module reads .TPO files created by National Geographic Topo! version
3.x and 4.x.  It will read tracks, routes, waypoints, map notes, symbols, and
text notes.  The latter three are converted to waypoints.</p><p>Contributed by Curt Mills.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_navicache"></a>Navicache.com XML (navicache)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_navicache_o_noretired" title="noretired option">noretired</a> .</p><p>
  This is the XML format that's used by Navicache.com for
  their geocaching data.  There are a number of fields in it that are
  marked "required" but are Navicache-specific, so GPSBabel can not
  write these files, but we can still read them. 
  <a class="ulink" href="http://www.navicache.com/cgi-bin/ib312a/ikonboard.cgi?act=ST;f=23;t=334" target="_top">navicache.com</a>
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_navicache_o_noretired"></a><code class="option">noretired</code> option</h3></div></div></div><p>
      Suppress retired geocaches.
    </p><p>
  If this option is present, retired (archived) caches will be suppressed on write.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_nmn4"></a>Navigon Mobile Navigator .rte files (nmn4)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_nmn4_o_index" title="index option">index</a> .</p><p>Support for Navigon Mobile Navigator route (.rte) files.
This is a very simple text format that only requires coordinates, but
has fields for many other things.  We only write coordinates as fields
like 'city' and 'street' cannot typically be populated from other
formats. <a class="ulink" href="http://www.navigon.com" target="_top">www.navigon.com</a>
         </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_nmn4_o_index"></a><code class="option">index</code> option</h3></div></div></div><p>
      Index of route to write (if more than one in source).
    </p><p>
Because the format supports only one route, this option may be used 
on output to select a single route from a collection of 
routes read from a more expressive format.  If you have, say, a 
<a class="link" href="#fmt_gpx" title="GPX XML (gpx)">gpx</a> file that contains two routes, you may
use this option to write them one at a time to individual files.
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f routes.gpx -o nmn4,index=1 -F route1.rte -o nmn4,index=2 -F route2.rte</code></strong></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_navigonwpt"></a>Navigon Waypoints (navigonwpt)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
  This is the waypoint file format for Navigon units such as the Navigon 7100.
</p><p>
  To actually manipulate the file on the unit, use a USB cable or SD card
  reader and work with <code class="filename">MN6\Settings\Favorites.storage</code> 
  The waypoints are be created with a minimal amount of data; the unit will
  fill in the other fields on use. The other fields appear to be data the
  unit infers, such as nearby streets.
</p><p>
  Note that this is the waypoint/placemark format (.storage) and not the 
  route file format (.rte, .mn4) that is used by routes.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_navilink"></a>NaviGPS GT-11/BGT-11 Download (navilink)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_navilink_o_nuketrk" title="nuketrk option">nuketrk</a>, <a class="link" href="#fmt_navilink_o_nukerte" title="nukerte option">nukerte</a>, <a class="link" href="#fmt_navilink_o_nukewpt" title="nukewpt option">nukewpt</a>, <a class="link" href="#fmt_navilink_o_nukedlg" title="nukedlg option">nukedlg</a>, <a class="link" href="#fmt_navilink_o_datalog" title="datalog option">datalog</a>, <a class="link" href="#fmt_navilink_o_power_off" title="power_off option">power_off</a> .</p><p>
	GPSBabel supports the Navilink protocol used by the
	<a class="ulink" href="http://www.locosystech.com/product.php?zln=en&amp;id=5" target="_top">Locosys GT-11</a> 
	and
	<a class="ulink" href="http://www.locosystech.com/product.php?zln=en&amp;id=30" target="_top">GT-31</a>
	GPS receivers. These are sold under a variety of names including:
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>NaviGPS</td><td>BGT-11</td><td>Amaryllo</td></tr><tr><td>NaviGPS-BT</td><td>GT-31</td><td> </td></tr><tr><td>GT-11</td><td>BGT-31</td><td> </td></tr></table><p>
</p><p>
	This format is used for both the serial protocol used on
	the USB link and for the files which can be copied from the
	internal memory to the SD card using recent firmware versions.
</p><p>
	If you specify a serial port for the file (.e.g. "COM1", "/dev/ttyUSB0")
	to be read or written, GPSBabel will use the serial protocol. Specifying
	a file, either on local filesystem or on a mounted flash card reader,
	will results in the file-based format being used.
</p><p>
	To access the device using the serial protocol over USB the
	device needs to be in Navilink mode, which can be activated
	from the main menu of the device.
</p><p>
	Details of the Navilink serial protocol can be found
	<a class="ulink" href="http://wiki.splitbrain.org/navilink" target="_top">here</a>.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_navilink_o_nuketrk"></a><code class="option">nuketrk</code> option</h3></div></div></div><p>
      Delete all track points.
    </p><p>
This option erases all track data in the receiver before or after
doing the transfer, depending on whether track data is sent to or
received from the device.
</p><p>
This is a convenient option to use in automated processes where you want
to ensure the units starts with a clean state before sending track data to
it, or if you want to clear the device after receiving the track data.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_navilink_o_nukerte"></a><code class="option">nukerte</code> option</h3></div></div></div><p>
      Delete all routes.
    </p><p>
This option erases all routes in the receiver before or after doing
the transfer, depending on whether routes are sent to or received from
the device.
</p><p>
This is a convenient option to use in automated processes where you
want to ensure the units starts with a clean state before sending
routes to it, or if you want to clear the device after receiving the
routes.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_navilink_o_nukewpt"></a><code class="option">nukewpt</code> option</h3></div></div></div><p>
      Delete all waypoints.
    </p><p>
This option erases all waypoints in the receiver before or after doing
the transfer, depending on whether waypoints are sent to or received
from the device.
</p><p>
This is a convenient option to use in automated processes where you
want to ensure the units starts with a clean state before sending
waypoints to it, or if you want to clear the device after receiving
the waypoints.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_navilink_o_nukedlg"></a><code class="option">nukedlg</code> option</h3></div></div></div><p>
      Clear the datalog.
    </p><p>
This option clears the datalogger in the receiver after doing the
transfer.
</p><p>
This is a convenient option to use in automated processes if you want
to clear the device after receiving the data logger contents.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_navilink_o_datalog"></a><code class="option">datalog</code> option</h3></div></div></div><p>
      Read from datalogger buffer.
    </p><p>
This option transfers the contents of the unit's data log. The data is
downloaded as a single track.
</p><p>
Only reading of the data log is supported, and you must use
the <code class="option">-t</code> option to receive any data.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_navilink_o_power_off"></a><code class="option">power_off</code> option</h3></div></div></div><p>
      Command unit to power itself down.
    </p><p>
This options powers down the Navilink receiver once any transfers are
complete.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_sbp"></a>NaviGPS GT-31/BGT-31 datalogger (.sbp) (sbp)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>
	This format is for SBP datalog files saved to the SD card by
	the Locosys GT-11/BGT-11/GT-31/BGT-31 GPS receivers.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_sbn"></a>NaviGPS GT-31/BGT-31 SiRF binary logfile (.sbn) (sbn)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>
	This format is for SBN datalog files saved to the SD card by
	the Locosys GT-11/BGT-11/GT-31/BGT-31 GPS receivers.
</p><p>
	On the device, logging in this format is enabled by choosing
	SBN from the NMEA ITEMS menu on the MEMORY CARD screen.
</p><p>
	Not all data logged in this format is converted by GPSBabel,
	but the following are:

</p><table border="0" summary="Simple list" class="simplelist"><tr><td>Position</td><td>Fix type (2D/3D/DGPS)</td><td>Number of satellites visible</td></tr><tr><td>Elevation</td><td>Speed</td><td>Horizontal Dilution of Precision (HDOP)</td></tr><tr><td>Time</td><td>Course</td><td> </td></tr></table><p>
</p><p>
	The specification of this format can be found in
	the <a class="ulink" href="http://www.navmanwirelessoem.com/oem/customer-support/oem-news/product-briefs-and-data-sheets/jupiter-32-xlp-new2/sirf-binary-protocol-reference-manual" target="_top">
	SiRF Binary Protocol Reference Manual</a>, in the section
	called Geodetic Navigation Data - Message ID 41.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_naviguide"></a>Naviguide binary route file (.twl) (naviguide)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_naviguide_o_output" title="output option">output</a>, <a class="link" href="#fmt_naviguide_o_reorder" title="reorder option">reorder</a> .</p><p>Naviguide 3.02 is off-road navigation software. Naviguide covers the area of Israel and uses the Israeli old grid as a reference; Naviguide uses Hebrew as its default language.</p><p>Naviguide uses unique map file format and binary file format (.twl) as route file.
The *.twl file contains a route that is comprised of a list of waypoints. Naviguide does not support a file that contains only waypoints.</p><p>GPSBabel supports reading and creating Naviguide route files. Plot files are not supported.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_naviguide_o_output"></a><code class="option">output</code> option</h3></div></div></div><p>
      'wp' - Create waypoint file , 'rte' - Create route file.
    </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_naviguide_o_reorder"></a><code class="option">reorder</code> option</h3></div></div></div><p>
      'n' - Keep the existing wp name, 'y' - rename waypoints.
    </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_navitel_trk"></a>Navitel binary track (.bin) (navitel_trk)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
   <a class="ulink" href="http://www.navitel.su" target="_top">Navitel</a>Navigator is very popular navigation
   software in Russia and it's neighbors.
</p><p>
   This binary format only stores the latitude and the longitude of a trackpoint and is
   limited to 10000 points per file.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_dna"></a>Navitrak DNA marker format (dna)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
    Navitrak DNA marker format - Another CSV format file. This
    is the format that is compatible with the DNA Desktop import/export
    command.  Reading the binary Markers.jwp format directly off the data
    card is not supported yet.  Contributed by Tim Zickus.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_netstumbler"></a>NetStumbler Summary File (text) (netstumbler)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_netstumbler_o_nseicon" title="nseicon option">nseicon</a>, <a class="link" href="#fmt_netstumbler_o_nsneicon" title="nsneicon option">nsneicon</a>, <a class="link" href="#fmt_netstumbler_o_seicon" title="seicon option">seicon</a>, <a class="link" href="#fmt_netstumbler_o_sneicon" title="sneicon option">sneicon</a>, <a class="link" href="#fmt_netstumbler_o_snmac" title="snmac option">snmac</a> .</p><p>
This format reads summary files from <span class="productname">NetStumbler</span><span class="productnumber">0.4</span> or <span class="productname">MacStumbler</span>™.
</p><p> 
The default behavior when creating waypoints is to use the SSID for
the short name, and information about the access point for the
description.  When the SSID is not unique, is not available, or
consists of whitespace, a short name is synthesized. 
</p><p> 
Different icons are assigned to encrypted,
non-encrypted, stealth, and non-stealth access points; these may be
changed with options. 
</p><p>
<a class="ulink" href="http://www.netstumbler.com/" target="_top">NetStumbler</a>
</p><p>
<a class="ulink" href="http://www.macstumbler.com/" target="_top">MacStumbler</a>   
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_netstumbler_o_nseicon"></a><code class="option">nseicon</code> option</h3></div></div></div><p>
      Non-stealth encrypted icon name.
    </p><p>
This option specifies the name of the icon to use for 
non-stealth, encrypted access points.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_netstumbler_o_nsneicon"></a><code class="option">nsneicon</code> option</h3></div></div></div><p>
      Non-stealth non-encrypted icon name.
    </p><p>
This option specifies the name of the icon to use for 
non-stealth, non-encrypted access points.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_netstumbler_o_seicon"></a><code class="option">seicon</code> option</h3></div></div></div><p>
      Stealth encrypted icon name.
    </p><p>
This option specifies the name of the icon to use for 
stealth, encrypted access points.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_netstumbler_o_sneicon"></a><code class="option">sneicon</code> option</h3></div></div></div><p>
      Stealth non-encrypted icon name.
    </p><p>
This option specifies the name of the icon to use for 
stealth, non-encrypted access points.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_netstumbler_o_snmac"></a><code class="option">snmac</code> option</h3></div></div></div><p>
      Shortname is MAC address.
    </p><p>
This option causes GPSBabel to use the MAC address as the short name for the
waypoint.  The unmodified SSID is included in the waypoint description.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_nima"></a>NIMA/GNIS Geographic Names File (nima)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>This is a CSV format from the National Imagery and Mapping
Agency.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_nmea"></a>NMEA 0183 sentences (nmea)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_nmea_o_snlen" title="snlen option">snlen</a>, <a class="link" href="#fmt_nmea_o_gprmc" title="gprmc option">gprmc</a>, <a class="link" href="#fmt_nmea_o_gpgga" title="gpgga option">gpgga</a>, <a class="link" href="#fmt_nmea_o_gpvtg" title="gpvtg option">gpvtg</a>, <a class="link" href="#fmt_nmea_o_gpgsa" title="gpgsa option">gpgsa</a>, <a class="link" href="#fmt_nmea_o_date" title="date option">date</a>, <a class="link" href="#fmt_nmea_o_get_posn" title="get_posn option">get_posn</a>, <a class="link" href="#fmt_nmea_o_pause" title="pause option">pause</a>, <a class="link" href="#fmt_nmea_o_append_positioning" title="append_positioning option">append_positioning</a>, <a class="link" href="#fmt_nmea_o_baud" title="baud option">baud</a>, <a class="link" href="#fmt_nmea_o_gisteq" title="gisteq option">gisteq</a>, <a class="link" href="#fmt_nmea_o_ignore_fix" title="ignore_fix option">ignore_fix</a> .</p><p> This format is the file representation of the NMEA 
(National Marine Electronics Association) 0183
log and waypoint format for GPS devices.  Some hardware and software
that work with NMEA-0183 formatted data include:
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>
  <a class="ulink" href="http://homepages.tig.com.au/~robk/datalogger.html" target="_top">GPS Data Logger</a>
</td><td>
  <a class="ulink" href="http://www.visualgps.net/VisualGPSce/default.htm" target="_top">VisualGPS</a>
</td><td>
  <a class="ulink" href="http://www.sparkfun.com/" target="_top">SparkFun GPS Datalogger</a>
</td></tr><tr><td>
  <a class="ulink" href="http://www.gpstm.com/eng/features_eng.htm " target="_top">GPS TrackMaker</a>
</td><td>
  <a class="ulink" href="http://www.gpsu.co.uk/" target="_top">GPS Utility</a>
</td><td>
  AMOD 3080 GPS
</td></tr><tr><td>
  <a class="ulink" href="http://www.gpsmaster.nl/ " target="_top">GPSMaster</a>
</td><td>
  <a class="ulink" href="http://www.kolumbus.fi/eino.uikkanen/geoconvgb/index.htm" target="_top">GeoConv</a>
</td><td>
  Wintec WPL-1000 GPS
</td></tr><tr><td>
  <a class="ulink" href="http://www.silcom.com/~rwhately/index.html" target="_top">NMEAlog</a>
</td><td>
  <a class="ulink" href="http://www.commlinx.com.au/GPS_recorder.htm" target="_top">CommLinx GPS recorder</a>
</td><td>
  Sony GPS_CS1
</td></tr></table><p>
This module also supports <a class="link" href="#tracking" title="Realtime tracking">realtime tracking</a> 
which allows realtime position reports from a GPS, such as one connected 
serially, over Bluetooth, or a USB module emulating a serial port, to be used
with selected output formats.  Just specify an input file that is the device
name such as COM1: for Windows or a device-dependent name like
/dev/cu.usbserial for Mac or /dev/ttyUSB0 for Linux.  (Note that serial 
device names vary on Mac and Linux.)
</p><p>
When used in <a class="link" href="#tracking" title="Realtime tracking">realtime tracking</a> mode, if
GPSBabel does not sense incoming NMEA sentences arriving from the port, it
will send Sirf "reset to NMEA" commands to the port at a variety of speeds
in an attempt to communicate with an attached GPS.   This lets devices
like the Microsoft GPS or Pharos GPS that are Sirf chips with an integrated
USB/Serial adapter work with this input format.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_nmea_o_snlen"></a><code class="option">snlen</code> option</h3></div></div></div><p>
      Max length of waypoint name to write.
    </p><p>
This option specifies the maximum length to be used for waypoint names in 
the GPWPL sentence.  Longer names will be shortened to no more than this 
length, but all waypoint names will remain unique.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_nmea_o_gprmc"></a><code class="option">gprmc</code> option</h3></div></div></div><p>
      Read/write GPRMC sentences.
    </p><p>
This option tells GPSBabel whether to read (on input) or write (on output) 
GPRMC sentences.  The default is to read or write GPRMC sentences.  To 
disable GPRMC sentences, specify <code class="option">gprmc=0</code>.
</p><p>
GPRMC sentences contain the "recommended mimimum" positional information, 
including date and time, heading, and velocity.  Note that they do not 
include altitude.  For altitude, you will have to include GPGGA sentences.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_nmea_o_gpgga"></a><code class="option">gpgga</code> option</h3></div></div></div><p>
      Read/write GPGGA sentences.
    </p><p>
This option tells GPSBabel whether to read (on input) or write (on output) 
GPGGA sentences.  The default is to read or write GPGGA sentences.  To 
disable GPGGA sentences, specify <code class="option">gpgga=0</code>.
</p><p>
GPGGA sentences contain the location and quality of the GPS position fix.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_nmea_o_gpvtg"></a><code class="option">gpvtg</code> option</h3></div></div></div><p>
      Read/write GPVTG sentences.
    </p><p>
This option tells GPSBabel whether to read (on input) or write (on output) 
GPVTG sentences.  The default is to read or write GPVTG sentences.  To 
disable GPVTG sentences, specify <code class="option">gpvtg=0</code>.
</p><p>
GPVTG sentences contain information about the heading and the speed at the
time of the fix.  They do not contain any location information; for that 
you will need either or both of GPGGA or GPRMC.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_nmea_o_gpgsa"></a><code class="option">gpgsa</code> option</h3></div></div></div><p>
      Read/write GPGSA sentences.
    </p><p>
This option tells GPSBabel whether to read (on input) or write (on output) 
GPGSA sentences.  The default is to read or write GPGSA sentences.  To 
disable GPGSA sentences, specify <code class="option">gpgsa=0</code>.
</p><p>
GPGSA sentences contain information on the quality of the positional fix
and the individual satellites from which it was derived.  However, GPSBabel
neither reads nor writes the individual satellite data.  On input, the 
satellite fields are ignored and on output they are left blank.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_nmea_o_date"></a><code class="option">date</code> option</h3></div></div></div><p>
      Complete date-free tracks with given date (YYYYMMDD)..
    </p><p>
On input, track points with times but no dates will have this date applied.  
</p><p>
This is necessary because some NMEA sentences contain times but no dates.  If
this option is not specified and the date cannot be determined from one or 
more of the available NMEA sentences, the tracks will be discarded.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_nmea_o_get_posn"></a><code class="option">get_posn</code> option</h3></div></div></div><p>
      Return current position as a waypoint.
    </p><p>This options, when specified, returns the current position as a single
waypoint.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_nmea_o_pause"></a><code class="option">pause</code> option</h3></div></div></div><p>
      Decimal seconds to pause between groups of strings.
    </p><p>
This option tells GPSBabel to pause between individual track records when
used on output.  This may be used with appropriate external software or 
hardware to simulate a GPS receiver for testing purposes.  On Unix, for
example, you may use a named pipe to feed the output from GPSBabel to gpsd.
</p><p>
If a value for this option is specified, it is in seconds and it may be
either a whole number of seconds or a fraction (e.g. 0.5 for a 1/2 second
pause between trackpoints.)
</p><p>
If this option is specified without a value, the time between adjacent 
trackpoints will be computed and used for the length of the pause.  That is,
if your trackpoints are 5 seconds apart, GPSBabel will pause 5 seconds 
between trackpoints.
</p><p>
Note that very long tracks may be subject to clock drift, as GPSBabel does 
not take into account the amount of time it may take to write the NMEA 
sentences.  Also, there is no guarantee that it will pause for exactly the
specified number of seconds between samples; different operating systems 
will allow greater or lesser precision for timers, so actual precision may
be as much as plus or minus 100 milliseconds.
</p><p>
If you are using this option with compressed or simplified tracks from 
your handheld GPS receiver, you might find the 
<a class="link" href="#filter_interpolate" title="Interpolate between trackpoints (interpolate)">interpolate</a> filter useful.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_nmea_o_append_positioning"></a><code class="option">append_positioning</code> option</h3></div></div></div><p>
      Append realtime positioning data to the output file instead of truncating.
    </p><p>
	When writing NMEA realtime positioning data, append to the 
	output file instead of truncating it on each successive position
	fix.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_nmea_o_baud"></a><code class="option">baud</code> option</h3></div></div></div><p>
      Speed in bits per second of serial port (baud=4800).
    </p><p>
To the "nmea" module, the "baud" option specifies the baud rate of the
serial connection when used with the real-time tracking option.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_nmea_o_gisteq"></a><code class="option">gisteq</code> option</h3></div></div></div><p>
      Write tracks for Gisteq Phototracker.
    </p><p>
  This option writes the Gisteq format - which has the extension of .GPS - 
  to allow third-party GPS hardware with the Gisteq PhotoTrackr software.  
</p><p>
  The Gisteq PhotoTrackr is a GPS data logger hardware and software package
  that allows one to easily record the locations of where the user has taken
  photos.  The PhotoTrackr software works by comparing EXIF timestamps in
  digital photos with the timestamps in the tracking data.  In doing so, the
  software plots the locations of the photos using Google Maps.  The logging
  format used by the Gisteq hardware is very close to NMEA format, but with a
  few small quirks.  
</p><p>
More information can be found at the 
<a class="ulink" href="http://www.gisteq.com/" target="_top">Gisteq</a> site.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_nmea_o_ignore_fix"></a><code class="option">ignore_fix</code> option</h3></div></div></div><p>
      Accept position fixes in gpgga marked invalid.
    </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_lmx"></a>Nokia Landmark Exchange (lmx)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_lmx_o_binary" title="binary option">binary</a> .</p><p> 
This format supports
<a class="ulink" href="http://sw.nokia.com/id/9001c8de-c19e-41a0-87d3-5be4297e4d4c/S60_Platform_Landmarks_Exchange_Specification_v1_0_en.pdf" target="_top">
Nokia Landmark Exchange (LMX) files</a> used by several Nokia phones.
GPSBabel supports the traditional XML format for reading and writing. The
compressed binary format (WBXML) can be written, but most current Nokia phones
do not support it (confirmed with N82 and N95).
</p><p>
With this format, landmarks can be imported into the landmark store of the
mobile phone. This landmark store is then used to display them on a map with
several applications. The most common ones are the pre-installed Ovi Maps (or
its predecessor Nokia Maps) and Google Maps Mobile.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_lmx_o_binary"></a><code class="option">binary</code> option</h3></div></div></div><p>
      Compact binary representation.
    </p><p>
This option specifies if you want to write the compressed binary format (WBXML)
instead of the XML format. However, most current Nokia phones do only support
the XML format (confirmed with N82 and N95).
</p><p>
This option has no effect when used for input, only reading the traditional XML
format is supported.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_osm"></a>OpenStreetMap data files (osm)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_osm_o_tag" title="tag option">tag</a>, <a class="link" href="#fmt_osm_o_tagnd" title="tagnd option">tagnd</a>, <a class="link" href="#fmt_osm_o_created_by" title="created_by option">created_by</a> .</p><p>
  This format is used to exchange data with the <a class="ulink" href="http://www.openstreetmap.org" target="_top">OpenStreetMap</a> project. 
  The main goal of this collaborative project is to create free editable maps.
</p><p>
  These data files are XML based. Every GPS element (way or node) described by the files has a unique
  number as identifier. When we write OSM data files and don't know something about the id's,
  negative numbers will be used as identifier. This has been tested with <a class="ulink" href="http://wiki.openstreetmap.org/index.php/JOSM" target="_top">JOSM</a>.
</p><p>
  Because the resulting timestamps of OSM ways differ from real GPS tracks, 
  we read OSM ways into routes. On the output side we write all available routes and tracks into the osm target file.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_osm_o_tag"></a><code class="option">tag</code> option</h3></div></div></div><p>
      Write additional way tag key/value pairs.
    </p><p>
  With this option you can preset OSM <a class="ulink" href="http://wiki.openstreetmap.org/index.php/Map_Features" target="_top">features</a> (tags) on all exported ways.
</p><p>
  <strong class="userinput"><code>gpsbabel -i gdb -f ways.gdb -o osm,tag="highway:motorway" -F ways.osm</code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_osm_o_tagnd"></a><code class="option">tagnd</code> option</h3></div></div></div><p>
      Write additional node tag key/value pairs.
    </p><p>
  With this option you can preset OSM <a class="ulink" href="http://wiki.openstreetmap.org/index.php/Map_Features" target="_top">features</a> (tags) on every written nodes.
</p><p>
  <strong class="userinput"><code>gpsbabel -i gdb -f nodes.gdb -o osm,tagnd="amenity:pub;building:yes" -F nodes.osm</code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_osm_o_created_by"></a><code class="option">created_by</code> option</h3></div></div></div><p>
      Use this value as custom created_by value.
    </p><p> Use this value as custom created_by value in an OSM file.</p><p>
With this option, the given string is added as the 'created_by' field in 
all the created nodes and ways.
</p><p>
<strong class="userinput"><code>
gpsbabel -i INTYPE -f INFILE -o osm,created_by=somestring -F out.osm
</code></strong>
</p><p>
  If an empty string is given, the 'created_by' tag is omitted altogether.
</p><p>
<strong class="userinput"><code>
gpsbabel -i INTYPE -f INFILE -o osm,created_by= -F out.osm
</code></strong>
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_ozi"></a>OziExplorer (ozi)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_ozi_o_pack" title="pack option">pack</a>, <a class="link" href="#fmt_ozi_o_snlen" title="snlen option">snlen</a>, <a class="link" href="#fmt_ozi_o_snwhite" title="snwhite option">snwhite</a>, <a class="link" href="#fmt_ozi_o_snupper" title="snupper option">snupper</a>, <a class="link" href="#fmt_ozi_o_snunique" title="snunique option">snunique</a>, <a class="link" href="#fmt_ozi_o_wptfgcolor" title="wptfgcolor option">wptfgcolor</a>, <a class="link" href="#fmt_ozi_o_wptbgcolor" title="wptbgcolor option">wptbgcolor</a>, <a class="link" href="#fmt_ozi_o_proximity" title="proximity option">proximity</a>, <a class="link" href="#fmt_ozi_o_altunit" title="altunit option">altunit</a>, <a class="link" href="#fmt_ozi_o_proxunit" title="proxunit option">proxunit</a> .</p><p>
  OziExplorer Waypoint Format - Another CSV format file.
  Tested against OziExplorer v 3.90.3a / Shareware. Contributed by Alex Mottram
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_ozi_o_pack"></a><code class="option">pack</code> option</h3></div></div></div><p>
      Write all tracks into one file.
    </p><p>
   In normal case GPSBabel creates for each track a separate file (track.plt, track-1.plt, ...). 
   With this option all tracks will be written into one file. A '1' in the third field of the
   trackpoint record signals the beginning of a new track.
</p><p>
  <strong class="userinput"><code>
    gpsbabel -i gpx -f tracks.gpx -o ozi,pack -F track
  </code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_ozi_o_snlen"></a><code class="option">snlen</code> option</h3></div></div></div><p>
      Max synthesized shortname length.
    </p><p>
  This option allows you to specify the length of waypoint names written to this format when used with the <code class="option">-s</code> option.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_ozi_o_snwhite"></a><code class="option">snwhite</code> option</h3></div></div></div><p>
      Allow whitespace synth. shortnames.
    </p><p>
  This option forces waypoint names generated with <code class="option"> -s </code> to allow whitespace in the names.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_ozi_o_snupper"></a><code class="option">snupper</code> option</h3></div></div></div><p>
      UPPERCASE synth. shortnames.
    </p><p>
  When specified, this option will force generated shortnames to be in all uppercase letters.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_ozi_o_snunique"></a><code class="option">snunique</code> option</h3></div></div></div><p>
      Make synth. shortnames unique.
    </p><p>
  When specified, this option will force the generated waypoint names to be unique.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_ozi_o_wptfgcolor"></a><code class="option">wptfgcolor</code> option</h3></div></div></div><p>
      Waypoint foreground color.
    </p><p>
  This option allows you to specify a foreground color of a waypoint.  You can specify it as either a decimal number or one of the standard web colors.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_ozi_o_wptbgcolor"></a><code class="option">wptbgcolor</code> option</h3></div></div></div><p>
      Waypoint background color.
    </p><p>
  This option allows you to specify a background color of a waypoint.  You can specify it as either a decimal number or one of the standard web colors.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_ozi_o_proximity"></a><code class="option">proximity</code> option</h3></div></div></div><p>
      Proximity distance.
    </p><p>
  This option, specified in meters, allows you to set the proximity of 
written waypoints.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_ozi_o_altunit"></a><code class="option">altunit</code> option</h3></div></div></div><p>
      Unit used in altitude values.
    </p><p>
  By default the ozi module uses feet as altitude unit. With this option you can specify also 'Meters' (m)
  as unit for altitude values.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_ozi_o_proxunit"></a><code class="option">proxunit</code> option</h3></div></div></div><p>
      Unit used in proximity values.
    </p><p>
  By default the proximity values are handled in meters. With this option you can now specify (m)iles,
  (k)ilometers or (n)autical miles as the units for proximity when reading or writing ozi files.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_pocketfms_bc"></a>PocketFMS breadcrumbs (pocketfms_bc)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
   This format provides support for binary breadcrumb files from <a class="ulink" href="http://www.pocketfms.com" target="_top">PocketFMS</a>. The default filename is GPS followed by the timestamp with no file extension. 
</p><p>
   PocketFMS breadcrumbs files contain track information. That is latitude, longitude, altitude, speed, course, variation, separation, GPS error, fix type and timestamp. With exception of separation all info get processed by GPSBabel in both in and out direction.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_pocketfms_fp"></a>PocketFMS flightplan (.xml) (pocketfms_fp)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read routes
        </p></li></ul></div><p>
   This format provides support for XML flightplans from <a class="ulink" href="http://www.pocketfms.com" target="_top">PocketFMS</a>.  
</p><p>
   PocketFMS XML flightplans contain route and waypoint information and much more flight planning info as airspaces, aircraft performance, fuel management etc. This format cannot be read by PocketFMS. Hence GPSBabel supports only input of route and waypoint information.
</p><p>
    The PocketFMS flightplan converter take into account the -w waypoint flag. If set then additional waypoints are stored to the route point and path information. 
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_pocketfms_wp"></a>PocketFMS waypoints (.txt) (pocketfms_wp)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
   This format provides support for the <a class="ulink" href="http://www.pocketfms.com" target="_top">PocketFMS</a> user waypoints text file. 
</p><p>
   PocketFMS waypoint text files contain one waypoint per line. Any waypoint has name, latitude and longitude, separated by space. Latitude and longitude are either decimal degrees or degrees°minutes'seconds'' triples. For details see the PocketFMS help file. You can find more information at the <a class="ulink" href="http://www.pocketfms.com/phpBB3/" target="_top">PocketFMS forum</a>. 
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_raymarine"></a>Raymarine Waypoint File (.rwf) (raymarine)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_raymarine_o_location" title="location option">location</a> .</p><p>
  This format supports the "Raymarine Waypoint File" format (.rwf).
  More information to Raymarine you'll find at their <a class="ulink" href="http://www.raymarine.com" target="_top">homepage</a>.
</p><p>
  Known limits: max. 16 characters for waypoint names and max. 50 waypoints per route.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_raymarine_o_location"></a><code class="option">location</code> option</h3></div></div></div><p>
      Default location.
    </p><p>
   With this option you can specify the name of the folder
   where the waypoints are placed.
</p><p>
   This name is also limited to 16 characters.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_ricoh"></a>Ricoh GPS Log File (ricoh)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>This is the format for the Ricoh 500SE GPS logging camera.
</p><p>
 This camera creates log files on the SD card in a folder name "GPSLOG" that 
  are named "YYMMDDNN.LOG" wher NN increments from 00 through 99.  The camera 
  appends new tracks into the current file, hence the "new track" field. When 
  the current file reaches about 500K, NN increments and logging continues into 
  the next file. Therefore, there may be multiple tracks in each log 
  file, and tracks may span one or more files. 
</p><p>
  GPSBabel will recognize the "new track" field and will generate a new track,
  so if you specify multiple files in the correct order, your tracks will be
  automatically split sensibly.  
</p><p>
For additional tips, see the
  <a class="ulink" href="http://wiki.openstreetmap.org/wiki/Ricoh_500SE_GPS_Log" target="_top">OpenStreetMap page on Ricoh 500SE</a>.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_cup"></a>See You flight analysis data (cup)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
  This format supports flight analysis data from the 
	<a class="ulink" href="http://www.seeyou.ws/" target="_top">See You</a> 
  program.
</p><p>
  Position information is preserved, but the aviation-specific 
  information such as runway length and airport frequency, are
  written as blanks and ignored on read.
</p><p>
  Tasks are not supported.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_skyforce"></a>Skymap / KMD150 ascii files (skyforce)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>
   This format provides support for ascii files from Skyforce PC interface for 
   Skymap IIIC, Skymap II (Version 4) and KMD 150. Our module was developed 
   from their interface description.
</p><p>
   Each kind of our basic GPS data (waypoints, routes, and tracks) is 
   stored in a separate file. Therefore you need three steps to 
   convert a complex format like GPX or GDB into skyforce.
   <strong class="userinput"><code>
      gpsbabel -i gpx -f file.gpx -o skyforce -w -F waypoints.txt -r -F routes.txt -t -F tracks.txt
   </code></strong>
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_skytraq"></a>SkyTraq Venus based loggers (download) (skytraq)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_skytraq_o_erase" title="erase option">erase</a>, <a class="link" href="#fmt_skytraq_o_targetlocation" title="targetlocation option">targetlocation</a>, <a class="link" href="#fmt_skytraq_o_configlog" title="configlog option">configlog</a>, <a class="link" href="#fmt_skytraq_o_baud" title="baud option">baud</a>, <a class="link" href="#fmt_skytraq_o_initbaud" title="initbaud option">initbaud</a>, <a class="link" href="#fmt_skytraq_o_read-at-once" title="read-at-once option">read-at-once</a>, <a class="link" href="#fmt_skytraq_o_first-sector" title="first-sector option">first-sector</a>, <a class="link" href="#fmt_skytraq_o_last-sector" title="last-sector option">last-sector</a>, <a class="link" href="#fmt_skytraq_o_dump-file" title="dump-file option">dump-file</a>, <a class="link" href="#fmt_skytraq_o_no-output" title="no-output option">no-output</a> .</p><p>Serial download protocol for GPS data loggers based on Skytraq Venus 5 and Venus 6 chipsets.
This chipset is used by a number of devices from different manufacturers.
If your logger came with the Windows software iTravelTech GPS Photo Tagger, chances are that you can
use this format to read its memory.</p><p>Following a list of devices which should be supported by this module
(Note that not all of them have actually been tested, so if you can confirm that additional models work, please mail the gpsbabel-misc group with your success, tips, and any pertinent links for your model.):</p><div class="table"><a id="skytraq_devices"></a><div class="table-title">Table 3.7. Devices supported by skytraq module</div><div class="table-contents"><table summary="Devices supported by skytraq module" border="1"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Manufacturer</th><th>Model</th><th>USB (baud)</th><th>Bluetooth (baud)</th></tr></thead><tbody><tr><td>SJA</td><td>"3-in-1" GPS logger</td><td>up to 230400</td><td>9600</td></tr><tr><td>Navilock</td><td>BT-455PDL</td><td>untested</td><td>untested</td></tr><tr><td>Polaris</td><td>Travel Honey</td><td>up to 230400</td><td>9600</td></tr><tr><td>Pearl Diffusion</td><td>Keymate STV-5</td><td>untested</td><td>untested</td></tr><tr><td>Canmore</td><td>GT-750F</td><td>untested</td><td>untested</td></tr><tr><td>Adapt Mobile</td><td>Keychain Pro</td><td>untested</td><td>untested</td></tr><tr><td>Adapt Mobile </td><td>Keychain Pro</td><td>9600</td><td>9600</td></tr></tbody></table></div></div><br class="table-break" /><div class="example"><a id="skytraq-on-linux"></a><div class="example-title">Example 3.29. Command showing skytraq download of tracks and erasing the logger on Linux</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i skytraq,erase -f /dev/ttyUSB0 -o gpx -F out.gpx</code></strong></p></div></div><br class="example-break" /><div class="example"><a id="skytraq-erase"></a><div class="example-title">Example 3.30. Command showing skytraq erasing the logger without download on Linux</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i skytraq,erase,no-output -f /dev/ttyUSB0</code></strong></p></div></div><br class="example-break" /><p>If available, reading the logger using bluetooth should also work. However, many devices support only one
specific baud rate over bluetooth, e.g. 9600. In that case you should use the option <strong class="userinput"><code>baud=0</code></strong>
to tell GPSBabel to use that default baud rate:</p><div class="example"><a id="skytraq-on-linux-bt"></a><div class="example-title">Example 3.31. Command showing skytraq download tracks via bluetooth on Linux</div><div class="example-contents"><p><strong class="userinput"><code>rfcomm bind 0 &lt;bdaddr&gt;</code></strong></p><p><strong class="userinput"><code>gpsbabel -i skytraq,baud=0 -f /dev/rfcomm0 -o gpx -F out.gpx</code></strong></p></div></div><br class="example-break" /><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_skytraq_o_erase"></a><code class="option">erase</code> option</h3></div></div></div><p>
      Erase device data after download.
    </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_skytraq_o_targetlocation"></a><code class="option">targetlocation</code> option</h3></div></div></div><p>
      Set location finder target location as lat,lng.
    </p><p>
  The device provides a location finder built from eight LEDs and can use
  those LEDs to guide you to a location.  You can set the target location
  with the 'targetlocation' option.  Use ':' as the delimiter between latitude
  and longitude. Note that GPSBabel terminates after writing the location info
  to the device, i.e. no logging data will be read from it.
</p><div class="example"><a id="skytraq-targetlocation"></a><div class="example-title">Example 3.32. Set the target location of the Skytraq location finder</div><div class="example-contents"><p>
       <strong class="userinput"><code>gpsbabel -i skytraq,targetlocation=12.34:-56.78 -f /dev/ttyUSB
0 -o unicsv -F -</code></strong>
  </p><p>
       Sets latitude and longitude of the location finder to N12.34 and 
	W56.78 respectively. 
       The arrows on the device will point you to this location as soon as 
	it has a satellite fix.
 </p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_skytraq_o_configlog"></a><code class="option">configlog</code> option</h3></div></div></div><p>
      Configure logging parameter as tmin:tmax:dmin:dmax.
    </p><p>
  Set the logging configuration as tmin:tmax:dmin:dmax.
  Here tmin and tmax are in seconds, and dmin and dmax in meters.
  With dt = time since last log, dx = distance since last log,
  and v the current speed, the device logs if
</p><p>
   (dt &gt; tmin and dx &gt;= dmin and v &gt;= vmin) or dt &gt; tmax or dx &gt; dmax or v &gt; vmax
</p><p>
   If you use this option, vmin is fixed at 0 and vmax at 65535 km/h.
</p><p>
   Example. Set the device to log every 6 seconds (or 10km, whichever
   happens first!)
</p><div class="example"><a id="skytraq-configulog"></a><div class="example-title">Example 3.33. Set the logging parameters for Skytraq device</div><div class="example-contents"><p>
<strong class="userinput"><code>
   gpsbabel -i skytraq,configlog=6:3600:0:10000 -f /dev/ttyUSB0
</code></strong>
</p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_skytraq_o_baud"></a><code class="option">baud</code> option</h3></div></div></div><p>
      Baud rate used for download.
    </p><p>The following baud rates can be used: 4800, 9600, 19200, 38400, 57600, 115200, 230400.
Note that your logger might not support all of them (especially 230400 which isn't documented
in the chipset manual, though there are known devices that are capable of this speed).</p><p>If <strong class="userinput"><code>baud=0</code></strong> (zero) download takes place at the baud rate the
device is currently set to. This is especially useful for Bluetooth connections since they
often don't allow changing the baud rate.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_skytraq_o_initbaud"></a><code class="option">initbaud</code> option</h3></div></div></div><p>
      Baud rate used to init device (0=autodetect).
    </p><p>The "initbaud" option might be helpful if autodetection fails or takes too long. With this option you
can tell GPSBabel the baud rate the device is currently set to. In contrast, the option "baud" specifies
the rate at which the actual download should take place. If it is different than "initbaud" (or the autodetected
rate, if initbaud wasn't given), the initial setting will be restored after finishing the download.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_skytraq_o_read-at-once"></a><code class="option">read-at-once</code> option</h3></div></div></div><p>
      Number of sectors to read at once (0=use single sector mode).
    </p><p>If <strong class="userinput"><code>read-at-once</code></strong> &gt;= 1, batch mode is enabled with that many sectors being read at a time.
A value of zero disables batch mode and switches to single read mode. Not all devices support batch mode; in that case
gpsbabel automatically switches to single read mode.</p><p>Under normal circumstances, the larger this number the faster the transfer.
Reducing <strong class="userinput"><code>read-at-once</code></strong> or even switching to single sector mode might help when you get
transmission errors/aborts.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_skytraq_o_first-sector"></a><code class="option">first-sector</code> option</h3></div></div></div><p>
      First sector to be read from the device.
    </p><p>The logger's memory is organized in sectors, serially numbered starting at 0. Each sector takes 4096 bytes of data.
Typical devices hold about 250 sectors. The memory is always filled from sector 0 on, until it is full or the device being
erased again by the user.</p><p>Normally you can safely omit this option. However, it might be useful to read data from erased devices: we observed
that on erase, only the first two sectors are actually cleared. The following example shows how to read the remaining data:
</p><div class="example"><a id="skytraq-restore-erased"></a><div class="example-title">Example 3.34. Command showing how to read data from an erased device</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i skytraq,first-sector=2 -f /dev/ttyUSB0 -o gpx -F out.gpx</code></strong></p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_skytraq_o_last-sector"></a><code class="option">last-sector</code> option</h3></div></div></div><p>
      Last sector to be read from the device (-1: smart read everything).
    </p><p>A value of -1 (the default) enables automatic mode, i.e. reading is stopped when an empty sector is
encountered.
We observed that sometimes the device doesn't report the correct number of used sectors, which confuses the Windows
software, so that it might not get all trackpoints.
In contrast, our algorithm ensures that everything is being read (please report if it doesn't work for you).</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_skytraq_o_dump-file"></a><code class="option">dump-file</code> option</h3></div></div></div><p>
      Dump raw data to this file.
    </p><p>Writes raw data as it is read from the logger to the file given as this option's argument
(additional to decoding it as usual). The resulting binary files can be read and decoded by the skytraq-bin format.
Mainly useful for debugging/development purposes.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_skytraq_o_no-output"></a><code class="option">no-output</code> option</h3></div></div></div><p>
      Disable output (useful with erase).
    </p><p>If this option is given, no GPS log data will be read from the device
(unless "dump-file" is given too; in that case only decoding will be disabled).</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_skytraq-bin"></a>SkyTraq Venus based loggers Binary File Format (skytraq-bin)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_skytraq-bin_o_first-sector" title="first-sector option">first-sector</a>, <a class="link" href="#fmt_skytraq-bin_o_last-sector" title="last-sector option">last-sector</a> .</p><p>Reads the binary format of GPS data loggers based on Skytraq Venus 5 and Venus 6 chipsets.
This can be used to read raw binary files created with the "dump-file" option of the skytraq format.
Mainly useful for debugging/development purposes.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_skytraq-bin_o_first-sector"></a><code class="option">first-sector</code> option</h3></div></div></div><p>
      First sector to be read from the file.
    </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_skytraq-bin_o_last-sector"></a><code class="option">last-sector</code> option</h3></div></div></div><p>
      Last sector to be read from the file (-1: read till empty sector).
    </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_subrip"></a>SubRip subtitles for video mapping (.srt) (subrip)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          write tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_subrip_o_video_time" title="video_time option">video_time</a>, <a class="link" href="#fmt_subrip_o_gps_time" title="gps_time option">gps_time</a>, <a class="link" href="#fmt_subrip_o_gps_date" title="gps_date option">gps_date</a> .</p><p>
		This is a write-only format for geotagging videos. It is used for
		videomapping, i.e. filming a trip while creating a GPS trace.
		It will produce a subtitle file in SubRip (.srt) format.
	</p><p>
		Unless the video and the GPS trace start at exactly the same time, you
		will need to synchronize both. For this purpose, film the display of
		your GPS receiver (or any other device) showing GPS time. (Important:
		you need precise GPS time for this; local time, especially from an
		inaccurate clock, will not do for this.) 
	</p><p>
		Determine the position in the video at which the GPS time is visible
		(in hours, minutes and seconds from the beginning of the video) and
		the GPS date and time shown. Specify these as command line options; you
		will need to do this once for each video file.
	</p><p>
		To use these files, choose the same name as for the associated video,
		changing just the extension to .srt, and place the srt file in the same
		directory as the video. Open the video in a media player and the GPS
		coordinates will be shown as subtitles (tested on VLC, your mileage may
		vary).
	</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_subrip_o_video_time"></a><code class="option">video_time</code> option</h3></div></div></div><p>
      Video position for which exact GPS time is known (hhmmss, default is 0:00:00).
    </p><p>
	Video position (relative to beginning of video) for which the corresponding
	GPS timestamp is known.
</p><p>
	Format is hhmmss. If omitted, 0:00:00 (beginning of video) is assumed.
</p><p>
	The GPS timestamp can be set with the <code class="option">gps_time</code> and 
	<code class="option">gps_date</code> options.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_subrip_o_gps_time"></a><code class="option">gps_time</code> option</h3></div></div></div><p>
      GPS time at position video_time (hhmmss, default is first timestamp of track).
    </p><p>
	The time part of the GPS timestamp which corresponds to a known position 
	in the video.
</p><p>
	Format is hhmmss. This option must be used together with 
	<code class="option">gps_date</code>; if one or both are missing, the timestamp of the
	first GPS trackpoint is used.
</p><p>
	The video position to which the timestamp corresponds can be set with the 
	<code class="option">video_time</code> option.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_subrip_o_gps_date"></a><code class="option">gps_date</code> option</h3></div></div></div><p>
      GPS date at position video_time (hhmmss, default is first timestamp of track).
    </p><p>
	The date part of the GPS timestamp which corresponds to a known position 
	in the video.
</p><p>
	Format is yyyymmdd. This option must be used together with 
	<code class="option">gps_time</code>; if one or both are missing, the timestamp of the 
	first GPS trackpoint is used.
</p><p>
	The video position to which the timestamp corresponds can be set with the 
	<code class="option">video_time</code> option.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_stmsdf"></a>Suunto Trek Manager (STM) .sdf files (stmsdf)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_stmsdf_o_index" title="index option">index</a> .</p><p>
	This format supports the .sdf files from the Suunto product family
	'Suunto Trek Manager', 'Suunto Ski Manager' and 'Suunto Sail Manager'.
	The contents of the sdf file depends on the used product and can
	be one route or one track. Thats why when you want to use sdf on the
	output side you have to use the
	<a class="link" href="#Route_And_Track_Modes" title="Route and Track Modes">-r OR the -t</a> option. This will tell
	GPSBabel which type of data should be written.
</p><p>
	Currently we can read the following file types:
	</p><table border="0" summary="Simple list" class="simplelist"><tr><td>4 = M9 TrackLog</td></tr><tr><td>5 = Route</td></tr><tr><td>28 = X9 TrackLog</td></tr></table><p>
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f some-routes.gpx -r -o stmsdf,index=3 -F single-route.sdf</code></strong></p><p>
	<a class="ulink" href="http://www.suunto.fi" target="_top">Suunto Website</a>
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_stmsdf_o_index"></a><code class="option">index</code> option</h3></div></div></div><p>
      Index of route (if more than one in source).
    </p><p>
	Convert route number 'index' from source into sdf format.
</p><p>
	We have a lot of more expressive formats thats support more than one route.
	At this place sdf files are limited to only one single route. With option index
	you can specify which route from source should be converted.
</p><p>
	Our default index is 1.
</p><p>
	This example will convert route number two and three into separate sdf files:
</p><p><strong class="userinput"><code> gpsbabel -i gdb -f routes.gdb -r -o stmsdf,index=2 -F route-one.sdf -r -o stmsdf,index=3 -F route-three.sdf </code></strong></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_stmwpp"></a>Suunto Trek Manager (STM) WaypointPlus files (stmwpp)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_stmwpp_o_index" title="index option">index</a> .</p><p>
This format supports the Suunto Trek Manager (STM) WaypointPlus format.
This is a simple format with coordinates and a time stamp.  Route points 
also have a short name.  A single file may only contain one route or one
track.
</p><p>
<a class="ulink" href="http://www.suunto.fi" target="_top">Suunto Website</a>
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_stmwpp_o_index"></a><code class="option">index</code> option</h3></div></div></div><p>
      Index of route/track to write (if more than one in source).
    </p><p>
Because the format supports only one route or track, this option may be used 
on output to select a single route or track from a collection of routes and
tracks read from a more expressive format.  If you have, say, a 
<a class="link" href="#fmt_gpx" title="GPX XML (gpx)">gpx</a> file that contains three routes, you may
use this option to write them one at a time to individual files.
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f routes.gpx -o stmwpp,index=1 -F route1.txt -o stmwpp,index=2 -F route2.txt -o stmwpp,index=3 -F route3.txt</code></strong></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_xol"></a>Swiss Map 25/50/100 (.xol) (xol)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>
   This module reads and writes xml based (.xol) files used by
   <a class="ulink" href="http://www.swisstopo.ch" target="_top">Swiss Map</a> software.
</p><p>
   These files uses the "Swiss national grid" (CS-1903) to store coordinates.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_openoffice"></a>Tab delimited fields useful for OpenOffice, Ploticus etc. (openoffice)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p> 
	Tab separated export-all (except geocaching data) file
	format.  Intended to serve as source for number-processing
	applications like OpenOffice, Ploticus and others. Tab was chosen as
	delimiter because it is a) supported by both OpenOffice and Ploticus
	and b) is not ',', so you can use <strong class="userinput"><code>sed -i
	"s/./,/g" &lt;x&gt;.csv'</code></strong> to adapt it to locales where ',' is
	used as decimal seperator.  Contributed by Tobias Minich.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_teletype"></a>Teletype [ Get Jonathon Johnson to describe (teletype)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li></ul></div><p>
This format reads the files written by the <a class="ulink" href="http://teletype.com" target="_top">Teletype</a> GPS devices with the extension of ".way".
</p><p>
  It's not entirely clear exactly which Teletype products are supported or
  what versions write the format we read.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_text"></a>Textual Output (text)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          write waypoints
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_text_o_nosep" title="nosep option">nosep</a>, <a class="link" href="#fmt_text_o_encrypt" title="encrypt option">encrypt</a>, <a class="link" href="#fmt_text_o_logs" title="logs option">logs</a>, <a class="link" href="#fmt_text_o_degformat" title="degformat option">degformat</a>, <a class="link" href="#fmt_text_o_altunits" title="altunits option">altunits</a>, <a class="link" href="#fmt_text_o_splitoutput" title="splitoutput option">splitoutput</a> .</p><p> This is a simple human readable version of the data file,
handy for listings of any type of waypoint files.
</p><p> The following command line reads a GPX file with
Groundspeak extensions and writes a text file with encrypted hints:
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f 12345.gpx -o text,encrypt -F 12345.txt</code></strong></p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_text_o_nosep"></a><code class="option">nosep</code> option</h3></div></div></div><p>
      Suppress separator lines between waypoints.
    </p><p>
To suppress the dashed lines between waypoints, use this option.  
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_text_o_encrypt"></a><code class="option">encrypt</code> option</h3></div></div></div><p>
      Encrypt hints using ROT13.
    </p><p>
Use this option to encrypt hints from Groundspeak GPX files.  
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_text_o_logs"></a><code class="option">logs</code> option</h3></div></div></div><p>
      Include groundspeak logs if present.
    </p><p>
Use this option to include Groundspeak cache logs in the created document.  
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_text_o_degformat"></a><code class="option">degformat</code> option</h3></div></div></div><p>
      Degrees output as 'ddd', 'dmm'(default) or 'dms'.
    </p><p>
When GPSBabel writes coordinates, this option is consulted to see if it
should write decimal degrees ('ddd') decimal minutes ('dmm') or degrees,
minutes, seconds ('dms').  The default is 'dmm'.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_text_o_altunits"></a><code class="option">altunits</code> option</h3></div></div></div><p>
      Units for altitude (f)eet or (m)etres.
    </p><p>
This option should be 'f' if you want the altitude expressed in feet and
'm' for meters.  The default is 'f'.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_text_o_splitoutput"></a><code class="option">splitoutput</code> option</h3></div></div></div><p>
      Write each waypoint in a separate file.
    </p><p>
  Splits output into separate files for each waypoint by appending a
  decimal number to the output filename.
</p><div class="example"><a id="text_splitoutput"></a><div class="example-title">Example 3.35. Example for splitoutput option to text format</div><div class="example-contents"><p>
    If "MyPQ.gpx" contains five waypoints, 
	<strong class="userinput"><code>
	    gpsbabel -i gpx -f MyPocketQuery -o text,split -F blah
	</code></strong>
    will result in files named blah1 ... blah5, each containing info
    from one of those waypoints.
   </p></div></div><br class="example-break" /></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_tomtom_itn"></a>TomTom Itineraries (.itn) (tomtom_itn)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
   tomtom_itn can be used to read and write <a class="ulink" href="http://www.tomtom.com" target="_top">TomTom</a> Navigator Itineraries (Routes).
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_tomtom_itn_places"></a>TomTom Places Itineraries (.itn) (tomtom_itn_places)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_tomtom_asc"></a>TomTom POI file (.asc) (tomtom_asc)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>
This format is derived from the <a class="link" href="#fmt_xcsv" title="? Character Separated Values (xcsv)">xcsv</a>
format, so it has all of the same options as that format.
</p><p>
   With this format you can read and write <a class="ulink" href="http://www.tomtom.com" target="_top">TomTom</a>
   Points of Interest - POI (ascii) files.
   It is a simple text (csv) format with only latitude, longitude and a short name.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_tomtom"></a>TomTom POI file (.ov2) (tomtom)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p> This format can read and write <a class="ulink" href="http://www.tomtom.com" target="_top">TomTom</a> .ov2 (POI) files,
as used by the TomTom GO and TomTom Navigator.  It has been tested
with an original TomTom GO running version 5.00 of the TomTom
software.  There may be some records that confuse the input module -
if you have an example of such a record "in the wild", and you aren't
restricted from sharing it, we encourage you to post to the
gpsbabel-misc mailing list to contact a developer.</p><p> Note that in addition to the .ov2 file, you will need a
.bmp file for the icon.  It should be 22x22 and 16 colors, and have
the same name (not including the extension) as the .ov2 file.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_tmpro"></a>TopoMapPro Places File (tmpro)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>Reads and writes places files for
use in <a class="ulink" href="http://www.topomappro.com" target="_top">TopoMapPro places files</a>.  As this file
type can store links other than web links, anything that is not a http
url will be discarded.  Note that this does not do datum conversions,
so if your input file does not have WGS84/NZGD2000 data, your output
file won't either. Colour of waypoint icons defaults to red.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_dmtlog"></a>TrackLogs digital mapping (.trl) (dmtlog)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_dmtlog_o_index" title="index option">index</a> .</p><p>
	This format can be used to convert files from
	<a class="ulink" href="http://www.tracklogs.co.uk" target="_top">TrackLogs Digital Mapping</a>. The files 
	have extension .trl and can contain waypoints and tracks.
</p><p>
	We have seen three different types of this format. Two are binary 
	and one is an XML based format.  All three types are supported 
	by our reader.
</p><p>
Users should note that this format orders waypoints in reverse order within the file. If direction of travel is important to you, consider using the Reverse filter to retain waypoint order.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_dmtlog_o_index"></a><code class="option">index</code> option</h3></div></div></div><p>
      Index of track (if more than one in source).
    </p><p>
   Convert track number 'index' from source into dmtlog format.
</p><p>
   The known variants of Tracklog 'digital mapping' files supports only
   one track per file. If you have more than one track in source 
   (f.e MapSource and many others can do such heavy things), you 
   can specify which track should by used for the conversion. 
</p><p>
   The default index is 1 (the first track of a possible list of tracks).
</p><p>
   An example usage you can find at the <a class="link" href="#fmt_ignrando" title="IGN Rando track files (ignrando)">ignrando</a> format,
   which uses option <a class="link" href="#fmt_ignrando_o_index" title="index option">index</a> in same manner.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_tiger"></a>U.S. Census Bureau Tiger Mapping Service (tiger)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_tiger_o_nolabels" title="nolabels option">nolabels</a>, <a class="link" href="#fmt_tiger_o_genurl" title="genurl option">genurl</a>, <a class="link" href="#fmt_tiger_o_margin" title="margin option">margin</a>, <a class="link" href="#fmt_tiger_o_snlen" title="snlen option">snlen</a>, <a class="link" href="#fmt_tiger_o_oldthresh" title="oldthresh option">oldthresh</a>, <a class="link" href="#fmt_tiger_o_oldmarker" title="oldmarker option">oldmarker</a>, <a class="link" href="#fmt_tiger_o_newmarker" title="newmarker option">newmarker</a>, <a class="link" href="#fmt_tiger_o_suppresswhite" title="suppresswhite option">suppresswhite</a>, <a class="link" href="#fmt_tiger_o_unfoundmarker" title="unfoundmarker option">unfoundmarker</a>, <a class="link" href="#fmt_tiger_o_xpixels" title="xpixels option">xpixels</a>, <a class="link" href="#fmt_tiger_o_ypixels" title="ypixels option">ypixels</a>, <a class="link" href="#fmt_tiger_o_iconismarker" title="iconismarker option">iconismarker</a> .</p><p>The U.S. Census Bureau provides online mapping facilities.
This format is described at: <a class="ulink" href="http://tiger.census.gov/instruct.html" target="_top">tiger.census.gov</a>.
Do notice that this format is not the actual Tiger line mapping
records, but rather the interface to their online mapping
program.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_tiger_o_nolabels"></a><code class="option">nolabels</code> option</h3></div></div></div><p>
      Suppress labels on generated pins.
    </p><p>This option tells GPSBabel to not generate labels on the pins.   If
this is true, the description of the incoming waypoints are ignored and not
placed on the pins.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_tiger_o_genurl"></a><code class="option">genurl</code> option</h3></div></div></div><p>
      Generate file with lat/lon for centering map.
    </p><p>
genurl is a convenience option for generating the scaling parameters
when accessing the Tiger servers.  It will output the latitude, longitude,
height, and width parameters in a form suitable for use in the URL to generate
a map that will hold all the points to be displayed  and is suitably scaled
and centered.   
</p><p>For example:</p><p><strong class="userinput"><code>gpsbabel -i geo -f geocaching.loc -o tiger,genurl=tiger.ctr -F tiger.dat</code></strong></p><p>
may create tiger.ctr with
</p><pre class="screen">
lat=36.042108&amp;lon=-86.877408&amp;ht=0.161172&amp;wid=0.591771&amp;iwd=768&amp;iht=768</pre><p>

After uploading tiger.dat to a public server, a request to 
</p><pre class="screen"> http://tiger.census.gov/cgi-bin/mapgen?murl=$THATFILE$(cat tiger.ctr)</pre><p>
will return a gif file from the tiger server that's suitably scaled.

</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_tiger_o_margin"></a><code class="option">margin</code> option</h3></div></div></div><p>
      Margin for map.  Degrees or percentage.
    </p><p>This option specifies a margin around the maps for the genurl options.
The margin may be specified in either decimal degrees or as a 
percentage.</p><p>
This option is most useful for ensuring there is adequate space for
the label around the markers when generating automatically scaled maps.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_tiger_o_snlen"></a><code class="option">snlen</code> option</h3></div></div></div><p>
      Max shortname length when used with -s.
    </p><p>
The snlen option controls the maximum length of names generated by the '-s'
option.  It's particularly useful in Tiger maps to avoid the amount of clutter
generated by potentially lengthy labels on the markers.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_tiger_o_oldthresh"></a><code class="option">oldthresh</code> option</h3></div></div></div><p>
      Days after which points are considered old.
    </p><p>This options allows you to control the threshold in days between
whether a pin is considered "new" (and thus potentially governed by the
'newmarker' option) or "old" (and thus potentially governed by the 
'oldmarker' option).
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_tiger_o_oldmarker"></a><code class="option">oldmarker</code> option</h3></div></div></div><p>
      Marker type for old points.
    </p><p>This option specifies the pin to be used if a waypoint has a creation
time newer than 'oldthresh' days.</p><p>The default is "redpin".</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_tiger_o_newmarker"></a><code class="option">newmarker</code> option</h3></div></div></div><p>
      Marker type for new points.
    </p><p>This option specifies the pin to be used if a waypoint has a creation
time older than 'oldthresh' days.</p><p>The default is "greenpin".</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_tiger_o_suppresswhite"></a><code class="option">suppresswhite</code> option</h3></div></div></div><p>
      Suppress whitespace in generated shortnames.
    </p><p>
When set, this options tells the '-s' smartname generator to not allow 
any spaces in the labels generated for markers.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_tiger_o_unfoundmarker"></a><code class="option">unfoundmarker</code> option</h3></div></div></div><p>
      Marker type for unfound points.
    </p><p> 
  Specifies the icon type for unfound geocaches.  Default is "bluepin".
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_tiger_o_xpixels"></a><code class="option">xpixels</code> option</h3></div></div></div><p>
      Width in pixels of map.
    </p><p>The xpixels argument lets you specify the number of pixels to be
generated by the Tiger server along the horizontal axis when using the 
'genurl' option.  </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_tiger_o_ypixels"></a><code class="option">ypixels</code> option</h3></div></div></div><p>
      Height in pixels of map.
    </p><p>The ypixels argument lets you specify the number of pixels to be
generated by the Tiger server along the vertical axis when using the
'genurl' option.  </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_tiger_o_iconismarker"></a><code class="option">iconismarker</code> option</h3></div></div></div><p>
      The icon description is already the marker.
    </p><p> This options signifies that the icon in the incoming format is to be used
without change in the generated Tiger output file.  Without this option,
GPSBabel tries to color pins based on their creation time and certain 
Geocaching traits when available.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_unicsv"></a>Universal csv with field structure in first line (unicsv)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_unicsv_o_datum" title="datum option">datum</a>, <a class="link" href="#fmt_unicsv_o_grid" title="grid option">grid</a>, <a class="link" href="#fmt_unicsv_o_utc" title="utc option">utc</a>, <a class="link" href="#fmt_unicsv_o_format" title="format option">format</a>, <a class="link" href="#fmt_unicsv_o_filename" title="filename option">filename</a> .</p><p>
   Unicsv examines the first line of a file to determine the field
   order and field separator in that file.   On write, it tries to 
   figure out what data it has and writes headers and all the data it can.
</p><p>
   If the first line contains any tabs, the data lines are assumed
   to be tab separated.   Otherwise the fields are assumed to be
   separated by commas.
</p><p>
   The list of keywords include:
   </p><pre class="screen">
      alt =      Elevation (in meters) of the point. Add "ft" or "feet" for feet.
      arch =     <a class="link" href="#style_def_isarchived" title="GEOCACHE_ISARCHIVED">Geocache archived flag</a>
      avail =    <a class="link" href="#style_def_isavailable" title="GEOCACHE_ISAVAILABLE">Geocache available flag</a>
      bng_e =    British National Grid's easting
      bng =      full coordinate in BNG format (zone easting northing)
      bng_pos =  full coordinate in BNG format (zone easting northing)
      bng_n =    British National Grid's northing
      bng_z =    British National Grid's zone
      caden =    Cadence
      comment =  Notes
      cont =     <a class="link" href="#style_def_geocontainer" title="GEOCACHE_CONTAINER">Geocache container</a>
      cour =     Heading / Course true
      date =     Date (yyyy/mm/dd)
      depth =    Depth (in meters).  Add "ft" or "feet" for feet.
      desc =     Description
      diff =     <a class="link" href="#style_def_geodiff" title="GEOCACHE_DIFF">Geocache difficulty</a>
      ele =      Elevation (in meters) of the point. Add "ft" or "feet" for feet.
      e/w =      'e' for eastern hemisphere, 'w' for western
      exported = Geocache export date 
      found =    <a class="link" href="#style_def_geofound" title="GEOCACHE_LAST_FOUND">Geocache last found date</a>
      fix =      3d, 2d, etc.
      gcid =     Geocache cache id
      geschw =   Geschwindigkeit (speed)
      hdop =     Horizontal dilution of precision
      head =     Heading / Course true
      heart =    Heartrate
      height =   Elevation (in meters) of the point
      hint =     <a class="link" href="#style_def_geohint" title="GEOCACHE_HINT">Geocache cache hint</a>
      icon =     Symbol (icon) name
      lat =      Latitude
      lon =      Longitude
      name =     Waypoint name ("Shortname")
      n/s =      'n' for northern hemisphere, 's' for southern
      notes =    Notes
      pdop =     Position dilution of precision
      placer =   <a class="link" href="#style_def_geoplacer" title="GEOCACHE_PLACER">Geocache placer</a>
      placer_id =Geocache placer id
      power =    Cycling power (in Watts)
      prox =     Proximity (in meters).  Add "ft" or "feet" for feet.
      sat =      Number of sats used for fix
      speed =    Speed
      symb =     Symbol (icon) name
      tempf =    Temperature (degrees Fahrenheit)
      temp =     Temperature (degrees Celsius)
      terr =     <a class="link" href="#style_def_geoterr" title="GEOCACHE_TERR">Geocache terrain</a>
      time =     Time (hh:mm:ss[.msec])
      type =     <a class="link" href="#style_def_geotype" title="GEOCACHE_TYPE">Geocache cache type</a>
      url =      URL
      utc_d =    UTC date
      utc_t =    UTC time
      utm_c =    UTM zone character
      utm_e =    UTM easting
      utm =      full coordinate in UTM format (zone zone-ch easting northing)
      utm_pos =  full coordinate in UTM format (zone zone-ch easting northing)
      utm_n =    UTM northing
      utm_z =    UTM zone
      vdop =     Vertical dilution of precision
      x =        Longitude
      x_pos =    Longitude
      y =        Latitude
      y_pos =    Latitude
      z =        Altitude (elevation).  See "elevation".
   </pre><p>
   We support some enhanced Garmin attributes. They are also available in 
   <a class="link" href="#fmt_gpx" title="GPX XML (gpx)">gpx</a>, <a class="link" href="#fmt_gdb" title="Garmin MapSource - gdb (gdb)">gdb</a>, 
   <a class="link" href="#fmt_garmin_gpi" title="Garmin Points of Interest (.gpi) (garmin_gpi)">garmin_gpi</a> and partly 
   <a class="link" href="#fmt_garmin_txt" title="Garmin MapSource - txt (tab delimited) (garmin_txt)">garmin_txt</a>. These entities are currently 
   not visible in <span class="productname">MapSource</span>™ (6.12.4), but are NOT dropped  
   when working with GDB (version 3) or GPX files.
   </p><pre class="screen"></pre><p>
   Please note, that these do NOT provide a geocoding service; don't expect
	to "convert" a street address to a latitude and longitude.
   </p><pre class="screen">
      addr =     Street address
      city =     City
      country =  Country
      faci =     Facility (not available in GPX)
      phone =    Phone number
      post =     Postal code
      state =    State
   </pre><p>
   Fuller spellings (i.e. "longitude") may be used. You can also
   use keywords with a whitespace instead of an underscore.
</p><p>
   A typical file may be:
   </p><pre class="screen">
     Name, Latitude, Longitude, Description 
     GCEBB,35.972033,-87.134700,Mountain Bike Heaven by susy1313
     GC1A37,36.090683,-86.679550,The Troll by a182pilot &amp; Family
   </pre><p>
</p><p>
   On the output side unicsv writes fixed number of columns (waypoint index, latitude and longitude)
   followed by a variable column list depending on internal data.
</p><p>
   With at least ONE valid timestamp in data a unicsv output may look like that:
   </p><pre class="screen">
     No,Name,Latitude,Longitude,Description,Date,Time
     1,"GCEBB",35.972033,-87.134700,"Mountain Bike Heaven by susy1313",2003/06/29,09:00:00
     2,"GC1A37",36.090683,-86.679550,"The Troll by a182pilot &amp; Family",,
   </pre><p>
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_unicsv_o_datum"></a><code class="option">datum</code> option</h3></div></div></div><p>
      GPS datum (def. WGS 84).
    </p><p>
   This option specifies the datum to be used on output. Valid values for this 
   option are listed in <a class="xref" href="#Datums" title="Appendix A. Supported Datums">Appendix A, <em>Supported Datums</em></a>.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_unicsv_o_grid"></a><code class="option">grid</code> option</h3></div></div></div><p>
      Write position using this grid..
    </p><p>
   This value specifies the grid to be used on write. It is similar to
   the grid option of garmin_txt (see <a class="xref" href="#garmin_grid" title="Table 3.1. Grid values for garmin_txt">Table 3.1, “Grid values for garmin_txt”</a>). The only difference is that unicsv does not
   write a degree sign (°) into the output file.
</p><p>
   Without this option unicsv writes the coordinates as simple numbers like in the samples above.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_unicsv_o_utc"></a><code class="option">utc</code> option</h3></div></div></div><p>
      Write timestamps with offset x to UTC time.
    </p><p>
This option specifies the local time zone to use when writing times.  It
is specified as an offset from Universal Coordinated Time (UTC) in hours.  
Valid values are from -23 to +23.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_unicsv_o_format"></a><code class="option">format</code> option</h3></div></div></div><p>
      Write name(s) of format(s) from input session(s).
    </p><p>
  When this option is enabled, we generate an additional 'Format' column.
  The values of this column are filled with names of previous input formats.
</p><div class="example"><a id="unicsv_format"></a><div class="example-title">Example 3.36. Example for unicsv format option to write names of input formats.</div><div class="example-contents"><p>
    The next example ...
    <strong class="userinput"><code>
      gpsbabel -i gpx -f file1.gpx -i gdb -f file2.gdb -o unicsv,format=y -F result.txt
    </code></strong>
    ... could produce following output:
    </p><table border="0" summary="Simple list" class="simplelist"><tr><td>No,Latitude,Longitude,Name,Description,Symbol,Date,Time,Format</td></tr><tr><td>1,51.075139,12.463689,"578","578","Waypoint",2005/04/26,16:27:23,"gdb"</td></tr><tr><td>2,51.081104,12.465277,"579","579","Waypoint",2005/04/26,16:27:23,"gdb"</td></tr><tr><td>3,50.844126,12.408757,"Gosel","Gosel","Exit",2005/02/26,10:10:47,"gpx"</td></tr><tr><td>4,50.654763,12.204957,"Greiz",,"Exit",2005/02/26,09:57:04,"gpx"</td></tr></table><p>
  </p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_unicsv_o_filename"></a><code class="option">filename</code> option</h3></div></div></div><p>
      Write filename(s) from input session(s).
    </p><p>
  When this option is enabled, we write an additional column called 'Filename'.
  The values of this column are filled with filenames of previous input formats.
</p><p>
  This can be very helpful for locating specific waypoints (i.e. using the position filter)
  in more than one file.
</p><div class="example"><a id="unicsv_filename"></a><div class="example-title">Example 3.37. Example for unicsv filename option to write filenames of input formats.</div><div class="example-contents"><p>
    The next example ...
    <strong class="userinput"><code>
      gpsbabel -i gpx -f file1.gpx -i gdb -f file2.gdb -o unicsv,filename=1 -F result.txt
    </code></strong>
    ... could produce following output:
    </p><table border="0" summary="Simple list" class="simplelist"><tr><td>No,Latitude,Longitude,Name,Date,Time,Filename</td></tr><tr><td>1,51.075139,12.463689,"578",2005/04/26,16:27:23,"reference/gdb-sample.gdb"</td></tr><tr><td>2,51.081104,12.465277,"579",2005/04/26,16:27:23,"reference/gdb-sample.gdb"</td></tr><tr><td>3,50.844126,12.408757,"580",2005/02/26,10:10:47,"reference/gdb-sample.gpx"</td></tr><tr><td>4,50.654763,12.204957,"581",2005/02/26,09:57:04,"reference/gdb-sample.gpx"</td></tr></table><p>
  </p></div></div><br class="example-break" /></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_vcard"></a>Vcard Output (for iPod) (vcard)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          write waypoints
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_vcard_o_encrypt" title="encrypt option">encrypt</a> .</p><p>The vCard output is intended to be in a format that
enables waypoints to be viewed with an Apple iPod. This is achieved by
mapping waypoint fields into vCard fields that can be displayed as
'Contacts' on the iPod. With the iPod mounted as a hard disk (see your
iPod manual for instructions), the resulting VCF file should be moved
into the iPod 'Contacts' folder. As an alternative, Mac OS X users may
prefer to drag the VCF file into their address book and synchronize
with the iPod using iSync. 
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_vcard_o_encrypt"></a><code class="option">encrypt</code> option</h3></div></div></div><p>
      Encrypt hints using ROT13.
    </p><p>
By default geocaching hints are unencrypted; use this option to encrypt them.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_vidaone"></a>VidaOne GPS for Pocket PC (.gpb) (vidaone)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_vidaone_o_ver" title="ver option">ver</a> .</p><p>
  This format supports the <a class="ulink" href="http://www.vidaone.com" target="_top">VidaOne</a> GPS for pocket PC GPB file type.
</p><p>
  This is have a very simple binary format which stores only the coordinates 
  in the tracklog (.gpb) files.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_vidaone_o_ver"></a><code class="option">ver</code> option</h3></div></div></div><p>
      Version of VidaOne file to read or write (1 or 2).
    </p><p>
This option specifies the data format version for the input and the output file.
Valid values are 1 (without altitude) or 2 (with altitude). 1 is the default.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_vitosmt"></a>Vito Navigator II tracks (vitosmt)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>Vito Navigator II is a Pocket PC GPS application.  This
format reads a Vito Navigator II .SMT track file and can work in
either waypoint or track mode.  The speed, heading and Dilution of
Position data is written in the notes field.</p><p> Support for writing .SMT tracks is very experimental and
may crash VitoNavigator II on the Pocket PC.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_vitovtt"></a>Vito SmartMap tracks (.vtt) (vitovtt)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>
  This format reads the binary (.vtt) track logs recorded by
  <a class="ulink" href="http://vitotechnology.com/en/products/smartmap_nokia_series60.html" target="_top">
  <span class="application">VITO SmartMap for Nokia Series 60</span>
  </a> 1.0, a GPS application for smartphones connected to
  NMEA 0183-compatible Bluetooth GPS receivers. It may work
  with .vtt files produced by versions of VITO SmartMap
  for other platforms.
</p><p>
  This format was reverse engineered from a .vtt file.
  Currently, the coordinates, altitude, and time are
  available for each point recorded in a track.
  The course speed and heading fields have been identified,
  but the units are not certain and so those fields are ignored.
  The rest of the entry has not yet been decoded. The format
  uses little-endian byte ordering. The application displays
  metric units by default. Time is UTC.
</p><div class="table"><a id="vito_header"></a><div class="table-title">Table 3.8. Vito SmartMap track file header (8 bytes)</div><div class="table-contents"><table summary="Vito SmartMap track file header (8 bytes)" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Position</th><th>Field info</th></tr></thead><tbody><tr><td>bytes 0-3</td><td>Probably a version field. Int value is 3 in sample file.</td></tr><tr><td>bytes 4-7</td><td>Number of points in file as int.</td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="idp74670304"></a><div class="table-title">Table 3.9. Vito SmartMap track point (32 bytes)</div><div class="table-contents"><table summary="Vito SmartMap track point (32 bytes)" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Position</th><th>Field info</th></tr></thead><tbody><tr><td>bytes 0-3</td><td>Decimal latitude multiplied by 20000000 as int.</td></tr><tr><td>bytes 4-7</td><td>Decimal longitude multiplied by 10000000 as int.</td></tr><tr><td>bytes 8-11</td><td>Altitude in meters as float.</td></tr><tr><td>bytes 12-13</td><td>Year, with century, as int.</td></tr><tr><td>byte 14</td><td>Month, ranging 1-12.</td></tr><tr><td>byte 15</td><td>Day of month, ranging 1-31.</td></tr><tr><td>byte 16</td><td>Hour, ranging 0-23.</td></tr><tr><td>byte 17</td><td>Minute, ranging 0-59.</td></tr><tr><td>bytes 18-21</td><td>Decimal second multiplied by 30000000 as int.</td></tr><tr><td>bytes 22-25</td><td>
        Probably speed in meters per second as float.
        Ranges 0-~3 in file, seems reasonable since sample
        file was acquired on foot.
      </td></tr><tr><td>bytes 26-27</td><td>
        Probably decimal heading multiplied by something.
        Ranges between min and max values possible when
        decoded as integer. Doesn't change when speed field is 0.
        Doesn't change smoothly, jumps around a bit.
      </td></tr><tr><td>bytes 28-31</td><td>
        Status field of some kind. Changes only twice in file.
        May contain satellite count or PDOP info, as both are
        reported by the application's GUI.
      </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_wfff"></a>WiFiFoFum 2.0 for PocketPC XML (wfff)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_wfff_o_aicicon" title="aicicon option">aicicon</a>, <a class="link" href="#fmt_wfff_o_aioicon" title="aioicon option">aioicon</a>, <a class="link" href="#fmt_wfff_o_ahcicon" title="ahcicon option">ahcicon</a>, <a class="link" href="#fmt_wfff_o_ahoicon" title="ahoicon option">ahoicon</a>, <a class="link" href="#fmt_wfff_o_snmac" title="snmac option">snmac</a> .</p><p> WFFF is the export format for <a class="ulink" href="http://www.aspecto-software.com/rw/applications/wififofum/index.html" target="_top">Aspecto Software's WiFiFoFum</a> 2.0 for Windows Mobile PCs.</p><p>It is a simple XML format that is read-only to GPSBabel and stores information about a WiFi stumbling session.</p><p>All WiFi-specific elements are written in the description  field, similar to the netstumbler format.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_wfff_o_aicicon"></a><code class="option">aicicon</code> option</h3></div></div></div><p>
      Infrastructure closed icon name.
    </p><p>
This option lets you specify an icon for infrastructure closed points.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_wfff_o_aioicon"></a><code class="option">aioicon</code> option</h3></div></div></div><p>
      Infrastructure open icon name.
    </p><p>
This option lets you specify an icon for infrastructure open points.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_wfff_o_ahcicon"></a><code class="option">ahcicon</code> option</h3></div></div></div><p>
      Ad-hoc closed icon name.
    </p><p>
This options lets you specify an icon for an Ad-hoc, closed, waypoint.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_wfff_o_ahoicon"></a><code class="option">ahoicon</code> option</h3></div></div></div><p>
      Ad-hoc open icon name.
    </p><p>
This options lets you specify an icon for an Ad-hoc, open, waypoint.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_wfff_o_snmac"></a><code class="option">snmac</code> option</h3></div></div></div><p>
      Shortname is MAC address.
    </p><p>
  This options lets you specify that the shortname of the waypoint is the MAC address.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_wintec_tes"></a>Wintec TES file (wintec_tes)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>This format supports Wintec .tec files, such as appear on the 
<span class="productname">Wintec WBT-202</span>™ data logger.
</p><p>
The WinTec WBT-202 stores tracks and waypoints on an internal
MICRO-SD Memory card. The log files can be accessed by connecting to an USB
host and setting the device into a mass storage device (MSD) mode. To enter
this mode, attach it to the computer, then hold the power button until the 
GPS and Bluetooth LEDs go out.  It will then behave like an USB Memory stick.
and individual files containing your tracks will show up on the "disk" with
names ending in .tes.   You can use GPSBabel to read these files directly
or copy them to your host computer.
</p><p>
Note that this format is for the TES files on the GPS, it has no relationship
to the .TK2 files created by Wintec's Time Machine software for Windows.
</p><p>
Despite the physical similarity to the 
<span class="productname">Wintec WBT-201</span>™, this is believed to be a rather
different product.  While this GPS probably works fine for 
<a class="link" href="#tracking" title="Realtime tracking">realtime tracking</a> over the bluetooth or 
serial lines (once you have appropriate serial drivers), it's expected
to not work with GPSBabel's <a class="link" href="#fmt_wbt" title="Wintec WBT-100/200 GPS Download (wbt)">GPSBabel WBT 
Protocol</a> module.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_wbt-bin"></a>Wintec WBT-100/200 Binary File Format (wbt-bin)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>File protocol for the <span class="productname">Wintec WBT-200</span>™
and <span class="productname">Wintec WBT-201</span>™ (sometimes called the <span class="productname"> G-Rays 2</span>™)GPS data loggers. This format reads the binary file format created
by Wintec's Windows application.</p><p>
<a class="ulink" href="http://www.semsons.com/wiwbmu3gpsre2.html" target="_top">Wintec WBT-201 </a>
</p><div class="example"><a id="wbt-bin-on-macos"></a><div class="example-title">Example 3.38. Command showing conversion of a Wintec binary file to GPX</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i wbt-bin -f tracks.bin -o
gpx -F out.gpx</code></strong></p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_wbt"></a>Wintec WBT-100/200 GPS Download (wbt)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_wbt_o_erase" title="erase option">erase</a> .</p><p>Serial download protocol for the 
<span class="productname">Wintec WBT-200</span>™  and
<span class="productname">Wintec WBT-201</span><span class="productname">Wintec WBT-1000</span>™ 
GPS data loggers. Although untested it is expected that this will also support the WBT-100.</p><p>
<a class="ulink" href="http://www.semsons.com/wiwbmu3gpsre2.html" target="_top">Wintec WBT-201</a>
</p><div class="example"><a id="wbt-on-macos"></a><div class="example-title">Example 3.39. Command showing WBT-200 download and erase over Bluetooth on Mac OS X</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -t -w -i wbt,erase -f /dev/cu.WBT200-SPPslave-1 -o gpx -F out.gpx</code></strong></p></div></div><br class="example-break" /><p>
Internally, this is actually a serial device that has a serial/USB adapter
built into it.  It uses the CP210x chip by Silicon labs.   You will probably
need a driver for this chip.  The product ships with one for Windows.  
The Linux 210x driver seems to work fine.  Mac users will need to download 
the <a class="ulink" href="http://www.silabs.com/tgwWebApp/public/web_content/products/Microcontrollers/USB/en/mcu_vcp.htm" target="_top">Mac driver for CP210x</a>.
</p><p>
GPSBabel does not try to offer an interface to configure these units. That
is left to the Windows software that comes with it or tools like the 
<a class="ulink" href="http://www.daria.co.uk/gps" target="_top">WBT 201 Viewer</a> for Mac OS/X
and Linux.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_wbt_o_erase"></a><code class="option">erase</code> option</h3></div></div></div><p>
      Erase device data after download.
    </p><p>This option erases the track log from the device after download.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_wbt-tk1"></a>Wintec WBT-201/G-Rays 2 Binary File Format (wbt-tk1)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>File protocol for the <span class="productname">Wintec WBT-201 / G-Rays 2</span>™
GPS data logger. This format reads the binary file format created
by Wintec's Time Machine X application.</p><p>
<a class="ulink" href="http://www.semsons.com/wiwbmu3gpsre2.html" target="_top">Wintec WBT-201</a>
</p><div class="example"><a id="wbt-tk1"></a><div class="example-title">Example 3.40. Command showing conversion of a Wintec binary file to GPX</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -w -t -i wbt-tk1 -f tracks.tk1 -o gpx -F out.gpx</code></strong></p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_itracku"></a>XAiOX iTrackU Logger (itracku)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_itracku_o_backup" title="backup option">backup</a>, <a class="link" href="#fmt_itracku_o_new" title="new option">new</a> .</p><p>Serial download protocol for the <span class="productname"><a class="ulink" href="http://www.xaiox.com/itracku_sirf3.htm" target="_top">XAiOX iTrackU BLUETOOTH GPS-RECEIVER SiRF III</a></span>™ data logger.</p><div class="example"><a id="itracku-download"></a><div class="example-title">Example 3.41. Command showing a download from itracku connected to com14.</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i itracku -f com14 -o gpx -F out.gpx</code></strong></p></div></div><br class="example-break" /><p>Use auto: as input filename to let gpsbabel detect the serial port to which the logger is connected.</p><div class="example"><a id="itracku-download-auto"></a><div class="example-title">Example 3.42. Command showing a download from itracku with automatic port detection.</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i itracku -f auto: -o gpx -F out.gpx</code></strong></p></div></div><br class="example-break" /><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_itracku_o_backup"></a><code class="option">backup</code> option</h3></div></div></div><p>
      Appends the input to a backup file.
    </p><p>Specifies a backup file for the binary logger data. New waypoints from the logger will be appended to an existing 
backup file. This allows you to create "endless" binary logger files which, for example, could contain the waypoint data of a whole year.</p><p>The backup file can be read with gpsbabel by  using the itracku format.</p><div class="example"><a id="itracku-backup"></a><div class="example-title">Example 3.43. Download from the data logger while and append the new binary logger data to a backup file. Read the contents of the backup file.</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i itracku,auto,backup=itracku.bak -f dummy -o gpx -F out.gpx</code></strong></p><p><strong class="userinput"><code>gpsbabel -i itracku -f itracku.bak -o gpx -F out.gpx</code></strong></p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_itracku_o_new"></a><code class="option">new</code> option</h3></div></div></div><p>
      Only waypoints that are not the backup file.
    </p><p>Will only pass waypoints along to filters and output formats that are not new, i.e. that are not already stored in the 
backup file. This option can only be used with the backup option.</p><p>Using this option allows you to output the waypoints of your latest trip with gpsbabel while keeping an endless log of all waypoints 
in the backup file.</p><div class="example"><a id="itracku-new"></a><div class="example-title">Example 3.44. Download from the data logger and append the new logger data to a backup file. Output only the new 
  waypoints.</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i itracku,auto,backup=itracku.bak,new -f dummy -o gpx -F out.gpx</code></strong></p></div></div><br class="example-break" /></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_itracku-bin"></a>XAiOX iTrackU Logger Binary File Format (itracku-bin)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_itracku-bin_o_backup" title="backup option">backup</a>, <a class="link" href="#fmt_itracku-bin_o_new" title="new option">new</a> .</p><p>Reads the binary format of the <span class="productname"><a class="ulink" href="http://www.xaiox.com/itracku_sirf3.htm" target="_top">XAiOX iTrackU BLUETOOTH GPS-RECEIVER SiRF III</a></span>™ data logger.</p><div class="example"><a id="itracku-bin"></a><div class="example-title">Example 3.45. Command showing reading an itracku data file.</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i itracku-bin -f itracku.bin -o gpx -F out.gpx</code></strong></p></div></div><br class="example-break" /><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_itracku-bin_o_backup"></a><code class="option">backup</code> option</h3></div></div></div><p>
      Appends the input to a backup file.
    </p><p>
  Providing a filename to this option will append the input to a backup file.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_itracku-bin_o_new"></a><code class="option">new</code> option</h3></div></div></div><p>
      Only waypoints that are not the backup file.
    </p><p>
 When used in conjunction with the "backup" option to this format, it
  will process only waypoints that don't already exist in the backup file.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fmt_yahoo"></a>Yahoo Geocode API data (yahoo)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li></ul></div><p>This format has the following options: <a class="link" href="#fmt_yahoo_o_addrsep" title="addrsep option">addrsep</a> .</p><p>
This format reads output from the 
<a class="ulink" href="http://developer.yahoo.com/maps/rest/V1/geocode.html" target="_top">Yahoo geocoding API</a>.  
This feature of GPSBabel makes it easy to get geocoded results from 
Yahoo into your favorite mapping program, GPS receiver, or other format.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_yahoo_o_addrsep"></a><code class="option">addrsep</code> option</h3></div></div></div><p>
      String to separate concatenated address fields (default=", ").
    </p><p>
This option specifies the string GPSBabel should use to separate the parts
of the street address.  Since most other formats supported by GPSBabel do 
not support street addresses, the street address fields from the Yahoo file
are concatenated into the waypoint "notes" field.
</p><p>
The default value for this option is a comma followed by a space (", ").
</p></div></div><div class="footnotes"><br /><hr class="footnote-hr" /><div id="ftn.posnonly" class="footnote"><p><a href="#posnonly" class="para"><sup class="para">[1] </sup></a>This model does not support transfer of waypoints, tracks, or routes, but may be used with the <a class="link" href="#tracking" title="Realtime tracking">realtime tracking</a> feature.</p></div><div id="ftn.gpx" class="footnote"><p><a href="#gpx" class="para"><sup class="para">[2] </sup></a>This unit uses GPX format, not Garmin protocol.  Therefore one should communicate with it by reading and writing GPX files instead of using this format.  Members of this class of products do not support realtime positioning protocol.</p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="Data_Filters"></a>Chapter 4. Data Filters</h1></div></div></div><div class="toc"><div class="toc-title">Table of Contents</div><dl class="toc"><dt><span class="section"><a href="#filter_bend">Add points before and after bends in routes (bend)</a></span></dt><dt><span class="section"><a href="#filter_polygon">Include Only Points Inside Polygon (polygon)</a></span></dt><dt><span class="section"><a href="#filter_arc">Include Only Points Within Distance of Arc (arc)</a></span></dt><dt><span class="section"><a href="#filter_radius">Include Only Points Within Radius (radius)</a></span></dt><dt><span class="section"><a href="#filter_interpolate">Interpolate between trackpoints (interpolate)</a></span></dt><dt><span class="section"><a href="#filter_height">Manipulate altitudes (height)</a></span></dt><dt><span class="section"><a href="#filter_track">Manipulate track lists (track)</a></span></dt><dt><span class="section"><a href="#filter_sort">Rearrange waypoints by resorting (sort)</a></span></dt><dt><span class="section"><a href="#filter_nuketypes">Remove all waypoints, tracks, or routes (nuketypes)</a></span></dt><dt><span class="section"><a href="#filter_duplicate">Remove Duplicates (duplicate)</a></span></dt><dt><span class="section"><a href="#filter_position">Remove Points Within Distance (position)</a></span></dt><dt><span class="section"><a href="#filter_discard">Remove unreliable points with high hdop or vdop (discard)</a></span></dt><dt><span class="section"><a href="#filter_reverse">Reverse stops within routes (reverse)</a></span></dt><dt><span class="section"><a href="#filter_stack">Save and restore waypoint lists (stack)</a></span></dt><dt><span class="section"><a href="#filter_simplify">Simplify routes (simplify)</a></span></dt><dt><span class="section"><a href="#filter_swap">Swap latitude and longitude of all loaded points (swap)</a></span></dt><dt><span class="section"><a href="#filter_transform">Transform waypoints into a route, tracks into routes, ... (transform)</a></span></dt><dt><span class="section"><a href="#filter_validate">Validate internal data structures (validate)</a></span></dt></dl></div><p> GPSBabel supports data filtering.  Data filters are
      invoked from the command line via the '-x' option.  It should be
      noted that data filters are invoked in the internal pipeline at
      the point that corresponds to their position on the
      command. This implies that specifying a filter before reading
      any data ('-x &lt;filter&gt; -f &lt;file&gt;'), despite being
      legal, will not have any effect. The advantage is that filters
      can be used intermittently between several variations of input
      and output functions.  It should also be noted that filtering
      data from different input types can sometimes produce
      undesirable results due to differences in the native data
      formats.
</p><p> Beware that most filters only apply to a certain kind of
      data. This is usually indicated below by referring to points,
      tracks or routes in the first sentence which describes each
      filter or in the table at <a class="ulink" href="http://www.gpsbabel.org/capabilities.html" target="_top">gpsbabel.org</a>
      .
</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="filter_bend"></a>Add points before and after bends in routes (bend)</h2></div></div></div><p>The bend filter modifies each route replacing each point inside a
curve with two points: one at a given distance in the direction of the
previous point, and another at the same distance in the direction of
the next point in the route. It only replaces points where there is a
change in heading big enough.</p><p>When creating a route, points are usually created inside curves or
intersections. That means that, while navigating that route using a
GPS unit, the course pointer would aim to the inside of that curve or
intersection, and only when you have passed that point will the GPS 
aim to the next waypoint in the route. This behaviour is useful in
marine navigation but when biking, for instance, it may be a bit late
to decide where to turn to in an intersection.</p><p>This filter tries to solve that creating a waypoint before and after
where there is a change in direction.That way, the course pointer will
point to the direction you should turn to ahead in time.</p><p>For this filter to work correctly, the route should be simple enough
that there is only one waypoint inside each curve or intersection.
Because of that, it is usually a good idea to use the simplify filter
before this one.</p><p>This command line reads route.gpx and replaces each point with other two
points: one 25 metres before and another 25 metres after the original
point. It replaces a point only if there is a change of direction
larger than 5 degrees.</p><p><strong class="userinput"><code>gpsbabel -i gpx -f route.gpx -x
bend,distance=25,interpolate,minangle=5 -o gpx -F newroute.gpx
</code></strong></p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_bend_o_distance"></a>distance option</h3></div></div></div><p>
      Distance to the bend in meters where the new points will be added.
    </p><p>Distance in meters to the original point where the new points will be added.</p><p>The new points will be created at this distance. The first one in the
direction of the previous point, ant the second one in the direction
of the next point in the route.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_bend_o_minangle"></a>minangle option</h3></div></div></div><p>
      Minimum bend angle in degrees.
    </p><p>Minimum curve angle in degrees.</p><p>The substitution will only be made if the change in the heading is
greater than this value. This avoids replacing a point if the GPS unit
is already pointing in the correct direction, or if the route reaches
a certain point and goes back the same road.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="filter_polygon"></a>Include Only Points Inside Polygon (polygon)</h2></div></div></div><p> 
The polygon filter includes points if they are inside
of a polygon.  A polygon file looks like an 
<a class="link" href="#filter_arc" title="Include Only Points Within Distance of Arc (arc)">arc</a> file, except
that the arc it describes must be a closed cycle.  That is,
for a simple polygon, the first and last points must be the
same.  Here's a square:
</p><pre class="screen">
# A square (not really) polygon
41.0000       -85.0000
41.0000       -86.0000
42.0000       -86.0000
42.0000       -85.0000
41.0000       -85.0000
</pre><p> 
Polygons may include islands and holes.  To include an
island or a hole, just append it to the main polygon.
</p><pre class="screen">
# A square polygon with a triangular hole
41.0000       -85.0000
41.0000       -86.0000
42.0000       -86.0000
42.0000       -85.0000
41.0000       -85.0000
# The hole begins here
41.5000       -85.5000
41.6000       -85.5000
41.6000       -85.6000
41.5000       -85.5000
</pre><p>
As with the arc filter, you define a polygon by
giving the name of the file that contains it, using
the <code class="option">file</code> option.  
</p><p> 
Note that this filter currently will not work properly
if your polygon contains one or both poles or if it spans the
line of 180 degrees east or west longitude.
</p><div class="example"><a id="example_polygon_filter"></a><div class="example-title">Example 4.1. Using the polygon filter</div><div class="example-contents"><p> 
Suppose you have a polygon file that defines the border of your county, 
called mycounty.txt.  This command line will give you only the points 
in your county:
</p><p><strong class="userinput"><code>gpsbabel -i geo -f 1.loc -x polygon,file=mycounty.txt -o mapsend -F 2.wpt</code></strong></p></div></div><br class="example-break" /><div class="example"><a id="example_in_or_close_to"></a><div class="example-title">Example 4.2. Using the polygon and arc filters to find points in or nearly in a 
polygon</div><div class="example-contents"><p>
Because the polygon and <a class="link" href="#filter_arc" title="Include Only Points Within Distance of Arc (arc)">arc</a> filters use
the same file format, you can use them together to find all points that are
"in or nearly in" a polygon.  This can be useful if your waypoints or the 
boundaries of your polygon are not quite perfect, so you want to provide a 
buffer zone around it in case there are points nearby that should be in the 
polygon but aren't quite.
</p><p><strong class="userinput"><code>
gpsbabel -i gpx -f points.gpx -x stack,push -x polygon,file=mycounty.txt 
-x stack,swap -x arc,file=mycounty.txt,distance=1k -x stack,pop,append 
-x duplicate,shortname -o gpx -F nearmycounty.gpx
</code></strong></p><p>
This command makes a copy of the points, finds the ones that are in your
your county, swaps that result with the copy of the original set of points,
finds the ones from that set that are within 1 km of the border of the county, 
puts the two lists together, and then filters out any points that appear twice
(This step is necessary because points inside the county but near the county 
line will be kept by both the polygon and the arc filter.)
</p></div></div><br class="example-break" /><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_polygon_o_file"></a>file option</h3></div></div></div><p>
      File containing vertices of polygon.
    </p><p>
This option is required.
</p><p>
This option specifies the name of the file containing the polygon to use for
filtering.  The format of the file is as described above.
</p><p>
GPSBabel supports converting any route or track to a file usable by this
filter; simply read it in the normal way and write it using the 
<a class="link" href="#fmt_arc" title="GPSBabel arc filter file (arc)">arc</a> file format.  Afterward, you will 
need to make sure that the first point and the last point in the 
file are the same, as the polygon filter depends on that.  You can do so
with any text editor.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_polygon_o_exclude"></a>exclude option</h3></div></div></div><p>
      Exclude points inside the polygon.
    </p><p>
When this option is specified, the usual sense of the polygon filter is 
reversed.   That is, points that are inside the polygon are discarded
while points that are further away are kept.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="filter_arc"></a>Include Only Points Within Distance of Arc (arc)</h2></div></div></div><p> 
This filter keeps or removes waypoints based on their proximity to an arc, 
which is a series of connected line segments similar to a route or a track 
but without any associated data other than the coordinates.  Optionally, it
can move each non-deleted waypoint over the closest segment of the arc.
</p><p> 
The arc may defined in a file whose name must be provided with the 
<code class="option">file</code>, or the tracks or routes that have already been read.  That file contains pairs of coordinates for the 
vertices of the arc, one coordinate pair per line.  Comments may be
included by preceding them with a '#' character.  An arc file looks 
something like this sample:
</p><pre class="screen">	  
# Lima Road/SR3 north of Fort Wayne, Indiana 	  
41.150064468    -85.166207433 	  
41.150064468    -85.165371895 	  
41.149034500    -85.165157318 	  
41.147832870    -85.164771080 	  
41.146631241    -85.164384842 	  
41.144270897    -85.163655281 	  
41.141953468    -85.162882805
</pre><p> 
An arc file may optionally contain gaps in the arc.  You may specify 
such a gap by inserting a line containing "#break" either on a line by 
itself or after the coordinates of the starting point of the new arc segment.
</p><div class="example"><a id="example_arc_filter"></a><div class="example-title">Example 4.3. Using the arc filter</div><div class="example-contents"><p>
Assuming the arc above is in a file called 
<code class="filename">lima_rd.txt</code>, the following command line
would include only points within one mile of the section of Lima Road 
covered by the arc.
</p><p><strong class="userinput"><code>gpsbabel -i geo -f 1.loc -x arc,file=lima_rd.txt,distance=1 -o mapsend -F 2.wpt</code></strong></p></div></div><br class="example-break" /><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_arc_o_file"></a>file option</h3></div></div></div><p>
      File containing vertices of arc.
    </p><p>
This option specifies the name of the file containing the arc to use for
filtering.  The format of the file is as described above.
</p><p>
GPSBabel supports converting any route or track to a file usable by this
filter; simply read it in the normal way and write it using the 
<a class="link" href="#fmt_arc" title="GPSBabel arc filter file (arc)">arc</a> file format.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_arc_o_rte"></a>rte option</h3></div></div></div><p>
      Route(s) are vertices of arc.
    </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_arc_o_trk"></a>trk option</h3></div></div></div><p>
      Track(s) are vertices of arc.
    </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_arc_o_distance"></a>distance option</h3></div></div></div><p>
      Maximum distance from arc.
    </p><p>
This option is not required, but if it is not specified the distance 
defaults to zero miles, which isn't very useful.
</p><p>
This option specifies the maximum distance a point may be from the arc 
without being discarded.  Points that are closer to the arc are kept, while
points that are further away are discarded.
</p><p>
Distances may be specified in miles (3M) or kilometers (5K).  If no units
are specified, the distance is assumed to be in miles.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_arc_o_exclude"></a>exclude option</h3></div></div></div><p>
      Exclude points close to the arc.
    </p><p>
When this option is specified, the usual sense of the arc filter is reversed. 
That is, points that are closer than <code class="varname">distance</code> are discarded
while points that are further away are kept.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_arc_o_points"></a>points option</h3></div></div></div><p>
      Use distance from vertices not lines.
    </p><p>
When this option is specified, only points that are within the specified 
distance of one of the vertices of the arc are kept.  This differs from the
normal mode of operation in that in the normal mode, points that are close to
the lines between points are also kept.
</p><p>
This option makes the arc filter act like a multi-point version of the
<a class="link" href="#filter_radius" title="Include Only Points Within Radius (radius)">radius</a> filter.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_arc_o_project"></a>project option</h3></div></div></div><p>
      Move waypoints to its projection on lines or vertices.
    </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="filter_radius"></a>Include Only Points Within Radius (radius)</h2></div></div></div><p> 
This filter includes or excludes waypoints based on their proximity to a 
central point.  All waypoints more than the specified distance from the 
specified point will be removed from the dataset.
</p><p>
By default, all remaining points are sorted so that points closer to the 
center appear earlier in the output file.
</p><div class="example"><a id="radius_to_find_points_close"></a><div class="example-title">Example 4.4. Using the radius filter to find points close to a given point</div><div class="example-contents"><p>This example command line would include only points within 1 1/2 miles
       of N30.000 W 90.000</p><p><strong class="userinput"><code>gpsbabel -i geo -f 1.loc -x radius,distance=1.5M,lat=30.0,lon=-90.0 -o mapsend -F 2.wpt</code></strong></p></div></div><br class="example-break" /><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_radius_o_lat"></a>lat option</h3></div></div></div><p>
      Latitude for center point (D.DDDDD).
    </p><p>
This option is required.
</p><p>
This option specifies the latitude of the central point in decimal degrees.
South latitudes should be expressed as a negative number.  Valid values for
this option are from -90 to 90.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_radius_o_lon"></a>lon option</h3></div></div></div><p>
      Longitude for center point (D.DDDDD).
    </p><p>
This option is required.
</p><p>
This option specifies the longitude of the central point in decimal degrees.
West longitudes should be expressed as a negative number.  Valid values for
this option are from -180 to 180.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_radius_o_distance"></a>distance option</h3></div></div></div><p>
      Maximum distance from center.
    </p><p>
This option is required.
</p><p>
This option specifies the maximum distance a point may be from the central
point in order to remain in the dataset.  Points closer than this distance
will be kept and points further away will be removed (unless the 
<code class="option">exclude</code> option is specified.)
</p><p>
Distances may be expressed in miles (3M) or kilometers (4K).  If no units
are provided, the distance is assumed to be in miles.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_radius_o_exclude"></a>exclude option</h3></div></div></div><p>
      Exclude points close to center.
    </p><p>
If this option is included, the action of the radius filter will be reversed:
points within the given distance will be removed, and points further away
will be kept.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_radius_o_nosort"></a>nosort option</h3></div></div></div><p>
      Inhibit sort by distance to center.
    </p><p>
If this option is specified, the radius filter will not sort the remaining
points by distance from the center.  They will remain in whatever order they
were originally.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_radius_o_maxcount"></a>maxcount option</h3></div></div></div><p>
      Output no more than this number of points.
    </p><p>
This option specifies the maximum number of points that the radius filter may
keep.  If there are more than this number of points within the specified 
distance of the center, the more distant points will be discarded even though
they are within the specified distance.  If this option is not specified, 
all points are kept regardless of how many there are.
</p><p>
Note that if the <code class="option">nosort</code> option is also specified, this 
option will instead keep points based on their position within the input
file rather than on their distance from the center.  This may or may not be
what you want.
</p><p>
Note, too, that this option may be used with the <code class="option">exclude</code> 
option, but the results might not be what you expect.  In particular, the 
results will not be the same as if you had kept all of the points you'd 
otherwise throw away.  You will still get no more than 
<code class="varname">maxcount</code> points, but they will all be at least 
<code class="varname">distance</code> away from the center.  (And possibly sorted.)
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_radius_o_asroute"></a>asroute option</h3></div></div></div><p>
      Put resulting waypoints in route of this name.
    </p><p>
This option specifies the name of a route.  If this option is specified, the
radius filter puts all points that are kept into a route with the given name.
The order of points in the route is by distance from the center (unless the
<code class="option">nosort</code> option is also specified.)
</p><p>
Note that this route is not necessarily the most efficient route to visit 
all of the points.  In fact, for some data sets, it might be the least 
efficient route.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="filter_interpolate"></a>Interpolate between trackpoints (interpolate)</h2></div></div></div><p>
This filter modifies any tracks so that either the distance or the time
between consecutive points is no less than the specified interval. Where
points are missing, the filter fills them in by following a straight 
line (actually a great circle) between the adjacent points.  You
must specify either the 
<code class="option">distance</code> or the <code class="option">time</code> option.
</p><div class="example"><a id="example_interpolate_filter"></a><div class="example-title">Example 4.5. Using the interpolate filter</div><div class="example-contents"><p>
This command line reads track.gpx and inserts points wherever two adjacent
trackpoints are more than 10 seconds apart:
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f track.gpx -x interpolate,time=10 -o gpx -F newtrack.gpx</code></strong></p><p>
This command reads track.gpx and inserts points wherever two adjacent
trackpoints are more than 15 kilometers apart:
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f track.gpx -x interpolate,distance=15k -o gpx -F newtrack.gpx</code></strong></p><p>
This command reads track.gpx and inserts points wherever two adjacent
trackpoints are more than 2 miles apart:
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f track.gpx -x interpolate,distance=2m -o gpx -F newtrack.gpx</code></strong></p></div></div><br class="example-break" /><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_interpolate_o_time"></a>time option</h3></div></div></div><p>
      Time interval in seconds.
    </p><p>
This option specifies the maximum allowable time interval between points in the
track.  If two points in the track are further apart than this value, new
points will be inserted between them.
</p><p>
This value is always specified in units of seconds.
</p><p>
Either this option or the <code class="option">distance</code> must be specified.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_interpolate_o_distance"></a>distance option</h3></div></div></div><p>
      Distance interval in miles or kilometers.
    </p><p>
This option specifies the maximum allowable distance between points in the
track.  If two points in the track are further apart than this value, new
points will be inserted between them.
</p><p>
This value may be specified in units of miles (3M) or kilometers (5K).  If
no units are specified, the units are assumed to be miles.
</p><p>
Either this option or the <code class="option">time</code> must be specified.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_interpolate_o_route"></a>route option</h3></div></div></div><p>
      Interpolate routes instead.
    </p><p>
If this option is specified, the interpolate filter interpolates routes 
rather than tracks.  Because route points do not have time stamps, it is an
error to use this option with the <code class="option">time</code> option.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="filter_height"></a>Manipulate altitudes (height)</h2></div></div></div><p> 
The height filter allows the correction of altitude values.

At least one popular gps logger does store the ellipsoidal height (sum of the height above mean see level and the height of the geoid above the WGS84 ellipsoid) instead of the height above sea level, as it can be found on maps. 

The height filter allows for the correction of these altitude values. This filter supports two options:   

<code class="option">wgs84tomsl</code> and <code class="option">add</code>.  
At least one of these options is required, both can be combined.  
</p><div class="example"><a id="height_wgs84tomsl"></a><div class="example-title">Example 4.6.  This option subtracts the WGS84 geoid height from every altitude. For GPS receivers like the iBlue747 the result is the height above mean see level.</div><div class="example-contents"><p><strong class="userinput"><code> gpsbabel -i gpx -f in.gpx -x height,wgs84tomsl -o gpx -F out.gpx</code></strong></p><p>The coordinates and altitude vales must be based an the WGS84 ellipsoid for this option to produce sensible results</p></div></div><br class="example-break" /><div class="example"><a id="height_add"></a><div class="example-title">Example 4.7.  This options adds a constant value to every altitude.</div><div class="example-contents"><p><strong class="userinput"><code> gpsbabel -i gpx -f in.gpx -x height,add=10.2f -o gpx -F out.gpx</code></strong></p><p>You can specify negative numbers to subtract the value. If no unit is specified meters are assumed. For feet you can attach an "f" to the value.</p></div></div><br class="example-break" /><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_height_o_add"></a>add option</h3></div></div></div><p>
      Adds a constant value to every altitude (meter, append "f" (x.xxf) for feet).
    </p><p>
Adds a constant value to every altitude. You can specify negative numbers to subtract the value.
</p><p>
If no unit is specified, (m)eters are assumed. You can override this by attaching a "f" for feet to the number.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_height_o_wgs84tomsl"></a>wgs84tomsl option</h3></div></div></div><p>
      Converts WGS84 ellipsoidal height to orthometric height (MSL).
    </p><p>
  Subtracts the WGS84 geoid height from every altitude.
</p><p>
  For GPS receivers like the iBlue747 this corrects the logged altitudes to height above mean sea level.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="filter_track"></a>Manipulate track lists (track)</h2></div></div></div><p>
WARNING: This filter always drops empty tracks.
</p><p>
This filter performs various operations on track data.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_track_o_move"></a>move option</h3></div></div></div><p>
      Correct trackpoint timestamps by a delta.
    </p><p>
This option changes the time of all trackpoints. This might be useful if
your track must be moved by one or more hours because of an incorrect
time zone.
</p><div class="example"><a id="ex_track_move"></a><div class="example-title">Example 4.8. Time-shifting a track with the track filter</div><div class="example-contents"><p>
The following command line will shift all tracks to be one hour later.
</p><p><strong class="userinput"><code>gpsbabel -t -i gpx -f in.gpx -x track,move=+1h -o gpx -F out.gpx</code></strong></p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_track_o_pack"></a>pack option</h3></div></div></div><p>
      Pack all tracks into one.
    </p><p> 
This option causes all tracks to be appended to one another to form a single
track.  This option does not work if any two tracks overlap in time; in that
case, consider using the <code class="option">merge</code> option. 
</p><p>
This option is most useful for rejoining tracks that might have
been interrupted by an equipment malfunction or an overnight stop.
</p><p>
If no other option is given to the track filter, this option is assumed.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_track_o_split"></a>split option</h3></div></div></div><p>
      Split by date or time interval (see README).
    </p><p> The input track will be split into several tracks
         depending on date of track points. If there is more than one
         track, use the pack option before before using this.  To
         split a single tracks into separate tracks for each day and
         name them, use this:
      </p><p><strong class="userinput"><code> gpsbabel -t -i gpx -f in.gpx -x track,split,title="ACTIVE LOG # %Y%m%d" -o gpx -F out.gpx</code></strong></p><p> If the input has multiple tracks, pack them together before
splitting them back apart per day thusly: </p><p><strong class="userinput"><code>     	    gpsbabel -t   -i gpx -f in.gpx  
     -x track,pack,split,title="ACTIVE LOG # %D"  	
     -o gpx -F out.gpx</code></strong></p><p> Additionally you can add an interval to the split
         option.  With this the track will be split if the time
         between two points is greater than this parameter. The
         interval must be numeric and can be int days, hours, minutes
         or seconds, expressed as one of the character "d", "h", "m",
         or "s".  If no trailing character is present, the units are
         assumed to be in seconds.
</p><p> For example, to split a track based on an four hour
         interval, use this:</p><p><strong class="userinput"><code>            
gpsbabel -t 
     -i gpx -f in.gpx 
     -x track,pack,split=4h,title="LOG # %c" 
     -o gpx -F out.gpx
</code></strong></p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_track_o_sdistance"></a>sdistance option</h3></div></div></div><p>
      Split by distance.
    </p><p> The input track will be split into several tracks
         if the distance between successive track points
         is greater than the distance given as a parameter.
         The distance must be numeric and can be in miles or kilometers,
         expressed as one of the character "k", or "m".
	If sdistance is given no parameters, this option has the same 
	effect as the split option without parameters. If there is more 
	than one track,
         use the pack option before before using this.</p><p> For example, to split the track if the distance between
         points is greater than 100 meters, use this:</p><p><strong class="userinput"><code>
gpsbabel -t 
     -i gpx -f in.gpx 
     -x track,pack,sdistance=0.1k" 
     -o gpx -F out.gpx
</code></strong></p><p> The sdistance option can be combined with the split option.
        The track then will be split only if both time and distance
        interval exceeds the supplied values. This technique can be used to 
	filter out gaps from
        the tracklog.  The gap is kept only if the gps device is without
        signal for longer time than that given and during that time it moves 
	a distance over that given.
        This example splits the track
        if the device is without signal for at least 5 minutes
        and during this time moves more than 300 meters:</p><p><strong class="userinput"><code>
gpsbabel -t 
     -i gpx -f in.gpx 
     -x track,pack,sdistance=0.3k,split=5m 
     -o gpx -F out.gpx
</code></strong></p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_track_o_merge"></a>merge option</h3></div></div></div><p>
      Merge multiple tracks for the same way.
    </p><p> 
This option puts all track points from all tracks into a single track 
and sorts them by time stamp.  Points with identical time stamps will be
dropped.
</p><div class="example"><a id="ex_track_merge"></a><div class="example-title">Example 4.9. Merging tracks with the track filter</div><div class="example-contents"><p> 
Suppose you want to merge tracks recorded with two different GPS devices 
at the same time.  To do that, use this command line:
</p><p><strong class="userinput"><code>gpsbabel -t -i gpx -f john.gpx -i gpx -f doe.gpx -x track,merge,title="COMBINED LOG" -o gpx -F john_doe.gpx</code></strong></p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_track_o_name"></a>name option</h3></div></div></div><p>
      Use only track(s) where title matches given name.
    </p><p>
With the name option you can filter out a track by title.
</p><p>
The comparison is always non-case-sensitive. Wildcards are allowed.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_track_o_start"></a>start option</h3></div></div></div><p>
      Use only track points after this timestamp.
    </p><p>
This option is used along with the <code class="option">stop</code> to discard 
trackpoints that were recorded outside of a specific period of time.  
This option specifies the beginning of the time period.
</p><p>
If this option is not specified, the time period is assumed to begin at the
dawn of time or January 1, 1970, whichever was later.  The time for this 
option is expressed in UTC. 
</p><p>
The value of this option must be in the form of YYYYMMDDHHMMSS, but it is
not necessary to specify the smaller time units if they are not needed.  
That is, if you only care about points logged between 10 AM and 6 PM on a
given date, you need not specify the minutes or seconds.
</p><div class="example"><a id="ex_track_startstop"></a><div class="example-title">Example 4.10. Extracting a period of time with the track filter</div><div class="example-contents"><p>
To get only the parts of a track that were mapped on 20 July 2005
between 10 AM and 6 PM, use this command line:
</p><p><strong class="userinput"><code>gpsbabel -t -i gpx -f in.gpx -x track,start=2005072010,stop=2005072018 -o gpx -F out.gpx </code></strong></p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_track_o_stop"></a>stop option</h3></div></div></div><p>
      Use only track points before this timestamp.
    </p><p>
This option is used in conjunction with the <code class="option">start</code> option to 
discard all trackpoints outside of a given period of time.  This option 
defines the end of the time period.
</p><p>
If this option is not specified, the time period is assumed to end at the 
end of civilization as we know it or the year 2038, whichever comes first.
The time for this option is expressed in UTC.
</p><p>
See the <code class="option">start</code> option for the format of this value and an 
example of usage.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_track_o_title"></a>title option</h3></div></div></div><p>
      Basic title for new track(s).
    </p><p> 
This option specifies a title for tracks generated by the track filter.
By default, the title of the new track is composed of the start time of 
the track appended to this value.
</p><p>
If this value contains a percent (%) character, it is treated as a format 
string for the POSIX strftime function, allowing custom time-based 
track names. 
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_track_o_fix"></a>fix option</h3></div></div></div><p>
      Synthesize GPS fixes (PPS, DGPS, 3D, 2D, NONE).
    </p><p>
This option sets the GPS fix status for all trackpoints to the specified
value.  Valid values for this option are PPS, DGPS, 3D, 2D, or NONE.
</p><p>
This option is most useful when converting from a format that doesn't 
contain GPS fix status to one that requires it.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_track_o_course"></a>course option</h3></div></div></div><p>
      Synthesize course.
    </p><p>
This option computes (or recomputes) a value for the GPS heading at each 
trackpoint.  This is most useful with trackpoints from formats that don't 
support heading information or for trackpoints synthesized by the 
<a class="link" href="#filter_interpolate" title="Interpolate between trackpoints (interpolate)">interpolate</a>
filter.  The heading at each trackpoint is simply the course from the
previous trackpoint in the track.  The first trackpoint in each track
is arbitrarily assigned a heading of 0 degrees.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_track_o_speed"></a>speed option</h3></div></div></div><p>
      Synthesize speed.
    </p><p>
This option computes a value for the GPS speed at each trackpoint.
This is most useful with trackpoints from formats that don't support
speed information or for trackoints synthesized by the 
<a class="link" href="#filter_interpolate" title="Interpolate between trackpoints (interpolate)">interpolate</a>
filter.  The speed at each trackpoint is the average speed from the
previous trackpoint (distance divided by time).  The first trackpoint 
in each track is assigned a speed of "unknown."
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_track_o_seg2trk"></a>seg2trk option</h3></div></div></div><p>
      Split track at segment boundaries into multiple tracks.
    </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_track_o_trk2seg"></a>trk2seg option</h3></div></div></div><p>
      Merge tracks inserting segment separators at boundaries.
    </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_track_o_segment"></a>segment option</h3></div></div></div><p>
      segment tracks with abnormally long gaps.
    </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_track_o_faketime"></a>faketime option</h3></div></div></div><p>
      Add specified timestamp to each trackpoint.
    </p><p>
This option assigns a time value to each trackpoint.
</p><p>
The value of this option must be in the form of fYYYYMMDDHHMMSS+SS.
</p><p>
The parameter f (force) is optional and means that the time value of each trackpoint is replaced.
If f is not specified, the time value of each trackpoint is only replaced when the trackpoint contains no time value.
</p><p>
YYYYMMDDHHMMSS is the pattern for the timestamp and is required.
</p><p>
The plus sign is the delimiter between the timestamp and the step time in seconds.
The first trackpoint receives the time value of the timestamp and
each following trackpoint receives the timestamp incremented by the step time.
The specification of the steptime is optional.
</p><p>
The parameter was added because some software products (e.g. garmin training center)
require a time value for each trackpoint.
</p><div class="example"><a id="ex_track_faketime1"></a><div class="example-title">Example 4.11. Replace time values of a track</div><div class="example-contents"><p>
Replace all time values with new time values.
Start at the 5 th of July, 2010 at 8 PM and
increment 2 seconds between each trackpoint:
</p><p><strong class="userinput"><code>gpsbabel -i kml -f in.kml -x track,faketime=f20100705200000+2 -o gtrnctr -F out.tcx</code></strong></p></div></div><br class="example-break" /><div class="example"><a id="ex_track_faketime2"></a><div class="example-title">Example 4.12. Add time values to a track</div><div class="example-contents"><p>
Add a time value to a trackpoint, if the trackpoint contains no time value.
Start at the 6 th of May, 2010 at 6 AM and
increment 5 seconds between each trackpoint:
</p><p><strong class="userinput"><code>gpsbabel -i kml -f in.kml -x track,faketime=20100506060000+5 -o gtrnctr -F out.tcx</code></strong></p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_track_o_discard"></a>discard option</h3></div></div></div><p>
      Discard track points without timestamps during merge.
    </p><p> 
This option is used in conjunction with the merge option to discard track points with missing
timestamps instead of aborting with the "Found track point at lat,lon without time!" error.
</p><div class="example"><a id="ex_track_discard"></a><div class="example-title">Example 4.13. Merging tracks with missing timestamps with the track filter</div><div class="example-contents"><p> 
Suppose you want to merge tracks that may have missing timestamps.  To do that, use this command line:
</p><p><strong class="userinput"><code>gpsbabel -t -i gpx -f john.gpx -f doe.gpx -x track,merge,discard -o gpx -F john_doe.gpx</code></strong></p></div></div><br class="example-break" /></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="filter_sort"></a>Rearrange waypoints by resorting (sort)</h2></div></div></div><p>
This filter sorts waypoints into alphabetical order by the selected field.
You must specify exactly one of the options.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_sort_o_gcid"></a>gcid option</h3></div></div></div><p>
      Sort by numeric geocache ID.
    </p><p>
If the data contains Groundspeak geocache IDs, this option causes the 
waypoints to be sorted in alphabetical order by geocache ID.
</p><p>
This option is not valid in combination with any other option.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_sort_o_shortname"></a>shortname option</h3></div></div></div><p>
      Sort by waypoint short name.
    </p><p>
This option causes the waypoints to be sorted in alphabetical order by 
short name.
</p><p>
This option is not valid in combination with any other option.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_sort_o_description"></a>description option</h3></div></div></div><p>
      Sort by waypoint description.
    </p><p>
This option causes the waypoints to be sorted in alphabetical order by 
description.
</p><p>
This option is not valid in combination with any other option.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_sort_o_time"></a>time option</h3></div></div></div><p>
      Sort by time.
    </p><p>
This option causes the waypoints to be sorted in chronological order by 
creation time.
</p><p>
This option is not valid in combination with any other option.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="filter_nuketypes"></a>Remove all waypoints, tracks, or routes (nuketypes)</h2></div></div></div><p>
There are three main types of data that GPSBabel deals with:
waypoints, tracks, and routes.   The nuketypes filter allows
removing all the data of any or all of those three types.
</p><div class="example"><a id="example_nuketypes_filter"></a><div class="example-title">Example 4.14. Filtering data types with nuketypes</div><div class="example-contents"><p>
If you have a GPX file that contains routes, tracks, and
waypoints and you want a GPX file that contains only tracks,
you may use this filter to remove the waypoints and the routes 
with this command:
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f bigfile.gpx -x nuketypes,waypoints,routes -o gpx -F tracksonly.gpx</code></strong></p></div></div><br class="example-break" /><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_nuketypes_o_waypoints"></a>waypoints option</h3></div></div></div><p>
      Remove all waypoints from data stream.
    </p><p>
This option causes the nuketypes filter to discard all waypoints that are not 
associated with a track or route.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_nuketypes_o_tracks"></a>tracks option</h3></div></div></div><p>
      Remove all tracks from data stream.
    </p><p>
This option causes the nuketypes filter to discard all track data.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_nuketypes_o_routes"></a>routes option</h3></div></div></div><p>
      Remove all routes from data stream.
    </p><p>
This option causes the nuketypes filter to discard all route data.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="filter_duplicate"></a>Remove Duplicates (duplicate)</h2></div></div></div><p> 
The duplicate filter is designed to remove duplicate points based on their 
short name (traditionally a waypoint's name on the GPS receiver), and/or 
their location (to a  precision of 6 decimals).  This filter supports two 
options that specify how duplicates will be recognized, 
<code class="option">shortname</code> and <code class="option">location</code>.  
Generally, at least one of these options is required.  
</p><div class="example"><a id="duplicate_to_suppress_points"></a><div class="example-title">Example 4.15. Using the duplicate filter to suppress points with the same 
         name and location</div><div class="example-contents"><p>
  This command line removes points that have duplicate short names
  and duplicate locations.  The result would be a 
  <a class="link" href="#fmt_gpx" title="GPX XML (gpx)">gpx</a> file that more than likely 
  contains only unique points and point data.
  </p><p><strong class="userinput"><code> gpsbabel -i gpx -f 1.gpx -f 2.gpx -x duplicate,location,shortname -o gpx -F merged_with_no_dupes.gpx</code></strong></p></div></div><br class="example-break" /><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_duplicate_o_shortname"></a>shortname option</h3></div></div></div><p>
      Suppress duplicate waypoints based on name.
    </p><p>
This option is the one most often used with the duplicate filter.  This 
option instructs the duplicate filter to remove any waypoints that share
a short name with a waypoint that has come before.  This option might be
used to remove duplicates if you are merging two datasets that were 
each created in part from a common ancestor dataset.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_duplicate_o_location"></a>location option</h3></div></div></div><p>
      Suppress duplicate waypoint based on coords.
    </p><p>
This option causes the duplicate filter to remove any additional waypoint 
that has the same coordinates (to six decimal degrees) as a waypoint that 
came before.  This option may be used to remove duplicate waypoints if the 
names are not expected to be the same.  It also might be used along with the
<code class="option">shortname</code> option to remove duplicate waypoints if the names 
of several unrelated groups of waypoints might be the same.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_duplicate_o_all"></a>all option</h3></div></div></div><p>
      Suppress all instances of duplicates.
    </p><p>
When this option is specified, GPSBabel will remove all instances of a
duplicated waypoint, not just the second and subsequent instances.  If
your input file contains waypoints A, B, B, and C, the output file will
contain waypoints A, B, and C without the <code class="option">all</code> option, 
or just A and C with the <code class="option">all</code> option.
</p><div class="example"><a id="duplicate_to_ignore"></a><div class="example-title">Example 4.16. Using the duplicate filter to implement an "ignore list."</div><div class="example-contents"><p>
This option may be used to implement an "ignore list."  In the following 
example, the duplicate filter is used to remove a list of waypoints to be
ignored from a larger collection of waypoints:
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f waypoints.gpx -i csv -f to_ignore.csv -x duplicate,shortname,all -o gpx -F filtered.gpx</code></strong></p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_duplicate_o_correct"></a>correct option</h3></div></div></div><p>
      Use coords from duplicate points.
    </p><p>
This option is used to change the locations of waypoints without losing any 
of the other associated information.  When this option is specified, the 
latitude and longitude from later duplicates will replace the latitude and
longitude in the original waypoint.
</p><p>
As an example, this option may be used to adjust the locations of "puzzle" 
geocaches in a Groundspeak pocket query:
</p><div class="example"><a id="Correcting_Cache_Locations"></a><div class="example-title">Example 4.17. Using the duplicate filter to correct the locations of "puzzle"
geocaches</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i gpx -f 43622.gpx -i csv -f corrections.csv -x duplicate,shortname,correct -o gpx -F 43622-corrected.gpx</code></strong></p><p>
After this command is run, the waypoints in the output file will have all 
of the descriptive information from <code class="filename">43622.gpx</code>, but 
waypoints that were also found in <code class="filename">corrections.csv</code> 
will have their coordinates replaced with the coordinates from that file.
</p></div></div><br class="example-break" /></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="filter_position"></a>Remove Points Within Distance (position)</h2></div></div></div><p> 
This filter removes points based on their proximity to each other.  A 
point is removed if it is within the specified distance of a point that 
has come before.
</p><div class="example"><a id="posn_to_suppress_close_points"></a><div class="example-title">Example 4.18. Using the position filter to suppress close points</div><div class="example-contents"><p>
The following command removes multiple points that are within 
one foot of each other, leaving just one.
</p><p><strong class="userinput"><code>gpsbabel -i geo -f 1.loc -f 2.loc -x position,distance=1f -o mapsend -F 3.wpt</code></strong></p></div></div><br class="example-break" /><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_position_o_distance"></a>distance option</h3></div></div></div><p>
      Maximum positional distance.
    </p><p>
This option specifies the minimum allowable distance between two points.  If 
two points are closer than this distance, only one of them is kept.
</p><p>
Distances may be expressed in feet (30f) or meters (10m).  If no unit is 
specified, the distance is assumed to be in feet.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_position_o_all"></a>all option</h3></div></div></div><p>
      Suppress all points close to other points.
    </p><p>
This option causes the position filter to remove all points that are within
the specified distance of one another, rather than leaving just one of them.
</p><p>
This option may be used to entirely remove clusters of points.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_position_o_time"></a>time option</h3></div></div></div><p>
      Maximum time in seconds beetween two points.
    </p><p>
  Specifies the maximum time in seconds between any two points. If the 
  time difference is larger than what's specified here, the points will 
  not be discarded.
</p><p>
  This is useful if you have multiple tracks of the same course and you'd
  like the filter to consider the tracks the same.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="filter_discard"></a>Remove unreliable points with high hdop or vdop (discard)</h2></div></div></div><p>
This filter is used to "fix" unreliable GPS data by discarding points
that are believed to be unreliable.  You may specify an 
HDOP and/or VDOP above a specified limit, a minimum number of satellites
that must have been in view for a fix to be considered, or both.
</p><p>
HDOP and VDOP are measures of the best possible horizontal or vertical precision for a given configuration of GPS satellites.   Higher numbers indicate a higher dilution of precision and therefore mathematically less useful.
</p><p>
</p><div class="example"><a id="example_discard_filter"></a><div class="example-title">Example 4.19. Using the discard filter for HDOP and VDOP. </div><div class="example-contents"><p><strong class="userinput"><code> gpsbabel -i gpx -f in.gpx -x discard,hdop=10,vdop=20,hdopandvdop -o gpx -F out.gpx</code></strong></p></div></div><p><br class="example-break" />
</p><p>
You may specify a minimum number of  satellites.  
</p><p>
</p><div class="example"><a id="example_discard_filter_sats"></a><div class="example-title">Example 4.20. Using the discard filter to require at least three satellites. </div><div class="example-contents"><p><strong class="userinput"><code> gpsbabel -i gpx -f in.gpx -x discard,sat=3 -o gpx -F out.gpx</code></strong></p></div></div><p><br class="example-break" />
</p><p> Contributed by Tobias Minich and Serge Droz. </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_discard_o_hdop"></a>hdop option</h3></div></div></div><p>
      Suppress waypoints with higher hdop.
    </p><p>
This option specifies the maximum allowable Horizontal Dilution of 
Precision (HDOP).  By default, any point with an HDOP in excess of 
this value will be discarded regardless of its VDOP, but see 
<code class="option">hdopandvdop</code>.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_discard_o_vdop"></a>vdop option</h3></div></div></div><p>
      Suppress waypoints with higher vdop.
    </p><p>
This option specifies the maximum allowable Vertical Dilution of 
Precision (VDOP).  By default, any point with an VDOP in excess of 
this value will be discarded regardless of its HDOP, but see 
<code class="option">hdopandvdop</code>.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_discard_o_hdopandvdop"></a>hdopandvdop option</h3></div></div></div><p>
      Link hdop and vdop supression with AND.
    </p><p>
If this option is used, only points that exceed both the maximum 
allowable HDOP and the maximum allowable VDOP will be discarded.  This
option requires that both the <code class="option">hdop</code> and 
<code class="option">vdop</code> options be specified.  
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_discard_o_sat"></a>sat option</h3></div></div></div><p>
      Minimium sats to keep waypoints.
    </p><p>
This option specifies the minimum required number of satellites.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_discard_o_fixnone"></a>fixnone option</h3></div></div></div><p>
      Suppress waypoints without fix.
    </p><p>
  This option is similar to the 'sat' option.   There are times when
  some GPSes will know how many satellites are in view, but not yet computed
  a valid fix.  This option allows you to discard those points.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_discard_o_fixunknown"></a>fixunknown option</h3></div></div></div><p>
      Suppress waypoints with unknown fix.
    </p><p>
  This option is similar to the 'sat' option. Some GPSes will log
  points with a fix value of 'unknown'.
  This option allows you to discard those points.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_discard_o_elemin"></a>elemin option</h3></div></div></div><p>
      Suppress waypoints below given elevation in meters.
    </p><p>
This option drops waypoints with an altitude lower than the specified 
value (in meters).   Although GPS altitude isn't very accurate, 
GPS devices may log faulty waypoints from time to time, such as when 
near tall buildings.  Elevation values that are way off may signify such waypoints.  Use this option to the filter to toss known rogue points.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_discard_o_elemax"></a>elemax option</h3></div></div></div><p>
      Suppress waypoints above given elevation in meters.
    </p><p>
This option drops waypoints with an altitude higher than the specified value (in meters).   See elemin for an explanation why this may be useful.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="filter_reverse"></a>Reverse stops within routes (reverse)</h2></div></div></div><p> The reverse filter is used to reverse tracks and routes.
	It's mostly useful for those few formats where track/route
	sequence matters and there isn't a way to reverse them using
	the program itself.</p><p> The reversal is performed in the laziest way possible.
        Timestamps are kept with the original waypoints so the
        resulting track or route will have the interesting
        characteristic that time runs backwards.  This tends to make
        Magellan Mapsend, in particular, do a weird thing and place
        each waypoint on a separate day.
</p><p> Additionally, if you're using this to reverse a route
         that navigates, say, an exit ramp or a one way street, you
         will be in for unpleasant ride. application cares about
         timestamps
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="filter_stack"></a>Save and restore waypoint lists (stack)</h2></div></div></div><p> 
This filter is designed to solve advanced problems that involve shuffling 
multiple lists of waypoints, tracks, or routes.  
</p><p>
The stack filter can be used to save the current state of the entire
collection of data.  That state is placed on top of a stack of collections,
so you can simultaneously have as many stored collections of data as you
can fit in your computer's memory.
</p><p> 
 The stack filter can be used in conjunction with other
 filters to implement a "union" or "logical or" functionality.
 The basic idea is to use the stack to store copies of the
 original list of waypoints, then use the 'swap' function to
 replace each copy with a filtered list.  Finally, append all
 of the filtered lists to create one big list, which is then
 output.  The following example finds a list of all points
 that are either inside county A or inside county B.  Any
 points that are inside both counties are duplicated (but the
 duplicates can be removed with the DUPLICATE filter; see
 above.)
</p><p><strong class="userinput"><code>           
gpsbabel -i gpx -f in.gpx 
         -x stack,push,copy 
         -x polygon,file=county_a.txt 
         -x stack,swap 
         -x polygon,file=county_b.txt 
         -x stack,pop,append 
         -o gpx -F out.gpx
</code></strong></p><p> This example reads a large list of waypoints and
         extracts the points within 20 miles of each of two cities,
         writing the waypoint descriptions into two different PalmDoc
         files and exporting all of the points to the GPS receiver:
</p><p><strong class="userinput"><code>           
gpsbabel -i gpx -f indiana.gpx 
         -x stack,push,copy 
         -x radius,lat=41.0765,lon=-85.1365,distance=20m 
         -o palmdoc,dbname=Fort\ Wayne -F fortwayne.pdb 
         -x stack,swap 
         -x radius,lat=39.7733,lon=-86.1433,distance=20m 
         -o palmdoc,dbname=Indianapolis -F indianapolis.pdb 
         -x stack,pop,append 
         -o magellan -F fwaind.wpt
</code></strong></p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_stack_o_push"></a>push option</h3></div></div></div><p>
      Push waypoint list onto stack.
    </p><p>
This is one of three "primary" options to the stack filter.
</p><p>
When this option is specified, the current state is pushed onto the top of
the stack.  By default, the current state is then cleared, but the 
<code class="option">copy</code> option can be used to cause it to be saved.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_stack_o_pop"></a>pop option</h3></div></div></div><p>
      Pop waypoint list from stack.
    </p><p>
This is one of three "primary" options to the stack filter.
</p><p>
This option "pops" the collection of data from the top of the stack.  
By default, the saved state replaces the current state, but see the 
<code class="option">discard</code> and <code class="option">append</code> options for 
alternatives.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_stack_o_swap"></a>swap option</h3></div></div></div><p>
      Swap waypoint list with &lt;depth&gt; item on stack.
    </p><p>
This is one of three "primary" options to the stack filter.
</p><p>
When this option is specified, the current state is swapped with a saved
state from the stack.  By default, it is swapped with the top of the stack,
but the <code class="option">depth</code> can be used to specify a different saved
state.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_stack_o_copy"></a>copy option</h3></div></div></div><p>
      (push) Copy waypoint list.
    </p><p>
This option is only valid when used with the <code class="option">push</code> option.
When this option is specified, a copy of the current state is pushed onto 
the stack but the current state is left unchanged.  Otherwise, the push 
operation clears the current data collection.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_stack_o_append"></a>append option</h3></div></div></div><p>
      (pop) Append list.
    </p><p>
This option is only valid in conjunction with the <code class="option">pop</code>.  
When it is specified, the topmost collection of data from the stack is
appended to the current collection of data.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_stack_o_discard"></a>discard option</h3></div></div></div><p>
      (pop) Discard top of stack.
    </p><p>
This option is only valid when used with the <code class="option">pop</code> option.
When this option is specified, the popped state is discarded and the current
state remains unchanged.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_stack_o_replace"></a>replace option</h3></div></div></div><p>
      (pop) Replace list (default).
    </p><p>
This option is only valid when used with the <code class="option">pop</code> option.
This is the default behavior of the <code class="option">pop</code> option, so you 
should never need to specify it, but it is included for the sake of 
readability.  When this option is specified, the popped state replaces 
the current state.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_stack_o_depth"></a>depth option</h3></div></div></div><p>
      (swap) Item to use (default=1).
    </p><p>
This option is only valid when used along with the <code class="option">swap</code>
option.  If specified, it indicates which item on the stack should be
swapped with the current state.  The default value is 1, which corresponds
to the top of the stack.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="filter_simplify"></a>Simplify routes (simplify)</h2></div></div></div><p> 
The Simplify filter is used to simplify routes and tracks for use with 
formats that limit the number of points they can contain or just to 
reduce the complexity of a route.
</p><p>
The filter attempts to remove points from each route until the number 
of points or the error is within the given bounds, while also attempting 
to preserve the shape of the original route as much as possible.  
</p><p> 
The quality of the results will vary depending on the density of points 
in the original route and the length of the original route.
</p><p> 
For example, suppose you have a route from Street Atlas 2003 that you 
wish to use with a Magellan GPS receiver that only supports up to 50 points 
in a route:
</p><p><strong class="userinput"><code>gpsbabel -r -i saroute -f RoadTrip.anr -x simplify,count=50 -o magellan  -F grocery.rte</code></strong></p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_simplify_o_count"></a>count option</h3></div></div></div><p>
      Maximum number of points in route.
    </p><p>
This option specifies the maximum number of points which may appear in the
simplified route.  For example, if you specify "count=50", all resulting
routes will contain 50 points or fewer.  
</p><p>
You must specify either this option or the <code class="option">error</code> option.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_simplify_o_error"></a>error option</h3></div></div></div><p>
      Maximum error.
    </p><p>
This option specifies the maximum allowable error that may be introduced
by removing a single point. Used with the <code class="option">length</code>
and <code class="option">crosstrack</code> methods, the value of this option is a distance,
specified in miles by default.  You may also specify the distance in 
kilometers by adding a 'k' to the end of the number.
For the <code class="option">relative</code> method it is a dimensionless quantity.
</p><p> 
How the error is determined depends on whether the <code class="option">length</code>,
<code class="option">crosstrack</code>, or <code class="option">relative</code> method is used.
If you are using the length method, the error is the change in the length of
the route introduced by removing a point.  If you are using the crosstrack
method, the error is the distance from the point to the line that results if
that point is removed. If you are using the relative method, the error is the
ratio between the crosstrack error and the horizontal accuracy (derived from
HDOP data).
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_simplify_o_crosstrack"></a>crosstrack option</h3></div></div></div><p>
      Use cross-track error (default).
    </p><p>
This option instructs GPSBabel to remove points that have the smallest 
overall effect on the overall shape of the route.  Using this method, the
first point to be removed will be the one that is closest to a line drawn 
between the two points adjacent to it.
</p><p>
If neither this option nor the <code class="option">length</code> option is specified,
this is the default.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_simplify_o_length"></a>length option</h3></div></div></div><p>
      Use arclength error.
    </p><p>
This option instructs GPSBabel to simplify by removing points that cause the
smallest change in the overall length of the route first.  
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_simplify_o_relative"></a>relative option</h3></div></div></div><p>
      Use relative error.
    </p><p>
Similar to the <code class="option">crosstrack</code> method, but the error introduced by
removing a point is set into relation to its associated horizontal accuracy,
determined as 6m * HDOP. If there is timestamp information, the distance to the interpolated point between
the two neighboring points is used instead of the distance to their connecting line.
</p><p>
The effect of the relative method is similar to a combination of
the crosstrack method with the discard filter: points are removed preserving the
overall shape of the route (track), but preferably those that are unreliable.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="filter_swap"></a>Swap latitude and longitude of all loaded points (swap)</h2></div></div></div><p>
   Simple filter to swap the coordinate values (latitude and longitude) of all
   points. This can be helpful for wrong defined/coded data. Or if you think, you can use
   one of our xcsv formats, but latitude and longitude are in opposite order.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="filter_transform"></a>Transform waypoints into a route, tracks into routes, ... (transform)</h2></div></div></div><p>
  This filter can be used to convert GPS data between different data types.
</p><p>
  Some GPS data formats support only some subset of waypoints, tracks,
  and routes.  The transform filter allows you to convert between these
  types.  For example, it can be used to convert a pile of waypoints (such
  as those from a CSV file) into a track or vice versa.
</p><p>
  The following example show you how to create a route from a waypoint table.
</p><p><strong class="userinput"><code>gpsbabel -i csv -f waypts.txt -x transform,rte=wpt -o gpx -F route.gpx</code></strong></p><p>
  Only the first letter of option value decides which transformation will be done.
  Depending on the used option it can be only 'W' for waypoints, 'R' for routes or
  'T' for tracks.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_transform_o_wpt"></a>wpt option</h3></div></div></div><p>
      Transform track(s) or route(s) into waypoint(s) [R/T].
    </p><p>
This option selects the destination type of this filter to be waypoints.  
Choose this when you want to convert tracks or routes into waypoints.
</p><div class="example"><a id="transform_to_wpt"></a><div class="example-title">Example 4.21. Converting a track to a sequence of waypoints</div><div class="example-contents"><p>
Say you you have a KML file that contains a track but you want to convert it to a CSV file that can contain only waypoints, perhaps to import into a spreadsheet.  Use the following command:
</p><p><strong class="userinput"><code>gpsbabel -i kml -f blah.kml -x transform,wpt=trk -o csv -F blah.txt</code></strong></p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_transform_o_rte"></a>rte option</h3></div></div></div><p>
      Transform waypoint(s) or track(s) into route(s) [W/T].
    </p><p>
This option selects the destination type of this filter to be routes.  Choose this when you want to convert tracks into waypoints routes.  A single route will be created in the sequence they appear in the input.
</p><div class="example"><a id="transform_to_rte"></a><div class="example-title">Example 4.22. Converting a pile of waypoints to a GPX route</div><div class="example-contents"><p>
Say you you have a data file that came from CSV file that you want to convert  
to a GPX route that can be loaded into Mapsource.  Use the following command:
</p><p><strong class="userinput"><code>gpsbabel -i csv -f blah.txt -x transform,rte=wpt -o gdb -F blah.gdb</code></strong></p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_transform_o_trk"></a>trk option</h3></div></div></div><p>
      Transform waypoint(s) or route(s) into tracks(s) [W/R].
    </p><p>
This option selects the destination type of this filter to be tracks.  
Choose this when you want to create tracks from a list of waypoints or routes. 
A single track will be created in the sequence they appear in the input.
</p><div class="example"><a id="transform_to_trk"></a><div class="example-title">Example 4.23. Converting a pile of waypoints to a GPX track</div><div class="example-contents"><p>
Say you you have a data file that came from CSV file that you want to convert  
to a GPX track that can be loaded into Mapsource.  Use the following command:
</p><p><strong class="userinput"><code>gpsbabel -i csv -f blah.txt -x transform,trk=wpt -o gdb -F blah.gdb</code></strong></p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_transform_o_rptdigits"></a>rptdigits option</h3></div></div></div><p>
      Number of digits in generated names.
    </p><p>
This option lets you configure how many digits GPSBabel uses for numbering generated route point names.
</p><p>
When GPSBabel creates route points during the transformation process these points are sequentially numbered and named "RPTxxx" where xxx represent the number. By default GPSBabel uses 3 digits for these numbers. Rationale: This way a large number of route points can be uniquely named while the generated names are limited to 6 characters. This limitation is imposed by specific GPS-devices.
</p><p>
Using this option GPSBabel can be configured to use less or more digits for the generated names. This option is best used in conjunction with the rptname option.
</p><div class="example"><a id="transform_rptdigits"></a><div class="example-title">Example 4.24. Convert a GPX track to a GPX route, deleting the original track, using 2 digits for the generated numbers.</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i gpx -f track.gpx -x transform,wpt=trk,del,rptdigits=2 -o gpx -F route.gpx</code></strong></p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_transform_o_rptname"></a>rptname option</h3></div></div></div><p>
      Use source name for route point names.
    </p><p>
With this option you can decide to let GPSBabel name generated route points according to their source track name.
</p><p>
GPSBabel creates route points during the transformation process named "RPTxxx" where xxx is a numeric part.</p><p>
Using this option GPSBabel can be configured to replace the "RPT" part of the generated names by the name of the source track during the transformation process. This is especially usefull if several differently named tracks are contained in the source file which should each be transformed into routes.
</p><div class="example"><a id="transform_rptname"></a><div class="example-title">Example 4.25. Convert a GPX track to a GPX route, deleting the original track, naming the generated points like the original track name.</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i gpx -f track.gpx -x transform,wpt=trk,del,rptname=y -o gpx -F route.gpx</code></strong></p></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_transform_o_del"></a>del option</h3></div></div></div><p>
      Delete source data after transformation.
    </p><p>
This option, when used in connection with the wpt, rte, or trk options, tells
GPSBabel to delete the source data after conversion.  This is most useful if 
you are trying to avoid duplicated data in the output.
</p><div class="example"><a id="transform_del"></a><div class="example-title">Example 4.26. Convert a GPX track to GPX waypoints, tossing the original track</div><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -i gpx -f blah.gpx -x transform,wpt=trk,del -o gpx -F converted.gpx</code></strong></p></div></div><br class="example-break" /></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="filter_validate"></a>Validate internal data structures (validate)</h2></div></div></div><p>
  This filter can be used to check internal data structures for validity.  The output of the filter is identical to the input, but if corruption is found a fatal error will be issued.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_validate_o_checkempty"></a>checkempty option</h3></div></div></div><p>
      Check for empty input.
    </p><p>
This option will cause a fatal error if there are no waypoints, no route waypoints and no track waypoints, i.e. the reader didn't produce anything.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_validate_o_debug"></a>debug option</h3></div></div></div><p>
      Output debug messages instead of possibly issuing a fatal error.
    </p><p>
This option will output verbose messages reporting the state of the internal data structures holding waypoints, routes and tracks.  Detected problems will normally produce a fatal error, but with this option in effect no error will be thrown allowing continued processing. 
</p></div></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="Datums"></a>Appendix A. Supported Datums</h1></div></div></div><p>
Some formats in GPSBabel support multiple datums.  For example, the 
<code class="option">datum</code> option to the 
<a class="link" href="#fmt_garmin_txt" title="Garmin MapSource - txt (tab delimited) (garmin_txt)">garmin_txt</a> format allows you to specify
a datum for the output file.  
</p><p>
The following is a list of the datums supported by GPSBabel.
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>Adindan</td><td>Cuba NAD27</td><td>La Reunion</td><td>Qornoq</td></tr><tr><td>AFG</td><td>Cyprus</td><td>Liberia 1964</td><td>Quatar National</td></tr><tr><td>Ain-El-Abd</td><td>Djakarta(Batavia)</td><td>Luzon</td><td>Rome 1940</td></tr><tr><td>Alaska-NAD27</td><td>DOS 1968</td><td>Mahe 1971</td><td>S-42(Pulkovo1942)</td></tr><tr><td>Alaska-Canada</td><td>Easter lsland 1967</td><td>Marco Astro</td><td>S.E.Asia_(Indian)</td></tr><tr><td>Anna-1-Astro</td><td>Egypt</td><td>Masirah Is. Nahrwan</td><td>SAD-69/Brazil</td></tr><tr><td>ARC 1950 Mean</td><td>European 1950</td><td>Massawa</td><td>Santa Braz</td></tr><tr><td>ARC 1960 Mean</td><td>European 1950 mean</td><td>Merchich</td><td>Santo (DOS)</td></tr><tr><td>Asc Island 58</td><td>European 1979 mean</td><td>Mexico NAD27</td><td>Sapper Hill 43</td></tr><tr><td>Astro B4</td><td>Finnish Nautical</td><td>Midway Astro 61</td><td>Schwarzeck</td></tr><tr><td>Astro Beacon E</td><td>Gandajika Base</td><td>Mindanao</td><td>Sicily</td></tr><tr><td>Astro pos 71/4</td><td>Geodetic Datum 49</td><td>Minna</td><td>Sierra Leone 1960</td></tr><tr><td>Astro stn 52</td><td>Ghana</td><td>Montjong Lowe</td><td>S. Am. 1969 mean</td></tr><tr><td>Australia Geo 1984</td><td>Greenland NAD27</td><td>Nahrwan</td><td>South Asia</td></tr><tr><td>Bahamas NAD27</td><td>Guam 1963</td><td>Naparima BWI</td><td>Southeast Base</td></tr><tr><td>Bellevue IGN</td><td>Gunung Segara</td><td>North America 83</td><td>Southwest Base</td></tr><tr><td>Bermuda 1957</td><td>Gunung Serindung 1962</td><td>N. America 1927 mean</td><td>Tananarive Obs 25</td></tr><tr><td>Bukit Rimpah</td><td>GUX1 Astro</td><td>Observatorio 1966</td><td>Thai/Viet (Indian)</td></tr><tr><td>Camp_Area_Astro</td><td>Herat North</td><td>Old Egyptian</td><td>Timbalai 1948</td></tr><tr><td>Campo_Inchauspe</td><td>Hjorsey 1955</td><td>Old Hawaiian_mean</td><td>Tokyo mean</td></tr><tr><td>Canada_Mean(NAD27)</td><td>Hong Kong 1963</td><td>Old Hawaiian Kauai</td><td>Tristan Astro 1968</td></tr><tr><td>Canal_Zone_(NAD27)</td><td>Hu-Tzu-Shan</td><td>Old Hawaiian Maui</td><td>United Arab Emirates</td></tr><tr><td>Canton_Island_1966</td><td>Indian</td><td>Old Hawaiian Oahu</td><td>Viti Levu 1916</td></tr><tr><td>Cape</td><td>Iran</td><td>Oman</td><td>Wake Eniwetok 60</td></tr><tr><td>Cape_Canaveral_mean</td><td>Ireland 1965</td><td>OSGB36</td><td>WGS 72</td></tr><tr><td>Carribean NAD27</td><td>ISTS 073 Astro 69</td><td>Pico De Las Nieves</td><td>WGS 84</td></tr><tr><td>Carthage</td><td>Johnston Island 61</td><td>Pitcairn Astro 67</td><td>Yacare</td></tr><tr><td>Cent America NAD27</td><td>Kandawala</td><td>S. Am. 1956 mean(P)</td><td>Zanderij</td></tr><tr><td>Chatham 1971</td><td>Kerguelen Island</td><td>S. Chilean 1963 (P)</td><td>Sweden</td></tr><tr><td>Chua Astro</td><td>Kertau 48</td><td>Puerto Rico</td><td> </td></tr><tr><td>Corrego Alegre</td><td>L.C. 5 Astro</td><td>Pulkovo 1942</td><td> </td></tr></table></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="GarminIcons"></a>Appendix B. Garmin Icons</h1></div></div></div><p>
Following is a list of the valid values for the 
<a class="link" href="#fmt_garmin" title="Garmin serial/USB protocol (garmin)">garmin</a> <code class="option">deficon</code> option.
These values are also used internally by the 
<a class="link" href="#fmt_gdb" title="Garmin MapSource - gdb (gdb)">GDB</a>,
<a class="link" href="#fmt_bcr" title="Motorrad Routenplaner (Map&amp;amp;Guide) .bcr files (bcr)">BCR</a>,
<a class="link" href="#fmt_mapsource" title="Garmin MapSource - mps (mapsource)">Mapsource</a>,
<a class="link" href="#fmt_pcx" title="Garmin PCX5 (pcx)">PCX</a>, and
<a class="link" href="#fmt_psitrex" title="KuDaTa PsiTrex text (psitrex)">PSITrex</a> 
formats.
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>ATV</td><td>Contact, Glasses</td><td>Hunting Area</td><td>Number 0, Green</td><td>Scales</td></tr><tr><td>Airport</td><td>Contact, Goatee</td><td>Ice Skating</td><td>Number 0, Red</td><td>Scenic Area</td></tr><tr><td>Amusement Park</td><td>Contact, Kung-Fu</td><td>Information</td><td>Number 1, Blue</td><td>School</td></tr><tr><td>Anchor</td><td>Contact, Panda</td><td>Intersection</td><td>Number 1, Green</td><td>Seafood</td></tr><tr><td>Anchor Prohibited</td><td>Contact, Pig</td><td>Intl freeway hwy</td><td>Number 1, Red</td><td>Seaplane Base</td></tr><tr><td>Animal Tracks</td><td>Contact, Pirate</td><td>Intl national hwy</td><td>Number 2, Blue</td><td>Shipwreck</td></tr><tr><td>Asian Food</td><td>Contact, Ranger</td><td>Italian food</td><td>Number 2, Green</td><td>Shopping Center</td></tr><tr><td>Bait and Tackle</td><td>Contact, Smiley</td><td>Large Ramp intersection</td><td>Number 2, Red</td><td>Short Tower</td></tr><tr><td>Ball Park</td><td>Contact, Spike</td><td>Large exit without services</td><td>Number 3, Blue</td><td>Shower</td></tr><tr><td>Bank</td><td>Contact, Sumo</td><td>Letter A, Blue</td><td>Number 3, Green</td><td>Ski Resort</td></tr><tr><td>Bar</td><td>Controlled Area</td><td>Letter A, Green</td><td>Number 3, Red</td><td>Skiing Area</td></tr><tr><td>Beach</td><td>Convenience Store</td><td>Letter A, Red</td><td>Number 4, Blue</td><td>Skull and Crossbones</td></tr><tr><td>Beacon</td><td>Cover</td><td>Letter B, Blue</td><td>Number 4, Green</td><td>Small City</td></tr><tr><td>Bell</td><td>Covey</td><td>Letter B, Green</td><td>Number 4, Red</td><td>Small Game</td></tr><tr><td>Big Game</td><td>Crossing</td><td>Letter B, Red</td><td>Number 5, Blue</td><td>Soft Field</td></tr><tr><td>Bike Trail</td><td>Dam</td><td>Letter C, Blue</td><td>Number 5, Green</td><td>Square, Blue</td></tr><tr><td>Blind</td><td>Danger Area</td><td>Letter C, Green</td><td>Number 5, Red</td><td>Square, Green</td></tr><tr><td>Block, Blue</td><td>Deli</td><td>Letter C, Red</td><td>Number 6, Blue</td><td>Square, Red</td></tr><tr><td>Block, Green</td><td>Department Store</td><td>Letter D, Blue</td><td>Number 6, Green</td><td>Stadium</td></tr><tr><td>Block, Red</td><td>Diamond, Blue</td><td>Letter D, Green</td><td>Number 6, Red</td><td>State Hwy</td></tr><tr><td>Blood Trail</td><td>Diamond, Green</td><td>Letter D, Red</td><td>Number 7, Blue</td><td>Steak</td></tr><tr><td>Boat Ramp</td><td>Diamond, Red</td><td>Letterbox Cache</td><td>Number 7, Green</td><td>Street Intersection</td></tr><tr><td>Border Crossing (Port Of Entry)</td><td>Diver Down Flag 1</td><td>Levee</td><td>Number 7, Red</td><td>Stump</td></tr><tr><td>Bottom Conditions</td><td>Diver Down Flag 2</td><td>Library</td><td>Number 8, Blue</td><td>Summit</td></tr><tr><td>Bowling</td><td>Dock</td><td>Light</td><td>Number 8, Green</td><td>Swimming Area</td></tr><tr><td>Bridge</td><td>Dot, White</td><td>Live Theater</td><td>Number 8, Red</td><td>TACAN</td></tr><tr><td>Building</td><td>Drinking Water</td><td>Localizer Outer Marker</td><td>Number 9, Blue</td><td>Tall Tower</td></tr><tr><td>Buoy, White</td><td>Dropoff</td><td>Locationless (Reverse) Cache</td><td>Number 9, Green</td><td>Telephone</td></tr><tr><td>Campground</td><td>Elevation point</td><td>Lodge</td><td>Number 9, Red</td><td>Tide/Current PRediction Station</td></tr><tr><td>Car</td><td>Event Cache</td><td>Lodging</td><td>Oil Field</td><td>Toll Booth</td></tr><tr><td>Car Rental</td><td>Exit</td><td>Man Overboard</td><td>Open 24 Hours</td><td>TracBack Point</td></tr><tr><td>Car Repair</td><td>Exit without services</td><td>Marina</td><td>Oval, Blue</td><td>Trail Head</td></tr><tr><td>Cemetery</td><td>Fast Food</td><td>Medical Facility</td><td>Oval, Green</td><td>Tree Stand</td></tr><tr><td>Church</td><td>First approach fix</td><td>Micro-Cache</td><td>Oval, Red</td><td>Treed Quarry</td></tr><tr><td>Circle with X</td><td>Fishing Area</td><td>Mile Marker</td><td>Parachute Area</td><td>Triangle, Blue</td></tr><tr><td>Circle, Blue</td><td>Fishing Hot Spot Facility</td><td>Military</td><td>Park</td><td>Triangle, Green</td></tr><tr><td>Circle, Green</td><td>Fitness Center</td><td>Mine</td><td>Parking Area</td><td>Triangle, Red</td></tr><tr><td>Circle, Red</td><td>Flag</td><td>Missed approach point</td><td>Pharmacy</td><td>Truck</td></tr><tr><td>City (Capitol)</td><td>Flag, Blue</td><td>Movie Theater</td><td>Picnic Area</td><td>Truck Stop</td></tr><tr><td>City (Large)</td><td>Flag, Green</td><td>Multi-Cache</td><td>Pin, Blue</td><td>Tunnel</td></tr><tr><td>City (Medium)</td><td>Flag, Red</td><td>Multi-Cache</td><td>Pin, Green</td><td>U Marina</td></tr><tr><td>City (Small)</td><td>Food Source</td><td>Museum</td><td>Pin, Red</td><td>U stump</td></tr><tr><td>City Hall</td><td>Forest</td><td>Navaid, Amber</td><td>Pizza</td><td>US hwy</td></tr><tr><td>Civil</td><td>Furbearer</td><td>Navaid, Black</td><td>Police Station</td><td>Ultralight Area</td></tr><tr><td>Coast Guard</td><td>Gambling/casino</td><td>Navaid, Blue</td><td>Post Office</td><td>Unknown Cache</td></tr><tr><td>Contact, Afro</td><td>Gas Station</td><td>Navaid, Green</td><td>Post Office</td><td>Upland Game</td></tr><tr><td>Contact, Alien</td><td>Geocache</td><td>Navaid, Green/Red</td><td>Private Field</td><td>VHF Omni-range</td></tr><tr><td>Contact, Ball Cap</td><td>Geocache Found</td><td>Navaid, Green/White</td><td>Puzzle Cache</td><td>VOR-DME</td></tr><tr><td>Contact, Big Ears</td><td>Geographic place name, Man-made</td><td>Navaid, Orange</td><td>RV Park</td><td>VOR/TACAN</td></tr><tr><td>Contact, Biker</td><td>Geographic place name, land</td><td>Navaid, Red</td><td>Radio Beacon</td><td>Virtual cache</td></tr><tr><td>Contact, Blonde</td><td>Geographic place name, water</td><td>Navaid, Red/Green</td><td>Ramp intersection</td><td>Water Hydrant</td></tr><tr><td>Contact, Bug</td><td>Ghost Town</td><td>Navaid, Red/White</td><td>Rectangle, Blue</td><td>Water Source</td></tr><tr><td>Contact, Cat</td><td>Glider Area</td><td>Navaid, Violet</td><td>Rectangle, Green</td><td>Waterfowl</td></tr><tr><td>Contact, Clown</td><td>Golf Course</td><td>Navaid, White</td><td>Rectangle, Red</td><td>Waypoint</td></tr><tr><td>Contact, Dog</td><td>Ground Transportation</td><td>Navaid, White/Green</td><td>Reef</td><td>Webcam Cache</td></tr><tr><td>Contact, Dreadlocks</td><td>Heliport</td><td>Navaid, White/Red</td><td>Residence</td><td>Weed Bed</td></tr><tr><td>Contact, Female1</td><td>Horn</td><td>Non-directional beacon</td><td>Restaurant</td><td>Winery</td></tr><tr><td>Contact, Female2</td><td>Hotel</td><td>Null</td><td>Restricted Area</td><td>Wrecker</td></tr><tr><td>Contact, Female3</td><td>House</td><td>Number 0, Blue</td><td>Restroom</td><td>Zoo</td></tr></table></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="Styles"></a>Appendix C. GPSBabel XCSV Style Files</h1></div></div></div><div class="toc"><div class="toc-title">Table of Contents</div><dl class="toc"><dt><span class="section"><a href="#styles_intro">Introduction to GPSBabel Styles</a></span></dt><dt><span class="section"><a href="#style_intro2">Style file overview</a></span></dt><dt><span class="section"><a href="#styles_internal_const">Internal Constants</a></span></dt><dt><span class="section"><a href="#style_global">Global Properties of the File</a></span></dt><dt><span class="section"><a href="#style_behavior">GPSBabel Behavior Directives</a></span></dt><dt><span class="section"><a href="#style_layout">Defining the Layout of the File</a></span></dt><dt><span class="section"><a href="#style_define">Defining Fields Within the File</a></span></dt><dt><span class="section"><a href="#style_examples">Examples</a></span></dt><dt><span class="section"><a href="#style_notes">Miscellaneous Notes</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="styles_intro"></a>Introduction to GPSBabel Styles</h2></div></div></div><p>
Often it is desirable to add a new file format for "one-off" work (perhaps
you want to export something to a spreadsheet or graphing program) or to read
a format that GPSBabel does not yet support.   For suitably simple formats,
this can be done by a user with no programming experience by providing a 
GPSBabel style file.
</p><p>
For a format to be described by a style file, it must be predictable and 
generally readable by humant.  Formats with binary or unreadable content 
are not good fits for this scheme.  It should have:
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>A fixed header at the beginning, if it has any at all. This is called a 'prologue'.</td></tr><tr><td>Waypoints that are grouped by fixed separators, often a newline.  In style file parlance, this is called a 'record'.</td></tr><tr><td>Traits of that waypoint described in that record.  In the style files, these are called 'fields' and examples may include longitude or a name.</td></tr><tr><td>Fields that are grouped by fixed separators, often a comma or a tab.  In the style files, this is called the field separator. Fields may be enclosed by characters, such as a double quote.</td></tr><tr><td>A fixed footer at the end, if it has any at all.  This is called the 'epilogue'.</td></tr></table><p>
</p><p>
Once you have created a style file that describes the file format you have
or want, you must tell GPSBabel to use the xcsv format and have the xcsv 
format use that file.  If you created a new style file called 
"mystyle.style" and you want to write the  waypoints from
a GPX file named "mine.gpx" to it, you would issue a command like:
</p><p><strong class="userinput"><code>gpsbabel -i gpx -f mine.gpx -o xcsv,style=mystyle.style -F mine.new</code></strong></p><p>
You might then examine <code class="filename">mine.new</code> to see if it met
your expectations.  If not, you could continue to tweak 
<code class="filename">mystyle.style</code> until it did, rerunning the above
command each time.  If 'mystyle' is a format 
that describes a popular program or is likely to be of use to others, you can
then share <code class="filename">mystyle.style</code> with other GPSBabel users.
Send it along with a coherent description to the GPSBabel-misc mailing 
list for consideration to be included in a future version.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="style_intro2"></a>Style file overview</h2></div></div></div><p>
The first and foremost important step is understanding how the style
file is laid out itself.  The format is:
</p><pre class="screen">DIRECTIVE&lt;whitespace&gt;VALUE</pre><p>
Where &lt;whitespace&gt; is one or more spaces or tabs.  There should
be no spaces or tabs at the beginning of the line; all directives start
at the left edge in column zero.
</p><p>
An example style format is shown here:
</p><div class="literallayout"><p><br />
<br />
# Format: MS S&amp;T 2002/2003<br />
# Author: Alex Mottram<br />
#   Date: 12/09/2002<br />
#<br />
<br />
DESCRIPTION 		Microsoft Streets and Trips 2002-2006<br />
EXTENSION               txt<br />
<br />
#<br />
# FILE LAYOUT DEFINITIIONS:<br />
#<br />
FIELD_DELIMITER		TAB<br />
RECORD_DELIMITER	NEWLINE<br />
BADCHARS		,"<br />
<br />
PROLOGUE	Name	Latitude	Longitude	Description	URL	Type	Container	Diff	Terr<br />
<br />
#<br />
# INDIVIDUAL DATA FIELDS, IN ORDER OF APPEARANCE:<br />
# NOTE: MS S&amp;T ONLY IMPORTS DATA, IT DOESN'T <br />
#       EXPORT THIS ANYWHERE SO WE CAN HAVE OUR <br />
#       WAY WITH THE FORMATTING. <br />
#<br />
IFIELD	SHORTNAME, "", "%s"		# Name<br />
IFIELD	LAT_DECIMAL, "", "%f"		# Latitude<br />
IFIELD	LON_DECIMAL, "", "%f"		# Longitude<br />
IFIELD	DESCRIPTION, "", "%s"		# Name 2 (Big Description)<br />
IFIELD	URL, "", "%s"			# URL<br />
IFIELD	GEOCACHE_TYPE, "", "%s"		# Geocache Type<br />
IFIELD	GEOCACHE_CONTAINER, "", "%s"	# Geocache Type<br />
IFIELD	GEOCACHE_DIFF, "", "%3.1f"	# Geocache Type<br />
IFIELD	GEOCACHE_TERR, "", "%3.1f"	# Geocache Type<br />
</p></div><p>
Each of these lines will be explained in the following sections.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="styles_internal_const"></a>Internal Constants</h2></div></div></div><p>
A few internal constants are defined in the XCSV parser to make the style
file simpler.  They may or may not be used and are optional in most cases. 
Note that only certain style file directives map these constants.
</p><p>
</p><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Style Constant</th><th>Maps to Char(s)</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">COMMA</td><td class="seg">,</td></tr><tr class="seglistitem"><td class="seg">COMMASPACE</td><td class="seg">,&lt;space&gt;</td></tr><tr class="seglistitem"><td class="seg">SINGLEQUOTE</td><td class="seg">'</td></tr><tr class="seglistitem"><td class="seg">DOUBLEQUOTE</td><td class="seg">"</td></tr><tr class="seglistitem"><td class="seg">COLON</td><td class="seg">:</td></tr><tr class="seglistitem"><td class="seg">SEMICOLON</td><td class="seg">;</td></tr><tr class="seglistitem"><td class="seg">NEWLINE</td><td class="seg">\n</td></tr><tr class="seglistitem"><td class="seg">CR</td><td class="seg">\r</td></tr><tr class="seglistitem"><td class="seg">CRNEWLINE</td><td class="seg">\r\n</td></tr><tr class="seglistitem"><td class="seg">TAB</td><td class="seg">\t</td></tr><tr class="seglistitem"><td class="seg">SPACE</td><td class="seg">&lt;space&gt;</td></tr><tr class="seglistitem"><td class="seg">HASH</td><td class="seg">#</td></tr><tr class="seglistitem"><td class="seg">PIPE</td><td class="seg">|</td></tr><tr class="seglistitem"><td class="seg">WHITESPACE</td><td class="seg">see below</td></tr></tbody></table></div><p>
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_const_whitespace"></a>WHITESPACE</h3></div></div></div><p>
The WHITESPACE constant has special properties.  When reading data, 
WHITESPACE refers to sequential runs of SPACES and/or TABS.  When
writing data, WHITESPACE is always a single SPACE.
</p><p>
For example, the following line:
</p><pre class="screen">SOME_NAME       30.1208 -91.1365    SOME OTHER NAME
</pre><p>
Parses into the following data fields: 
</p><pre class="screen">SOME_NAME,30.1208,-91.1365,SOME,OTHER,NAME
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_const_comments"></a>COMMENTS</h3></div></div></div><p>
Anything after a hash (#) on a line is not parsed.  For example:
</p><pre class="screen">#THIS ENTIRE LINE IS A COMMENT.
#FIELD	LAT_DECIMAL, "", "%f"   THIS ENTIRE LINE IS A COMMENT
FIELD LAT_DECIMAL, "", "%f"  # ONLY THIS SENTENCE IS A COMMENT.
</pre></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="style_global"></a>Global Properties of the File</h2></div></div></div><p>
There are a few available directives to describe general traits of the 
file being described and not specific data within the file itself.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_global_description"></a>DESCRIPTION</h3></div></div></div><p>
This is the description of the file format being described. This text
appears in the help screens and in menus used by the various GUI wrappers.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_global_extension"></a>EXTENSION</h3></div></div></div><p>
This directive gives the filename extension generally associated with
this file.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_global_encoding"></a>ENCODING</h3></div></div></div><p>
Describes the character set used by this format.  The value given
must be one listed by 'gpsbabel -l'.    example:
</p><pre class="screen">   ENCODING          UTF-8	# Use UTF-8 for input and output.
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_global_datum"></a>DATUM</h3></div></div></div><p>
This value specifies the GPS datum to be used on read or write. Valid values for this 
option are listed in <a class="xref" href="#Datums" title="Appendix A. Supported Datums">Appendix A, <em>Supported Datums</em></a>.
</p><pre class="screen">   DATUM             European 1950
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_global_datatype"></a>DATATYPE</h3></div></div></div><p>
Specifies the kind of data we have to read or write.
</p><p>
By default all data are seen as waypoint data. With DATATYPE you are now able to bind
a specific type to this format. Possible values are WAYPOINT, ROUTE or TRACK.
</p><pre class="screen">   DATATYPE          ROUTE # route-only format
</pre></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="style_behavior"></a>GPSBabel Behavior Directives</h2></div></div></div><p>
There are a few available directives to control some of the internal 
processing functions of GPSbabel.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_behave_shortlen"></a>SHORTLEN</h3></div></div></div><p>
   This sets the maximum allowed shortname length when using the internal
   shortname synthesizer.
</p><p>
   example:
</p><pre class="screen">   SHORTLEN	16	# shortnames will be at most 16 characters long.
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_behave_shortwhite"></a>SHORTWHITE</h3></div></div></div><p>
   This tells the shortname synthesizer whether or not to allow whitespace
   in the synthesized shortnames.  Allowed values are zero and one.
</p><p>
   example:
</p><pre class="screen">   SHORTWHITE	0	# Do not allow whitespace in shortname.
   SHORTWHITE   1	# Allow whitespace in shortname.
</pre></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="style_layout"></a>Defining the Layout of the File</h2></div></div></div><p>
The first few directives define the layout the physical file itself:
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_layout_field"></a>FIELD_DELIMITER</h3></div></div></div><p>
   The field delimiter defines the character(s) that separate the fields in 
   the rows of data inside the XCSV file.  Common field delimiters are commas 
   and tabs. (referred to as "comma separated values" and "tab separated 
   values")
</p><p>
   examples: 
</p><pre class="screen">   FIELD_DELIMITER    COMMA
   FIELD_DELIMITER    ~
</pre><p>
   The directive FIELD_DELIMITER is parsed for STYLE CONSTANTS as defined in 
   the table above.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_layout_field_enclose"></a>FIELD_ENCLOSER</h3></div></div></div><p>
   The field encloser defines the character(s) that surround the field values.
   Common field enclosers are single and double quote marks. Many styles will
   leave this directive unset. If set, it will be applied to all fields.
</p><p>
   examples: 
</p><pre class="screen">   FIELD_ENCLOSER    DOUBLEQUOTE
   FIELD_ENCLOSER    SINGLEQUOTE
</pre><p>
   The directive FIELD_ENCLOSER is parsed for STYLE CONSTANTS as defined in 
   the table above.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_layout_rec"></a>RECORD_DELIMITER</h3></div></div></div><p>
   The record delimiter defines that character(s) that separate ROWS of 
   data (FIELDS) in the XCSV file.  The most common record delimiters
   are NEWLINE and CR (carriage return).
</p><p>
   examples:
</p><pre class="screen">   RECORD_DELIMITER    NEWLINE
   RECORD_DELIMITER    |
</pre><p>
   The directive RECORD_DELIMITER is parsed for STYLE CONSTANTS as defined 
   in the table above.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_layout_badchars"></a>BADCHARS</h3></div></div></div><p>   
   Bad characters are things that should *never* be written into the XCSV
   file as data on output.  GPSBabel automatically includes any non-blank
   FIELD_DELIMITER and FIELD_ENCLOSER and RECORD_DELIMITER characters as
   BADCHARS by default.
</p><p>
   examples: 
</p><pre class="screen">  BADCHARS    COMMA
  BADCHARS    ~|
</pre><p>
   The directive BADCHARS is parsed for STYLE CONSTANTS as defined in the 
   table above.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_layout_prologue"></a>PROLOGUE</h3></div></div></div><p>
   A prologue is basically constant data that is written to the output
   file BEFORE any waypoints are processed.  PROLOGUE can be defined 
   multiple times in the style file, once for each "line" before the data 
   begins.  This is commonly used in XCSV files as a "header" row.  
</p><p>
   examples: 
</p><pre class="screen">  PROLOGUE	OziExplorer Waypoint File Version 1.1
  PROLOGUE	WGS 84
  PROLOGUE	Symbol,Name,Latitude,Longitude
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_layout_epilogue"></a>EPILOGUE</h3></div></div></div><p>
   An Epilogue is the same as a prologue, except this data is written at 
   the END of the file.  See the examples for PROLOGUE above.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="style_define"></a>Defining Fields Within the File</h2></div></div></div><p>
A field defines data.  There are two different classifications of FIELDS,
IFIELD (file input) and OFIELD (file output).  In the absence of any OFIELDS,
IFIELDS are use as both input and output.  The existence of OFIELDS is 
primarily to allow more flexible mapping of GPSBabel data to output data 
(say, for instance, to map the internal GPSBabel "description" variable to 
two or more fields on output).  For all practical purposes, IFIELDS and 
OFIELDS are defined the same way in the style file.</p><p>The following per-field options are defined:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
   "no_delim_before" is supported on in OFIELD tags to specify that this
   field should be written without a field delimiter before it.  It's
   useful for limited field concatenation.
</p></li><li class="listitem"><p>
   "absolute" is supported on OFIELD tags for lat and lon to indicate
   that only absolute values (never negative) are to be printed.
</p></li><li class="listitem"><p>
   "optional" is supported only OFIELD tags and indicates that the
   field may or may not be available in the source data.  If the
   field is absent, no trailing field separator is written.
</p><p>
   This attribute is most useful when paired with "no_delim_before" as
   it allows you to concatenate fields without concern for whether those
   fields are actually populated or not.
</p></li></ul></div><p>
There are several different types of fields that may be defined.  Each field 
consists of three pieces of information: the FIELD TYPE, a DEFAULT VALUE, and 
a PRINTF CONVERSION (for output).  In many cases, not all pieces are used,
but all 3 pieces are required.   Additionally, an fourth field is supported
that modifies the behaviour of the field being described.
</p><p>
FIELDS should be defined in the style file in the logical order that they
appear in the data, from left to right.  This is the order in which they are
parsed from input and written to output.
</p><p>
The fields used by the XCSV parser are as follows:
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_ignore"></a>IGNORE</h3></div></div></div><p>
   IGNORE fields are, guess what, ignored on input.   Internally, IGNORE 
   fields are treated as CHARACTER data, and as such, require a printf 
   conversion for a character array.  
</p><p>
examples:
</p><pre class="screen">   IFIELD IGNORE,"","%14.14s"   # (writes a 14 character blank field)
   IFIELD IGNORE,"","%s"        # (writes a blank field on output)
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_constant"></a>CONSTANT</h3></div></div></div><p>
   CONSTANT fields are, of course, constant.  They are ignored on input, 
   however they write CONSTANT data on output.  As such, they require a 
   DEFAULT VALUE and a printf conversion for a character array. 
</p><p>
examples:
</p><pre class="screen">   IFIELD CONSTANT,"FFFFFF","%s"   # (writes "FFFFFF" in the field)
   IFIELD CONSTANT,"01/01/70","%s" # (a constant date field)
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_index"></a>INDEX</h3></div></div></div><p>
   An INDEX field is used ONLY on output.  The INDEX constant defines a field 
   that, at output, contains the sequence number of the waypoint being 
   written, starting at 0.  An index is managed internally as an INTEGER 
   and requires an INTEGER printf conversion.  An INDEX has one special
   property.  The DEFAULT VALUE of the index is added to the index 
   on each iteration (to allow indexes starting at 1, 100, etc..).   
</p><p>
examples:
</p><pre class="screen">   IFIELD INDEX,"0","%04d"     # (Starts counting at zero)
   IFIELD INDEX,"","%04d"      # (Starts counting at zero)
   IFIELD INDEX,"1","%04d"     # (Starts counting at one)
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_shortname"></a>SHORTNAME</h3></div></div></div><p>
   A SHORTNAME is generally the waypoint name of the data being processed.  
   SHORTNAME maps directly to the GPSBabel variable -&gt;shortname.  A SHORTNAME 
   is CHARACTER data and requires a character array printf conversion.
</p><p>
example:
</p><pre class="screen">   IFIELD SHORTNAME,"","%s"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_description"></a>DESCRIPTION</h3></div></div></div><p>
   A DESCRIPTION is generally a long description of the waypoint.  A 
   DESCRIPTION maps to the GPSBabel variable -&gt;description and is otherwise 
   handled exactly like a SHORTNAME.
</p><p>
examples:
</p><pre class="screen">   IFIELD DESCRIPTION,"","%s" 
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_notes"></a>NOTES</h3></div></div></div><p>
   NOTES are generally everything else about a waypoints. NOTES map to the 
   GPSBabel variable -&gt;notes and is otherwise handled exactly like a 
   SHORTNAME.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_url"></a>URL</h3></div></div></div><p>
   URL is a URL for the waypoint.  URL maps to the GPSBabel variable 
   -&gt;url and is otherwise handled exactly like a SHORTNAME.
</p><p>
example:
</p><pre class="screen">   IFIELD URL,"","%s"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_urllinktext"></a>URL_LINK_TEXT</h3></div></div></div><p>
   URL_LINK_TEXT is a textual description of where a URL points.  
   URL_LINK_TEXT maps to the GPSBabel variable -&gt;url_link_text and 
   is otherwise handled exactly like a SHORTNAME.
</p><p>
example:
</p><pre class="screen">   IFIELD URL_LINK_TEXT,"","%s" 
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_icondescr"></a>ICON_DESCR</h3></div></div></div><p>
   ICON_DESCR is a textual description of an icon type for a waypoint.
   ICON_DESCR maps to the GPSBabel variable -&gt;icon_desc and is otherwise 
   handled exactly like a SHORTNAME.
</p><p>
example:
</p><pre class="screen">   IFIELD ICON_DESCR,"","%s" 
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_latdec"></a>LAT_DECIMAL</h3></div></div></div><p>
   LAT_DECIMAL defines LATITUDE in DECIMAL format.  Note that this is a PURE 
   signed decimal format (i.e. -91.0000).  This data is handled internally as 
   a DOUBLE PRECISION FLOAT and requires a FLOATING POINT printf conversion.
</p><p>
example:
</p><pre class="screen">   IFIELD LAT_DECIMAL,"","%f"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_londec"></a>LON_DECIMAL</h3></div></div></div><p>
   See LAT_DECIMAL, except LON_DECIMAL defines LONGITUDE.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_latint32"></a>LAT_INT32DEG</h3></div></div></div><p>
   LAT_INT32DEG defines LATITUDE in what I call INT32DEGREES.  This value is 
   a signed LONG INTEGER and requires a LONG INTEGER printf conversion.
   (This format is only used by some DeLorme products.)
</p><p>
example:
</p><pre class="screen">   IFIELD LAT_INT32DEG,"","%ld"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_lonint32"></a>LON_INT32DEG</h3></div></div></div><p>
   See LON_INT32DEG except LON_INT32DEG defines LONGITUDE.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_latdirdec"></a>LAT_DECIMALDIR / LAT_DIRDECIMAL</h3></div></div></div><p>
   LAT_DECIMALDIR and LAT_DIRDECIMAL  define LATITUDE in DECIMAL format 
   with the added bonus of a 'N/S' or 'E/W' direction character.  This data 
   is handled internally as a DOUBLE PRECISION FLOAT and a single 
   CHARACTER and requires a FLOATING POINT as well as a CHARACTER printf 
   conversion.  The only difference between the two is whether the directional
   character appears before (LAT_DIRDECIMAL) or after (LAT_DECIMALDIR) the
   decimal number.
</p><p>
examples:
</p><pre class="screen">   IFIELD LAT_DECIMALDIR,"","%f %c"     #  (writes 31.333 N)
   IFIELD LAT_DIRDECIMAL,"","%c %f"     #  (writes N 31.333)
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_londirdec"></a>LON_DECIMALDIR / LON_DIRDECIMAL</h3></div></div></div><p>
   Same as LAT_DECIMALDIR / LAT_DIRDECIMAL except LON_ defines LONGITUDE.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_latlondir"></a>LAT_DIR / LON_DIR</h3></div></div></div><p>
   LAT_DIR returns the single character 'N' or 'S' depending on the 
   hemisphere of the latitude.  LON_DIR returns 'E' or 'W' depending on
   the hemisphere of the longitude.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_lathuman"></a>LAT_HUMAN_READABLE</h3></div></div></div><p>
   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 conversions, 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.
</p><p>
examples:
</p><pre class="screen">
   #  (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" 
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_map_en_bng"></a>MAP_EN_BNG</h3></div></div></div><p>
   MAP_EN_BNG converts coordinates from/to British National Grid (BNG).
</p><p>
   The only supported order of the items is: Map,Easting,Northing.
   During output all coordinates have to be located within this limited area.
</p><p>
examples:
</p><pre class="screen">
   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")
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_lonhuman"></a>LON_HUMAN_READABLE</h3></div></div></div><p>
   See LAT_HUMAN_READABLE except LON_HUMAN_READABLE defines LONGITUDE.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_latlonhuman"></a>LATLON_HUMAN_READABLE</h3></div></div></div><p>
   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.
</p><p>
example:
</p><pre class="screen">   IFIELD LATLON_HUMAN_READABLE,"","%c %d %f"
           # (writes "N 31 40.126 W 85 09.62" as a single field)
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_latnmea"></a>LAT_NMEA</h3></div></div></div><p>
   Defines the latitude in the format used by the NMEA standard which is
   degrees multiplied by 100 plus decimal minutes.
</p><p>
example:
</p><pre class="screen">   IFIELD  LAT_NMEA, "%f", "%08.3f"     # (writes  3558.322)
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_latddmmdir"></a>LAT_DDMMDIR</h3></div></div></div><p>
Derived from the LAT_NMEA latitude format, with degrees * 100 plus decimal 
minutes, but using an additional specifier to position the  'N' or 'S' instead of a leading minus sign (or 
absence thereof) to give direction from zero.
</p><p>
</p><pre class="screen"> IFIELD LAT_DDMMDIR, "%f", "%08.3f%c" # (writes "5334.192S" giving -53.56987 degrees latitude)
</pre><p>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_lonnmea"></a>LON_NMEA</h3></div></div></div><p>
   Defines the longitude in the format used by the NMEA standard which is
   degrees multiplied by 100 plus decimal minutes.
</p><p>
Example:
</p><pre class="screen">   IFIELD  LON_NMEA, "%f", "%010.3f"  # (writes -08708.082)
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_londdmmdir"></a>LON_DDMMDIR</h3></div></div></div><p>
Derived from the LON_NMEA longitude format, with degrees * 100 plus decimal minutes, but using an additional character format character to position the
'E' or 'W' instead of a leading minus sign (or absence thereof) to give direction from zero.
</p><p>
Example:
</p><pre class="screen"> IFIELD LON_DDMMDIR, "%f", "%010.3f%c" # (writes "01232.745W" giving -12.54575 degrees
longitude)
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_latlon_10ex"></a>LAT_10EX / LON_10EX</h3></div></div></div><p>
   Defines the latitude or longitude in the format used i.e. by TomTom Navigator
   itinerary files. It is degrees multiplied by 10 power X. X have to be replaced with
   a valid decimal value. A factor of 10000 would be generated by LAT_10E5 as shown
   in the examples below.
</p><p>
examples:
</p><pre class="screen">   IFIELD  LAT_10E5, "%f", "%.f"       # (writes  3558322)
</pre><pre class="screen">   IFIELD  LON_10E5, "%f", "%.f"       # (writes -8708082)
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_utm"></a>UTM</h3></div></div></div><p>A location in UTM has several components: a zone, a northing, and an easting.   The UTM format specifier is the most common representation of these.
</p><p>example: </p><pre class="screen">
IFIELD UTM, "%s" # writes 6S 519045 3984035  -the easting is first by convention.</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_utm_easting"></a>UTM_EASTING</h3></div></div></div><p>This is the decimal component representing the easting
</p><p>example: </p><pre class="screen">
IFIELD UTM_EASTING, "", "%d"  # outputs 519045
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_utm_northing"></a>UTM_NORTHING</h3></div></div></div><p>
This is the decimal component representing the northing
</p><p>example: </p><pre class="screen">
IFIELD UTM_NORTHING "", "%d"  # outputs 3984035
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_utm_zone"></a>UTM_ZONE</h3></div></div></div><p>The UTM zone.
</p><p>example: </p><pre class="screen">
IFIELD UTM_ZONE "", "%d"  # outputs 6
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_utm_zonec"></a>UTM_ZONEC</h3></div></div></div><p>
The UTM Zone character.
</p><p>example: </p><pre class="screen">
IFIELD UTM_ZONEC "", "%d"  # outputs S
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_utm_zonef"></a></h3></div></div></div><p>
The full UTM zone and latitude band.
</p><p>example: </p><pre class="screen">
IFIELD UTM_ZONEF "", "%d%c"  # outputs 6S
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_altfeet"></a>ALT_FEET</h3></div></div></div><p>
   ALT_FEET is the position's ALTITUDE in FEET.  This value is treated as 
   a SIGNED DOUBLE PRECISION FLOAT and requires a FLOATING POINT printf 
   conversion.
</p><p>
example:
</p><pre class="screen">   IFIELD ALT_FEET,"","%.0f"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_altmeters"></a>ALT_METERS</h3></div></div></div><p>
   ALT_METERS is identical to ALT_FEET with the exception that the altitude
   is in METERS.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_heartrate"></a>HEART_RATE</h3></div></div></div><p>
   Heart rate, measured in beats per minute.  Only valid for units with 
   heart rate monitor features (i.e. Garmin Forerunner 301).
</p><p>
example:
</p><pre class="screen">   IFIELD HEART_RATE,"","%d"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_cadence"></a>CADENCE</h3></div></div></div><p>
   Cadence in revolutions per minute.  Only valid for units with 
   heart rate monitor features (i.e. Garmin Edge 305).
</p><p>
example:
</p><pre class="screen">   IFIELD CADENCE,"","%d"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_power"></a>POWER</h3></div></div></div><p>
   Cycling power in Watts.  Only valid for units with power meter
   features (i.e. Garmin Edge 305).
</p><p>
example:
</p><pre class="screen">   IFIELD POWER,"","%.1f"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_temperature"></a>TEMPERATURE</h3></div></div></div><p>
   Temperature in degrees Celsius.
</p><p>
example:
</p><pre class="screen">   IFIELD TEMPERATURE,"","%.1f"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_temperaturef"></a>TEMPERATURE_F</h3></div></div></div><p>
   Temperature in degrees Fahrenheit.
</p><p>
example:
</p><pre class="screen">   IFIELD TEMPERATURE_F,"","%.1f"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_exceltime"></a>EXCEL_TIME</h3></div></div></div><p>
   EXCEL_TIME is the waypoint's creation time, if any.  This is actually
   the decimal days since 1/1/1900 and is handled internally as a DOUBLE
   PRECISION FLOAT and requires a FLOATING POINT printf conversion.
</p><p>
example:
</p><pre class="screen">   IFIELD EXCEL_TIME,"","%11.5f"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_timettime"></a>TIMET_TIME</h3></div></div></div><p>
   TIMET_TIME is the waypoint's creation time, if any.  This is actually
   the integer seconds since 1/1/1970 (let's not start the holy war) and
   is handled internally as a LONG INTEGER and requires a LONG INTEGER
   printf conversion.
</p><p>
example:
</p><pre class="screen">   IFIELD TIMET_TIME,"","%ld"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_timettimems"></a>TIMET_TIME_MS</h3></div></div></div><p>
   TIMET_TIME_MS is the same as TIMET_TIME, but expressed in milliseconds.
   It too is handled internally as a LONG INTEGER and requires a LONG INTEGER
   printf conversion.
</p><p>
example:
</p><pre class="screen">   IFIELD TIMET_TIME_MS,"","%ld"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_yyyymmdd"></a>YYYYMMDD_TIME</h3></div></div></div><p>
   YYYYMMDD_TIME is the waypoint's creation time, if any.  It's a single
   decimal field containing four digits of year, two digits of month, 
   and two digits of date.   Internally it is a LONG INTEGER and thus
   requires a LONG INTEGER printf conversion.
</p><p>
example:
</p><pre class="screen">   IFIELD YYYYMMDD_TIME,"","%ld"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_gmttime"></a>GMT_TIME</h3></div></div></div><p>
   GMT_TIME is the waypoint's creation time, in UTC time zone.  It uses the
   strptime conversion format tags.  
</p><p>
example:
</p><pre class="screen">   IFIELD GMT_TIME,"","%m/%d/%Y %I:%M:%D %p"
</pre><p>
   Search the web for 'strptime man page' for details strptime, but one 
   such page can be found at
<a class="ulink" href="http://www.die.net/doc/linux/man/man3/strptime.3.html" target="_top">http://www.die.net/doc/linux/man/man3/strptime.3.html</a>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_localtime"></a>LOCAL_TIME</h3></div></div></div><p>
 LOCAL_TIME is the waypoint's creation time, in the local
 time zone.  It uses strptime conversion format tags.  See GMT_TIME for a
 reference.
</p><p>
example:
</p><pre class="screen">   IFIELD LOCAL_TIME,"","%y-%m-%d"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_hmsgtime"></a>HMSG_TIME</h3></div></div></div><p>
   HMSG_TIME parses up to three time parts and am/pm string to add
   this value to the previously parsed *_TIME field that contains 
   only a date.  On output, will print the time in UTC.
</p><p>
example:
</p><pre class="screen">   IFIELD HMSG_TIME,"","%d:%d:%d %s"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_hmsltime"></a>HMSL_TIME</h3></div></div></div><p>
   HMSG_TIME parses up to three time parts and am/pm string to add
   this value to the previously parsed *_TIME field that contains 
   only a date.  On output, will print the time in local time.
</p><p>
example:
</p><pre class="screen">   IFIELD HMSL_TIME,"","%dh%dm"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_isotime"></a>ISO_TIME</h3></div></div></div><p>
   ISO_TIME is the waypoint's creation time, in ISO 8601 format, 
   which include time zone information. 
   It is expected to be in the format yyyy-mm-ddThh:mm:sszzzzz
   where zzzzzz is the local time offset or the character Z
   for UTC time.
   On output, UTC 'Z' time zone will always be used.
</p><p>
example:
</p><pre class="screen">   IFIELD ISO_TIME,"","%s"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_isotimems"></a>ISO_TIME_MS</h3></div></div></div><p>
   ISO_TIME_MS is much like ISO_TIME, but expresses milliseconds at the
   end of the timestamp.
   It is thus in the format yyyy-mm-ddThh:mm:ss.SSSzzzzz
   where 'SSS' is milliseconds and zzzzzz is the local time offset 
   or the character Z for UTC time.
   On output, UTC 'Z' time zone will always be used.
</p><p>
example:
</p><pre class="screen">   IFIELD ISO_TIME_MS,"","%s"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_nettime"></a>NET_TIME</h3></div></div></div><p>
  Microsoft dot net represents times in 100 nanoscond intervals since midnight
  Jan 1/0001 GMT, giving absurdly large numbers like 633943150010000000 for 
  mid-November, 2009.  NET_TIME is how to represent those in GPSBabel.
</p><p>
example:
</p><pre class="screen">   IFIELD NET_TIME,"","%f"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_geodiff"></a>GEOCACHE_DIFF</h3></div></div></div><p>
   GEOCACHE_DIFF is valid only for geocaches and represents a DOUBLE 
   PRECISION FLOAT.  This is the geocache "difficulty" rating as defined by
   Groundspeak.  A "three and a half star" cache would therefore be "3.5"
</p><p>
example:
</p><pre class="screen">   IFIELD GEOCACHE_DIFF,"","%3.1f"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_geoterr"></a>GEOCACHE_TERR</h3></div></div></div><p>
   GEOCACHE_TERR is valid only for geocaches and represents a DOUBLE 
   PRECISION FLOAT.  This is the geocache "terrain" rating as defined
   by Groundspeak.  A "three and a half star" cache would therefore be "3.5"
</p><p>
example:
</p><pre class="screen">   IFIELD GEOCACHE_TERR,"","%3.1f"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_geocontainer"></a>GEOCACHE_CONTAINER</h3></div></div></div><p>
   GEOCACHE_CONTAINER is valid only for geocaches and is heavily influenced
   by the Groundspeak container types.   Examples would include "Micro" 
   and "Virtual".
</p><p>
example:
</p><pre class="screen">   GEOCACHE_CONTAINER,"","%s"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_geotype"></a>GEOCACHE_TYPE</h3></div></div></div><p>
   GEOCACHE_TYPE is valid only for geocaches and is heavily influenced
   by the Groundspeak cache types.   Examples would include "Event cache" 
   and "Multi-Cache".
</p><p>
example:
</p><pre class="screen">   GEOCACHE_TYPE,"","%s"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_geoplacer"></a>GEOCACHE_PLACER</h3></div></div></div><p>
   GEOCACHE_PLACER is a string containing the name of the placer of a 
   geocache.   
</p><p>
example:
</p><pre class="screen">   GEOCACHE_PLACER,"","%s"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_isavailable"></a>GEOCACHE_ISAVAILABLE</h3></div></div></div><p>
   GEOCACHE_ISAVAILABLE is a string containing "True" or "False" 
   indicating whether a geocache is currently available or not.  
</p><p>
example:
</p><pre class="screen">   GEOCACHE_ISAVAILABLE,"","%s"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_isarchived"></a>GEOCACHE_ISARCHIVED</h3></div></div></div><p>
   GEOCACHE_ISARCHIVED is a string containing "True" or "False" 
   indicating whether a geocache has been archived.   
</p><p>
example:
</p><pre class="screen">   GEOCACHE_ISARCHIVED,"","%s"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_geofound"></a>GEOCACHE_LAST_FOUND</h3></div></div></div><p>
   A long integer in format YYYYMMDD containing the last time this geocache
   was found.
</p><p>
example:
</p><pre class="screen">   GEOCACHE_LAST_FOUND,"","%ld"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_geohint"></a>GEOCACHE_HINT</h3></div></div></div><p>
   The hint for this geocache.   No additional transformation (such as rot13)
   will be performed on this string.
</p><p>
example:
</p><pre class="screen">   GEOCACHE_HINT,"","%s"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_pathdistmi"></a>PATH_DISTANCE_MILES</h3></div></div></div><p>
   PATH_DISTANCE_MILES outputs the total length of the route or track from
   the start point to the current point, in miles.  This and the altitude
   could be used to create an elevation profile.  PATH_DISTANCE_MILES is
   a DOUBLE PRECISION FLOAT.
</p><p>
   PATH_DISTANCE_MILES is not valid as an input field.
</p><p>
   PATH_DISTANCE_MILES is only meaningful if the data comes from a track
   or a route; waypoint data will generate essentially meaningless output.
</p><p>
example:
</p><pre class="screen">   PATH_DISTANCE_MILES,"","%f"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_pathdistkm"></a>PATH_DISTANCE_KM</h3></div></div></div><p>
   PATH_DISTANCE_KM is like PATH_DISTANCE_MILES except it outputs the 
   length in kilometers. 
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_pathdistm"></a>PATH_DISTANCE_METERS</h3></div></div></div><p>
   PATH_DISTANCE_METERS is like PATH_DISTANCE_MILES except it outputs the 
   length in meters. 
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_pathspeed"></a>PATH_SPEED</h3></div></div></div><p>
   Speed in meters per second. Gpsbabel does NOT calculate this data by 
   default; it is read from the input file if present.  (If not present,
   it may be calculated with the <a class="link" href="#filter_track" title="Manipulate track lists (track)">track</a>
   filter.)
</p><p>
example:
</p><pre class="screen">   PATH_SPEED,"","%f"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_pathspeed_kph"></a>PATH_SPEED_KPH</h3></div></div></div><p>
   Like PATH_SPEED but means kilometers per hour.
</p><p>
example:
</p><pre class="screen">   PATH_SPEED_KPH,"","%.1f"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_pathspeed_mph"></a>PATH_SPEED_MPH</h3></div></div></div><p>
   Like PATH_SPEED but means miles per hour.
</p><p>
example:
</p><pre class="screen">   PATH_SPEED_MPH,"","%.1f"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_pathspeed_knots"></a>PATH_SPEED_KNOTS</h3></div></div></div><p>
   Like PATH_SPEED but means knots (nautical).
</p><p>
example:
</p><pre class="screen">   PATH_SPEED_KNOTS,"","%.1f"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_pathcourse"></a>PATH_COURSE</h3></div></div></div><p>
   Course in degrees.  Gpsbabel does not calculate this data by default; 
   it is read from the input file if present.  (If not present, it may be
   calculated with the <a class="link" href="#filter_track" title="Manipulate track lists (track)">track</a> filter.)
</p><p>
example:
</p><pre class="screen">   PATH_COURSE,"","%f"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_dop"></a>GPS_HDOP / GPS_VDOP / GPS_PDOP</h3></div></div></div><p>
   GPS horizontal / vertical / positional dilution of precision 
   parameters. Needs float conversion.
</p><p>
example:
</p><pre class="screen">   GPS_HDOP,"","%f"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_gpssat"></a>GPS_SAT</h3></div></div></div><p>
   Number of satellites used for determination of the position. Needs
   integer conversion.
</p><p>
example:
</p><pre class="screen">   GPS_SAT,"","%d"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_def_gpsfix"></a>GPS_FIX</h3></div></div></div><p>
   Type of fix (see GPX spec or <a class="link" href="#filter_track" title="Manipulate track lists (track)">track</a>
filter). Needs string conversion.
</p><p>
example:
</p><pre class="screen">   GPS_FIX,"","%s"
</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_track_new"></a>TRACK_NEW</h3></div></div></div><p>If '1', it indicates that this trackpoint is the first point of a new track.  Needs integer conversion.</p><p>example:</p><pre class="screen">IFIELD TRACK_NEW,"","%d"</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_track_name"></a>TRACK_NAME</h3></div></div></div><p>The name of the track currently being operated on.  Needs string conversion.</p><p>example:</p><pre class="screen">TRACK_NAME, "", "%s"</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_route_name"></a>ROUTE_NAME</h3></div></div></div><p>The name of the route currently being operated on.  Needs string conversion.</p><p>example:</p><pre class="screen">ROUTE_NAME, "", "%s"</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_street_addr"></a>STREET_ADDR</h3></div></div></div><p>Street address including house number.  Notice that this is not used for any geocoding, it's merely textual description associated with a position.</p><p>example:</p><pre class="screen">STREET_ADDR, "", "%s"</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_city"></a>CITY</h3></div></div></div><p>The name of a city. Sometimes part of "Points of Interest".   This is simple textual data associated with a position, no geocoding will be done..</p><p>example:</p><pre class="screen">CITY, "", "%s"</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_country"></a>COUNTRY</h3></div></div></div><p>The name of a country associated with a position.</p><p>example:</p><pre class="screen">COUNTRY, "", "%s"</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_facility"></a>FACILITY</h3></div></div></div><p>The name of a facility to associate with a position.</p><p>example:</p><pre class="screen">FACILITY, "", "%s"</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_phone_nr"></a>PHONE_NR</h3></div></div></div><p>A phone number associated with a position.  This is just textual data attached for convenience.</p><p>example:</p><pre class="screen">PHONE_NR, "", "%s"</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_postal_code"></a>POSTAL_CODE</h3></div></div></div><p>A postal code to associate with a position.  It is freeform text and is not used by GPSBabel for any geocoding or such.</p><p>example:</p><pre class="screen">POSTAL_CODE, "", "%s"</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_filename"></a>FILENAME</h3></div></div></div><p>The name of the input file from where the points were loaded. This field is available only on output.</p><p>example:</p><pre class="screen">OFIELD FILENAME, "", "%s"</pre></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_format"></a>FORMAT</h3></div></div></div><p>The name of the input format from where format the points came. This field is available only on output.</p><p>example:</p><pre class="screen">OFIELD FORMAT, "", "%s"</pre></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="style_examples"></a>Examples</h2></div></div></div><p>
Here is one example style file from the GPSBabel source.
</p><div class="literallayout"><p><br />
# gpsbabel XCSV style file<br />
#<br />
# Format: Garmin POI<br />
# Author: Robert Lipe<br />
# Date: 10/07/2005<br />
# Reference: http://forums.groundspeak.com/GC/index.php?showtopic=110641&amp;st=0&amp;#entry1752204<br />
#<br />
DESCRIPTION Garmin POI database<br />
#<br />
#<br />
# FILE LAYOUT DEFINITIIONS:<br />
#<br />
FIELD_DELIMITER COMMA<br />
RECORD_DELIMITER NEWLINE<br />
BADCHARS COMMA<br />
SHORTLEN 24<br />
<br />
#<br />
# INDIVIDUAL DATA FIELDS, IN ORDER OF APPEARANCE:<br />
#<br />
IFIELD LON_HUMAN_READABLE, "", "%08.5f"<br />
IFIELD LAT_HUMAN_READABLE, "", "%08.5f"<br />
IFIELD SHORTNAME, "", "%s"<br />
IFIELD DESCRIPTION, "", "%s"<br />
<br />
OFIELD LON_DECIMAL, "", "%08.5f"<br />
OFIELD LAT_DECIMAL, "", "%08.5f"<br />
OFIELD SHORTNAME, "", "%-.24s"<br />
OFIELD GEOCACHE_TYPE, "", " %-.4s", "no_delim_before,optional"<br />
OFIELD GEOCACHE_CONTAINER, "", "/%-.4s ", "no_delim_before,optional"<br />
OFIELD GEOCACHE_DIFF, "", "(%3.1f", "no_delim_before,optional"<br />
OFIELD GEOCACHE_TERR, "", "/%3.1f)", "no_delim_before,optional"<br />
OFIELD DESCRIPTION, "", "%-.50s"<br />
</p></div><p>
When used on a Groundspeak Pocket Query, it will output lines that
look like:
</p><div class="literallayout"><p><br />
-76.76234,38.39123,GC5370 Loca/Virt (1.0/1.0),Dude.. Wheres my Limo??<br />
-90.42345,38.55234,GCC8B Trad/Regu (2.0/2.0),Sweet Reward<br />
-90.81456,38.62456,GC3091 Trad/Regu (1.5/2.0),Matson Hill<br />
</p></div><p>
that are suitable for Garmin's POI loader.
</p><p>
For additional examples, please see the 
<code class="filename">*.style</code> files in the 
<code class="filename">style/</code> subdirectory of the GPSBabel source tree or at the <a class="ulink" href="http://code.google.com/p/gpsbabel/source/browse/#svn%2Ftrunk%2Fgpsbabel%2Fstyle" target="_top">online source.</a>.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="style_notes"></a>Miscellaneous Notes</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="style_notes_default"></a>Default Values</h3></div></div></div><p>   
Default values are supported for any output fields that contain pure 
   character data output such as URL and NOTES.  Default values are only
   written on output and are not used to supplement missing input.  When 
   using default values your mileage will vary greatly depending on the 
   input formats used to populate waypoint data.
</p></div></div></div><div class="glossary"><div class="titlepage"><div><div><h1 class="title"><a id="Glossary"></a>Glossary</h1></div></div></div><p>Terms that are used in conjunction with GPSBabel.</p><div class="glossdiv"><h3 class="title">G</h3><dl><dt><a id="gl_xml"></a><span class="glossterm">Geocaching</span></dt><dd class="glossdef"><p>GPS based "paper chase", see 
          <a class="ulink" href="http://en.wikipedia.org/wiki/Geocaching" target="_top">http://en.wikipedia.org/wiki/Geocaching</a></p></dd></dl></div><div class="glossdiv"><h3 class="title">I</h3><dl><dt><a id="gl_itinerary"></a><span class="glossterm">Itinerary</span></dt><dd class="glossdef"><p>same as a Route (e.g. used by TomTom)</p></dd></dl></div><div class="glossdiv"><h3 class="title">P</h3><dl><dt><a id="gl_poi"></a><span class="glossterm">Points of Interest (POI)</span></dt><dd class="glossdef"><p>a collection of gas stations, post boxes, shops and
          like.</p></dd></dl></div><div class="glossdiv"><h3 class="title">R</h3><dl><dt><a id="gl_route"></a><span class="glossterm">Route</span></dt><dd class="glossdef"><p>a list of geopoints (often with names) connected in
          a specific order. Usually a collection of geopoints
          defining the route you want to pass while traveling,
          created by PC software, or generated inside a GPS device.
          They can be composed of existing waypoints, or new
          "routepoints" might be generated.</p></dd></dl></div><div class="glossdiv"><h3 class="title">T</h3><dl><dt><a id="gl_track"></a><span class="glossterm">Track</span></dt><dd class="glossdef"><p>a collection of geopoints recorded by your GPS
          device while traveling -- "breadcrumb trails". The order
          of trackpoints within the track is important. Usually a
          trackpoint doesn't have a name or comment, but a
          timestamp. This distinguishes a trackpoint from a
          waypoint.</p></dd></dl></div><div class="glossdiv"><h3 class="title">W</h3><dl><dt><a id="gl_waypoint"></a><span class="glossterm">Waypoints</span></dt><dd class="glossdef"><p>are geopoints that are not necessarily connected to
          other points, and their order is unimportant. They can be
          entered before, while or after you actually visit the
          place and might have tags like name, comment and the
          like. Usually used to mark special locations as your
          home, a hotel or a geocache.</p></dd></dl></div></div></div></body></html>