Python number precision output rounded to 15 decimals instead of 3

Michael_Kirschner2 · July 22, 2021, 8:39pm

I don’t think Dynamo does any rounding -

the XYZ ToPoint method is here:

DynamoDS/DynamoRevit/blob/d8265df98b2d623d0953cfc0d984a2930cbd92fd/src/Libraries/RevitNodes/GeometryConversion/GeometryPrimitiveConverter.cs#L148


      
          {
              xyz.Enabled = true;
          
              return Autodesk.DesignScript.Geometry.BoundingBox.ByCornersCoordinateSystem(
                  xyz.Min.ToPoint(convertUnits), xyz.Max.ToPoint(convertUnits),
                  xyz.Transform.ToCoordinateSystem(convertUnits));
          }
          
          public static Autodesk.DesignScript.Geometry.Point ToPoint(this XYZ xyz, bool convertUnits = true)
          {
              var pt = Autodesk.DesignScript.Geometry.Point.ByCoordinates(xyz.X, xyz.Y, xyz.Z);
              return convertUnits ? pt.InDynamoUnits() : pt;
          }
          
          public static Autodesk.DesignScript.Geometry.Point ToProtoType(this Autodesk.Revit.DB.Point point, bool convertUnits = true)
          {
              return point.Coord.ToPoint(convertUnits);
          }
          
          public static Vector ToVector(this XYZ xyz, bool convertUnits = false)
          {

the InDynamoUnits does do a scale though depending on Revit units:

github.com

DynamoDS/DynamoRevit/blob/d8265df98b2d623d0953cfc0d984a2930cbd92fd/src/Libraries/RevitNodes/GeometryConversion/UnitConverter.cs#L50


      
          /// <param name="geometry"></param>
          /// <returns></returns>
          public static T InDynamoUnits<T>(this T geometry)
              where T : Autodesk.DesignScript.Geometry.Geometry
          {
              if (geometry == null)
              {
                  throw new ArgumentNullException("geometry");
              }
          
              var result = (T)geometry.Scale(HostToDynamoFactor(SpecTypeId.Length));
              geometry.Dispose();
              return result;
          }
          
          /// <summary>
          /// Convert from Revit Display Units to Revit API internal units (feet)
          /// 
          /// Can be used simply as geometry.InHostUnits()
          /// </summary>
          /// <typeparam name="T"></typeparam>

which as has been stated, will create noise with floating point numbers.

If you mean you see the displayed number in Dynamo’s preview as rounded - that is possible, but I don’t think that rounding has actually been applied to the point - it’s just for display AFAIK.

If you see it in Revit, then I’m not sure.

ruben.romero · July 22, 2021, 10:15pm

Springs.Number.ToString package node helped, you see the difference between what Dynamo shows and what the number it really is:

First list is what is done in Revit, second list is fixed with script.

Disgusting Revit numbers, most annoying thing I ever resolved in Dynamo.

Topic		Replies	Views
Dynamo Coordinates - Project Issue	12	3253	August 9, 2018
Getting coordinates from Project Base Point or from Survey Point? Revit	18	18745	August 15, 2018
[SOLVED] - Elements location different between node Dynamo and Python script	2	365	August 19, 2020
Spot Coordinates Error Revit revit , dynamo	3	633	May 7, 2019
Document.ProjectPosition Packages	7	1179	April 22, 2015

Python number precision output rounded to 15 decimals instead of 3

Related Topics