City, district and neighbourhood codes of a residential property (uncoordinated) (01-01-2023 - 01-01-2024)

Description

This component provides a link between an object (RINOBJECT NUMBER) and the municipality/neighborhood/neighborhood to which this object belongs (GWBCODE_A). More information on how to access the data: > https://www.cbs.nl/en-en/our-services/custom-and-microdata/microdata-self-research ### Methodology The GWBCODE is year-dependent. For more information, see the description of this variable. In this component, GWBCODEYYYY is included as 'array' (GWBCODE_A). That is, as far as possible within this single file, the GWBCODE of 1999 has been 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 successively with this file. Namely, by choosing the municipality/neighbourhood/neighbourhood classification of one year and keeping it constant, figures from different reference years can be calculated according to the chosen classification. The first four positions of the GWBCODEYYY are the municipality code, or the variable GEMJJYY. Using the procedure 'PARTICIPATIONST4' the GEMYYYY variable can be derived from the GWBCODEYYY. This file can therefore be used both for assigning the municipality code to objects and for assigning the municipality-neighborhood code to objects. The update frequency has been adjusted accordingly: Every quarter new objects are provided with a GWBCODE_A in the form of 'city code' +'----', e.g. '0003----'. If the district and neighbourhood classification of the relevant year is already available (for the first time in the March bus), the municipality code will be supplemented with the correct district-neighbourhood code. '0003-----' then, if possible, change to e.g. '00030001'. The quarterly updates have the following approach:1. December bus (with version number VYYYY121, available on 1 March YYYY+1): New objects are added. The GWBCODE_A is extended with a new year. This GWBCODEYYY is filled for all objects with ' city code of the new year' +'----', e.g. '0003----'. Border corrections are not taken into account for this purpose.2. March bus (with version number VYYYY031, available on 1 June YYYY): New objects are added. The GWBCODE_A will be expanded for the new year (which has already been added with the December bus) with the right neighbourhood code. '0003-----' then, if possible, change to e.g. '00030001'. 3. June bus (with version number VYYYY061, available on 1 September YYYY): New objects are added. All objects are, if possible, provided with municipality code and district-neighborhood code.4. September bus (with version number VYYYY091, available on 1 December YYYY): New objects are added. All objects are, if possible, provided with municipality code and district-neighbourhood code.1x per year a coordinated=final component is delivered. The final component of year t is equal to the provisional (' actual') March-bus YYYY+1. For example, the coordinated component of fiscal year 2015 is equal to the provisional March bus of 2016, which became available on 1 June 2016. Name of coordinated versions: VSLGWBJJJJTABVVName of current versions: VRLVSLGWBTABVV The 8-digit coding of the GWBCODEYYY is made up of 4 digits for the municipality, 2 characters of the district and 2 characters of the neighborhood code. In more than 99 neighbourhoods in a municipality or in more than 99 neighbourhoods within a neighbourhood, the neighbourhood and/or neighbourhood code contains letters in addition to numbers. ### Population All objects from the Basic Register of Addresses and Buildings (BAG) and all objects that appeared in the SSB before 1-1-2012 (historical objects). In other words, all objects with provenance (ORTOBJECTNUMBER) 'B' or 'H'. It concerns not only inhabited objects, but also objects such as companies, schools, new construction objects where no one lives yet, etc. The population of this file concerns a cumulative set of RINOBJECT NUMBERS from 1995 for the inhabited objects (former RINADRESsen) and from 1998 for the other objects. The population includes at least all objects up to and including the version number of the component. So in VRLVSLGWBTABV2014031 objects occur until the beginning of April 2014. The starting point is that from the December bus (FYYYY121) the position on 1 January of the new year can also be derived. In (VRL)VSLGWBTABHISTORIE.docx (part of the standard documentation) it is stated exactly until which date the population runs. New objects are added to this file every quarter. The GWBCODE_A is also periodically extended with a new year.

Resources

Name Format Description Link

Tags

  • microdata
  • data-governance-act
  • odissei
  • dga

Topics

Categories