# LESSON 25: Display Your GPS Data as Track on Google Earth

In this lesson we will learn how to take the data we are logging from our GPS, and display it properly on Google Earth. This lesson builds on Lesson 22Lesson 23 and Lesson 24. You will need to complete those lessons before undertaking this lesson. In this series of lessons we are using the Arduino,  Adafruit Ultimate GPS, Virtuabotix SD card reader, and a Battery Clip to power the arduino during your mobile jaunts.  You will need a 9V battery. If you are going to be doing a lot of mobile work, it is probably worth it to invest in a good 9v Rechargable battery system.

When you get your gear gathered up, you will be ready to get this project going. First, hook the GPS and Card Reader up as we did in Lesson 23. We will start with the software that we used in Lesson 23. This software correctly reads data from the GPS and then logs the data into two data files on the SD card. The problem, though, we did not really do any fine tuning of the data file we were creating.

In this lesson we want to create a data file that we can display as a track in Google Earth. In order for this to work, we have to save the data in the manner a KML file wants to see. We have to save the data as:

Decimal Longitude, Decimal latitude, Altitude

I find it works to not use a line ending, but put a single white space after the Altitude.  That is, delimit with commas as shown above, but then use one white space to delimit between successive lines of data.

Lesson 24 explained in great detail how to interpret the NMEA sentences. The challenge here is that the Arduino is very poor at parsing strings. The NMEA sentence would be easy to parse in Python, because Python is so good at easily manipulating strings. Since it is tedious to manipulate strings in Arduino, we are going to try and parse the data using numbers and math, not strings. To explain this, I will give an example for Latitude, and Longitude will work in a similar manner. The latitude data we get from the parsed data from the Adafruit GPS looks like this:

3051.8007

From lesson 24, we know that this represents 30 degrees and 51.8007 minutes. In order to parse this in Arduino using just numbers I do the following. First create three variables deg, degWhole, and degDec. The variable deg will hold the final answer, degWhole holds the whole part of the number, and degDec whole the part to the right of the decimal. Adding degWhole to degDec gives you deg, your final answer. So, lets assume x = 3051.8007, our Latitude from the GPS.

Dividing by 100 moves the decimal to the left two spots, and taking the int removes anything to the right of the decimal. Then converting back to float gives us a round number with no values to the right of the decimal. For 3051.8007 it turns it into 30.0, the whole number part of degrees. Now to get the fractional part, we need to take minutes and divide by 60. This will always be a number less than one. To get fractional part of the latitude in degrees, we do the following:

We have to multiply degWhoe by 100 to get the decimal moved back to the right by 2. Then we subtract that number from the original latitude, and we are left with minutes. Then divide by 60 and we have converted minutes to a fraction of a degree. We now have the whole part and the fractional part of the answer, so we just add those together:

We now have a nice decimal number, deg, which is the decimal representation of our Latitude. We have one more thing to deal with. If the GPS is reporting ‘N’, leave the number positive. If the GPS is reporting ‘S’ (that we are in the Southern Hemisphere),  you need to make your latitude number negative. Similarly, when you are doing your longitude, you need to make the longitude negative if you are in the Western Hemisphere.

Finally, when you write the file, Google Earth will want you to store the data as:

Longitude, Latitude,altitude

It is curious that this is reverse from what you would do if you were entering coordinates into the Google Earth search bar. That wants Latitude first.

In any event, with the parsing and formatting described above, you can create a file that is almost ready to read into Google Earth. The code below will create your coordinates in the correct format for KML, which Google Earth will read. Please watch the video for a complete description of the code.

The final thing we have to do is to put a “wrapper” around the coordinates to turn the coordinates into a .kml file Google Earth will like. I just do this manually. I open the text file on the SD card created by the code above, and then just paste it into this KML wrapper, and save the file with a .kml extension. The KML wrapper is as follows:

Just paste your coordinate data in the file above between <coordinates> and </coordinates>, save with a .kml extension, and you should be able to open it with Google Earth and see your track. Good luck!

# LESSON 24: Understanding GPS NMEA Sentences

GPS units spit out data in a dizzying array of formats. It can become a challenge to take the output from a GPS unit, like the Adafruit Ultimate GPS breakout board, and get that data to play nicely with mapping programs like Google earth. It is as if no one is speaking the same language. In this lesson we will look at what the data coming off the GPS means, and how you can work with it, and get it to display properly in programs like Google Earth.

When you connect a GPS board up, and look at the data coming off of it, you are likely to see something like this:

\$GPRMC,000009.800,V,,,,,0.00,0.00,060180,,,N*43
\$GPVTG,0.00,T,,M,0.00,N,0.00,K,N*32
\$GPGGA,000010.800,,,,,0,0,,,M,,M,,*41
\$GPGSA,A,1,,,,,,,,,,,,,,,*1E
\$GPRMC,000010.800,V,,,,,0.00,0.00,060180,,,N*4B
\$GPVTG,0.00,T,,M,0.00,N,0.00,K,N*32
\$GPGGA,000011.800,,,,,0,0,,,M,,M,,*40
\$GPGSA,A,1,,,,,,,,,,,,,,,*1E
\$GPRMC,000011.800,V,,,,,0.00,0.00,060180,,,N*4A
\$GPVTG,0.00,T,,M,0.00,N,0.00,K,N*32
\$GPGGA,000012.800,,,,,0,0,,,M,,M,,*43
\$GPGSA,A,1,,,,,,,,,,,,,,,*1E
\$GPGSV,1,1,00*79

This is what the data looks like when your GPS does not have a fix. When it does have a fix, there will be all types of numbers between the commas in the lines above. So, how do we make sense of all this? The first thing is to learn some of the lingo. Each line above is referred to as a NMEA sentence. There are different NMEA sentence type, and the type is indicated by the first characters before the comma. So, \$GPGSA is a certain type of NMEA sentence, and \$GPRMC is a different type of NMEA sentence. To make this whole thing a manageable problem, the first thing we must realize is that the data that we want will be in the \$GPRMC sentence  and the \$GPGGA sentence. If your GPS unit has options to turn the other sentences off, then turn them off to simplify the data getting thrown at you. If you can not turn the other sentences off, then just ignore them, and focus on the two you care about,  \$GPRMC, \$GPGGA.

If your GPS has a fix, then your GPS sentences should look something like this:

Lets start by breaking down the \$GPRMC sentence.

The \$GPRMC is simply telling what sentence type is on the line. The next number,  represents the Coordinated Universal Time (UTC). It works like this, 194530.000 would be 19:45 and 30.0 seconds in UTC. Since converting from UTC to your local time is simply a matter of knowing what time zone you are in, you can see that one thing you get from a GPS is a very accurate clock. The next letter just lets you know if your signal is Active (A) or Void (V).  An ‘A’ indicates you are getting a signal and things are working properly. A ‘V’ means you do not have a signal.

Now, for the good stuff, the next number and following letter gives you your lattitude.  3051.8007,N should be interpreted as follows:

Your Latitude is: 30 degrees, 51.007 minutes, in the Northern Hemisphere.

Similarly, the next number, 10035.9989,W,  is Longitude. This is interpretted as:

Your Longitude is:  100 degrees 35.9989 minutes, in the Western Hemisphere.

Degrees could be a one, two or three digit number. Hence you have to be careful parsing this data. What is always the case is that the first two numerals to the left of the decimal place, and the numbers to the right of the decimal represent the minutes. So, always take the number starting two to the left of the decimal, and those following all the way to the comma, and that is your minutes. Unfortunately, if you simply try to put 3051.8007,N,10035.9989,W, into Google Earth, it will not recognize it. The simplest thing you can do to get Google Earth to recognize and properly display the coordinate would be to enter the following:

30 51.8007N, 100 35.9989W

Notice the space inserted between degrees and minutes, and no comma before hemisphere designation. This would properly display that single point via the Google Earth search bar. The challenge however is that if you want to log data from your GPS and then show a track of where you have been, you will have to create a KML or KMZ file. These files are even more particular about the format of the coordinate data. These files want both latitude and longitude as decimal numbers, so we must convert degrees, minutes to decimal degrees. You can do this simply by realizing that there are sixty minutes in a degree. So, for the case above, 51.8007 Minutes = 51.8007/60 degrees = .86335 degrees. So, to make a KML file that Google Earth will like, 30 51.8007N should be converted to 30.86335. We still have to deal with the N and W. KML files do not know what to do with the N, S, E, W. So, you must do the conversion. On Latitude, if you have a N, leave Latitude positive, if you have a S make your Latitude negative. On Longitude, if you have an E leave your number positive. If you have a W make your Longitude negative. Following these rules:

Should become:

30.8633, -100.5999

Those numbers will not only display properly in a KML file, they will also work if directly typed into the search bar on Google Earth.

We will talk more about KML files in the next lesson, but we will state here that in the KML file, you should put Longitude first, followed by Latitude. Opposite of how you put the numbers in Google earth, which wants latitude followed by longitude.

OK, that is the hard part, now for the rest of the characters in the sentence. The next number, 1.49 in the example above is the speed in knots. I was walking, so you can see this is a small number in the above example. The next number represents track angle, not something I find useful or use.  Then after that, you see the number  310714. This is the date, which would be DD/MM/YY so this date is July 31, 2014. You can see on my NMEA sentence, I just get commas after that. Some units report magnetic variation here, but mine doesn’t. Then finally, the final characters represent a checksum, something we do not need to worry with.

So there, our first NMEA sentence parsed. You can see that you get just about everything you need in this one sentence.

So why do we need the \$GPGGA sentence you ask. Well, it has a couple of nuggets of info we need, particularly if we are doing High Altitude Ballooning/Edge of Space work. Lets look at the \$GPGGA sentence:

Again, the first number represents the time.

194530.000 would be 19:45 and 30.000 seconds, UTC

The next numbers represent Latitude and Longitude, just as in the \$GPRMC sentence above, so I will not go through that again.

Now the next number, 1 above, is the fix quality. a 1 means you have a fix and a 0 means you do not have a fix. If there is a different number it is more details on the type of fix you have. Next number is how many satellites you are tracking. For us, 4. The larger number here the better. Next up, 2.18 is the horizontal dilution of position. Something I don’t worry with. Next one is an important one . . . 746.4 is my altitude in meters above mean seal level. This is hugely important for projects like high altitude ballooning. It is a direct indication of your altitude. Next number is the altitude of mean sea level where you are. This is something you do not need to worry about in most applications but is related to a geometric approximation of the earth as an ellipsoid. Look up WGS84 Ellipsoid if you really want to understand this number.

OK, lets bring this all home now. Using the  \$GPRMC and \$GPGGA NMEA sentences, we can get our latitude and longitude coordinates, and convert them to numbers that can be recognized by Google Earth, or put into a KML file. We also have our speed in knots, and our altitude. These are all the things we would want for projects like unmanned aerial drones, or high altitude balloons.