Cave Designation Numbering Scheme Validator
Actual cave designation syntax callerPREFIX-hyphen-exact ASCII digit width. No numbering allocation, registry authority, uniqueness or universal regional naming scheme.
Description
A cave designation scheme can specify an ASCII region prefix and a fixed digit width.
A cave designation scheme can specify an ASCII region prefix and a fixed digit width.1
Matching that syntax does not reserve a designation or verify registry membership.
When to use Cave Designation Numbering Scheme Validator
Use this tool to obtain matchesCallerScheme from the supplied records using the stated calculation. Establish the survey or observation scope, reference frame, units and independently applicable calibration or qualified plan.
How to use Cave Designation Numbering Scheme Validator and understand its results
- Establish the survey or observation scope, reference frame, units and independently applicable calibration or qualified plan.
- Enter actualDesignation, callerRegionPrefix, callerRequiredDigitWidth, using the field meanings and rules below, then run the tool.
- Read result.matchesCallerScheme. Use the units and sign conventions below, and review any unknown records separately.
- 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 |
|---|---|---|---|
| actualDesignation | Actual designation | string | Required |
| callerRegionPrefix | Caller region prefix | string | Required |
| callerRequiredDigitWidth | Caller required digit width | number | Required |
Require an ASCII alphanumeric region prefix of one through 32 characters and an integer digit width of one through twenty. Test the exact designation against prefix, one hyphen and exactly that many ASCII digits. No trimming or case normalization is applied. A nonmatching designation returns false rather than an input error; malformed scheme parameters fail.
matches=exactPrefix+"-"+exactlyDigitWidthAsciiDigits Use the matching field units and the exact boundary, ordering and reference rules above.
| Output field | Meaning | Value type |
|---|---|---|
| result | Qualified observed calculation or explicit reference | object |
| result.matchesCallerScheme | True for the exact prefix-hyphen-digit-width designation scheme; false for a nonmatching designation. | boolean |
{
"input": {
"actualDesignation": "REG-012",
"callerRegionPrefix": "REG",
"callerRequiredDigitWidth": 3
},
"output": {
"result": {
"matchesCallerScheme": true
}
}
}Limitations and assumptions
The actual observation coverage, calibration and qualified plan determine applicability. A numerical result does not establish survey accuracy, route suitability, atmosphere conditions or equipment adequacy beyond the declared comparison.
Missing required fields, unknown fields, wrong types and violated rules return input issues. Numeric values and outputs must be finite. Extremely large composite outputs are rejected.
Alternative or Complementary methods
For a related step, use Passage Name Uniqueness Prefix Checker: Passage names can collide within an adopted survey inventory. For a complementary comparison, use Shot Data Unit Consistency Checker: A survey record's distance and angle tags declare how its numbers are interpreted.
References
Similar or alternative tools
- Passage Name Uniqueness Prefix Checker
Passage names can collide within an adopted survey inventory.
- Shot Data Unit Consistency Checker
A survey record's distance and angle tags declare how its numbers are interpreted.