hen placing contour labels on a sloped Toposolid Revit does not reliably orient the label text to read uphill — that is, from the lower elevation toward the higher elevation. In standard topographic practice (and in most international drafting standards), contour labels must always be readable from the downhill side, with the text facing upward along the slope. This ensures that anyone reading the drawing can immediately understand the direction of rise without needing additional notation.
Currently in Revit:
• Label orientation appears to be based on the direction the contour line was generated, not the slope direction.
• The "Readability" parameter, where it exists in label families, does not consistently enforce uphill orientation across all contour lines.
• Manual flipping of individual labels is the only reliable workaround — which is impractical on any site with more than a handful of contours.
• There is no global setting that enforces uphill readability project-wide.
---
HOW IT SHOULD WORK
The correct behavior would be:
1. A project-level or type-level setting — such as "Readability: Uphill" — that automatically orients every contour label so the text reads from the low side toward the high side.
2. This orientation should update dynamically if the Toposurface is modified.
3. The setting should be accessible and clearly documented, consistent across all contour label family types.
This is standard behavior in AutoCAD Civil 3D, where contour label styles include a built-in "Uphill" orientation option that works reliably across the entire surface.
---
WHY IT MATTERS
Landscape architects, civil engineers, and site planners rely on accurate topographic communication. Incorrectly oriented contour labels are not just an aesthetic issue — they can lead to misreading of site conditions, errors in grading design, and non-compliance with drawing standards required by municipalities and planning authorities.
Fixing this would significantly improve Revit's usability for site and landscape design workflows, and bring it in line with industry-standard drafting conventions.
I would appreciate this being reviewed by the development team and considered for an upcoming release.
