Skip to Content
GeocodingReferenceData and metrics

Data and metrics

For: developers and platform owners.

Where each resolution is stored and what you can measure.

Tables

TableOne row perWhat it stores
miot_trips.locationLocationWhat was declared (address, country, district_code, district_name), the point (latitude, longitude, plus_code), resolution_source, resolution_status, resolution_note and geofence_id
miot_trips.geocode_cacheAddress, district and countryThe point, the source and the provider. Shared by all organizations. No organization, place name or provider response
miot_integrations.geocode_usageResolution by POST /resolve or by a feed siteOrganization, user, source, result, provider, whether it was a cache hit, whether the provider was called and its cost
miot_integrations.geocoding_plan(one row)The plan
miot_integrations.geocoding_subscriptionsSubscribed organizationOwn quota, what happens when it runs out and the last month alerted
miot_integrations.geocoding_billing_historyChange to the plan or to a subscriptionCopy of the terms with the date they take effect
miot_trips.audit_eventChange to a locationWho, which action and the details
miot_integrations.async_jobsFeed serviceThe job that applied the service and, in result.located, which locations it tried

geocode_usage

ColumnValue
organizationIdentifier of the organization whose quota was used
tenant_idTenant of the organization’s GPS data
user_idUser, service account or feed:<feedKey>
sourcegeofence, plus_code, coordinates, internal, provider, or null if no source gave a point
resultresolved or needs_review
providermapbox or google: the provider called (even if the call failed) or the cache’s provider
cache_hittrue if the cache answered
provider_calledtrue if the provider answered. This is what counts toward the quota
cost_usdThe platform connection’s costPerRequestUsd at that moment, only if provider_called
recorded_atDate

Placing by hand (PUT /point) and rejecting write no rows.

A month’s usage by source:

SELECT source, result, count(*) AS resolutions, count(*) FILTER (WHERE cache_hit) AS cache_hits, count(*) FILTER (WHERE provider_called) AS provider_calls, sum(cost_usd) AS provider_cost_usd FROM miot_integrations.geocode_usage WHERE organization = 'demo' AND recorded_at >= '2026-10-01' AND recorded_at < '2026-11-01' GROUP BY 1, 2 ORDER BY 1, 2;

audit_event

actionWhendetails
location.createdA location is created (through the API, by /resolve or by a feed)name, type
location.resolvedA resolution or a manual point ends resolvedstatus, source, geofenceId
location.needs_reviewA resolution ends in reviewstatus, source, geofenceId
location.rejectedSomeone rejects the location
location.updatedPATCH of the location
location.geofence_linkedSomeone links a geofence by handgeofenceId

entity_type is location and entity_id is the location’s id. actor is the user, the service account or feed:<feedKey>.

async_jobs

Each service in a feed batch is a trips_feed_service job, with the service code in correlation_key. After applying the service, the job locates the origin and the destination and leaves the result in result.located:

{ "action": "create", "tripId": "…", "located": ["GEO-PROV-ORIGEN-2: resolved"], "errors": [], "warnings": [] }

Each element is code: status, or code: could not resolve site if it failed. Without sites tried, located does not appear. An error while locating does not fail the job. You see the jobs in Integrations › Job console; the result is in the Payload tab.

Metrics

The platform publishes these metrics (Micrometer). In Prometheus the dots become _ and counters end in _total.

MetricTypeTagsMeasures
geocoding.resolutionsCountersource (none if none), resultResolutions
geocoding.cache.lookupsCounterresult: hit, missCache lookups
geocoding.provider.latencyTimer (in Prometheus, geocoding_provider_latency_seconds_count, _sum, _max)provider, outcome: found, emptyDuration of each provider call
geocoding.provider.errorsCounterprovider, reason: no_connection, config, io, interruptedCalls that were not made or failed
geocoding.quota.refusalsCountercode: geocoding_no_subscription, geocoding_quota_exhaustedCalls refused by the quota
geocoding.quota.usedGaugeorganizationThe month’s calls, at the last calculation
geocoding.quota.limitGaugeorganizationThe month’s quota

Example, cache hit rate in the last hour:

sum(increase(geocoding_cache_lookups_total{result="hit"}[1h])) / sum(increase(geocoding_cache_lookups_total[1h]))

Quota event

When an organization reaches the alertPct of its quota, the platform publishes the geocoding.quota.threshold event once per month (source miot-integrations, context geocoding_quota):

FieldExample
organizationdemo
month2026-10
used800
quota1000
usedPct80
onExhaustedreview

The event does not send messages on its own. To receive an alert, create a conversation rule on that event in the organization.

Last updated on