When I open the KML file generated by marble on maemo with marble desktop,there're no problems. However,when I try to open the same KML file with google earth,the track is totally different from what it looks on marble desktop. pls see attached screenshot for comparison.
Created attachment 61024 [details] Screenshot opening same KML with marble desktop and google earth
Hi, thanks for reporting this bug. Some initial thoughts: - Could you provide the generated KML for debugging? - Does Google Earth really just render a straight line? Or does the rendering otherwise continue in Hongkong just like in Marble? In that case I suspect that there is an initial node prepended that Marble doesn't render which is rendered in Google Earth.
- Generated KML attached - I opened the track in google earth again and zoom in to check,you're right. It looks like Marble ignore the first and the last couple of track points but google earth will not. That's why the track looks different but I don't know how to fix it. I also attach the screenshot for your reference. It may help.
Created attachment 61066 [details] KML file generated by Marble on maemo
Created attachment 61067 [details] Deep zooming-in to check marble-generated KML in google earth
Ok,I dived into the generated KML file and removed the first couple of track points whose coords looks very similar and opened it in google earth again. Guess what! The track display correctly(see attach). So question is why does Marble save these track points in the KML file and ignore them when opening the file? Seems Marble is tolerant for some problem KML files but others not.
Created attachment 61069 [details] KML file display correctly in google earth after removing first couple track points
One possible culprit is the fact that we record initial track positions irrelevant of their quality (for instance in n900, initial positions are quick to arrive but way off the exact position). A point to take also is we wouldn't zoom out to the extent of the track while opening the file (yet). Points for improvements: - zoom to file extents (the last point to close bug #) - do not save track points with bad quality, taking into account indicators like hdop, vdop, accuracy indicators... )
Git commit 5f34651b2f1e28d053324936d181503898ee0f5d by Thibaut Gridel. Committed on 11/09/2011 at 15:53. Pushed by tgridel into branch 'master'. PositionTracking: only keep detailed level accuracy positions BUG: 275746 M +5 -4 src/lib/PositionTracking.cpp http://commits.kde.org/marble/5f34651b2f1e28d053324936d181503898ee0f5d
Git commit 64ca5a73c965812558ba88072fbbd16692ba645b by Thibaut GRIDEL. Committed on 26/09/2011 at 22:31. Pushed by tgridel into branch 'KDE/4.7'. PositionTracking: only keep detailed level accuracy positions BUG: 275746 (cherry picked from commit 5f34651b2f1e28d053324936d181503898ee0f5d) M +5 -4 src/lib/PositionTracking.cpp http://commits.kde.org/marble/64ca5a73c965812558ba88072fbbd16692ba645b