Skip to main content

Location codes, regions, and scoping: what is the difference?

Beginner-friendly · Especially useful for MeshCore observers, repeater operators, and newcomers

You might see an observer reporting from GDW, and separately hear a discussion about a MeshCore mi-central scope. Those settings are not interchangeable. One identifies an area in an observation or mapping system; the other can affect which radio repeaters forward a packet.

That distinction matters even more when a regional organization publishes recommended settings for the repeaters in its area. Recommendations can improve interoperability, but they should be identified as that organization's recommendations, not presented as mandatory rules for every independent operator in a state.

This guide separates the technology from the organizational choices. It explains why scopes are useful, where they can cause problems, and how to keep a network welcoming to newcomers.

Scope of this article: MeshCore-specific radio traffic forwarding and observer metadata. Other systems (including Meshtastic, APRS and voice repeaters) have different rules and protocols. MeshCore firmware and apps continue to change.

1. Two identifiers that serve different purposes​

Observer IATA-style location codeMeshCore region scope
ExampleGDWmi-central
What it describesA geographic reporting or mapping area used by observer servicesThe set of repeaters through which the sender wants certain flooded radio packets to travel
Where it appearsObserver configuration, mapping services, or MQTT topics such as meshcore/GDW/<observer-public-key>/packetsCompanion/channel/default-scope settings and repeater region-forwarding configuration
Does it make a repeater forward or reject radio packets?No. Not by itselfYes, when matching rules and forwarding permissions apply to MeshCore flood traffic
Does setting one automatically configure the other?NoNo

Observer location code: organizing reported data​

An listens to MeshCore radio traffic and may report what it hears to a mapping or monitoring service over the Internet. Many observer/MQTT systems use an to group those observations. For example, GDW can be part of an observer's reporting namespace.

The observer's configured code helps the Internet-side reporting system organize where observations came from. It is not a radio forwarding rule and does not add a region scope to the packets that the observer heard.

The code is not necessarily the airport nearest to the antenna: services define their own reporting areas and accepted codes. Different services can organize those areas differently.

MeshCore region scope: influencing RF forwarding​

A affects how eligible are repeated across a MeshCore network. A sender can choose a scope (for example mi-central), and a repeater's configured MeshCore region list determines whether that repeater is eligible to forward packets with that scope.

A repeater may be configured with several scopes, such as midwest, mi, and a more local region. Names must match; scopes do not become interchangeable just because an observer's IATA code refers to a nearby area.

Some communities choose three-letter airport codes such as grr as scope names too. This reuse is a naming choice: using an IATA-style label as a scope does not make the observer reporting code and the RF forwarding mechanism the same thing.

Takeaway: You can run an observer under GDW without using gdw as a MeshCore region scope. One setting does not dictate the other.

2. Why regions and scopes can be useful​

Radio spectrum has limited airtime: every retransmission occupies time on a shared channel. With many repeaters, an unrestrained flooded message can be rebroadcast far beyond the area where it is useful.

Scopes can help operators:

  • Keep local traffic from unnecessarily consuming airtime across a much wider area.
  • Reduce repeated packets and congestion as the network expands.
  • Provide local, regional, or broad communication choices for different purposes.
  • Make forwarding behavior more predictable when the names, coverage, and rules are documented.
  • Design intentional links across adjacent areas when there is a genuine coverage need.

These benefits are real. Using a scope is not inherently gatekeeping. The tradeoff depends on how the repeater network is configured and how well people understand that configuration.

3. What is actually filtered?​

MeshCore repeaters have a list of region scope names they recognize and allow to flood. A packet scoped to a name the repeater does not recognize will not be forwarded by that repeater through the scope-filtered flood mechanism.

A few points are especially important:

  1. Unscoped packets are a separate case. The * entry represents the unscoped/null region in MeshCore's region-filtering commands—not a magic “allow every named scope” setting.
  2. Defining additional regions does not automatically disable unscoped forwarding. A repeater administrator can separately allow or deny unscoped traffic with region allowf * or region denyf *.
  3. Scoped packets can still stop at a mismatch even if unscoped traffic remains allowed. For example, a repeater that knows mi but not mi-central does not automatically recognize the latter.
  4. Region hierarchy does not imply matching inheritance. A repeater should be configured to recognize each distinct scope it intends to carry; parent-looking names do not automatically cover their children.
  5. Filtering flood forwarding is not the same as blocking reception or every kind of direct radio message. Some discovery, advertisement and unknown-path traffic can also involve scoped flooding. Exact effects depend on firmware and application versions.

Example: why a newcomer may be confused​

These are illustrative configurations, not claims about a particular Michigan repeater:

User's outgoing floodRepeater configurationWhat happens
UnscopedUnscoped forwarding permittedEligible for relay (other RF limits still apply)
Unscopedregion denyf *The repeater will not relay that unscoped flood
Scoped to mi-centralOnly mi configuredThe repeater does not automatically relay the differently named mi-central scope
Scoped to mi-centralmi-central recognized and flood-allowedEligible for relay
Scoped to mi-centralOne relay accepts it, but a later relay does notThe flood can stop partway through the network

“Eligible” is not a delivery guarantee. Antenna placement, terrain, noise, congestion, routing and other protocol rules still apply.

Hearing someone else's message does not prove that your outgoing message will be repeated along the reverse path.

4. When does this become a walled garden?​

A walled garden develops when successful participation effectively requires knowing conventions that aren't clearly explained or accessible to new users.

Examples include:

  • Several important repeaters deny unscoped traffic, while beginner setup instructions leave the default scope blank.
  • Local scope names are mandatory in practice but not published where new users can find them.
  • Different groups choose conflicting labels or configure few paths between regions.
  • Configuration changes happen without notice or practical testing from an unconfigured device.
  • Someone reports missing messages and is dismissed for not knowing rules they were never told about.

A repeater owner can make operational choices about their equipment. The issue is the consequences for interoperability and accessibility, especially if the community presents a particular configuration as a universal obligation.

Whether restrictive filtering is justified depends on actual congestion, coverage, deployment maturity, and the availability of clear onboarding instructions.

5. Whose standard is it? A case study from Michigan​

The MichMesh article Regions and Scoping uses the heading “Where Michigan Stands” and says “Every Michigan repeater should be tagged now”, referring to a prescribed list of scope names such as midwest, mi, and a subregion.

There are two questions to keep distinct:

Technical proposal: Is that a useful configuration for repeaters that voluntarily want to participate in a particular Michigan-wide forwarding plan? It might be. Coordinated scope names can make traffic management and interoperability easier. There is room for legitimate debate about which regions, how to bridge them, and when filtering should be enabled.

Representation and authority: Does MichMesh speak for every Michigan repeater operator, or have authority to impose settings on independent networks? No statewide authority follows from publishing a network guide. A group may describe the standards it wants its participants to use. It should not imply those are regulations binding every Michigan operator.

The word “should” is a recommendation rather than a legal command. Nevertheless, framing it as “Where Michigan Stands” can imply a level of statewide consensus or representative authority that the page alone does not establish. A clearer presentation would say “MichMesh's recommended region configuration for participating repeaters.”

An important nuance in the published guidance​

MichMesh's separate Repeater Setup Guide distinguishes defining region names now from activating restrictive scoping. It explicitly says that scoping is on hold, and instructs operators to leave unscoped floods available while region lists are prepared.

That matters: adding region names to a repeater is not identical to denying all unscoped packets. We should not claim its current published policy blocks newcomers without evidence that deployed repeaters are actually using restrictive settings.

Even while unscoped traffic is permitted, scope mismatches can still cause a message sent with a scope to stop at a repeater that lacks that scope.

About firmware requirements​

A community's particular setup instructions may require a firmware version because they use a newer configuration command (such as region def). That is different from saying all MeshCore region filtering was first introduced in that version. Region filtering existed in earlier firmware; use the current firmware's documented command syntax for your actual device.

What would responsible leadership look like?​

Instead of implying statewide mandates, a regional project can be transparent:

  • Say whose proposal the settings are, and who participated in agreeing to them.
  • State explicitly whether the settings are optional interoperability recommendations or requirements only for project-operated infrastructure.
  • Publish the reasons, measurements, and tradeoffs behind the recommendations.
  • Explain what a brand-new companion does by default.
  • Explain whether unscoped floods are currently allowed and how to tell.
  • Publish a real migration and rollback plan before changing forwarding rules.
  • Respect operators who prefer different configurations on independent networks.

Technical collaboration does not require pretending one organization governs the entire state.

6. Practical troubleshooting: I hear traffic, but mine isn't getting repeated​

  1. Confirm the basics: appropriate MeshCore firmware role and compatible radio settings (frequency, bandwidth, spreading factor and coding rate).
  2. Separate observer settings from radio settings: an IATA-style observer code like GDW does not determine the RF scope.
  3. Check your companion's default scope and any per-channel scope. A channel-specific scope can override the default.
  4. Check the repeater's allowed scope names: use region discovery where supported, or consult the operator's public documentation.
  5. Check whether you're sending unscoped traffic and whether nearby repeaters permit the null/unscoped region *.
  6. Check the entire possible forwarding path: one repeater accepting a scope is not enough if another does not.
  7. Don't assume filtering: weak signal, terrain, interference, collisions and routing can look similar.
  8. Ask for help without accepting blame: requesting an explanation of a network's settings is a reasonable beginner question.

Don't reconfigure someone else's repeater without authorization.

7. Our approach at Northern Michigan Mesh​

Our Northern Michigan regional map uses three-letter geographic reference codes, including GDW, CAD, TVC, APN, CIU, MQT and CMX. These support our geographic organization and observer-reporting context. They are not a published MeshCore region-scope policy, and the map does not impose repeater forwarding rules.

We welcome people who choose MeshCore scopes to manage airtime. We also welcome those who question a scope plan, prefer different boundaries, or operate independent equipment.

We believe:

Interoperability should be encouraged through explanation and voluntary coordination—not declarations of authority over operators who never agreed to participate.

Primary and practical resources​


Agree or disagree? Have a scope configuration that works well—or a newcomer experience that didn't? Share evidence and questions on our forum. This is an educational discussion, not a requirement to join any organization.