Documentation How it works
Data sources
What each source establishes, how it is collected and what remains unknown.
On this page
Evidence, not a universal dataset
Adapters run on the server and produce typed evidence records. Each record describes a claim, source identity, URL when available, status, retrieval time, scope and assumptions. Quantities and publication or observation metadata are retained where supported.
| Source | Provides | Does not establish |
|---|---|---|
| PDOK Locatieserver | Confirmed address identity, address linkage and supplied centroid | Ownership, engineering suitability or connection approval |
| BAG | Address-linked building use, registered floor area and linked building context | Usable roof area or structural capacity |
| 3DBAG | Modeled building geometry and semantic roof surfaces for solar research | A current survey, shading assessment or usable PV area |
| PVGIS | Modeled annual and monthly production quantities using supplied assumptions | Actual production, roof suitability or export permission |
| Grid postcode CSV | Published categorical consumption and feed-in status for an exact postcode | Property-level available kW, queue position or a connection date |
| RVO and ACM | Retrieved national guidance and regulatory explanations | Site-specific eligibility or an individual legal decision |
| Enexis guidance | Direction-specific explanations of published map colours | Binding transport capacity for a property |
Source states
available: a usable record was retrieved for the adapter’s stated scope.missing: required input or an exact matching record was absent.unavailable: access, networking, a disabled adapter or another collection failure prevented retrieval.
Other stale or unknown-date conditions must remain visible in freshness evaluation. An unavailable BAG request does not mean there is no building, and a missing postcode row does not mean zero capacity.
Exact address linkage
The collector resolves the confirmed PDOK ID, obtains the BAG number designation and queries the corresponding verblijfsobject. For solar research, the linked BAG building provides the exact identifier used to query 3DBAG.
This chain matters: nearby geometry or a successful HTTP response is not proof that the returned object belongs to the researched address. The adapters recheck the relevant identities and retain linkage provenance.
Grid directions and colours
Consumption and feed-in remain separate evidence records. Official guidance is fetched for the consumption and feed-in legends separately, so a consumption-only explanation is not silently used as evidence of export rules.
Always distinguish postcode-area indication from property connection decision. Source access is disabled by default behind GRID_STATUS_SOURCE_ENABLED; enabling the adapter technically does not establish permission to reuse or redistribute its data. Grid-data reuse permission remains unresolved.
Retry and cache behavior
JSON and guidance requests have bounded retries for transient failures, with 500 ms then 1,000 ms backoff. Building requests use a 12-second request deadline; other JSON/guidance requests use 9 seconds. Cancellation stops waiting and prevents subsequent stages from starting. The separate grid CSV adapter has its own bounds.
BAG and 3DBAG object results can be reused from a bounded process-local cache for up to 24 hours. The cache holds at most 128 objects and retains original retrieval and observation provenance. Failed requests are not cached. A process restart clears this cache; it is not a persistent source archive.
Guidance and dates
Official HTML is converted to bounded readable text with a content hash and source URL. The text is evidence, never instructions to the model. General guidance is not a site-specific ruling, and retrieval does not invent a publication or effective date.
Source reliability can vary between runs. Read the evidence saved with your report rather than assuming that a source available for a previous address was available for yours.