Skip to content

Main content

Feature Property JSON Null Replacement Tool

Calculate feature property json null replacement from explicit caller-supplied inputs.

Loading tool…

Description

Parse a properties object, record whether key exists as an own member, remove its old entry if present, and append the key with JSON null before serializing.

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 a properties object, record whether key exists as an own member, remove its old entry if present, and append the key with JSON null before serializing.

When to use this tool

Use Feature Property JSON Null Replacement when you need a literal GeoJSON metadata, identifier, or shallow-key operation.

How to use the tool and how it works

  1. Enter propertiesJson, key. 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 propertiesJson, existed. Inspect existed before interpreting the associated values.

Parse a properties object, record whether key exists as an own member, remove its old entry if present, and append the key with JSON null before serializing.1

Input fieldMeaning and unitsAccepted input
propertiesJsonProperties JsonRequired. Text; maximum UTF-16 length 8192.
keyKeyRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
propertiesJsonProperties JsonRequired. Text; maximum UTF-16 length 8192.
existedExistedRequired. Boolean.
json
{
  "input": {
    "propertiesJson": "{\"a\":1,\"b\":2}",
    "key": "a"
  },
  "output": {
    "propertiesJson": "{\"b\":2,\"a\":null}",
    "existed": true
  }
}

Limitations and assumptions

  • Null replaces the value rather than deleting the property. An absent key is added, nested values are untouched, and original byte formatting is not preserved.
  • 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-property-json-null-replacement — tool.io

Similar or alternative tools