Hello @Nikhil_VJ! Looks like just the thing I was looking for, but the strings I get from geotrace using ODK collect are different to your example from Ona, and end up producing some massive triangles around the globe when I run them through the converter.
Example string (2 points from a geotrace):
10.719660522754717 124.79800276052386 75.0725241471082 10.0;10.719660522754717 124.79800276052386 75.0725241471082 10.0;
As far as I can tell the 75.07.... is altitude, and the 10.0 is accuracy. Once it runs through the converter script, I think the 75.07... ends up being considered alternately as a lat or long - which then shifts the actual lat and long to also alternate between lat and long, hence the massive triangles. Would it be possible to edit the code to make it able to process stings like this?
On a side note - the above geopoints provide decimal places pinpointing a fraction of a micrometer of the earth's surface - give or take the 10m GPS reported accuracy! There really is no need for more than 5 decimal places on the lat/long (and I would happily ignore the GPS altitude entirely). Do you know if it is possible to constrain the number of decimals stored by geotrace?