GetTrackAndPointsToXml

Returns the track responding to TracksAndPointsParameters criteria in Xml format

public XmlDocument GetTrackAndPointsToXml(bool <byHttps>, string <userName>, string <password>, TracksAndPointsParameters <tracksAndPointsParameters>, ref char <messageType>, ref string <message>)

Parameters:

bool <byHttps> Set to true if you want to user https protocol otherwise, if you want to use http, set it to false
string <userName> A string containing the username assigned from MyWakes
string <password> A string containing the password for the MyWakes user
TracksAndPointsParameters <tracksAndPointsParameters> A TracksAndPointsParameters object containing command's specific parameters
ref char <messageType> A string containing output parameter that will return the type of message returned in <message> field: I=information, W=warning, E=error
ref string <message> A string containing output parameter with the message content

TracksAndPointsParameters

bool <InterestPoints> If set to true the backend server will send POI (Points Of Interest) along with track data. If set to false no POI is sent.
DateTime? <LastTime> If set the backend server will return only points with a date greater then this user value.
UInt32? <MaxItem> 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.
UInt32? <MinItem> Used for paging results. If set returns points greater than this value.
UInt32? <SimplifiedMax> Only if a track is closed, and no values are set for <MaxItem> and <MinItem>, permits to have track points in simplified mode.
UInt32 <TrackId> Id of the track to load.

Returned Type: XmlDocument

Returns an XML Document according to trackload command with the following structure:

<?xml version="1.0" encoding="utf-8"?>
<furesult>
	<message><![CDATA[ OK ]]></message>
	<track>
		<description><![CDATA[titolo della traccia]]></description>
		<color1>00ffff</color1>
		<color2>00ff00</color2>
		<public>1</public>
		<updateposition>1</updateposition> 
		<autoclosed>0</autoclosed>
		<photo>http://www.mysite.com/photo/name.kmz</photo>
		<starttime>20101112173025</starttime> 
		<endtime>20101112174015</endtime>
		<length>50.18</length>
		<minaltitude>1000</minaltitude>
		<maxaltitude>2000</maxaltitude>
		<totpoints>2</totpoints>
		<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>20101112173026</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>20101112174000</time>
			</point>
		</points>
	</track>
</furesult>

 

Where

  • <message> contains OK or Error description
  • <track> if the command has succeeded and <message> is OK this tag exists and contains the track with the following tags:
    • <description> description of the track
    • <color1> the line's color in rrggbb format.
    • <color2> the transparency altitude's color in rrggbb format
    • <public> can be:
      • 0 (zero) – if track is private and still visible only to the track owner.
      • 1 (one) – if the track will be published to a page that has to be shown to friends
      • 2 (two) – if the track can be published in a common page where all public tracks are visible to everybody
    • <updateposition> can be:
      • 0 (zero) – if trackpoint command did not update current user's position
      • 1 (one) – if trackpoint command update current user's position
    • <photo> the URL of KMZ file that shows all the pictures that are linked to the track
    • <starttime> the start UTC date and time of recording in yyyyMMddhhmmss format
    • <endtime> the end UTC date and time of recording in yyyyMMddhhmmss format (only if track is closed)
    • <length> track length in Km (only if track is closed)
    • <minaltitude> minimum altitude of the track in Feet (only if track is closed)
    • <maxaltitude> maximum altitude of the track in Feet (only if track is closed)
    • <totpoints> total number of points of the track. Also when paging this field contains the total number of points but is present only if the track is closed
    • <realtime> the device real time mode:
      • 0 (zero) – the device is not in real time mode
      • 1 (one) – the device is in real time mode
    • <autoclosed> can be:
      • null – the track is open
      • 0 (zero) – the track has been closed correctly by the user
      • 1 (one) – the track has been closed by the server
    • <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
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