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 feedsADS-B ExchangeAWS IoTAzure Event HubAzure Service BusBaron WeatherCisco Edge IntelligenceDTN WeatherGeotab (DeviceStatusInfo)Geotab (LogRecord)gRPCGTFSHAAS AlertFeature LayerFlightAware (Airborne)FlightAware (Surface)HTTP PollerHTTP ReceiverHTTP SimulatorKafkaKplerMotive AVLMQTTPreCise MRMRabbitMQRSSSamsaraStream LayerTAK Client (Beta)TracPlusVectronic AerospaceVerizon 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

Kpler

In this topic

  1. Examples
  2. Usage notes
  3. Parameters
  4. Consideration and limitation

The Kpler feed type in ArcGIS Velocity connects to Kpler to ingest automatic identification system (AIS) data, providing real-time visibility into global maritime vessel movements.

Learn more about Kpler

Examples

The following are example use cases for the feed:

  • A maritime logistics company uses the Kpler feed to monitor real‑time vessel movements, identify expected arrivals, berthing delays, and deviations from scheduled routes.
  • A national government agency uses the Kpler feed for vessel tracking congestion monitoring and to assess maritime traffic density and high-risk congestion zones for safety and compliance.

Usage notes

Keep the following in mind when working with the feed:

  • You can create consumer groups by using your provided consumer group prefix and appending a unique suffix. For example, if your prefix is cityname-group, the new consumer group IDs include cityname-group-example1 or cityname-group-example2.
  • Velocity automatically handles the data schema. Adding fields is not supported because the schema is predetermined and based on the data provided by Kpler.
  • Velocity automatically handles the Date and time and Track ID parameters for the feed.
  • The data provided by Kpler is in the JSON data format, so the Location parameter is handled automatically when identifying key fields.

Parameters

The following are the parameters for the feed:

ParameterDescriptionData type
Kpler Username

(Required)

The username associated with your Kpler account.

String

Kpler Password

(Required)

The password associated with your Kpler account.

String

Kpler Topic

(Required)

The Kpler topic provided by Kpler to which the Kpler feed subscribes for messages.

String

Kpler Consumer Group ID

(Required)

The consumer group ID provided by Kpler for data streaming.

String

Consideration and limitation

Consider the following when using the feed:

Each consumer group can have only one active feed. You can create multiple feeds using the same consumer group, but only one of those feeds can be actively ingesting data.

Feedback on this topic?

In this topic
  1. Examples
  2. Usage notes
  3. Parameters
  4. Consideration and limitation