You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 3, 2024. It is now read-only.
It looks like fetching lightning strikes doesn't work with metolib. When trying something like this
var STORED_QUERY_LIGHTNING = "fmi::observations::lightning::multipointcoverage";
fi.fmi.metoclient.metolib.WfsRequestParser.getData({
url : url,
storedQueryId : STORED_QUERY_LIGHTNING,
requestParameter : "ellipse_major",
begin : new Date('2015-06-24'),
end : new Date('2015-06-25'),
bbox : "20.750000000000014,61.60639637138627,45.00000000000002,66.51326044311185",
timestep : 60 * 60 * 1000,
callback : function(data, errors) {
handleCallback(data, errors, "strikes");
}
});
No data is returned in callback (although server is returning a lot of data). Difference to other multipointcoverage stuff seems to be that there is no target:LocationCollection information in xml, which seems to result in metolib parser ignoring everything.
It would be nice to get this working.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It looks like fetching lightning strikes doesn't work with metolib. When trying something like this
No data is returned in callback (although server is returning a lot of data). Difference to other multipointcoverage stuff seems to be that there is no target:LocationCollection information in xml, which seems to result in metolib parser ignoring everything.
It would be nice to get this working.
The text was updated successfully, but these errors were encountered: