[Architecture] Geo-Dashboard - Stationery Alert Usecase

2014-10-22 Thread Damith Wickramasinghe
Hi, Following is the Architecture for Stationery alert requirement. Use case: An alert should be generated if an object stays in a specific place for some specific time User will be providing the stationery position, its radius and the time. Then an alert will be given if the object satisfies f

Re: [Architecture] Geo-Dashboard - Stationery Alert Usecase

2014-10-22 Thread Damith Wickramasinghe
Attaching the document. On Wed, Oct 22, 2014 at 6:50 PM, Damith Wickramasinghe wrote: > Hi, > > Following is the Architecture for Stationery alert requirement. > > Use case: An alert should be generated if an object stays in a specific > place for some specific time > > User will be providing th

Re: [Architecture] Geo-Dashboard - Stationery Alert Usecase

2014-10-22 Thread Sriskandarajah Suhothayan
The stationary alert need not only be defined on a stationery circle but the user should also be able to define a polygon instead. So make it as: An area where the the stationary alert is valid (here we can pass the geo-fence ), and then the time period. Suho On Wed, Oct 22, 2014 at 9:30 AM, Da

Re: [Architecture] Geo-Dashboard - Stationery Alert Usecase

2014-10-22 Thread Damith Wickramasinghe
Hi, I thought the use case as the below image shown. I will add the necessary. Thank you. Regards, Damith. On Wed, Oct 22, 2014 at 7:46 PM, Sriskandarajah Suhothayan wrote: > The stationary alert need not only be defined on a stationery circle but > the user should also be able to define a p

Re: [Architecture] Geo-Dashboard - Stationery Alert Usecase

2014-10-22 Thread Sriskandarajah Suhothayan
Yes, I believe the original use case was done for circles but i think that too restrictive. Thanks Suho On Wed, Oct 22, 2014 at 1:20 PM, Damith Wickramasinghe wrote: > Hi, > > I thought the use case as the below image shown. I will add the necessary. > Thank you. > > Regards, > Damith. > > > On

Re: [Architecture] Geo-Dashboard - Stationery Alert Usecase

2014-10-23 Thread Inosh Perera
Hi Damith, When you say, user provides his Geo stationary position, how is the Geo stationary position/entering the Geo-fence captured? Is it through some GPS enabled device? If so, when setting the radius for the geo-fence, GPS fluctuation has to be considered, in the client side. Are you handling

Re: [Architecture] Geo-Dashboard - Stationery Alert Usecase

2014-10-23 Thread Damith Wickramasinghe
Hi Inosh, Yes it is done through a GPS enabled device. We are not handling anything at Client side. As for the fluctuations, we are going to use the concept Kalman filtering which will smooth the events. Thanks, Damith. On Fri, Oct 24, 2014 at 8:43 AM, Inosh Perera wrote: > Hi Damith, > When

Re: [Architecture] Geo-Dashboard - Stationery Alert Usecase

2014-10-23 Thread Inosh Perera
Hi Damith, Yes, Using Kalman filter in the server-side will smoothen the results. Best approach is using sensor fusion on client-side. Here[1] is an example of Java Kalman filter implementation. [1] https://code.google.com/p/efficient-java-matrix-library/wiki/KalmanFilterExamples Regards, Inosh

Re: [Architecture] Geo-Dashboard - Stationery Alert Usecase

2014-10-23 Thread Damith Wickramasinghe
Hi Inosh, Thanks for the resource. Doesn't sensor fusion use Kalman filter? And why do you say its the best approach? can you please elaborate on that? Regards, Damith. On Fri, Oct 24, 2014 at 11:07 AM, Inosh Perera wrote: > Hi Damith, > Yes, Using Kalman filter in the server-side will smoothe

Re: [Architecture] Geo-Dashboard - Stationery Alert Usecase

2014-10-23 Thread Inosh Perera
Hi Damith, If you don't have access to the client-side, using Kalman filter is the best approach. For example, if you leave a GPS device stationary, the GPS reading fluctuate, though it doesn't move. Typically, this is about 20m inaccuracy. To avoid this, we look at a combination of accelerometer a

Re: [Architecture] Geo-Dashboard - Stationery Alert Usecase

2014-10-23 Thread Damith Wickramasinghe
Hi Inosh, Yes as for now we are not handling anything at client side. I will look into that Thanks. Regards, Damith. On Fri, Oct 24, 2014 at 12:00 PM, Inosh Perera wrote: > Hi Damith, > If you don't have access to the client-side, using Kalman filter is the > best approach. For example, if you

Re: [Architecture] Geo-Dashboard - Stationery Alert Usecase

2014-10-26 Thread Manoj Gunawardena
Hi Damith, Suho, Two questions came into my mind. 1. Is it possible to capture same event by two geostationary execution plans (two plans overlap), if then the duplicate events may occur in UI MAP. How to validate and remove those ? 2. User input the time of object exists -: I think this time i

Re: [Architecture] Geo-Dashboard - Stationery Alert Usecase

2014-10-26 Thread Kasun Thennakoon
On Sun, Oct 26, 2014 at 1:33 PM, Manoj Gunawardena wrote: > Hi Damith, Suho, > > Hi Manoj, > > Two questions came into my mind. > > 1. Is it possible to capture same event by two geostationary execution > plans (two plans overlap), if then the duplicate events may occur in UI > MAP. How to vali