Provenance

How a coordinate was established — a distinct axis from precision (how exact the point is) or confidence (how much it's trusted). A user_confirmed point can be spatially rough; a third_party_match point can be spatially precise and confidently wrong.

sourcestring

device_gps: a live GPS/network/fused fix reported by a device at request time. geocoded_text: inferred purely from parsing/matching text or grid math, no real-world confirmation. third_party_match: matched against an external dataset (OSM, Google Open Buildings, GhanaPostGPS's own registry) without independent confirmation on the ground. user_confirmed: explicitly entered/confirmed by the address owner. agent_verified: independently confirmed by a human or a real event — a field agent's manual promotion, a signed proof-of-delivery — the strongest tier.

Possible values: [device_gps, geocoded_text, third_party_match, user_confirmed, agent_verified]

Example: agent_verified

providerstring

The upstream/system that produced the point (e.g. "ghanapostgps", "osm", "google_open_buildings", "customer_app"), separate from source's trust tier.

Example: ghanapostgps

accuracy_metersnumber<double>

A physical measurement (GPS accuracy, computed drift, snap distance) — independent of confidence.

confidencenumber<double>

Trust score, 0.0–1.0.

Possible values: >= 0 and <= 1

Example: 0.85

verified_atstring<date-time>

Provenance

{
  "source": "agent_verified",
  "provider": "ghanapostgps",
  "accuracy_meters": 0,
  "confidence": 0.85,
  "verified_at": "2024-07-29T15:51:28.071Z"
}