*Input Stream:* GPX XML NMEA Simple Lat,lon *Processing* Use Geotools functions such as WITHIN, OVERLAY etc. These will be available as geo: constructs in CEP.
*Configuration* The projection and CRS for both input streams and input geometries need to be specified, and need to be matching formats for pattern matching. These can be input in the query itself or as a conf value. *Input UI* Generic helper UI consisting of a set of maps, which provides functions such as - Create a polygon for geo-fencing - Create list of points and buffers for point-based alarms *Storage* - The above will be converted to a standard format (e.g: GeoJSON) and put to storage or will create queries in CEP directly. - Since GeoJSON is the accepted input, users can directly input GeoJSON as well which would be the case in most professional deployments. *Output UI/User UI* Generic UI, mostly included as a sample which includes - Fleet management view - moving pointers, built using HTML5, Openlayers and web-sockets *Example functions based on above* - Geo-fencing - No fly zone - Detect whether an points in the stream fall within a no-fly-zone - Geo-fencing - Check whether tagged elephants are leaving the protected area - Point based alarms - Plot all bus halts on the map, and assign a 100m buffer to them. Alert if a certain bus is at a certain bus halt for more than its allocated time - Movement based alarms - Alert if 2 busses are moving in parallel (like our busses racing each other on Galle Road!) Mifan -- *Mifan Careem* Director - Solution Architecture, WSO2 Inc. Member, Sahana Software Foundation Consultant Spatial Architect M: +94 773 437 283 LinkedIn: http://lk.linkedin.com/in/mifan Skype: mifan_skype
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
