> For the complete documentation index, see [llms.txt](https://codifi-fdm.gitbook.io/codifi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codifi-fdm.gitbook.io/codifi-docs/mobile-app/creating-records/example-1-stps-on-a-transect.md).

# Example 1 — STPs on a Transect (GIS-led)

You're at the start of a survey transect with a crew. The Project has two relevant archetypes: a **Transect** (line) and **Shovel Test Probes** (STPs, points) that are children of Transects. The day's job is to walk the transect, drop STPs at regular intervals, log soil horizons at each, and move on.

This example shows the full **GIS-led** pattern — geometry first, form second — and along the way demonstrates the GPS quick-create toggle, repeaters, Ripple auto-calculations, and Quick Actions.

***

## Setup before you start walking

1. **Confirm the Project is synced.** Cloud icon should be solid green.
2. **Confirm the right GPS source is selected.** Tap the GPS chip in the Live Data Bar; if you're using an external receiver, verify it's showing the device name and reporting a fresh fix.
3. **Open the Project map view.** You should see the Project area and any reference overlays your PM uploaded.

***

## Step 1 — Create the Transect

A Transect is a line archetype — you'll draw it as you walk.

1. Tap the **+** button on the map screen.
2. Pick **Transect** from the create menu.
3. You're offered two paths: **Create** (just create the Record, fill data later) or **Create and Map** (jump straight to geometry capture). Pick **Create and Map**.
4. You land in the Transect's location card with **Draw mode** active.

### Drawing with bearing and distance

In Draw mode, switch to **Manual** mode. Manual lets you place vertices precisely.

* **Short-tap an existing vertex** → opens the vertex editor with bearing and distance fields. Type a heading and distance, and the next vertex is added at exactly that offset.
* Useful when your transect specification is "150 meters at 30° from the start point" — type the bearing and distance and the vertex lands exactly where it should.

You can mix this with GPS mode at any time: walk to a point, switch to GPS, hit "Add Point" to drop a vertex at your current location, then switch back to Manual to extend by bearing if needed.

Tap **Commit** when the transect line is the shape you want.

***

## Step 2 — Drop the first STP

Now that the Transect exists, you're back on the map. Tap the Transect on the map to open its Record card, then tap the kebab menu → **Add Child Record** → **Shovel Test Probe**.

### Quick GPS Create

Most Projects with lots of single-point Records have the **GPS Quick Create** toggle on in [Mobile Project Settings](/codifi-docs/mobile-app/mobile-project-settings.md). When it's on, single-point archetypes skip the two-button "Create vs Create and Map" dialog — they create the Record AND drop a GPS point at your current location in one tap.

For STPs, this is exactly what you want. The new STP appears under the Transect at your current GPS position.

> If your Project has Quick GPS Create *off*, you'll see the same two-button "Create vs Create and Map" prompt as you did for the Transect. Just pick "Create and Map" each time.

***

## Step 3 — Log soil horizons with a repeater

The STP form opens. You'll see standard fields (depth, results, notes) plus a **Horizon** repeater section.

A repeater is a section that can hold multiple rows of the same fields — perfect for soil horizons where each row is one stratum.

1. Tap **Add a new row**. Row 1 opens with sub-fields: Top, Bottom, Texture, etc.
2. Fill the row. Top: 0. Bottom: 20. Texture: Sand.
3. Tap **Add a new row** again for the next stratum.

### Duplicate and edit

If the next horizon is similar to the previous one, **long-press** the previous row and choose **Duplicate and Edit**. Codifi copies all fields into a new row; you just adjust what's different. Saves a lot of typing for stratigraphies with similar layers.

→ See [Repeaters and Duplicate-and-Edit](/codifi-docs/mobile-app/creating-records/repeaters.md) for the full reference.

***

## Step 4 — Watch Ripple fill the totals

If your Composition is configured well, the **Total Depth** field won't need to be filled — it's calculated automatically from the horizon thicknesses you just entered. Look for the **FX icon** next to its label; that's Ripple at work.

Same goes for any other auto-fields: the upper-depth-from-previous-row on horizon 2 automatically equals the bottom-depth of horizon 1, etc.

→ See [Ripple from a Field Crew's Perspective](/codifi-docs/mobile-app/creating-records/ripple-for-field-crews.md) for what to expect.

***

## Step 5 — Quick Actions chain the next STP

Save the STP. When you return to the map, the **+** button now shows a **Quick Action suggestion**: "Add another STP under Transect 1."

Tap it. The new STP gets created, auto-assigned to the same Transect parent, named with the next sequential number, and (with Quick GPS Create on) gets a fresh GPS point at your new location — all without re-navigating the relationship picker.

This is the **chained capture rhythm** that makes Codifi efficient for high-volume field work. Walk to the next STP location → tap the Quick Action → fill the horizons → walk to the next.

→ See [Quick Actions (Smart FAB Suggestions)](/codifi-docs/mobile-app/creating-records/quick-actions.md) for what triggers them and how to disable.

***

## What you just demonstrated

In one \~5-minute workflow, you exercised:

| Feature                                      | When it appeared                           |
| -------------------------------------------- | ------------------------------------------ |
| **Create and Map** vs **Create-only**        | Choosing how to start each Record          |
| **Manual draw mode with bearing + distance** | Building the Transect line                 |
| **GPS Quick Create**                         | Each STP creation                          |
| **Add Child Record**                         | Wiring STPs as Transect children           |
| **Repeaters**                                | Logging soil horizons                      |
| **Duplicate and Edit**                       | Speeding up similar rows                   |
| **Ripple**                                   | Total-depth and inherited-value auto-fills |
| **Quick Actions**                            | Chaining the next STP                      |

That's the GIS-led pattern in full.

***

## Where to go next

* [**Example 2 — Utah Site Form**](/codifi-docs/mobile-app/creating-records/example-2-utah-site-form.md) — the forms-led counterpart, where you defer geometry instead of leading with it.
* [**Repeaters and Duplicate-and-Edit**](/codifi-docs/mobile-app/creating-records/repeaters.md) — deeper reference on the repeater pattern.
* [**Ripple from a Field Crew's Perspective**](/codifi-docs/mobile-app/creating-records/ripple-for-field-crews.md) — what the FX icon means and what to do if a calculated field looks wrong.
* [**Quick Actions**](/codifi-docs/mobile-app/creating-records/quick-actions.md) — when they appear and how to manage them.
* [**Records in Context — End-of-Day QA**](/codifi-docs/mobile-app/records-in-context/end-of-day-qa.md) — what to do at the end of a day full of STPs.