# Prospecting: county mode for practitioners — apply

    cp -R prospecting-county/app/*       ./app/
    cp -R prospecting-county/config/*    ./config/
    cp -R prospecting-county/database/*  ./database/

## 1. Migrate
    php artisan migrate --force

## 2. TDLR importer — county fallback (see docs/tdlr-county-patch.md)
Practitioner files leave BUSINESS COUNTY empty but fill COUNTY (col 3).

## 3. Backfill counties
ZIP centroids: reload from the CSV including its county column.
Locations: derive each location's county from its ZIP.

## 4. Controller — pass the mode and county through
In ProspectingController::index(), add `county: $request->query('county')` to the
search() call and include `'mode' => $result['mode']` in the Inertia payload.

## 5. Re-import (the unique key now includes profession)
    php artisan prospects:tdlr

## Why two modes
TDLR practitioner records carry a county and nothing else — no street, ZIP or phone.
Establishment records carry full addresses. Rather than fabricate coordinates for
340,000 practitioners, practitioner tabs filter by the county their licence names and
omit the distance column; establishment tabs keep radius search. This matches how the
reference report behaves.