trackpointsloadbydate

trackpointsloadpubbydate

Returns user's points or public points or friend's points between given dates. If it is used “trackloadpubbydate” command, public tracks can be read without giving username and password.

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: “trackpointsloadbydate” or “trackpointsloadpubbydate”.

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

  • txtParameter field contains a structure like this:

<?xml version="1.0" encoding="utf-8" ?> 
<trackpointsloadbydate>
	<from>20131031080000</from>
	<to>20131031150000</to>
	<consumer>10</consumer> 
	<time>20131031203040</time> 
</trackpointsloadbydate>
{
  "trackpointsloadbydate": {
    "from": "20131031080000",
    "to": "20131031150000",
    "consumer": "10",
    "time": "20131031203040"
  }
}

Note: both commands' root tag is <trackpointsloadbydate>

 

Where

  • <from> optional. The start of interval of points to search. If no value is set the backend server will return all points from the beginning.

  • <to> optional. The end of interval of points to search. If no value is set the backend server will return all points till the end.

  • <consumer> mandatory. Consumer Id by which search the tracks.

  • <interestpoints> optional. Can be:

    • 0 (zero) MyWakes does not send POIs. This is default value.
    • 1 (one) MyWakes sends POI.
  • <lasttime> optional. In format yyyyMMddhhmmss. If set the backend server will return only points with a date greater then this user value.

  • <minitem> optional. Used for paging results. If set returns points greater than this value.

  • <maxitem> optional. Used for paging results. If set returns points less than this value. Note that order to prevent your system from being flooded with oversized responses, the number of messages that will be returned on a single response is limited to 2000.

  • <simplifiedmax> optional. Only if a track is closed, and no values are set for <MaxItem> and <MinItem>, permits to have track points in simplified mode.

  • <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” + “from” + + “to” + “time” + “generated character to 32”.

Looking at the previous example, the string on which calculate the check will be:
“trackpointsloadbydate20131031080”


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

Returns a structure like the following:

<?xml version="1.0" encoding="utf-8"?>
<furesult>
	<message><![CDATA[ OK ]]></message>
	<open>0</open>
	<photos>
		<photo>http://www.mysite.com/photo/name.kmz</photo>
	</photos>
	<points>
		<point>
			<latitude>44.5927777777778</latitude>
			<longitude>11.6555555555556</longitude>
			<accuracy>20</accuracy>
			<altitude>500</altitude>
			<altitudeaccuracy>15</altitudeaccuracy>
			<heading>10</heading>
			<speed>170</speed>
			<message><![CDATA[Ciao.]]></message>
			<type>0</type>
			<time>20131031123026</time>
		</point>
		<point>
			<latitude>44.62</latitude>
			<longitude>11.70</longitude>
			<accuracy>20</accuracy>
			<altitude>500</altitude>
			<altitudeaccuracy>15</altitudeaccuracy>
			<heading>30</heading>
			<speed>270</speed>
			<message><![CDATA[Ciao.]]></message>
			<type>0</type>
			<time>20131031124000</time>
		</point>
	</points>
</furesult>
{
  "furesult": {
    "message": " OK ",
    "open": "0",
    "photos": { "photo": "http://www.mysite.com/photo/name.kmz" },
    "points": {
      "point": [
        {
          "latitude": "44.5927777777778",
          "longitude": "11.6555555555556",
          "accuracy": "20",
          "altitude": "500",
          "altitudeaccuracy": "15",
          "heading": "10",
          "speed": "170",
          "message": "Ciao.",
          "type": "0",
          "time": "20131031123026"
        },
        {
          "latitude": "44.62",
          "longitude": "11.70",
          "accuracy": "20",
          "altitude": "500",
          "altitudeaccuracy": "15",
          "heading": "30",
          "speed": "270",
          "message": "Ciao.",
          "type": "0",
          "time": "20131031124000"
        }
      ]
    }
  }
}

 

Where

  • <message> contains OK or Error description
  • <open> identify an open track and can be:
    • 0 (zero) – all tracks are closed
    • 1 (one) – an open track is present
  • <photos> this node may contain a collection of pictures' files.
    • <photo> this tag can be repeated many times as more than one KMZ file cloud be present. Each node contains the URL of a KMZ file that shows the pictures linked to the track
  • <points> this node contains the points forming the track:
    • <point> at least one point have to exists. Every single <point> node contains:
      • <latitude> the point's latitude in degree and decimal degrees. If the position is in the southern hemisphere the value will be negative so it will be preceded by a minus sign
      • <longitude> the point's longitude in degree and decimal degrees. If the position is in the western hemisphere the value will be negative so it will be preceded by a minus sign
      • <altitude> the point's altitude in feet without decimal numbers
      • <accuracy> the point's accuracy in meters without decimal numbers
      • <altitudeaccuracy> the altitude's accuracy in feet without decimal numbers
      • <heading> the direction of the vehicle in degrees from 0 to 359
      • <speed> the detected speed expressed in meters per second and tenths of a meter per second
      • <message> message sent along with the position. Maximum length is 1000 characters
      • <type> The type of the position and can be:
        • 0: standard
        • 1: SOS
        • 2: begin of activity
        • 3: end of activity
        • 4: button 1 pressed
        • 5: button 2 pressed
        • 6: button 3 pressed
        • 7: button 4 pressed
        • 8: state changed from motion to rest
        • 9: state changed from rest to motion
        • 100~218: POI's (Point of Interest) category linked to the track. The categories are visible in the following table

           

          Point types

           

      • <time> UTC date and time of the position in yyyyMMddhhmmss format

If MyWakes server returns an error, the format of this answer is described in the error section.

Terms Of Use | Privacy Statement | Company info
  • © Cedac Sistemi srl
  • Head office: Via Toscana, 3 40035 Castiglione dei Pepoli (Italy) Tel.: +39 0534-93811 Fax: +39 0534-93899
  • Branch office: Via del Lavoro, 47 40033 Casalecchio di Reno (Italy)
  • Branch office: Via Parini, 1 40033 Casalecchio di Reno (Italy)
  • Share capital Euro 26,000.00 - Company Register of Bologna / VAT no / fiscal code 01695261204