(2026-03-21, 23:58)cutty Wrote: From the nature of your other posts, I might suggest you review all the Blitzortung documentation. No, there's no 'explicit measure of error'. It's an assumed 'deviation' of location for each stroke for each station. It IS displayed for each stroke in various map view configurations. It is a computed, assumed error based on a large number of variables mixed with hard data....
Ok, so I was looking at the JSON-formatted "raw" data availble to project members. It appears that each element (object) is a strike detection with an array of descriptors of base stations that contributed to the detection. What if I used that data and looked at one or more of the follwing statistics for an area around my new detector:
- Total number of lightning strikes in a time period before and after installation
- Number of base stations participating in a strike detection
- Maximum angle subtended by any two adjacent detectors (as seen by the strike location)