I'm a new member, and I registered using the grid square given to me by W7MD.net. Apparently they had my wrong latitude and longitude. When I entered my correct coordinates, I was given the correct grid square. eQSL won't let me change the grid square on my profile...what's up with that? How can I make the correction? Thanks.

---

W3WHK Saul F. Broudy

It is because QTH information on eQSLs comes from what is stored in the user profile. What we are preventing is users moving to a new QTH and then updating the QTH info in their profile, because that changes it on all the eQSLs previously sent. We require a new, attached account to be created in that case with the new QTH info.

In your case, where you made a mistake, all you need do is contact support using the "Help!" link at the top of this page, be sure to say you made a mistake when you entered your grid and say what the grid should be and we will fix it.

---

73, Dave - VA3KAB

This sounds like a major design flaw of the eQSL system.

Logbook of the World allows a call sign to be used across multiple QTH locations. When the operator uploads their QSOs they chose their location. The Gridsquare of that location is associated with the QSO. Changing QTH information does not result in changing the QTH info on previously submitted QSOs.

Is eQSL looking to fix this design flaw?

---

K3JSJ JOHNSON, JASON S
Edited by K3JSJ JOHNSON, JASON S on Feb 10, 2021 at 03:51 AM


Edited by F6DKQ Guy FALCOZ on Feb 10, 2021 at 08:53 PM

So does eQSL, with LOTW, you create different QTH's in TQSL, locally, on your computer
With eQSL you create qth/nicknames on the server itself

the main difference is that eQSL does not allow OVERLAPPING dates for a same CALLSIGN, multiple locations.

I know that the webmaster is working at solutions for highly mobile stations
This has already been discussed in the forum

---

73 - F6DKQ
Edited by F6DKQ Guy FALCOZ on Feb 10, 2021 at 08:55 PM

Also consider that our primary goal is to create a unique eQSL card you can print, that has QTH-specific information on it. Thus each QTH needs potentially a different looking card, or at the very least, different text overlaid on the graphic. If someone goes mobile on a trip from Florida to California and wants to have different card designs for each state, we need to allow for that. So we use a relational database where each QTH has its own "account" with potentially different QSL design information, and the QSOs just point to that account. Now imagine he's also a county hunter and thus operates from 300 different counties, and has 300 accounts. The management of that with the current screens would be a nightmare. SO we are developing some new screens that allow management of a large number of QTHes easily. But easily for the user is not easily for the developer, and thus it's taking longer than we expected. I have a friend who recently flew around the world in his airplane, operating airmobile, and uploading logs all along the way. That's my test case, and as soon as it works in that acid test, we'll release it for everyone.

---

Of course, that's just my opinion... I could be wrong!

73,
Dave Morris, N5UP

Thank you for that information. I am having trouble understanding using the same call sign across multiple grid squares

---

K3JSJ JOHNSON, JASON S

Follow up question hopefully someone will be able to answer. Say you operate from home exclusively for 100 days. Then on day 101 you make QSOs from you home and another location. Then day 102 forward you operate from home. In all three cases you use your callsign and no suffix.

Is is possible to QSL all the calls from both your home (grid x) and another location (grid y) for day 101?

For QSOs from you home
Do you define one QTH for days 1-100 and one QTH for days 102 forward?

---

K3JSJ JOHNSON, JASON S

No

home1
other location
home2

...from home -> home1

---

73 - F6DKQ



Edited by F6DKQ Guy FALCOZ on Apr 17, 2021 at 05:00 AM