Changes between Version 759 and Version 760 of doc/app/errmsg

Timestamp:

Apr 9, 2021 1:07:52 PM (4 years ago)

Author:

suehring

Comment:

--

doc/app/errmsg

@@ -790 +790 @@
 ||[=#PA0571 PA0571]  || If soil_type(y,x) = 0, all levels of soil_pars at this location must be set || ||
 ||[=#PA0572 PA0572]  || If building_type(y,x) = 0, all parameters of building_pars at this location must be set || ||
-||[=#PA0573 PA0573]  || Each location where a  building is set requires a type ( and vice versa ) in case the urban-surface model is applied. i, j =  ( , ) ||Apart from the obvious inconsistent setting of building input data, please check if building_id has reasonable numbers. Even though building_id's can be set arbitrary, only values representable on a 32-bit integer can be used. For ids that cannot be represented, errors in the building processing can happen, causing this error. ||
+||[=#PA0573 PA0573]  || Each location where a  building is set requires a type ( and vice versa ) in case the urban-surface model is applied. i, j =  ( , ) ||Apart from the obvious inconsistent setting of building input data, please check if building_id has reasonable numbers. Even though building_id's can be set arbitrary, only values representable on a 32-bit integer can be used. For ids that cannot be represented, errors in the building processing can happen, causing this error. Another reason could be that the model domain is too shallow and thus the building and surface classification does not work properly. ||
 ||[=#PA0574 PA0574]  || Each location where a  building is set requires an ID ( and vice versa ). i, j =  ( , ) ||Apart from the obvious inconsistent setting of building input data, please check if building_id has reasonable numbers. Even though building_id's can be set arbitrary, only values representable on a 32-bit integer can be used. For ids that cannot be represented, errors in the building processing can happen, causing this error.||
 ||[=#PA0575 PA0575]  || Each building grid point requires an ID. || ||