LotW Grid squares are not pulling in during LotW Sync - Intended? #1059
-
This is in reference to a previous question #1004 Is this intended to be added? In the /application/controllers/Lotw.php:674 I can see there is a TODO to add an option for this, but I don't know if this is still planned as the TODO was added to the software it looks like back in 2013. I can see from the /application/controllers/Lotw.php:443 (loadFromFile) that this calls on line 516 the lotw_update function on the logbook_model. This function does not import the Grid Square that exists on the LotW record. The lotw_update function exists in application/models/Logbook_model.php:1374. This function does update the database table TABLE_HRD_CONTACTS_V01 with the related QSL data, beside the Grid Squares. If you want an additional contributor I'm willing to give it a shot - I haven't used PHP before but tracking this down wasn't that hard. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
Yeah it's currently intentional, probably not a huge issue on HF but on VHF+ it's seen quite often the operator uploads qsos against the wrong square and I hadn't decided how best to handle it beyond not updating the fields if data is already present |
Beta Was this translation helpful? Give feedback.
-
Grid square is written and tested. Working great, will upload for PR hopefully by next weekend. Currently written to only import gridsquare if not populated, or if gridsquare matches (LotW has 6/8 characters, and Cloudlog has 4 or 6.) Vucc Grid Squares I don't have any samples to review to see how this should populate in the database - so I will not be attempting that at this time. |
Beta Was this translation helpful? Give feedback.
Yeah it's currently intentional, probably not a huge issue on HF but on VHF+ it's seen quite often the operator uploads qsos against the wrong square and I hadn't decided how best to handle it beyond not updating the fields if data is already present