Description
Parse a properties object, test whether key exists as an own member, remove that exact top-level key if present, and serialize the remaining entries.
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, test whether key exists as an own member, remove that exact top-level key if present, and serialize the remaining entries.
When to use this tool
Use Feature Properties Single Key Removal when you need a literal GeoJSON metadata, identifier, or shallow-key operation.
How to use the tool and how it works
- Enter propertiesJson, key. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read propertiesJson, removed. Inspect removed before interpreting the associated values.
Parse a properties object, test whether key exists as an own member, remove that exact top-level key if present, and serialize the remaining entries.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| propertiesJson | Properties Json | Required. Text; maximum UTF-16 length 8192. |
| key | Key | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| propertiesJson | Properties Json | Required. Text; maximum UTF-16 length 8192. |
| removed | Removed | Required. Boolean. |
{
"input": {
"propertiesJson": "{\"a\":1,\"b\":2}",
"key": "a"
},
"output": {
"propertiesJson": "{\"b\":2}",
"removed": true
}
}Limitations and assumptions
- An absent key produces removed false. This is shallow deletion and does not preserve whitespace, key formatting, or original JSON bytes.
- 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
Similar or alternative tools
- Feature Properties Absent Versus Null
Distinguish an absent properties member, JSON null, and a properties object; reject any other present value.
- Feature Property Key Collision Policy
Parse properties as an object and require oldKey to exist as an own key.