How easy is it to load Waypoints
- Thread starter PeterBain
- Start date
trevpond
New Member
Hi,
At the moment, the only way would be to do it through Google Earth, then, using the program that is available via Dynon, to put it onto your Skyview via a USB stick as a User Waypoint.
I hope that V3.2 might include this so that you can do it directly.
regards
Trev
At the moment, the only way would be to do it through Google Earth, then, using the program that is available via Dynon, to put it onto your Skyview via a USB stick as a User Waypoint.
I hope that V3.2 might include this so that you can do it directly.
regards
Trev
- Joined
- Mar 23, 2005
- Messages
- 13,226
3.2 doesn't have the "ultimate" user waypoint system that we have in mind, but it does add the ability to point at a place on the map and add it to a flight plan. It doesn't stick around forever (unless you export the flight plan that contains that point), and they get auto-named as Map01, Map02, etc. So it's not the "final" user waypoint solution that lets you robustly edit waypoints on SkyView itself, but it adds more flexibility over what 3.1 is capable of.
tucsonphil
New Member
Along the lines of adding waypoint...routes...are there plans to support the Aspen "connect" protocol so I can load my route from ForeFlight Mobile to Skyview?
- Joined
- Mar 23, 2005
- Messages
- 13,226
We just learned about it at Oshkosh ourselves. At first glance, it looks like it's centered more around certified to handheld interfacing, and it may well be a proprietary Aspen interface. We're not really competitors, but still.... So that's a "we haven't really thought about it". We'll keep an eye on what's going on there, though.
It seeems Jeppesen have left us South Africans with the basics as far as roads,rivers and out of the way airfields.
We have a very good local flight Planner which can convert flight plans into gpx files.
I see the Goodgle system converts dup files.
what is in the pipeline for us from Jeppesen as far as getting us more useful data
Failing that how can we go about loading the local programs onto Skyview gpx files
We have a very good local flight Planner which can convert flight plans into gpx files.
I see the Goodgle system converts dup files.
what is in the pipeline for us from Jeppesen as far as getting us more useful data
Failing that how can we go about loading the local programs onto Skyview gpx files
- Joined
- Mar 23, 2005
- Messages
- 13,226
Let's be clear here: The Jeppesen NavData data includes airports, navaids, and airspace worldwide, period. No region is getting more data from Jeppesen than any other. Obstacle data includes just obstacles. The FAA data we're able to provide to US customers directly is a bit more robust on the private/small airports, but beyond that, the story is the same here on background data such as roads, rivers, and smaller/private airfields. They are not in the Jeppesen data, but we're working on solutions for those features which we know you want to see on the map.
A little more background here: what you think of as the complete "map" that you're picturing as the ultimate product you want (and that we will provide, eventually) is actually a bunch of layers of different data, all superimposed on each other and aggregated by a system like SkyView. Other systems, particularly many of the aviation portables, aggregate all of these different layers into single updates that they distribute as a single update. People tend to think of them as "Jeppesen" updates, but in reality they're Jeppesen NavData supplemented by a bunch of other third party data. This isn't obvious to most people, and frankly wasn't obvious to us, and this is why we're now figuring out what our customers (you) really want to see in mapping data. Anyway, thanks for your patience as we work through that discovery process and build in the features that you ask for.
A little more background here: what you think of as the complete "map" that you're picturing as the ultimate product you want (and that we will provide, eventually) is actually a bunch of layers of different data, all superimposed on each other and aggregated by a system like SkyView. Other systems, particularly many of the aviation portables, aggregate all of these different layers into single updates that they distribute as a single update. People tend to think of them as "Jeppesen" updates, but in reality they're Jeppesen NavData supplemented by a bunch of other third party data. This isn't obvious to most people, and frankly wasn't obvious to us, and this is why we're now figuring out what our customers (you) really want to see in mapping data. Anyway, thanks for your patience as we work through that discovery process and build in the features that you ask for.
Thanks for the update.
I am sure you are working frantically on this issue, as it makes or breaks the GPS side of things.
Would it be cheeky to ask for a time frame around this development?
If i was to download .gpx files from a local distributor www.aviationdirect.co.za could i in any way corrupt the Skyview?
Your thoughts on this would be greatly appreciated in order to get thru this dry period
I am sure you are working frantically on this issue, as it makes or breaks the GPS side of things.
Would it be cheeky to ask for a time frame around this development?
If i was to download .gpx files from a local distributor www.aviationdirect.co.za could i in any way corrupt the Skyview?
Your thoughts on this would be greatly appreciated in order to get thru this dry period
mmarien
Murray M.
I've been manually editing the dfg files and reloading them with no side effects - touch wood. : I've also added comments to the file for my own purpose and SV politely ignores the extraneous stuff. I think if the SV can't make sense of the file it just won't load it. The case in point is the old dup files created with the pre 3.0 Dynon Google earth export function. They just wouldn't load.
I've also added comments to the file for my own purpose and SV politely ignores the extraneous stuff. I think if the SV can't make sense of the file it just won't load it. The case in point is the old dup files created with the pre 3.0 Dynon Google earth export function. They just wouldn't load.