CHIRP

Tom Hayward wrote:

If you manage your channels in a CSV file, there is a comment field. Then for each of your radio imgs you can import that CSV file.

But the purpose behind using Chirp is to have it manage the channels and saving to an img for the baofeng or to a csv (img not supported) for the kenwood is the "save"/backup feature.

I import from repeater book or other support sources from within Chirp to Chirp and then to the radio. Editing the csv file manually by reading the data in chirp is not a friendly or more importantly, efficient process.

I have dozens of radios and the way I keep them synchronized is by importing all of their channels from a master CSV. I only edit in the CSV, and I only import in the imgs. It scales O(2), meaning that once you have two or more radios there is no more efficient process to keep them in sync. It is always just two steps: maintain channels in the CSV file, import into the img.

But if you read the duplicate issues, this isn't as much about efficiency as it is about the radios themselves. Your Baofeng does not support comments. The img is a verbatim memory download from the radio, and nowhere in there is a place to store comments. The result: when you edit imgs in Chirp, there's no place to store comments. To add another field that's not supported by the radio, you'll need another datastore. Chirp has implemented one and called it CSV. If you want to store comments, you'll need to use CSV.

If you have a vision for this feature request that fits within the constraints of your Baofeng, please describe how it should work (where it would store and synchronize this metadata). Otherwise what you're describing just isn't physically possible.