In Between - Including Bounds-The line length is between or equal to the number of units specified in the Lower Bound (minimum) and Upper Bound (maximum) text boxes.
For example, if the value is 10, lines with a length value of 10 are returned as results.
Equal to-The line length is equal to the number of units specified.
For example, if the value is 10, lines with a length value of 8, 12, or any other value that is not equal to 10 are returned as results.
Not equal to-The line length is not equal to the number of units specified.
For example, if the value is 12, lines with a length value of 12 or more are returned as results.
Greater than or equal-The line length is equal to or greater than the number of units specified.
For example, if the value is 10, lines with a length value of 11 or more are returned as results.
Greater than-The line length is greater than the number of units specified.
For example, if the value is 10, lines with length values of 10 through 0 are returned as results.
Less than or equal-The line length is equal to or less than the number of units specified.
For example, if the value is 10, lines with length values of 9 through 0 are returned as results.
Less than-The line length is less than the number of units specified.
Click the Operation drop-down arrow and choose an operation to use.
Click the drop-down arrow in the Length area and choose the unit of measurement to use with the feature length.
Segment-A section of a line feature that is connected by two adjacent vertices on a line feature.
Part/Path-A part of a multipart line feature or a single path on a line feature.
Click an option for the polyline feature in the Type area.
To run the check on specific features in a feature class, click SQL to construct an SQL query.
#Gpsmapedit reducing points in a polyline full#
To run the check on the entire feature class and save this setting, check the Always Run on Full Database check box.
Click the Feature Class/Subtype drop-down arrow to choose the feature class and subtype on which to run the check.
This is useful when you have multiple instances of the same check to validate the same feature classes or tables but with different validation parameters. The check title can be used to describe the conditions you are looking for with the check.
#Gpsmapedit reducing points in a polyline plus#
Click the Select Data Check drop-down arrow on the Data Reviewer toolbar, click the plus sign (+) next to Polyline Checks, then click Evaluate Polyline Length Check.
On the main menu, click Customize > Toolbars > Data Reviewer.
The lower the number, the greater the priority the check's results have. The severity rating allows you to indicate how important the results from a check are in terms of your quality assurance/quality control processes. The notes allow you to provide a more specific description for the feature that has been written to the Reviewer table and are copied to the Notes field in the Reviewer table. Once you have defined the criteria for the check, you can configure the notes and a severity rating. The check can be run on an entire feature class, a subtype, or a set of features selected using a SQL query. In this case, street centerlines with any part less than one meter can be returned as results. For example, you can find street centerlines with parts that are too small relative to the size of the feature. Any features that meet the conditions specified in the check are returned as results. The Evaluate Polyline Length check evaluates the length of any of the polyline components to make sure it is within allowed parameters. Paths are specific to polylines and rings are specific to polygons. Polyline features can be analyzed as whole features or in terms of their components, such as segments and parts or paths. Evaluating segment, part/path, and polyline lengths