Revit forgets path to UniformatClassifications file

[Anonymous]

I set the path to  UniformatClassifications.txt from Manage > Additional Settings > Assembly Code, close the file, open another one and Revit FORGETS.

I have to do it again, and again, and again.

It might be because I'm accessing it via a share (drive J:) instead of an URL, but there is NO WAY to put in an URL, you can only browse to a path.

But then I copied it to my local drive and STILL forgets.

I copy UniformatClassifications.txt to a libray (as set in Options) and select 'At Library locations' but it makes no difference.

I browse to default library location and it tells me it is not a at a libary location (it's not, I haven't set options to look there).

It this a joke? Does Autodesk care about standards at all?

Revit 20150511_0715

[arief.rahman · Accepted solution]

Hi,

For the file houses the Uniformat Assembly Codes, and the location is fixed; it cannot be moved or specified in a library location [i.e. on a server].  

UniformatClassifications.txt - C:\Program Files\Autodesk\<Revit Version>\Program

If you wish to edit this file in one location, it is recommended to keep a copy on a server location, and create a batch file to copy & replace the specific file on the user workstation.  This file is read once at the Revit application launch.

http://revitclinic.typepad.com/my_weblog/2010/12/10-revit-supplementary-files-and-where-they-are-loc...

Regards,

[Anonymous · Accepted solution]

If that is the case why is there a command to browse to a different location?

The Omniclass definition file OmniClassTaxonomy.txt is at a fixed location. But under Manage tab, Additional settings there is an Assembly Code tool to browse to the UniformatClassifications.txt (or UniformatClassifications_2010.txt) file.

It appears the path and filename set using this command is saved in the file, not globally. And because I am adding Assembly Codes to family files it is really really annoying.

But I can see it makes sense if you have different Assembly Code definitions for different projects. Which can happen because comparing the current default UniformatClassifications.txt with the new file UniformatClassifications_2010.txt I find there are different codes for the same thing.

And guess what? There is a new OmniClassTaxonomy.txt file as well. The OmniClassTaxonomy.txt file currently shipped with Autodesk products
(including 2016) is based on a 2006 Omniclass draft. There is a new file, it is refered to as Omniclass 2012. But it is doing the rounds on the internet with the same filename. The 2006 file is 127kb, the new 2012 one is 308kb. Oh, and the new file doesn't assign omniclass numbers to Revit categories like the old one. I've attached it for anyone interested.

And yes, the numbers are different between the two files, so if you are using the Autodesk supplied one your Omniclass numbers are wrong.

So I suppose this issue is resolved. It is just business as usual working with an AutoDesk product. 

[loboarch]

The change in Omniclass numbering is a known issue and documented here:  http://help.autodesk.com/view/RVT/2016/ENU/?guid=GUID-BA0B2713-ADA0-4E51-A7CD-85D85511F3ED

There is an issue with the formatting of the new ominclass numbering system and Revit's ability to sort the numbers by category.  A change to the underlying datastructure of Revit is needed in order to read the Omniclass text file so category sorting is possible.  So if you need the newer numbers you have to manually search the file rather than relying on sorting.  So unitl Revit is changed you either need to use the older Omniclass numbering (with category sorting) or use the newer Omniclass numbering without category sorting. 

[Anonymous]

Looking at the definition file it is just looks like the new file is missing codes for Revit categories. Mind you Revit categories are just a suggestion. Any direct correspondence is a coincidence. 

What surprises me is that AutoDesk products ship with an incorrect definition file. It is not that the new file has more in it, the numbers are actually different.

It may be a "known issue", but one easily fixed. Just ship products with a correct definition file.

[aaron_rumple]

They really should ship the current release with the current OmniClass, Uniformat, IFC and other standards.

I understand why they don't. Just plain lazy.

They would have to go into their old families and update all the parameters they set. As would all the offices around the country. These field don't update from the text file when loaded. They just keep the old, incorrect values. So faster just to ship the old stuff and let you deal with it.

What they really need is a translation table that would update old families and projects to the newer formats.

This will be an ongoing issue as BIM matures.

[megastoreonline1234]

Foam mats for floor provide cushioning and comfort, making them perfect for exercise spaces, playrooms, or areas where prolonged standing is required. They also offer insulation and sound absorption properties.

[prateekr819]

• https://microadia.net/blog/best-ice-cream-maker-machines-in-india/