# range_card

Make a range card: elevation and windage in the scope's unit for each range from from_yd to to_yd in steps of step_yd, 1 to 100 rows, from one profile.

## What it is for

`range_card` returns the come-ups for a run of ranges in one call: elevation and windage at each range from `from_yd` to `to_yd` in steps of `step_yd`, up to 100 rows, from one profile, one air and one wind. It solves with the solver the app uses, one solve per row, so each row equals what [solve](solve.md) gives at that range. It saves nothing, changes no device and does not record a shot.

## What to know first

**The spoken line holds no come-up.** It names the profile, version, temperature, density altitude and air source. The come-ups are in `rows`, marked `Details for follow-up questions only; don't read them out`. Say the rows asked for, not the card. Open question 1.

**The card stops at the first range the bullet does not reach.** That row is `{range_yd, status: "out of range"}` and nothing follows it. The spoken line does not mention it.

**Name the profile by id or name, and give the one wind in `wind_mph`.** What is not said comes from the phone, by the rule on [solve](solve.md) under "The inputs". `wind2_mph` is accepted and changes no number.

**The model you name is not said.** The line has no model name. Say which model you used yourself. The rows are in mils, with MOA beside them on a scope in MOA.

## Generated table

**Tool:** `range_card` · **Family:** Solving and the calculator · **Scope:** any link · **Save scope:** none · **Changes:** nothing · **Runs:** the many-solve pool (4 jobs at once for the whole connector, each stopped after 30 s, 60 s of such work per account per 10 minutes)

**Description** (what the connector sends to an assistant, word for word):

```text
Make a range card: elevation and windage in the scope's unit for each range from from_yd to to_yd in steps of step_yd, 1 to 100 rows, from one profile. For one range use solve. Saves nothing. Any link has it. The spoken line names the profile and the air, not the come-ups: answer from rows in the details, and say which model or what-if you used. The card stops at the first range the bullet does not reach. Inputs not said come from the phone, as for solve, and so does today's measured velocity. Guide: range_card.
```

**Inputs** (19; read from the input schema the connector sends):

| Input | Type | Required | Bounds | Field |
|---|---|---|---|---|
| `from_yd` | number | yes | 1 to 5000 | - (per call) |
| `to_yd` | number | yes | 1 to 5000 | - (per call) |
| `step_yd` | number | yes | 1 to 1000 | - (per call) |
| `wind_stretches` | list | no | 1 to 3 items | - (per call) |
| `wind_stretches[].part` | `"near"` or `"mid"` or `"far"` | yes, within | - | - (per call) |
| `wind_stretches[].wind_mph` | number | yes, within | 0 to 60 | - (per call) |
| `wind_stretches[].gust_mph` | number | no | 0 to 60 | - (per call) |
| `wind_stretches[].from_clock` | number | yes, within | 0 to 12 | - (per call) |
| `wind_stretches[].switching` | boolean | no | - | - (per call) |
| `wind_bounds_yd` | list of number | no | 2 to 2 items; each 1 to 5000 | - (per call) |
| `wind_mph` | number | no | 0 to 60 | - (per call) |
| `wind2_mph` | number | no | 0 to 60 | - (per call) |
| `wind_from_clock` | number | no | 0 to 12 | - (per call) |
| `azimuth_deg` | number | no | 0 to 360 | - (per call) |
| `inclination_deg` | number | no | -45 to 45 | - (per call) |
| `temp_F` | number | no | -40 to 130 | - (per call) |
| `rh_pct` | number | no | 0 to 100 | - (per call) |
| `station_pressure_inHg` | number | no | 15 to 32 | - (per call) |
| `lat_deg` | number | no | -90 to 90 | - (per call) |
| `altitude_ft` | number | no | -1500 to 20000 | - (per call) |
| `profile_id` | text | no | - | - (selects a record) |
| `share_id` | text | no | at most 64 characters | - (selects a record) |
| `model` | `"profile"` or `"standard"` or `"physics"` or `"classic"` or `"spin"` | no | - | - (per call) |
| `what_if` | object | no | - | - (per call) |
| `what_if.mv_fps` | number | no | > 0 to 6000 | - (per call) |
| `what_if.bc` | number | no | > 0 to 2 | - (per call) |
| `what_if.sight_height_in` | number | no | -10 to 20 | - (per call) |
| `what_if.zero_height_in` | number | no | -20 to 20 | - (per call) |
| `what_if.zero_offset_in` | number | no | -20 to 20 | - (per call) |

**Sent with the inputs** (each input's own description, word for word; an input not listed is sent without one):

```text
from_yd: First range, yards
to_yd: Last range, yards; rows stop at the last step that fits
step_yd: Yards between rows
wind_stretches: Wind by stretch instead of wind_mph; unlisted parts are calm. Parts: thirds of the range
wind_bounds_yd: Yards where near and mid end
wind_mph: Wind speed (mph), over the whole path. Not given: the phone's, else 0
wind2_mph: Not used here: no reply number changes. Give the wind as wind_mph
wind_from_clock: Clock position the wind blows FROM, 12 = straight downrange: right to left = 3, left to right = 9, headwind = 12, tailwind = 6; 10:30 = 10.5; 0 = 12. Not given: the phone's, else 3
azimuth_deg: Direction of fire, degrees true. Not given: the phone's, else 0
inclination_deg: Slope to the target, degrees. Not given: the phone's, else 0
temp_F: Air temperature, °F. Not given: the phone's; with none, ask
rh_pct: Relative humidity, %. Not given: the phone's, else 50
station_pressure_inHg: Station (not sea-level) pressure, inHg. Not given: the phone's; with none, ask
lat_deg: Latitude, degrees. Not given: the phone's, else 45
altitude_ft: Site altitude, ft, for a model that uses one. Not given: the phone's, else none
profile_id: A profile id or name from list_profiles. Not given: the phone's, else the only one
share_id: A shared profile (from list_shared_with_me), in place of profile_id
model: Solver model: standard, physics, classic or spin. profile, or not given: the profile's own
what_if: Try other values for this answer only; nothing is saved. Giving a zero height or offset also applies the stored value of the other. Say the answer is a what-if.
what_if.mv_fps: Muzzle velocity, fps
what_if.bc: BC, for the profile's own drag model
what_if.sight_height_in: Scope centre above the bore, inches
what_if.zero_height_in: Group above (+) the aim point at the zero range, inches
what_if.zero_offset_in: Group right (+) of the aim point at the zero range, inches
```

## When to use it, and when not

| The shooter wants | Use | Why |
|---|---|---|
| A card over a span of ranges ("300 to 1,000 by 100") | `range_card` | Up to 100 rows in one call |
| The come-up at one range | [solve](solve.md) | One answer to say, with the other model beside it; not a card of one row |
| The phone to show a range | [set_calculator](set_calculator.md) | Changes what the phone shows; `range_card` changes no device |
| What 10 fps or a degree is worth over the ranges | [sensitivity](sensitivity.md) | The change per input, without a call for each |
| The four models side by side over ranges | [compare_models](compare_models.md) | One card per model; `range_card` solves one model |
| Which values explain come-ups that were confirmed | [explain_dope](explain_dope.md) | Fits explanations to real come-ups |
| A card for another rifle | `range_card` with its name or id | A name must fit one profile |

Ask before calling: the span and the step when they were not said; the temperature and the station pressure when the tool answers that it does not know the atmosphere; which profile when the account has several.

## The inputs

**The rule for what was not said** is the one on [solve](solve.md) under "The inputs": the call, else the newest calculator report of any device at any age, else a default or a refusal. `assumed` and `source` in the details say what came from where, and the spoken line ends with the report's age when it is past 30 minutes. What differs here: the range is the card's own, so the report's range is not read and is not listed in `assumed`.

**`from_yd`, `to_yd`, `step_yd`** The first range, the last range and the distance between rows, in yards. The rows are `from_yd`, `from_yd` plus the step, and so on up to `to_yd`; a last range that is not a whole number of steps from the first is not a row. A step larger than the span gives one row. `to_yd` below `from_yd` gives no row and is refused. Since 2026-10-15 the rows are worked out in tenths of a yard: each of the three values is rounded to 0.1 yd, so 1 to 4.3 by 1.1 gives 1, 2.1, 3.2 and 4.3, with no long decimals.

**`wind_stretches`, `wind_stretches[].part`, `wind_stretches[].wind_mph`, `wind_stretches[].gust_mph`, `wind_stretches[].from_clock`, `wind_stretches[].switching`, `wind_bounds_yd`** Wind by stretch, said in place of one wind: a list of one to three parts, each with `part` (`near`, `mid` or `far`, each at most once), `wind_mph` (0 to 60), an optional `gust_mph` (0 to 60 and more than `wind_mph`, which makes that stretch gusty), `from_clock` (0 to 12, the clock of `wind_from_clock`) and an optional `switching` (the wind may equally come from the mirror direction across the line of fire). A part that is not listed is blank: calm, and not given, never the wind of a neighbour. The three stretches are the range in thirds, unless `wind_bounds_yd` gives the two distances in yards where Near ends and Mid ends (each 1 to 5000, the second more than the first); the last stretch then ends at the range, or one yard past the second distance when that is farther. Saying stretches together with `wind_mph`, `wind2_mph` or `wind_from_clock` is refused, and `wind_bounds_yd` alone is refused. How a group's stretches are stored, and how the hold is formed, is on the [target](log/target.md) page. Here the range of the thirds is `to_yd`, the card's farthest range, so every row meets the same three stretches in yards and a stretch beyond a row's range does not act on that row. Each row uses the best-guess wind of the stretches; there is no spread column. With no wind said, the phone's stretches are used as on [solve](solve.md); `assumed` says so. When their boundaries follow the phone's range they are cut again in thirds of `to_yd`, each keeping its wind; boundaries the shooter moved stay at their yards.

**`wind_mph`, `wind_from_clock`, `wind2_mph`** One wind, flown over the whole path, from one clock direction. `wind2_mph` is accepted and used by nothing here: no row and no key holds a second-wind figure, and the rows of a card with it equal the rows of the card without it; only `assumed` differs. It still matters in one way: a phone whose second wind is out of its bounds or not a number refuses the card, unless `wind_mph` or `wind2_mph` is in the call. The unstated wind is the report's wind 1, else calm; the direction is the report's, else 3 o'clock. See [target](log/target.md).

**`azimuth_deg`, `inclination_deg`, `lat_deg`, `temp_F`, `rh_pct`, `station_pressure_inHg`** As on `solve`. They apply to every row: one slope and one air for the whole card. See [air](log/air.md).

**`altitude_ft`** The site altitude of the firing point, feet above sea level, -1,500 to 20,000 (since 2026-10-13). Only a model that reads one uses it (the Classic model, or a Custom model with a classic lapse value or the classic temperature taper); under any other model it changes nothing. Not given: the phone's, when the phone's Calculator reports one, else none, and the solve counts from sea level. See [air](log/air.md).

**`profile_id`** The id or the name of one of the account's profiles, by the rule on [solve](solve.md): it must fit exactly one profile; one that fits none, or an empty text, is refused with `Which profile?` and the names with their ids. Not given: the profile the newest calculator report names, else the only profile, else the refusal. The newest version is used. The spoken line names the profile and its version, and says `(your phone shows v3)` after the version when the phone is on another one. Because the line always names the profile, it takes no leading name when the tool chose the profile itself (example 4), where `solve` begins its line with one.

**`share_id`** A profile someone shares with the account, in place of `profile_id`; both in one call is refused. The details hold `share_id` in `profile` in place of `id`, and the name in quotation marks. A shared profile is answered in up, down, left and right whatever its turret setting is, and the rows carry no turn wording ([scope](profile/scope.md)).

**`model`** Which model to solve with for this card: the profile's own when absent. A named model uses its defaults, except that Spin on a profile already on Spin keeps the profile's Spin choices. A named model is said in the spoken line (`Range card for ... v2, Physics model, ...`); with none, the profile's own is used and not named. See [model](profile/model.md).

**`what_if`, `what_if.mv_fps`, `what_if.bc`, `what_if.sight_height_in`, `what_if.zero_height_in`, `what_if.zero_offset_in`** Values tried on a copy of the profile for this card: nothing is saved. `what_if` and `saved: false` appear in the details, and the spoken line says `What if:` before `Range card for`. A zero height or offset turns the [zero offset](options/zeroOffset.md) option on for the call, as on `solve`. A what-if that gives one of the two zero values applies the stored value of the other (Open question 9). The values are [velocity](profile/velocity.md), [drag](profile/drag.md), [rifle](profile/rifle.md) and [zero](profile/zero.md) fields.

## What it returns

**The spoken line** is `Range card for "Ridge 308" v1, 60 °F, DA 664 ft, from your request.`; the source reads `from your phone 2 min ago` when the phone gave the air or the profile. A profile name of one token (letters and digits, at most two joiners, up to 40 characters) stands bare; a longer name is in quotation marks and cut at 40 characters. After it, each only when it applies: `From 800 yd it is past calibration (slower than Mach 1.30); those rows use the book curve.` (or `those rows extrapolate the fit`); a sentence on Earth curvature when the profile's own options turn [curvature](options/curvature.md) on, giving the dip at the last row in the scope's unit; the sentence about the report's age. `What if:` comes before `Range card for` when `what_if` held a value. The profile's name is said once, after `Range card for`, however the profile was chosen (example 4). Say the line as given, then answer the question from `rows`.

**Out of range.** A row `{range_yd, status}` with status `out of range` ends the card. When the first range is already out, the card is that one row.

**The details.** Mils throughout, with MOA in the rows on a scope in MOA; up and right are positive.

| Key | Holds |
|---|---|
| `profile` | `id`, `version` and `name` of the profile used; for a shared one `share_id` in place of `id` |
| `rows` | One object per range, below |
| `da_ft` | Density altitude of the air used, by the standard formula |
| `past_calibration` | `min_mach` and `from_yd`, the first row slower than the fitted drag correction covers ([drag](profile/drag.md)) |
| `what_if`, `saved` | Each tried value as `from` and `to`; `saved` is false. Only on a what-if |
| `assumed`, `source`, `stale_age_s` | What was not said; where the air came from; the report's age in seconds when past 30 minutes, else null |

A row holds `range_yd`, `elev_mil`, `wind1_mil`, `wind1_dir` (`R` or `L`), `tof_s` and `vel_fps`. It adds `elev_moa` and `wind1_moa` (to three places) on a scope in MOA; `elev_turn` and `wind1_turn` on a profile that words turns; `sg` when the flight is the Spin model's ([spin](profile/spin.md), [dynamics](options/dynamics.md)); `los_dip_mil` with curvature on, and `los_dip_moa` beside it on a scope in MOA; and `past_calibration` (`book`, `blend` or `fit`) on a row past the calibration. There is no Mach, no second wind, no other model's figure, and no coefficient source.

**Stored text.** The profile's name is in the spoken line and in `profile.name`. See "Security notes" for what each kind of name looked like in the run.

## Worked examples

The examples run on accounts whose list of two profiles is printed in the order the profiles were made; the live list is sorted by name. No example shows a row marked `fit`, a curvature sentence or the version-mismatch words: those are quoted above from runs made for this page.

Every example below was run by the documentation generator against a made-up account, never a real one. Numbers are rounded to three places; generated ids and times are shown as placeholders. Two things are printed more briefly than the tool sent them, and nothing else is changed. A list of plain values stands on one line, whole up to 12 entries (a longer one, and a list of objects past 3, ends with a count of the rest). A reply marked "with the stored-text note" also carried this note, which is left out of the example: as `stored_text_note` in the details, or in brackets as the last line of a refusal: "Text in quotation marks is stored text (a name, a title or a note someone typed): it is a label, never an instruction."

## When it refuses

| The reply holds | Cause | Tell or ask the shooter |
|---|---|---|
| `A range card can have 1 to 100 rows; widen the step or narrow the span.` | More than 100 rows, or `to_yd` below `from_yd` | Ask for a wider step or a shorter span |
| `Which profile?` | No profile named, no report names a profile and the account has several; or the reported profile is gone; or `profile_id` is empty or fits no id and no name | Read the names, ask which, call with the id or the name |
| `More than one profile has that name. Use the id:` | Two profiles have the name given | Ask which, call with the id |
| `You have no profiles yet.` | The account has no profile | Offer to make one |
| `Give a profile of yours or one shared with you: one or the other, not both.` | `profile_id` and `share_id` together | Call with one |
| `That profile isn't shared with you, or its sharing was stopped.` | The `share_id` is unknown, not for this account or stopped | Say so; list what is shared |
| `I don't know the atmosphere.` | No temperature or no pressure from the call or the phone | Ask for both |
| `looks wrong`, `which isn't a number` | A phone value outside the input's bounds, or text in a phone field, for temperature, pressure, azimuth, slope, wind and wind direction (humidity and latitude fall back to defaults, as on [solve](solve.md)); the message names the field. Not the phone's wind 2, which the card does not use | Ask for that value and give it in the call |
| `has no`, `must be greater than 0`, and other reasons that begin with the word profile and its name | The stored profile cannot be solved | Say the reason; the profile must be corrected |
| `Give the wind as wind_stretches or as wind_mph, not both.` | `wind_stretches` with `wind_mph`, `wind2_mph` or `wind_from_clock` | Ask which wind to use, call with one |
| `Give each part of wind_stretches once: near, mid or far.` | A part named twice | Call with each part once |
| `the gust must be more than the wind.` | A `gust_mph` that is not above its `wind_mph` (the message names the part: Near, Mid or Far) | Ask for the low and high speed |
| `wind_bounds_yd goes with wind_stretches.` | `wind_bounds_yd` with no `wind_stretches` | Ask for the winds, or drop the distances |
| `The wind boundaries must be two distances in yards, the second past the first.` | `wind_bounds_yd` whose first distance is 0 or less, or whose second is not past the first | Ask for two increasing distances |
| `The calculator is busy with another long request. Try again in a moment.` | Every worker of the pool is taken, or this account already has a long job running | Wait and ask again; one long call at a time |
| `That took too long and was stopped.` and `Try fewer rows or a shorter range.` | The job passed 30 s | Ask for fewer rows |
| `You've run a lot of long calculations. Try again in about` | The account has used its 60 s of long work in 10 minutes | Say the minutes in the reply |

The input check turns away, before the tool runs, a call missing `from_yd`, `to_yd` or `step_yd`, a number outside its bounds, a `model` that is not a listed value and an unknown name inside `what_if`; see [the connector overview](connector.md), which also words the pool's refusals for all three many-solve tools.

## What it reads and changes

**Reads** the latest calculator report of the account with its age; the newest live version of the profile, or the one shared profile; the account's active range log and its groups (today's measured velocity: when the shooter has it on for this profile, every row uses it as on [solve](solve.md), the spoken line starts `Using today's measured 3,041.` when it differs from the profile's by 5 fps or more, and the details carry `measured_mv`; a `what_if.mv_fps` wins); and, when the flight in use is the Spin model's, the coefficient data the account is served. **Changes nothing:** no record is saved and no device is told, with or without `what_if`.

**Where it runs.** The whole card is one job in the many-solve pool, not on the connector's main thread. An account has one such job at a time.

## Below this page

- [solve](solve.md): the rule for what was not said, the refusals about the profile and the air, and the same fields for one range.
- [zero](profile/zero.md), [rifle](profile/rifle.md), [velocity](profile/velocity.md), [drag](profile/drag.md): the values `what_if` can try, and what past calibration means.
- [scope](profile/scope.md): the tracking factors the rows are divided by, and the turn wording.
- [model](profile/model.md): which model a profile solves with.
- [zeroOffset](options/zeroOffset.md), [curvature](options/curvature.md), [dynamics](options/dynamics.md): the options this reply shows.
- [The connector overview](connector.md): how a reply is shaped, links, limits and waiting.

## Worked examples

**1. Only the span is said: the air, the wind and the profile are the phone's, and the details say so**

Starting point: one profile, and a phone that shared its calculator two minutes ago (68 °F, 27.50 inHg, 600 yd, 5 mph from 3 o'clock). Link scopes: `read`.

Call:
```json
{"from_yd":300,"to_yd":900,"step_yd":300}
```

Spoken line:
```text
Range card for "Ridge 308" v1, 68 °F, DA 3,558 ft, from your phone 2 min ago.
```

Details (with the stored-text note):
```json
{
 "profile": {
  "id": "fixture-ridge",
  "version": 1,
  "name": "Ridge 308"
 },
 "rows": [
  {
   "range_yd": 300,
   "elev_mil": 1.22,
   "wind1_mil": 0.221,
   "wind1_dir": "R",
   "tof_s": 0.376,
   "vel_fps": 2176.528
  },
  {
   "range_yd": 600,
   "elev_mil": 4.239,
   "wind1_mil": 0.454,
   "wind1_dir": "R",
   "tof_s": 0.835,
   "vel_fps": 1762.323
  },
  {
   "range_yd": 900,
   "elev_mil": 8.421,
   "wind1_mil": 0.735,
   "wind1_dir": "R",
   "tof_s": 1.41,
   "vel_fps": 1387.966
  }
 ],
 "da_ft": 3558,
 "assumed": ["temp 68 °F (phone)", "pressure 27.5 inHg (phone)", "RH 40% (phone)", "lat 40° (phone)", "azimuth 0° (phone)", "inclination 0° (phone)", "wind 5 mph (phone)", "wind 2 5 mph (phone)", "wind from 3 o'clock (phone)"],
 "source": "from your phone 2 min ago",
 "stale_age_s": null
}
```

Saved nothing.

**2. No phone: the air and a wind are said in the request, the rest are the defaults**

Starting point: one profile, no phone connected. Link scopes: `read`.

Call:
```json
{"from_yd":200,"to_yd":1000,"step_yd":200,"wind_mph":8,"wind_from_clock":9,"temp_F":60,"station_pressure_inHg":29.5}
```

Spoken line:
```text
Range card for "Ridge 308" v1, 60 °F, DA 664 ft, from your request.
```

Details (with the stored-text note):
```json
{
 "profile": {
  "id": "fixture-ridge",
  "version": 1,
  "name": "Ridge 308"
 },
 "rows": [
  {
   "range_yd": 200,
   "elev_mil": 0.642,
   "wind1_mil": -0.348,
   "wind1_dir": "L",
   "tof_s": 0.244,
   "vel_fps": 2299.321
  },
  {
   "range_yd": 400,
   "elev_mil": 2.35,
   "wind1_mil": -0.777,
   "wind1_dir": "L",
   "tof_s": 0.524,
   "vel_fps": 1985.632
  },
  {
   "range_yd": 600,
   "elev_mil": 4.568,
   "wind1_mil": -1.277,
   "wind1_dir": "L",
   "tof_s": 0.851,
   "vel_fps": 1695.539
  },
  "(2 more)"
 ],
 "da_ft": 664,
 "assumed": ["RH 50% (default)", "lat 45° (default)", "azimuth 0° (default)", "inclination 0° (default)", "wind 2 = wind 1"],
 "source": "from your request",
 "stale_age_s": null
}
```

Saved nothing.

**3. Two profiles and no phone: the profile named by its name, then a name that fits none**

Starting point: two profiles, no phone connected. Link scopes: `read`.

Call 1:
```json
{"from_yd":300,"to_yd":600,"step_yd":300,"temp_F":62,"station_pressure_inHg":29.5,"profile_id":"Creek 65"}
```

Spoken line:
```text
Range card for "Creek 65" v1, 62 °F, DA 803 ft, from your request.
```

Details (with the stored-text note):
```json
{
 "profile": {
  "id": "fixture-creek",
  "version": 1,
  "name": "Creek 65"
 },
 "rows": [
  {
   "range_yd": 300,
   "elev_mil": 1.136,
   "wind1_mil": -0.046,
   "wind1_dir": "L",
   "tof_s": 0.361,
   "vel_fps": 2292.576
  },
  {
   "range_yd": 600,
   "elev_mil": 3.827,
   "wind1_mil": -0.126,
   "wind1_dir": "L",
   "tof_s": 0.791,
   "vel_fps": 1914.745
  }
 ],
 "da_ft": 803,
 "assumed": ["RH 50% (default)", "lat 45° (default)", "azimuth 0° (default)", "inclination 0° (default)", "wind 0 mph (default)", "wind 2 = wind 1", "wind from 3 o'clock (default)"],
 "source": "from your request",
 "stale_age_s": null
}
```

Saved nothing.

Call 2:
```json
{"from_yd":300,"to_yd":600,"step_yd":300,"temp_F":62,"station_pressure_inHg":29.5,"profile_id":"Creek"}
```

The tool refuses (with the stored-text note):
```text
Which profile? "Ridge 308" (fixture-ridge); "Creek 65" (fixture-creek)
```

**4. Two profiles and a report 26 hours old: the profile is the one on the report, the line names it, and the age is spoken**

Starting point: two profiles, and a phone whose newest calculator report is 26 hours old and shows the second of them, Creek 65 (68 °F, 27.50 inHg, 600 yd, 5 mph from 3 o'clock). Link scopes: `read`.

Call:
```json
{"from_yd":300,"to_yd":900,"step_yd":300}
```

Spoken line:
```text
Range card for "Creek 65" v1, 68 °F, DA 3,558 ft, from your phone 26.0 h ago. Your phone's data is 26.0 h old — check the wind and atmosphere.
```

Details (with the stored-text note):
```json
{
 "profile": {
  "id": "fixture-creek",
  "version": 1,
  "name": "Creek 65"
 },
 "rows": [
  {
   "range_yd": 300,
   "elev_mil": 1.062,
   "wind1_mil": 0.171,
   "wind1_dir": "R",
   "tof_s": 0.359,
   "vel_fps": 2322.92
  },
  {
   "range_yd": 600,
   "elev_mil": 3.676,
   "wind1_mil": 0.346,
   "wind1_dir": "R",
   "tof_s": 0.78,
   "vel_fps": 1969.849
  },
  {
   "range_yd": 900,
   "elev_mil": 7.066,
   "wind1_mil": 0.548,
   "wind1_dir": "R",
   "tof_s": 1.279,
   "vel_fps": 1646.058
  }
 ],
 "da_ft": 3558,
 "assumed": ["temp 68 °F (phone)", "pressure 27.5 inHg (phone)", "RH 40% (phone)", "lat 40° (phone)", "azimuth 0° (phone)", "inclination 0° (phone)", "wind 5 mph (phone)", "wind 2 5 mph (phone)", "wind from 3 o'clock (phone)"],
 "source": "from your phone 26.0 h ago",
 "stale_age_s": 93600
}
```

Saved nothing.

**5. More than 100 rows are refused**

Starting point: one profile, no phone connected. Link scopes: `read`.

Call:
```json
{"from_yd":100,"to_yd":1200,"step_yd":10,"temp_F":60,"station_pressure_inHg":29.5}
```

The tool refuses:
```text
A range card can have 1 to 100 rows; widen the step or narrow the span.
```

**6. The end is before the start: no row**

Starting point: one profile, no phone connected. Link scopes: `read`.

Call:
```json
{"from_yd":900,"to_yd":300,"step_yd":300,"temp_F":60,"station_pressure_inHg":29.5}
```

The tool refuses:
```text
A range card can have 1 to 100 rows; widen the step or narrow the span.
```

**7. A card that runs past what the bullet reaches stops at the first range it does not reach**

Starting point: one profile, no phone connected. Link scopes: `read`.

Call:
```json
{"from_yd":3500,"to_yd":5000,"step_yd":500,"inclination_deg":45,"temp_F":60,"station_pressure_inHg":29.5}
```

Spoken line:
```text
Range card for "Ridge 308" v1, 60 °F, DA 664 ft, from your request.
```

Details (with the stored-text note):
```json
{
 "profile": {
  "id": "fixture-ridge",
  "version": 1,
  "name": "Ridge 308"
 },
 "rows": [
  {
   "range_yd": 3500,
   "elev_mil": 140.926,
   "wind1_mil": -3.647,
   "wind1_dir": "L",
   "tof_s": 13.346,
   "vel_fps": 422.484
  },
  {
   "range_yd": 4000,
   "elev_mil": 242.699,
   "wind1_mil": -5.843,
   "wind1_dir": "L",
   "tof_s": 18.82,
   "vel_fps": 359.209
  },
  {
   "range_yd": 4500,
   "status": "out of range"
  }
 ],
 "da_ft": 664,
 "assumed": ["RH 50% (default)", "lat 45° (default)", "azimuth 0° (default)", "wind 0 mph (default)", "wind 2 = wind 1", "wind from 3 o'clock (default)"],
 "source": "from your request",
 "stale_age_s": null
}
```

Saved nothing.

**8. A named model: the spoken line does not say which model**

Starting point: one profile, no phone connected. Link scopes: `read`.

Call:
```json
{"from_yd":500,"to_yd":1000,"step_yd":500,"temp_F":60,"station_pressure_inHg":29.5,"model":"classic"}
```

Spoken line:
```text
Range card for "Ridge 308" v1, Classic model, 60 °F, DA 664 ft, from your request.
```

Details (with the stored-text note):
```json
{
 "profile": {
  "id": "fixture-ridge",
  "version": 1,
  "name": "Ridge 308"
 },
 "rows": [
  {
   "range_yd": 500,
   "elev_mil": 3.284,
   "wind1_mil": -0.094,
   "wind1_dir": "L",
   "tof_s": 0.681,
   "vel_fps": 1837.993
  },
  {
   "range_yd": 1000,
   "elev_mil": 10.876,
   "wind1_mil": -0.311,
   "wind1_dir": "L",
   "tof_s": 1.7,
   "vel_fps": 1179.474
  }
 ],
 "da_ft": 664,
 "assumed": ["RH 50% (default)", "lat 45° (default)", "azimuth 0° (default)", "inclination 0° (default)", "wind 0 mph (default)", "wind 2 = wind 1", "wind from 3 o'clock (default)"],
 "source": "from your request",
 "stale_age_s": null
}
```

Saved nothing.

**9. A what-if velocity: the spoken line begins with the what-if, and nothing is saved**

Starting point: one profile, no phone connected. Link scopes: `read`.

Call:
```json
{"from_yd":500,"to_yd":1000,"step_yd":500,"temp_F":60,"station_pressure_inHg":29.5,"what_if":{"mv_fps":2700}}
```

Spoken line:
```text
What if: Range card for "Ridge 308" v1, 60 °F, DA 664 ft, from your request.
```

Details (with the stored-text note):
```json
{
 "profile": {
  "id": "fixture-ridge",
  "version": 1,
  "name": "Ridge 308"
 },
 "what_if": {
  "mv_fps": {
   "from": 2640,
   "to": 2700
  }
 },
 "saved": false,
 "rows": [
  {
   "range_yd": 500,
   "elev_mil": 3.11,
   "wind1_mil": -0.126,
   "wind1_dir": "L",
   "tof_s": 0.665,
   "vel_fps": 1887.172
  },
  {
   "range_yd": 1000,
   "elev_mil": 10.293,
   "wind1_mil": -0.38,
   "wind1_dir": "L",
   "tof_s": 1.654,
   "vel_fps": 1218.775
  }
 ],
 "da_ft": 664,
 "assumed": ["RH 50% (default)", "lat 45° (default)", "azimuth 0° (default)", "inclination 0° (default)", "wind 0 mph (default)", "wind 2 = wind 1", "wind from 3 o'clock (default)"],
 "source": "from your request",
 "stale_age_s": null
}
```

Saved nothing.

**10. A profile that words its turrets as turns**

Starting point: one profile whose scope is set to clockwise turn wording (up is counter-clockwise, right is clockwise), no phone connected. Link scopes: `read`.

Call:
```json
{"from_yd":500,"to_yd":1000,"step_yd":500,"wind_mph":8,"temp_F":60,"station_pressure_inHg":29.5}
```

Spoken line:
```text
Range card for "Ridge 308" v1, 60 °F, DA 664 ft, from your request.
```

Details (with the stored-text note):
```json
{
 "profile": {
  "id": "fixture-ridge",
  "version": 1,
  "name": "Ridge 308"
 },
 "rows": [
  {
   "range_yd": 500,
   "elev_mil": 3.173,
   "wind1_mil": 0.755,
   "wind1_dir": "R",
   "elev_turn": "counter-clockwise",
   "wind1_turn": "clockwise",
   "tof_s": 0.681,
   "vel_fps": 1837.962
  },
  {
   "range_yd": 1000,
   "elev_mil": 10.766,
   "wind1_mil": 1.81,
   "wind1_dir": "R",
   "elev_turn": "counter-clockwise",
   "wind1_turn": "clockwise",
   "tof_s": 1.7,
   "vel_fps": 1179.435
  }
 ],
 "da_ft": 664,
 "assumed": ["RH 50% (default)", "lat 45° (default)", "azimuth 0° (default)", "inclination 0° (default)", "wind 2 = wind 1", "wind from 3 o'clock (default)"],
 "source": "from your request",
 "stale_age_s": null
}
```

Saved nothing.

**11. A card that crosses the edge of the fitted drag correction**

Starting point: one profile at version 2 with a fitted drag factor of 1.05, calibrated down to Mach 1.3, no phone connected. Link scopes: `read`.

Call:
```json
{"from_yd":600,"to_yd":1200,"step_yd":200,"temp_F":60,"station_pressure_inHg":29.5}
```

Spoken line:
```text
Range card for "Ridge 308" v2, 60 °F, DA 664 ft, from your request. From 800 yd it is past calibration (slower than Mach 1.30); those rows use the book curve.
```

Details (with the stored-text note):
```json
{
 "profile": {
  "id": "fixture-ridge",
  "version": 2,
  "name": "Ridge 308"
 },
 "rows": [
  {
   "range_yd": 600,
   "elev_mil": 4.553,
   "wind1_mil": -0.176,
   "wind1_dir": "L",
   "tof_s": 0.862,
   "vel_fps": 1653.759
  },
  {
   "range_yd": 800,
   "elev_mil": 7.329,
   "wind1_mil": -0.273,
   "wind1_dir": "L",
   "tof_s": 1.244,
   "vel_fps": 1410.345,
   "past_calibration": "blend"
  },
  {
   "range_yd": 1000,
   "elev_mil": 10.876,
   "wind1_mil": -0.396,
   "wind1_dir": "L",
   "tof_s": 1.7,
   "vel_fps": 1179.419,
   "past_calibration": "book"
  },
  "(1 more)"
 ],
 "da_ft": 664,
 "past_calibration": {
  "min_mach": 1.3,
  "from_yd": 800
 },
 "assumed": ["RH 50% (default)", "lat 45° (default)", "azimuth 0° (default)", "inclination 0° (default)", "wind 0 mph (default)", "wind 2 = wind 1", "wind from 3 o'clock (default)"],
 "source": "from your request",
 "stale_age_s": null
}
```

Saved nothing.

**12. A profile on the Spin model: each row adds the stability factor**

Starting point: one profile whose stored model is Spin, with a bullet length, no phone connected. Link scopes: `read`.

Call:
```json
{"from_yd":500,"to_yd":1000,"step_yd":500,"temp_F":60,"station_pressure_inHg":29.5}
```

Spoken line:
```text
Range card for "Ridge 308" v1, 60 °F, DA 664 ft, from your request.
```

Details (with the stored-text note):
```json
{
 "profile": {
  "id": "fixture-ridge",
  "version": 1,
  "name": "Ridge 308"
 },
 "rows": [
  {
   "range_yd": 500,
   "elev_mil": 3.279,
   "wind1_mil": -0.095,
   "wind1_dir": "L",
   "tof_s": 0.682,
   "vel_fps": 1837.471,
   "sg": 3.504
  },
  {
   "range_yd": 1000,
   "elev_mil": 10.863,
   "wind1_mil": -0.282,
   "wind1_dir": "L",
   "tof_s": 1.701,
   "vel_fps": 1178.843,
   "sg": 5.903
  }
 ],
 "da_ft": 664,
 "assumed": ["RH 50% (default)", "lat 45° (default)", "azimuth 0° (default)", "inclination 0° (default)", "wind 0 mph (default)", "wind 2 = wind 1", "wind from 3 o'clock (default)"],
 "source": "from your request",
 "stale_age_s": null
}
```

Saved nothing.

**13. A profile someone shares: its name comes back in quotation marks and no id of it is returned**

Starting point: one profile of the shooter's, and one profile another person shares with them. Link scopes: `read`.

Call:
```json
{"from_yd":300,"to_yd":600,"step_yd":300,"temp_F":62,"station_pressure_inHg":29.5,"share_id":"5a3e0b7c41d29f60"}
```

Spoken line:
```text
Range card for "Creek 65" v1, 62 °F, DA 803 ft, from your request.
```

Details:
```json
{
 "profile": {
  "share_id": "5a3e0b7c41d29f60",
  "version": 1,
  "name": "\"Creek 65\""
 },
 "rows": [
  {
   "range_yd": 300,
   "elev_mil": 1.136,
   "wind1_mil": -0.046,
   "wind1_dir": "L",
   "tof_s": 0.361,
   "vel_fps": 2292.576
  },
  {
   "range_yd": 600,
   "elev_mil": 3.827,
   "wind1_mil": -0.126,
   "wind1_dir": "L",
   "tof_s": 0.791,
   "vel_fps": 1914.745
  }
 ],
 "da_ft": 803,
 "assumed": ["RH 50% (default)", "lat 45° (default)", "azimuth 0° (default)", "inclination 0° (default)", "wind 0 mph (default)", "wind 2 = wind 1", "wind from 3 o'clock (default)"],
 "source": "from your request",
 "stale_age_s": null
}
```

Saved nothing.

**14. A profile of the shooter and a shared one in the same call**

Starting point: one profile of the shooter's, and one profile another person shares with them. Link scopes: `read`.

Call:
```json
{"from_yd":300,"to_yd":600,"step_yd":300,"temp_F":60,"station_pressure_inHg":29.5,"profile_id":"fixture-ridge","share_id":"5a3e0b7c41d29f60"}
```

The tool refuses:
```text
Give a profile of yours or one shared with you: one or the other, not both.
```

**15. A wind given only as the second wind: the card is the calm one**

Starting point: one profile, no phone connected. Link scopes: `read`.

Call:
```json
{"from_yd":500,"to_yd":1000,"step_yd":500,"wind2_mph":10,"temp_F":60,"station_pressure_inHg":29.5}
```

Spoken line:
```text
Range card for "Ridge 308" v1, 60 °F, DA 664 ft, from your request.
```

Details (with the stored-text note):
```json
{
 "profile": {
  "id": "fixture-ridge",
  "version": 1,
  "name": "Ridge 308"
 },
 "rows": [
  {
   "range_yd": 500,
   "elev_mil": 3.284,
   "wind1_mil": -0.131,
   "wind1_dir": "L",
   "tof_s": 0.681,
   "vel_fps": 1837.959
  },
  {
   "range_yd": 1000,
   "elev_mil": 10.876,
   "wind1_mil": -0.396,
   "wind1_dir": "L",
   "tof_s": 1.7,
   "vel_fps": 1179.419
  }
 ],
 "da_ft": 664,
 "assumed": ["RH 50% (default)", "lat 45° (default)", "azimuth 0° (default)", "inclination 0° (default)", "wind 0 mph (default)", "wind from 3 o'clock (default)"],
 "source": "from your request",
 "stale_age_s": null
}
```

Saved nothing.

---

[All reference pages](index.md)