I am having trouble getting OpenRoads to recognize tc and C that enter for a Catchment using composite tables. It keeps wanting to use the user-defined tc and c that were entered earlier...
When the above is changed to below...
… the catchment recognizes only the input that was entered in as user-defined...
… does anybody have any idea what is causing this?
The attribute feedback display is showing the user-defined entry, but if you check the results you'll see that the composite "c" value is being used in the calculations.
Karl Dauber, PEAdvance ConsultingLaurens County, SCkarldauber@advconsult.netwww.advconsult.netwww.linkedin.com/in/karldauber
Thank you so much for your reply. It is using the composite c for calculations, but it is also using the user-defined tc for calculations, which seems very strange. Do you know how to change what values it uses for calculations and what values it shows in the heads up display?
JonMark, I just tried it in 2020 R1 version. The Tc works the same as the C value. When using composite values, the calculations are correct but the attribute feedback display is not updated.