gpsbabel-misc Mailing List for GPSBabel
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
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Robert L. <rob...@gp...> - 2024-03-19 08:07:35
|
Either modify the duplicate to do it or write the output before and after the duplicate filter and diff them. Something approximately like: gpsbabel -i whatever -f blah -o unicsv -F unfiltered -x duplicate -F filtered diff unfiltered filtered More or less. There may be a way to do it with the stack filter, but diff is the tool I'd reach for first, personally. RJL On Tue, Mar 19, 2024 at 1:31 AM Sutripta <sut...@gm...> wrote: > Hi, > I want to see the duplicate waypoints which have been removed using the -x > duplicate filter, not the ones which remain. How does one do that? > > TIA. > > Regards > Sutripta > _______________________________________________ > Gpsbabel-misc mailing list http://www.gpsbabel.org > Gps...@li... > To unsubscribe, change list options, or see archives, visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc > |
From: Sutripta <sut...@gm...> - 2024-03-19 06:30:28
|
Hi, I want to see the duplicate waypoints which have been removed using the -x duplicate filter, not the ones which remain. How does one do that? TIA. Regards Sutripta |
From: Robert L. <rob...@gp...> - 2024-02-02 20:04:38
|
Probably. It's clearly not a recently tested combination and you may have to debug it... But that going to be true if anything. I can't, however, recommend buying a 1990s era tech device, though. Any modern Garmin is going to give you a better experience. If you absolutely adore that and want to keep that cable,. I'd at least go for the 2000 or 2001 model of that device, the Map 330. OTOH, all. The maps you can get for it are going to be windows only and from about 2005 at best. It is, however a better receiver in the same form factor. On Fri, Feb 2, 2024, 1:52 PM D McC <dmc...@gm...> wrote: > > Hi, > > Years ago I had a Magellan 315 and uploaded waypoints to it via some > Windows software, don’t remember. This used the Magellan data cable and > 9-pin serial port. > > Anyway, I liked the 315 for a few reasons and may get a “new” one on > eBay. I would use the same data cable, but plug the RS-232 end of that > into a RS-232-USB adapter. Then plug the USB end of the adapter into my PC > (Linux). > > I now have a standard GPX file of waypoints, which I have used with other > more modern devices. > > So, question is — with the above setup, will gpsbabel command line be able > to upload the GPX file waypoints into a Magellan 315 ? > > thanks for any answers > > > > -- > Doug McCasland <dmc...@gm...> > > > _______________________________________________ > Gpsbabel-misc mailing list http://www.gpsbabel.org > Gps...@li... > To unsubscribe, change list options, or see archives, visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc > |
From: D M. <dmc...@gm...> - 2024-02-02 19:51:52
|
Hi, Years ago I had a Magellan 315 and uploaded waypoints to it via some Windows software, don’t remember. This used the Magellan data cable and 9-pin serial port. Anyway, I liked the 315 for a few reasons and may get a “new” one on eBay. I would use the same data cable, but plug the RS-232 end of that into a RS-232-USB adapter. Then plug the USB end of the adapter into my PC (Linux). I now have a standard GPX file of waypoints, which I have used with other more modern devices. So, question is — with the above setup, will gpsbabel command line be able to upload the GPX file waypoints into a Magellan 315 ? thanks for any answers -- Doug McCasland <dmc...@gm...> |
From: <ri...@sa...> - 2024-01-25 10:19:16
|
Hello community, I am after version 1.8.0 in order to convert/ create ov2 tomtom files. Is there any way to download it either from an official link or trusted site? Thanks in advance! |
From: Don H. <har...@at...> - 2024-01-07 23:38:00
|
OK Thank you. I had lat and long reversed form that POI factory file. Now I don't have to use garmin poi loader and mess with wine. On 1/7/24 1:52 PM, tsteven4 wrote: > gpsbabel -i unicsv,fields=lat+lon+name+desc -f Wendys_USA_Can.csv -o > garmin_gpi,category="Wendys Rest" -F wendys.gpi |
From: tsteven4 <tst...@gm...> - 2024-01-07 18:53:05
|
If you input starts like: -149.93732,61.18088,"Wendy's-Anchorage,AK ","4407 Spenard Rd, Anchorage,AK, (907) 677-8890" -149.86787,61.19424,"Wendy's-Anchorage,AK ","2927 Seward Hwy, Anchorage,AK, (907) 258-4239" -149.86386,61.11842,"Wendy's-Anchorage,AK ","11310 Old Seward Hwy, Anchorage,AK, (907) 344-0834" -149.83755,61.21754,"Wendy's-Anchorage,AK ","2323 E 5th Ave, Anchorage,AK, (907) 279-8271" then longitude precedes latitude, so use gpsbabel -i unicsv,fields=lon+lat+name+desc -f wendys.csv ... On 1/7/2024 11:00 AM, Don Harter wrote: > I downloaded a csv file then made a .gpi/POI file for my garmin gps. > > When I display it in the garmin most of the pois are not shown and the > few that are; are 4000 miles away. I tried several formats for the > input file. Here are my command lines. For the latter I added a line > at the top for the header. > > gpsbabel -i csv -f Wendys_USA_Can.csv -o garmin_gpi,category="Wendys > Rest" -F wendys.gpi > > > gpsbabel -i unicsv,fields=lat+lon+name+desc -f Wendys_USA_Can.csv -o > garmin_gpi,category="Wendys Rest" -F wendys.gpi > > > > > _______________________________________________ > Gpsbabel-misc mailing listhttp://www.gpsbabel.org > Gps...@li... > To unsubscribe, change list options, or see archives, visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc |
From: tsteven4 <tst...@gm...> - 2024-01-07 18:45:57
|
Please provide enough information to reproduce the problem, including the input file Wendys_USA_Can.csv. What version of gpsbabel are you using? On 1/7/2024 11:00 AM, Don Harter wrote: > > I downloaded a csv file then made a .gpi/POI file for my garmin gps. > > When I display it in the garmin most of the pois are not shown and the > few that are; are 4000 miles away. I tried several formats for the > input file. Here are my command lines. For the latter I added a line > at the top for the header. > > gpsbabel -i csv -f Wendys_USA_Can.csv -o garmin_gpi,category="Wendys > Rest" -F wendys.gpi > > > gpsbabel -i unicsv,fields=lat+lon+name+desc -f Wendys_USA_Can.csv -o > garmin_gpi,category="Wendys Rest" -F wendys.gpi > > > > > _______________________________________________ > Gpsbabel-misc mailing listhttp://www.gpsbabel.org > Gps...@li... > To unsubscribe, change list options, or see archives, visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc |
From: Don H. <har...@at...> - 2024-01-07 18:11:06
|
I downloaded a csv file then made a .gpi/POI file for my garmin gps. When I display it in the garmin most of the pois are not shown and the few that are; are 4000 miles away. I tried several formats for the input file. Here are my command lines. For the latter I added a line at the top for the header. gpsbabel -i csv -f Wendys_USA_Can.csv -o garmin_gpi,category="Wendys Rest" -F wendys.gpi gpsbabel -i unicsv,fields=lat+lon+name+desc -f Wendys_USA_Can.csv -o garmin_gpi,category="Wendys Rest" -F wendys.gpi |
From: Robert L. <rob...@gp...> - 2024-01-04 22:03:24
|
There is absolutely none. What on our site made you think that? On Thu, Jan 4, 2024 at 8:05 AM tsteven4 <tst...@gm...> wrote: > I can't remember any dependence of GPSBabel on Java3D. What version of > GPSBabel are you using? The current release is 1.9.0 which is available at GPSBabel > official download <https://www.gpsbabel.org/download.html>. > On 1/4/2024 6:37 AM, bar...@gm... wrote: > > Hi, I recently installed GPSBabel and found out, Java3D is not pre-installed. So I was downloading it from Oracle. Following the instructions to install it I failed. Can you please let me know in which directory you are expexting Java3D to be installed? I guess it is the default JRE directory. But how to find out? > I am using MacOS in Version 14.2.1 in a M1 Silicon Chip MacBook Pro and Java JRE 8. > BR R.C. > > _______________________________________________ > Gpsbabel-misc mailing list http://www...@li... > To unsubscribe, change list options, or see archives, visit:https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc > > _______________________________________________ > Gpsbabel-misc mailing list http://www.gpsbabel.org > Gps...@li... > To unsubscribe, change list options, or see archives, visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc > |
From: tsteven4 <tst...@gm...> - 2024-01-04 14:04:57
|
I can't remember any dependence of GPSBabel on Java3D. What version of GPSBabel are you using? The current release is 1.9.0 which is available at GPSBabel official download <https://www.gpsbabel.org/download.html>. On 1/4/2024 6:37 AM, bar...@gm... wrote: > Hi, I recently installed GPSBabel and found out, Java3D is not pre-installed. So I was downloading it from Oracle. Following the instructions to install it I failed. Can you please let me know in which directory you are expexting Java3D to be installed? I guess it is the default JRE directory. But how to find out? > I am using MacOS in Version 14.2.1 in a M1 Silicon Chip MacBook Pro and Java JRE 8. > BR R.C. > > _______________________________________________ > Gpsbabel-misc mailing listhttp://www.gpsbabel.org > Gps...@li... > To unsubscribe, change list options, or see archives, visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc |
From: <bar...@gm...> - 2024-01-04 13:38:24
|
Hi, I recently installed GPSBabel and found out, Java3D is not pre-installed. So I was downloading it from Oracle. Following the instructions to install it I failed. Can you please let me know in which directory you are expexting Java3D to be installed? I guess it is the default JRE directory. But how to find out? I am using MacOS in Version 14.2.1 in a M1 Silicon Chip MacBook Pro and Java JRE 8. BR R.C. |
From: Robert L. <rob...@gp...> - 2023-12-27 02:08:31
|
The source is still n Git if you or anyone else (contract workers are out there) wants to maintain a format that's fallen below the threshold of cost/benefits for us. Good luck. On Tue, Dec 26, 2023, 1:07 PM srpoth--- via Gpsbabel-misc < gps...@li...> wrote: > I'm a little late to the party and was not aware that some older, unused > formats were being removed until I downloaded 1.9.0. Would it be possible > to add back in support for > > *mapfactor* Mapfactor Navigator > > ?? > > I do use Mapfactor Navigator as an Android app from time to time, and the > format looks pretty simple, but I do understand if you want it to stay > retired. > > Thanks! > Steve > > > _______________________________________________ > Gpsbabel-misc mailing list http://www.gpsbabel.org > Gps...@li... > To unsubscribe, change list options, or see archives, visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc > |
From: <sr...@ne...> - 2023-12-26 19:06:00
|
I'm a little late to the party and was not aware that some older, unused formats were being removed until I downloaded 1.9.0. Would it be possible to add back in support for *mapfactor* Mapfactor Navigator?? I do use Mapfactor Navigator as an Android app from time to time, and the format looks pretty simple, but I do understand if you want it to stay retired. Thanks! Steve |
From: Sutripta <sut...@gm...> - 2023-08-01 12:35:21
|
Hi everybody, Just adding my two bits of unsolicited thought. I use Mapsource (6.13.7) a lot. This version handles .gdb like a champ. So I use .gdb files not because I like gdb but Mapsource does and I like Mapsource. Though officially MS should handle .gpx files it chokes on both (very moderate) size and almost any variation in format, even if it will pass GPX validation. The later versions of Mapsource handles GPX files somewhat better, which is actually not saying much. Now if someone can handhold me in loading Mapsource on my Win11 laptop. I still have the original CD. Else it looks like I'll have to somehow keep my Win7 desktop going. My suggestion - please provide an archive of the older GPSBabel versions, along with a changelog. Regards Sutripta On Fri, 21 Jul 2023 at 06:12, Gary Turner <g...@el...> wrote: > Wow! Thank you so much! > > On 21/07/2023 9:25 am, tsteven4 wrote: > > This has been resolved in the master branch of > https://github.com/GPSBabel/gpsbabel. Two searches that resulted in > complexity of O(n^2) have been reduced to O(n). > > The provided test case, with 674133 points, now converts in 4.5 SECONDS on > my laptop instead of the reported ~6 HOURS you reported. > On 7/19/2023 5:36 AM, Gary Turner wrote: > > Sorry, I didn't have a copy of the old email still, so wasn't able to > reference it. This PC is 2013 vintage. > > We're not using Mapsource for these files. We load the GDB files into a > legacy map editor, that runs way faster with GDB files rather than gpx > files. 'We' here is a local open source map project, so we're not making > any money out of it. > > You're right. Mapsource gurgles a bit on a few thousand points. But as > above, that's not relevant to us. The editor we use is OK with GDB files > this size though. > > Sorry, but I still have to disagree that GDB is dead. I still use > Mapsource regularly, given what a joke Basecamp was, and although Mapsource > handles GPX, it's not particularly robust at it. > On 19/07/23 22:46, Robert Lipe wrote: > > Good grief. When referencing problems I've already personally diagnosed > for you that were 13 YEARS ago, please at least include the subject. This > was from Jan 30, 2012. > > The fundamental problem is that you're doing GIS-class tasks with > consumer-grade software (Mapsource) that isn't. Even other people chimed in > on that thread that Mapsource locked up on WAY smaller files than you were > asking us to produce (without us), even once it was produced. > > Mapsource reads GPX. No conversion is even necessary. > > We do have better infrastructure that might be possible to speed that up, > but this is basically custom development work in an otherwise dead format. > Creating 650,000 points (that have non-unique locations and names - and > your source file DID have collisions - it's not just a sorting problem) > into software that requires unique names (Mapsource) is always going to be > a bad fit. > > With the infrastructure we now have in place, speeding it up is possible > (perhaps ismo would like to do the work as a consulting project for you) > but validating the result in a generally useful way isn't at all easy. > > > > I should have deleted GDB format ten+ years ago... > > > > > On Tue, Jul 18, 2023 at 6:57 AM tsteven4 <tst...@gm...> wrote: > >> I can't find the context of this thread. Without a test case including >> input data files and the specific gpsbabel command line you are using >> this is not going anywhere. >> >> On 7/18/2023 1:36 AM, Gary Turner wrote: >> > Quite some time ago, I asked about why it took a long time for >> > GPSBabel to do my conversions. >> > To convert a file with 600,000 odd points from GPX to GDB takes around >> > 6 hours. >> > Back then, from memory, Robert had a look at it, and thought that the >> > issue might be sorting. Again, from memory, he said that GDB files had >> > to be sorted. >> > I had a thought recently - might it be possible to 'bin' the data, >> > e.g. into say 0-9 and A-Z, and then only sort each of these bins, and >> > then assemble the sorted bins in correct order? Would that be quicker? >> > >> > >> > _______________________________________________ >> > Gpsbabel-misc mailing list http://www.gpsbabel.org >> > Gps...@li... >> > To unsubscribe, change list options, or see archives, visit: >> > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc >> >> >> _______________________________________________ >> Gpsbabel-misc mailing list http://www.gpsbabel.org >> Gps...@li... >> To unsubscribe, change list options, or see archives, visit: >> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc >> > > _______________________________________________ > Gpsbabel-misc mailing list http://www.gpsbabel.org > Gps...@li... > To unsubscribe, change list options, or see archives, visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc > |
From: Robert L. <rob...@gp...> - 2023-08-01 09:43:22
|
Lowrance USR trail version 6 not supported!! That's the important bit. Nobody has reverse-engineered that format and submitted an implementation. Can you save the file on the Lowrance as a simple (older .usr or, better yet, a GPX or other open file format? On Tue, Aug 1, 2023 at 4:29 AM Anton Vasko <ton...@gm...> wrote: > Me llamo Anton i tengo un problema en convertir waypoints de lowrance que > estan en formato usr. a formato para googel maps que lo necesita en kmz. > esto es lo que pone GPS Babel al intentar convertir :gpsbabel -w -r -t -i > lowranceusr -f C:/Users/Anton/Desktop/waypoints/Waypoints OLBAP.usr -o kml > -F C:/Users/Anton/Desktop/waypoints/waypoints para earth.kml > > Lowrance USR trail version 6 not supported!! > > Error ejecutando gpsbabel: El proceso terminó sin suerte y con el código 1 > > > > _______________________________________________ > Gpsbabel-misc mailing list http://www.gpsbabel.org > Gps...@li... > To unsubscribe, change list options, or see archives, visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc > |
From: Anton V. <ton...@gm...> - 2023-08-01 09:28:47
|
Me llamo Anton i tengo un problema en convertir waypoints de lowrance que estan en formato usr. a formato para googel maps que lo necesita en kmz. esto es lo que pone GPS Babel al intentar convertir :gpsbabel -w -r -t -i lowranceusr -f C:/Users/Anton/Desktop/waypoints/Waypoints OLBAP.usr -o kml -F C:/Users/Anton/Desktop/waypoints/waypoints para earth.kml Lowrance USR trail version 6 not supported!! Error ejecutando gpsbabel: El proceso terminó sin suerte y con el código 1 |
From: Robert N. <rob...@gm...> - 2023-07-29 21:45:10
|
Hello, In the support documentation for IGC files ( https://www.gpsbabel.org/htmldoc-1.8.0/fmt_igc.html) there is the following paragraph on converting IGC to GPX: "gpsbabel -i igc -f myflight.igc -o gpx -F myflight.gpx Header information from the IGC file will be written to the description field of the track(s). *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*." If I have an IGC file with both pressure and GNSS altitude, is there a way to convert to GPX using only the pressure or GNSS altitude? (not both) Thanks, Robert |
From: tsteven4 <tst...@gm...> - 2023-07-28 13:25:36
|
There is work in progress towards reducing the complexity of the simplify filter, https://github.com/GPSBabel/gpsbabel/pull/1149. This reduces the complexity of the simplify filter from O(n^2) to O(nlog(n)) ~= O(n). The filtered results should be identical. Extrapolating the test data estimates of execution times for 10^6 points where half are deleted are ~239,000 seconds (2.8 days) for the current code and ~111 seconds for the modified code. On 12/2/2019 3:26 PM, Owen Duffy wrote: > Hi, > > I am trying to 'decimate' a very large NMEA file (~10,000,000 records). > > I have used the following filter with good sucess on smaller files: > > -x discard,fixnone,fixunknown -x transform,rte=trk,del -x > simplify,error=0.010k > > In measuring some run times on smaller files, it appears that the run > time grows at more than order N. > > Is there a way to optimised this process in GPSBABEL, or should I give > up and split the file into a hundred small files, process each and then > concatenate (using GPSBABEL)? > > Owen > > > _______________________________________________ > Gpsbabel-misc mailing list http://www.gpsbabel.org > Gps...@li... > To unsubscribe, change list options, or see archives, visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc |
From: Gary T. <g...@el...> - 2023-07-21 00:41:35
|
Wow! Thank you so much! On 21/07/2023 9:25 am, tsteven4 wrote: > > This has been resolved in the master branch of > https://github.com/GPSBabel/gpsbabel. Two searches that resulted in > complexity of O(n^2) have been reduced to O(n). > > The provided test case, with 674133 points, now converts in 4.5 > SECONDS on my laptop instead of the reported ~6 HOURS you reported. > > On 7/19/2023 5:36 AM, Gary Turner wrote: >> >> Sorry, I didn't have a copy of the old email still, so wasn't able to >> reference it. This PC is 2013 vintage. >> >> We're not using Mapsource for these files. We load the GDB files into >> a legacy map editor, that runs way faster with GDB files rather than >> gpx files. 'We' here is a local open source map project, so we're not >> making any money out of it. >> >> You're right. Mapsource gurgles a bit on a few thousand points. But >> as above, that's not relevant to us. The editor we use is OK with GDB >> files this size though. >> >> Sorry, but I still have to disagree that GDB is dead. I still use >> Mapsource regularly, given what a joke Basecamp was, and although >> Mapsource handles GPX, it's not particularly robust at it. >> >> On 19/07/23 22:46, Robert Lipe wrote: >>> Good grief. When referencing problems I've already personally >>> diagnosed for you that were 13 YEARS ago, please at least include >>> the subject. This was from Jan 30, 2012. >>> >>> The fundamental problem is that you're doing GIS-class tasks with >>> consumer-grade software (Mapsource) that isn't. Even other people >>> chimed in on that thread that Mapsource locked up on WAY smaller >>> files than you were asking us to produce (without us), even once it >>> was produced. >>> >>> Mapsource reads GPX. No conversion is even necessary. >>> >>> We do have better infrastructure that might be possible to speed >>> that up, but this is basically custom development work in an >>> otherwise dead format. Creating 650,000 points (that have non-unique >>> locations and names - and your source file DID have collisions - >>> it's not just a sorting problem) into software that requires unique >>> names (Mapsource) is always going to be a bad fit. >>> >>> With the infrastructure we now have in place, speeding it up is >>> possible (perhaps ismo would like to do the work as a consulting >>> project for you) but validating the result in a generally useful way >>> isn't at all easy. >>> >>> >>> >>> I should have deleted GDB format ten+ years ago... >>> >>> >>> >>> >>> On Tue, Jul 18, 2023 at 6:57 AM tsteven4 <tst...@gm...> wrote: >>> >>> I can't find the context of this thread. Without a test case >>> including >>> input data files and the specific gpsbabel command line you are >>> using >>> this is not going anywhere. >>> >>> On 7/18/2023 1:36 AM, Gary Turner wrote: >>> > Quite some time ago, I asked about why it took a long time for >>> > GPSBabel to do my conversions. >>> > To convert a file with 600,000 odd points from GPX to GDB >>> takes around >>> > 6 hours. >>> > Back then, from memory, Robert had a look at it, and thought >>> that the >>> > issue might be sorting. Again, from memory, he said that GDB >>> files had >>> > to be sorted. >>> > I had a thought recently - might it be possible to 'bin' the >>> data, >>> > e.g. into say 0-9 and A-Z, and then only sort each of these >>> bins, and >>> > then assemble the sorted bins in correct order? Would that be >>> quicker? >>> > >>> > >>> > _______________________________________________ >>> > Gpsbabel-misc mailing list http://www.gpsbabel.org >>> > Gps...@li... >>> > To unsubscribe, change list options, or see archives, visit: >>> > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc >>> >>> >>> _______________________________________________ >>> Gpsbabel-misc mailing list http://www.gpsbabel.org >>> Gps...@li... >>> To unsubscribe, change list options, or see archives, visit: >>> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc >>> |
From: tsteven4 <tst...@gm...> - 2023-07-20 21:25:15
|
This has been resolved in the master branch of https://github.com/GPSBabel/gpsbabel. Two searches that resulted in complexity of O(n^2) have been reduced to O(n). The provided test case, with 674133 points, now converts in 4.5 SECONDS on my laptop instead of the reported ~6 HOURS you reported. On 7/19/2023 5:36 AM, Gary Turner wrote: > > Sorry, I didn't have a copy of the old email still, so wasn't able to > reference it. This PC is 2013 vintage. > > We're not using Mapsource for these files. We load the GDB files into > a legacy map editor, that runs way faster with GDB files rather than > gpx files. 'We' here is a local open source map project, so we're not > making any money out of it. > > You're right. Mapsource gurgles a bit on a few thousand points. But as > above, that's not relevant to us. The editor we use is OK with GDB > files this size though. > > Sorry, but I still have to disagree that GDB is dead. I still use > Mapsource regularly, given what a joke Basecamp was, and although > Mapsource handles GPX, it's not particularly robust at it. > > On 19/07/23 22:46, Robert Lipe wrote: >> Good grief. When referencing problems I've already personally >> diagnosed for you that were 13 YEARS ago, please at least include the >> subject. This was from Jan 30, 2012. >> >> The fundamental problem is that you're doing GIS-class tasks with >> consumer-grade software (Mapsource) that isn't. Even other people >> chimed in on that thread that Mapsource locked up on WAY smaller >> files than you were asking us to produce (without us), even once it >> was produced. >> >> Mapsource reads GPX. No conversion is even necessary. >> >> We do have better infrastructure that might be possible to speed that >> up, but this is basically custom development work in an otherwise >> dead format. Creating 650,000 points (that have non-unique locations >> and names - and your source file DID have collisions - it's not just >> a sorting problem) into software that requires unique names >> (Mapsource) is always going to be a bad fit. >> >> With the infrastructure we now have in place, speeding it up is >> possible (perhaps ismo would like to do the work as a consulting >> project for you) but validating the result in a generally useful way >> isn't at all easy. >> >> >> >> I should have deleted GDB format ten+ years ago... >> >> >> >> >> On Tue, Jul 18, 2023 at 6:57 AM tsteven4 <tst...@gm...> wrote: >> >> I can't find the context of this thread. Without a test case >> including >> input data files and the specific gpsbabel command line you are >> using >> this is not going anywhere. >> >> On 7/18/2023 1:36 AM, Gary Turner wrote: >> > Quite some time ago, I asked about why it took a long time for >> > GPSBabel to do my conversions. >> > To convert a file with 600,000 odd points from GPX to GDB takes >> around >> > 6 hours. >> > Back then, from memory, Robert had a look at it, and thought >> that the >> > issue might be sorting. Again, from memory, he said that GDB >> files had >> > to be sorted. >> > I had a thought recently - might it be possible to 'bin' the data, >> > e.g. into say 0-9 and A-Z, and then only sort each of these >> bins, and >> > then assemble the sorted bins in correct order? Would that be >> quicker? >> > >> > >> > _______________________________________________ >> > Gpsbabel-misc mailing list http://www.gpsbabel.org >> > Gps...@li... >> > To unsubscribe, change list options, or see archives, visit: >> > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc >> >> >> _______________________________________________ >> Gpsbabel-misc mailing list http://www.gpsbabel.org >> Gps...@li... >> To unsubscribe, change list options, or see archives, visit: >> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc >> |
From: SRE <ste...@cl...> - 2023-07-20 17:49:04
|
Many of us prefer MapSource to BaseCamp, and are still using it regularly. Works fine with current Windoze, so no need to update. When I do need to use BaseCamp, for some specific task, I import my data in a way that allows me to blow it all away afterward. BaseCamp tends to suck everything into one huge file database and store that database where you can't back it up. That's avoidable, but not the default. MapSource is OK working on a single file and letting you control where that file lives. Just adding a voice to the discussion: lack of updates does not necessarily mean lack of use. On the other hand, I don't use GDB at all. Both Garmin tools can import/export GPX (with some serious limitations on handling ALL gpx files), so I'd encourage people to use that format instead of GDB (if they can). Steve On 07/20/2023 9:56 AM, tsteven4 wrote: > > mapsource is dead, garmin hasn't updated it since 2010. > > garmin did update basecamp in 2023. > > gpsbabel support for gdb is on life support. > |
From: David P. <dav...@gm...> - 2023-07-20 17:18:33
|
People still use MapSource (the development stopped a while ago). People still use BaseCamp (the development has been minimal for a while). Somebody released a BaseCamp tutorial on YouTube within the past couple of years. That suggests there is a fair amount of people using it. I suspect most people realize they have to live with what support already exists for GDB. So, if something doesn't work, they won't say anything. That wouldn't necessarily mean they don't use it. I have a program that uses GPSBabel to convert from GDB files to KML for use in BaseCamp/MapSource and people actually pay (a little bit of) money for it. Being able to use GDB still appears to useful. It would be unfortunate to lose benefit of the work done to add the support. Yes, I realize it costs something to maintain it but it's not like there's no value in supporting it. There's reading the format and writing it. It's possible that there's not as much need to write it and that it might make sense to drop that support. For my purpose, what works currently for GDB is sufficient (so, personally, I'd be fine with freezing any updates/improvements to the GDB support). Being able to read GDB is certainly within the "spirit" of GPSBabel. On 7/20/2023 12:56 PM, tsteven4 wrote: > > mapsource is dead, garmin hasn't updated it since 2010. > > garmin did update basecamp in 2023. > > gpsbabel support for gdb is on life support. However, your issue was > technically interesting, so despite limited enthusiasm for the gdb > format a fix is in process. > > Note that current gpsbabel provided windows installer requires >= > Windows 10 (gpsbabel 1.8.0). It is still possible to build with Qt > 5.12 which requires >= Windows 7. In the near future Qt 5 will no > longer be supported, and >= Windows 10 will be required. I suspect > you don't have windows 10 on your 2013 PC, if so you will need to > build gpsbabel with the fixes and Qt 5 before we drop support for Qt 5. > > On 7/19/2023 5:36 AM, Gary Turner wrote: >> >> Sorry, I didn't have a copy of the old email still, so wasn't able to >> reference it. This PC is 2013 vintage. >> >> We're not using Mapsource for these files. We load the GDB files into >> a legacy map editor, that runs way faster with GDB files rather than >> gpx files. 'We' here is a local open source map project, so we're not >> making any money out of it. >> >> You're right. Mapsource gurgles a bit on a few thousand points. But >> as above, that's not relevant to us. The editor we use is OK with GDB >> files this size though. >> >> Sorry, but I still have to disagree that GDB is dead. I still use >> Mapsource regularly, given what a joke Basecamp was, and although >> Mapsource handles GPX, it's not particularly robust at it. >> >> On 19/07/23 22:46, Robert Lipe wrote: >>> Good grief. When referencing problems I've already personally >>> diagnosed for you that were 13 YEARS ago, please at least include >>> the subject. This was from Jan 30, 2012. >>> >>> The fundamental problem is that you're doing GIS-class tasks with >>> consumer-grade software (Mapsource) that isn't. Even other people >>> chimed in on that thread that Mapsource locked up on WAY smaller >>> files than you were asking us to produce (without us), even once it >>> was produced. >>> >>> Mapsource reads GPX. No conversion is even necessary. >>> >>> We do have better infrastructure that might be possible to speed >>> that up, but this is basically custom development work in an >>> otherwise dead format. Creating 650,000 points (that have non-unique >>> locations and names - and your source file DID have collisions - >>> it's not just a sorting problem) into software that requires unique >>> names (Mapsource) is always going to be a bad fit. >>> >>> With the infrastructure we now have in place, speeding it up is >>> possible (perhaps ismo would like to do the work as a consulting >>> project for you) but validating the result in a generally useful way >>> isn't at all easy. >>> >>> >>> >>> I should have deleted GDB format ten+ years ago... >>> >>> >>> >>> >>> On Tue, Jul 18, 2023 at 6:57 AM tsteven4 <tst...@gm...> wrote: >>> >>> I can't find the context of this thread. Without a test case >>> including >>> input data files and the specific gpsbabel command line you are >>> using >>> this is not going anywhere. >>> >>> On 7/18/2023 1:36 AM, Gary Turner wrote: >>> > Quite some time ago, I asked about why it took a long time for >>> > GPSBabel to do my conversions. >>> > To convert a file with 600,000 odd points from GPX to GDB >>> takes around >>> > 6 hours. >>> > Back then, from memory, Robert had a look at it, and thought >>> that the >>> > issue might be sorting. Again, from memory, he said that GDB >>> files had >>> > to be sorted. >>> > I had a thought recently - might it be possible to 'bin' the >>> data, >>> > e.g. into say 0-9 and A-Z, and then only sort each of these >>> bins, and >>> > then assemble the sorted bins in correct order? Would that be >>> quicker? >>> > >>> > >>> > _______________________________________________ >>> > Gpsbabel-misc mailing list http://www.gpsbabel.org >>> > Gps...@li... >>> > To unsubscribe, change list options, or see archives, visit: >>> > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc >>> >>> >>> _______________________________________________ >>> Gpsbabel-misc mailing list http://www.gpsbabel.org >>> Gps...@li... >>> To unsubscribe, change list options, or see archives, visit: >>> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc >>> > > > _______________________________________________ > Gpsbabel-misc mailing listhttp://www.gpsbabel.org > Gps...@li... > To unsubscribe, change list options, or see archives, visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc |
From: tsteven4 <tst...@gm...> - 2023-07-20 16:56:31
|
mapsource is dead, garmin hasn't updated it since 2010. garmin did update basecamp in 2023. gpsbabel support for gdb is on life support. However, your issue was technically interesting, so despite limited enthusiasm for the gdb format a fix is in process. Note that current gpsbabel provided windows installer requires >= Windows 10 (gpsbabel 1.8.0). It is still possible to build with Qt 5.12 which requires >= Windows 7. In the near future Qt 5 will no longer be supported, and >= Windows 10 will be required. I suspect you don't have windows 10 on your 2013 PC, if so you will need to build gpsbabel with the fixes and Qt 5 before we drop support for Qt 5. On 7/19/2023 5:36 AM, Gary Turner wrote: > > Sorry, I didn't have a copy of the old email still, so wasn't able to > reference it. This PC is 2013 vintage. > > We're not using Mapsource for these files. We load the GDB files into > a legacy map editor, that runs way faster with GDB files rather than > gpx files. 'We' here is a local open source map project, so we're not > making any money out of it. > > You're right. Mapsource gurgles a bit on a few thousand points. But as > above, that's not relevant to us. The editor we use is OK with GDB > files this size though. > > Sorry, but I still have to disagree that GDB is dead. I still use > Mapsource regularly, given what a joke Basecamp was, and although > Mapsource handles GPX, it's not particularly robust at it. > > On 19/07/23 22:46, Robert Lipe wrote: >> Good grief. When referencing problems I've already personally >> diagnosed for you that were 13 YEARS ago, please at least include the >> subject. This was from Jan 30, 2012. >> >> The fundamental problem is that you're doing GIS-class tasks with >> consumer-grade software (Mapsource) that isn't. Even other people >> chimed in on that thread that Mapsource locked up on WAY smaller >> files than you were asking us to produce (without us), even once it >> was produced. >> >> Mapsource reads GPX. No conversion is even necessary. >> >> We do have better infrastructure that might be possible to speed that >> up, but this is basically custom development work in an otherwise >> dead format. Creating 650,000 points (that have non-unique locations >> and names - and your source file DID have collisions - it's not just >> a sorting problem) into software that requires unique names >> (Mapsource) is always going to be a bad fit. >> >> With the infrastructure we now have in place, speeding it up is >> possible (perhaps ismo would like to do the work as a consulting >> project for you) but validating the result in a generally useful way >> isn't at all easy. >> >> >> >> I should have deleted GDB format ten+ years ago... >> >> >> >> >> On Tue, Jul 18, 2023 at 6:57 AM tsteven4 <tst...@gm...> wrote: >> >> I can't find the context of this thread. Without a test case >> including >> input data files and the specific gpsbabel command line you are >> using >> this is not going anywhere. >> >> On 7/18/2023 1:36 AM, Gary Turner wrote: >> > Quite some time ago, I asked about why it took a long time for >> > GPSBabel to do my conversions. >> > To convert a file with 600,000 odd points from GPX to GDB takes >> around >> > 6 hours. >> > Back then, from memory, Robert had a look at it, and thought >> that the >> > issue might be sorting. Again, from memory, he said that GDB >> files had >> > to be sorted. >> > I had a thought recently - might it be possible to 'bin' the data, >> > e.g. into say 0-9 and A-Z, and then only sort each of these >> bins, and >> > then assemble the sorted bins in correct order? Would that be >> quicker? >> > >> > >> > _______________________________________________ >> > Gpsbabel-misc mailing list http://www.gpsbabel.org >> > Gps...@li... >> > To unsubscribe, change list options, or see archives, visit: >> > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc >> >> >> _______________________________________________ >> Gpsbabel-misc mailing list http://www.gpsbabel.org >> Gps...@li... >> To unsubscribe, change list options, or see archives, visit: >> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc >> |
From: tsteven4 <tst...@gm...> - 2023-07-20 16:49:26
|
This isn't checked in yet, but it looks promising. > $ time ./gpsbabel -i gpx -f Auckland-numbers.gpx -o gdb -F > Auckland-numbers.gdb > > real 0m5.672s > user 0m5.423s > sys 0m0.217s |