Documentation of KmlLookAt behaviour

[GoogleCodeExporter]

I have an app which controls the position of a KmlLookAt which follows a
“Target Point” along a pre-defined track (downloaded from a GPS with
lat/long/alt and time) across the ground. I find that the KmlLookAt’s
position generally follows my commands, but also has a “mind of its own”
especially when its close to the ground. It can often be observed to
position itself with effectively a larger Range value than I have supplied.  
There is nothing in the documentation that indicates that the
KmlLookAt.setRange function would do other than actually position the
KmlLookAt, so I have spent many hours debugging my code for a cause.
I have concluded that this is probably an intended behaviour, but it is a
bit of an annoyance when I have gone to the trouble of precisely
calculating the co-ordinates, to find them” hijacked” by a helpful(?) genie
behind the scene in the API. 
Much time and frustration would have been saved if the documentation had
provided a fuller explanation this behaviour.
(PS I Love the whole Google Earth product and geapi in particular - more
power to you all)

Original issue reported on code.google.com by gpsanima...@gmail.com on 10 Jan 2009 at 4:14

[GoogleCodeExporter]

Hi,

You may want to use KmlCamera since that offers much more control over the 
camera
position. KmlLookAt.setRange simply sets the desired range, the [rather 
complex] view
logic then kicks in to place the camera properly.

- Roman

Original comment by api.roman.public@gmail.com on 21 Jan 2009 at 1:24

• Changed state: WontFix