Latest Contributions by MorakotPilouk

A number of people asked me whether it is possible to use GeoEvent to do proximity alerts or collision avoidance. For example testing whether two airplanes or ships are within a certain distance between each other current positions. The bad news is there is no Proximity operator in the current GeoEvent 10.3 to help you. The good news you can compose a solution that works even if there are thousands of tracks (of moving objects). GeoEvent 10.3 added a number of key elements that allow composing a solution to perform this kind of operation. First is a fast in-memory spatial indexing which is a Quadtree-based to help finding an object in space very quickly. Second is Stream Service which is a WebSocket-based that allows push-based real-time streaming output. Third is the GeoFence Synchronization with Stream Service. And the fourth one is the Buffer Creator Processor. Other components are also needed. First the input data should be output to a Stream Service as is (i.e. point geometry) to make it available for GeoFence Synchronization then a Synchronize GeoFences needs to be created by connecting to the Stream Service URL outputting from the first step. Once this is done, proximity test processing logic can be set up by first using the Buffer Creator to create a circular geometry for each point. Use GeoTagger to tag the incoming event (the results from the Buffer Creator) with the name of the GeoFence using a Spatial Operator, e.g. "Contains Any". This is pretty much a point-in-polygon test. Please note that there can be more than one GeoFence contained in the resulting field value due to the fact that a buffer polygon can contain more than one point -- which is what we want anyway. If the resulting GeoTag field is not null then trigger the proximity alert by using a filter. The buffers that were GeoTagged can be output to a feature or stream service for displaying on a WebMap in real-time. I tested this with the flight tracking data and obtained results display in a WebMap as shown below: ... View more

The March 16, 2015 Sierra Wireless Connector update is more stable and optimized. All the different RAP message types (RAP0x11, 0x12, 0x13, 0x14) are now consolidated into one and have become a field in the RAP GeoEvent definition. Several more fields and event types (e.g. Stationary (0x2C -- Stationary and 0x2D -- Started moving), Maximum Speed (0x2E -- Maximum Speed Exceeded and 0x2F -- Vehicle went back below max speed)) also added including the RAP device source IP. Odometer value parsing was also corrected. This update also supports the "Store and Forward" behavior if it is enabled on the RAP device. Store and Forward causes GPS reports to be queued up if the RAP device goes out of cellular coverage. Once the RAP device is back in cellular coverage, the GPS reports are sent to the GeoEvent Sierra Wireless input thus preventing the gap in the vehicle tracking data. ... View more

The Verizon Networkfleet connector for GeoEvent 10.3 has been updated 3/25/2015. This update added more fields to the Diagnostic message. The following fields were added: "EventTime" "EventTimeUTF" "Odometer" "EngineHours" "TotalGallons" "BufferType" Here's the download location: http://www.arcgis.com/home/item.html?id=720c28f0ef72426792012d10c37a251a ... View more

Temporal aspect can be added to a filter by using string templates. Steps: - Create a Filter - Set up condition(s) comparing the $RECEIVED_TIME with values based on temporal templates - Time period can be created by AND condition - Multiple time periods can be created by AND and OR operator - Exception can be done using NOT operator For example the expression below shows to time periods that allow the asdi-FAA data to get through: OR (Any of these are true)      AND (All of these are true)            $RECEIVED_TIME >= 15h 37m            $RECEIVED_TIME < 15h 38m      AND (All of these are true)           $RECEIVED_TIME >= 15h 40m           $RECEIVED_TIME < 15h 41m Here's a sample list of temporal template: - 2013y -- year = 2013 - 2013y 1M -- 2013/Jan - 2013y 2M -- 2013/Feb - 2013y 2M 25d -- 2013/Feb/25 - 2012y,2013y -- list of years for using with the IN operator - 2013y 2M,2013y 1M,2013y 10M,2011y 2M -- list of year and months for using with the IN operator - 2013y 2M 25d,2013y 2M 24d,2D -- list of year/month/date and year/month/day of week for using with the IN operator - 11h -- 11 o'clock - 12h -- 12 o'clock - 12h 9m -- 12:09 - 12h 10m -- 12:10 - 12h 10m 10s -- 12:10:10 - 11h,12h,10h -- list of hours for using with the IN operator - 12h 10m, 21h 5m -- list of hour/minute for using with the IN operator - 12h 10m 11s,12h 11m 12s -- list of hour/minute/second for using with the IN operator - 2D,4D -- list of days of week for using with the IN operator - 2013y 2M 25d,12h 10m 10s,2D -- list of year/month/date, hour/minute/second, day of week for using with the IN operator Note: One can use the Field Calculator to add the current time to a new field by entering currentTime() into the expression input box. ... View more