GetTrackAndPointsByDatePublicToXml

Returns public points between given dates responding to TracksAndPointsByDateParameters criteria in Xml format

public XmlDocument GetTrackAndPointsByDatePublicToXml(bool <byHttps>, TracksAndPointsByDateParameters <pointsByDateParameters>, 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
TracksAndPointsByDateParameters <tracksAndPointsByDateParameters> A TracksAndPointsByDateParameters 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

TracksAndPointsByDateParameters

UInt32 <Consumer> Consumer Id by which search the tracks
DateTime? <DateTimeFrom> The start of interval of points to search. If no value is set the backend server will return all points from the beginning.
DateTime? <DateTimeTo> The end of interval of points to search. If no value is set the backend server will return all points till the end.
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.
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.
DateTime? <NextLastTime> If set the backend server will return only points with a date greater then this user 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.

Returned Type: XmlDocument

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

<?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>

 

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
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