I have a 296 which I sync with SD. Any waypoints not in the 296 are stored as user defined waypoints. Periodically I do a delete all on both routes and user def waypoints.

I think most of the flight planning packages do this. Howver, the key is to be able to delete them as a Group. This requires the planning software to put them in the same (but different from other dedicated Garmin points) category. Not sure if SkyDemon does this but I suspect it does  .. certainly the symbol is different.

So from time to time you can purge them without jeopardising other stuff.

D

have submitted the query to Garmin and Jeppesen. Will keep you posted if hear anything back.

We've spoken to a chap at Garmin UK technical support on the phone, I think his name was Alasdair.

Interesting....

I'm no expert on this, but it looks like your numbers are correct decimal formats of the AIP data, and the Jeppesen data is slightly different.



Do you have any contacts at Garmin/Jeppesen? I'd like to send them a query about their data.



Many thanks

It depends on the logic the Garmin device uses, but it seems like a good guess to me. We use the position as promulgated through the official AIP.

Just to follow up on this with some more info for you (since through further testing many waypoints that are in the Garmin DB get made as custom waypoints from a Skydemon route).



The positions seem slightly out between Skydemon and Garmin (current database)



Using Compton VOR (CPT) for example:



From the Skydemon plan (custom waypoint CPT created)

N 51 29.500

W001 13.183



CPT in Garmin 495 DB:

N 51 29.503

W001 13.179



I guess this slight discrepancy is why the custom waypoints are being created?

PS, having been evaluating skydemon web, and plan (on my mac through vmware) for the past weeks, I've now purchased.

It's a great product, and I hope it continues to evolve.

Thanks for the info.

We don't explicitly create any waypoints at all, the device does that on its own. I am aware that where possible we tell the device that a waypoint is likely to be in its own internal database, but this doesn't always work unfortunately. I think that's why you occasionally see a duplicate waypoint.