I got an Oregon 300 yesterday, and have successfully installed some OSM maps on it.
I'm confused by the handling of GPX files (on the additional microSD card) though:

- While I can delete all Waypoints (i.e. additional waypoints in GPX files), I'm apparently unable to remove Geocaches.

- Since I will use this unit to test and fix geo-html2gpx, how can I make sure that already stored GCs and WPs will be overwritten by a newly created GPX file?

- Is there a validity checker for GPX files somewhere? The Oregon seems to be more strict about file contents than my Nüvi was, and doesn't accept some points - it even happens that the main (GC) point isn't accepted while the additional WPs are.

And another somewhat related question: in PQ-generated GPX files, how are "yet undefined" points (stations of a multi, for example GC1XWDJ) represented?

TIA for any input!

Google: gpsbabel oregon gpx

Thanks for answering - isn't gpsbabel involved in processing awk output in geo-html2gpx, and shouldn't its output conform to some standards?
Never mind, there seems to be another (additional) limitation I ran into (with 3.40 software freshly loaded, if that matters): If I refresh the set of GPX files on the memory card, *different* GCs show up. In addition to 3 GCs that have been marked as "found", "Find a GC" shows me exactly 10 GC locations (but all additional waypoints). Removing them from the input allows an eleventh point to show up.
Very mysterious :(

Update on GPX structure: http://forums.groundspeak.com/GC/index.php?showtopic=43005&pid=505395&mode=threaded&show=&st= post #2 has some details...



Edited 1 time(s). Last edit at 12/06/2009 09:50AM by Steve8x8.

http://www.topografix.com/gpx_validation.asp

Thanks!
Making geo-html2gpx output getting close to passing the validation would require to activate the "long" <gpx> header already present in diff25 - with a proper replacement of the Creator= entry, of course... Still there's an issue with the postponed <sym> element:
"Message: element 'sym' is not allowed for content model '((ele,time,magvar,geoidheight,name,cmt,desc,src,url,urlname,sym,type,fix,sat,hdop,vdop,pdop,ageofdgpsdata,dgpsid),)'"
This looks like the only little issue (not affecting GPSr operation), and a major rewrite would be the only way to completely fix it.

Meanwhile I've found that the list of GCs shown on the Oregon depends a bit on the order of GPX files in the directory. All files throw the same message when validating. Looks like side-effects :(

What's strange indeed: if I plug the same µSD into my (not virgin though) nüvi, it will show the points...



Edited 2 time(s). Last edit at 12/06/2009 02:23PM by Steve8x8.

Found some very interesting "feature" hints in the Oregon Wiki FAQ (garminoregon.wikispaces.com) which may explain my findings with GPX files generated by geo-html2gpx and my new Oregon 300.
Patches for geo-html2gpx will show up over there, in the geo-html2gpx thread.

I think this thread can be closed...



Edited 1 time(s). Last edit at 12/07/2009 03:11PM by Steve8x8.