> ## Documentation Index > Fetch the complete documentation index at: https://docs.mapxagent.com/llms.txt > Use this file to discover all available pages before exploring further. # 15-minute Neighbourhood Coverage · Jakarta > Audit who can reach a school, a clinic and a park within an 800 m walk in central Jakarta, rank the neighbourhoods with the biggest shortfall, and score accessibility. 15-minute Neighbourhood Coverage measures the daily-life side of planning: **who can reach a school, a clinic and a park on foot**, and which neighbourhoods carry the largest shortfall. It is the MapX version of a 15-minute neighbourhood audit, and it deliberately reports two yardsticks — coverage and accessibility — instead of a single score. The Jakarta 15-minute neighbourhood run as delivered: three neighbourhood shortfall ramps, ADM4 boundaries and the pinned three-class comparison heatmap ## What the scenario ships Seven prepared layers cover Jakarta; the scenario's default study window is Kota Jakarta Pusat (central Jakarta). | Layer | Data | Role in the study | | - | - | - | | Education facilities | OSM education POIs (7,470 city-wide) | Schools that supply the education circle | | Health facilities | Healthsites.io (2,447 city-wide) | Clinics and hospitals that supply the health circle | | Road network | Overture transportation | The walking network used for service areas | | Administrative boundaries | 46 kecamatan (ADM3) | District framing and attribution | | Green space and parks | OSM green polygons (3,942) | Source of the destination-park set | | Neighbourhood boundaries | kelurahan (ADM4); 44 in the study area, 1.09 km² average | The evaluation unit that is ranked and named | | Population | WorldPop, 100 m | Residents at risk of being outside a circle | *All layers come from the [built-in catalog](/en/concepts/builtin-datasets) with source and attribution attached, and they are not limited to Jakarta: the catalog provides the same datasets for other cities at the same specification — switch the study area, add the same entries, and this chapter's method chain transfers in minutes.* ## How the study works | Stage | Question | What MapX runs | Output | | - | - | - | - | | 1. Coverage audit | How much of each neighbourhood is outside the walk? | Select features, Overlay clip/dissolve/erase, Network service area at 800 m, Zonal statistics, Field calculator | Shortfall layer per class with `gap_sum` and a share-of-residents column | | 2. Service mix and balance | Which neighbourhoods lack one, two or all three classes? | Zonal summary chaining, Overlay dissolve/erase | Neighbourhood summary table with population, coverage count 0–3 and three shortfall columns | | 3. Accessibility diagnosis | Where is access hardest, even inside the circle? | 2SFCA accessibility, Top N ranking, Label anchors, Charts | Top-10 shortfall rankings, per-class accessibility scores and a pinned heatmap | In short, the study first computes a walking service area for each of the three facility classes and crosses it with neighbourhood population to produce three shortfall layers of residents outside the circle; it then assembles the shortfalls into one neighbourhood table and ranks the neighbourhoods with the biggest gaps; finally a 2SFCA accessibility score measures how tight supply is inside the circle, cross-checking coverage against accessibility, and the run delivers rankings, a heatmap and a report. ## Run it The screenshots below come from this scenario's reference workspace. Each step names the platform surface it uses, so you can follow the same path in your own project. **Suggested question:** *"Run a 15-minute neighbourhood diagnosis for central Jakarta (Jakpus): check the walking service areas of schools, clinics and parks, find coverage gaps and imbalanced districts, and name the areas to prioritise; deliver coverage layers, charts and a report."* ### 1. Open the scenario Open **Scenarios** in the top menu, select this card and choose **Open scenario**. The whole bundle imports at once: every layer keeps its default style, legend, source and attribution, and the camera flies to the study area. Use the **Layers** panel to switch layers on and off before you type anything. The Jakarta scenario opened in a fresh project: the layer bundle imported, the Layers panel expanded, and the chat panel confirming the import with the suggested question ### 2. Ask the suggested question and review the plan Send the **suggested question** in the box above — or edit it first. [Plan mode](/en/concepts/plan-mode) asks the four decisions that change the answer — study unit, walking radius, supply assumption and deliverables — and fixes the rest, including the park definition, in the plan document. The Jakarta plan document in full-width view: side panels collapsed, plan sections and recorded decisions readable ### 3. Approve the plan and run the analysis The run uses selection, clipping and erasing to shape the study area, network **service areas** at 800 m for all three facility classes, zonal statistics to count the residents left outside, field calculations for the shortfall shares, the accessibility model (2SFCA) and a chained summary table. The graph shows every branch, including the three facility classes side by side. The **Analysis** panel keeps every run's operator, inputs, parameters and result layer. The analysis view for Jakarta: the Analysis panel lists every operator run on the left, with the workflow graph in the centre ### 4. Style the result on the map The three shortfall ramps share one break scale, so a dark purple and a dark teal mean the same share; the ADM4 boundary sits on top with neighbourhood labels, and blank space means inside the circle. The style editor on a deliverable layer: classed-colour breaks and label settings, with the layer editing panel highlighted in red ### 5. Turn the result into charts and a report The run produces per-class rankings, a three-class comparison and a heatmap that can be pinned to the map while you pan the ramps. The **[report](/en/concepts/reports)** then names the priority neighbourhoods and states the radius, the park definition and the caveats. The same run can also export the report as a Word document for a formal submission or a slide deck for a presentation handoff. A chart from this scenario in the chart editor, with the editing area highlighted in red The scenario report opened in the report canvas, with an executive summary, figures and embedded maps The Word version of the same report: the document preview with the summary table, an embedded map figure and the written analysis The slide-deck report generated from this run: the title slide in the presentation preview, with the report versions listed in the left panel ## Example output The screenshots above come from one example run with the default settings on the shipped data. They show the shape of the deliverables, not what your run will return. A finished run hands back a named, reusable set of deliverables instead of a single map: * **Layers** — one neighbourhood shortfall layer per facility class, the accessibility scores, the top-10 rankings, the neighbourhood summary table as a layer, and the labelled boundary. * **Tables** — the neighbourhood summary with population, coverage count and the three shortfall columns, plus the per-class rankings. * **Charts** — three class rankings, a grouped comparison and a heatmap, all editable and pinnable. * **Report** — the diagnosis document naming the priority neighbourhoods, with the radius, the park definition and the coverage caveats. The layer names follow the run language, but the deliverable set is stable enough to plan a handover around. ## Related * [Scenarios](/en/concepts/scenarios) — the full catalog and how scenarios work * [Public Facility Siting](/en/concepts/scenarios/public-facility-siting) — turns the gaps into candidate sites * [Carrying Capacity Assessment](/en/concepts/scenarios/carrying-capacity-assessment) — the same city, read through environmental constraints * [Analysis](/en/concepts/analysis) — service areas, accessibility and zonal statistics * [Charts](/en/concepts/charts) — rankings and pinned comparison views This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.