> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neochamber.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Sites and the map

> How site markers get their position, and why the map always tells you which source it used.

Every node reports the `--site` label it was installed with, and the fleet map
turns those into markers sized by GPU count and colored by health.

**The card is the map**: a title, one sentence, the markers, and a compact
legend. Everything about a site — its nodes, GPU models, aggregate GPU memory,
newest heartbeat, online/offline split, open conditions, its coordinates, and
the button that changes them — is in the box that opens when you hover a marker.

<Note>
  Keyboard: Tab to a marker for the same box, and press **E** on a focused marker
  to open its editor. The box stays open while your pointer or focus is inside it.
</Note>

## A marker comes from one of two places, and the map says which

<CardGroup cols={2}>
  <Card title="Coordinates you set" icon="location-dot">
    **Solid marker.** From *Edit location* in a marker's hover box, or
    `PUT /api/ops/sites/<site>`. Yours always win — a position you typed is
    never replaced or moved by anything else, and clearing it is one click.
  </Card>

  <Card title="Where that site's agents connect from" icon="wifi">
    **Hollow, dashed, prefixed `≈`.** For a site nobody has placed, the map
    falls back to the approximate location of the machines' own connections.
    The hover box says the position came from the agents.
  </Card>
</CardGroup>

## Unplaced sites

Sites with no coordinates and nothing reporting a location have no marker to
hover. They are the line under the map:

> *"N site locations don't have coordinates yet"*

which opens a list of exactly those sites, each with its node and GPU counts
intact, and each editable there.

<Note>
  An empty map means **nothing placed yet**, never **no hardware**.
</Note>

## Nothing is guessed from the name

`dal-01` is a string you typed, not a claim about Dallas. There is **no
geocoder and no name-to-city table** anywhere in the product.

And a derived marker is always **one real machine's** location, never a point
averaged between machines — averaging two nodes on different continents would
draw a marker in open water, where no hardware is.

See [Data residency](/platform/data-residency#what-we-record-about-location) for
exactly what location data is recorded and who can see it.