ArcGIS GeoEvent Server 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 Extend GeoEvent Server to learn more about adapters and transports.
GeoEvent Server includes the following input connectors:
Input connectors available on the ArcGIS GeoEvent Server Gallery include the following:
Receive Feature JSON from ActiveMQ
Receive JSON from ActiveMQ
Receive Text from ActiveMQ
Azure IoT Hub
Receive JSON from Azure IoT Hub
Common Alerting Protocol (CAP)
Receive CAP XML Messages
Cursor on Target (CoT)
Receive CoT XML Messages
Receive GTFS Realtime Feed
Receive Media Feed from Instagram
Receive CSV from an External MQTT Message Broker
Receive JSON from an External MQTT Message Broker
Receive XML from an External MQTT Message Broker
Receive NMEA on a UDP Socket
Receive text from RabbitMQ
Sierra Wireless RAP
Receive Sierra Wireless using RAP
Receive Trimble using TAIP
Receive tweets from Twitter
Verizon Connect (formerly Telogis)
Receive Verizon Connect
Receive Waze Connected Citizen Program Feed
Esri Partner-contributed input connectors available on the ArcGIS GeoEvent Server Partner Gallery include the following:
Looking for a different connector?
If the connectors available do not provide the flexibility you need, you can customize the connectors using the GeoEvent Manager to develop your own connectors using the GeoEvent Server Software Development Kit (SDK).
See Extend GeoEvent Server to learn more about customizing connectors or developing your own connectors.
Do you have ideas for new input connectors? Post your ideas on the ArcGIS GeoEvent Server Ideas place in the Esri Community.