Documentation
DocumentationGeographic eligibility
DOCS / UWA V1 RELEASE CONTRACT SELF-HOSTED GATEWAY

Geographic eligibility

Coverage must be proven, and returned coordinates are checked against drift ceilings.

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

#Fail closed eligibility

Provider eligibility combines request coordinates, operator-reviewed product rules, provider coverage, deployment use and country polygons where applicable. A globally shaped API request does not imply a global provider licence or local station observation.

#Coordinate drift ceilings

To prevent gross upstream misrouting from being served or cached, ValidateRequestedLocation in internal/normalization/request_location.go enforces maximum great-circle distance ceilings between requested coordinates and upstream-reported coordinates:

  • OpenWeather, WeatherAPI, Open-Meteo Forecast: maximum 50 km discrepancy.
  • MET Norway, Bright Sky / DWD, US NWS Forecast, Open-Meteo Marine: maximum 25 km discrepancy.

Responses exceeding these tolerances are rejected as malformed and trigger eligible fallback.

#Regional data and polygons

US NWS forecast and active alerts are US-only and require a reviewed APP_COUNTRY_POLYGONS_FILE. Bright Sky covers Germany and supported DWD grid regions. Both are gated under full_experimental until regional operator acceptance is completed.

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