> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spirii.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Locations
> What a location is, what it contains, and how it connects to the rest of the platform.
A location is the container for the chargers at a single physical site: the entity that every charge box, tariff, session, and access rule is organised under.
## Overview
A location is the top of the [charger hierarchy](#the-charger-hierarchy): before a charge box can come online, it has to belong to one. It holds the site's identity (name, address, geolocation, and type) and anchors the pricing, access, operational, and financial settings that apply to everything installed there.
Because so much hangs off it, how you set up a location shapes how every charger on the site behaves.
## Context
What a location is depends on which side of the platform you work from.
### CPO context
For a CPO, a location is a site you operate. You [create it](/capabilities/connection/location-configuration), set its [pricing](/capabilities/pricing/pricing-options-and-logic) and [access](/capabilities/access/location-access), and [bring chargers online](/capabilities/connection/charger-activation) under it. The attributes, types, and states below describe a location as Connect models it for the operator.
### eMSP context
For an eMSP, a location isn't something you operate — it's a node you reach for your drivers, over roaming. You don't work with the Connect model below. Instead you receive a read-only representation published by the operator, which follows the roaming standard's (OCPI) conventions rather than Connect's: the location types, the charger structure, and even the meaning of "published" differ. [Roaming](/capabilities/roaming/roaming-connection) covers how that exchange works.
## Key attributes
| Attribute | Description | Example |
| --------------- | ------------------------------------------------------------------------------------------ | ----------------------------------------- |
| ID | Unique identifier for the location | `12345` |
| Name | Free-text name; shown to drivers in the app | `Munich DC Hub` |
| Customer | The customer that owns the location in the platform | `Acme Inc.` |
| Address | Street, postcode, city, and country | `Bayerstraße 10a, 80335 München, Germany` |
| Coordinates | Latitude and longitude, used to place the map pin in apps | `48.0827, 11.5550` |
| Public | Whether the location is visible and usable in Spirii apps and with tokens | `true` |
| Roaming enabled | Whether the location is published to roaming networks | `true` |
| Tariff | The tariff setting the price and conditions for public charging via Spirii apps and tokens | `Public DC (0,50 €/kWh)` |
| Roaming tariff | The tariff for charging via roaming networks | `SPI-230 (0,50 €/kWh)` |
## Types and states
The types and states below are Spirii's CPO model in Connect, as introduced under Context; an eMSP reaching the location over roaming sees OCPI's values instead.
### Location types
| Type | Description | Typical use |
| ------------------------- | ------------------------------- | ----------------------------------------------- |
| Residential | A home charging location | Private B2C charging, company-car home charging |
| Public road | A publicly available site | Highway hubs, on-street and urban parking |
| Parking lot | A public site at a parking area | Depots, retail, workplace charging |
| Parking lot (indoor) | A parking building | Multi-storey car parks |
| Parking lot (underground) | An underground parking garage | Basement car parks |
| Hotel | A charging location at a hotel | Hotels |
Residential locations aren't publicly priced, but they're not tariff-free: a free residential tariff is assigned automatically in the background.
### Location states
A location's state is derived from the chargers installed on it:
| State | Meaning |
| ------- | ---------------------------------------------------------------------------------------- |
| Online | One or more chargers are online and ready to charge |
| Pending | The location is commissioning, awaiting installation and activation of its first charger |
| Offline | One or more of the location's chargers are disconnected |
| Faulted | One or more of the location's chargers are faulted |
## Relationships
A location sits at the top of the charger hierarchy and anchors four kinds of settings across the site: pricing, access, operations, and financial.
### The charger hierarchy
Chargers on a location are structured in four levels:
* **Location:** the full site
* **Charge box:** an individual physical unit
* **EVSE:** the part of a charge box that can serve one EV at a time; each has its own ID and a status, such as Charging or Available
* **Connector:** the socket or cable an EV plugs into, with its plug type (e.g. CCS), power type (e.g. DC), and maximum power (e.g. 150 kW)
```mermaid theme={null}
flowchart TD
L("Location") --> CB1("Charge box\nAC")
L --> CB2("Charge box\nDC")
CB1 --> E1("EVSE")
CB2 --> E2("EVSE")
CB2 --> E3("EVSE")
E1 --> C1("Connector\nType 2")
E2 --> C2("Connector\nCCS")
E2 --> C3("Connector\nCHAdeMO")
E3 --> C4("Connector\nCCS")
```
## Used in
Publish the location to roaming networks and price it for roaming.
The chargers that come online under a location.