Municipal greenhouse-gas accounts
Annual territorial greenhouse-gas emissions per municipality and county by sector and source since 2009, plus land-use (LULUCF) emissions and removals.
Explore in the wiki
All lookup operations
Open HTML operations for navigation. The JSON link for each operation is only for programmatic data access.
Building software or a dashboard? List operation names as JSON, then open the selected operation's descriptor before fetching data.
-
find_areas– List the counties and municipalities the emission accounts cover, with the internal ids the other tools accept.
HTML GET template -
get_emissions– Get a municipality's or county's territorial greenhouse-gas emissions by sector and year, or the sources within one sector.
HTML GET template -
get_land_use_emissions– Get net emissions and removals from land use, land-use change and forestry (LULUCF) for a municipality or county.
HTML GET template
Programmatic access
First confirm the operation and parameters in HTML, then use the read-only JSON API.
Does the client support MCP? Find the corresponding Allemannsdata server and registered tools.
How an AI agent should use this page
Ground rule: Navigate with HTML GET links to keep explanations and relationships. Use the page's JSON alternative only when concrete values must be extracted, compared or computed.
How to use Municipal greenhouse-gas accounts
Annual territorial greenhouse-gas emissions per municipality and county by sector and source since 2009, plus land-use (LULUCF) emissions and removals. Choose a search lookup first when you lack an identifier; use a detail lookup when you already have a stable ID.
- Read requirements, cache time and known usage limits.
- Open the lookup and use the HTML GET template.
- Follow normalized result links onward; use JSON only for structured data work.
Related sources and scope
AI agent? Read the complete navigation and programming guide.