<!DOCTYPE html
  PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<!--
Copyright (c) 2006 UGS Corp.

All Rights Reserved.

This software and related documentation are proprietary to UGS Corp.
-->
<html>
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <title>Overview</title>
      <script language="javaScript">
        abridged="false";
        displayConditions=new Array();
      </script>
      <link type="text/css" href="../css/main_styles.css" rel="stylesheet">
   </head>
   <body class="bodydocs" onload="top.pageLoader()" bgcolor="#FFFFFF">
      <div class="title_topic3" id="xps10_pagetitle">Overview</div>
      <hr noshade="true">
      <table cellspacing="4" align="center">
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Overview</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('dataexchange/iges_advanced.html');return(false);">Options</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('dataexchange/how_do.html');return(false);">Related Topics</a></p>
            </td>
         </tr>
      </table><br><p class="para_topic">The IGES user interface will look for the settings file iges.def in the local directory. If the system finds the settings file, its contents will be used as the initial settings of the user interface options. &nbsp;If no local file is found, then the settings file provided with the installation &ndash; UGII_BASE_DIR\iges\iges.def &ndash; will be used. We distribute this file user interface options set to the most appropriate values.</p>
      <div class="title_division">Object types</div>
      <p class="para_division">You use the object types to limit the types of data you import from the IGES file. If you know the contents of the file, you might be able to eliminate unwanted or unnecessary construction geometry or drawing information during the import by filtering unwanted data types.</p>
      <p class="para_division"><b class="uiTerm">All Object Types</b> select by default.
      </p>
      <div class="title_division">Map subfigure</div>
      <p class="para_division">Sub-figures are IGES constructs that represent geometry that repeats within a model. Most systems use the Sub-figure construct to pass assembly and component structure within an IGES file. By selecting this option, each sub-figure creates as an NX component within an assembly. The system bases the name of the component on the name of sub-figure, although some systems do not name their sub-figures. If you don't map sub-figures to components, the geometry creates at each location where the sub-figure is located.</p>
      <p class="para_division"><b class="uiTerm">Mapping Subfigures to Component</b> is the default.
      </p>
      <div class="title_division">Layer default for level 0</div>
      <p class="para_division">IGES uses the term Level for what are Layers in NX. However, IGES levels start a 0. You can specify any NX layer to hold the Level 0 information.</p>
      <p class="para_division">The default is to map level 1 to NX layer .</p>
      <div class="title_division">Specify Levels to Import</div>
      <p class="para_division">IGES supports up to 99999 levels (layers). You can use this range to limit the Levels to import into NX. Levels import into the corresponding NX layers. However for Levels greater than 256 map to NX layer on a cyclic basis &ndash; Level 257 is added to NX Layer 1, Level 258 to Layer 2, and so on until all of the Levels are accommodated in an NX Layer.</p>
      <p class="para_division">The default range of 0-99999 will ensure all Levels are imported.</p>
   </body>
</html>