iCapture v2

Suggestions and changes, some of which are in light of recent issues

At the moment we send DEVICEID, DATETIME, USER, X,Y (plus more) for every tracking event

Would suggest we add a new ACTION method of TRACKING This would sent the same informatino, but also multiple tracking points in one go syntax would be ACTION=TRACKING&COMPANY=Trimble&DEVICED=&DEVICENAME=etc

&TRACKING=X0,Y0,T0,X1,Y1,T1,X2,Y2,T2…..Xn,Yn,Tn

where X,Y are coords and T is timestamp

YES

Suggest we prefix all the reserved keys.

It is likely that many users will want to use Type, Class, Status as field names, so we should use something else Suggest we at least prefix an Underscore on all reserved words?

AGREE - prefix all fixed names

Drop Type as keyword

At the moment we send &X=&Y=&Z= for coordinates.

Suggest we introduce new object &Geometry=WKT

WKT follows the WellKnownText format as described here http://en.wikipedia.org/wiki/Well-known_text

Currently we would only support points

&_GEOMETRY=POINT(X Y)

but in future we might support

&_GEOMETRY=LINESTRING(X1 Y1,X2 Y2,X3 Y3)

&_GEOMETRY=POLYGON(X1 Y1,X2 Y2,X3 Y3,X1 Y1)

Just store wkt string as text field for now - maybe experiment with real geometry

Unfortunately this was probably incorrect in the beginning and has remained so ever since! Currently the Type corresponds to the ATP name, and Class and Status are just fields defined within the ATP file

Unfortunately this dictates that the ATP file MUST contain a CLASS field in order for the system to work (Currently STATUS gets added if not present)

Arguably Type should be one of Point/line/Area and Class should correspond to the ATP name ?

=Current setting=

$settings→devicedisplay→TEAM→USER $settings→eventdisplay→TYPE→CLASS→STATUS=array(icon,template,popuptemplate) $settings→eventnotifications→INCIDENT→ALERT→email

=New Setting= Setting→_ATP[]=array(trigger,icon,template,popuptemplate,msglist,emaillist) Seting→Device[]=array(trigger,icon,template,popuptemplate,msglist,emaillist)

triggers would be a string of tests to be performed, which should return True or False eg trigger = ”{status}=='warm' || {status}=='hot'”

 trigger = "{status}=='open' && {fruit}=='bananas && {count}>5"
 trigger = "{team}=='TPS' && {user}=='wynsleeman'"

ATP Editor

As the Status field is used on the display screens it is difficult to remove or change it without altering the front end

Probably the only real change required would be to rename it _status, or maybe _taskstatus

We could also then be more justified in hardwiring the _taskstatus values to something like 0-Open, 1-Closed,2-In Progress (plus any others?)

We would then leave 'status' as a non-reserved field available for users

_itemStatus