Open KD7CAO opened 10 months ago
If we were to start a new DICE plan from scratch, I see a lot of value in moving to this system. However, one of the core goals of the DICE plan is maintaining backwards compatibility in channel numbers.
This is a tricky one that will definitely require some more thought.
Abandon the old one. I honestly hate the current one so much I don't use it. We were trying to build off a regional plan idea. It was better than the aviation City code method. Yet was still confusing. Also, it was developed before D*STAR took off so we adapted using zones for digital. Now with multi-mode plans it honestly doesn't leave room for growth anymore that makes sense.
The likely outcome of this issue is that an additional column or two will be added to define "Zone" and "Channel" such that radios with 16 channels per zone can be organized in a coherent manner, while not breaking compatibility with continuous-channel type radios.
Utilize a table format for an organization that allows for easy identification of the county a site is in.
For example:
Channel 50: Collin Channel 51: McKinney Channel 52: McKinnney #2
Channel 60: Tarrant Channel 61: Ft. Worth
The county label should be the primary repeater for EMCOMM in that jurisdiction. The zero at the end of a channel number also helps identify the site as the county site, negating the need for a C or something on the name. The next channel should be the backup or alternate site. We should also standardize labels for each that allows for multiple alias characters. Some radios are six, some eight. Some other radios may not have a limit.