Work with input data

Configure input dataIngest real-time dataIngest historical dataLocation parametersDate and time parametersFeed polling interval schedulingFeed to history feature layer

Feeds

Work with feedsFeed details and statusShare feedsAWS IoTAzure Event HubAzure Service BusCisco Edge IntelligenceGeotab (DeviceStatusInfo)Geotab (LogRecord)gRPCGTFSFeature LayerHTTP PollerHTTP ReceiverHTTP SimulatorKafkaMQTTRabbitMQRSSSamsaraStream LayerVerizon Connect RevealWazeWebSocket

Data sources

Work with data sourcesAmazon S3Azure Blob StorageAzure Cosmos DBFeature LayerFeature Layer (archive)HTTP PollerRSSStandard geographies

Data formats

Supported data formatsDelimitedJSONEsri JSONGeoJSONXML

Troubleshoot

Common ingestion issues and solutions
Back to Top

HTTP Receiver

In this topic

  1. Examples
  2. Usage notes
  3. Parameters
  4. Considerations and limitations

Rather than having an IoT system make requests for external data, a common workflow is to push data from devices within an organization's IoT infrastructure. One way is through HTTP POST requests made to a web server. The HTTP Receiver feed in ArcGIS Velocity creates a built-in HTTP endpoint that can be used to programmatically send data from IoT devices and applications to Velocity with HTTP POST requests.

Examples

The following are examples of using the HTTP Receiver feed:

  • An organization has devices configured to push data to a specified Velocity HTTP endpoint using POST requests.
  • A GIS analyst writes a Python script that processes features and pushes data to a specified Velocity HTTP endpoint using a POST request each time the script runs.

Usage notes

Keep the following in mind when working with the HTTP Receiver feed:

  • Send HTTP POST requests as plain text.
  • The HTTP Receiver feed is configured by the user, including the schema and key fields. Once the feed is created, the URL is available on the feed details page under HTTP Endpoint Path. This is the URL to which data can be pushed using an HTTP POST request.
  • Set the Authentication type parameter to ArcGIS to use OAuth 2.0 authentication. Each incoming message must include a valid token for the owner of the feed. Messages without a valid token will be rejected.
  • After configuring the feed connection parameters, see Configure input data to learn how to define the schema and the key fields.

Parameters

The following are the parameters for the HTTP Receiver feed:

ParameterExplanationData Type

HTTP Endpoint Path

The full URL to use to send messages.

The URL is generated and populated by Velocity after the feed is started.

String

Authentication type

Specifies the authentication type for incoming messages. Options are None and ArcGIS. If None is specified, no authentication is performed. If ArcGIS is specified, each incoming message must include a valid token for the owner of the feed. Messages without a valid token will be rejected.

The token must be in the request headers as Authorization: Bearer <your token>.

String

Additional logging

Specifies whether logging for raw HTTP requests and responses issued by Velocity will be enabled.

Note:

Only enable this parameter for troubleshooting purposes and disable it when troubleshooting is complete. Once enabled, start the feed, and the debug level logs will be available on the feed logs page. Contact Esri Technical Support for assistance with troubleshooting if necessary.

Boolean

Considerations and limitations

HTTP Receiver feeds using the ArcGIS authentication can be shared with write privileges to other users and groups. When an HTTP Receiver feed is shared with write privileges, users and groups who it is shared with can write data to the feed. Do not share a feed with write privileges enabled if you do not want other users and groups to write data to it. You can enable and disable write privileges from the feed details page in Velocity. For more information, see Share feeds.

Feedback on this topic?

In this topic
  1. Examples
  2. Usage notes
  3. Parameters
  4. Considerations and limitations