Parse WFS response in R

100%

Parse WFS response in R

✓ Published0🌍 Public

Last edited Jul 31, 2018

Created on Jul 31, 2018

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.

AI-generated description

Similar vizzes

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

72% match

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

64% match

Loading thumbnail…

sf only supports request paging for ESRI’s hosted feature service, not for WFS

This example compares pagination behavior in R’s `sf` package for two web service types. It demonstrates that while `sf` automatically pages through ESRI hosted feature services, fetching all records, it does not for WFS endpoints, where only the first batch of records is retrieved despite the presence of a `next` URL in the response. The analysis uses live API queries to BAG WFS and ArcGIS services, with code in R and visualizations rendered via R Markdown. The title and author metadata are shown at the top.

FFrieseWoudloper

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

59% match

Loading thumbnail…

met wfs en geojson als output formaat

This example shows how to load and display GeoJSON data that has been retrieved from a WFS (Web Feature Service) and converted to TopoJSON format. The map renders the Dutch municipal boundaries as SVG paths using D3 v4. The data pipeline is notable: GeoJSON in EPSG:4326 is fetched from a WFS, the winding order of the polygons is reversed in FME, and the result is written to TopoJSON. The visualization displays the topology-encoded arcs, demonstrating the boundary polygons of Dutch municipalities with a minimal, functional style typical of D3 examples.

FFrieseWoudloper

59% match

Loading thumbnail…

Adapted the script by Yonhah: https://github.com/yonghah/esri2sf/blob/master/R/esri2sf.R

This example demonstrates how to fetch GIS feature data from an ArcGIS REST server and convert it into simple features for spatial analysis in R. It shows a workflow that queries a specified layer, retrieves object IDs, and then pulls the corresponding attributes and geometries as GeoJSON. The code relies on the `httr` package for HTTP requests, `jsonlite` for parsing JSON responses, and `sf` for handling spatial data. It also includes a helper function to generate authentication tokens when the server requires login. The implementation uses the ArcGIS REST API's `query` endpoint to request data in batches of 500 IDs, ensuring efficient retrieval of large datasets.

FFrieseWoudloper

58% match

Loading thumbnail…

Oefenen met scale

This example demonstrates how to load and display geographic boundary data from a Web Feature Service (WFS) endpoint using D3.js. It shows a map of Dutch arrondissementsgebieden (judicial districts) for 2019, projected with a Mercator projection. The code uses `d3.json` to fetch GeoJSON from the national georegister WFS, then renders it as SVG paths via `d3.geo.path` with a `d3.geo.mercator` projection. A simple alert greets viewers before the visualization loads, and the SVG canvas is sized to 960 by 500 pixels.

FFrieseWoudloper

57% match

Loading thumbnail…

R-script voor het downloaden en converteren van een JSON-bestand met locaties van jachthavens converteren naar shape-bestand

This example demonstrates how to download JSON data containing marina locations from a Dutch tourism website and convert it into a shapefile. The script shows the process of fetching data via an HTTP POST request with a custom header, parsing the JSON response, extracting attributes like address and contact details from nested HTML, and then transforming geographic coordinates from WGS84 to the Dutch RD coordinate system using the `sp` and `rgdal` packages. It uses `httr` for the API request, `jsonlite` for JSON parsing, and `XML` for handling HTML content within the JSON. The final shapefile is written with `writeOGR`.

FFrieseWoudloper

55% match