Which products are relevant to this feature request?
Google Earth - All
What should this feature enhancement do?
Allow the display of the coordinates of placemark in a balloon window. This may
not seem like something worthwhile to the end user, because they can get the
coordinates by right clicking and finding properties, or based on where their
mouse pointer is. However, this will allow for developers to do interesting
things. There is currently no way to get the coordinates of the current
balloon. Take the following situation:
A user has a kml file with many placemarks that were generated by a mySQL
database. He wants to move one of these placemarks to a different location,
using the Google Earth client interface. He moves the placemark, clicks on the
placemark to display the balloon and presses an update button. The new
coordinates are automatically placed in the link at the end of the url
(http://myserver.com/move.php?coordinates=$[coordinates]).
There are tutorials for the GE plugin that explain how to do the exact thing I
just described... and the tutorial states how useful this functionality is.
Here is the tutorial:
http://code.google.com/apis/maps/articles/phpsqlinfo.html#CreatingMap
Are there any currently known workarounds that produce the same, or
similar, result?
Not that I am aware of. The GE plugin has eventlisteners to add this ability,
however, the Google Earth client has no support for this, which seems strange
to me. Balloonstyle has support for all these $[name], $[description],
$[address], $[id], $[Snippet] but no support for $[coordinates] ? If there are
any workarounds, I would like to know about them.
Right now, the only way I can have a user move a placemark around and save it
to the database is by tweaking the <viewFormat> in network link to have the
user move to the new location and center it in the screen, then click an update
link and have it send the <viewFormat> lookatLat and lookatLong info in the url.
Original issue reported on code.google.com by Reno...@gmail.com on 23 Nov 2011 at 8:29
Original issue reported on code.google.com by
Reno...@gmail.comon 23 Nov 2011 at 8:29