[chirp_users] CSV Import

[Dan Smith]

> Probably a good idea, particularly while the file structure is
> expanding / changing on a regular basis and there is the likelihood
> that people have older version csv files.

Okay, I'll make it so.

> What would probably be even more useful (IMHO) would be to publish on
> the wiki a simple data model that shows each of the fields, syntax, 
> acceptable values (and whether they are generic or radio specific),
> as well as any default values (if no entry made).  This would help
> reduce errors made by people manually editing any of the files.

That's a good idea.  I spent a whole lot of time defining the schema for
the .chirp files.  It's documented in a special meta language for
specifying such things.  There doesn't exist anything for CSV in that
way, since it's not as formally-structured, but even an ad-hoc
definition would be good, I think.

> I can probably assist, if no one else wants to, with putting together
> a draft (after the Xmas lights are up and running) but would need you
> to vet the data/format for accuracy.

It's very easy for a programmer to show code to non-programmers and
expect them to understand what's going on.  So, I'll do just that.  Here
is where most of those formats are defined in the code:

http://d-rats.danplanet.com/hg/hgwebdir.cgi/chirp.hg/file/9de7939a634f/chirp/chirp_common.py

Most of the values are probably easy to scope out without really
understanding the code.  If you look, for example, at the first
definition, it lists all the tone values, then the valid DTCS codes,
modes, etc, etc.

I can write a script to print those in some more appropriate fashion, if
you like, for easier copy-and-paste to the wiki.

-- 
Dan Smith
dsmith#danplanet.com, s/#/@/
www.danplanet.com
KK7DS