Encoding Decoding of Geo Location for IOT network for sharing compacted-point-locations in M2M Transections.

Storing Latitude & Longitude in database occupy 32 bits each means total 64 bits. but while transmitting coordinates over http with content-type text/plain or text/html, all digits, signs, floating points & seprater are treated as text-charecter, which occupy 8 bits per charecter means with current 6-decimal-precision it moccupies 22 charecters max, equivalent to 176 bits. Hence, Here tried to compress Geo coordinate from base-10 to base36/62.

1. max 12 charectets compression from 22 charecters hence 96 bits occupied.
2. It is case sensitive, hence suitable to M2M (machine-to-machine) transections.

1. max 13 charectets compression from 22 charecters hence 104 bits occupied.
2. It is case in-sensitive, hence suitable to H2M (Humant-to-machine) / M2H / H2H transection.

Maximum 22 characters are required to store location (currently precision is upto 6 decimals for general public mpas)

Seprator index denotes where is seprator situated after removal of Floating point & Signs. It means its value = No of Latitude Digits - 1

for example,

Sign defines that from which octant, the cordinate belongs to. its index value ranges from 0 to 3.

Floating Points may be in Latitude & Longitude both.

1. Defigning Sign-Index for given coordinates & then removing signs.
2. Defining Decimal-Index for coordinates received thru step-1 & then removing floating points.
3. Defining Seprator-Index for coordinates received thru step-2 & then removing seprator.
4. Encoding big number received thru step-3 for Base-36/62.
5. Concatanating Sign-Index & Deciimal-Index, then encoding them to Base-36/62.
6. Concatanating followings in sequence :
   • Encoded number received thru step-4
   • Sperator index received thru step-3
   • Encoded Charecter received thru step-5

1. Currently, Seprator-Index is not encoded because its max value is considered 7, but if decimals digits in Lat increases, it can be encoded
2. Encoding-Decoding functions are developed for client side in Javascript. which can be made for server side languages as well as device side platforms (like android)

For handling bignumbers in javascript, I gone thru various libraries & their performance test result. Finally came accors @MikeMcl's bignumber.js library which I found best according to performance & usability.