Skip to content

Start a FreqMapper region

FreqMapper is one global system with regional maps. Starting a region is as much a community job as it is a map job: it needs people who know the area, are willing to care for it, and want the data to stay honest.

If you are deciding whether your mesh is ready, first read How FreqMapper works for mesh administrators. It explains the required pieces, the Watcher evidence path, and what FreqMapper does and does not control.

Before you apply

Have these basics ready:

  • A distinct local mesh area that does not unreasonably overlap an active region.
  • A proposed IATA code and plain-language display name.
  • At least one working feeder already operated by the local mesh team and able to provide authorized read-only MQTT receipts; two or more are strongly recommended.
  • A proposed regional boundary. County-derived shapes are a good starting point.
  • A local contact person who can coordinate with the community.

FreqMapper does not create, supply, host, or maintain the feeder node, gateway, broker, internet connection, or local mesh. Build and validate that path with the local mesh team before requesting FreqMapper integration.

The review flow

  1. Start: explain the intended region and local need.
  2. Code and name: propose the IATA key, display name, and public map address.
  3. Boundary: think through which cities, counties, and communities belong together, and check for overlap with nearby regions.
  4. Mesh evidence: identify the existing locally operated Watchers and confirm they can supply authorized read-only MQTT receipts.
  5. Verification: FreqMapper connects the approved source and confirms actual receipts from its Watchers.
  6. Review: the FreqMapper team checks the boundary, overlap, public text, activity, and local stewardship.
  7. Activation: the region becomes discoverable and can collect verified coverage.

Boundary guidance

Think about the boundary as part of the region proposal, not as a last-minute file upload. It should describe one understandable local mapping community without unreasonably overlapping a neighboring region.

Consider:

  • The cities, counties, or other communities that naturally belong together.
  • Recognizable edges such as county or state lines, while allowing a custom shape when local geography calls for one.
  • Nearby regions, including awkward overlaps or gaps that could confuse mappers.
  • Whether the proposed area is a practical size for local people to support and grow.
  • Future growth, without claiming a much larger area before the community can care for it.

The boundary is an organization and presentation area, not an RF wall or a promise of coverage. County-derived shapes are a good starting point, and Boundary Maker can help explore which counties fit together. At this stage, focus on agreeing what the region should include.

Begin with the local mesh team if the feeder and MQTT path do not exist yet. When that infrastructure is working, contact the Freq51 community team in Discord to discuss the FreqMapper region and source connection.

Once your regional access is ready, use the Regional administration guide for the console options and safe operating steps.

Last updated: 2026-09-24