Feature request: Mark repeaters as foreign when outside IATA region boundaries

[MartynasZilinskas]

Summary

Add support for marking repeaters as foreign when their advertised location is outside the configured IATA regions.

Problem or motivation

Related issue: #66

If a Beacon server is configured with IATA regions, it should be possible to automatically mark repeaters as foreign when they are outside those regions.

This would help separate local/internal mesh network repeaters from repeaters that are heard from outside the intended operating area.

Our usage: Lithuania is split into 4 different regions, and we are mostly focused on our internal mesh network. If repeaters from outside Lithuania appear, for example Latvian or Polish repeaters through tropo ducting, or later through a proper connection, we still want to keep the focus on our own network.

Proposed solution

When IATA regions are configured and this feature is enabled, Beacon server should check whether a repeater's Advert contains a location that falls within one of the configured IATA regions.

• If the location is inside one of the configured IATA regions, the repeater is treated as local.
• If the location is outside all configured IATA regions, the repeater is marked as foreign.
• If the Advert does not contain a location, the behavior could remain unchanged or be configurable.

In CoreScope, it is possible to define or display boundaries where repeaters outside those boundaries are marked as foreign (it's only in the backend, no frontend implementation in CoreScope yet). Image below shows global boundary:

I think this would work especially well together in the Beacon with the #66 feature, where each IATA region could have an GeoJSON border.

@446564 suggested optional field possiblyForeign on the node.

Alternatives considered

Additional context

[MrAlders0n]

This is tied to #66