There is an issue with the XML lookup process, which is returning erroneous information and may require attention. I use the current expedition TO3K (2 August 2025 to 10 August 2025) as an example; however, I have encountered this problem on multiple occasions in the past. Issue: The XML data returns information not associated with the expedition's callsign but rather with the operator requesting its addition to QRZ. See the attached image. All the information within the red square pertains not to TO3K but to an Italian operator. Moreover, the grid square and GPS coordinates inexplicably correspond to Paris, France. Instructions in the QRZ Database Helpers Forums (as of 2 August 2025) state the following: --------------------------------------------- HOW TO ADD YOUR CALLSIGN TO THE QRZ DATABASE Your QRZ username must be the same as your callsign You must provide your name and surname, town or city, nation, and DXCC entity A PDF or JPG of your amateur radio license showing both your name and callsign (do not use a QSL card, driver's license, national ID card, passport, or personal photo) --------------------------------------------- This process is suitable for non-U.S. operators who wish to add their callsigns to the database. The problem arises when the callsign being added is that of a temporary expedition. The instructions ask individuals to provide their "town or city, nation, and DXCC entity," but this request is ambiguous, as it may refer not to the expedition in question but to the operator requesting the addition. This misinterpretation causes the XML data to populate with incorrect information. It appears that the person entering the data reasonably assumes the instructions are asking for their personal details rather than those of the expedition. Information regarding QSLing, expedition leadership, and related matters can and should be included in the biography section. Of course, QSL manager information is returned in the XML data. I suggest revising the instructions to specifically address the issue of temporary expeditions, ensuring that the added information pertains to the entity itself in order to prevent erroneous XML data—especially given that this is a paid service.
The detail tab for TO3K shows Paris as the location. QRZ did not enter this information the admin, IK3ZAQ did.
That's my point. We need better instructions so those entering that data know what they should enter. The information entered is NOT related to TO3K because the instructions are a bit vague in the case of expeditions. ...............Bob
