|
Jörg Hofmann
|
|
|
Group: Forum Members
Posts: 8,
Visits: 5
|
Hi everybody.
Are there some GoogleEarth Specialists here?
Flightlogs can be displayed relatively simply and well in Google Earth.
But i want: A in SD planned flight (e.g. the austrian alps region) Pre-View in Google Earth also. Not also as track on ground, i just want to see (and "feel" theoretical) how my planned altitudes are safe for me, cause in Google Earth i can see neighboring terrain.
Can i arrange this? how?
|
|
|
|
|
pgroell
|
|
|
Group: Forum Members
Posts: 99,
Visits: 17K
|
I do the following on a PC.
- save the route as GPX file
- open GPX file with Google Earth (I am using the free Pro version)
- upon import, Google Earth opens a pop-up asking a few options, select all the options.
You are done.
|
|
|
|
|
Jörg Hofmann
|
|
|
Group: Forum Members
Posts: 8,
Visits: 5
|
+xI do the following on a PC. - save the route as GPX file - open GPX file with Google Earth (I am using the free Pro version) - upon import, Google Earth opens a pop-up asking a few options, select all the options. You are done. Ok. Same here. But after importing i see the planned Track lying on the ground. The planned altitudes where not considered!?
|
|
|
|
|
pgroell
|
|
|
Group: Forum Members
Posts: 99,
Visits: 17K
|
+x+xI do the following on a PC. - save the route as GPX file - open GPX file with Google Earth (I am using the free Pro version) - upon import, Google Earth opens a pop-up asking a few options, select all the options. You are done. Ok. Same here. But after importing i see the planned Track lying on the ground. The planned altitudes where not considered!? A I understand it, it is because the planned altitudes are not part of the elements considered by Google Earth. See below the format of a reporting point in GPX -------------------------------------------------------------- <rtept lat="48.458140" lon="3.533306"> <ele>95.0000</ele> <name /> <extensions> <skd:level type="A" value="4500" /> </extensions> ------------------------------------------------------------- <ele> is the elevation of the reporting point in meters <skd:level type="A" value="4500" /> is the planned altitude (type = "A") Google Earth only uses the <ele> part and not the planned altitude which seems proprietary information for Skydemon. I think that to do what you want you would have to create a routine to reformat the GPX file to a KML file.
|
|
|
|
|
pgroell
|
|
|
Group: Forum Members
Posts: 99,
Visits: 17K
|
+x+x+xI do the following on a PC. - save the route as GPX file - open GPX file with Google Earth (I am using the free Pro version) - upon import, Google Earth opens a pop-up asking a few options, select all the options. You are done. Ok. Same here. But after importing i see the planned Track lying on the ground. The planned altitudes where not considered!? A I understand it, it is because the planned altitudes are not part of the elements considered by Google Earth. See below the format of a reporting point in GPX -------------------------------------------------------------- <rtept lat="48.458140" lon="3.533306"> <ele>95.0000</ele> <name /> <extensions> <skd:level type="A" value="4500" /> </extensions> ------------------------------------------------------------- <ele> is the elevation of the reporting point in meters <skd:level type="A" value="4500" /> is the planned altitude (type = "A") Google Earth only uses the <ele> part and not the planned altitude which seems proprietary information for Skydemon. I think that to do what you want you would have to create a routine to reformat the GPX file to a KML file. I found a kind of solution to your problem but you have to experiment a bit. First you will need to open the GPX file with a text editor (Notepad ++ or any other), and replace <skd:level type="A" value="4500" /> with <altitude>4500</altitude> for every leg you have created ( if you don't change altitude or level too meuch then bulk Search and replace works). You might have to delete the <extensions> and </extensions> lines (I deleted them but have no time to test with the lines undeleted). Then go to this website http://www.gpsvisualizer.com/map_input?form=googleearth It will create a KMZ or KML file from the GPX file. There are many options, you will have to experiment. It is akward but it works.
|
|
|
|
|
Jörg Hofmann
|
|
|
Group: Forum Members
Posts: 8,
Visits: 5
|
I will try asap and will report here. So much thanks for the moment, i think you got it!
|
|
|
|
|
Jörg Hofmann
|
|
|
Group: Forum Members
Posts: 8,
Visits: 5
|
So - this works. Great. But the way is a bit long :-( Anyway, THANK you so much, pgroell! Let me summarize the steps: 1) Open the SkyDemon outputed GPX File with a Text-Editor. 2) replace lines like <skd:level type="A" value="4500" /> with <altitude>4500</altitude> 3) remove <extensions> and </extensions> lines. This has to been done! 4) save the GPX File and close it 5) load up this GPX File here: http://www.gpsvisualizer.com/map_input?form=googleearth right side of the window! 6) change these settings in the left half window, middle section: Altitude mode to "extruded" . choose also line width and desired colour and change the units (left window on top) to nautical! 7) klick on "Create KML File" on the right side. Wait. 8) open / import the produced Kml File to Google Earth 9) Enjoy ;-)
|
|
|
|
|
Jörg Hofmann
|
|
|
Group: Forum Members
Posts: 8,
Visits: 5
|
+xSo - this works. Great. But the way is a bit long :-( Anyway, THANK you so much, pgroell! Let me summarize the steps: 1) Open the SkyDemon outputed GPX File with a Text-Editor. 2) replace lines like <skd:level type="A" value="4500" /> with <altitude>4500</altitude> 3) remove <extensions> and </extensions> lines. This has to been done! 4) save the GPX File and close it 5) load up this GPX File here: http://www.gpsvisualizer.com/map_input?form=googleearth right side of the window! 6) change these settings in the left half window, middle section: Altitude mode to "extruded" . choose also line width and desired colour and change the units (left window on top) to nautical! 7) klick on "Create KML File" on the right side. Wait. 8) open / import the produced Kml File to Google Earth 9) Enjoy ;-) Edit: Point 2) has to be changed the data from feet to meter. Correct it must be: 2) replace lines like <skd:level type="A" value="4500" /> with <altitude>1372</altitude> otherwise the line in Google Earth won't be comporable in heights and elevations.
|
|
|
|
|
emporer
|
|
|
Group: Forum Members
Posts: 69,
Visits: 5
|
I have for you this workaround:
- plan your route in SD
-simulate the flight in SD or fly it in a flight sim
- a log file will be generated by SD
- select the log file and open it in google earth, you will see your track elevated over ground in whatever altitude you were simulating it
|
|
|
|
|
Jörg Hofmann
|
|
|
Group: Forum Members
Posts: 8,
Visits: 5
|
+xI have for you this workaround: - plan your route in SD -simulate the flight in SD or fly it in a flight sim - a log file will be generated by SD - select the log file and open it in google earth, you will see your track elevated over ground in whatever altitude you were simulating it Pls what? For about 3 hr. Trip i should wait at least 2hr. to get a log file written? Crazy... 
|
|
|
|
|
emporer
|
|
|
Group: Forum Members
Posts: 69,
Visits: 5
|
+x+xI have for you this workaround: - plan your route in SD -simulate the flight in SD or fly it in a flight sim - a log file will be generated by SD - select the log file and open it in google earth, you will see your track elevated over ground in whatever altitude you were simulating it Pls what? For about 3 hr. Trip i should wait at least 2hr. to get a log file written? Crazy... In flight sim you can increase the simulation speed, so you will have the log -date for an 3 h flight in 9 min
|
|
|
|
|
emporer
|
|
|
Group: Forum Members
Posts: 69,
Visits: 5
|
I have for you this workaround:
- plan your route in SD
-simulate the flight in SD or fly it in a flight sim
- a log file will be generated by SD
- select the log file and open it in google earth, you will see your track elevated over ground in whatever altitude you were simulating it
|
|
|
|