-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors in calculation depending on the separation between receivers #641
Comments
Hi, There is an issue with the column type that can't store -1155.2235 dB We could set a minimum value when storing levels or change the column type. What emission value you set on your sound source ? (because there is only DEM in your files) |
Sorry. Here is the correct ZIP file: I have verified that the following files exist: |
Any news?? ;) |
It should not crash with the last automated build: But looking if it is an issue with such a large computation will take some time. If you are using the geoserver based release you have to replace the noisemodelling jar file noisemodelling-jdbc and the groovy script Noise_level_from_source.groovy and Noise_level_from_traffic.groovy |
NoiseModelling version
4.0.5
Describe the bug
Calculating large scale model (Large number of sources, receivers, buildings). Accurate DEM (25x25 m)
When the distance between receivers is less than 150 m, a calculation error occurs, which is repeated in several phases of the process.
When calculation processs finishes, the Lday_geom, levening_geom... tables are empty.
If the distance between receivers is greater than 150 m, calculate carefully.
I have tried uninstalling and installing NoiseModelling, and redoing from the beginning. The problem always repeats itself.
To Reproduce
Process file: Process.txt
SourceData files: https://drive.google.com/file/d/1L9Xis8nylmkYW5ukrb7V0SGkto2JrHmL/view?usp=sharing
Geoserver log
See this errror "INSERT INTO LDAY_RESULT VALUES (? , ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [22001-214]
org.h2.jdbc.JdbcSQLDataException: Valor demasiado largo para la columna "HZ8000 NUMERIC(5, 2)": "CAST(-1155.2235037857104 AS DOUBLE PRECISION) (53)"
Attach geoserver log: geoserver - copia.log
The text was updated successfully, but these errors were encountered: