[chirp_users] CVS conversion
Hi Dan, I'm working on my 2820 and I tried to export italian rpeater list into a csv file. I've modified the fields to accomplish to the CSV format readed by chirp but I see that chirpw don't read my cvs... i've saved a native chirp file to a csv and I've imported it again with no success. I think managing CSV files will be a good thing when you have lots of rows to edit. Can you document CSV managemet by chirp or give a chance to use csv for import?
73 de Leo IZ5FSA
Hi Leo,
I'm working on my 2820 and I tried to export italian rpeater list into a csv file. I've modified the fields to accomplish to the CSV format readed by chirp but I see that chirpw don't read my cvs... i've saved a native chirp file to a csv and I've imported it again with no success. I think managing CSV files will be a good thing when you have lots of rows to edit. Can you document CSV managemet by chirp or give a chance to use csv for import?
I'm not sure what you mean by "give a chance to use csv for import".
I assume you're looking for more explanation as to why it won't open/import your CSV file in the UI, right? I should definitely improve that reporting.
The recent betas have a bit better CSV import support, namely they let you leave out fields that you don't care about, and CHIRP uses the first row of column headers to determine which column is which.
In the sort term, feel free to send me your CSV file and I'll figure out what's wrong with it and try to make CHIRP report what is failing better.
I want to know CSV columns names, format and domain expected by chirpw. I had to create a single file with italians repeaters/frequency memories to upload on every radio managed by chirp converting CSV to native chirp or img files.
I've seen you manage dup column always with a 0 (when exporting to CSV)... What kind of data you expect in input (+, -, <pace>) ?
I think this can help to chirp diffusion and data management.
73s de Leo IZ5FSA
Il 09/03/2011 22:28, Dan Smith ha scritto:
Hi Leo,
I'm working on my 2820 and I tried to export italian rpeater list into a csv file. I've modified the fields to accomplish to the CSV format readed by chirp but I see that chirpw don't read my cvs... i've saved a native chirp file to a csv and I've imported it again with no success. I think managing CSV files will be a good thing when you have lots of rows to edit. Can you document CSV managemet by chirp or give a chance to use csv for import?
I'm not sure what you mean by "give a chance to use csv for import".
I assume you're looking for more explanation as to why it won't open/import your CSV file in the UI, right? I should definitely improve that reporting.
The recent betas have a bit better CSV import support, namely they let you leave out fields that you don't care about, and CHIRP uses the first row of column headers to determine which column is which.
In the sort term, feel free to send me your CSV file and I'll figure out what's wrong with it and try to make CHIRP report what is failing better.
I want to know CSV columns names, format and domain expected by chirpw. I had to create a single file with italians repeaters/frequency memories to upload on every radio managed by chirp converting CSV to native chirp or img files.
I've seen you manage dup column always with a 0 (when exporting to CSV)... What kind of data you expect in input (+, -, <pace>) ?
How's this for a start?
http://chirp.danplanet.com/content/csv-format
Nice.... I'll work on it.
I'll work on a CSV and i'll try tofit it into ICE2820, ICE92D and ICE80D and finally into a THD72E.
I'll give you my feedback!
73 de Leo IZ5FSA
Il 10/03/2011 22:34, Dan Smith ha scritto:
I want to know CSV columns names, format and domain expected by chirpw. I had to create a single file with italians repeaters/frequency memories to upload on every radio managed by chirp converting CSV to native chirp or img files.
I've seen you manage dup column always with a 0 (when exporting to CSV)... What kind of data you expect in input (+, -,<pace>) ?
How's this for a start?
I've created my own CSV file... but CHIRP don't seems to understand... open file or import from file don't make anything!
I've attached for your test!
73 de Leo IZ5FSA
Il 10/03/2011 22:34, Dan Smith ha scritto:
I want to know CSV columns names, format and domain expected by chirpw. I had to create a single file with italians repeaters/frequency memories to upload on every radio managed by chirp converting CSV to native chirp or img files.
I've seen you manage dup column always with a 0 (when exporting to CSV)... What kind of data you expect in input (+, -,<pace>) ?
How's this for a start?
no... I see no messages! Is it in debug.log?
Il 12/03/2011 06:16, Dan Smith ha scritto:
I've created my own CSV file... but CHIRP don't seems to understand... open file or import from file don't make anything!
When I try to open that file, it shows an error that on line 5, "520" is not a valid DTCS code. Do you see that?
Ok, I've updated to latest chirp version and I've corrected errors on CSV file.
Only 2 questions: 1) why you don't import UR RPT1 RPT2 fields? 2) is there a way to "merge" *.img memories tab with the brand new CSV generic memories tab????
73s de Leo IZ5FSA
PS: on IC2820 my tests are all ok.
Il 12/03/2011 06:16, Dan Smith ha scritto:
I've created my own CSV file... but CHIRP don't seems to understand... open file or import from file don't make anything!
When I try to open that file, it shows an error that on line 5, "520" is not a valid DTCS code. Do you see that?
- why you don't import UR RPT1 RPT2 fields?
Because I forgot to add it when I re-wrote the CSV driver recently :)
Should be fixed in the repo now for the next beta...
- is there a way to "merge" *.img memories tab with the brand new CSV generic
memories tab????
Hmm, I'm not sure what you mean. You can open a CSV file directly in the editor and then import from one or more .img files to do some merging. Is that what you mean?
- is there a way to "merge" *.img memories tab with the brand new CSV generic
memories tab????
Hmm, I'm not sure what you mean. You can open a CSV file directly in the editor and then import from one or more .img files to do some merging. Is that what you mean?
Yes... I'll test it on brand new latest beta.
participants (2)
-
Dan Smith -
IZ5FSA