Recording extra attributes (compass, temperature, accelerometer, battery, etc.) in GPX format

[GoogleCodeExporter]

I would like to record as much raw data as possible, in GPX format, to allow 
refinement of the GPX trace by postprocessing. The GPX format does allow custom 
extensions, so technically this is possible.

I am thinking of allowing the user to choose which of the following attributes 
to record:

• temperature
• barometric pressure (for more accurate elevation calculations)
• compass bearing
• accelerometer data (e.g., for determining the smoothness of the surface 
when the device is mounted on bicycle handlebars)
• ANT+Sport sensor data (as raw as possible, e.g., wheel rotations instead of 
wheel speed)
• battery level

An example of postprocessing would be in areas with bad GPS reception. 
Calibrate the compass deviation and the wheel diameter when riding straight in 
good reception. Then, when the GPS accuracy is bad (I hope it is being recorded 
in the <sat>, <hdop>, <vdop>, <pdop> elements), a postprocessor could generate 
a GPX file that extrapolates the position from the compass reading and the 
wheel speed.

I am a professional C/C++ programmer, and I have written some Java. But, I have 
been unable to compile the code. I am not sure if this is due to Eclipse being 
new to me, or due to a broken source tree. For example, 
com.google.android.maps.mytracks.BuildConfig is not found in 1397:0b29d29ce1c4 
tip. Is there some ‘known good’ source version that I should start with?

Original issue reported on code.google.com by msmak...@gmail.com on 25 Mar 2012 at 8:43

[GoogleCodeExporter]

I've seen these errors for "tip" too. Upgrading the ADT and the SDK fixed it.

Original comment by ezerot...@gmail.com on 26 Mar 2012 at 11:48

[GoogleCodeExporter]

Thanks for the hint, I finally compiled MyTracks. Now, for testing, all I need 
is a working ADB connection. Either the USB cable or the data pins on the 
device are broken. I have already ordered replacement cables.

Original comment by msmak...@gmail.com on 26 Mar 2012 at 9:17

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

In CSV, we are exporting all the data we are recording like compass bearing and 
battery level. For GPX, I prefer not to add a custom extension since there 
won't be any program that can read it.

Original comment by jshih@google.com on 10 Sep 2012 at 11:43

[GoogleCodeExporter]

Original comment by jshih@google.com on 11 Sep 2012 at 12:53

• Changed title: Recording extra attributes (compass, temperature, accelerometer, battery, etc.) in GPX format

[GoogleCodeExporter]

I checked with the author of MyTourbook, and you seem to be right that there is 
no commonly agreed schema for recording extra attributes in GPX. Basically, the 
extension tag may contain anything.

I have been a bit busy with work. I am now learning Android basics. My current 
plan is to extend OsmAnd with an interface that allows external apps to log 
extra data, which would be written into the OsmAnd GPX file. The idea is that 
whoever writes or uses such plugins would write or use some postprocessing 
scripts too.

Original comment by msmak...@gmail.com on 11 Sep 2012 at 9:24

[GoogleCodeExporter]

Thanks for the response. Going to close this for now.

Original comment by jshih@google.com on 11 Sep 2012 at 6:02

• Changed state: WontFix