I'm currently looking into the potential of Btraced for a number of applications, and I'm working on a backend web service which can handle and process Btraced app data. I now have a few questions about the data types being used:
1) Point id's: what is the data type for this (precision or range), and how does the app cope with it while it seems ever increasing? Does it go 'round robin' after it goes out of range? I'm able to generate a lot of points if I set the updating of points to the highest resolution. Not really a problem if you use an unsigned 64-bit integer, but it ís a problem when you use a signed 16-bit integer (max is 32767!)

2) GetTripUrl: always seems to be set at '1' it seems, thus resulting our server responding with a full URL after each request, while sending it once should be enough (and saves bandwidth)

3) Altitude: From documentation: "Can be -1.0 if vertical accuracy cannot be determinated". Problem is that an elevation of -1.0 (or lower) is actual a valid value in meters. Living below sea level you will see these figures all the time

Thank you in advance for some answers and regards,
Erik