path not visible

2,222 views
Skip to first unread message

arian...@undp.org

unread,
Jan 25, 2008, 5:55:14 AM1/25/08
to KML Developer Support - Third Party Applications
I am running GE+ version 4.2.0. I used to import Garmin tracks and
other data from Garmin MapSource as well as dirctly from my hand held
eTrex to GE+.

Since one month I have updated the GE to 4.2.0 and the paths imported
are not visible except for when I right-click on the particular datum
and open the properties window, THEN the path appears!

Color and line width are not the issue. I have tried to start uo GE in
DirectX mode but the problem persists.

If somebody can help I can send the related .kml file.

Jonathan van Tuijl

unread,
Jan 25, 2008, 7:17:23 PM1/25/08
to KML Developer Support - Third Party Applications
> If somebody can help I can send the related .kml file.

There should be a link called "Files" at the far right. Go there,
upload the file (note that it'll be out there for everyone to see),
and post the file name here.

Jonathan

tffs

unread,
Feb 20, 2008, 8:34:33 PM2/20/08
to KML Developer Support - Third Party Applications
I'm having the same problem.
I download a track from a garmin GPS and save it as a GPX file then
open it in GE and it's invisible until I open the properties window.
I've also downloaded it a couple different ways including through
OZIExplorer and then used GPSBabel to translate it to KML. Same
result.

I've attached the KMZ file in the "FILES" section of the forum. It is
called recorrido.kmz.

Any ideas??

thanks in advance!!

Trent

Jonathan van Tuijl

unread,
Feb 21, 2008, 3:20:24 PM2/21/08
to KML Developer Support - Third Party Applications
You hit the max number of segments that Google Earth can display in
one path. Note that when you open the properties window, only red
squares appear where the vertices of the line are, not the line
itself. But the limit is somewhere between 30000 and 35000, I suspect
2^15 or slightly less, and your path only has 6973 segments. It failed
because the tessellate option told Google Earth to add extra segments.
Your path isn't sensitive at all to the problems that could occur
without the option, so it's safe to disable it. To disable it, extract
the KMZ file as a zip file (rename to .zip or force the zip utility if
you can), which should give you a file doc.kml. In that file, look for
<tessellate>1</tessellate> on one of the last lines, just before the
really long <coordinates>6974 vertices</coordinates> line, and replace
the 1 with a 0. Then save the file and open it the file in Google
Earth to see if it works. If you want a small KMZ file again, just zip
KML file and rename to .kmz. I'll upload my result as "recorrido
fixed.kmz".

Jonathan

ManoM

unread,
Feb 21, 2008, 6:08:09 PM2/21/08
to KML Developer Support - Third Party Applications
Some people have had success with dividing the coordinates between two
or more geometries, say two LineStrings, and putting them into a
<MultiGeometry> element.

ManoM

tffs

unread,
Feb 21, 2008, 6:15:13 PM2/21/08
to KML Developer Support - Third Party Applications
Jonathan, you are a genius!!! Thanks!!! I would have never figured
out that one. Although I thought it might have something to do with
the size of the path. I was actually planning to break it into several
paths using OZIExplorer or something like that and then trying it
again. But this solution is much better.

Thanks again!
Trent.

On Feb 21, 1:20 pm, Jonathan van Tuijl wrote:
> tffs wrote:
> > I'm having the same problem.
> > I download a track from a garmin GPS and save it as a GPX file then
> > open it in GE and it's invisible until I open the properties window.
> > I've also downloaded it a couple different ways including through
> > OZIExplorer and then used GPSBabel to translate it to KML. Same
> > result.
>
> > I've attached the KMZ file in the "FILES" section of the forum. It is
> > called recorrido.kmz.
>
> You hit the max number of segments that Google Earth can display in
> onepath. Note that when you open the properties window, only red
> squares appear where the vertices of the line are,notthe line
> itself. But the limit is somewhere between 30000 and 35000, I suspect
> 2^15 or slightly less, and yourpathonly has 6973 segments. It failed
> because the tessellate option told Google Earth to add extra segments.
> Yourpathisn't sensitive at all to the problems that could occur
Reply all
Reply to author
Forward
0 new messages