How does the macro detect groundlevel?

It will first look at the hmsl for the last 10 seconds and get a average height.

It will then add 50m/150 ft to this number to make sure you are in the air.

Find the row you are ground+50/150 and search in the rows below for a flare.

To find the flare it will look at the horisontal speed and match it with the "landingspeed".

This setting is called "Swoop end" and can be found at Google Earth settings.

The default value is 5 km/h or 3 mph, and this is the groundspeed at which it detects you as landed.

When it finds that your speed is below the setting it will make this as the groundlevel + 1.8m/6 ft.

Basically it will assume you made a standup landing and that you are about 1.8m tall.

keep in mind the inaccuracy of the GPS is far more than if you are only 1.6 m tall.

What is Swoop start and Swoop end?

This is the settings on how to calculate the swoop.

Swoop start is the altitude above ground that it will start "counting" the swoop from.

The default value is 3.5 m or 11 feet. The value comes from the 5 feet tall gates in swooping,

and then adding a "manheight" to this value.

If your feet is "touching the gates" at 5 feet and you are 6 feet with the FlySight on the helmet, thats 11 feet.

Swoop end is a horisontal speed. This is the speed that you land your canopy.

If you always run with the canopy (don't flare it all the way) you might need to set a higher value.

If you fly a slow canopy you might need to set a lower value.

There is a limit with these settings. If you jump in strong winds it can't detect the flare.

And that's because you are already below the Swoop end groundspeed on your final approach.

If this happens the macro will deactivate "swoop" and Google Earth will show "canopy" till you turn off the GPS.

Icon for landing accuracy?

This sets a "pin" on Google Earth showing the point where you wanted to land and calculates the distance to it.

To use it you first need to know the latitude and longitude of this point.

My advice is to place the FlySight on this point and turn it on and leave it there for a while (2-3 minutes).

This gives you a good reading on the loaction.

Open the file and look at the numSV and accuracy of the GPS.

NumSV (number of GPS sattelites) should be a high number and accuracy(hAcc) should be low.

Most likely the at the end of the file you got the best numbers.

(You could get a average number to make it more accurate)

Write down lat/lon (or copy to notepad) and the next time you run FlySight macro you paste the numbers.

The distance will be calculated from "Swoop end" point to landing accuracy pin.

So if the Swoop is inaccurate the landing accuracy will also be inaccurate.

Jump name/description?

Jump name is label that you can add to the jump and it will show up in Google Earth.

Default is "Jump". It can be used when you want to look at several jumps at the same time.

Lets say you made six jumps on one day and you want to compare the jumps in Google Earth.

Naming them for example "Jump 1", "Jump 2", etc. will make it much easier to see the jumps.

This is the only use for this setting, it will not change anything else.

Why do you advice AGL altitude?

Google Earth is not very accurate with the ground level.

If you use MSL setting the KML file (Google Earth file) the macro creates uses Google Earths absolute setting.

This means all altitudes are based from sea level, but because Google Earths groundlevel is inaccurate

sometimes the graphs/tracks will show you as landing below ground.

When you use AGL setting, I can use RelativToGround in the KML file.

This means I tell Google Earth "He was 25 feet above ground", and it will calculate it from

Google Earths (sometimes inaccurate) groundlevel and show you are beeing 25 feet up.

According to sources on internet (yeah right!) Google Earth has a +-30 m/ ~90 feet inaccuracy.

That's why I advice AGL setting.