Hi Lance, really appreciate the replies...helps a lot. I'm starting to get the main point: - rendering KML on Gmap will not display placemark names. In order to get the KML placemark names to display on Gmap must parse the KML file, using EGeoXml and Elabels.
The above seems like a whole lotta extra work, and it would seem that Gmap would simply behave the same way as Google Earth when it comes to the display of the KML placemark name, but sigh, the two do not behave the same way, hence the need for ya'lls js libraries. Again, thanks mucho for the links, the extra patience & explanations...just when I climb one hill, another appears... 4est On Feb 9, 7:50 am, Lance Dyas <lancealand...@gmail.com> wrote: > On Mon, Feb 8, 2010 at 3:58 PM, Woody <horn...@gmail.com> wrote: > > Hi Lance, > > mucho thanks for the reply...but sigh, I'm still in a bit of > > denial...and a bit confused...I was hoping to keep my web page > > abstracted from the whole chore of displaying the icon label name...as > > in Google Earth that label display was already accomplished within the > > KML itself. > > > Sooo...some dumb question: > > > A.) I briefly looked through the Elabels js and also the GeoXML js > > documentation before I posted this question (as other folks seemed to > > have a similar challenge with the Gmap kml icon display). But these js > > libraries seemed to only pertain to the JavaScript on the web page > > itself? > > how is that that a problem? > > > ...and as far as I know, there's no way to embed JavaScript > > within a KML itself, only HTML (plz correct me if I'm wrong on this). > > javascript doesnt need to be operating inside the kml. > > a short ways down this pagehttp://econym.org.uk/gmap/egeoxml.hml > there is a description of how to use Elabels with EGeoXml > the technique is virtually the same with GeoXml except their are two style > classes > polylabelclass and pointlabelclass. (placemarks use the latter) > > here is an example with polygons and > GeoXmlhttp://www.dyasdesigns.com/geoxml/gmlusa.htm > > Note neither will work with cross domain data sources unless you use a proxy > to act as a reflector > > I am doing something like it here (no I dont have labels turned > on)http://www.microimages.com/ogc/newtntmap/gmap.htm?kml=http://www.lumi... > > Nor will they work with KMZ (those are zip files not readable client side > this too could be solved with a server side unzipping mechanism) > > In spite of those limits, the clientside parsers have a number of advantages > they can load local files (so you can preview locally), they avoid being > cached by google so you dont worry about them being out of date as much.. > you can access individual > components of a kml you have loaded and many more possibilities. -- You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to google-maps-...@googlegroups.com. To unsubscribe from this group, send email to google-maps-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.
