When you have calculated a noise contour or noise levels at individual receivers, you will need to analyse them to extract conclusions about the noise impact of your project.<\/p>\n
NoiseMap has a ‘Results Processor’ to help with this. Previous versions of NoiseMap had\u00a0 \u2018Compare contour\u2019\u00a0, \u2018Noise Floor\u2019 and \u2018Offset to add\u2019 functions, but the Results Processor lets you create your own processing functions.<\/p>\n
In summary, you can:<\/p>\n
The results processing can be as complex as you need, although \u2018house-counting\u2019 functions will come later.<\/p>\n
Creating\u00a0 results expressions<\/strong><\/p>\n You write\u00a0expressions using a notation similar to that of Excel. For example, assuming R1,\u00a0R2\u00a0and R3 are three sets of noise contours or receiver results, then:<\/p>\n R1 – R2 calculates the difference contour\/results<\/p>\n LOGSUM(R1, R2, R3)\u00a0 calculates the cumulative effect of the results<\/p>\n MAX(R1,30)\u00a0applies a\u00a0noise floor of 30 dB\u00a0to result\u00a0R1<\/p>\n If(R1>67.5) and (R1>(R2+1)),1,0) could test for noise insulation<\/p>\n The results processor provides 25 mathematical operators, permitting a wide range of in-line processing.<\/p>\n Moreover, because receiver noise levels can be imported from an external file, these could be used as criteria\u00a0 to check for exceedances, for example on a construction site.<\/p>\n You can import results expressions from a script file, which allows complex\u00a0processes to be prepared in advance and used as required.<\/p>\n Practical examples are shown here<\/a><\/strong>.<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" When you have calculated a noise contour or noise levels at individual receivers, you will need to analyse them to extract conclusions about the noise impact of your project. NoiseMap has a ‘Results Processor’ to help with this. Previous versions of NoiseMap had\u00a0 \u2018Compare contour\u2019\u00a0, \u2018Noise Floor\u2019 and \u2018Offset to add\u2019 functions, but the Results … Continue reading Results Processor<\/span>