Jon,
I couldn't agree more.
Our biggest hurdle right now in making transfers to and from other
tools is that they are not using "standard" naming conventions for
shapes. Instead, they typically provide an option to directly "map"
from their names to another tools names. However, this runs contrary
to the idea of a data exchange standard independent of each
proprietary tool.
For example, RISA-3D CIS/2 translator imports & exports shapes using
their own naming convention. To get their translator to interpret the
AISC standard names, the end user is expected to define a "mapping
file" to do so. They do provide some pre-defined mapping files direct
translation to other tools, but again, this is not true independent
data exchange.
In fact, the industry (AISC - US at least) *has* a published "shapes
database" that contains all its standard names
(EDI_Std_Nomenclature). The applications just haven't been using it.
It should be the CIS/2 translator's job to translate proprietary names
to AISC standard names, not the end user's job.
On Jun 29, 11:44 pm, Jon Mirtschin <
geometry...@googlemail.com> wrote:
> Hi Jason,
>
> Whilst I can't advise you on a work flow or mapping file, I'm
> interested in the reason behind your comment to avoid IFC and the
> aspects/behaviour that lead to that statement? I've been developing
> Rhino3d plug-ins for exchanging structural models (IFC and CIS/2,
> although the IFC has progressed further,
http://geometrygym.blogspot.com
> ).
>
> The need to use mapping tables is one of the biggest concerns I have
> for the use of the plug-ins, I really wish the industry could bite the
> bullet and mandate uniform names. Of course, both IFC and CIS/2 can
> carry section profile shapes (ie profile dimensions) within their
> model exchange, but I'm assuming either that option is unavailable or
> unacceptable for the exchange you are trying to achieve.
>
> Cheers,
>
> Jon
>
> On Jun 29, 8:46 pm, jharrisghafari <
jhar...@ghafari.com> wrote:
>
>
>
> > We have a CIS/2 export from SDS/2 7.152, and are trying to import it
> > into Bentley Structural V8i (08.11.05.38). At the import dialogue
> > window, we select the section mapping option, and no parts show up.
> > So we assume the built-in mapping file covers these. However, after
> > import we are missing 13,000+ pieces, which are primarily truss web
> > angles.
>
> > First off, does anyone know of a SDS/2 to Bentley mapping file?
> > Secondly, what other options could we use to get CIS/2 to DWG format?
> > We would really like to avoid IFC, if possible.
>
> > Thanks,
>
> > Jason- Hide quoted text -
>
> - Show quoted text -