A decision to make now is how/if you want your KML to display with any other viewer, e.g. back in Google Earth or on someone else's map.
If you add a magic word to a placemark description, it'll normally be visible in other viewers - even in your own until/unless code is written to hide it. That might be fine for you. You could actually "hide" the magic message by something like inserting an empty <div class='xxx'> into the description with some magic class name, and hope that the chosen word should never match any genuine CSS where it might get displayed. A hidden div might also work, but there is more chance of some viewers ignoring inline CSS and displaying it anyway. To find any of those, you'd need to inspecta placemark's description before building the infowindow. I _think_ GeoXml allows you to specify a custom infowindow function to do that, wthout altering the basic tool? KML does allow for insertion of non-standard data, which will normally be ignored by ordinary viewers. This would leave your KML compatible with anyone else. http://code.google.com/apis/kml/documentation/extendeddata.html The ExtendedData with something like <directions>true</directions> might be simplest? I know not if this is easy to add from GE or if you would need to post- edit what GE produces to insert it. Then in your customised parser, for each placemark you'd need to look for the inclusion of the extended data. This is probably the most difficult but more 'correct' way to do it. -- 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.
