CSW Nationaal Georegister (NGR)

100%

CSW Nationaal Georegister (NGR)

✓ Published0🌍 Public

Last edited Jul 5, 2018

Created on Jul 4, 2018

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.

AI-generated description

Similar vizzes

Loading thumbnail…

ArcGIS Online hosted feature service in lezen in R

This example demonstrates how to read and visualize the Dutch national heritage register (Rijksmonumenten) from an ArcGIS Online hosted feature service. It shows the full workflow of querying the service's metadata, counting features, and paginating through all 64,020 records, then maps them with `tmap` and `sf`. The code uses the `httr` and `jsonlite` packages to construct URL requests and parse JSON, while `sf::st_read()` reads the GeoJSON response. It explicitly checks pagination support via the service’s `advancedQueryCapabilities` and explains an anomaly where the initial page returns more records than `maxRecordCount` suggests. The final map is rendered with `qtm()`, and summary statistics (min/max OBJECTID) are computed via the service’s `outStatistics` parameter.

FFrieseWoudloper

61% 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

59% match

Loading thumbnail…

R script om te demonstreren hoe je WFS paging kunt implementeren in R

This example shows how to retrieve all Dutch address objects (verblijfsobjecten) in the town of Zuidhorn from the BAG Web Feature Service (WFS) using paging to handle large result sets. The code first queries the server’s maximum page size via GetCapabilities, then counts matching features, and finally fetches them page by page using `startindex` while sorting by identifier. It uses the `httr`, `xml2`, and `sf` R packages to parse the WFS responses and convert the resulting GeoJSON into simple features, which are then mapped with the `tmap` package. The data source is the national georegister’s BAG WFS endpoint.

FFrieseWoudloper

59% match

Loading thumbnail…

API request OData CBS

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.

FFrieseWoudloper

57% match

Loading thumbnail…

Simple example of requesting items from the SRU gateway at the Library of Congress

This example demonstrates how to query the Library of Congress SRU gateway for a single bibliographic record, using the Library of Congress Control Number (LCCN) as the search key. It shows how to request metadata in a specific format—here, MODS, though DC and MARCXML are also supported—and then extract the record data from the SRU XML response. The code relies on the `http:send-request` function from the EXPath HTTP Client to perform the GET request, and uses XQuery 3.0 with namespace declarations for MODS, Dublin Core, MARCXML, and the SRU/Z39.50 protocol. The returned record is selected via the `zs:recordData` path.

CCliffordAnderson

56% match

Loading thumbnail…

Simple example of retrieving a record in EAD (or Dublin Core) from the Archives Hub using SRU

This example demonstrates how to retrieve a single metadata record from the Archives Hub using the SRU (Search/Retrieval via URL) protocol, converting it into a specified format such as EAD or Dublin Core. It shows a live HTTP query to the Archives Hub API, where the user can adjust the search keyword and the desired metadata schema (e.g., "ead", "srw_dc", or "oai_dc"). The code uses XQuery 3.0 with the `http:send-request` function to fetch the XML response, then extracts the record data via the SRU namespace. The result is the raw metadata record, ready for display or further processing.

CCliffordAnderson

55% match

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

54% match

Loading thumbnail…

Geocoding example - uses PDOK LocationServer

This example demonstrates geocoding Dutch childcare locations by mapping street addresses to geographic coordinates. It shows the first 100 entries from a national childcare registry, displaying their matched BAG object IDs and centroid coordinates. The code uses the `httr` package to query the PDOK LocationServer API, while `dplyr` and `purrr` handle data manipulation and iterative geocoding. The input data is sourced from a CSV file provided by the Landelijk Register Kinderopvang. Each address is processed through the API’s free endpoint, returning the closest match’s details, which are then combined with the original dataset for display.

FFrieseWoudloper

52% match