is_feedin marks it in the dataset, and
the consumption endpoints exclude it outright.
Feed-in is a matrix, not a number
An operator’s feed-in sheet is rarely one rate. A typical one varies the payment along six axes at once, and the harmonized form keeps them:
A single operator’s sheet can expand to a few dozen rows. That is the sheet
faithfully represented, not duplication.
Prices that are not fixed
price_basis says what kind of number energy_min is:
On the map
Feed-in has its own map layer and its own endpoint,GET /api/map_feedin, with
the same per-operator shape as the consumption map:
/api/map/tariffs filters feed-in out at the SQL
level rather than by convention, so no combination of parameters can pull a
remuneration into a consumption colour.Coverage
Feed-in is published less consistently than consumption tariffs, and the structured matrix fields are populated only where the operator publishes a structured sheet — a great many publish a paragraph of prose instead. Where a sheet was machine-read,stage is ki and the usual
provenance rules apply.