GoogleGeorge
Autopilot for Google Earth Flight Simulator


GoogleGeorge is an autopilot that flies the Google Earth Flight Simulator. It's a free Windows program. It was designed for Windows XP, but it should also run under later versions of Windows.

GoogleGeorge provides automatic control of the following flight parameters:

It also has the following features:

Downloading


Running


Normal view

Normal View

This is GoogleGeorge's normal view. It has the following controls:


Controlling GoogleGeorge


Flying a circuit


Flight Plan

GoogleGeorge can be made to follow a flight plan consisting of a list of waypoints and other instructions in a plain text file. Here is an example:

Let's go!, TakeOff, 500, 3000, 500
Raise landing gear, Gear
Slow down a bit, Speed, 300
Long Beach, Waypoint, 40 35 19 N, 73 29 28 W, 3000
Lower landing gear, Gear
La Guardia runway 31, Land, 40 46 19.48 N, 73 51 25.64 W, 7, 302.25

If the F16 plane is sitting on runway 13R at JFK, then this list of instructions will cause the plane to take off, raise the gear, fly around for a few minutes, line up with La Guardia runway 31, lower the gear and land. A detailed explanation of these instructions is given below.

To activate this flight plan, copy and paste the list of instructions above to a text file, run GoogleGeorge, choose "Flight Plan..." from GoogleGeorge's "Options" menu, then in the Flight Plan dialog box click the "Open..." button, and open the text file. Then click the "Add all at start" button, and then click the "Start" button. See below for more details.


Entering waypoints and other instructions

Each waypoint or other instruction is described by a single line in a text file. The line starts with the name of the waypoint/instruction, which can be any text you like, so long as it does not include a comma (","), for example Let's go!, or La Guardia runway 31. Following the name is a comma, then the type of the waypoint/instruction, which must be one of the following words (exactly as shown, with no spaces):

Following that is another comma, and then a list of values separated by commas. The number of values and their meaning depend on the type of instruction, as follows: Latitude and longitude should be given in degrees, minutes and seconds, followed by N or S (for the latitude), E or W (for the longitude). Minutes and seconds may be omitted, and fractional values may be used. So 51 degrees 28 minutes 20.28 seconds North may be written as any of the following:
  • 51 28 20.28 N
  • 51 28.338 N
  • 51.4723 N
The meanings of the instructions in the example above are:
Let's go!, TakeOff, 500, 3000, 500
  • The name of this instruction is Let's go!
  • The type of this instruction is TakeOff, which requires 3 values:
    • Speed is 500 knots
    • Vertical speed is 3000 feet per minute
    • Target height is 500 feet above the ground
Raise landing gear, Gear
  • The name of this instruction is Raise landing gear
  • The type of this instruction is Gear, which requires no further values
Slow down a bit, Speed, 300
  • The name of this instruction is Slow down a bit
  • The type of this instruction is Speed, which requires 1 value:
    • Target speed is 300 knots
Long Beach, Waypoint, 40 35 19 N, 73 29 28 W, 3000
  • The name of this instruction is Long Beach
  • The type of this instruction is Waypoint, which requires 2 or 3 values – in this case there are 3 values:
    • Latitude is 40 35 19 N
    • Longitude is 73 29 28 W
    • Altitude is 3000 feet above sea level
Lower landing gear, Gear
  • The name of this instruction is Lower landing gear
  • The type of this instruction is Gear, which requires no further values
La Guardia runway 31, Land, 40 46 19.48 N, 73 51 25.64 W, 7, 302.25
  • The name of this instruction is La Guardia runway 31
  • The type of this instruction is Land, which requires 4 values:
    • Latitude is 40 46 19.48 N
    • Longitude is 73 51 25.64 W
    • Altitude is 7 feet above sea level
    • Heading is 302.25 degrees

Menu options


Flight Plan dialog box

Waypoints dialog box
Click to enlarge


Diagnostic view

Diagnostic View
Click to enlarge

This shows some of the internal working of GoogleGeorge. Most of the controls use PID controllers, and the multipliers are in the block on the left. You shouldn't need to change anything here. If GoogleGeorge has problems communicating with Google Earth then the "Info" window might indicate what the problem is.


Release history


Notes

If you have any problems with GoogleGeorge or suggestions for improvement then email me by clicking here.

Cheers,
Chris Hills.


Links

  • GoogleGeorge_v1p0.exe
  • GoogleGeorge20101120.exe
  • GoogleGeorge_v1p1.exe
  • GoogleGeorge_v2p0.exe
  • GoogleGeorge_v2p1.exe
  • GoogleGeorge_v2p2.exe

  • All text and images on this website are © Copyright Chris Hills 2010 - 2017, or their respective copyright holders.