Thanks for the reply, and I do understand your frustration - but yes, I did read it. Would the issue noted affect my MesoWest location? It is also wrong, however it seems most of the people in that thread had correct MW positions.
https://www.wrh.noaa.gov/mesowest/getobext.php?wfo=lox&sid=F0821&num=48Lat/Lon: 47.61183/-122.31367
http://www.findu.com/cgi-bin/raw.cgi?call=FW0821FW0821>APRS,TCPXX*,qAX,CWOP-7:@141501z
4741.86N/12220.83W_318/000g000t045r000p001P001b10171h94L000.WD 31
If that's the case, then I can just wait to see what happens when they get the backend databases all synced again, but I was mostly concerned that the wrong location was flowing outward. I could deal with indication only on gladstonefamily.net, but I got concerned when it seemed that it affected the location of the downstream sites.
Thanks.