Import Model

Imports a STEP Physical File into EDMdatabase. The imported data set will be stored in a new data model, i.e., it cannot be stored in an existing model. The Header Section of the STEP file can optionally be stored in a STEP Header Model in the EDMdatabase. A STEP Header Model is a population of the HEADER_SECTION_SCHEMA defined in ISO 10303-21 and it exists always as a dictionary model in EDMdatabase.
The Express schema that defines the structure in the Data Section of the actual STEP file must exist as a dictionary model in EDMdatabase before this command can be successfully executed. The name of this Express schema is found in the attribute FILE_SCHEMA.SCHEMA_IDENTIFIERS in the Header Section of the STEP file. See Schemata>DefineSchema for how to make a dictionary model in EDMdatabase.
The STEP Physical File format is defined in to ISO 10303-21: Clear text encoding of the exchange structures. A STEP Physical File is also referred to as a Part 21 file.
This is one of the implementation forms of ISO 10303, and can be used to exchange data between two EDMdatabases or between the EDMdatabase and any application that conforms to ISO 10303-21. The produced file can also be used for long time archiving of data.
When the option [keep STEP identifiers] is enabled, a STEP Identifier model is created and connected to the data model created by this operation. The purpose of this STEP Identifiers model is to hold the correspondence between the entity instance identifiers on the actual STEP file (stepID) and the related instanceID in the EDMdatabase. The STEP Identifiers model will be opened for read only access when the related data model is opened, and the STEP Identifiers model will be deleted when the connecting data model is deleted. The STEP Identifiers model can also be handled as an individual model.
The command Data>ShowStepIdentifier can be used to display the stepID of an instanceID and vice versa when the actual data model has a connected STEP Identifier model.
A STEP Physical File can be created by any application compliant to ISO 10303-21 or by the EDMsupervisor using the Data>ExportModel command.
For information on the format of the file in argument <short names file>, see Short names in the User Guide.
Arguments:

Repository:	Specify the name of the repository that should hold the new created model(s). Repository names are case sensitive. When activating the Select button, all open repositories will be displayed in the related selection list.
Model:	Specify the name of the model to be created and populated. The model must have a name that is unique within the repository that holds the model, i.e., model names must be unique within a repository. The model name must start with a letter and the rest of the model name can be any mix of alphanumeric characters and the underscore character. Model names are case sensitive. When activating the Select button, the name of all open models located in the repository(ies) specified by the <Repository> argument will be displayed in the related selection list.
STEP Header Model:	Specify the name of the model to be created and populated. The model must have a name that is unique within the repository that holds the model, i.e., model names must be unique within a repository. The model name must start with a letter and the rest of the model name can be any mix of alphanumeric characters and the underscore character. Model names are case sensitive. When activating the Select button, the name of all STEP header models in the repository specified by the <Repository> argument will be displayed in the related selection list.
STEP file:	Specify the name of the STEP file to import. The default file extension is ".stp". When activating the Select button, a window is opened to allow browsing the directory structure and specify the desired file.
Log file:	Specify the name of a file that will contain a log of the imported file. The log will be a copy of the specified STEP file with a line sequence number added the start of each line. In addition all warnings and errors detected during the import process will be written to the place in the log file where the warning and/or error condition occurred. An empty argument means that no log file is created. This argument is only effective when the [log to file] option is set. When activating the Select button, a window is opened to allow browsing the directory structure and specify the desired file.
Schema:	The name of the Express schema that defines the structure of the data in the Data Section of the actual STEP file is found in the attribute FILE_SCHEMA.SCEMA_IDENTIFIERS in the Header Section of the STEP file. This schema will be used as the underlying schema of the new data model resulting from this command, hence this Express schema must exist as a dictionary model in the EDMdatabase. If for one reason or another this schema exists with another name in EDMdatabase, this argument can be used to overrule the schema name found in the Header Section of the STEP file, else this argument should be blank. To overrule the Express schema name found in the Header Section of the STEP file, specify the name of an Express schema that will be used as the underlying schema of the new data model resulting from this command. The name of an Express schema is case insensitive. The specified Express schema must exist a dictionary model in EDMdatabase. When activating the Select button, the name of all Express schemata that exist as a dictionary model in EDMdatabase will be displayed in the related selection list.
Short names file:	Specify the name of the file containing the mapping matrix between full entity names and its unique short name. For each STEP AP, a short name file is provided by ISO TC184/SC4 and can be downloaded from http://www.steptools.com/short_names/index.html When activating the Select button, a window is opened to allow browsing the directory structure and select the desired file.

Options:

accumulating command output:	A global option that appends the command output to the EDMsupervisor output window. Otherwise the output window is refreshed and only the last command output is displayed.
match selected input:	A global option that specifies that only items that partly or exactly matches the string in the related argument input field when activating a Select button, will be in the selection list. An empty (blank) string will match all items. This option has no effect on file name arguments.
header model only	Specifies that only the Header Section of the specified STEP file will be parsed and a STEP Header Model will be created and populated in EDMdatabase. No data model will be created when this option is set.
parse only:	The specified STEP file will be parsed only, i.e. only checked for syntactical correctness, no data will be stored in the EDMdatabase.
pre parse file:	This option may increase performance for STEP files with many forward references.
keep STEP identifiers:	A STEP Identifier model will be created and connected to the data model created by this operation. The STEP Identifier model will keep the correspondence between the STEP file entity instances and the EDM instanceID. The command Data>ShowStepIdentifier can be used to display the stepID corresponding to an EDM instanceID and vice versa. The EDMmodelChecker can optionally output the stepID of failing instances on the validation report.
no string encoding:	Specifies that the actual STEP file has no encoding of STRING data values, hence no decoding will take place during the import operation. The ISO 10303-21 specifies that all characters in a STRING data type that have an ASCII value less than 32 or greater than 126 should be encoded in a STEP file and hence decoded when importing the STEP file into an EDMdatabase.
conformance class 1:	Overrules the mapping method given in the Header Section of the actual STEP file such that the STEP file will be interpret according to ISO 10303-21:1994/TC1 CC1. The options [conformance class 1], [conformance class 2] and [DIS version] are mutually exclusive, i.e., only one of this options should be activated in one execution of the Data>ImportModel command.
conformance class 2:	Overrules the mapping method given in the Header Section of the actual STEP file such that the STEP file will be interpret according to ISO 10303-21:1994/TC1 CC2. The options [conformance class 1], [conformance class 2] and [DIS version] are mutually exclusive, i.e., only one of this options should be activated in one execution of the Data>ImportModel command.
DIS version:	Overrules the mapping method given in the Header Section of the actual STEP file such that the STEP file will be interpret according to ISO 10303-21:1994/TC1 DIS version. The options [conformance class 1], [conformance class 2] and [DIS version] are mutually exclusive, i.e., only one of this options should be activated in one execution of the Data>ImportModel command.
deleting existing model	Delete model with given name before operation, if it already exists.
add to existing model	The created instances will be added to the specified model, if it already exists.
user controlled inverse:	To safeguard consistency inverse attributes are set/updated implicitly by EDM, and users are prohibited from modifying such attributes. When this option is enabled, control of inverse attributes is left to the user/application. This option is only effective when a new model is created during the import operation.
unpacked model:	Setting this option enables the model to operate in fragmented form – i.e. de-allocated space is not recovered. This setting may enable improved performance to the cost of more disc space usage. If this option is not set, the de-allocated space of the actual model will be recovered. This option is only effective when a new model is created during the import operation.
no instance references:	No "instance references tables" will be created and maintained in the actual model. The built in function USEDIN will not work correctly on such models. This option is only effective when a new model is created during the import operation.
delete instances with refs:	Setting this option will permit instances in the actual model to be deleted even though the instances are referenced by other instances, i.e., one or more other instances have one or more relations to the actual instance to be deleted. Instances that are referred to by any other instances cannot be deleted before all the references are deleted except when this option is set. So-called "dangling pointers" is one of the results of deleting instances that are referenced by other instances. This option is only effective when a new model is created during the import operation.
delete instance refs on delete:	The delete instance operation on instances in the actual model will be legal for instances with references. The references to the actual instances will automatically be deleted when the actual instance is deleted. This option is only effective when a new model is created during the import operation.
log errors and warnings only:	Limits the log to only include logging of instances related to errors and warnings.
log to file:	Logged information will be stored in a file specified by the <Log file> argument.
log to stdout	Logged information will be displayed in EDMsupervisor output window.