02 / GEOGRAPHIC INTELLIGENCE
One coverage question, three connected views. Filter synthetic dealers, inspect the map, and compare the service load across regions.
OPTIONAL / LOCAL RECORDING PREPARATION
Confirming a scene creates a memory-only route and table. The first checkpoint survives repeated resets; saved geographic, table and appearance preferences stay untouched. This does not start screen capture. Presentation views only reframe the same live data; they never reset the query or load the SDK. An already-loaded public map may redraw tiles when its viewport changes.
Normal demo. No recording checkpoint exists. Reload resumes saved preferences; an in-memory checkpoint cannot survive it.
A reset/restore pauses the optional map and never loads the SDK or moves its camera. If a previous map view exists, restoring its camera/layers is a separate explicit action that may request public tiles. Pending query/fixture work is invalidated or cancelled, never replayed.
Read the route-specific script and shot outline · Read the complete recording playbook
The record list and comparisons work immediately. Load ArcGIS when you want to explore the map.
Loads ArcGIS Maps SDK 5.1.27 and a public Esri basemap. No key is used.
Map not loaded. All query controls and records are available without it.
Select a region to narrow the same map and record query. Bars compare matching locations with the full synthetic region.
| Region | Matched / total | Open tickets | Synthetic revenue |
|---|
Loading the synthetic dataset…
Search, sort, filter, paginate and select records without using the map. The selected record appears below; DataTables preferences are saved separately for this route and table.
THE SERVICE BOUNDARY
A bounded fixture imitates a service with a 17-feature transfer limit. The adapter enumerates IDs, retrieves batches, splits truncated batches and rejects incomplete results.
Deterministic fixture. No external feature service is queried.
PROVENANCE & LIMITS
Shared synthetic data is bundled with the Lab. ArcGIS renders a client-side FeatureLayer. Public raster tiles provide context and retain Esri attribution. Filter timing is a measured browser operation, not a production benchmark.
There is no hosted feature service, scheduled data pipeline, paid routing, or production access in this demonstration. Hosting, update and rollback architecture are explained in the tutorial.
Read the architecture & release steps →