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 de elop in ! main stages: Stage ": Custom Pictures for De ices#Trackers 1.- Add a function to the s stem to incorporate ! pictures for each tracker/device " e#: picture1 for driver and picture! for car $: a$ %icture should be associated to corresponding tracker using the device/tracker 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 automaticall " no more than '()*/picture $ if re+uired to meet the correct si&es that allow to be displa ed later inside the trackers, balloon infowindow c$ Devices table on database should include the info for the pictures d$ %ictures for the trackers must be displa ed on the -oogle map infowindow, 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 /%0123 04 123565738 which would be like 9ustoms 4i#ed :arkers to be allocated on the global map " -oogle $: a$ 3he user would create markers associated to its account with the intention to create/edit %oint of 1nterest 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 1nterest :arkers definition should have: an icon " could be selected from a few fi#ed collection $, a name, a description, one picture, one pair of coordinates " latitude and longitude to could <map it, $ c$ 2ew table"s$ is preferred to store the %oint 0f 1nterest markers d$ 9ustom 4i#ed :arkers should be alwa s visible for all users of the corresponding accounts on both maps view " Device map and -roup map $ due to the would be an important reference for the users. e$ 1nformation for each marker " name, description, picture, latitude and longitude should be displa ed on the marker infowindow $

!.- Add a feature to allow that authori&ed users for each account could declare /9=59)%012378 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)%0123 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 <map it, $ c$ 2ew table"s$ is preferred to store the 9heckpoint markers d$ 3his :arkers should be alwa s visible onl for specified user/users on each account, and displa ed on both map views " Device map and -roup map $. e$ 1nformation for each marker " name, description, latitude and longitude should be displa ed on the marker infowindow $ f$ 0ne e-mail to specified user should be send if an device cross over a 9heckpoint. 5mail must contain the 9heckpoint information, Device information, and event information " date and time of the event at the moment that device crossed the checkpoint $ ..- 5nable the e-mail feature on our >inu# server and on the open-37 platform to allow e-mails indicated on point ! could be sent b the server. Stage (: )mpro e Custom Ser er for Meitrack trackers ;e have alread developed a basic version of 9ustom 7erver for meitrack -%7 trackers " www.meitrack.com $ , server is functional for location purpose " can handle latitude, longitude, speed, time of event, and direction $, but need to be finished to integrate the possibilit to read parameters reported from the tracker and sending user commands to trackers from the server platform. 0ur current version of the :eitrack traker for 0pen-37 " source code $ will be supplied to the developer as well as the -%67 commands and communication protocol to facilitate the work to do on this stage. 1.- 1ntegrate the function into meitrack custom server on open-37 to read the trackers status " batter level, digital input status, engine start/stop, alarm event, analog inputs level, etc $ , store it on the database and displa it on the trackers infowindow tab no.! that is reserved for that purpose. !.- 1ntegrate the function into meitrack custom server on open-37 to send user commands to trackers according to -%67 commands list available for that trackers. Stage !: Customi*e Reports 1.- 5nable and Displa onl the e#isting reports that would be used !.- Develop three " . $ new reports and include them on the report menu.