Polyline Collinear Middle Pruner
Prune middle vertices lying within a supplied perpendicular distance of the enclosing segment and between endpoints; reversals are preserved.
Description
Prune middle vertices lying within a supplied perpendicular distance of the enclosing segment and between endpoints; reversals are preserved.
A nearly collinear middle point can be removed only if it lies between the retained endpoints. That condition avoids erasing a backtrack.
When to use this tool
Prune middle vertices lying within a supplied perpendicular distance of the enclosing segment and between endpoints; reversals are preserved.
- Prepare the supplied points, tolerance fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter points, tolerance. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.points, result.sourceIndexes. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Maintain retained source indexes as a stack. For each newest triple measure middle-point perpendicular distance to the outer segment and its projection bounds; remove it when distance is within nonnegative tolerance and projection lies on the segment. Repeat as needed.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| points | points. | Numeric rows; at most 128 rows and 128 values per row |
| tolerance | tolerance. | Finite number; zero or greater |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.points | The points list in the ordering and representation described above. |
| result.sourceIndexes | Original input positions of the retained or selected records, under the ordering described above. |
{
"input": {
"points": [
[
0,
0
],
[
1,
1
],
[
2,
2
]
],
"tolerance": 0
},
"output": {
"result": {
"points": [
[
0,
0
],
[
2,
2
]
],
"sourceIndexes": [
0,
2
]
}
}
} Limitations and assumptions
- Tolerance uses the point-coordinate unit. This local simplifier does not guarantee a global error bound, preserve topology or simplify SVG curves.
- Point pairs use [x,y], rectangles and viewBox use [x,y,width,height], and all coordinate units must be consistent. This tool does not read, render or modify an SVG document.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- String lists have at most 128 entries of at most 128 code units; matrices have at most 128 rows and columns. Larger numeric lists and parsed JSON have separate bounded budgets. Nonfinite results and excessively large serialized outputs are rejected.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Use a full SVG parser or rendering engine when the task includes commands and CSS values outside the documented branch. Compare coordinates and transforms under the same units and viewport convention.
References
Similar or alternative tools
- Polyline Dash Span Planner
Plan clipped one-dimensional dash spans for an explicit dash/gap cycle and phase; not a complete SVG stroking or corner renderer.
- Polyline Distance Point Lookup
Interpolate a point by Euclidean cumulative polyline distance without extrapolation; zero-length segments are skipped for interpolation.