Project

General

Profile

Actions

Bug #1251

closed

Unable to import CSV file WORKAROUND

Added by Wolfy Wolf over 10 years ago. Updated over 10 years ago.

Status:
Rejected
Priority:
High
Assignee:
-
Category:
-
Target version:
-
Start date:
11/18/2013
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
(All models)
Platform:
Windows
Debug Log:
I read the instructions above:

Description

Baofeng UV-5R+ model, exported contents to CSV file, modified, saved, then attempted to import but reached error saying unknown file format.

Issue and workaround:
NOTE: For clarity, orig.csv refers to original exported .csv file and mod.csv refers to modified .csv file
Exported orig.csv
Copied orig.csv file to another location with name orig1.csv
Changed orig1.csv file and saved using OpenOffice Calc under mod.csv
Changed (not saved) both orig1.csv and mod.csv to a .txt file, viewed both orig1.txt and mod.txt in Notepad, and found that orig1.txt export used COMMA'S for delineaters and the SAVED mod.txt file used SEMICOLON'S.

Did an EDIT, FIND AND REPLACE, changed semicolons to comma's, saved the mod.txt, then manually changed file extension again back to .csv, imported successfully into program with only the following errors (11 total but only one shown, line numbers only changed, I believe this is not needed for the Baofeng radios):
Line 2: [duplex] `-0' is not in valid list: ['', '+', '-', 'split', 'off']

Hope this helps, perhaps could include this into the FAQ portion about Unable to import CSV until its fixed
Cheers
Wolfy
K4GHL


Files

CSV editing.jpg (90.1 KB) CSV editing.jpg Wolfy Wolf, 11/19/2013 06:22 AM
Actions #1

Updated by Tom Hayward over 10 years ago

  • Status changed from New to Rejected

I'm going to close this because it isn't actually a bug.

Chirp supports CSV or "Comma Separated Values" files. It does not support semicolon separated values files.

Despite the bug being closed, users with this problem will still be able to find this page with the search feature.

Actions #2

Updated by Wolfy Wolf over 10 years ago

Notice the DEFAULT options when first opening an exported CSV file in the attached image. If the user FAILS to UNCHECK the semicolon option (BOTH comma AND semicolon are selected by default) then when its saved you will wind up with an unimportable file into the CHIRP program.

By changing a field and then simply SAVING the file, you wind up with (by default):
500;TESTEDIT;999.99;999;999;;;;;;;;;;;;

Without some type of highly visible alerting that this will cause issues, you will wind up with folks who get frustrated with the software and may go elsewhere. CSV has become a generic term to the extent that all kinds of different syntax can be used to separate fields of text.

Actions

Also available in: Atom PDF