1. OGC API Features
In the QGIS Data Source Manager, open WFS / OGC API – Features. Create a connection with the root URL, connect, and choose a collection.
https://qgeo.tech/ogc/Working with geodata
Connect to QGIS
CRS, formats, access, limitations, and errors for a stable QazGeo connection.
2. Coordinates and filters
GeoJSON: CRS84, longitude → latitude. bbox: west,south,east,north. Records without geometry are preserved. datetime validates the format: collection objects have no observation time, so they match any valid period.
curl --fail --silent --show-error 'https://qgeo.tech/ogc/collections/regions/items?bbox=69,50,73,53&limit=5'3. Saving GeoJSON
Open the file as a QGIS vector layer. Save HTTP headers, provenance, and SHA-256 alongside it. If a next link is present, the file is not the full collection. Server data may change.
curl --fail --silent --show-error --dump-header territories.headers --output territories.geojson 'https://qgeo.tech/ogc/collections/regions/items?limit=100'
curl --fail --silent --show-error --output provenance.json 'https://qgeo.tech/provenance.json'
shasum -a 256 territories.geojson territories.headers provenance.json > territories.sha2564. Handling errors
Public OGC GET requests work without a key. 400 – invalid parameter; 404 – object not found; 429 – reduce frequency (respect Retry-After when present); 5xx – temporary failure, retry with limited delay. Distinguish an empty result from a failure.
curl --silent --show-error --include 'https://qgeo.tech/ogc/collections/regions/items?limit=0'5. Version and limitations
The HTTP contract is described in OpenAPI 3.1. QGIS application testing is separate from HTTP/API testing; no QGIS version certification is claimed here. Check the changelog and collection limitations.
curl --fail --silent --show-error 'https://qgeo.tech/ogc/'
curl --fail --silent --show-error 'https://qgeo.tech/ogc/collections/regions'