Background:
In projects we get feedback that some of our grids don't seem to be 100% correct mathematically.
If we want to reproduce this, it is virtually impossible. It looks like Revit can move things 1.000000001 mm, but a user can't.
The idea:
There must be a reliable relationship between the number of digits Revit can 'display' and the way Revit creates floating point errors. Visually for starters.
And if possible, also in the invisible IT world. Because there ís logic in a digital building.
Considerations:
Every engineer understands that working with trigonometry, curves or infinite divisions (e.g. 1/3) produces strange or almost impossible floats. But if Revit shows a user she/he is copying a Grid 7200mm in a straight line. A user really expects the software to do this. And when a user moves or copies a collection of those grids, that user really expects the software to respect that relationship wherever the user looks.
Bonus:
Perhaps there should (also) be an API command to reset these floats to significant figures, based on specified arguments. At least to solve floating point errors in a rational orthogonal system. This will probably solve most of the user frustration on this topic.
Grids, Levels, Reference planes and Reference lines should be reliable objects to drive real geometry.
