Ticket to Ride Route Length Points

Base Ticket to Ride route-length score schedule for lengths 1–6; expansions/variant bonuses excluded.

Description

Ticket to Ride Route Length Points: look up a supported built-in reference entry.

Route scoring uses a ruleset-specific relationship between route length and awarded points. This lookup contains the common supported lengths one through six.

This tool returns a built-in reference entry for an exact supported selector. The supported entries and their scope are part of the tool; no website or current external table is queried.

When to use this tool

Use this tool when the supplied inputs match the specific operation described above and you need a repeatable result under its stated convention.

  • Check the supported input and output contract against an existing calculation or observation.
  • Use the complete example to confirm units, selector spelling and result interpretation.

How to use the tool and how it works

  1. Enter every field in the input table using the stated units and the exact supported selector spelling where applicable.
  2. Run the tool. Correct input errors before interpreting an output.
  3. Read the result fields below; use accompanying flags and the stated sign, boundary or model convention when interpreting a number.

Look up the string routeLength in the stored table: 1, 2, 3, 4, 5 and 6 map to 1, 2, 4, 7, 10 and 15 points.1

Input fieldMeaning and unitsAccepted input
routeLengthRoute length.Exact value: "1", "2", "3", "4", "5", "6"
routeLengthBuilt-in entry
"1"1
"2"2
"3"4
"4"7
"5"10
"6"15
Output fieldInterpretation
resultObject containing the following named result fields.
result.referenceThe stored entry for the exact selected key; its type may be text, a number or a list.
json
{
  "input": {
    "routeLength": "4"
  },
  "output": {
    "result": {
      "reference": 7
    }
  }
}

Limitations and assumptions

  • Other lengths, expansions and scoring variants are outside the table.
  • Every declared field is required and unexpected fields are rejected. Numeric inputs must be finite; input errors are distinct from a valid false result or an explicitly qualified output.
  • Extremely large inputs and nonfinite or excessively large outputs are rejected. List positions reported by the tool use zero-based indices unless stated otherwise.

Alternative or Complementary methods

Check the underlying observations, units and conventions independently before using the result in a larger workflow. The tools listed below address nearby tasks; compare their inputs and scope before substituting one for this operation.

References

  1. Tool behavior and example: Ticket to Ride Route Length Points — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies