You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When "enrich_DEM_with_roads" is run, it gives the following error:
"Process failed during execution javax.script.ScriptException: org.h2.jdbc.JdbcSQLSyntaxErrorException: Columna "POS_SOL" no encontrada Column "POS_SOL" not found; SQL statement: CREATE TABLE dem_roads AS SELECT THE_GEOM, 'ROAD' as SOURCE, (CASE WHEN ROADWIDTH>3 THEN ROADWIDTH/2 ELSE 1.5 END) as WIDTH FROM ROADS_z WHERE POS_SOL = '0' AND st_zmin(THE_GEOM [42122-214] org.h2.jdbc.JdbcSQLSyntaxErrorException: Columna "POS_SOL" no encontrada Column "POS_SOL" not found; SQL statement: CREATE TABLE dem_roads AS SELECT THE_GEOM, 'ROAD' as SOURCE, (CASE WHEN ROADWIDTH>3 THEN ROADWIDTH/2 ELSE 1.5 END) as WIDTH FROM ROADS_z WHERE POS_SOL = '0' AND st_zmin(THE_GEOM [42122-214] Columna "POS_SOL" no encontrada Column "POS_SOL" not found; SQL statement: CREATE TABLE dem_roads AS SELECT THE_GEOM, 'ROAD' as SOURCE, (CASE WHEN ROADWIDTH>3 THEN ROADWIDTH/2 ELSE 1.5 END) as WIDTH FROM ROADS_z WHERE POS_SOL = '0' AND st_zmin(THE_GEOM [42122-214]"
To Solve
It seems that it is necessary that the "roads" layer has the "POS_SOL" field, with value = "0". If this field exists, it works!
For more details
Enriching the DEM avoids errors in the calculation.
In the following images it is observed that, without DEM enrichment, "strange" results are predicted. Possibly due to sources that remain below the terrain.
DEM enrichment works like the "raise all sources above terrain" option available in other softwares.
Without DEM enrichment:
With DEM enrichment:
good job guys!
The text was updated successfully, but these errors were encountered:
NoiseModelling version
4.0.5
Describe the bug
When "enrich_DEM_with_roads" is run, it gives the following error:
"Process failed during execution javax.script.ScriptException: org.h2.jdbc.JdbcSQLSyntaxErrorException: Columna "POS_SOL" no encontrada Column "POS_SOL" not found; SQL statement: CREATE TABLE dem_roads AS SELECT THE_GEOM, 'ROAD' as SOURCE, (CASE WHEN ROADWIDTH>3 THEN ROADWIDTH/2 ELSE 1.5 END) as WIDTH FROM ROADS_z WHERE POS_SOL = '0' AND st_zmin(THE_GEOM [42122-214] org.h2.jdbc.JdbcSQLSyntaxErrorException: Columna "POS_SOL" no encontrada Column "POS_SOL" not found; SQL statement: CREATE TABLE dem_roads AS SELECT THE_GEOM, 'ROAD' as SOURCE, (CASE WHEN ROADWIDTH>3 THEN ROADWIDTH/2 ELSE 1.5 END) as WIDTH FROM ROADS_z WHERE POS_SOL = '0' AND st_zmin(THE_GEOM [42122-214] Columna "POS_SOL" no encontrada Column "POS_SOL" not found; SQL statement: CREATE TABLE dem_roads AS SELECT THE_GEOM, 'ROAD' as SOURCE, (CASE WHEN ROADWIDTH>3 THEN ROADWIDTH/2 ELSE 1.5 END) as WIDTH FROM ROADS_z WHERE POS_SOL = '0' AND st_zmin(THE_GEOM [42122-214]"
To Solve
It seems that it is necessary that the "roads" layer has the "POS_SOL" field, with value = "0".
If this field exists, it works!
For more details
Enriching the DEM avoids errors in the calculation.
In the following images it is observed that, without DEM enrichment, "strange" results are predicted. Possibly due to sources that remain below the terrain.
DEM enrichment works like the "raise all sources above terrain" option available in other softwares.
Without DEM enrichment:
With DEM enrichment:
good job guys!
The text was updated successfully, but these errors were encountered: