Resolve place to cell64 + band inventory
emem_locateGet the canonical address (cell64) of a real-world place. Every agent resolves a place to the same cell64, so two models refer to the same ground. The answer also lists, by topic, the bands and algorithms that you can recall there. For an OBJECT identity (a bridge, a plot) instead of a cell, use emem_entity. Send lat+lng as numbers, or a free-text place. When both arrive, the coordinates win. q, query and name are other names for place. The answer lists keys that this schema does not declare in _unrecognised_arguments, so a typo is visible.
When to use: Call this when the next step needs the cell64 of a named place, or the bands that exist there. data_at_this_cell lists every band you can recall, by topic (live_bands_by_topic), the recipes that use them (algorithms_for_topic), and the bands with no materializer here. For one packaged answer in one call, use emem_ask.
Example arguments: {"place":"Mount Everest"}
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Alias for `place`, accepted because OSM/Mapbox/Google Geocoding all use `q`. Provide either this or `place` (or `lat`+`lng`). | |
| lat | No | WGS-84 latitude in degrees, paired with `lng`. REQUIRED with `lng` unless `place`/`q` is provided. | |
| lng | No | WGS-84 longitude in degrees, paired with `lat`. REQUIRED with `lat` unless `place`/`q` is provided. | |
| name | No | Alias for `place`. | |
| place | No | Free-text place name (e.g. 'Mount Everest', 'Tokyo'). REQUIRED unless `lat`+`lng` is provided. Aliases also accepted: `q`, `query`, `name`. | |
| query | No | Alias for `place`. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| next | Yes | ||
| cell64 | No | Pass as `cell` to emem_recall. | |
| status | No | needs_location: no place named. | |
| selected | No | ||
| place_label | No | ||
| data_at_this_cell | No |