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 SimulatorKafkaMQTTRabbitMQRSSStream LayerVerizon Connect RevealWebSocket

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

GTFS

In this topic

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

The GTFS feed type in ArcGIS Velocity periodically polls GTFS Realtime data by sending an HTTP or HTTPS request to a specified URL. For more information about the GTFS Realtime specification, see GTFS Realtime Overview in the GTFS Realtime documentation.

ArcGIS Velocity supports the following GTFS realtime data feed types in either the protocol buffers (protobuf) or JSON format:

  • Vehicle positions
  • Trip updates
  • Service alerts

Example

A transportation analyst wants to ingest data from a transit agency to receive updates on trips, alerts, or vehicle locations.

Usage notes

Keep the following in mind when working with the GTFS feed type:

  • The GTFS endpoint must be externally accessible on the internet.
  • The feed will poll the GTFS endpoint to load data at the rate defined on the Feed Polling Interval step of the configuration wizard.
  • When a polling interval is set, the polling occurs at regular time intervals as opposed to the start time of the feed. For example, if the feed is set to poll for data every five minutes, and the feed is started at 8:03 a.m., the first request for data will occur at 8:05 a.m., the next at 8:10 a.m., and so on.

Parameters

The following table lists the GTFS feed type parameters:

ParameterDescriptionData type

URL

The full URL to the externally accessible GTFS endpoint.

String

GTFS type

Specifies the type of information the feed will receive. Options are as follows:

  • Vehicle positions—Information about the vehicles including location and congestion level
  • Trip updates—Information about delays, cancellations, and changed routes
  • Service alerts—Information about stop, moved, and unforeseen events affecting a station, route, or the entire network

String

HTTP headers

Specifies the headers to use for the GTFS URL endpoint.

String

Additional logging

Optionally enable logging for raw HTTP requests and responses issued by Velocity.

Note:

This parameter should only be enabled for troubleshooting purposes and disabled when troubleshooting is complete. Once enabled, start the feed and the debug level logs will be available on the feed logs page. If necessary, contact Esri Technical Support for assistance with troubleshooting.

Boolean

Considerations and limitations

The following are considerations and limitations for the GTFS feed type:

  • The GTFS feed must be externally accessible on the internet.
  • The GTFS feed must be in the protobuf (binary) or JSON format.

Feedback on this topic?

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