District Signal Studio
Seven weeks for analysts and product managers who ship location features and still cannot walk a stakeholder through drop-off between “entered zone” and “completed action”.
Who it is for
You already have an SDK, a map, and a dashboard. What you lack is a schema that survives sparse GPS, overlapping fences, and the PDPA conversation that arrives after the first press mention. Teams of two (PM + analyst) get more from the room than solo attendees, though both are welcome.
It is not an introduction to SQL, and it is not a GIS degree. If you have never opened your app’s location event table, start with a Walkthrough Seat instead.
Modules
- 01
Permission ethics and consent states
OS dialogues, precise-location toggles, background updates, and why “location off” is a segment rather than missing data.
- 02
Event schemas for fence, dwell, and path
Naming rules, doubt columns, and the difference between an observed ping and an inferred visit.
- 03
Attribution windows that survive sparse GPS
How to credit a conversion when the trace has holes, without inventing presence.
- 04
Heatmaps versus corridor models
Why density flattery misleads, and how to sketch BTS and soi corridors before you chart.
- 05
Cohorting by district, not just city
Bangkok districts, provincial towns, and the error of treating “Thailand” as one mobility regime.
- 06
Thailand and SEA data quirks
Address systems, mall indoor dead-zones, and transfer halls that break naive geofences.
- 07
Capstone: a Bangkok F&B funnel
Rebuild visit-to-order for a multi-branch app. Present to the instructor bench with limitations in writing.
What you should be able to do afterwards
- Defend a location metric in a product review, including the cases where you should not quote it.
- Write an event schema that records consent state alongside geometry.
- Resolve overlapping geofences with an explicit priority rule.
- Produce a one-page attribution memo a privacy counsel can annotate.
Instructor
Kanya Rattanaporn
Kanya spent a decade as a lead analyst on consumer apps in Southeast Asia where location was a core loop, not a novelty tile. She now teaches full time at Systempacketline and still reviews one alumni funnel a month. She will tell you when your heatmap is flattery.
Informational pricing
Map Room Cohort seat: ฿48,900 per person. Team invoices available. No payment is taken on this website. See seats and residencies and the refund policy.
Questions we actually hear
Do I need GIS software?
No. We sketch corridors on paper and work in whatever warehouse you already use. A mapping licence is not included and not required for the capstone dataset we provide.
Can my engineer join instead of a PM?
Yes. Mixed rooms work best. Pure engineering pairs sometimes skip the narrative week; we still mark the attribution memo, and it is often the harder assignment for that audience.
What if our app has almost no indoor coverage?
That is a real limitation of this studio. Week six uses mall traces that assume some indoor signal. Teams with GPS-only data can still complete the capstone, but the indoor exercises will feel thinner. We would rather say that than sell you a week you cannot use.
Is there a certificate?
A letter confirming completion, if you finish the capstone. We do not run a badge marketplace.
From recent studios
The district cohorting week stopped us averaging Bangkok with upcountry traces. Activation “in Thailand” was a vanity number; district slices were the first time growth and ops agreed.
Capstone feedback was sharper than the lectures. I wanted more time on iOS precise-location quirks; we only got a half-session. Still the only course that made our counsel sit through a funnel review without leaving early.