There's no benefit to .chirp over .csv. Just use .csv.

Thanks for the head's up. As I cannot upload a .csv file to the radio, I have to export it first to a format that can, that's the step I was wondering if I could get around: EG: storing metadata in a file format that can directly program the radio as well. Sounds like for the time being the best method is to work with a native .CSV file for any updates, and then export it as a .chirp file for upload to the radio,

Regards,

John Kellas

On Mon, Jan 6, 2014 at 11:21 AM, Tom Hayward <esarfl@gmail.com> wrote:

On Mon, Jan 6, 2014 at 9:51 AM, John Kellas <sales@mparam.com> wrote:
> I see when working in a .csv file I can use the comment field. That field
> does not export over to the .chirp file. Is there a way to add a comments
> field to the .chirp or .img files?

There's no benefit to .chirp over .csv. Just use .csv.

.img files are a direct data dump from the radio. They can only store
fields supported by the radio. If your radio doesn't have a built in
comment field (I'm not aware of any that do), then there's no way to
store a comment in the .img file.

Dan has proposed a new file format that would store the img data plus
some additional metadata. This is a long way from fruition.

Tom KD7LXL
_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users