Maximum Plucker Waypoints?

[+zahadoom]

Anyone else have issues with Plucker and large GPX files?

 

I have a 300km 500max waypoint pocket query, and I just can't get plucker to process it... Goes up to 16,000 files, when it gets those down to 6000, thats where is starts freezing up and doing it one by one...

 

Ive tryed everything, seems its the Large files?

 

Anyone else have this problem, whats the maximum waypoints I can process into it and get results?

[+PDOP's]

I regularly use Plucker with a couple of thousand caches. Which software are you using to process the GPX files into HTML?

[+Shilo]

Glad I did a search on this and not start another topic

I just started having this trouble recently. About the same time the new google maps showed up. Can this be causing problems?

I am having trouble getting .gpx files of 450 caches or more to work. Twice now on 2 different regions. I use to do 500 cache files.

I re-installed plucker and still the same problem.

I'm using GPX Spinner for my .gpx file.

Any help or suggestions?

[+Lasagna]

This has been discuss on a number of threads previously ... Plucker has been known to freeze up. Two things to try ...

 

1. Change the order in which Plucker finds the files to enumerate (think the default is depth then across, change it to across then depth -- whichever it is presently, try the other).

 

2. If that doesn't work, try generating the Plucker PDB file using SunriseXP. It generates Plucker format outputs just like the Plucker desktop software does but is much faster and I've never had it hang up. The software's free and you continue to use the Plucker reader on your handheld to view the results.

[+Shilo]

This has been discuss on a number of threads previously ... Plucker has been known to freeze up. Two things to try ...

 

1. Change the order in which Plucker finds the files to enumerate (think the default is depth then across, change it to across then depth -- whichever it is presently, try the other).

 

2. If that doesn't work, try generating the Plucker PDB file using SunriseXP. It generates Plucker format outputs just like the Plucker desktop software does but is much faster and I've never had it hang up. The software's free and you continue to use the Plucker reader on your handheld to view the results.

Thank you for the answers. I'll try both solutions you gave. I did a search and this was the first thread to show up. I'll search again and read up on those as well.

 

UPDATE: I think I did #1. It says breadth first and I changed it to depth first. Instead of locking up in the beginning it locks up near the end. I never found anything like you posted. Maybe I looked in the wrong place. Let me know

Edited May 24, 2006 by Shilo

[+PDOP's]

Bad HTML on a cache page can freeze up Plucker. See this topic on the GSAK support forums.

[+Shilo]

Bad HTML on a cache page can freeze up Plucker. See this topic on the GSAK support forums.

What that user experienced is exactly what I'm having a problem with. It hangs on a file and I can't scroll down fast enough to find it.

I'll go see what this 'Tidy' thing is. I'm so computer illiterate

[+Lasagna]

Here's the link for the Sunrise XP converter ... it works where Plucker Desktop fails ...

 

http://www.sunrisexp.com

[+Shilo]

Here's the link for the Sunrise XP converter ... it works where Plucker Desktop fails ...

 

http://www.sunrisexp.com

ok Thanks. I'll read up on it

[+Shilo]

I did find a work around for the problem I'm having with plucker hanging up. It was bad html in a cache page.

This is what I did:

Once plucker hangs, hit Ctrl/ALT/DEL and goto processes and 'end process' on python.exe. Go back to plucker and scroll down to the last cache on the list. This is the one with bad html. Enter a search on geocaching.com for that waypoint and add it to your ignore list. Re-adjust your PQ so the 'ignore caches list' (or whatever it called) box is checked and re-run your PQ. Should work fine now unless you have more than one cache with bad html or you run 5 PQ's that day then you can't re-run it until the next day.

Not really a fix to the problem but it got me through it.

Also, if you find a bad html cache page you might want to let the cache owner know as well so it can be fixed.

[+PDOP's]

....Once plucker hangs, hit Ctrl/ALT/DEL and goto processes and 'end process' on python.exe. Go back to plucker and scroll down to the last cache on the list. This is the one with bad html.

 

Thanks for the tip Shilo.