position

Sets a point for the specified user in the radar.

Command's fields description:

• txtUser1 field is the “username” of MyWakes account.

• txtUser2 field is the “password” of MyWakes account.

• txtCommand field contains the command: “position”.

• txtFormat optional field specifies txtParameters and response formats. more info.

• txtParameter field contains a structure like this:

<?xml version="1.0" encoding="utf-8" ?>
<position>
	<latitude>44.5</latitude>
	<longitude>11</longitude>
	<altitude>2500</altitude>
	<accuracy>10</accuracy>
	<altitudeaccuracy>20</altitudeaccuracy>
	<heading>50</heading>
	<speed>55.55</speed>
	<message><![CDATA[Ciao.]]></message>
	<time>20101025183000</time>
</position>

{
  "position": {
    "latitude": "44.5",
    "longitude": "11",
    "altitude": "2500",
    "accuracy": "10",
    "altitudeaccuracy": "20",
    "heading": "50",
    "speed": "55.55",
    "message": "Ciao.",
    "time": "20101025183000"
  }
}

Where

• <consumer> optional. Id of the Consumer which refers to the position. If it is not specified the position will be set for the “non defined” consumer.

• <imei> optional. If present, <consumer> tag is unnecessary. If neither tag is not specified the position will set for the “non defined” consumer.

• <latitude> mandatory. It is the point's latitude, expressed in degrees and decimal degree. The decimal separator must be the “.” (dot). In the case of Southern Hemisphere the value will be negative and then preceded by a minus sign.

• <longitude> mandatory. It is the point's longitude, expressed in degrees and decimal degree. The decimal separator must be the “.” (dot). In the case of Western Hemisphere the value will be negative and then preceded by a minus sign.

• <altitude> optional. It is the altitude expressed in feet without decimals.

• <accuracy> optional. It is the point's accuracy expressed in meters without decimals.

• <altitudeaccuracy> optional. It is the altitude accuracy expressed in feet without decimals.

• <heading> optional. Consumer's direction expressed in degree from 0 to 359 without decimals.

• <speed> optional. It is expressed in meters per second and fractions of a meter per second. The decimal separator must be the “.” (dot).

• <odometer> optional. Odometer value of the consumer at this point expressed in Km. The decimal separator must be the “.” (dot).

• <hoursmeter> optional. Hoursmeter value of the consumer at this point expressed in hours. The decimal separator must be the “.” (dot).

• <message> optional. A text message to associate to the point with maximum length of 1000 characters.

• <time> mandatory, date and time in UTC. The accepted format is “yyyyMMddhhmmss”.

• txtProvider field must contain the application calling ID and generated characters.

• txtSignature field must contain the signature based on the string made of “Command Name” + “time” + “latitude” + “longitude” + “generated character to 32”. If this string (with latitude and longitude) exceeds 32 characters it will be cut to 32 characters.

Looking at the previous example, the string on which calculate the check will be:
“position2010102518300044.511xxxx”

Therefore the txtProvider field will be:
“76a865d4-fab8-51cd-ba78-2da325f6955axxxx”

Returns a structure like the following:

<?xml version="1.0" encoding="utf-8"?>
<furesult>
	<message><![CDATA[ OK ]]></message>
</furesult>

{
  "furesult": {
    "message": " OK "
  }
}