Data inputs for your own models
Connect registered buildings and municipal statistics to your own analyses and scenarios with explicit assumptions.
Example: a local demand scenario
An analysis team wants to explore how the age profile could affect demand for housing or services in a municipality.
- Request Municipal context for the correct municipality. Read source periods and age bands before choosing variables.
- Use income and employment as context. Compare compatible periods and geographies only; do not add overlapping age bands.
- For analysis involving specific buildings, use Address and buildings to link the address to registered buildings and dwelling units. Record your assumptions and test the scenario against independent observations.
Value in your workflow
Your own scenario with documented inputs, periods and assumptions that can be reviewed and refreshed as the data changes.
Relevant data packages
Address and buildings
Address API ·
package=home_profile- Address and property identifiers
- Buildings
- Dwelling units
- Building data coverage
View the package in the API documentation →
See the lookup workflow →Municipal context
Region API ·
package=core- Region code and validity
- Employment by year
- Age profile by period
- Household income by year
View the package in the API documentation →
See the lookup workflow →
Requirements and boundaries
These packages do not deliver a ready-made prediction, 3D geometry or an active model release. Geometry and execution of Datakilde models require separate documented contracts and availability.
This is an illustrative workflow, not a fetched response. Packages select sections; source terms and effective access determine delivery. Check source status, coverage and freshness. Missing data is unresolved, not a negative finding.
Lookup access does not automatically grant storage, redistribution or model/LLM training rights. Check the permitted purpose and terms for each source.