location_tagger

Location Tagger Agent

The Location Tagger is a built-in, global default agent that automatically finds place names in a document and turns them into geocoded annotations: OC_COUNTRY, OC_STATE, and OC_CITY. Each annotation it creates carries the resolved coordinates and administrative codes in its data payload, so the places show up as pins on the Discover and Corpus Home maps.

It is wired to run through the ordinary corpus-actions framework — the same execution path used by the built-in Document Assistant and Corpus Assistant — so you configure it once on a corpus and it runs automatically.

What it does

For every place mention it recognises, the agent calls the add_annotations_from_exact_strings tool with the appropriate label and a set of hints. When the label is one of the geographic labels (OC_COUNTRY / OC_STATE / OC_CITY), the tool routes the string through the offline geocoding service (#1819) and stores the result on the annotation:

{
  "canonical_name": "Austin",
  "lat": 30.2672,
  "lng": -97.7431,
  "admin_codes": { "iso_alpha2": "US", "admin1": "TX" },
  "geocoded": true
}

Non-geographic labels are unaffected — the hints field is simply ignored for them, so existing callers of the tool keep working unchanged.

Configuration walkthrough

1. Migrate. After deploying, run migrations. The Location Tagger appears as a global, public agent in the agent picker:

   docker compose -f production.yml --profile migrate up migrate
   

   Note — the migration is a one-time snapshot. It copies DEFAULT_LOCATION_TAGGER_INSTRUCTIONS from settings into the agent's system_instructions column at creation time. If you later improve the prompt in config/settings/base.py, existing databases keep the old prompt — update the Location Tagger agent record via the Django admin (or a follow-up data migration) to pick up the revision.