Description
Construct a null-geometry GeoJSON Feature with an explicit null property or its omission.
GeoJSON separates a Feature’s identifier, geometry and properties. Null geometry, an explicit null property and an omitted property are distinct states. Coordinate-order labels do not transform positions, and stringifying a value already entered as a number cannot restore lost identifier precision or spelling.
Construct a null-geometry GeoJSON Feature with an explicit null property or its omission.
When to use this tool
Use Feature Null Property Preservation when checking the stated restricted GeoJSON construction, property or identifier convention.
How to use the tool and how it works
- Enter featureId, propertyName, preserveNull. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read featureJson. Use the output convention below.
Serialize a Feature with supplied ID, null geometry and either a propertyName:null entry when preserveNull=true or empty properties otherwise.1
A GeoJSON Feature can have null geometry. An explicitly null property value remains different from an omitted property.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| featureId | Feature Id | Required. Text; maximum UTF-16 length 8192. |
| propertyName | Property Name | Required. Text; minimum UTF-16 length 0; maximum UTF-16 length 8192. |
| preserveNull | True creates an explicit null property; false omits it. Geometry remains null in either case. | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| featureJson | Feature Json | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"featureId": "F17",
"propertyName": "note",
"preserveNull": true
},
"output": {
"featureJson": "{\"type\":\"Feature\",\"id\":\"F17\",\"geometry\":null,\"properties\":{\"note\":null}}"
}
}Limitations and assumptions
- A null geometry and an explicit null property have separate meanings; no coordinates, feature identity or property schema is verified.
- 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 against the intended GeoJSON contract and use verified longitude/latitude and datum conventions for actual geographic data exchange.
References
Similar or alternative tools
- Feature Property Null Removal Choice
Optionally remove top-level null entries from a JSON properties object.
- Feature Null Geometry Presence Tag Tool
Calculate feature null geometry presence tag from explicit caller-supplied inputs.