These started as a personal project — talkgroup lists I built for my own radios because wading through the full network dumps drove me nuts. They saved me enough hassle that I figured I'd share them in case they help someone else. I'm not saying this is the right way or the best way to do DMR — it's just the way that works for me. Take what's useful and leave the rest.
Hand-sorted from each network's official list down to the talkgroups English-speaking and US hams actually use — grouped so they make sense, in a single .csv you arrange to fit your radio's CPS. The sorting's already done.
N6JET · pick your network · read the how-to, then download the list
Some lists refresh from the APIs by the hour. Talkgroups don't change that fast, though — so I update these quarterly, without chasing changes that rarely occur. But the real point is simpler: BrandMeister alone runs 1,800-plus talkgroups, and once you're on more than one DMR network, that's thousands of padded talkgroups you'll never key up. A CPS loaded that way is cumbersome to work with. These lists are trimmed network by network to the ones English-speaking hams actually use, sorted and ready to load: a lean codeplug that gets you on the air and stays easy to manage. So pick the tool that fits how you operate: if hour-by-hour accuracy is what you're after, use one of the live API lists — that's exactly what they're built for. If ease of use and a codeplug that's already organized is what you want, give mine a try. Different tools, different jobs — no wrong answer.
Each list is one .csv with all the talkgroup data in it. Because every radio's CPS wants its columns in a particular order, take a minute to arrange the columns to match your CPS's import format before you load it — a quick, one-time step. One file works for any radio; you just line up the columns. The hard part, picking and sorting the talkgroups, is already done.
Because these lists are lean, they're quick to re-pad for your own setup — tweak the talkgroup padding to match whichever DMR networks you run. Out of the box they use WPSD's default padding scheme, so WPSD users can load and go.