To be effective, triggering a click event would also need the ability to pass a location (where the click occurred) - preferably by latLng. This would allow features in a KMLLayer to be selected from external controls or the ability to link to a page with a specific KML feature's info window already open.

I agree this would be a good enhancement, an concur with Chad's assessment of passing a location in latlng.

Actually after having thought about this for a while, the KML feature id would be a much better/more accurate identifier from which to trigger the event.

I would suggest that it passes the latLng as well as the KML feature id, as this would have been useful in my implementation. 

I prefer the suggestion that the click passes the KLM feature id. That way it's simple. The KLM data includes latLng so is easily derived from the given id.

I think it all depends on how you intend to use this kind of event. For me, I would know the lat/long, and then I want to pass that lat/long to the KML so that the appropriate feature gets "clicked". I might not know the KML's feature id.

Take this mashup: http://gis.mda.state.mn.us/animord/
Imagine that, after typing in a city or zip to get an address match, that the KML overlay is then automatically "clicked" to reveal the pertinent animal ordinance. Right now the user can zoom, but then THEY have to click in the map to reveal the ordinance.

I'd love to see this, and the kml feature id being passed in option preferably. 
In the case of the getting a lat/lng from an address lookup and then clicking there, the odds a zip / postcode matching the pixel of a kml seems small to me, 
so i'd rather see that as another api call, featureIdFromPoint(LatLng) that could then be passed into the event trigger.

Matt, you have to look at my mashup use case to understand my scenario. The KML overlay in my map is a continuous coverage of polygons (not a set of discrete points or small polygons). So the "odds" of a lat lng from zip/post falling inside one of my KML features are actually pretty good.

Having said that, I understand needs for triggering a KML click both based on the feature ID or a lat/lng. If I understand your suggestion about the api call correctly, that sounds like a good method too.

(No comment was entered for this change.)

I am creating a ground snow load map with kml data from the ASCE 7-10.  My map/mashup is here: 
http://design.medeek.com/resources/snow/groundsnowloads.html

I would like to trigger a click or somehow extract the kml description attribute after using the geocode feature.  Currently this is missing and user is required to click to display this information, basically rendering my interactive map as broken.

Please add this feature or provide a workaround.

(No comment was entered for this change.)

Thank you for suggesting this feature, and for listing your use cases. It's a good idea.

(No comment was entered for this change.)