Datagroup Catalog Editor / units - Building Analysis and Design Forum - Building Analysis and Design - Be Communities by Bentley

Datagroup Catalog Editor / units

Building Analysis and Design

Building Analysis and Design
This is where you can find and contribute to discussions, ideas, and other information about Bentley Building Analysis and Design products.
Building Analysis and Design Forum

Datagroup Catalog Editor / units

  • Picture0001.png

    Why does the datagroup catalog editor show those strange units?

  • Andreas,

    I tried this my end , but I'm seeing proper units while creating a new catalog Item/ Type.

    Can you please check by creating a new Destination file ? , since units setting gets enabled when you create a new destination file .

    Guess you might be using some existing destination file ...

    Thanks,

    Sandeep

  • I do use an exisiting destination file - "NODE_Structural.xml".

    The screenshot below shows both the dialogue box for a new item, and the start of the destination file.

  • Andreas, does the element place using imperial units?  The reason I ask is that the units in the New Catalog Item dialog are grayed out, so perhaps it's not actually reading those values.   Even when I create a new catalog item written to a new XML file, witth mm/mm chosen at the units, going back and adding a new catalog item to that file (or any other).

      

  • Sorry, I didn't catch that.

    What do you mean with "the element place using imperial units"?

  • For example, if you place it with a width of "1000", does it actually measure 1000mm?

      

  • Yes, it does.

    Regardless of which xml file I choose, it always shows ft/in. Needless to say we don't use that units in either of the xml files.

  • So it is placing/measuring correctly, it's just when setting up a new file that the grayed out ft/in always makes an appearance, regardless of the source or destination files?

      

  • Setting up a new file allows me to choose whichever units I like, so I'd use mm.

    It's just greyed out when defining a new item in an existing file that the units are greyed out and show US-units.

  • Gotcha...     Honestly, I'm not sure why that is.   It suppose it doesn't have any negative effect other than the disconcerting appearance of ft/in (though grayed out) in a metric file.

      

  • Steve

    'It suppose it doesn't have any negative effect other than the disconcerting appearance of ft/in (though grayed out) in a metric file. '

    Indeed it is 'disconcerting' ...... though fortunately in the case presented by Andreas, it's perhaps not too big a problem. I assume you're using a metric dataset Andreas.

    I'd like to chip in there then ...... this is symptomatic of the problems with the Dataset/Datagroup Catalogue for U use at any rate. I've used about 4 or 5 version of the so-called UK metric dataset. Problem is much of it is basically just an imperial Dataset. You get 25.4 mm and all sorts of other sizes that are essentially imperial sizes that have just had the labels changed to metric. This really isn't on. This product (BA) several times now as a 'ready for production use' product, with a 'metric' dataset, which basically is NOT a metric Dataset at all. Sorry guys but this is simply unacceptable. First ever time maybe it was an oversight, but repeatedly ,,,,..... that's just plain negligent and sloppy.

    Try demonstrating this 'great new software' to your boss, and things keep popping up that are basically not the standard/expected sizes for general architectural use. Your boss will not be interested in wasting much more of his/her time on this 'demonstration' for much longer.

    It's very disappointing that Bentley/BA Team are not picking up on these relatively 'low hanging fruit/easy wins' type things.

    In relation to other discussions re other so-called BIM software, we need to get people over the first 2 or 3 hurdles quickly and easily, to get them 'up and running' so to speak with regards from moving on from 2D drafting to modelling>analysis>production information.

    Anyway ....(Andreas, apologies for jumping in ...... but really, come on Bentley, please, if we have selected metric, ..... could we actually get 'real-world' metric ....... please!)

    Regards

    Danny Cooley

    Freelance CAD/Architectural Technician & Low Carbon Consultant

    Microstation SS2, BA SS1 (+update), Windows 7 Pro, 64 bit, quad core 3Ghz, 8Gb RAM, ATI 6870 1Gb, ect,

  • Hi Danny...  point taken.  

    I've never been all that involved with the regional datasets much myself, primarily because most of the users I've worked with were here in the US.  However, AFAIK there is a concerted effort to bring the metric datasets into ABD in more organized and complete fashion.    If you have the opportunity, it might be worthwhile checking out the current Uniclass dataset to see how it fares in comparison.

      

  • Steve

    No problem .....

    From what I can tell the latest UK Uniclass Dataset on the Bentley web site is dated the 02 June 2009 (from about 2 and a half years ago). I already have that one .... which sadly is littered with the issues I've mentioned

    .......2 and a half years (actually a few more as the previous Datasets were similarly not appropriate) is way too long to be having to fiddle around 'fixing' your Dataset

    This information is not something that is obscure. Bentley could easily find this out by having some discussion with the various professional institutions and professional bodies ......

    This was one of the main reasons my interest in BA dropped off.

    Thanks anyway

    Regards

    Danny Cooley

    Freelance CAD/Architectural Technician & Low Carbon Consultant

    Microstation SS2, BA SS1 (+update), Windows 7 Pro, 64 bit, quad core 3Ghz, 8Gb RAM, ATI 6870 1Gb, ect,

  • Here's that déjà vu feeling again.

    And here are my proposals...again. 

    • Bentley should use a metric dataset by default, especially for its beta programs. After all its a metric world, not an imperial. Localized versions with imperial units for Burma, Liberia and the USA can be done afterwards.

    • Bentley should publish its dataset under the GPL or LGPL. By default the dataset will be incomplete. If we are expected to fix it / contribute to it, we must legally be able to do that.

    • Bentley is free to provide manuals or courses for changing datasets. However I do very much doubt that we are willing to pay for that.
  • I support Andreas suggestion.

    A big ISO-only button at installation would be fine.