Skip to content

Main content

Linestring Coordinate One Insertion Count Tool

Calculate linestring coordinate one insertion count from explicit caller-supplied inputs.

Loading tool…

Description

Return count+1 and endpoint for insertion at zero or count.

A line's positions have an order, and endpoint or insertion rules depend on indexes in that order. Sequence length and index validity do not establish a geographic route, nondegenerate segments, or a valid complete geometry.

Return count+1 and endpoint for insertion at zero or count.

When to use this tool

Use Linestring Coordinate One Insertion Count when you need a local line-position or sequence-index operation.

How to use the tool and how it works

  1. Enter count, index. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read newCount, endpoint. Inspect endpoint before interpreting the associated values.

Require count at least two and insertion index from zero through count. Return count+1 and endpoint for insertion at zero or count.1

Input fieldMeaning and unitsAccepted input
countCount under the documented selection and duplicate convention.Required. Safe integer; minimum 2.
indexPosition under the documented indexing convention; inspect any absence sentinel.Required. Safe integer; minimum 0.
Output fieldInterpretationReturned shape
newCountNew CountRequired. Safe integer.
endpointEndpointRequired. Boolean.
json
{
  "input": {
    "count": 4,
    "index": 2
  },
  "output": {
    "newCount": 5,
    "endpoint": false
  }
}

Limitations and assumptions

  • Index equals count appends after the existing last entry; no actual coordinates are inserted and no line validity, location, or distinctness is assessed.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Validate the entire coordinate sequence and intended geometry after edits. Use a routing or geodesic method for questions about actual travel paths or physical distances.

References

  1. Calculation and input contract: geojson/linestring-coordinate-one-insertion-count — tool.io

Similar or alternative tools