Description
Compare the supplied member name exactly with type, coordinates, geometries, bbox, geometry, properties, and features; return whether it conflicts with this fixed list.
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.
Compare the supplied member name exactly with type, coordinates, geometries, bbox, geometry, properties, and features; return whether it conflicts with this fixed list.
When to use this tool
Use Geometry Foreign Member Name Conflict when you need a literal GeoJSON metadata, identifier, or shallow-key operation.
How to use the tool and how it works
- Enter name. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read reserved. Inspect reserved before interpreting the associated values.
Compare the supplied member name exactly with type, coordinates, geometries, bbox, geometry, properties, and features; return whether it conflicts with this fixed list.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| name | Name | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| reserved | Reserved | Required. Boolean. |
{
"input": {
"name": "coordinates"
},
"output": {
"reserved": true
}
} Limitations and assumptions
- Matching is case sensitive. The list does not contain id and is this tool's policy rather than a complete object-specific GeoJSON validity check.
- 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 Shallow Rename
Reject an occupied destination unless both names match, then rename a present own top-level member.
- Feature Foreign Member Count
Parse any plain JSON object and count own keys absent from the supplied member-name vocabulary.