Available in real-time and big data analytics.
The Merge Layers tool
copies two layers to create a single output
layer. Both layers must have the same feature geometry
type (tabular, point, line, or polygon) and at least one matching field name and type. If
time is enabled on one layer, the other layer must also be time
enabled and have the same time type (instant or interval).
Workflow diagram
Example
A city wants to restore the area around a river by developing a new park. The park must be near the river but not in close proximity to existing parks or hazardous facilities. Buffers around the existing parks and hazardous facilities can be merged into a single layer using the Merge Layers tool to create an exclusion zone where a new park should not be developed.
Usage notes
- Two inputs of the same feature geometry type are required (point, line, polygon, or tabular).
- The two inputs must have at least one matching field name and type to be merged.
- For any matching field name, the field type must be the same.
- If a field is present in one schema but not the other, it will be added to the output schema and a null value will be configured if a value is not present for a record.
- This tool can merge inputs with the same schema that have fields in a different order. It is recommended you merge inputs with fields in the same order.
Parameters
| Parameter | Description | Data type |
|---|---|---|
Input Layer | The point features for which density will be calculated. | Features |
Merge With | The point, line, or polygon features or table to merge with the input layer. The merge layer must contain the same feature type and schema as the input layer. | Features |
Output layer
The output layer will retain the same schema of the input and merge layers. For any matching field name, the field type must be the same. If a field is present in one schema but not the other, it will be added to the output schema and a null value will be configured if a value is not present for a record.
Considerations and limitations
- Input layers can be point, line, or area features, and must be the same feature type.
- For any matching field name, the field type must be the same.
- When merging fields with the same name but different nullable values (nullable can be true or false), the resulting field will be nullable.
- If a field is present in one schema but not the other, it will be added to the output schema and a null value will be configured if a value is not present for a record.