Essential analytic concepts

Real-time analysisBig data analysisAnalytic optionsShare analyticsView analytic details and statusGeofence analysisSample real-time data

Analyze patterns

Calculate DensityCalculate JourneysFind Hot SpotsFind Point ClustersGeneralized Linear RegressionForest-based Classification and Regression

Enrich data

Calculate Motion Statistics

Find locations

Delay and Reorder TracksDetect IncidentsDetect GapsFind Dwell LocationsFind Similar Locations

Manage data

Add XYZ ValuesCalculate FieldControl Event VolumeDissolve BoundariesFeature to PointFilter by ExpressionFilter by Time RangeFilter by GeometryMap FieldsMergeMulti-MergeOverlay LayersProjectRoute by ExpressionsSelect Fields

Summarize data

Aggregate PointsJoin FeaturesReconstruct TracksSummarize AttributesSummarize Within

Use proximity

Create BuffersCreate Range FansCalculate DistanceSnap to Network

Schedule recurring analysis

Schedule recurring big data analysisNear real-time analysisGenerate up-to-date informational products

Arcade expressions

Use Arcade expressionsUse track functionsBest practices for Arcade expressions

Troubleshoot

Common analysis issues and solutions
Back to Top

Multi-Merge

In this topic

  1. Example
  2. Usage notes
  3. Parameter
  4. Output pipelines

Tool button Available in real-time analytics.

The Multi-Merge tool combines up to 10 inputs into a single output schema. All inputs must share the same feature geometry type (point, line, polygon, or tabular) and their schemas must include at least one field with a matching name and data type.

Example

A transportation authority monitors multiple real-time data feeds for incidents, such as accidents, road closures, and severe weather alerts. The Multi-Merge tool can combine these incoming feeds into a single unified schema. This allows you to use downstream tools to process all incident types through one pipeline rather than managing multiple pipelines for each feed.

Usage notes

Keep the following in mind when working with the tool:

  • The Multi-Merge tool consists of a single input port that accepts a minimum of two and up to 10 inputs, and a single output port of a single output. At least one field with the same name and data type must be present in all input schemas.
  • Partial or complete schema overlap from each input is supported. For example, if input 1 with fields A, B, C, is merged with input 2 with fields B, C, D, the resulting output is union of all fields: A, B, C, D. If data comes from input 1, it populates the D field with null values.
  • Fields do not need to be in the same order in each input schema to be merged.
  • If two or more input schemas contain fields with the same name and data type, but one includes tags, such as TRACK_ID, START_TIME, or END_TIME, and the others do not, the output schema includes the tags.
  • If two or more fields across input schemas are assigned the same tag, such as TRACK_ID, START_TIME, or END_TIME, the tool returns a validation error.
  • When multiple input schemas contain a field with the same name but different numeric data types (for example, int32 in one schema and float64 in another), ArcGIS Velocity automatically resolves the conflict by converting all occurrences of that field to a single target numeric data type. The target data type is chosen based on a numeric promotion hierarchy: Int32 → Int64 → Float32 → Float64.
    • A special case applies when a field with the same name appears as Int64 in one input schema and Float32 in another, the field is upgraded to Float64 (instead of Float32) to prevent significant precision loss.
  • When merging fields with the same name but different nullable values (nullable can be true or false), the resulting field is nullable.

Parameter

The following is the parameter for the tool:

ParameterDescriptionData type
Input layers

The point, line, polygon, or tabular features to be merged. Each input must have the same feature geometry type (point, line, polygon, or tabular) and their schemas must include at least one field with a matching name and data type.

Features

Output pipelines

The output contains a unified schema that merges the fields from all input schemas. Fields common across each input schema are retained. If a field exists in one input schema but not in the other, it is added to the output schema. If an incoming feature does not provide a value for that field, a null value is assigned.

Feedback on this topic?

In this topic
  1. Example
  2. Usage notes
  3. Parameter
  4. Output pipelines