Description
Require a Feature object, test own-member presence of geometry, and report separately whether the present member is JSON null.
GeoJSON distinguishes geometry objects, Features, FeatureCollections, and nullable Feature geometry. Type names and container structure identify these roles, but a recognized token or expected array member alone does not establish full validity.
Require a Feature object, test own-member presence of geometry, and report separately whether the present member is JSON null.
When to use this tool
Use Feature Null Geometry Presence Tag when you need one explicit GeoJSON object-shape or container operation.
How to use the tool and how it works
- Enter featureJson. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read present, nullGeometry. Inspect present, nullGeometry before interpreting the associated values.
Require a Feature object, test own-member presence of geometry, and report separately whether the present member is JSON null.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| featureJson | Feature Json | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| present | Present | Required. Boolean. |
| nullGeometry | Null Geometry | Required. Boolean. |
{
"input": {
"featureJson": "{\"type\":\"Feature\",\"geometry\":null}"
},
"output": {
"present": true,
"nullGeometry": true
}
} Limitations and assumptions
- The presence flag does not validate a non-null geometry value. Null geometry and an absent geometry member remain distinct even when both provide no coordinate data.
- 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
Use a full GeoJSON validator and any needed geometric validity checks for interchange. Preserve the distinction between absence, null, empty containers, recognized type, and valid coordinates.
References
Similar or alternative tools
- Geometry Null Versus Empty Label
Parse geometryJson as null or an object with one of the seven recognized geometry types.
- Feature Properties Absent Versus Null
Distinguish an absent properties member, JSON null, and a properties object; reject any other present value.