Forum Post: RE: The maximum elevation for the rating table is not the same as the headwater maximum

Hi Mark, Thanks for sending the files. I'm uncertain exactly why this is needed, but if you change the datum to zero and re-type in the values, it works. Here's the "fixed" model: Basically I changed the user defined outlet's "elevation" to zero, global edited the elevation column in the rating table itself and added 90.6. I then re-typed in the first and last elevation in the rating table and in the min/max headwater range in the composite outlet structure. I have also combined the two aforementioned articles that Sushma sent into one, and added this workaround: Notifications about minimum or maximum elevations on the rating table not matching the headwater range