Description
Reject an occupied destination unless both names match, then rename a present own top-level member.
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.
Reject an occupied destination unless both names match, then rename a present own top-level member.
When to use this tool
Use Feature Foreign Member Shallow Rename when you need a literal GeoJSON metadata, identifier, or shallow-key operation.
How to use the tool and how it works
- Enter featureJson, from, to. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read featureJson, renamed. Inspect renamed before interpreting the associated values.
Require a Feature object and from/to names outside the fixed reserved set type, geometry, properties, id, bbox, features, coordinates, and geometries. Reject an occupied destination unless both names match, then rename a present own top-level member.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| featureJson | Feature Json | Required. Text; maximum UTF-16 length 8192. |
| from | From | Required. Text; maximum UTF-16 length 8192. |
| to | To | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| featureJson | Feature Json | Required. Text; maximum UTF-16 length 8192. |
| renamed | Renamed | Required. Boolean. |
{
"input": {
"featureJson": "{\"type\":\"Feature\",\"source\":\"survey\"}",
"from": "source",
"to": "provenance"
},
"output": {
"featureJson": "{\"type\":\"Feature\",\"provenance\":\"survey\"}",
"renamed": true
}
}Limitations and assumptions
- This shallow rename preserves member values but not JSON formatting. An occupied destination is rejected even when the source is absent; reserved-name policy alone does not establish full Feature validity.
- 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 Foreign Member Count
Parse any plain JSON object and count own keys absent from the supplied member-name vocabulary.
- GeoJSON: Feature Crs Legacy Member Flag
Return rfc7946CrsMemberAllowed false as a constant policy flag inside result.