Latest Contributions by MarkBramer

Yes, and yes. ... View more

In some weird twist of fate, I got this error literally about 4 hours after I read your post and thought "wow, that's a weird one..." What worked for me is stopping GeoEvent, deleting the .jar from /deploy, deleting the /data folder in the GeoEvent installation location, then restarting, and redeploying.  Deleting /data is a last-resort option for resetting GeoEvent when things really start to go squirrely.  It seems like you're deleting part of the actual GeoEvent install, but you're not - GeoEvent will rebuild the entire /data folder upon restart.  Of course with all things like this, it's best to copy /data to somewhere else (Desktop, C:/temp, anything) before deleting. ... View more

Jeremy, I apologize for not seeing your message.  Either I do not have my GeoNet notifications set up properly, or GeoNet notifications suck.  I did not realize you replied until I just clicked on this message thread.  I doubt your original use case is still in effect, but if you want to keep talking GeoEvent, email me at [email protected]. Mark ... View more

Are all your SSL certificates fully valid and in place?  Can you navigate to https://mirie-pc.stltd.co.il/arcgis/rest/services/cars_Feed/StreamServer in a browser without any secure connection warnings, and get a 'green' notification (i.e. padlock, green 'http:', etc) that everything is good?  ... View more

I can physically see the service endpoint (i.e. no firewall is blocking me) but I get prompted for a token.  I follow the link it presents to get one, but I then get a blank page with just an "API reference" link.   You can either geofence the items in the live feed or import buffered static points as geofences.  Both are viable options.   Option 1. If you have static points, you can buffer them in ArcMap, then serve out the buffers as a feature service.  You register a "Data Store" (ArcGIS Server, Portal, or ArcGIS Online) in GeoEvent Manager that points to that instance, then you will have access to the buffer layer when setting up any filter or processor that needs to use those buffers as a geofence. Option 2. You could just serve out the points layer as a feature service.  Register the data store the same way, then you will have access to the points layer the same way.  The only difference is that you'll need to buffer the geoevents, then use that polygon in your filter or processor to do your spatial operation.  They both can get you what you want, just using two different logical approaches. In case #1 you have geoevent *points* you use with an "INSIDE" operation when comparing to *polygon* geofences (the polygons in the feature service), whereas in case #2, you have geoevent buffer *polygons* you use with a "CONTAINS" operation when comparing to *point* geofences (the points in the feature service).  You can do exactly what you want, it's just a matter of piecing it together.  I know your question is still unanswered, but I'm trying to lay out general concepts.  If you can get me a link to a feed I can see, I can list out the exact steps you need to do. In the meantime, here is a video from UC that you may want to check out.  I haven't watched the whole thing but upon skimming it, I noticed some setting up of inputs, and setting up of some geofencing.   Video Link : 3486  ... View more

Hi Jeremy, Some questions to start with: 1. Do you have the hurricane feed actively working in GeoEvent, so that you see an incrementing "Count" in the Monitor tab of GeoEvent Manager? 2. Are the geoevents in this feed points or polygons (cones)? 3. The points to be buffered - are they geoevents themselves, or static points that already exist?  Or do the buffers exist? Mark ... View more

Anything's possible.  I know, I know, you just rolled your eyes, but hear me out. The key here is to not think of the vendors' ability or non-ability to work directly with GeoEvent.  Unless the vendor, or an otherwise interested party, creates the GeoEvent connectors, it's impossible for the Esri GeoEvent team to make and maintain a connector for every possible vendor - it's just not a realistic development and maintenance feasibility. So then what's the key?  The key is to find out lower level details about these vendors' APIs and data formats.  How does a developer or integrator communicate with the vendors' products/APIs - HTTP?  TCP?  Web socket?  UDP?  What is the format of the actual data?  Comma-separated fields? Tab-separated fields?  XML?  JSON? GeoEvent ships with native support for a bunch of industry standard transport mechanisms (HTTP, TCP, UDP, Web socket, etc) as well as native support for a a bunch of data formats (CSV, JSON, etc).  If a vendor's connector doesn't exist natively (which is most likely the case), but you find out their API is REST-based and returns tab-separated data, then you could "marry-up" the HTTP transport with the Text adapter and make a new GeoEvent connector with no development required.   There are possibilities to integrate vendors' products APIs with GeoEvent, but I won't go into it here.  Anybody interested in hearing more can contact me if desired. I hope this helps clarify some things. Mark Bramer ... View more

Do you need to enter, or re-enter credentials for the data store connection in Manager-Site-Data Stores? ... View more

Jay, You can make a new connector to do what you want by combining the XML adaptor with the File transport.  Look here for a start: http://server.arcgis.com/en/geoevent-extension/latest/administer/extending-the-geoevent-extension.htm   Mark ... View more

Hi Heather,   Just some simple statements on the multiple items you mention:   No, you do not need the Web Adaptor on your ArcGIS Server machine hosting GeoEvent.  You can choose to install it for all the reasons we recommend (http://server.arcgis.com/en/server/latest/install/windows/about-the-arcgis-web-adaptor.htm#GUID-030D93EF-B788-4B4A-9262-1F3601D7FA35) but GeoEvent does not need it, nor do you need it to use GeoEvent.  The Web Adaptor does not support any web socket-based GeoEvent outputs, including Stream Services.  To set up a real-time server in a reverse-proxy manner while using any web socket based outputs, we recommend using NGINX (pronounced "engine ex") as it has good support for the web socket protocol. You've done what we recommend for real-time deployments, which is to stand up a dedicated ArcGIS Server box with GeoEvent.    GeoEvent clustering has not worked out like we hoped and we no longer recommend using it.  If you have a throughput rate greater than what can be handled by a single real-time server, it is certainly possible to set up multiple real-time servers to handle throughput, but you need to really think about things like how to split up your incoming messages, how to handle any stateful scenarios like 'enter' or 'exit' geofence operations or monitoring ongoing incidents, and how to handle event outputs appropriately (i.e. can you afford outputting messages in a non-chronological order?  ...not necessarily an issue if they're time-stamped).   If any of this is confusing or you want more info, feel free to email me at [email protected].   Mark ... View more

Also, see this: GeoEvent Processor won’t start up after upgrade ... View more

Glad to hear it's fixed, and glad to have more info for if/when I see it myself! ... View more

Hi Jawadh, If I understand what you're asking, you would use the "Add a feature" output.  There are now two of these - one for regular feature services (there since 10.2) and one for the new Spatiotemporal Big Data Store (10.4).  Both enable the "breadcrumb" capability since the outputs are simply appending the database with each new GeoEvent received.  This is contrary to the two "Update a feature" outputs, which update (i.e. move or modify an attribute) a particular asset, vessel, vehicle, etc. Mark ... View more

Hi Bobby, Whenever I need to see what is emitted from any component in a GeoEvent Service, I wire up a JSON file output directly after the component I'm curious about.  The great thing about the JSON file output is that the field names are written as well as the values (csv files do not have the field names).  So create a new JSON file output, and modify your GE Service to wire up your geotagger to output to the JSON file output, then look in the JSON file to see your data with the field names and values. Mark ... View more