Passage Name Uniqueness Prefix Checker

Exact case-sensitive passage-name collision versus actual inventory with explicit section prefix. Does not reserve identity, infer fuzzy equivalence or validate nomenclature authority.

Description

Passage names can collide within an adopted survey inventory.

Passage names can collide within an adopted survey inventory.^[1]

A section-prefixed identity and an exact unprefixed name comparison serve different naming purposes.

When to use Passage Name Uniqueness Prefix Checker

Use this tool to obtain normalizedCandidateIdentity, exactNameAlreadyPresent 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 Passage Name Uniqueness Prefix Checker and understand its results

Establish the survey or observation scope, reference frame, units and independently applicable calibration or qualified plan.
Enter actualExistingPassageNames, proposedPassageName, proposedSectionPrefix, using the field meanings and rules below, then run the tool.
Read result.normalizedCandidateIdentity, result.exactNameAlreadyPresent. 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
actualExistingPassageNames	Actual existing passage names	list of string	Required
proposedPassageName	Proposed passage name	string	Required
proposedSectionPrefix	Proposed section prefix	string	Required

Require a nonempty unique nonblank existing-name inventory and nonblank proposed name/prefix without forward slashes. Trim only the proposed name and prefix, join them with a slash for the candidate identity, and compare the trimmed proposed name with existing names exactly. The collision check ignores the prefix and does not normalize stored names; it does not reserve the proposed identity.

candidate=trim(prefix)+"/"+trim(name); alreadyPresent=existingNames.includes(trim(name))

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.normalizedCandidateIdentity	Trimmed proposed prefix joined to trimmed proposed name with a forward slash.	string
result.exactNameAlreadyPresent	True when the trimmed proposed unprefixed name exactly matches a stored name.	boolean

json

{
  "input": {
    "actualExistingPassageNames": [
      "North",
      "South"
    ],
    "proposedPassageName": "West",
    "proposedSectionPrefix": "CaveA"
  },
  "output": {
    "result": {
      "normalizedCandidateIdentity": "CaveA/West",
      "exactNameAlreadyPresent": false
    }
  }
}

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. Lists and matrices must be dense, without missing cells. String lists allow at most 128 entries of at most 128 UTF-16 units each; blank and duplicate rules are stated above. Extremely large composite outputs are rejected.

Alternative or Complementary methods

For a related step, use Cave Designation Numbering Scheme Validator: A cave designation scheme can specify an ASCII region prefix and a fixed digit width. 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

Passage Name Uniqueness Prefix Checker — tool.io

Similar or alternative tools

Cave Designation Numbering Scheme Validator
A cave designation scheme can specify an ASCII region prefix and a fixed digit width.
Shot Data Unit Consistency Checker
A survey record's distance and angle tags declare how its numbers are interpreted.