Apologies for posting another issue report. :)
I have noticed that using setArea doesn't actually limit the area for tracking the lightning strikes. Maybe this got changed at some point as well. I am giving it the standard object like so:
area
- from
- latitude: 46.557853
- longitude: 17.702659
- to
- latitude: 44.557853
- longitude: 19.702659
The method accepts the object without any errors, but the API gives strikes for the whole globe regardless.
![image](https://user-images.githubusercontent.com/7534126/89060111-b713b800-d362-11ea-840a-21a4efc3e77b.png)
While this issue does not impede my use case, as I check the distance to strikes anyway, it would help to lower the need for processing so many strikes regardless.