stevemarple/aurorawatchnet

Building a network of magnetometers for auroral alerts and citizen science.

aurorawatchnet's Issues

Have upload_data.py indicate when no data is present.

When upload_data.py runs but no data is found there is no trace on the upload server that the command even ran. In such cases make an empty GET request to indicate that data is missing.

upload_data.py does not handle HTTP redirects

Data transfer fails if a HTTP redirect is issued.

Content of AuroraWatch UK API v1.0 stations file

The auroraplot Python library will be used for data processing. This arranges data by project, site, data type and channel. In our case data type is always magnetometer data so the important items to identify the magnetometers in use will be project and site. The station list must include:

• Station list
  • Station
    • Project (eg. AURORAWATCHNET, SAMNET)
    • Site (eg. LAN1)
    • Location
      • Place (eg. Lancaster, UK)
      • Latitude (N positive)
      • Longitude (E positive)
    • Data attribution
    • Copyright notice
    • License (eg. CC-BY-SA-NC 3,0).

Formatting may follow the convention used by GAIA, http://gaia-vxo.org. See http://calgary.canada.gaia-vxo.org/rest_xml/projects for an example.

Cannot unset remote hostname

Cannot unset remote hostname using send_cmd.py. This prevents a static IP address being used once a hostname has been defined. Workaround is to send an eepromWrite command to the console of the sensor unit.

Silkscreen errors on FLC100 shield v2.0

Silkscreen wrongly states v1.0 (in 4 places).

Making QDCs fails in a new year

Have make_qdc.py create the target directory before attempting to save the file.

Content of AuroraWatch UK API v1.0

I'm generating a list of the information that should included in the v1.0 AuroraWatch UK API. So far I have:

• Threshold list
  • Threshold
    • Status level
    • Lower limit (and upper limit?)
    • Color with RGB values
• Activity list
  • Start time
  • Status level
  • Value
• Station list (list of magnetometers used to compute the current status)
  • Station/instrument/magnetometer
    • Project (eg. AURORAWATCHNET, SAMNET)
    • Site (eg. LAN1)
• Current status
  • Status level
• Previous status
  • Status level
• Creation time
• Status message
  • Message text
  • Issued (ISO8601 datetime)
  • Time-to-live (TTL, in seconds)

If the status message is present, and its message text is not empty, this provides a message which could be presented (silently?) to the user, eg, "System down due to maintenance", "Aurora sighted from Cornwall!". The message should not be displayed after the TTL has expired. If implemented the app is responsible for ensuring the message is not displayed multiple times.

The nested list hints at how the XML document is likely to be structured. The list of stations will be fairly static so I think that is perhaps best left to a separate document to minimise the data transferred. See issue #5 for details.

As much as I hate American spellings I will use "color" since that is the spelling used in HTML/CSS.