One governed view from daily operations to infrastructure investment planning.
A city receives reports of waterlogging, failed streetlights and waste overflow across different channels. It needs one governed map without collapsing department ownership, must deduplicate related reports, dispatch the correct crew, preserve citizen privacy, publish honest status, and analyze service equity using versioned ward and asset data.
Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.
Retain authoritative assets, work orders, ownership and service outcomes; the map does not become an ungoverned replacement master.
Layer ↔ steward, source, schema, CRS, sensitivity, version
GETStill Map Image API/{REST_KEY}/still_imageThis normalized operation matches the stage intent and remains subject to its source, lifecycle, authentication, entitlement, host, and regional gates.Record stage 1 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Keep one coordinating incident with explicit owning/participating work orders; never transfer authority by map edit alone.
mGIS registers layers, schemas, CRS, stewards, update cadence, license/sensitivity and immutable versions.
Report/alarm ↔ source identity, consent, event/receipt time, coarse/public projection
GETGets the live data of devices./deviceThis normalized operation matches the stage intent and remains subject to its source, lifecycle, authentication, entitlement, host, and regional gates.Record stage 2 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Restrict raw evidence, derive a coarse operational/public location and apply purpose-specific retention/redaction.
Normalizes citizen reports and sensor alarms, preserves each source, and derives bounded incident clusters under a versioned rule.
Derived incident ↔ member evidence IDs and correlation policy version
GETGet users attendance details with travelled distance./reports/attendancesThis is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.Record stage 3 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Version projections, display freshness, alert on reconciliation delay and correct with an attributable update.
Creates department-specific tasks, routes capable crews, tracks progress/proof and reconciles closure to the owning system.
Work order ↔ owning department, asset, SLA, task/provider identity, closure proof
GETGets the historical location events of a device./devices/{deviceId}/eventsThis is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.Record stage 4 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Keep one coordinating incident with explicit owning/participating work orders; never transfer authority by map edit alone.
Control room, department, executive and public views apply distinct access, aggregation, delay, accessibility and disclosure policy.
Layer ↔ steward, source, schema, CRS, sensitivity, version
POSTTraveled Route Image API/{REST_KEY}/still_image_polylineThis is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.Record stage 5 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Restrict raw evidence, derive a coarse operational/public location and apply purpose-specific retention/redaction.
The recipe starts from the normalized GET /tasks contract. Execute six deterministic fixture outcomes before an issued account is involved.
https://workmate.mapmyindia.com/apis/tasks?startTime=1700000000000&endTime=1700000000000&ownerId=1&assigneeId=1&clientDetails=true&activityDetails=truecurl --request GET \
--url 'https://workmate.mapmyindia.com/apis/tasks?startTime=1700000000000&endTime=1700000000000&ownerId=1&assigneeId=1&clientDetails=true&activityDetails=true' \
--header "Accept: application/json" \
--header "Authorization: Bearer ${MAPPLS_ACCESS_TOKEN}"Credential-safe by constructionSet MAPPLS_ACCESS_TOKEN only in your trusted runtime. Code generation stays local. Sandbox execution sends only bounded fixture inputs to this developer platform and never reads a credential or calls Mappls.
These controls are required at this operating depth; deeper recipes add durable truth rather than merely more API calls.
Every aggregate has an invariant, expected version, stable command identity, and attributable actor.
Duplicate, late, reordered, invalid, stale, timed-out, and restarted execution preserve one durable truth.
Unknown provider outcomes reconcile by original identity before replay or compensation.
Terminal decisions, human review, audit, outbox delivery, privacy, retention, and rollback remain independently evidenced.
/tasksGETGets the live data of devices./deviceGETStill Map Image API/{REST_KEY}/still_imageGETTo get the task details for the given task id./tasks/{taskId}GETGets the historical location events of a device./devices/{deviceId}/eventsGETElevation API/{REST_KEY}/elevationGETGet users attendance details with travelled distance./reports/attendancesGETGets drive details of a device./devices/drivesPOSTTraveled Route Image API/{REST_KEY}/still_image_polylineGETTo get form based check in/out details/reports/forms/{formId}GETGets the live data of devices./devicesGETGet users movement details/reports/movements/{userId}Coordinate a revision-safe aircraft turnaround, pause for airside exceptions, preserve four service milestones, and require independent airline, airport, and safety readiness decisions.
This recipe composes source-derived contracts, application architecture, fixtures, and maintained learning evidence. It does not prove package availability, provider payload shape, account entitlement, regional behavior, production compatibility, or release approval.