Skip to content

Main content

Feature ID Number String Type Tag Tool

Calculate feature id number string type tag from explicit caller-supplied inputs.

Loading tool…

Description

Parse the supplied ID JSON value, label null explicitly and other values by JavaScript type, and accept only string or number identifiers.

Feature properties and foreign members are JSON metadata, distinct from the geometry coordinates. Exact key operations and ID type checks can preserve useful distinctions, but do not independently authenticate records or validate an entire Feature.

Parse the supplied ID JSON value, label null explicitly and other values by JavaScript type, and accept only string or number identifiers.

When to use this tool

Use Feature ID Number String Type Tag when you need a literal GeoJSON metadata, identifier, or shallow-key operation.

How to use the tool and how it works

  1. Enter idJson. 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 type, valid. Inspect valid before interpreting the associated values.

Parse the supplied ID JSON value, label null explicitly and other values by JavaScript type, and accept only string or number identifiers.1

Feature identifiers may be strings or numbers; accepted type does not establish uniqueness.2

Input fieldMeaning and unitsAccepted input
idJsonId JsonRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
typeLiteral type token or parsed-value classification under the stated vocabulary.Required. Text; maximum UTF-16 length 8192.
validWhether this specific check passes; not necessarily a full object-validity verdict.Required. Boolean.
json
{
  "input": {
    "idJson": "\"42\""
  },
  "output": {
    "type": "string",
    "valid": true
  }
}

Limitations and assumptions

  • Arrays receive the object type label. Parsing numeric JSON can lose precision before this test; the tool neither assigns IDs nor proves uniqueness.
  • 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.

Alternative or Complementary methods

Validate the complete Feature and its intended data model after editing. Preserve identifier precision and distinguish null values, absent members, collisions, and nested properties explicitly.

References

  1. Calculation and input contract: geojson/feature-id-number-string-type-tag — tool.io

  2. RFC 7946: Feature identifiers — IETF

Similar or alternative tools