![]() |
HydroCoupleOgc
0.1.0
OGC web service clients (WMS, WMTS, WCS, WFS) over Qt Network (0.1.0)
|
What a WFS server offers, and how to ask it for features. More...
#include "hydrocoupleogc/crsurn.h"#include "hydrocoupleogc/export.h"#include <QByteArray>#include <QList>#include <QRectF>#include <QString>#include <QStringList>Go to the source code of this file.
Classes | |
| struct | HydroCouple::Ogc::WfsFeatureType |
| One collection of features a WFS publishes. More... | |
| struct | HydroCouple::Ogc::WfsCapabilities |
| What a WFS server said about itself. More... | |
Namespaces | |
| namespace | HydroCouple |
| namespace | HydroCouple::Ogc |
Functions | |
| HYDROCOUPLEOGC_EXPORT WfsCapabilities | HydroCouple::Ogc::parseWfsCapabilities (const QByteArray &xml) |
| Reads a WFS GetCapabilities response. | |
What a WFS server offers, and how to ask it for features.
WMS and WMTS answer with pictures of data. A WFS answers with the data, which is what makes it the one service in this library that can put a catchment boundary into a model rather than merely behind one.
Its capabilities document is shaped like WMTS's — OWS operations metadata, a flat list of what is published — with one difference that matters: what a feature type is published in and what it can be asked for are per type, not per service. A server may hold one layer in the national grid and another in WGS 84.