Products/Data operations
hybrid2 platforms6 source families
Keep location truth fresh

Capture & Feedback

On-demand location capture, camera evidence, map feedback, and update workflows.

Start building Get credentials

Capture a trustworthy position with explicit accuracy and timeout budgets, attach camera or form evidence, and submit map feedback through user-friendly SDK surfaces. This family helps delivery, insurance, survey, compliance, and citizen apps prove where an action happened and improve the map safely.

Capabilities

Single-shot and subscribed locationProduction guidance, platform support, examples, and operational considerations included.01
Accuracy and timeout policiesProduction guidance, platform support, examples, and operational considerations included.02
Camera and field evidenceProduction guidance, platform support, examples, and operational considerations included.03
Map issue reportingProduction guidance, platform support, examples, and operational considerations included.04
Reviewable update workflowsProduction guidance, platform support, examples, and operational considerations included.05
Battery-aware captureProduction guidance, platform support, examples, and operational considerations included.06

Available platforms

Keep business identifiers and server-side policy portable; use the native surface where device integration or long-lived state matters.

SDK entitlement and user consent

Request the minimum device permission needed, retain evidence only for the declared purpose, and make capture policy visible to the user. The repository snapshot documents entitled SDK operations; direct REST access remains selection-required until an authoritative HTTP contract is supplied.

  • Use separate projects for development, staging, and production.
  • Apply the narrowest domain, IP, platform, product, and resource scopes available.
  • Never ship a server secret in a browser bundle, mobile binary, prompt, or public repository.

Quickstart

Replace placeholders with credentials from the developer console. Examples include the lifecycle and failure-handling context that short snippets usually omit.

Capture & Feedback quickstart
struct CapturePolicy {
  let desiredAccuracyMeters: Double
  let timeoutSeconds: TimeInterval
  let acceptsCachedLocationSeconds: TimeInterval
}

let policy = CapturePolicy(
  desiredAccuracyMeters: 25,
  timeoutSeconds: 12,
  acceptsCachedLocationSeconds: 5
)

// Pass the equivalent policy into the entitled Mappls Location Capture SDK.
// Always handle permission denial, timeout, and insufficient-accuracy states.
Before productionRestrict and rotate credentialsHandle timeouts and typed errorsAdd tracing without logging secretsTest quota and degraded-mode behavior

Operate the complete lifecycle

These blueprints name every state, actor, command, event, invariant, durable record, retry boundary, failure recovery, source contract, and operational signal.

Browse all stateful journey blueprints

Source repositories

Reference content is reconciled against these public and private source families. Version, authentication generation, and maturity are recorded before content is promoted.

Browse all 60 related integration guides