Elevated Radiation in Missouri

[Thomas Peterson]

https://map.safecast.org/?y=39.902&x=-94.149&z=11&l=0&m=0

Location is northwestern Missouri on Interstate 35.

Does anyone know what might be causing this?

[jan.he...@gmail.com]

Hi,

nobody replied yet so at least I try... I looked on the data:

https://api.safecast.org/en-US/users/934/measurements

and looks like it is not measured with Safecast bGeigie detector but some other device so I cannot get any additional information for it.

https://map.safecast.org/?y=49.82985&x=16.23508&z=16&l=0&m=0

in addition - if you check this part:

https://map.safecast.org/?y=39.96552&x=-94.0996&z=16&l=0&m=0

there seems to be another higher value from the same guy but nearby measurement has nothing abnormal:

https://api.safecast.org/en-US/bgeigie_imports/30729

There might be several possibilities...

1) the device showing high values has small detector (thus also bigger distance between measured points) - small detector usually means lower sensitivity and in normal radiation levels too few impulses per measuring interval resulting in greater inaccuracy of dose rate calculation.

2) the device is incorrectly set / faulty

3) there is higher dose rate because of natural radiation (bedrock) or road backfill...

few examples - nothing dangerous here:

https://map.safecast.org/?y=49.4114&x=14.6631&z=15&l=0&m=0

https://map.safecast.org/?y=49.2157&x=15.8802&z=15&l=0&m=0

the best way would be to have a ride there with the bGeigie and check the data.

regards

Jan

Dne neděle 26. listopadu 2023 v 2:03:20 UTC+1 uživatel Thomas Peterson napsal:

[az...@safecast.org]

Thomas: Thank you for pointing this out.   Jan: Thank you for commenting.

This user seems to have managed to upload data from a non-Safecast device using our app, bypassing the moderation process. This data is certainly erroneous. There's a fairly time-consuming "last resort" process for removing those kinds of data points, which I did earlier this year. Obviously I didn't find them all. 

Chers,

Azby