Hey @Rich Howard,
I think it would be good to move the Height Measurement option (ground, stump, other) to the cruise design level, rather than the calibration level, since this would vary between cruise types rather than between calibrations.
top of page
To see this working, head to your live site.
Comments (2)
bottom of page
I think having settings in both would be fine - perhaps just have any new cruise records use the calibration setting unless the user specifies otherwise?
Of course, a user could just modify cruise data before compiling to account for whatever the calibration is set to, but that has less of a paper trail and could lead to multiple overwrites and subsequent data loss.
Very true for cruise data, but Height Measurement is also used during growth and simulation where the original cruise design is no longer tracked. For example, seedlings and growth equations. The database reads and stores height data according to Height Measurements and Assisi must convert correctly when heights are read in and heights are saved. Calibration is the more universal place to put it.
Still, does it makes sense to have both a cruise level height setting and a calibration level height setting? Or perhaps a cruise level height setting and a database level height setting?
Thoughts?