Oregon 550T missing waypoints - Help please

My Oregon 550T cannot seem to locate the waypoints stored in it. In Basecamp, after attaching my unit, when I click on | Devices | Oregon 550 | All Data, the waypoints show up properly.

In the Garmin Oregon | Garmin | GPX directory, there is a waypoint.gpx file. Looking at its contents with notepad, I see the names of the missing waypoints amongst a lot of other data.

I did a restore from Basecamp, but the Oregon unit still does not see any waypoints.

Help please (thanks).

-Dale-
  • Former Member
    0 Former Member over 14 years ago
    This seems like an Oregon problem. These devices, especially the newer Oregons have a lot of bugs in reading and writing correct gpx files. Attach your gpx file here and someone should be able to take a look at it and figure out what is tripping up the Oregon.
  • So far I have discovered that there was a missing Current.GPX file in the Current folder. I don't know what phantom made that disappear.

    From Basecamp, I've learned that I can select a waypoint, then make any change to it's properties, and exit. The changed waypoint now will appear on the Oregon device. I wish there were a more global way to resurrect all of the missing waypoints that are still correctly showing in Basecamp from my device, but I haven't stumbled on any way, yet.
  • Using my previously learned way to restore a single waypoint, I selected all waypoints in the properties window of Basecamp and globally changed the Icons, then exited. Now I have all my waypoints back in the device again. That's a pretty extreme way to do it, but it worked. No doubt someone will figure an even better way, but the whole problem really sucks.

    I discovered the missing waypoints when out kayaking yesterday, which, of course, was when I needed them. Other than putting fresh batteries in the device, which was powered off beforehand, I have no explanation why this loss of critical data occured.
  • Former Member
    0 Former Member over 14 years ago
    These Oregon devices are notorious for their non-acceptance of correct gpx files. In this case though, the culprit is the missing current.gpx. Can't imagine what you had in your data to make the device unhappy.