9 hours ago
(Edit: URLs are not allowed, so removing them, mentally add them where appropriate)
Tried to search this forum with all the relevant keywords but could not find this to have been discussed. Sorry in advance if I'm mistaken.
I am writing software to fetch the recent strikes as per documentation, and while everything else seems to work perfectly, the "time" parameter in the URL seems to be ignored.
/Data/Protected/last_strikes.php?time=1778840631155816319&number=30000&west=10&east=40&north=70&south=50&sig=0
done at time 1778840931155816319 (i.e. the request limit is 5 min earlier) results in response containing (as last record, there were 1188 records, so the "number" parameter did not limit anything either)
{"time":1778827480863817500,"lat":60.535376,"lon":33.547539,"alt":0,"pol":0,"mds":14367,"mcg":242,"status":0,"region":1}
Here are the times again with a fixed width font and a space separating seconds from nanoseconds
REQUEST: 1778840631 155816319
REQUEST DONE AT: 1778840931 155816319
RESPONSE: 1778827480 863817500
So the record is almost 4 hours old. I can easily filter those out, but just wondering whether there is a bug or I just do not understand something here. Likely the latter.
Also, the documentation states that the default value of the "time" is "current time stamp", which cannot possibly be true? Wouldn't that filter out all the strikes automatically (and by default!)?
Anyway, being new to this project and community, I have to say that I am deeply impressed by the quality of everything. Especially I love the no-nonsense diagnostic page of the station!
Tried to search this forum with all the relevant keywords but could not find this to have been discussed. Sorry in advance if I'm mistaken.
I am writing software to fetch the recent strikes as per documentation, and while everything else seems to work perfectly, the "time" parameter in the URL seems to be ignored.
/Data/Protected/last_strikes.php?time=1778840631155816319&number=30000&west=10&east=40&north=70&south=50&sig=0
done at time 1778840931155816319 (i.e. the request limit is 5 min earlier) results in response containing (as last record, there were 1188 records, so the "number" parameter did not limit anything either)
{"time":1778827480863817500,"lat":60.535376,"lon":33.547539,"alt":0,"pol":0,"mds":14367,"mcg":242,"status":0,"region":1}
Here are the times again with a fixed width font and a space separating seconds from nanoseconds
REQUEST: 1778840631 155816319
REQUEST DONE AT: 1778840931 155816319
RESPONSE: 1778827480 863817500
So the record is almost 4 hours old. I can easily filter those out, but just wondering whether there is a bug or I just do not understand something here. Likely the latter.
Also, the documentation states that the default value of the "time" is "current time stamp", which cannot possibly be true? Wouldn't that filter out all the strikes automatically (and by default!)?
Anyway, being new to this project and community, I have to say that I am deeply impressed by the quality of everything. Especially I love the no-nonsense diagnostic page of the station!
