Skip to Content
ModulesReportsMap reports

Map reports

Plot requests as bubbles sized by count, on an OpenStreetMap-backed Leaflet map. Replaced the previous “Heatmap” rendering in v1.51 — bubbles read better at small data sizes.

Who this is for: anyone with reports.manage.

How it works

  • Each request row stores latitude + longitude if its Recipient Location could be geocoded.
  • New requests geocode automatically on save.
  • Existing rows (before the geocoding feature shipped) need a one-time backfill.
  • The Map chart groups rows into ~110m location buckets server-side, so the client receives {lat, lng, count, label} per bucket — not raw per-request coordinates.

Steps

  1. Open the report → set Chart type to Map.
  2. If you see “No geocoded requests yet”, click Backfill existing rows. CartonCrew geocodes up to 50 rows per click via the US Census geocoder (digit-bearing addresses) + Nominatim fallback (city-only).
  3. Pace yourself — Nominatim asks for ≤ 1 req / s; CartonCrew enforces this.
  4. After backfill, the Map populates with bubbles. Hover / click a bubble for the city + request count popup.

What you’ll see

Video — coming soonBuild a Map report + backfill geocodingRecorder brief: V18 — Build Map report + backfill. Requests → Map → 'No geocoded requests' → Backfill → 50 attempted, N geocoded → bubbles.

Common issues

  • Map tiles are grey — CSP issue blocking OpenStreetMap tile hosts. Should be fixed since v1.49.4; if you see this in v1.51+, file a bug.
  • Double zoom controls — fixed in v1.51.
  • Bubble count smaller than total request count — only requests with geocoded latitude/longitude appear. The empty-state message shows the total + how many are geocoded.

Last updated: 2026-06-01 · Applies to: CartonCrew v1.56+

Pinning to dashboardOverview