Re: [chirp_users] programming assistance
On 2024-01-10 08:15:, Jim Unroe wrote:
CHIRP CSV files often have multiple trailing commas at the end of each line due to the URXALL, RPT1CALL, RPT2CALL and DVCODE fields rarely being used. Power,Comment,URCALL,RPT1CALL,RPT2CALL,DVCODE 5.00,,Low,,,,, Excel is known to remove multiple trailing commas at the end of a line. When CHIRP reads the CSV file where the trailing commas have been removed, the trailing data will be read into the wrong fields. Excel always works fine if there is alway something in the last field of each line. I've read that there is a setting that you can enable in excel that tells it to leave trailing commas alone. I don't have excel so I can't verify this. Perhaps it would be possible to have CHIRP always resync with the beginning of the CSV file's next line when a linefeed is encountered? Jim KC9HI
// This is the discussion that I need to capture in my notes for the ARES group. // I have been "lucky" not to have run into this in the past. And wrt the present file, all channels end with a comment, so if there are blank fields, the csv will be correctly formatted (IAW your trailing ,,, comment).
I will look into Excel settings, but any rate, I need to caution the group. I've never had a problem with chirp, but then I am fairly computer literate, and I don't know how that enhances my chirp experiences.
...and finally...
so I can't verify this. Perhaps it would be possible to have CHIRP always resync with the beginning of the CSV file's next line when a linefeed is encountered? Jim KC9HI
Absolutely common sense. Would be surprise were it not already the case...
73 Rich NE1EE The Dusty Key On the banks of the Piscataqua
so I can't verify this. Perhaps it would be possible to have CHIRP always resync with the beginning of the CSV file's next line when a linefeed is encountered? Jim KC9HI
Absolutely common sense. Would be surprised were it not already the case...
Very much looks to me as if it is already the case. The csv data is read using a standard python csv library and parsed line by line. Any data that is 'missing' is simply skipped over when it's being read into memory. This is not 'exactly' the same action as a blank field (missing skips the data, blank sets it to 'None') but I would expect the overall effect to be the same. If anyone wants to investigate, the place to look would seem to be the _parse_csv_data_line() function in generic_csv.py.
Rog (hoping he's helping rather than complicating!)
-----Original Message----- From: <chirp_users-bounces@intrepid.danplanet.com mailto:chirp_users-bounces@intrepid.danplanet.com> on behalf of Rich NE1EE <TheDustyKey@imaginarian.org mailto:TheDustyKey@imaginarian.org> Reply to: Discussion of CHIRP <chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com> Date: Wednesday, 10 January 2024 at 13:34 To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com> Subject: Re: [chirp_users] programming assistance
On 2024-01-10 08:15:, Jim Unroe wrote:
CHIRP CSV files often have multiple trailing commas at the end of each line due to the URXALL, RPT1CALL, RPT2CALL and DVCODE fields rarely being used. Power,Comment,URCALL,RPT1CALL,RPT2CALL,DVCODE 5.00,,Low,,,,, Excel is known to remove multiple trailing commas at the end of a line. When CHIRP reads the CSV file where the trailing commas have been removed, the trailing data will be read into the wrong fields. Excel always works fine if there is alway something in the last field of each line. I've read that there is a setting that you can enable in excel that tells it to leave trailing commas alone. I don't have excel so I can't verify this. Perhaps it would be possible to have CHIRP always resync with the beginning of the CSV file's next line when a linefeed is encountered? Jim KC9HI
// This is the discussion that I need to capture in my notes for the ARES group. // I have been "lucky" not to have run into this in the past. And wrt the present file, all channels end with a comment, so if there are blank fields, the csv will be correctly formatted (IAW your trailing ,,, comment).
I will look into Excel settings, but any rate, I need to caution the group. I've never had a problem with chirp, but then I am fairly computer literate, and I don't know how that enhances my chirp experiences.
...and finally...
so I can't verify this. Perhaps it would be possible to have CHIRP always resync with the beginning of the CSV file's next line when a linefeed is encountered? Jim KC9HI
Absolutely common sense. Would be surprise were it not already the case...
73 Rich NE1EE The Dusty Key On the banks of the Piscataqua
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rog at rog@rog.cc mailto:rog@rog.cc To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com mailto:chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com
On Wed, Jan 10, 2024 at 8:43 AM Roger Jane via chirp_users chirp_users@intrepid.danplanet.com wrote:
so I can't verify this. Perhaps it would be possible to have CHIRP always resync with the beginning of the CSV file's next line when a linefeed is encountered? Jim KC9HI
Absolutely common sense. Would be surprised were it not already the case...
Very much looks to me as if it is already the case. The csv data is read using a standard python csv library and parsed line by line. Any data that is 'missing' is simply skipped over when it's being read into memory. This is not 'exactly' the same action as a blank field (missing skips the data, blank sets it to 'None') but I would expect the overall effect to be the same. If anyone wants to investigate, the place to look would seem to be the _parse_csv_data_line() function in generic_csv.py.
Rog (hoping he's helping rather than complicating!)
It might be the case, but it doesn't fully mitigate the issue. I took one of my saved img files and saved it as a csv file. I then loaded the csv to make sure that it loaded OK. It did. I then use a text editor to remove 2 commas from the end of the row for memory 5. The file is loaded but memory 5 is missing. So at least the memory row that is missing the trailing commas did not prevent the rest of the csv file from loading. So apparently the library used is somewhat better in CHIRP-next than it is in classic CHIRP, because loading the file in classic CHIRP fails.
Jim KC9HI
participants (3)
-
Jim Unroe -
Rich NE1EE -
Roger Jane