The Simplifier Processor is used to correct geometry associated with an event record to render the geometry topologically consistent with its type. The Simplifier Processor has no effect on point geometry. Multipoint geometries snap all vertices to a grid appropriate for the geometry's spatial reference and remove duplicate vertices. Polyline and polygon geometries with self-intersecting segments are reconstructed with multiple paths or rings to produce a topologically correct multipart polyline or polygon.
Examples
The following are example uses of the Simplifier Processor:
- The Simplifier Processor can be used to correct the geometry from external data sources before attempting to send the event data to a feature service for display in a web map.
- Use the Simplifier Processor at the beginning of a GeoEvent Service as one method to ensure quality assurance and quality control of geometric data.
Usage notes
Keep the following in mind when working with the Simplifier Processor:
- Simplification is not the same as generalization. Simplification removes unnecessary vertices along an otherwise topologically correct line segment or reshapes a geometry to reduce detail to produce a geometry for more efficient display at small map scales. The purpose of simplification is to produce a feature that is valid for writing to a geodatabase.
- Provided a point, the processor returns the same point. The processor has no effect on point geometry.
- Provided a multipoint, the processor snaps all vertices to a grid appropriate for the geometry’s spatial reference, removing duplicate vertices.
- Provided a polyline or polygon, the processor evaluates for self-intersecting segments. Geometries with self-intersecting segments are reconstructed with multiple paths or rings to produce a topologically correct multipart polyline or polygon.
- Features created in an ArcGIS Desktop or ArcGIS Pro editing session are already topologically correct and simple.
- Features polled from a feature service do not require simplification before processing them in a GeoEvent Service.
- This processor can be configured to replace the event record's geometry with the simplified geometry or place the simplified geometry into a new field using the Replace Geometry parameter. Adding a new field to an event record alters the event record's schema, which requires GeoEvent Server to create a new GeoEvent Definition. The new GeoEvent Definition is managed by GeoEvent Server and deleted if changes are made to the processor or the GeoEvent Service in which the processor is used.
Parameters
The following are the parameters for the Simplifier Processor:
| Parameter | Description |
|---|---|
|
Name |
A descriptive name for the processor used for reference in GeoEvent Manager. |
|
Processor |
Specifies the processor selected. |
| Geometry Field | The name of the geometry field or the field tagged with the GEOMETRY tag from the inbound event record. The processor evaluates and corrects the geometry from this field to render it topologically consistent with its type. |
| Replace Geometry | Specifies whether to replace the active geometry with the simplified geometry. The default is Yes.
|
| New Geometry Field Name (Conditional) | The name of the new geometry field that stores the simplified geometry. The parameter is shown when Replace Geometry is set to No and is hidden when set to Yes. |
| Tag the New Geometry Field as Geometry (Conditional) | Specifies whether the new geometry field created by the processor is tagged with the GEOMETRY tag. The GEOMETRY tag is used by GeoEvent Server to identify the event record’s realized geometry when multiple geometry fields are present. The default is No. The parameter is shown when Replace Geometry is set to No and is hidden when set to Yes. |
| New GeoEvent Definition Name (Conditional) | The name assigned to the new GeoEvent Definition. The new GeoEvent Definition combines the schema of the inbound event record with the new geometry field. The parameter is shown when Replace Geometry is set to No and is hidden when set to Yes. |
Considerations and limitations
Consider the following when working with the Simplifier Processor:
Replace the existing event record geometry with the simplified (corrected) geometry before sending the event data to a feature service. Feature services only support one geometry type field, which should be tagged with the GEOMETRY tag. The second geometry field's value can be converted to string to retain the event record's data value. Feature services drop or discard invalid geometries received from GeoEvent Server.