As I mentioned earlier they are SEPARATE systems. They do share some common interoperable talk groups. Think of those talk groups as mutual aid frequencies. You wouldn't group systems together just because they both have the same mutual aid frequencies. Also since these systems share the same geographic area a radio can be in a neighboring area but still be on their own system. Hence the use of some common talk groups (they have the same ID on all systems). If the user radio is programmed with both systems then it can access the others talk groups. But that fills up the radio with LOTS of talk groups.
BB
Agreed. The point of P25 is interoperability, nothing more, nothing less. It isn't about digital vs. analog, or even conventional vs. trunked. Ask any radio salesman or tech and they should realistically say the same thing.
That being said, the point of linking the two systems is interoperability--JoCo units can use KCMO, and vice versa. They can both transmit--and receive--from both sets of towers on both systems, but the systems are still separate, regardless of the label given to the system (MARRS).
Now, with the Kansas Statewide system, each tower has its own talkgroup "home profile" for the standard sets of users that typically talk on that tower, plus a handful of talkgroups that every tower has (e.g. KHP, KDOT, ICS, Interoperability, KBI, etc.); some also have certain talkgroups assigned to them, but don't rebroadcast traffic on them unless a radio has affiliated with the control channel on that particular tower (i.e. the end user is dragging traffic to the repeater). There is no reason why this same scenario can't (and isn't) present on the MARRS system, which is why it works.
If the systems themselves are separate, but linked, from a presentation standpoint, why would you show them as the same system, when in fact they're not? I realize that data entry is labor intensive, but using XML to import and export could greatly speed up the process, especially if there are identical talkgroups on both systems.