City, neighbourhood and neighbourhood codes of a residence object (01-01-2019-01-01-2020)

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. The first four positions of the GWBCODEYYYY are the municipal code, or the variable GEMYYYY.The first four positions of the GWBCODEYYYY are the municipal code, or the variable GEMYYY. Using procedure 'PARTMENTST4 ' can be derived from the GWBCODEJJJJ the variable GEMJJJJ.This file can therefore be used for assigning the municipal code to objects as well as for assigning the municipal district-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 & municipality code ' + '--------#039; e.g. '0003------#039;. If the district and neighbourhood layout of the relevant year is already available (for the first time in the March bus) then the municipal code will be supplemented with the correct district-neighbourhood code. '0003------#039; 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 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;. This does not take into account border corrections.2. March bus (with version number VYYYJ031, available on 1 June YYYY): New objects are added. The GWBCODE_A will be expanded with the right neighbourhood code for the new year (which has already been added with the December bus). '0003------#039; then, if possible, change to e.g. '00030001 '. 3. June bus (with version number VYYYJ061, available on 1 September YYYY): New objects are added. If possible, all objects will be provided with city code and district-neighborhood code.4. September bus (with version number VYYJJ091, available on 1 December YYYY): New objects are added. If possible, all objects are provided with municipal code and district-neighborhood code.1x per year a coordinated = final component is delivered. The final component of year t is the provisional (& current ') March-bus JJJJ+ 1. For example, the coordinated component of reporting year 2015 is the same as the 2016 preliminary March bus, which became available on 1 June 2016. Name Coordinated Versions: VSLGWBJJJJTABVVName 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 businesses, schools, new buildings where no one lives yet, etc.The population of this file concerns a cumulative set of RINOBJECTNUMMERs from 1995 for the inhabited objects (formerly 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.Every quarter new objects are added to this file. The GWBCODE_A is also periodically extended to include a new year.本组件用于建立对象（RINOBJECTNUMMER）与其所属市政区域、行政区或街区之间的关联，关联标识为GWBCODE_A（GWBCODE_A）。 更多数据访问相关信息，请参阅： https://www.cbs.nl/nl-nl/onze-diensten/maatwerk-en-microdata/microdata-zelf-onderzoek-doen ### 方法学说明 GWBCODE 与年份相关，更多细节请参阅该变量的官方说明。本组件中，GWBCODEJJJ 以数组形式包含，对应标识为GWBCODE_A（GWBCODE_A）。即，在此文件中，尽可能为每个对象提供1999年、2000年、2001年、2002年等多个年份的GWBCODE，即便该对象仅自2004年起才存在。 GWBCODEYYYY 的前四位为市政区域代码，对应变量为GEMYYYY；原文此处存在重复表述，实际GWBCODEYYYY的前四位对应市政代码，即变量GEMYYYY。通过执行`PARTMENTST4`（PARTMENTST4）流程，可从GWBCODEJJJJ（GWBCODEJJJJ）中提取变量GEMJJJJ（GEMJJJJ）。因此，本文件既可用于为对象分配市政区域代码，也可用于为对象分配行政区-街区代码。 本组件的更新频率据此进行了优化：每季度新增的对象将被赋予格式为「市政代码 + '--------'」的GWBCODE_A，例如「0003------」。若对应年份的行政区与街区划分数据已就绪（首次在三月批次中提供），则会为市政代码补充正确的行政区-街区代码，例如将「0003------」优化为「00030001」。季度更新遵循以下流程： 1. 十二月批次（版本号VYYYY121，于次年3月1日上线）：新增对象，为GWBCODE_A扩展新的年度字段。所有对象的GWBCODEJJJY将被填充为「新年度市政代码 + '--------'」，例如「0003------」，此流程未考虑区域边界调整。 2. 三月批次（版本号VYYYJ031，于当年6月1日上线）：新增对象，为已通过十二月批次纳入的新年度GWBCODE_A补充正确的街区代码，例如将「0003------」优化为「00030001」。 3. 六月批次（版本号VYYYJ061，于当年9月1日上线）：新增对象，尽可能为所有对象补充市政代码与行政区-街区代码。 4. 九月批次（版本号VYYJJ091，于当年12月1日上线）：新增对象，尽可能为所有对象补充市政代码与行政区-街区代码。 每年将交付一次经过协调的最终版本组件。年度t的最终版本对应次年t+1的临时三月批次。例如，报告年度2015的协调版本等同于2016年临时三月批次，该批次于2016年6月1日上线。协调版本命名格式为：VSLGWBJJJJTABVV；当前版本命名格式为：VRLVSLGWBTABVV。 ### 覆盖对象范围 本组件覆盖的对象包括来自地址与建筑基础登记系统（Basic Registration Addresses and Buildings, BAG）的全部对象，以及2012年1月1日前曾出现在SSB系统中的所有历史对象。换言之，所有源标识（SOORTOBJECTNUMMER）为`'`或`'H'`的对象均纳入覆盖范围。此类对象不仅包括居住建筑，还涵盖商铺、学校、尚未投入使用的新建楼宇等。 本文件的覆盖对象为累计数据集：居住类对象（原称为RINADRESsen）的累计数据始于1995年，其余对象的累计数据始于1998年。本文件至少包含截至组件版本发布时的全部对象。例如，在版本VRLVSLSLGWBTABV2014031中，覆盖的对象截止至2014年4月初。需说明的是，从十二月批次（版本号VYYY121）起，可同步获取次年1月1日的对象快照。标准文档附件(VRL)VSLGWBTABHISTORY.docx 明确说明了本文件覆盖对象的截止日期。本文件每季度都会新增对象，同时GWBCODE_A也会定期扩展以纳入新的年度数据。