16 Jan
2020
16 Jan
'20
2:36 p.m.
Awesome work Joe! Glad UMass has such a lousy orientation :-)
Thanks, Heimir. K1JT did some work there a few years back that got a bit of notice, so I'm glad to get noticed also.
I am considering adjusting the response to the APIs in case something goes wrong:
{
"payload": [],
"errors": [{
"code": 1,
"description": "Resource is bad"
},
]
}
Additionally, HTTP Status Codes in the 400-599 range are sent as a secondary indication of a problem.
Speaking of things going wrong, QO-100 has no "passes" as such. Except at the very edge of the footprint it never rises and sets. I'd love to hear ideas on how to handle this case.
de KM1P Joe