Municipal, district and neighbourhood codes of additional properties (01-01-1999-01-01-2016)

Open data API in a single place

Provided by Centraal_Bureau_voor_de_Statistiek

Get early access to Municipal, district and neighbourhood codes of additional properties (01-01-1999-01-01-2016) API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
Microdata, Data Governance Act, DGA, ODISSEI
Quality scoring

Dataset description

This component provides a link between other objects (RINOBJECTNUMMERs) and the municipality/district/neighborhood to which this object belongs (GWBCODENIETVSL_A). Other objects are objects that do not appear in the BAG and have not been given a historical number. More information on how to access the data: > https://www.cbs.nl/nl-nl/onze-diensten/maatwerk-en-microdata/microdata-zelf-onderzoek-doen ### Methodology The GWBCODENIETVSL is year dependent. For more information, see the description of this variable. In this component, GWBCODENIETVSLJJJ is included as “array” (GWBCODENIETVSL_A). That is, ear as far as possible within this one file is given the 1999 GWBCODE for each object, but also that of 2000, 2001, 2002 etc. Even as an object only since, for example, 2004 exists. As a result, figures can be made comparable with this file over time. Namely, by choosing and keeping the municipal/district/neighbourhood classification of one year constant, figures of different reference years can be calculated according to the chosen classification. The first four positions of the GWBCODEJJJ are the municipal code, or the variable GEMJJJ. Using procedure 'PARTMENTST4 ' can be derived from the GWBCODEJYY the variable GEMYYYY. Unlike its & counterpart ' component VSLGWB, no distinction is made between provisional (& current ') and final & coordinated ' versions of the component. For the time being, it follows the updates of the GBAADRESOBJECTBUS. In the first version of a new year, the municipality code of the new year is included. The file is a cumulative timeless component. It does not cover a specific period (year, quarter, etc.), but runs from the beginning of the data source (1998) to the “present” (version date of the file). In every new version, there are always records. (RINOBJECTNUMMERs) added. ### Population All objects that do not appear in the BAG and have not been given a historical number. In other words, all objects of origin (SOORTOBJECTNUMMER) are not &B ' or 'H and#039;. The population of this stock is a cumulative set of RINOBJECTNUMMERs. It includes at least all objects up to and including the version number of the component. So in NOTVSLGWBTABV2014091 there are objects issued until the beginning of September 2014. The starting point is that from the December bus (VYYY121) the stand on 1 January of the new year can also be derived. The exact date until which the population is running is specified in NONVSLWBTABHISTORY.docx (part of the standard documentation). Periodically, new objects are added to this file. The GWBCODE_A is also periodically extended to include a new year. Under & #039;8. Methodology ' it is mentioned how this is addressed. As of the reporting year 2015, the Caribbean part of the Kingdom of the Netherlands has been included. Of the six islands, three have separate status within the Kingdom and the remaining three are special municipalities of the Netherlands. To indicate this difference with the other municipalities, the codes of the Caribbean municipalities start with a '3 ' instead of the usual &0 ' or '1 and#039;.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks