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 <[email protected]> wrote: > 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 and > Gyroscope reading in combination with GPS data to determine it the device > is stationary, this is called sensor fusion. This will get rid of all the > outliers, before sending data to the server. > > Regards, > Inosh > > On Fri, Oct 24, 2014 at 11:31 AM, Damith Wickramasinghe <[email protected]> > wrote: > >> 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 <[email protected]> wrote: >> >>> 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 >>> >>> On Fri, Oct 24, 2014 at 10:52 AM, Damith Wickramasinghe < >>> [email protected]> wrote: >>> >>>> 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 <[email protected]> wrote: >>>> >>>>> 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 the >>>>> client side part as well? >>>>> >>>>> Regards, >>>>> Inosh >>>>> >>>>> On Wed, Oct 22, 2014 at 11:11 PM, Sriskandarajah Suhothayan < >>>>> [email protected]> wrote: >>>>> >>>>>> 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 < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> 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 < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> 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, Damith Wickramasinghe < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Attaching the document. >>>>>>>>> >>>>>>>>> On Wed, Oct 22, 2014 at 6:50 PM, Damith Wickramasinghe < >>>>>>>>> [email protected]> 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 the stationery position, its radius and >>>>>>>>>> the time. Then an alert will be given if the object satisfies >>>>>>>>>> following >>>>>>>>>> two conditions. >>>>>>>>>> >>>>>>>>>> 1.Object should come into the stationery circle, which is created >>>>>>>>>> using the radius user provided. >>>>>>>>>> 2.Object should be in the circle for a specific time which user >>>>>>>>>> provided. >>>>>>>>>> >>>>>>>>>> Please find below the link for the Architecture. >>>>>>>>>> >>>>>>>>>> [1] Architecture >>>>>>>>>> <https://docs.google.com/a/wso2.com/drawings/d/1X1LE8qjbXCvLmqHVrFoAFkTBdNHxDCiUrQd_FwfEDMA/edit?usp=sharing> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Best Regards, >>>>>>>>>> Damith Wickramasinghe. >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Software Engineer >>>>>>>>>> WSO2 Inc.; http://wso2.com >>>>>>>>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> >>>>>>>>>> lean.enterprise.middleware >>>>>>>>>> >>>>>>>>>> mobile: *+94728671315 <%2B94728671315>* >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Software Engineer >>>>>>>>> WSO2 Inc.; http://wso2.com >>>>>>>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> >>>>>>>>> lean.enterprise.middleware >>>>>>>>> >>>>>>>>> mobile: *+94728671315 <%2B94728671315>* >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> *S. Suhothayan* >>>>>>>> Technical Lead & Team Lead of WSO2 Complex Event Processor >>>>>>>> *WSO2 Inc. *http://wso2.com >>>>>>>> * <http://wso2.com/>* >>>>>>>> lean . enterprise . middleware >>>>>>>> >>>>>>>> >>>>>>>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >>>>>>>> http://suhothayan.blogspot.com/ >>>>>>>> <http://suhothayan.blogspot.com/>twitter: >>>>>>>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | >>>>>>>> linked-in: >>>>>>>> http://lk.linkedin.com/in/suhothayan >>>>>>>> <http://lk.linkedin.com/in/suhothayan>* >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Software Engineer >>>>>>> WSO2 Inc.; http://wso2.com >>>>>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> >>>>>>> lean.enterprise.middleware >>>>>>> >>>>>>> mobile: *+94728671315 <%2B94728671315>* >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> *S. Suhothayan* >>>>>> Technical Lead & Team Lead of WSO2 Complex Event Processor >>>>>> *WSO2 Inc. *http://wso2.com >>>>>> * <http://wso2.com/>* >>>>>> lean . enterprise . middleware >>>>>> >>>>>> >>>>>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >>>>>> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: >>>>>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | >>>>>> linked-in: >>>>>> http://lk.linkedin.com/in/suhothayan >>>>>> <http://lk.linkedin.com/in/suhothayan>* >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> [email protected] >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Inosh Perera >>>>> Software Engineer, WSO2 Inc. >>>>> Tel: 0785293686 >>>>> >>>> >>>> >>>> >>>> -- >>>> Software Engineer >>>> WSO2 Inc.; http://wso2.com >>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> >>>> lean.enterprise.middleware >>>> >>>> mobile: *+94728671315 <%2B94728671315>* >>>> >>>> >>> >>> >>> -- >>> Inosh Perera >>> Software Engineer, WSO2 Inc. >>> Tel: 0785293686 >>> >> >> >> >> -- >> Software Engineer >> WSO2 Inc.; http://wso2.com >> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> >> lean.enterprise.middleware >> >> mobile: *+94728671315 <%2B94728671315>* >> >> > > > -- > Inosh Perera > Software Engineer, WSO2 Inc. > Tel: 0785293686 > -- Software Engineer WSO2 Inc.; http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> lean.enterprise.middleware mobile: *+94728671315*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
