My March log. I got the contact yesterday at 23:58 and then again as the clock rolled over. It was a couple seconds after it rolled over to 00:00 that I called him, and then it would have taken at least ten seconds for the contact to take place and for me to log the contact but the software logged it as 00:00:00 and failed to log the Park number. I refreshed the page and it still didn’t add the park number.
I had no other contacts between these two so nothing at all was changed on the logging page other than the date/time.
I edited the contact and added the park and saved it, but WRL would not add it to the contact. I tried a couple more times and then made a screenshot and submitted this report.
So the issues are showing the contact at 00:00:00 when it was more likely 00:00:15, the failure to show the park, and the failure to show the park even after I manually input the park number.
I’m guessing that if I manually adjust the time to 00:01 that things would work themselves out, but I left it as is so the team can look at it unaltered.
@W7YBY This is because there is only park information for one of those two contacts and not both. The UTC day logic applies to pota hunting/activating, so if both contacts had park data then it wouldn’t show as a dupe. For regular logging there is a 12 hour window for the dupe logic.
@K4AZE Brad, please re-read the original post. The reason there isn’t Park info for the second contact is because WRL would NOT put the Park info in there, either automatically or manually as I tried to do several times.
Also, WRL logged the contact as 00:00:00, not as 00:00:15 or 00:00:20 whenever it was I actually logged it, which is what led me to believe that the time issue had something to do with it showing as a Dupe and not letting me load the Park info.
And the third issue was the distance not filling in for the KA9GWM contact that following morning. As of 07:00 UTC on 03/28 it still hasn’t filled in the distance.
@W7YBY So as far as the time goes we dont have mm:ss:ms so if its 00:00:20 or whatever you would either need to leave it as 00:00 or 00:01, it does update the time. It also updates the park without any issue, you’ll just need to figure out what park he was at via the pota page and add it in there.
As far as the distance goes, im not 100% sure. If this was a contact that was made by double clicking a spot (that had a park reference attached and for whatever reason it didn’t add the park) It could be trying to do the distance calculation based off of the park but since the park isn’t added its not adding the distance.
In this case i would simply find the park the user was at, then just relog the contact with the park added and delete the original log entry, that will clear up everything else.
We’ve pushed several changes around the spotting tab the last couple of days.
