Yes, and even more intriguing due to the fact that "my" directions
element is under a separate namespace so presumably Earth should not
have any idea how to interpret it.  I may experiment later to see if
it is really because I have a directions element or if the same
behavior is elicited with any extended data element.  I suspect this
is an Earth bug since it really should be ignoring elements outside
the kml namespace... I think.
joe
On Jul 14, 8:22 am, Lance Dyas <[email protected]> wrote:
> That is intriguing.. I am pretty sure there isnt a <directions></directions>
> in the kml specification especially one with the namespace... heheh
>
> On Wed, Jul 14, 2010 at 8:18 AM, [email protected] 
> <[email protected]>wrote:> Hi all,
> > In response to a request by Lance, I edited a kml file and added the
> > extended data element to one of the placemarks exactly as indicated in
> > my previous post.  I was quite surprised to find that when I opened
> > the file in Google Earth, that one placemark behaved differently from
> > all others.  Only the placemark with the extended data element opened
> > an information baloon with directions to here / from here links.
> > I had expected that Earth would ignore the extended data element.
> > joe
>
> > On Jul 13, 10:00 am, "[email protected]" <[email protected]>
> > wrote:
> > > :) .... I think that problem is one that I brought up also, under an
> > > alter ego, bttman.  Sorry to be such a PITA.
>
> > > I am free to alter the kml.  I actually am generating it with Earth
> > > from gpx files that I export from garmin basecamp.  I would prefer not
> > > to have to add yet another step to the already tedious process, but
> > > your suggestion does make the most sense technically speaking.
> > > So, I guess we're talking about something like this perhaps???
>
> > >   <Placemark>
> > >     <name>Trailhead</name>
> > >     <!-- Imported schema requires use of namespace prefix -->
> > >     <ExtendedData xmlns:geoxml="http://www.dyasdesigns.com/geoxml/";>
> > >       <geoxml:directions>1</geoxml:directions>
> > >     </ExtendedData>
> > >     <Point>
> > >       <coordinates>-114.041,53.7199</coordinates>
> > >     </Point>
> > >   </Placemark>
>
> > > On Jul 13, 9:41 am, Lance Dyas <[email protected]> wrote:
>
> > > > On Tue, Jul 13, 2010 at 11:23 AM, Rossko <[email protected]>
> > wrote:
> > > > > > (or another attribute on the Placemark)
>
> > > > > That sounds smart ; any well-behaved KML parser would ignore
> > > > > attributes it doesn't understand, surely?
>
> > > > > > I was thinking would be a better  better solution... it would be
> > > > > relatively
> > > > > > natural.
>
> > > > > Sounds like Lance needs some encouragement to add this as a feature
> > to
> > > > >GeoXml
>
> > > > Will likely be looking in to it tonight.. there is an error with
> > regards to
> > > > markers not being created in a way that is google earth plugin friendly
> > I
> > > > need to get at too.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google Maps API" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> > [email protected]<google-maps-api%[email protected]>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/google-maps-api?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Maps API" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-maps-api?hl=en.

Reply via email to