I copied this sample map and the kml file it displays: http://code.google.com/apis/maps/documentation/javascript/examples/layer-kml.html
I deleted the zoom setting so my version lets Google set the zoom based on the data in the KML file. Here’s my version: http://www.mappingsupport.com/test_ng_topo/cta-layer-kml.html So far so good. Next I added these lines to the KML file: <LookAt> <longitude>-87.707291</longitude> <latitude>41.855754</latitude> <range>1</range> </LookAt> Here is the new KML file: http://www.mappingsupport.com/test_ng_topo/cta-lookat-1.kml Here is my map displaying the new KML file: http://www.mappingsupport.com/test_ng_topo/cta-layer-kml-lookat-1.html Obviously the <range> value causes the map to zoom in all the way. This doc http://code.google.com/apis/kml/documentation/kmlelementsinmaps.html states that Maps does not support <LookAt> but does support <range>. Pardon me Google but I am struggling to comprehend how this makes sense. Why should Maps support a sub-component of a bigger thing that is not supported? More to the point, how does it make sense to allow a <range> value to override the default zooming for KML files? Does this behavior reflect a bug? Is there some reasonable way I can have my maps use the default KML zooming even if the KML file contains a <range> value? -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
