Cross Type Variant Identifier (fitchy/patty etc.)
Resolve explicit named cross variants from independently verified drawing features. Exact source/edition/context reference lookup; caller independently verifies text, applicability and uncertainty. No invented current, normative or universal data.
Description
Cross variants are named through their shape and the adopted heraldic vocabulary.
Cross variants are named through their shape and the adopted heraldic vocabulary.1
A reference notice does not recognize a variant from a drawing. The tool retrieves your supplied source-specific notice for one exact key; it contains no built-in or live reference database.
When to use Cross Type Variant Identifier (fitchy/patty etc.)
Use this tool to calculate or review the supplied observations under the stated rules. Establish the source tradition, viewing frame, coordinate units and independently annotated features.
How to use Cross Type Variant Identifier (fitchy/patty etc.) and understand its results
- Establish the source tradition, viewing frame, coordinate units and independently annotated features.
- Enter callerVerifiedEditionContextKeys, callerVerifiedReferenceTexts, queryEditionContextKey, using the field meanings and rules below, then run the tool.
- Read result.matchedCallerReference, using the output meanings and calculation rules below. Confirm that the exact matched record is the one whose source and context apply.
- Correct any reported input issue and run again. Before using a successful result, check the stated units, signs, reference scope and observation coverage.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| callerVerifiedEditionContextKeys | Caller verified edition context keys | list of string | Required |
| callerVerifiedReferenceTexts | Caller verified reference texts | list of string | Required |
| queryEditionContextKey | Query edition context key; use the exact reference token or coordinate domain stated below | string | Required |
Supply nonempty aligned unique nonblank context keys and nonblank notices, then query one exact existing key. Matching is case-sensitive without trimming or normalization. Return its original notice unchanged; unknown keys fail. No data is fetched or independently verified.
notice=notices[indexOf(keys,exactQuery)] Use the matching field units and the exact boundary, ordering and reference rules above.
| Output field | Meaning | Value type |
|---|---|---|
| result | Calculated observation or reference | object |
| result.matchedCallerReference | matched Caller Reference | string |
{
"input": {
"callerVerifiedEditionContextKeys": [
"source-a/edition-a/context-a",
"source-b/edition-b/context-b"
],
"callerVerifiedReferenceTexts": [
"CrossVariant independently established source-a reference",
"CrossVariant independently established source-b reference"
],
"queryEditionContextKey": "source-a/edition-a/context-a"
},
"output": {
"result": {
"matchedCallerReference": "CrossVariant independently established source-a reference"
}
}
}Limitations and assumptions
The supplied annotations, measurements and source tradition determine applicability. The tool does not independently establish identity, provenance, entitlement or heraldic acceptability. Reference records and their claimed verification are supplied by the caller; the tool does not retrieve or verify them.
Missing required fields, unknown fields, wrong types and violated rules return input issues. Numeric values and outputs must be finite. Lists and matrices must be dense, without missing cells. Numeric lists allow at most 10000 entries; ordinary string lists allow at most 128 strings of 128 UTF-16 units each; numeric matrices allow at most 128 rows and 128 columns, subject to narrower requirements above. Extremely large composite outputs are rejected.
Alternative or Complementary methods
For a related step, use French-English Blazon Term Cross-Mapper: Heraldic term translation depends on the vocabulary and context of the reference being used. For a complementary comparison, use Saltire Diagonal Intersection Point Solver: A saltire-like crossing can be represented by two finite line segments.
References
Similar or alternative tools
- French-English Blazon Term Cross-Mapper
Heraldic term translation depends on the vocabulary and context of the reference being used.
- Saltire Diagonal Intersection Point Solver
A saltire-like crossing can be represented by two finite line segments.