Settings
How each building is configured, and the limits that cannot be changed.
Building settings
Changes are logged| Building | Closes within | Early warning | Reopen wait | Reopens on its own | |
|---|---|---|---|---|---|
|
Hammock Club
13013 Boggy Creek Dr, Riverview, FL 33579
|
11.0 mi | Yes | |||
|
Streambed
11920 Streambed Dr, Riverview, FL 33579
|
11.0 mi | Yes | |||
|
Tripoli
12809 Boggy Creek Dr, Riverview, FL 33579
|
11.0 mi | Yes |
"Closes within" is how near lightning has to strike before this building closes. 10 miles is the recommended setting — a smaller ring closes less often but leaves less warning. The early-warning distance follows automatically one mile further out, so there is only one number to decide. Every change is recorded in the closure log.
Checking & spending
Takes effect within ~30 seconds, no restartLimits that cannot be lowered
| Reopen wait floor | 30 minutes — may be raised per site, never lowered |
| Minimum poll spacing | 15s enforced in code, regardless of configuration |
| Current poll interval | 60s |
| Reopen early | Does not exist. Staff may close early or hold closed longer only. |
| Ambiguous strikes | A poorly located ground strike within 1 mi outside the ring counts as inside |
Free-tier allowance
1075 calls leftThe weather service gives 15,000 free accesses a month across everything, and lightning requests count as ten each — so the real allowance is 1,500 lightning calls. There is no spending limit at their end, so this cap is enforced here instead: when it runs out the system stops calling out and shows a warning rather than running up a bill. Adding a payment method in the Xweather portal is what lifts it.
Data feed
xweather| When | Strikes | Pages | Latency | Closest-first | Result |
|---|---|---|---|---|---|
| 01:59:28Z | 0 | 1 | 734 ms | yes | OK |
| 01:55:12Z | 0 | 1 | 702 ms | yes | OK |
| 01:53:04Z | 0 | 1 | 702 ms | yes | OK |
| 01:48:48Z | 0 | 1 | 734 ms | yes | OK |
| 01:44:32Z | 0 | 1 | 765 ms | yes | OK |
| 01:40:16Z | 0 | 1 | 843 ms | yes | OK |
| 01:36:00Z | 0 | 1 | 890 ms | yes | OK |
| 01:31:44Z | 0 | 1 | 827 ms | yes | OK |
| 01:27:28Z | 0 | 1 | 811 ms | yes | OK |
| 01:23:12Z | 0 | 1 | 765 ms | yes | OK |
| 01:21:04Z | 0 | 1 | 811 ms | yes | OK |
| 01:16:48Z | 0 | 1 | 844 ms | yes | OK |
| 01:12:32Z | 0 | 1 | 938 ms | yes | OK |
| 01:08:16Z | 0 | 1 | 844 ms | yes | OK |
| 01:04:00Z | 0 | 1 | 905 ms | yes | OK |
| 00:59:44Z | 0 | 1 | 1047 ms | yes | OK |
| 00:55:28Z | 0 | 1 | 561 ms | yes | OK |
| 00:51:12Z | 0 | 1 | 875 ms | yes | OK |
| 00:46:56Z | 0 | 1 | 907 ms | yes | OK |
| 00:44:48Z | 0 | 1 | 813 ms | yes | OK |
| 00:40:32Z | 0 | 1 | 1780 ms | yes | OK |
| 00:36:16Z | 0 | 1 | 813 ms | yes | OK |
| 00:32:00Z | 0 | 1 | 907 ms | yes | OK |
| 00:27:44Z | 0 | 1 | 780 ms | yes | OK |
| 00:23:28Z | 0 | 1 | 842 ms | yes | OK |
Closest-first matters because a single query returns at most 1000 strikes. If the provider sorts nearest-first, anything dropped is the farthest away and least relevant. This column records that per poll so a silent change in their behaviour surfaces here rather than quietly losing strikes.