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

# Locations and prices

> Which locations are on the map, how statuses count, what a price means and how occupancy is measured.

## What is on the map

* The public locations of the operators Plugchoice roams with, as they publish them over OCPI, when they have coordinates.
* Chargers on Plugchoice whose owners opened them to roaming with a price, at locations with coordinates.

Chargers an operator removed are left out. A location's id is `remote-…` for an operator's location and `site-…` for one on Plugchoice. Treat it as an opaque string.

## Statuses

A tile counts each connector by its charger's (EVSE's) status, in three groups:

| Status | Counts as |
| - | - |
| `AVAILABLE` | available |
| `CHARGING`, `BLOCKED`, `RESERVED` | occupied |
| `OUTOFORDER`, `INOPERATIVE`, `UNKNOWN`, `PLANNED` | out of order |

A location's detail has each EVSE's own status and `status_since`.

## Power

A pin's `power_types` are `AC`, `DC` or both, from its connectors. `max_power_kw` is the most powerful connector's kW: what the operator gives as its maximum power, or else its voltage times its current (times the phases for AC). It is what the connector can deliver. A car may charge slower.

## Prices

`price_per_kwh` on a pin is in euros per kWh, before VAT, from the tariff in effect now in the location's own time zone. A tariff can differ by time of day, by day and by power. The pin has the lowest price of its connectors. It is `null` when the location has no price per kWh, or only one in another currency.

This is the price the operator publishes to roaming partners. A driver pays what their charge card's provider charges, which can add its own fees and VAT. Show it as an indication.

A location's detail has its tariffs as the operator publishes them, by id: OCPI 2.2.1 tariffs with every element, price component and restriction, so you can show a time or parking fee too. `prices_include_vat` is always `false`. A price component's `vat` is the percentage on top, when the operator gives it.

## Occupancy

Plugchoice samples every location's connectors every 5 minutes and keeps twelve weeks of the sums. From that, once a location has two weeks of history, its detail has:

* `occupancy`: 7 days, Monday first, of 24 hours in the location's own time zone. Each hour is the share of its working connectors that were occupied, from 0 to 1, or `null` for an hour without data.
* `out_of_order_ratio_30d`: the share of the last 30 days its connectors were out of order, from 0 to 1.

Before two weeks both are missing from the answer. The samples count connectors and keep nothing about who charged.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.