Skip to main content
SimilarExport ZIP
100%

Identify if issue with same name in XML WMS capabilities

✓ Published0🌍 Public
TThomasG77
Last edited Nov 24, 2022
Created on Nov 24, 2022

This example checks WMS GetCapabilities XML files for duplicate layer names, which can cause issues in clients. It parses the XML using either `lxml` or Python’s built-in `xml.etree.ElementTree` via `etree.parse`, then uses XPath expressions to find all `<Layer>` and `<Name>` elements. It filters out names starting with `inspire_common:`, counts occurrences with `collections.Counter`, and prints each duplicated name or a success message. The tool accepts both remote URLs and local file paths through `argparse` and `urllib.request.urlopen`.

AI-generated description

Similar vizzes

Loading thumbnail…

OGC WFS consumption URLs from a service

This example demonstrates how to enumerate all downloadable data layers and their available output formats from an OGC Web Feature Service (WFS). Using the `@camptocamp/ogc-client` JavaScript library for the WFS endpoint, it retrieves the service metadata, layer types, and output formats, then constructs a complete GetFeature URL for every layer-format combination. The code also shows a Python equivalent using `OWSLib` to achieve the same enumeration, highlighting the interoperability of the two approaches. The visualization likely presents these generated URLs as a list or table, connecting users directly to data downloads.

TThomasG77
53% match
Loading thumbnail…

ol-ext: WMS Capabilities control

This example demonstrates the ol-ext WMSCapabilities control, which loads WMS layers onto an OpenLayers map. It shows a dialog for selecting a service and displaying available layers via the GetCapabilities request. The code uses the ol.control.WMSCapabilities API, OpenLayers map, and a Grid.js table for layer metadata. Users can search services like BRGM and Sandre, with the layer definition output to the console. The map view uses EPSG:2154 projection, and a LayerSwitcher and SearchNominatim control are also included.

TThomasG77
51% match
Loading thumbnail…

Log related to answer https://gis.stackexchange.com/questions/446578/how-does-qgis-extract-features-from-the-xml-response-of-an-inspire-wfs-server/446580

This example shows a debug log from a GDAL/OGR-based workflow that extracts cadastral parcel features from an INSPIRE WFS server and writes them to a GeoPackage. The log details sequential GDAL API calls, including `GDALOpen`, `GDALDriver::Create`, and repeated HTTP `Fetch` requests, revealing how the WFS driver negotiates capabilities, disables multi-layer definitions, and paginates through `GetFeature` requests. It also demonstrates the internal use of an Expat XML parser for GML reading and a temporary in-memory file (`/vsimem/tempwfs_0x21f0b20/file.gml`) to process the downloaded data. The output shows the explicit `STARTINDEX` and `COUNT` parameters used to fetch batches of up to 10,000 features.

TThomasG77
49% match
Loading thumbnail…

Get IGN legends for WMS Raster, WMS Vecteur and WMTS webservices

This example visualizes the availability of legends for IGN web services, specifically WMS Raster, WMS Vecteur, and WMTS layers. It shows that 241 out of 598 services have retrievable legend images, while 357 do not. The code downloads a CSV of service metadata from the IGN geoportal, then probes a guessed URL pattern on the geoportail.gouv.fr domain for each layer's legend image using `curl`. Successful results are compiled into an augmented CSV and JSON file, with the legend images stored locally.

TThomasG77
45% 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
45% match
Loading thumbnail…

Gist 2bd25e856943977444bac9a5fd8c6408

This example shows a QGIS workflow for automatically populating the application with WMS, WMTS, and WFS service connections from the French IGN geoservices portal. The script scrapes the portal’s documentation page to find a CSV file containing service metadata, parses it using the `csv` module, and deduplicates entries via Python dictionaries. It then defines functions to add or remove connections in QGIS’s settings using `QgsSettings`, configuring parameters like URLs, versions, and axis orientation. The code demonstrates a practical approach to batch-importing OGC web services into a desktop GIS environment.

TThomasG77
45% match
Loading thumbnail…

Leaflet WMS

This example shows a map centered on a region in France, displaying both urban areas from a French government WMS layer alongside a French statistical data layer, with a scale bar. Built with the Leaflet JavaScript library, it combines OpenStreetMap tiles with two Web Map Service (WMS) layers. The first WMS source, accessed via a proxy from `data.europa.eu`, uses `L.WMS.source` and `source.getLayer("Tache_urbaine_1980_R43")`, while the second uses `L.tileLayer.wms` to load INSEE income data from an IGN endpoint.

TThomasG77
44% match
Loading thumbnail…

Third title

This example demonstrates how to use XPath queries with lxml to extract data from both HTML and XML documents. It shows techniques for selecting elements by tag name, attribute values, and text content, as well as navigating the document tree with axes like `following-sibling` and the `..` operator. The code uses `lxml.html.fromstring` and `lxml.etree.fromstring` to parse content fetched from a live website and a hardcoded XML sample, respectively. It highlights namespace handling in XML, showing that prefixed queries require explicit namespace mapping, while unprefixed queries fail without a default namespace binding. The example also illustrates retrieving attribute values like `setCount` and iterating over all elements with `getiterator`.

IIanHopkinson
44% match