Latest Contributions by RJSunderman

If you are using the Push JSON to an external website outbound connector, yes, the connector's adapter will create a JSON representation of the GeoEvent it receives. At the 10.3.x and 10.4.x releases, the Push JSON to an external website outbound connector does not support the inclusion of query parameters in the URL. Beginning with the 10.5 release you can include query parameters in the outbound connector's URL. Variable substitution will provide value(s) for the query parameters based on the event record received by the outbound connector. Please refer to the following blog: Enhancements to the GeoEvent Server's outbound HTTP transport - RJ ... View more

Hello Morgan - I'm not sure I understand when you say "and put it into another service before i send it to the output" ... You should be able to include as many processors -- Field Reducer, Field Calculator, Field Enricher, etc. -- in-line to manage an event's fields, calculate new (or update existing) fields, and enrich events with data prior to sending then to an Output. There's only one GeoEvent Service in play; you shouldn't need another service to do what you are trying to do. Keep in mind that an Input receives event data as a byte-stream and is responsible for constructing a GeoEvent. The GeoEvent is the object being processed by the GeoEvent Service. If, for example, you do not want a recipient to see certain fields in the JSON they receive, you need to use either a Field Reducer to remove those fields from the GeoEvent or a Field Mapper to map the GeoEvent to a target output schema. The GeoEvent Service is not going to "manipulate the JSON or format of data". The Output will receive a processed GeoEvent and deconstructing it to build a JSON representation before sending the event data as JSON to the external website. - RJ ... View more

Thank you for the clarification.  If you are sending the data as MobileDeviceId,latitude,longitude then I would recommend creating a GeoEvent Definition with those fields in that order. Keeping in mind that every GeoEvent being processed must have a GeoEvent Definition which matches the event's schema. Comma-separated text being received via a UDP/Text Input must still have an Event Definition which specifies the event field names, data types, and field order. You will want to configure your Input to create a Geometry from the received latitude and longitude fields, and include a field of type Geometry in the GeoEvent Definition so that the Input has somewhere to put the Geometry it creates. - RJ ... View more

Hello - I'd like to confirm that you are using the revision of the Intro tutorial marked 'GEP 10.2 / Rev A' (cover page) released August 2013. You'll find these indicators at the bottom of each page of the tutorial. Are you using the initial product release (10.2.0) or the update (10.2.1)? Navigate to the Manager's version" rel="nofollow" target="_blank">https://localhost:6143/geoevent/manager/version.txt]version page to confirm this. The message indicating 'Configuration imported successfully' will only be displayed in your web browser's window for a few seconds before it disappears. If you missed the message, it may appear as if nothing happened. When navigating to the  Manager's [URL=https://localhost:6143/geoevent/manager/index.html]Monitor[/URL] page, do you see the SimpleGeoEventService, tcp-text-in, tcp-text-out, and file-out GeoEvent Service, Input, and Outputs listed? There is no harm in repeating steps 2, 3, and 4 on page 39 to attempt to re-import the WorkingWithFeatures_Config.xml product configuration file. If you repeat these steps and do not see the indicated message and service components, please reply confirming which product release you are using and the version and browser you are using to access Manger. - RJ ... View more

Hello - I would like to know if there is a format or specic standard for sending coordinates of a mobile arcgis geoevent processor It might be helpful to back up for a moment and remember that GeoEvent Services are designed with four basic components:  Input(s), Output(s), Filter(s), and Processor(s). Inputs are inbound connectors and Outputs are outbound connectors. Behind every connector is an adapter and a transport. A transport is responsible for receiving (or sending) event data in to (or out from) a GeoEvent Service. Out of the box, GeoEvent Processor has transports for system files, Esri feature services, as well as the HTTP, TCP, UDP, and WebSocket protocols. On the inbound side, an adapter is is responsible for adapting or interpreting the event data received. Out of the box, GeoEvent Processor has adapters which support comma separated text, generic JSON, Esri feature JSON, and GeoRSS. Additional adapters intended to highlight product extensibility are available on the Esri" rel="nofollow" target="_blank">http://links.esri.com/geoevent-gallery]Esri Gallery, Partner" rel="nofollow" target="_blank">http://links.esri.com/geoevent-partner-gallery]Partner Gallery, and Community" rel="nofollow" target="_blank">http://links.esri.com/geoevent-community-gallery]Community Gallery. Since you are developing the mobile application intended to provide the data stream, and have identified the UDP protocol as your preferred transport, I would recommend formatting the data as comma separated text and leveraging the 'Receive text from a UDP Socket' Input connector available out-of-the-box. I would encourage you to take some time to go through the Introduction" rel="nofollow" target="_blank">http://www.arcgis.com/home/item.html?id=265c334a47994dcc95e1bd57cf20e98e]Introduction to GeoEvent Processor tutorial to familiarize yourself with how GeoEvent Services are designed to receive and process GeoEvents created from event data received as comma separated text. Updates to this tutorial will be available shortly which will make the content more approachable - but you should find the currently available tutorial adequate for your needs. You may also find the following on-line references useful: Overview of Input Connectors Input Connectors Overview of Output Connectors Output Connectors Hope this information helps - RJ ... View more

Yes. If you want to use a GeoTagger to prepare an event for secondary enrichment then the GeoFences used for tagging events with the GeoFence name must not overlap. ... View more

Hello Morgan - It works great, UNTIL I have overlapping presets and when it gets to my Joining Processor to Field Enrich off of the existing preset (polygon layer) it isn't enriching the field with data... If I understand the issue you are describing, you are running into a known limitation of combining a Field Enricher with a GeoTagger. Think of GeoTagging as a special case of event enrichment which only allows an event to be enriched with the name of a GeoFence (and optionally the name of the Category to which the GeoFence belongs). I'll refer to this as the "primary enrichment". As long as none of your GeoFences overlap, you can use the name of the GeoFence from the "primary enrichment" as a key to join the enriched event to the polygon feature from which the GeoFence was derived and complete a "secondary enrichment". The GeoFence and polygon feature are separate objects in this model. The GeoFence object maintained by GeoEvent Processor does not include all of the attributes of the polygon feature. Hence your need to perform a table join in order to pull in the additional attributes from the polygon feature. If one or more GeoFences overlap and the event's geometry is inside the overlapping area, the primary enrichment performed by the GeoTagger enriches the event with some sort of list of names which destroys the key needed for the table join and secondary enrichment. Another way of destroying the key needed for the secondary enrichment is to include the Category to which the GeoFence belongs with the primary enrichment performed by the GeoTagger. The attribute field of the original polygon feature from which the GeoFence was derived contains only the name of the GeoFence, not the name and category, so the table join fails and the secondary enrichment cannot be completed. - RJ ... View more

On a Windows installation, the elements you create from within GeoEvent Processor Manger (e.g. Inputs, Outputs, GeoEvent Services, GeoEvent Definitions, GeoFences, registered Data Stores, etc.) are persisted beneath C:\ProgramData\Esri\GeoEventProcessor. The folders you find here are not removed when you uninstall the product. They are left behind deliberately so that you can leverage what you created when upgrading to a new product release. If you first stop the Windows service being used to run GeoEvent Processor and then delete the sub-folders beneath C:\ProgramData\Esri\GeoEventProcessor ... leaving the .\certs folder ... you will have removed the elements you previously created. The C:\ProgramData\Esri\GeoEventProcessor directory structure will be rebuilt when you restart GeoEvent Processors' Windows service. To more thoroughly reset your product installation you will need to remove the persisted cache and files used by the product during runtime. Beneath your ArcGIS for Server product installation directory (C:\Program Files\ArcGIS\Server is the default for Windows systems), locate the ...\GeoEventProcessor\data folder. If you first stop the Windows service being used to run GeoEvent Processor and then delete the data folder you will reset GeoEvent Processor to how you find it immediately following a new product installation. The ...\GeoEventProcessor\data folder will be rebuilt when you restart GeoEvent Processors' Windows service. Hope this information helps - RJ ... View more

Hello Elias - Let's try some simple checks first. On the GeoEvent Processor Manager's Monitor page, is the event count for the Watch a folder for new .csv files Input increasing? Keep in mind that if a GeoEvent Definition is not available to construct a GeoEvent from the data received - the comma separated text in this case - the event will be discarded. Your indication that this is happening is observing the event count for the Input is not increasing on the Monitor page. You might try allowing the Input to create an event definition and checking whether or not your Input is expecting the name of the event definition to be included as the 0th field of the event data. Also, keep in mind that the first two lines of the CSV file are reserved for a comma separated list of field name and a comma separated list of field data types - your actual event data needs to start with the 3rd line of the text file. With no filtering or processing in-between the Input and Output, the event count 'In' and 'Out' for the GeoEvent Service should match. The GeoEvent Service receives the events 'In' and sends them 'Out' to the Publish text to a tcp socket Output. In this case, there's nothing to debug with regard to the Output, as long as you were able to open the TCP Console application and see the message confirming that the app is listening for events on the designated port. Have you tried stopping and restarting the the Watch a folder for new .csv files Input? This will clear the Input's buffers forcing a re-read of the CSV file. Please keep in mind that a known limitation of this Input is that once it has read data from a particular file, it will not re-read that file - even if the file's contents are changed. Deleting and dragging a new copy of the file into the folder being watched has no effect. The Input is remembering the file name and will not re-read the file to re-ingest its event data. You must stop/restart the Input in order to re-read the file, or change the file's name. Hope this information helps - RJ ... View more

Hello Diallo - You are on the right track. Yes, you will need some sort of application running on the mobile device to broadcast the device's position over a communication channel / protocol (e.g. TCP, UDP, HTTP ...) which GeoEvent Processor can monitor to receive the data. Alternatively you could have an application running on the mobile device which posts JSON to a GeoEvent Processor Input connector's REST endpoint ... or establish a REST endpoint the GeoEvent Processor could poll to retrieve position information from the mobile device. These are three typical ways to get event data into GeoEvent Processor. You might want to take a look at the NMEA" rel="nofollow" target="_blank">http://www.arcgis.com/home/item.html?id=1717c2f7fe5b497491234ce3a352bdd2]NMEA Adapter tutorial we have available on our Product" rel="nofollow" target="_blank">http://www.arcgis.com/home/group.html?owner=GeoEventTeam&title=ArcGIS%20GeoEvent%20Processor]Product Gallery. While this tutorial is probably not applicable to your GPS enabled Motorola device, reading through the tutorial may provide some clarity for you with regard to how GeoEvent Processor is used to receive data feeds from mobile devices which are broadcasting information over TCP / UDP. You might also want to take a look at the forum thread [url=http://forums.arcgis.com/threads/95071-esri-receive-features-rest-in]esri-receive-features-rest-in[/url] which describes one of the alternatives I mention above - posting JSON to an Input's REST endpoint. If developing a web application using the Silverlight API doesn't provide you a ready solution, you might consider leveraging one of the native SDKs (Java, Android, iOS, WPF, ...) to develop a Runtime application which can broadcast the device's position information. Hope this information helps - RJ ... View more

Hello Kerry - Unfortunately, rework to the Manager to support the IE8 browser could not be completed for the 10.2.2 stability release. The development team has incorporated changes supporting the older browser into our daily builds of the 10.3 product, but please be aware that while all of the Manger's pages are rendering for us with these changes, the controls and page layout is not optimal. The results so far are impacting the Manager's functionality. Do your users have an option to use Chrome or Firefox on their systems? Keep in mind that if the Server itself has restrictions on what can be installed, it might be possible to manage the Server from a client machine onto which a later browser release can be installed. Hope this information helps - RJ ... View more

Hello David - I'd like to make sure I understand your question or scenario. You would like the ability to configure a filter element with an expression similar to GEOMETRY OUTSIDE FlightZones/${ZoneID} rather than naming a specific GeoFence such as GEOMETRY OUTSIDE FlightZones/ZoneA. This isn't supported in the current release. The spatial expression for a filter element (or Incident Detector processor element) will not substitute a value (e.g. an attribute value) for a variable (e.g. the name of an event field) on-the-fly as the expression is evaluated by the filter / processor when an event is received. The spatial expression must include the GeoFence category and a GeoFence name. Regular expression patterns are accepted, so an expression such as GEOMETRY OUTSIDE FlightZones/.* is valid. What you can do, at the 10.2.1 release, is combine a GeoTagger with a Filter in order to generate an alert when an asset is tagged outside of its assigned zone. For example, if you configured a GeoTagger processor to enrich events with just the name of the GeoFence they are found INSIDE, you could then configure a filter which checked to see if the name of the asset's assigned zone did not match the name of the zone in which it was most recently tagged. Something like the attached illustration. (Notice that I did not include the name of the GeoFence Category in the GeoTagger's enrichment, so I can use variable-substitution to compare the value from the field ZoneID (where the flight is supposed to be) with the value in the GeoTag field TaggedInZone. Hope this helps - RJ ... View more

The simulation files such as Flight.csv should have been included in the ZIP file with the PDF of the Introduction to GeoEvent Processor you download from the Product" rel="nofollow" target="_blank">http://www.arcgis.com/home/item.html?id=265c334a47994dcc95e1bd57cf20e98e]Product Gallery ... they are not part of the product installation on the server. Please make sure that you have the following to support your walk through of the tutorial exercises. configurations/AVLConfig.xml configurations/FieldMapping_Config.xml configurations/Geotagging_Config.xml configurations/IncidentDetection_Config.xml configurations/WorkingWithFeatures_Config.xml data/WorkingWithFeatures/Flights.mpk data/WorkingWithFilters/polygon.txt data/WorkingWithFilters/Storms.mpk data/WorkingWithProcessors/flightPilotInformation.csv data/WorkingWithProcessors/IncidentDetection.mpk data/WorkingWithProcessors/Pilots.mpk simulation_files/AVLSample.csv simulation_files/FeatureFlights.csv simulation_files/FieldMapping.csv simulation_files/Flight.csv simulation_files/Geotagging.csv simulation_files/Trucks.csv utilities/OperationsDashboard.application utilities/tcp-console-app/tcp-console-app.bat utilities/tcp-console-app/TcpPrinter.class - RJ ... View more

Hello Ayman - To which Input are you referring?  At the 10.2.1 product release 'Poll an ArcGIS Server for Features' allows you to choose either the 'FeatureServer' or 'MapServer' endpoint of a published service to poll for feature data. Other product capabilities such as synchronizing GeoFences also support the selection of 'FeatureServer' or 'MapServer' endpoints. Are you trying to use a 'MapServer' endpoint and it is not working? - RJ ... View more

Looks like the folks from SharpenYourGISSkills did not include the demonstration data in their map package. The ZIP file available from the [URL= http://sharpenyourgis.maps.arcgis.com/home/item.html?id=42bbc4283b2b408dbc71d4ecc97aa032]demonstration page[/URL] has been updated. If you download the updated ZIP you�??ll find a GEP.gdb in the �?�/02 GeoEvent Processor/Data folder. As you noted, if you allow Desktop to unpack the map package, the *.mxd and supporting data are usually found in folders named v10 and v101 beneath the �?�/ArcGIS/Packages/ folder (usually in your user�??s My Documents folder). When I open the GEP.mpk from the download in ArcMap, my TOC is full of broken feature layers. The layers appear to be looking for their data in a database named GEP in an instance of SqlExpress named localhost_sqlexpress. You could either repair the map document by pointing its data layers to the GEP.gdb found in the �?�/02 GeoEvent Processor/Data folder �?� or use a copy of the GEP.mpk I�??ve attached to this thread. The map package I�??ve attached includes the GEP.gdb inside the map package�??s v101 internal folder ... so it should open in ArcMap cleanly without any broken layers. The reason, by the way, that you need to copy the data to an enterprise geodatabase in your enterprise is that feature services cannot be published with the �??Feature Access�?? capability enabled if the datasets supporting the map document�??s feature layers are in a file geodatabase �?? which is how the data is packaged for distribution when sharing map packages. Using GEP to update the data through a published feature service requires that the 'Feature Access' capability be enabled. Hope this helps - RJ ... View more