Input Connectors
GeoEvent is capable of receiving event data from virtually any source by using an Input Connector. An Input Connector must know how the data is being received as well as how the data is formatted. These tasks are handled by adapters and transports, which are technical implementations beneath each and every connector.
See Extending GeoEvent Processor to learn more about adapters and transports.
Input Connectors
GeoEvent Processor includes the following Input Connectors:
ArcGIS Server | Poll an ArcGIS Server for features |
File | Watch a folder for new .csv files Watch a folder for new .json files |
RSS | Receive RSS |
Socket | Receive text from a TCP socket Receive text from a UDP socket |
Web | Receive features on a REST endpoint Receive JSON on a REST endpoint Poll an external website for JSON |
WebSocket | Receive JSON on a WebSocket |
Input Connectors available on the ArcGIS GeoEvent Processor Gallery include the following:
ActiveMQ | Receive feature JSON from ActiveMQ Receive JSON from ActiveMQ Receive text from ActiveMQ |
Receive media feed from Instagram | |
NMEA | Receive NMEA on a UDP socket |
Sierra Wireless | Receive Sierra Wireless using RAP |
Trimble | Receive Trimble using TAIP |
Receive Tweets from Twitter |
Esri Partner-contributed Input Connectors available on the ArcGIS GeoEvent Processor Partner Gallery include the following:
exactEarth | Receive AIS |
Networkfleet * | Receive Networkfleet |
Zonar * | Receive Zonar |
* This Input Connector is coming soon.
Looking for a different connector?
If the connectors available do not provide the flexibility you need, you can customize the connectors using the GeoEvent Processor Manager.
See Extending GeoEvent Processor to learn more about customizing connectors.
Do you have ideas for new Input Connectors? Visit ArcGIS Ideas, tag the ideas with geoevent processor, and choose the ArcGIS Server category when posting.