View Issue Details

IDProjectCategoryView StatusLast Update
00029263 - Current Dev ListMaintenancepublic2019-04-11 05:18
ReporterPD9FERAssigned ToWA9PIE 
Status assignedResolutionopen 
Product Version 
Target VersionFixed in Version 
Summary0002926: New and altered IOTA data in Logbook

There are some changes/additions in the IOTA designators (see link above)
Customer worked a station in IOTA NA-249P but it is not in the list.
Steps To ReproduceOpen ALE
Open the IOTA List dropdown
Look for NA-249 It is not there.

Additional InformationTicket #874915

Changes where made, use the link
for those.

The file was provided by the IOTA site on RSGB in XML format (filename: fulllist.xml). Periodically, we downloaded it and made the update. It seems that there are new entries to this list.

TagsNo tags attached.
TestingNot Started



2019-02-15 11:02

administrator   ~0007401

We've had a few more tickets on this topic and we should address it.


2019-03-23 07:26

administrator   ~0007724

Ticket #827216 just received about when and how the IOTA in HRD would be updated.


2019-04-09 11:18

manager   ~0007845

Where can I find documentation on the suggested API?


2019-04-09 12:05

manager   ~0007846

I've dug around on their site a bit, and this is all I can find:

so I've written the email address given there to request information about their API, licensing, and acceptable use.


2019-04-11 05:18

manager   ~0007847

I got in touch with the IOTA team. A given API key is good for only 1000 queries per day, so we'll need to build a reflector -- in the same way we have for the solar weather data. We'll need to decide how that works, how often it updates, and how it is monitored.

Architecturally, we'll need to figure out how to handle the format change; the existing code expects an XML format for IOTA data, while the new format is JSON. Does the forwarding service provide XML, or JSON, or a completely new format? It's not much fun parsing JSON in C++, so it seems like we should stick with XML or invent our own format -- seems like CSV would be fine, and simpler and faster than XML. Either way, if we're not sending JSON to the applications, then we need to have code translate the JSON into the redistributed format rather than simply serve a specific file.

I'm not sure how these decisions should/would be addressed by the team.

Issue History

Date Modified Username Field Change
2018-10-30 08:05 PD9FER New Issue
2018-10-31 16:38 WA9PIE Additional Information Updated View Revisions
2018-10-31 16:38 WA9PIE Assigned To => PD9FER
2018-10-31 16:38 WA9PIE Status new => assigned
2019-02-15 11:02 WA9PIE Note Added: 0007401
2019-02-15 11:02 WA9PIE Project 1 - Backlog => 3 - Current Dev List
2019-02-15 11:02 WA9PIE Assigned To PD9FER => K7ZCZ
2019-03-23 07:26 KB3NPH Note Added: 0007724
2019-04-09 11:18 K7ZCZ Note Added: 0007845
2019-04-09 11:18 K7ZCZ Assigned To K7ZCZ => WA9PIE
2019-04-09 12:05 K7ZCZ Note Added: 0007846
2019-04-11 05:18 K7ZCZ Note Added: 0007847