Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WWFF: Autofill locator and QTH field #1702

Closed
magicbug opened this issue Oct 18, 2022 Discussed in #1701 · 8 comments
Closed

WWFF: Autofill locator and QTH field #1702

magicbug opened this issue Oct 18, 2022 Discussed in #1701 · 8 comments
Labels
Feature This would improve Cloudlog

Comments

@magicbug
Copy link
Owner

Discussed in #1701

Originally posted by m0urs October 18, 2022
I really like the separate WWFF field which has been introduced some time ago. It would be even better, if, after entering a WWFF reference, the locator and QTH field would be automatically filled, if not already populated. Currently I do these steps every time manually and it would be great help, if this could be done automatically.

Just like it has already been implemented with the SOTA reference.

All the required information would be available as a CSV file from https://www.cqgma.org/wwff.csv

I already looked a bit into the code but that is, unfortunately, too difficult for me to do by myself :-(

@phl0
Copy link
Contributor

phl0 commented Oct 19, 2022

Assign it to me (I can't).

@phl0
Copy link
Contributor

phl0 commented Oct 19, 2022

For SOTA it is done by querying the SOTA API (e.g. https://api2.sota.org.uk/api/summits/DM/BW-005) for summit details not from the SOTA txt file. I am checking if such exists for WWFF.

@phl0
Copy link
Contributor

phl0 commented Oct 19, 2022

wwff.co does not seem to have such a function. But I was able to provide some lines of code to cqgma.org which can now deliver such data. Cloudlog changes in #1704.

@m0urs
Copy link
Contributor

m0urs commented Oct 20, 2022

@phl0 I have two things which could be improved (from my point of view :-)):

  1. If there is already a value in Locator or QTH, the auto fill option should not overwrite it.
  2. The auto lookup (for SOTA and WWFF) seems only to work for a new QSO but not if I edit a existing QSO. Could we have that for edited QSOs as well?

@phl0
Copy link
Contributor

phl0 commented Oct 20, 2022

  1. If there is already a value in Locator or QTH, the auto fill option should not overwrite it.

We now have 3 items that overwrite the grid locator besides it being manually entered or pulled from qrz/hamqth. That makes it 6 in sum. Which one should overwrite which one?
I think it should stay the way it is: After you enter a callsign the grid is pulled from qrz (which most likely is the home grid). If you then enter a WWFF/SOTA reference it will be replaced. I think SOTA/WWFF grid should have preceedence as most ops most probably do not have their /p grids in qrz/hamqth. And if they give a grid during the QSO it should most likely be the same as the lookup function provides.

  1. The auto lookup (for SOTA and WWFF) seems only to work for a new QSO but not if I edit a existing QSO. Could we have that for edited QSOs as well?

I think we could implement that.

@m0urs
Copy link
Contributor

m0urs commented Oct 20, 2022

Which one should overwrite which one?

I get your point. I will play with it for a while to see if it working during normal daily use.

I think we could implement that.

Thanks, that would be very helpful.

@phl0
Copy link
Contributor

phl0 commented Oct 26, 2022

PR #1704 has been merged to dev branch. Pls test.

@m0urs
Copy link
Contributor

m0urs commented Oct 26, 2022

PR #1704 has been merged to dev branch. Pls test.

This works for me. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature This would improve Cloudlog
Projects
None yet
Development

No branches or pull requests

3 participants