...
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
...
Track Filter Command Example
| Code Block | ||
|---|---|---|
| ||
<!--MsgId is the unique id of the message being sent --> <!--UserId is the numeric user id of the entity which requires to be updated --> <!--This command will enable the area with UserId 1 --> <?xml version="1.0" encoding="utf-8"?> <TrackFilterCommand xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" MsgId="0" MsgTimeStamp="0001-01-01T00:00:00" UniqueId="fb55785b-d087-4cbf-bcd5-8bff047ebdac" Latitude1="51.591427" Longitude1="-1.384499" Latitude2="51.59081" Longitude2="-1.381755" xmlns="ICDNAV001-TrackFilterCommand"> <Sender SenderId="SenderId1" NetworkAddress="127.0.0.1" NetworkPort="10000" /> </TrackFilterCommand > |
...
Track Filter Command Attributes
Attributes | Description | Type | Notes |
MsgId | Unique message Id | Long | This must be globally unique across all message types |
MsgTimeStamp | Date and time that the message was sent | DateTime | |
UniqueId | Id of this area | Guid | This should be a unique Id that represents an area to allow tracks from |
Latitude1 | Top Left Latitude | Double | Top left latitude of tracker filter area |
Longitude1 | Top Left Longitude | Double | Top left latitude of tracker filter area |
Latitude2 | Bottom Right Latitude | Double | Bottom right latitude of tracker filter area |
Longitude2 | Bottom Right Longitude | Double | Bottom right latitude of tracker filter area |
Network Sender Element
Each incoming message can include an optional Sender element. This must include the IP address and port that the client is using to send instructions.
...