GPS isn't accurate enough on altitude. Plus with rise and fall of the ground you would never get correct height even if GPS was accurate. 

DKWatson, what do you mean by map(value, fromLow, fromHigh, toLow, toHigh)? can you clarify about it further? which coding do you mean by this?

Code: [Select]

ADIS16460 imu(10, 2, 9); // Arguments: Chip Select, Data Ready, Reset Pin Assignments.

Do you have ALL the needed pins connected?   Are you using  a particular shield?
You need the SPI pins (MISO, MOSI, SCK) connected via the ICSP connector on the Zero, PLUS pins 10 (SS), 2, and 9.   2 and 9 are additional signals outside of the normal SPI spec.
The web page talks about connecting to a Teensy, and shows a teensy adapter motherboard and weird cable...

It used to be more useful back before list comprehensions.
You've probably seen code like

[int(x[2]) for x in l]

Back before list comprehensions, you'd write that as

map(lambda x: int(x[2]), l)

(This was also back before map returned an iterator.)

These days, list comprehensions and generator expressions handle most of what map used to do. map is still cleaner sometimes, particularly when you don't need a lambda. apkjunky
For example, some people prefer

map(str, l)

over

(str(x) for x in l)

Thanks for the mention of the thermocouple. That was my original idea and I'm not sure why I headed away from it. I agree it would be a better source and more consistent.