View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002926||2 - Next Dev List (Holding Area)||Maintenance||public||2018-10-30 08:05||2019-06-16 17:38|
|Summary||0002926: 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 Reproduce||Open ALE |
Open the IOTA List dropdown
Look for NA-249 It is not there.
|Additional Information||Ticket #874915 |
Changes where made, use the link https://www.iota-world.org/info/new_groups_2018.pdf
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.
|Tags||No tags attached.|
||We've had a few more tickets on this topic and we should address it.|
||Ticket #827216 just received about when and how the IOTA in HRD would be updated.|
||Where can I find documentation on the suggested API?|
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.
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.
||Doesn't this API essentially build the list? And if so, can't we build the list once... at the time we compile code?|
If we build the list when the code is complied, then we won't pick up changes until the next version is compiled. Customers won't pick up the changes until the next time they install a new version. Building new versions of code to accommodate changes in external data doesn't seem like a good pattern to me.
Plus, as I detail above, the API produces data in a format that we're not prepared to consume.
Attached are the IOTA docs I was sent. They're very scant--in particular, no meaningful definitions for each field in the data that's provided by the API.
On our side, we don't have any documentation for the existing IOTA XML format, or for any of the IOTA features themselves. This means we have to go through the code to figure out what the data does and what it's used for. Then, we'll need to get data from the new IOTA API and compare it to what we can infer about the old XML format to see if there's a direct replacement or not ... or if some translation is needed.
||second try at the attachment ...|
||Looks like attachments aren't working right for me :(|
|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|
|2019-05-10 18:31||WA9PIE||Note Added: 0007929|
|2019-05-12 20:52||K7ZCZ||Note Added: 0007931|
|2019-05-13 12:57||K7ZCZ||Note Added: 0007932|
|2019-05-13 12:58||K7ZCZ||Note Added: 0007933|
|2019-05-13 12:59||K7ZCZ||Note Added: 0007934|
|2019-06-16 17:38||WA9PIE||Project||3 - Current Dev List => 2 - Next Dev List (Holding Area)|