NoiseCapture icon indicating copy to clipboard operation
NoiseCapture copied to clipboard

Use gps precision when computing hexagon

Open nicolas-f opened this issue 7 years ago • 5 comments

Include measure point in hexagons intersecting with the circle of the measure point defined by it's precision.

nicolas-f avatar Jul 19 '17 05:07 nicolas-f

Don't understand. Do you want to collect the data for each hexa according the GPS precision ?

ebocher avatar Jul 19 '17 08:07 ebocher

The idea is to affect the noise level value of a given point to the corresponding hexagons in function of the value of the GPS accuracy for the corresponting point. For example, if the GPS accuracy is 20m for a given point, then the sound level at this point could be affected to several hexagons.

Picaut avatar Jul 20 '17 09:07 Picaut

Ok sounds good Thanks

ebocher avatar Jul 20 '17 09:07 ebocher

But it means that we could affect several times the same value ? Also, worst will be the GPS accuracy, more weight will have the value ?

pierromond avatar Jul 20 '17 11:07 pierromond

Yes. The point could be on each on the hexagon. It seems difficult to weight the sound level at this step. Remember that this first map (with the hexagons) is a "raw" map including all raw data without any filtering (the only filtering is based on the GPS accuracy: if greater than 15m, the point is not considered).

We will be able to propose new maps (with a better process) in a next step.

Picaut avatar Jul 21 '17 13:07 Picaut