Check pyhamtools callinfo for lat/Lon of DXCC from static country info as a last resort. Closes #13

webassets/apidocs/openapi.yml

@@ -417,6 +417,19 @@ components:
           type: number
           description: Latitude, in degrees. This could be from a geographical reference e.g. POTA, or from a QRZ lookup
           example: -1.2345
+        location_source:
+          type: string
+          description: Where we got the location (grid/latitude/longitude) from. If this was from the spot itself, it's likely quite accurate, but if we had to fall back to QRZ lookup, or even a location based on the DXCC itself, it will be a lot less accurate.
+          enum:
+            - SPOT
+            - QRZ
+            - DXCC
+            - NONE
+          example: SPOT
+        location_good:
+          type: boolean
+          description: Does the software think the location is good enough to put a marker on a map? This is true if the source is "SPOT", or alternatively if the source is "QRZ" and the callsign doesn't have a slash in it (i.e. operator likely at home).
+          example: true
         qrt:
           type: boolean
           description: QRT state. Some APIs return spots marked as QRT. Otherwise we can check the comments.