Categories: Problems and Errors : Windows :

Path is different in Google Earth Pro than it was in standard Google Earth

Showing 1-9 of 9 messages
Path is different in Google Earth Pro than it was in standard Google Earth Mike_W. 9/26/11 6:51 AM
Last week I started using the 7 day trial of Google Earth Pro.  I generated a .kml file a while back, which included a couple paths.  It displays fine in the free version of Google Earth, but when I try to open it in Pro, the lines no longer appear where they are supposed to.  The beginnings of the paths have disappeared, and seem to be replaced by a dashed line around the equator.  About the second half of the path does show up where it's supposed to, but the width oscillates between being much narrower and much wider than it should be.

I have noticed this behavior before I started using Pro.  In my .kml files, I use the "absolute" altitude setting, and I noticed that if I accidentially enter an altitude below where the ground is at a point, I will get the same ring around the equator and distorted lines.  But as I mentioned, the particular file I am trying to open works fine if I open it with the free version.  I had 5 seperate files that all were fine before I started using Pro, and 2 of them behave this way.  Unfortunately I can't come up with anything in common between the files that don't work that they don't have in common with the files that do.

Thanks in advance for the help, and if there is any more information that could help please let me know.
-Mike
Re: Path is different in Google Earth Pro than it was in standard Google Earth jasonM1 (GE TC) 9/26/11 10:41 AM
Assume the following example shows the same in both your GE versions.
http://kml-samples.googlecode.com/svn/trunk/kml/Placemark/LineString/styled.kml

Are both GE versions 6.1 or 6.0 ?

Do you have to use "absolute" or can you use "clampToGround" with tesselation enabled ??
http://kml-samples.googlecode.com/svn/trunk/kml/Placemark/LineString/tessellate.kml
http://code.google.com/apis/kml/documentation/kmlreference.html#tessellate
Re: Path is different in Google Earth Pro than it was in standard Google Earth Mike_W. 9/27/11 6:46 AM
Thanks for the quick reply!

That sample did show up the same in both.  Versions are:
Google Earth Pro                    6.1.0.4738 (beta)
Google Earth (free)                  6.0.3.2197

Should it display differently between versions?  I would think it would be set up to be backwards compatable.  The "KML Reference" site you linked is what I used when I was making my .kml files, and I didn't see anything in it anywhere that suggested it would behave differently for different versions, from what I recall (there was something about labels not showing up right in 6.1, but all my labels are showing up fine).

As far as the altitude mode, I think I need it set to "absolute".  Just to check, tessellate keeps the lines from going right along the surface of the Earth, and extrude puts the lines up in the air but draws a line down to the surface, correct?  If so, I think absolute altitude and extrude are going to be the way the particular project I'm working on will look best.
Re: Path is different in Google Earth Pro than it was in standard Google Earth jasonM1 (GE TC) 9/27/11 7:35 AM
It should absolutely be backward compatible. If ot then probably a bug. Correct about extrude and tessellate (only works with clamptoground mode).

Folks on the forum can help more if you could post a working example of your KML here. If you demonstrate the problem with a single placemark that would be great.
Re: Path is different in Google Earth Pro than it was in standard Google Earth Mike_W. 9/28/11 6:54 AM
The problem with that is that I don't always see this behavior for every file, and I can't find a way to reproduce it on demand.  When I make a new file, sometimes it shows up fine, and sometimes it comes out wrong.  I'm a little hesitant to just paste in the .kml code, because a lot of work went into generating the data in it and I really doubt the company I work for would want me to release it.  And since I don't know what the actual issue is that's causing this behavior, I can't just make a quick demo file that I know will have the problem.

The only other thing I can think of is that I frequently (but not always) get the - GE has encountered a problem and needs to shut down.  Do you want to send an error log - problem that I've seen before on this site.  I've kinda figured it is just an issue where my computer doesn't have the right hardware, since the other people in my office with newer computers never seem to have it.  I suppose it may be connected though.

I guess what I was really hoping for when I posted this was that it was a known issue that had a fix someone had figured out already that someone could give me a link to, or that Google was working on for the next update, but it doesn't look like I'm that lucky haha.
Re: Path is different in Google Earth Pro than it was in standard Google Earth jasonM1 (GE TC) 9/28/11 9:25 AM
As for the crashing issue there are some hints for that. Check out the related article and immediately delete your cache. Then check out updating the DirectX drivers and video card drivers.

Also if you haven't done it recently it's best to run disk fragmentor (one comes with windows in Accessories). That will help things run smoothly and making sure ~15% of disk is free space.
Re: Path is different in Google Earth Pro than it was in standard Google Earth filipferris 1/30/12 6:31 AM
I have the same problem as Mike_W, our balloon-flight-data has suddenly started showing up around equator. A kml-file is included. 
Re: Path is different in Google Earth Pro than it was in standard Google Earth Noisette 1/30/12 6:46 AM
Hi Filip,you have space between the coordinates.

From the release notes for 6.1:
To conform more closely with the OGC KML 2.2 standard, we've made the parsing of the <coordinates> tag more strict in version 6.1. Spaces must only be used to separate the (longitude,latitude,altitude) triplets which specify the coordinates of a single point. It is invalid to add spaces between individual coordinates. We understand that previous versions of the client were more lenient, so if your KML files contain spaces beween coordinates in coordinate triplets, an easy workaround is to remove all whitespace located immediately before or after commas inside a <coordinates> tag.
http://support.google.com/earth/bin/answer.py?hl=en&answer=40901

I used a text editor to do a search and replaces to get rid of the extra space, leaving only the comma, and it seems to be correct now.
Re: Path is different in Google Earth Pro than it was in standard Google Earth filipferris 1/30/12 6:57 AM
Thanks Noisette, I'll update our scripts. Big up from the so-called rocket scientists in Norway.