API request OData CBS

100%

API request OData CBS

✓ Published0🌍 Public

Last edited Nov 19, 2018

Created on Nov 10, 2018

This example demonstrates the structure and querying of CBS (Statistics Netherlands) open data via its OData API, showing how different URL patterns access metadata, raw datasets, and filtered subsets. The visualization highlights the API’s flexibility by contrasting `$top`, `$skip`, `$filter`, and `$format` parameters across both untyped and typed data feeds. It uses the `$metadata` endpoint to reveal the dataset schema, while the queries return JSON-formatted rows for geographic units like neighborhoods. The rendering relies on standard browser fetch or XMLHttpRequest for these OData requests, with no external visualization libraries—the focus is purely on data retrieval patterns and response structures.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist ed318d44833c6e35336fbf5dff774017

This example visualizes Dutch neighborhood-level geographic data by combining CBS microsubsidy statistics with municipal boundary geometries. It first fetches neighborhood polygons from the national georegister WFS service, parsing the Well-Known Text geometry strings, and then joins these with the statistical dataset. The visualization maps the subsidy figures onto the neighborhood shapes, likely using a choropleth approach to show geographic distribution. The code relies on the `cbsodata` API for the statistical data and pandas for data manipulation, while the geometries are loaded directly from the WFS endpoint.

FFrieseWoudloper

67% match

Loading thumbnail…

CBS Dataviz nL

This visualization shows the number of Dutch people vacationing in the Netherlands per quarter, comparing 2019 data with 2020 (the Corona year) via an interactive checkbox. D3 v6 renders animated SVG bars that grow from the baseline when switching between years, using `d3.scaleLinear` and `d3.scaleBand` for axes. The data comes from a GitHub-hosted CBS JSON endpoint, with all bars transitioning smoothly over two seconds via D3's `.transition()` method.

NNathan Neelis

58% match

Loading thumbnail…

CSW Nationaal Georegister (NGR)

This example demonstrates how to query and explore the Dutch National Georegister's Catalog Service for the Web (CSW) through a series of URL-encoded HTTP requests. It shows the service’s capabilities, including fetching dataset metadata in Dublin Core and ISO 19119 formats, filtering records by text (e.g., "water"), counting hits, and retrieving domain values for the `organisationName` parameter. The code relies on standard XML/HTTP requests to the CSW endpoint, with explicit use of parameters like `GetRecords`, `GetDomain`, `DescribeRecord`, and `maxRecords`, and highlights the need for URL encoding and the service's timeout limitations on large queries.

FFrieseWoudloper

57% match

Loading thumbnail…

Loading CBS data

This example demonstrates how to load and parse a semicolon-delimited CSV file from a remote URL using D3 v6. It fetches age-related statistics from a CBS dataset via `d3.dsv` with a semicolon delimiter, then logs the parsed data array to the browser console. The page displays a large title but no visual chart, focusing instead on the data-loading and parsing workflow. The code relies on D3’s promise-based `d3.dsv` method and the `then` callback to handle the asynchronous response.

LLaurens

56% match

Loading thumbnail…

Some refactored API live coding

This example demonstrates a live-coding workflow for inspecting and cleaning data fetched from the Dutch RDW open-data API (`https://opendata.rdw.nl/resource/t5pc-eb34.json`). It fetches the raw JSON using the `fetch` API within an `async` function, then maps results down to a single selected column (`areaid`). With the filtered array, the code logs all data, a single record, and the cleaned column values, then uses a `Set` to list unique entries and filters for values containing "WEST". The visualization is limited to console output, with no graphical rendering.

Ddavidvanr21

54% match

Loading thumbnail…

Some refactored API live coding

This example demonstrates a live-coded workflow for inspecting and cleaning data from the Dutch government’s open-data API for road traffic information, accessed via the `fetch` API. It fetches JSON from the RDW endpoint, extracts values from a specified column (`areaid`), and then logs unique values and filters entries containing “WEST” using standard JavaScript array methods. The code shows a step-by-step refactoring process, with console output at each stage, but does not render a visualization. It uses no external libraries, relying solely on native JavaScript functions like `Set` for deduplication.

LLaurens

54% match

Loading thumbnail…

Live API Coding - By Laurens

This example fetches live data from the RDW Open Data API using the `fetch` function, starting with the endpoint `https://opendata.rdw.nl/resource/t5pc-eb34.json`. It retrieves the JSON response, logs the full dataset and the first record, and then applies a custom `filterData` function to extract all values for the `areaid` column. The code also defines a `listUnique` function to identify unique values in an array, though it is not called in the visible flow. The page itself is minimal, with no visual output—only console logging and basic HTML/CSS styling.

Ddavidvanr21

54% match

Loading thumbnail…

Parse WFS response in R

This example demonstrates how to inspect a WFS service’s capabilities and identify its supported output formats and available feature types, along with the server’s maximum result limit. The R script uses the `XML` package to parse the `GetCapabilities` response from the Dutch national georegister’s CBS boundary service, applying XPath queries to extract `ows:Value` texts and `wfs:Name` entries. It also reads the `CountDefault` constraint to determine the per-request cap. The output shows the parsed metadata as character and integer vectors, revealing the service’s configuration without fetching any actual geographic data.

FFrieseWoudloper

53% match