HydroCoupleOgc  0.1.0
OGC web service clients (WMS, WMTS, WCS, WFS) over Qt Network (0.1.0)
Loading...
Searching...
No Matches
wmscapabilities.h File Reference

What a WMS server says it can do, read off its GetCapabilities. More...

#include "hydrocoupleogc/export.h"
#include <QByteArray>
#include <QRectF>
#include <QString>
#include <QStringList>
Include dependency graph for wmscapabilities.h:
This graph shows which files directly or indirectly include this file:

Go to the source code of this file.

Classes

struct  HydroCouple::Ogc::WmsLayerInfo
 One layer a WMS offers. More...
 
struct  HydroCouple::Ogc::WmsCapabilities
 What a WMS server said about itself. More...
 

Namespaces

namespace  HydroCouple
 
namespace  HydroCouple::Ogc
 

Functions

HYDROCOUPLEOGC_EXPORT WmsCapabilities HydroCouple::Ogc::parseWmsCapabilities (const QByteArray &xml)
 Reads a WMS GetCapabilities response.
 

Detailed Description

What a WMS server says it can do, read off its GetCapabilities.

Author
Caleb Buahin

A pure function over bytes. It performs no I/O, owns no network, and knows nothing about layers or painting, so the awkward half of talking to a WMS — which is reading what the server claims — can be checked against saved responses from real servers rather than against a live one.

That is the whole reason this is separate from the layer that draws the imagery. The same code in openswmm.gui is entangled with QNetworkReply slots and layer state, and has no tests at all.