Modification to openGTS opensource platform for GPS Tracking Original source code: http://sourceforge.net/projects/opengts/ Our Current Custom installation is running at: http://track.migps.net General Requirement: Developer must deliver to us the source code of all the files that be modified from the original source code, and also the source code of the new files that result from the development of this project. Details about the required task to deelop in ! main stages: Stage ": Custom Pictures for Deices#Trackers
1.- Add a function to the sstem to incorporate ! pictures for each tracker/device " e#: picture1 for driver and picture! for car $: a$ %ictur %icturee should should be associa associated ted to corresp correspond onding ing tracker tracker using using the device device/tra /tracke ckerr administration web page " same used to view/edit the rest of the tracker/device info $ for a friendl management b authori&ed users on each account. b$ %ictures si&e and resolution should be controlled and resi&ed resi& ed automaticall " no more than '()*/picture $ if re+uired to meet the correct si&es that allow to be displaed later inside the trackers balloon infowindow c$ Devices Devices table on on database database should should includ includee the info info for the the pictures pictures d$ %ictures %ictures for the trackers trackers must be displa displaed ed on the oogle oogle map infowin infowindow, dow, on a tab enabled for that purpose " currentl our infowindow have tabs, one of them reserved for that purpose $ Stage $: Custom Markers for %ccounts& 'ith rules
1.- Add a feature to allow that authori&ed users for each account could declare %023 04 23565738 23565738 which would be like 9ustoms 9ustoms 4i#ed arkers arkers to be allocated allocated on the global map " oogle $: a$ 3he user user would would create create markers markers associat associated ed to its account account with the the intentio intention n to create/edit %oint of nterest for them. 5#: ain 0ffice, *ranch1, ;arehouse, 7tore, 9ustomer1, 9ustomer!, etc. 3his would be done using a web interface on the anagement section. b$ 5ach %oint of nterest arkers definition should have: an icon " could be selected from from a few fi#ed collection collection $, a name, a description, description, one picture, picture, one pair of coordinates " latitude and longitude to could
!.- Add a feature to allow that authori&ed users for each account could declare 9=59)%02378 which would be also like 9ustoms 4i#ed arkers to be allocated on the global map " oogle $, but associated to a rule that would send an email notification to the selected user/users on each account when selected device/tracker cross over the 9=59)%023 marker.
a$ 3he user would create 9heckpoint markers associated to its account with the intention to know when certain devices visit some forbidden places or enter a forbidden road, etc. 3his would be done using a web interface on the anagement section. b$ 5ach 9heckpoint arker definition should have: an icon " one same icon for all markers of this kind is acceptable $, a name, a description, one pair of coordinates " latitude and longitude to could
