Datagroup Catalog Editor / 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.

I support Andreas suggestion.

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

Danny,

I was actually referring to the GB dataset being created for ABD.  It's based on the emerging British Standard BS1192, so includes many changes all around.  

I believe there is a thread somewhere - either here on the ABD beta forum - where the topic of metric datasets was discussed.  From what I recall, the majority of our BA user base was and is in the US, hence Imperial is the default.  However, that doesn't mean it won't or shouldn't change to reflect a more international metric "flavor".  In fact, I wouldn't be surprised if it does... at least as an option.

Steve

'the majority of our BA user base was and is in the US, hence Imperial is the default'

I can understand that, that's in itself if fine

'I was actually referring to the GB dataset being created for ABD.  It's based on the emerging British Standard BS1192, so includes many changes all around. '

I see, ...... well let's hope they do more than just 'label' things using clauses/categories from BS1192

The previous UK datasets were based on UK standards (Uniclass of CIfsb) ...... but only in name. The actual sizes, dims and styles of the 'building components' was on the whole definitely not metric. On the whole it seemed to be just the imperial dataset, just re-badged with metric 'labels' and names.

This was (and is) a big disappointment and and very off-putting.

BS1192 does NOT give you any information about what sizes things are. It's just a protocol for naming and categorising things. One hopes they realise this and intend to provide actual 'real-world' building components that match the sizes and dims that one would expect to find in a UK context (and one assumes people in Italy, France, Norway, ...... ect would expect likewise)

Anyway, ..... thank you for your comments

Steve, if I read the Bentley annual report from last year, there clearly is no majority of users using imperial datasets. Just for the records.

On the other hand we are running into problems everywhere.

Just to give you an example about something I found out right now. Microstation is by default using seed.dwg as the seed file for export to dwg. Guess which units this file has set by default. No it's not metric.

Why isn't there any indication that this seed file is intended for imperial units only?

We can't accept that in the long run. There needs to be a fundamental different approach from Bentley to this problem.

Service Ticket number 8001304339 filed.

Steve, if I read the Bentley annual report from last year, there clearly is no majority of users using imperial datasets. Just for the records.

On the other hand we are running into problems everywhere.

Just to give you an example about something I found out right now. Microstation is by default using seed.dwg as the seed file for export to dwg. Guess which units this file has set by default. No it's not metric.

Why isn't there any indication that this seed file is intended for imperial units only?

We can't accept that in the long run. There needs to be a fundamental different approach from Bentley to this problem.

Service Ticket number 8001304339 filed.

It is really so simple.  

Bentley create several Datasets - one for each group

Place under different directories

And One variable to correctly pick the proper Dataset Directory.

And then the responsibility is the true issue.  Build the dataset - step by step - from item by item