Refactor of caching & data storage part 4 #118

spotproviders/towers.py

@@ -30,8 +30,8 @@ class Towers(HTTPSpotProvider):
                         dx_call=source_spot["call"].upper(),
                         freq=likely_freq,
                         comment=source_spot["comment"],
-                        sig="WWTOTA",
-                        sig_refs=[SIGRef(id=source_spot["ref"], sig="WWTOTA")],
+                        sig="Towers",
+                        sig_refs=[SIGRef(id=source_spot["ref"], sig="Towers")],
                         time=datetime.strptime(response_json["updated"][:10] + source_spot["time"],
                                                "%Y-%m-%d%H:%M").timestamp())
 

spotproviders/wota.py

@@ -25,7 +25,7 @@ class WOTA(HTTPSpotProvider):
 
     def _http_response_to_spots(self, http_response):
         new_spots = []
-        rss = cast(RSS, Parser.parse(http_response.content.decode()))
+        rss = cast(RSS, Parser.parse(http_response.content.decode("utf-8-sig")))
         # Iterate through source data
         for source_spot in rss.channel.items:
 

spotproviders/xota.py

@@ -11,7 +11,7 @@ from spotproviders.websocket_spot_provider import WebsocketSpotProvider
 class XOTA(WebsocketSpotProvider):
     """Spot provider for servers based on the "xOTA" software at https://github.com/nischu/xOTA/
     The provider typically doesn't give us a lat/lon or SIG explicitly, so our own config provides a SIG which we can
-    then use for lookups. This functionality is implemented for TOTA events, of which there are
+    then use for lookups. This functionality is implemented for Toilets on the Air events, of which there are
     several - so a plain lookup of a "TOTA reference" doesn't make sense, it depends on which TOTA, which is why we also
     provide a sig_ref_prefix in our config. This is applied to the reference ID, so e.g. "T-01" at C3 might become
     "C3 T-01". This allows us to provide location lookups for TOTA at several conferences."""