GCM Docs

Appearance

Filters and layers ​

The map page gives you a single card of controls above the Leaflet view. Every filter that changes what you see lives on the surface — no hidden side panel, no settings dialog.

Map controls

Layer toggles ​

Two checkboxes sit at the top-left of the control card:

  • Members — every member in your organisation with a coordinate on file. Blue circle markers with a photo or initial. See Viewing members on the map for the marker anatomy.
  • Org units — every campus, branch, or sub-unit in your hierarchy that has a coordinate. Coloured pill markers labelled with the level's three-letter abbreviation. See Org units on the map for how levels map to colours.

Each toggle also shows the count of records that could be drawn for that layer — Members (847) means 847 members in this org have at least one coordinate. Uncheck the box and those pins vanish; the count stays so you know what's available.

TIP

Turning both layers off gives you the Enable at least one layer to see markers on the map empty state. It's not a bug — it's a hint that you're filtering yourself out of seeing anything.

Source selector ​

Members and org units can each carry two independent coordinates: an exact pin (set by hand on the profile) and an approximate coordinate (placed by the geocoder from the address). The source dropdown decides which one the map draws.

  • Exact (manual) — only records with a hand-placed pin. Sparse but ground-truth.
  • Approximate (estimated) — only records the geocoder placed. Dense, but only as accurate as the address.
  • All locations (mixed) — default. Prefer the exact pin; fall back to the approximate coordinate if no pin exists. Each record contributes at most one marker.

Switching source re-fits the map to whatever points are now visible. If you switch from Approximate to Exact and your org has very few hand-placed pins, the map will zoom in tightly around the handful that exist.

The popup on each member marker shows which source it came from — a green Exact (pin placed) badge or an amber Approximate (from address) badge. Use the badge to sanity-check that a pin in the middle of a field isn't actually a geocoder guess for a member whose address only includes a city name.

Default source ​

Your org's default source lives at Settings → Map. When the page first loads, the dropdown is set to whatever default the org configured (usually All locations). Once you change the dropdown by hand, the page remembers your choice for the rest of the session — refreshing the page returns you to the org default.

Filtering by org unit ​

The map does not (yet) have its own org-unit filter sidebar. To narrow members to a single campus or branch, the workflow today is:

  1. Open the members list and apply a Org unit filter.
  2. Note the member set.
  3. Come back to /map and zoom into the region those members live in.

A first-class org-unit filter is on the roadmap; in the meantime, the Org units layer with the colour-coded level markers gives you a good visual sense of which members cluster around which campus.

Filtering by member type ​

Member type filtering also runs through the members list today, not the map. Open Members, filter by Member type (Adult / Youth / Child / Visitor — whatever your org has configured), and check the resulting count. The map currently draws every member with a coordinate, regardless of type.

If you regularly need just the youth pinned on a map, the easiest workaround is to export the filtered list from Members → list view and pin the addresses in a side tool.

Clustering ​

The Cluster checkbox lives on the right side of the control row. It's on by default.

When clustering is on:

  • Member markers within 30 pixels of each other on screen collapse into a numbered bubble.
  • Click a bubble to zoom in until it splits.
  • Past zoom level 17 (close enough to see individual buildings) clustering disables automatically, so you always see every pin at street scale.
  • If two members share an identical coordinate (a husband and wife both pinned at their front door), the cluster spiderfies — click and the pins fan out radially with thin lines back to the centre.

When clustering is off, every visible member is drawn as its own marker. Useful for sparse maps; punishing on a 1,200-member city map (you'll get a solid blue smear).

Org-unit markers are not clustered — there are usually only a handful of them and they're meaningful as individual pins. See Org units on the map for why that's deliberate.

Clustering is per-session — toggling it doesn't write back to the database or affect other staff using the map at the same time.

Pin count badge ​

The badge on the far right of the control row (123 pins) is the total of whatever the map is currently rendering after all the filters above. It updates live as you toggle layers or change source — a useful reality check that the map you see matches the data set you mean to see.

Five hundred members in your org but the badge says 42 pins while the source is set to Exact? You probably haven't placed many manual pins yet. Switch to All locations and the count should jump to reflect the geocoded estimates.