Description
Build a Point Feature with one property under the literal key and serialize featureJson.
Geometry and feature wrappers change the container around existing coordinate or object content. A newly constructed wrapper can have the intended outer shape while still containing coordinates or members that need separate validation.
Build a Point Feature with one property under the literal key and serialize featureJson.
When to use this tool
Use Point Feature Single Property Wrapper when you need a specified single-item GeoJSON container transformation.
How to use the tool and how it works
- Enter position, key, valueJson. 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.
Require position with at least two entries and parse valueJson as a portable JSON value. Build a Point Feature with one property under the literal key and serialize featureJson.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| position | Position | Required. Array of finite number; maximum items 256. |
| key | Key | Required. Text; maximum UTF-16 length 8192. |
| valueJson | Value Json | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| featureJson | Feature Json | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"position": [
1,
2
],
"key": "name",
"valueJson": "\"Park\""
},
"output": {
"featureJson": "{\"type\":\"Feature\",\"geometry\":{\"type\":\"Point\",\"coordinates\":[1,2]},\"properties\":{\"name\":\"Park\"}}"
}
}Limitations and assumptions
- The key is not interpreted as a path and coordinate bounds and dimensions beyond the minimum are not validated; no property schema, actual location, or complete GeoJSON validity is established.
- 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.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Run complete schema and geometry validation on the resulting object. Preserve and review any required foreign metadata or bounding box deliberately rather than assuming every wrapper copies it.
References
Similar or alternative tools
- Multi Point Single Position Wrapper
Require position with at least two entries and serialize a MultiPoint with that position as its sole coordinate entry.
- Feature Collection Single Feature Wrapper
Wrap the whole object as the only feature in a newly serialized FeatureCollection.