Documentation
DocumentationProvider configuration
DOCS / UWA V1 RELEASE CONTRACT SELF-HOSTED GATEWAY

Provider configuration

An adapter in source is not an activated or certified integration.

ONE GATEWAYCoordinates → eligible provider → canonical responseWhy UWA
On this page 3 sections

#Activation and release profiles

Provider registration in cmd/gateway/providers.go is governed by credentials, explicit opt-in flags, and the active release profile (lean_v1 vs full_experimental). Public Nominatim is never registered by default. In production and staging, every registered provider must also have an explicit entry in APP_PROVIDER_QUOTAS_JSON or startup fails closed.

#Inventory and schema catalog

The provider matrix and internal/normalization/catalog.go define the 15 source adapters across current weather, forecast, geocoding, astronomy, air quality, history, marine and alerts. Inspect credentials, coordinate drift ceilings and restrictions individually.

#Licensing

UWA’s MIT source licence does not grant third-party weather data rights. Before enabling any upstream, verify that provider’s current terms, public-service usage policy, attribution, quota, commercial status and caching permissions.

Canonical contracts: docs/openapi.yaml (lean_v1) and docs/openapi.experimental.yaml · Verify against your build before production use.

Search local documentation. No external requests.

↑↓ to move · Enter to openESC to close