![]() |
HydroCoupleOgc
0.1.0
OGC web service clients (WMS, WMTS, WCS, WFS) over Qt Network (0.1.0)
|
OGC web service clients — WMS, WMTS, WCS, WFS, XYZ and ArcGIS REST — shared by HydroCoupleComposer and openswmm.gui.
Qt only, deliberately. In both consuming projects GDAL is built without curl: /vsicurl and CPLHTTPFetch are stubs and the WMS/WCS/WFS drivers are not registered, so GDAL cannot fetch anything. It is still used, in the consumers, to decode what this library fetches.
The library is in three tiers, and the boundary is what makes it testable:
| Tier | What | Depends on |
|---|---|---|
| capabilities | bytes -> struct parsers, URL builders, CRS URN resolution | Qt6::Core |
| fetch | HTTP, caching, cancellation, credentials | Qt6::Network |
| layers | not here — each host has its own layer contract | — |
The first tier is where the protocol risk lives, so it is pure functions over saved responses from real servers, and every test runs without a network.
Dependencies come the same way they do in the consuming projects: Qt from a Qt installation, everything else from vcpkg's manifest.
vcpkg.json declares Google Test behind a tests feature, which the presets turn on. Qt is deliberately not a vcpkg dependency — the consumers both take it from a Qt installation through CMAKE_PREFIX_PATH, and a second Qt built by vcpkg would be a second Qt in the same process.
Through FetchContent, which is how HydroCoupleComposer takes it:
Set FETCHCONTENT_SOURCE_DIR_HYDROCOUPLEOGC to a local checkout to build against that instead of a download — which is what makes editing this library and its consumer in the same session possible. An installed copy also works: find_package(HydroCoupleOgc CONFIG REQUIRED) finds the same target under the same name.
The test suites are the repository's own business and are off unless this is the project being built, so a consumer needs no Google Test of its own.
First-time contributors must sign the project CLA before a pull request can be merged. The CLA grants the project a perpetual, royalty-free copyright and patent license to your contributions and preserves the project's ability to relicense in the future; you retain full copyright ownership of your work.
Signing is automated through CLA Assistant — when you open your first PR, a bot comments with a one-click sign-in link. The CLA covers all subsequent contributions, so you only sign once. Corporate contributors should additionally submit a CCLA per CLA §6.
LGPL-3.0-or-later, and deliberately so. This library is linked by HydroCoupleComposer (LGPL) and by openswmm.gui (GPL); weak copyleft is what lets one shared library serve both.