Thread: [Gpsbabel-code] gdb: depth and proximity validity
Brought to you by:
robertl
From: Robert L. <rob...@us...> - 2005-08-12 02:35:17
Attachments:
gp
|
gdb.c and the rest of the code have a different idea of what constitutes "unknown" for the depth and altitude. Unfortunately, this means files written by our GDB writer tend to specify a depth and a proximity which means if you write a GDB file and then use Mapsource to send that file to a GPS that doesn't have those (i.e. streetpilot) or has only a fixed number of entries (i.e. 60C) the transfer will fail. Since waypt_new doesn't set these to unknown_alt, we probably shouldn't be testing those here. The patch below fixes things for me. It still passes testo. (BTW, Olaf, when we revisit the color/visibility stuff to use Ron's new looker upper, we should consider moving these into the "garmin specific" types as only the Garmin formats or things heavily influenced by them seems to have this concept.) |
From: Olaf K. <O.B...@t-...> - 2005-08-12 18:21:05
Attachments:
047-cet-02.patch.gz
048-gdb-11.patch.gz
|
Dear all, > gdb.c and the rest of the code have a different idea of what constitutes > "unknown" for the depth and altitude. Unfortunately, this means files > written by our GDB writer tend to specify a depth and a proximity which i've realized the differecences. For the moment i think it's better gdb writer don't writes any depth or proximity. The second patch fixes an error within CET brunch. O.K. |