Skip to content

Region Groups

A Region Group places nearby FreqMapper regions under one shared public view and one administration team. It can contain individual regions, other Region Groups, or both. For example, the Utah and Idaho Region Group brings together Utah regions such as SLC and LGU with Idaho regions such as TWF, PIH, and BOI. Each region remains available on its own inside the shared group view.

Use a Region Group only when the member communities are part of the same practical radio area and benefit from seeing their evidence together. A Region Group does not join unrelated radio systems or change the meaning of coverage evidence.

Public addresses

Every active region and Region Group has its own public subdomain:

  • slc.freqmapper.net opens only the SLC region;
  • idaho.freqmapper.net opens only the regions in the Idaho Region Group; and
  • freqmapper.net opens the all-region directory and map.

Choosing another area in the map or leaderboard changes to that area's public address.

What the public sees

Selecting a Region Group shows all individual regions below it together, including regions reached through child groups. The shared view includes:

  • one combined boundary and map extent;
  • verified transmit coverage and separate received-here evidence from every member;
  • Watcher, feeder, and live mapping activity scoped to those regions;
  • Watcher cards labeled with their individual member region;
  • combined coverage statistics;
  • a group-owned Info panel with its own introduction, public links, and official mesh radio settings; and
  • one Region Group leaderboard.

The Regions directory keeps the full member-region list visible below each Region Group entry. Each region remains selectable on its own. The global Region overview remains a separate directory and activity view; it does not combine every region's coverage into one unscoped layer.

Administration

A Region Group has its own admins and moderators. Their access is inherited by every child group and individual region below it:

  • a Region Group admin can open the group control room and each member region's control room, changing the settings available there;
  • a Region Group moderator can review each region but cannot make changes; and
  • direct regional admins and moderators continue to work normally.

The /region-admin area chooser lists Region Groups and individual regions separately. Opening either console provides a Section menu that keeps each tool on its own focused page. A Region Group overview includes combined map and leaderboard links plus links to each regional control room. Region and Region Group admins can publish an About section and public links for their own area. They can also publish authoritative LoRa region, modem preset, frequency slot, primary channel, and secondary channel settings for the public Info panel and mobile-app checks.

The Region Group API access section manages server-to-server coverage keys for the group's current member regions, including regions inside child groups. The key scope follows membership changes. If the console does not offer an action to create a new partner or replacement key, contact a FreqMapper administrator or moderator for help. Existing keys remain visible and revocable.

Child-region boundary, team, Watcher, invite, radio, MQTT, and API controls remain in each regional control room. Group-owned public information and radio settings stay separate from the member regions and never overwrite them.

A Region Group can also own MQTT broker connections. Configure a shared broker once on the Region Group instead of repeating it on Utah, Idaho, or every individual region. That read-only source applies to every active region below the group, including regions reached through child groups. Each accepted packet is still assigned to one exact regional boundary, and a Watcher can provide evidence only for its own assigned region.

Request or change a Region Group

Creating a Region Group, changing its member regions, renaming it, or changing its public address is not available in the regional console. Contact a FreqMapper administrator or moderator for help.

When requesting a new group or membership change, provide:

  • the Region Group name;
  • the regions that should appear together;
  • why their radio communities and mapping work belong in one shared view; and
  • the verified email addresses of the people who should administer or review the whole group.

Group-wide access applies across every member region, so keep local administrators assigned directly to a region when they should not manage the complete group. After a requested change is completed, check the Region Group map and at least one member-region map. If the member list, boundary, evidence, statistics, or leaderboard looks wrong, contact a FreqMapper administrator or moderator instead of trying to change the group structure yourself.

Last updated: 2026-09-24