Description
Return rfc7946CrsMemberAllowed false as a constant policy flag inside result.
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.
Return rfc7946CrsMemberAllowed false as a constant policy flag inside result.
When to use this tool
Use GeoJSON: Feature Crs Legacy Member Flag when you need a literal GeoJSON metadata, identifier, or shallow-key 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 result. Expand result to inspect the returned fields.
Require a Feature object and report whether it has an own crs member. Return rfc7946CrsMemberAllowed false as a constant policy flag inside result.1
RFC 7946 fixes coordinate semantics. Foreign metadata cannot restore the older alternate-CRS mechanism; the constant false flag expresses this tool policy.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| featureJson | Feature Json | Required. Text. Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| result | Object containing the calculated members; expand to inspect the fields below. | Required. Object. |
| result.legacyCrsPresent | Legacy Crs Present | Calculated result member: boolean. |
| result.rfc7946CrsMemberAllowed | Constant false policy flag, even when no crs member is present; foreign metadata cannot change coordinate semantics. | Calculated result member: boolean. |
{
"input": {
"featureJson": "{\"type\":\"Feature\",\"geometry\":null,\"properties\":{},\"crs\":null}"
},
"output": {
"result": {
"legacyCrsPresent": true,
"rfc7946CrsMemberAllowed": false
}
}
}Limitations and assumptions
- The constant is false even when crs is absent. The tool flags the legacy CRS mechanism; foreign metadata cannot change RFC 7946 coordinate semantics. It does not remove metadata, transform coordinates, or perform full validation.
- Outputs are nested inside result. 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.