X and Y coordinates of a residence object (from 01-10-2012)

Open data API in a single place

Provided by Centraal_Bureau_voor_de_Statistiek

Get early access to X and Y coordinates of a residence object (from 01-10-2012) API!

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

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
Verblijfsobject, ODISSEI, DGA, Locatie, Coördinaat, Data Governance Act, Microdata
Quality scoring

Dataset description

This component provides a link between an object (RINOBJECTNUMMER) and its x-coordinate (XCOORDADRES) and Y-coordinate YCOORDADRES. RINOBJECTNUMMERs without x and y coordinates are not included in this component. More information on how to access the data: > https://www.cbs.nl/nl-nl/onze-diensten/maatwerk-en-microdata/microdata-zelf-onderzoek-doen ### Methodology An object coordinate is formed by a combination of an x-coordinate and a y-coordinate.These values are only useful for the area of the Dutch projection. This is the municipal territory of the state of the Netherlands and a small area around it on the North Sea, Germany and Belgium. In this component, only objects in the Netherlands are provided with a coordinate. The values are therefore limited to locations on land and houseboat locations near land within the Netherlands.The x- and y-coordinate of an object is extracted from the Basic Registration Addresses and Buildings (BAG).For the assignment of coordinates to historical objects (which do not link to the BAG), the coordinates of the relevant objects from earlier versions of the “AdresCoordinates of the Netherlands” (ACN) file of the Kadaster were used (if available). For subsequent versions, more recent data from BAG and/or ACN will be used.As a result, as a result of quality improvement in these sources in a subsequent version of this component, an object may be assigned a different, better x and y coordinate.1x per year a coordinated = final component is delivered. The final component of year t is equal to the provisional (& current ') component version June year t+ 1. Name coordinated versions: VSLCOORDJJJTABVVName current versions: VRLVSLCOORDTABVV ### 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), i.e. all objects with origin (SOORTOBJECTNUMMER) & #039;B ' or 'H ' and of which coordinates are known. These are not only inhabited objects, but also objects such as companies, schools, new buildings where no one lives yet, etc. RINOBJECTNUMMERs without x and y coordinates are NOT included in this component.The population of this file concerns a cumulative set of RINOBJECTNUMMERs 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 VRLVSLCOORDTABV2014031 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) VSLCOORDTABISTORY.docx (part of the standard documentation) specifies exactly the date until which the population runs. This component provides a link between an object (RINOBJECTNUMMER) and its x-coordinate (XCOORDADRES) and Y-coordinate YCOORDADRES. RINOBJECTNUMMERs without x and y coordinates are not included in this component. More information on how to access the data: > https://www.cbs.nl/nl-nl/onze-diensten/maatwerk-en-microdata/microdata-zelf-onderzoek-doen ### Methodology An object coordinate is formed by a combination of an x-coordinate and a y-coordinate. These values are only useful for the area of the Dutch projection. This is the municipal territory of the state of the Netherlands and a small area around it on the North Sea, Germany and Belgium. In this component, only objects in the Netherlands are provided with a coordinate. The values are therefore limited to locations on land and houseboat locations near land within the Netherlands.The x- and y-coordinate of an object is extracted from the Basic Registration Addresses and Buildings (BAG). For the assignment of coordinates to historical objects (which do not link to the BAG), the coordinates of the relevant objects from earlier versions of the “AdresCoordinates of the Netherlands” (ACN) file of the Kadaster were used (if available). For subsequent versions, more recent data from BAG and/or ACN will be used. As a result, as a result of quality improvement in these sources in a subsequent version of this component, an object may be assigned a different, better x and y coordinate.1x per year a coordinated = final component is delivered. The final component of year t is equal to the provisional (& current ') component version June year t+ 1. Name coordinated versions: VSLCOORDJJJTABVVName current versions: VRLVSLCOORDTABVV ### 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), i.e. all objects with origin (SOORTOBJECTNUMMER) & #039;B ' or 'H ' and of which coordinates are known. These are not only inhabited objects, but also objects such as companies, schools, new buildings where no one lives yet, etc. RINOBJECTNUMMERs without x and y coordinates are NOT included in this component.The population of this file concerns a cumulative set of RINOBJECTNUMMERs 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 VRLVSLCOORDTABV2014031 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) VSLCOORDTABISTORY.docx (part of the standard documentation) specifies exactly the date until which the population runs.
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