City, neighbourhood and neighbourhood codes of a residence object (01-01-1999-01-01-2012)

This component provides a link between an object (RINOBJECTNUMMER) and the municipality/district/neighborhood to which this object belongs (GWBCODE_A). 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 GWBCODE is year-dependent. For more information, see the description of this variable. In this component, GWBCODEJJJ is included as “array” (GWBCODE_A). That is, as far as possible, within this one file the GWBCODE of 1999 is given for each object, but also that of 2000, 2001, 2002 etc. Even if an object only exists since, for example, 2004. 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. This file can therefore be used for assigning the municipal code to objects as well as for assigning the municipal district-neighbourhood code to objects. The update frequency has been adjusted accordingly: Every quarter new objects are provided with a GWBCODE_A in the form of & municipality code ' + '--------#039; e.g. '0003------#039;. The quarterly updates have the following approach: 1. December bus (with version number VYYYY121): The GWBCODE_A will be expanded with a new year. This GWBCODEJJJY will be filled with & municipality code of the new year &#039 for all objects; + '--------#039; e.g. '0003------#039;. Border corrections are not taken into account. 2. May bus (with version number VYYYY031): The new objects will be provided with a GWBCODE_A in the form of & municipality code ' + '--------#039; e.g. '0003------#039;. 3. June bus (with version number VYYYJ061): The GWBCODE_A is supplemented by the correct neighbourhood code, & #039;0003— then, if possible, change to e.g. '00030001 '. The GWBCODE added in January of a new year cannot yet be provided with a neighbourhood code, because the district/neighbourhood classification of the new year is not yet available. 3. September bus (with version number VYYYJ091): The GWBCODE_A is supplemented by the correct neighbourhood code, & #039;0003------#039; then, if possible, change to e.g. '00030001 '. The new year’s GWBCODE added in January will also be complemented by the right neighbourhood code. Once a year, a coordinated = final component is delivered. The final component year t is the provisional (& current ') component version June year t+ 1. Name of Coordinated Versions: VSLGWBJJJJTABVV Name of current versions: VRLVSLGWBTABVV ### Population All objects from the Basic Registration Addresses and Buildings (BAG) and all objects that occurred in the SSB before 1-1-2012 (historical objects). In other words, all objects with origin (SOORTOBJECTNUMMER) ' or 'H and#039;.These are not only inhabited objects, but also objects such as companies, schools, new buildings where no one lives, etc. The population of this stock is a cumulative set of RINOBJECTNUMMERs from 1995 for the inhabited objects (former RINADRESsen) and from 1998 for the remaining objects. The population includes at least all objects up to and including the version number of the component. So in VRLVSLSLGWBTABV2014031 objects appear until the beginning of April 2014. The starting point is that from the December bus (VYYY121) the stand on 1 January of the new year can also be derived. (VRL)VSLGWBTABHISTORY.docx (part of the standard documentation) specifies exactly the date until which the population runs. New objects are added to this file every quarter. The GWBCODE_A is also periodically extended to include a new year. Under & #039;8. Methodology ' it is mentioned how this is addressed.