Here is my question. How do I import my POTA Hunter Log QSOs from the POTA website. Since that file does not contain Lat and Lon or GRID info. Are you working on a POTA capability that is other than Activations? Or am I missing something already available>
We currently do not have this functionality to import hunter logs downloaded from the POTA site. This is actually the first we’ve had this request. Since there is no lat/lon, frequency, band/mode, or timestamp it would be difficult to import this data. I don’t think there is a way to download this information from the POTA site easily is there?
The only info from a download is date of QSO and park reference and Park name. Not even the activators call sign. So not a lot of info there. I guess that would entail having a table of Parks with Lat Lon and or grid info. That would make for a serviceable map of Hunted Parks.
The LAt and Lon is somewhere on the POTA database. Because Lat and Lon is shown on every park’s info page. Don’t know if you could get access.
I love maps and would love to see this feature.
Admittedly, my problem is that I don’t log my Hunted parks anywhere. I depend on seeing it on POTA. So my mistake to start Hi hi. Otherwise I could massage my data and display it on one of your maps.
The link you provided is just a list of all the parks, which is already currently being pulled into WRL. The problem is there is no way for us to call the pota site and pull hunted QSO’s for another user. That can (as far as I know) only be done by the user that is logged into the pota site. It also doesn’t look like there is a way for users to download their hunter log either, which is unfortunate (that would be very helpful for some users).
We would either need the ability to pull that data directly from the pota site or pota provide a way for users to download their hunter logs that the user could then upload into WRL.
I am anble to donwload all my Hunted POTA Parks. In a CSV file now. The Park number etc. The only thing lacking is the grid or lat/lon. That is available in the link i sent above. In my simple mind it would appear to me that i would only need a script to pull the Park Number lat/lon or grid location and attach it to my LOG. And create an ADIF file. I THUNK!
I am obviously oversimplifying. But everything is there in the two spreadsheets I have downloaded directly from POTA.
Unfortunately that export from the pota site doesn’t have the QSO data (ie callsign, freq, band/mode, etc) it only has one column that says QSO’s that lists a number of QSO’s that have been hunted as the specific park. We would need the QSO data to be able to fill in a logbook.