Improved Lat/Long precision and accuracy

I patched the base code to use longs rather than floats for lat/long, and to put them in the correct format (lat/long are in units of 1/10,000,000 of a degree with the minutes converted to 1/100,000 of a degree). Using a common integer format is more accurate, and using longs instead of floats is both faster and more precise. I'm uploading some geo-fencing code to GitHub that uses this version of the library and is much faster and extremely precise with WAAS enabled (within 3m). 

For example, the library would return a lat/long of approximately 407,098,514N / 740,079,168W for AdaFruit HQ.