Skip to main content

Common ingestion issues and solutions

Common issues you can encounter when ingesting data in ArcGIS Velocity are described below, along with recommended solutions. If you encounter an issue that is not addressed below, check Esri Community and contact Esri Technical Support.

Note:

For issues and solutions related to accessing the Velocity app, signing in, or creating and starting items, refer to the troubleshooting page.

Data sampling

Data issues

General feed behavior and issues

Why are no samples returned for the Confirm Schema step?

If you're using the HTTP Poller or RSS feed or data source, ensure that the website response or file being polled does not exceed 16 MB. The maximum file size is 16 MB, regardless of your Velocity license level.

For other feed or data source types, the time it takes to sample data can exceed the time-out for sampling. This issue can arise from large data sizes or insufficient sample collection during the sampling period. Try resampling or use the workflow to manually type samples.

Learn more about sample real-time data

Why is my data not (or no longer) being received by the feed or analytic data source?

Ensure that the schema defined on the feed or data source matches the incoming data and the data is externally accessible. Consider the following:

  • Did the samples retrieved on the feed or data source configuration encompass all possible attributes?

  • Did you provide samples that do not match the incoming data?

  • Did the format of the data change since the feed or source was configured?

  • Is the geometry configured correctly?

  • Is the external system or resource still accessible on the internet with the defined connection properties?

Ensure that Velocity can still connect to the external system or resource (broker, website, cloud IoT resource, or other). Try editing the feed or data source and resampling data as the configuration process checks for connectivity. Creating a new feed or source can be faster than troubleshooting an existing source. If the schema changes, it can affect analytic outputs using the feed or data source and you may need to re-create them.

If the issue is with a feed that polls periodically for data, consider the frequency of the polling schedule. Polling occurs on regular clock intervals as opposed to the start time of the feed. For example, if a feed is set to poll for data every 5 minutes and the feed starts at 8:03 a.m., the first request for data occurs at 8:05 a.m., the next at 8:10 a.m., and so on. For data that changes infrequently, a best practice is to test the feed with a polling interval of every 10 or 30 seconds to ensure that the data is successfully retrieved; then update the feed with the appropriate polling interval.

Why is my data missing values or have incorrect values in certain attributes?

Field types can be incorrectly defined.

  • Defining a field as numeric when string character values are also present in the data associated with that field results in no data being ingested.

  • Setting a Float64 field as a Float32 field alters the data values by dropping precision.

For date fields created from strings, ensure that the data formatting string is accurate for all incoming date values.

Why doesn't my feed start?

There can be errors related to the feed. Review validation errors on the feed details page and edit the feed to fix any errors as necessary.

Why did my feed stop unexpectedly?

Feeds are controlled by the ArcGIS Velocity Feed Manager service. If an individual feed or collection of feeds exceeds the resources available to the Feed Manager service, feeds can stop. A system administrator performing administrative actions on the site may also cause feeds to temporarily stop.

Cannot connect to data source

Some data providers, such as Kpler, transmit data over ports that differ from standard web traffic and must be explicitly permitted through your organization's firewall. If these ports are blocked, Velocity is not able to connect to the data source. If you encounter errors while entering and validating the data source during feed configuration, contact your data provider to confirm if ports are required for data access.

Cannot successfully add feed to Map Viewer

If you cannot successfully add a feed to Map Viewer and stream features, this is commonly caused by SSL/TLS certificate issues between the Map Viewer client and the stream service endpoint. Check your certificate configuration and ensure that all applicable root and intermediate certificates have been imported. For more information, refer to the troubleshooting topic.