The address to post the data to is www.psgpages.com/trackdata/poster.php The function will return an error message if anything suspicious occurs, and OK for a succesful POST.
The following parameters from the POST string will be processed:-
One of
The database consists of 3 tables
| Field | Type | Comment |
|---|---|---|
| UID | Integer | Primary Key |
| COMPANY | String | |
| PASSWORD | String | |
| DEVICE | String | |
| ICON | String | Icon to be used when populating map (not used yet) |
| EVENTTABLE | String | Table used for storing Device Events (not used yet) |
| X | Float | |
| Y | Float | |
| TIME | TIMESTAMP | Server time if not passed as parameter |
| Field | Type | Comment |
|---|---|---|
| UID | Integer | Primary Key |
| DEVICES_UID | Integer | Defines Parent relationship to DEVICES table |
| X | Float | |
| Y | Float | |
| USER | String | |
| Z | Float | |
| TIME | TIMESTAMP | Server time if not passed as parameter |
| TYPE | String |
| Field | Type | Comment |
|---|---|---|
| UID | Integer | Primary Key |
| EVENT_UID | Integer | Defines Parent relationship to EVENTS table |
| NAME | String | Data field nmame |
| VALUE | String | Data field value |
(probably use TRACKING / INCIDENT as different event types - i think there is some confusion on what dean was doing - the incidents table was completly unrelated to the tracking stuff, they where just two data sources displayed on the same map. - but if having them linked makes it easier, iam not to bothered (would it be better if if EVENTTYPE was in the tracking DB))
What did work quite nicley is that only todays incidents where listed.
It would probably work nicley, if a INCIDENT update came in then, that is the aALARM trigger
i still dont reaqlly get what you are doing here, ive just sent a link that updated a JOBname & JOBcnt additional fields - yet i dont see them in the tracking view