gpsbabel-misc Mailing List for GPSBabel (Page 405)
Brought to you by:
robertl
You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(11) |
Nov
(24) |
Dec
(45) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(17) |
Feb
(19) |
Mar
(26) |
Apr
(38) |
May
(20) |
Jun
(11) |
Jul
(39) |
Aug
(47) |
Sep
(14) |
Oct
(18) |
Nov
(6) |
Dec
(14) |
2004 |
Jan
(41) |
Feb
(46) |
Mar
(98) |
Apr
(71) |
May
(25) |
Jun
(40) |
Jul
(68) |
Aug
(59) |
Sep
(78) |
Oct
(34) |
Nov
(25) |
Dec
(52) |
2005 |
Jan
(51) |
Feb
(63) |
Mar
(47) |
Apr
(36) |
May
(23) |
Jun
(80) |
Jul
(78) |
Aug
(56) |
Sep
(34) |
Oct
(117) |
Nov
(145) |
Dec
(102) |
2006 |
Jan
(158) |
Feb
(117) |
Mar
(85) |
Apr
(116) |
May
(102) |
Jun
(80) |
Jul
(168) |
Aug
(161) |
Sep
(112) |
Oct
(88) |
Nov
(90) |
Dec
(84) |
2007 |
Jan
(115) |
Feb
(142) |
Mar
(76) |
Apr
(90) |
May
(165) |
Jun
(91) |
Jul
(158) |
Aug
(108) |
Sep
(58) |
Oct
(69) |
Nov
(136) |
Dec
(60) |
2008 |
Jan
(50) |
Feb
(87) |
Mar
(79) |
Apr
(90) |
May
(114) |
Jun
(55) |
Jul
(89) |
Aug
(105) |
Sep
(77) |
Oct
(91) |
Nov
(29) |
Dec
(89) |
2009 |
Jan
(83) |
Feb
(44) |
Mar
(58) |
Apr
(70) |
May
(62) |
Jun
(69) |
Jul
(96) |
Aug
(82) |
Sep
(100) |
Oct
(43) |
Nov
(44) |
Dec
(32) |
2010 |
Jan
(69) |
Feb
(61) |
Mar
(70) |
Apr
(85) |
May
(93) |
Jun
(145) |
Jul
(36) |
Aug
(57) |
Sep
(54) |
Oct
(89) |
Nov
(44) |
Dec
(58) |
2011 |
Jan
(39) |
Feb
(59) |
Mar
(29) |
Apr
(35) |
May
(37) |
Jun
(31) |
Jul
(43) |
Aug
(48) |
Sep
(23) |
Oct
(30) |
Nov
(74) |
Dec
(49) |
2012 |
Jan
(43) |
Feb
(35) |
Mar
(38) |
Apr
(44) |
May
(60) |
Jun
(32) |
Jul
(34) |
Aug
(43) |
Sep
(42) |
Oct
(38) |
Nov
(46) |
Dec
(21) |
2013 |
Jan
(16) |
Feb
(30) |
Mar
(21) |
Apr
(25) |
May
(13) |
Jun
(29) |
Jul
(31) |
Aug
(25) |
Sep
(17) |
Oct
(22) |
Nov
(19) |
Dec
(31) |
2014 |
Jan
(11) |
Feb
(16) |
Mar
(65) |
Apr
(27) |
May
(24) |
Jun
(45) |
Jul
(56) |
Aug
(23) |
Sep
(18) |
Oct
(26) |
Nov
(11) |
Dec
(11) |
2015 |
Jan
(25) |
Feb
(24) |
Mar
(30) |
Apr
(26) |
May
(25) |
Jun
(23) |
Jul
(22) |
Aug
(30) |
Sep
(17) |
Oct
(21) |
Nov
(43) |
Dec
(31) |
2016 |
Jan
(46) |
Feb
(55) |
Mar
(24) |
Apr
(17) |
May
(27) |
Jun
(9) |
Jul
(47) |
Aug
(15) |
Sep
(8) |
Oct
(16) |
Nov
(3) |
Dec
(17) |
2017 |
Jan
(3) |
Feb
(8) |
Mar
(18) |
Apr
(6) |
May
(17) |
Jun
(6) |
Jul
(22) |
Aug
(6) |
Sep
(19) |
Oct
(11) |
Nov
(20) |
Dec
(12) |
2018 |
Jan
|
Feb
(8) |
Mar
(7) |
Apr
(1) |
May
(24) |
Jun
(9) |
Jul
(34) |
Aug
(24) |
Sep
(17) |
Oct
(16) |
Nov
(4) |
Dec
(17) |
2019 |
Jan
(9) |
Feb
(4) |
Mar
(27) |
Apr
(31) |
May
(26) |
Jun
(28) |
Jul
(41) |
Aug
(29) |
Sep
(9) |
Oct
(14) |
Nov
(12) |
Dec
(38) |
2020 |
Jan
(13) |
Feb
|
Mar
(10) |
Apr
(4) |
May
(30) |
Jun
(10) |
Jul
(7) |
Aug
(62) |
Sep
(12) |
Oct
(5) |
Nov
(29) |
Dec
(19) |
2021 |
Jan
(5) |
Feb
(7) |
Mar
(11) |
Apr
(3) |
May
(29) |
Jun
(10) |
Jul
|
Aug
|
Sep
(2) |
Oct
(6) |
Nov
(1) |
Dec
(2) |
2022 |
Jan
(7) |
Feb
(31) |
Mar
(17) |
Apr
|
May
(3) |
Jun
(21) |
Jul
(11) |
Aug
|
Sep
(16) |
Oct
(7) |
Nov
(6) |
Dec
(6) |
2023 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(13) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
2024 |
Jan
(8) |
Feb
(2) |
Mar
(11) |
Apr
(17) |
May
|
Jun
(4) |
Jul
(11) |
Aug
(16) |
Sep
(8) |
Oct
|
Nov
|
Dec
|
From: Robert L. <rob...@us...> - 2002-10-18 04:28:52
|
> > while I was staring at it. It seems like there's some other format we > > have that represent unknown altitude with a magic constant but I can't > > seem to find it to fix it in the same way... > > That'd be Cetus. An elevation of -1e8 signifies "unknown." I won't get to it before I leave town for the weekend, but if you'd like to code up brackets for this catching -1e8 into unknown_alt on the way in and out, I'll apply them on my return. I'm guessing the reference files are "wrong" in this regard, so they'll need fixing, too... RJL |
From: Ron P. <pa...@fw...> - 2002-10-17 18:36:38
|
> I just committed it and added a fix for the Ozi "unknown altitude" stuff > while I was staring at it. It seems like there's some other format we > have that represent unknown altitude with a magic constant but I can't > seem to find it to fix it in the same way... That'd be Cetus. An elevation of -1e8 signifies "unknown." |
From: Robert L. <rob...@us...> - 2002-10-12 03:39:57
|
> The whine and scream line was put in there mainly to flag data that > would confuse ozi.c while parsing data (embedded commas, which I now Fixed length, comma delimited. Sheesh... Still, at the advice of the Ozi developer, I've removed the warning and will just let it silently ignore the extra fields. Leaving them out on a write is allegedly fine, too. RJL |
From: Alex M. <mi...@to...> - 2002-10-11 22:04:46
|
>Ray provided a sample file. Ozi changed the file format without changing >either the version number or the doc. So I just made the code ignore the >new six fields for now. I asked him to ask Ozi for doc but even if we don't >get it, that's OK. I can't even find a new version of ozi beyond the one I wrote the spec around (you mean the spec was in the help somewhere?!?!?! I generally don't read 'help'). They *do* have the layout for the routes in there also. hmm... Admittedly, I don't use oziexplorer. I checked it out, as well as oziexplorerCE. Seems I don't much care for making my own detail maps and paying relatively big bucks for the privilege.. :( The whine and scream line was put in there mainly to flag data that would confuse ozi.c while parsing data (embedded commas, which I now know breaks the ozi spec). As it's fixed-width CSV, it could very well be pulled out and the data could be chunked out of the lines with disregard for anything it doesn't know (or need for that matter. (pointer direction? come on!) I'm glad to see someone using it. :) ... alex |
From: Robert L. <rob...@us...> - 2002-10-11 13:57:44
|
Ray Perkins wrote: > I noticed a problem with Ozi input files. The later Ozi versions have more > data field entries than are listed in the help(technical) file (sample > waypoint below). The 3 extra entries and 3 extra placeholers (commas) cause Ray provided a sample file. Ozi changed the file format without changing either the version number or the doc. So I just made the code ignore the new six fields for now. I asked him to ask Ozi for doc but even if we don't get it, that's OK. I just committed it and added a fix for the Ozi "unknown altitude" stuff while I was staring at it. It seems like there's some other format we have that represent unknown altitude with a magic constant but I can't seem to find it to fix it in the same way... > specification.". I don't know what the extra data does, or why Des hasn't > documented it in the help file, but it seems to mess up the Ozi to Cetus > conversion. He also sent me the sample files. This was caused by the cetus output format not opening the file for write as binary which tripped up some Windows OSes; a problem Kjeld and I analyzed earlier in the week and committed a fix for earlier. Both issues are closed in the top of tree. Thanx, Ray. RJL |
From: Robert L. <rob...@us...> - 2002-10-11 02:47:46
|
Ray Perkins wrote: > I noticed a problem with Ozi input files. The later Ozi versions have more > data field entries than are listed in the help(technical) file (sample Yay. > waypoint below). The 3 extra entries and 3 extra placeholers (commas) cause > GPSbabel to give an error: "Warning: data fields on line xx exceed > specification.". I don't know what the extra data does, or why Des hasn't Well, that's a warning and not an error. It doesn't look like it should choke it. Can you please provide us with a complete sample file of this "new" format so we can verify that everything else is cool. That gibberish at the top of the file matters to us. Actually, if you could just slurp reference/ozi.ozi into the file and write it back out, that'd be even vetter as that'd highlight the exact same set of waypoint data with only the differences of the new format. Similarly, can you contact the Ozi folks and see what those fields are for? Thanx, RJL |
From: Ray P. <ray...@3w...> - 2002-10-11 00:00:24
|
I noticed a problem with Ozi input files. The later Ozi versions have more data field entries than are listed in the help(technical) file (sample waypoint below). The 3 extra entries and 3 extra placeholers (commas) cause GPSbabel to give an error: "Warning: data fields on line xx exceed specification.". I don't know what the extra data does, or why Des hasn't documented it in the help file, but it seems to mess up the Ozi to Cetus conversion. sample: 2,ADDIST,44.661127,-75.883144,36776.3232800,1,1,5,0,65535,Addison,0,0,0,-777 ,6,0,17,0,10.0,2,,, Cheers, Ray Perkins |
From: Robert L. <rob...@us...> - 2002-10-09 01:36:30
|
> I seem to have stumbled across a problem with the signing on lat/lon > pairs. The problem is, I don't know if it is something I need to > program around, a problem with the commerical program I'm using to If you want to talk through it, I'll listen. I found it helpful to get someone to generate opposing signed coords with names to tell me what they were when figuring this sort of thing out. "1N, 1E" -> "1N1E" for pairs like 1N1W, 1S1E, 1S1E and so on. RJL |
From: Alex M. <al...@co...> - 2002-10-08 16:26:26
|
I've been working on getting NG Topo! / Topo!GPS format working with gpsbabel. I seem to have stumbled across a problem with the signing on lat/lon pairs. The problem is, I don't know if it is something I need to program around, a problem with the commerical program I'm using to generate Topo! files (not Topo!), or something about signing FP numbers that I just don't understand. I'm 99% of the way to something that works and this is the last big (and obviously very important) hurdle. As I don't have Topo!, I'm looking for someone with this application that is willing to generate a few .tpg files and do a bit of testing or point me towards a downloadable Topo! demo. I wouldn't turn away a free copy landing on my doorstep, either. :) If that person is you, please contact me for more information. Regards, Alex Mottram |
From: Robert L. <rob...@us...> - 2002-10-03 16:18:29
|
I've spun the release. Many thanx to those that contributed code to improve GPSBabel. Enjoy! RJL |
From: Robert L. <rob...@us...> - 2002-09-18 20:39:25
|
I'd like to have a 1.0 release of theis software within a week. Please check it out on your combination of hardware and file formats. Thank you, RJL |