PDA

View Full Version : imperial cr*p



xiqx
2011-03-04, 03:09 PM
I guess this is what you get when 'underwater' the system works with imperial units

All walls were modelled 4000mm heigh and when you export this to sql you get this.....


UnconnectedHeight
4000
4000
4000
4000
4000,00000000023
4000,00000000023
4000,00000000023
4000,00000000023
4000,00000000023
4000,00000000023
4000,00000000023
4000,00000000023
4000,00000000023
4000,00000000023
4000,00000000023
4000,00000000023
4000,00000000023
4000,00000000023
4000,00000000023
4000,00000000023
4000,00000000023
4000,00000000023
4000,00000000023
4000,00000000023
4000
4000
4000
4000

DoTheBIM
2011-03-04, 07:04 PM
That doesn't make sense, although I've seen similar things.... When I export an imperial project to ODBC it puts it in Meter units then becuase the fields are truncated to 6 places or something like that...when we do a conversion back to feet, the results will be off by a few decimals of a foot. 4000,00000000023 doesn't even work out to a "nice" imperial number.

xiqx
2011-03-05, 11:57 AM
The strangest thing is the inconsistency.

They are all the same in Revit but when exported they are different.

I suppose Autocad works internally a bit better.

Although I can't say for sure you still wouldn't get weird export numbers if Revit were to deal to deal the same with units as Autocad does.

DoTheBIM
2011-03-07, 04:08 PM
agree on the inconsistency, but can be explained by users moving things by typing in dimensions rather than snapping, or aligning to things that were moved that way. or many other user habits that can't be broken to provide consistency. I have a user that always moved things in microstation by taking a measurement via a measure tool, then moving it the resulting amount, well everything is rounded to sixteenths, so there are lots of things that ended up not right on the mark if he'd of employed snapping techniques that have been available since the age of dinosaurs. Made for some real fun when trying figure our why something didn't measure up to what it was supposed to. I fixed his butt in Revit by changing the measure tool to measure to the 1/256". He still to this day measures then moves, but at least now it won't be as far off. of course dimensions are rounded to the 1/16" so I've seen him use a dimension, then move, then delete the dimension. I think most of the problem lies in that the potential snap points don't lie on the start and end points of the move, so in his mind he as no snap points even though he does if he'd use his measurement points. *shrugs shoulders* Can't teach and old dog new tricks I guess.