edmiRemoteWriteStepFile2Ex

 EdmiError   edmiRemoteWriteStepFile2Ex (SdaiServerContext       serverContextId,
                                         SdaiString              remoteModelRepositoryName,
                                         SdaiString              remoteModelName,
                                         SdaiString              remoteHeaderModelRepositoryName,
                                         SdaiString              remoteHeaderModelName,
                                         SdaiString              stepFile,
                                         SdaiString              diaFileName,
                                         SdaiString              shortNamesFile,
                                         SdaiOptions             options,
                                         SdaiInteger             realPrecision,
                                         SdaiInteger             stringEncodingCode,
                                         SdaiInteger            *nbWarnings,
                                         SdaiInteger            *nbErrors,
                                         EdmiError              *sdaiError,
                                         SdaiInvocationId       *edmiInvocationId);

Invokes the EDMp21Handler to produce a STEP Physical File representation of the population of an edmModel in the remote EDMdatabase specified by the given server context. The STEP Physical File format is defined in ISO 10303-21: Clear text encoding of the exchange structures. A STEP Physical File is also referred to as a Part 21 file. STEP Physical File is one of the implementation forms of ISO 10303, and can be used to exchange data between two EDMdatabase s or between one EDMdatabase and any ISO 10303-21 conformant application. The STEP Physical File can also be used for long-term archiving of the data. The Header Section part of the STEP Physical file can be produced from an existing header model in the EDMdatabase or a default Header Section can be produced when no header model is specified as input argument to this function. A header model is a model of the HEADER_SECTION_SCHEMA defined in ISO 10303-21. The default Header Section can be configured by setting the EDM system variable EDM_STEP_FILE_AUTHOR.

Arguments

1	Type	Name	Comment
2	SdaiServerContext	serverContextId	Context identification, from edmiDefineServerContext
3	SdaiString	remoteModelRepositoryName	The name of the edmRepository in the remote EDMdatabase that contains the edmModel. Repository names are case sensitive.
4	SdaiString	remoteModelName	The name of the edmModel. Model names are case sensitive.
5	SdaiString	remoteHeaderModelRepositoryName	The name of the edmRepository in the remote EDMdatabase that contains the STEP Header Model. Repository names are case sensitive.
6	SdaiString	remoteHeaderModelName	The name of the STEP Header Model that will be mapped to the Header Section in the resulting STEP Physical file. Model names are case sensitive. All instances in the STEP Header Model will be mapped to as is to the STEP Physical file Header Section, except for the attribute FILE_DESCRIPTION.IMPLEMENTATION_LEVEL which will be set according to the mapping method specified by one of the options CONFORMANCE_CLASS_1, CONFORMANCE_CLASS_2 and EDM_PRIVATE_FORMAT. The attribute FILE_NAME.TIME_STAMP will be set to current date and time. When the NO_HEADER_CHANGE option is set, the specified STEP header model will be mapped as is, i.e., also the attribute values described above will be mapped from the specified STEP header model to the STEP Physical file. When this argument is left blank, a default STEP Header Section is generated. The default header section can be configured by setting the EDM system variable EDM_STEP_FILE_AUTHOR.
7	SdaiString	stepFile	The name of the STEP Physical File to create on the local disk. The default file extension is .stp
8	SdaiString	diaFileName	The name of an optional file that will receive the diagnostic information resulting from the generating of the STEP Physical File. If this argument is NULL, the diagnostics will be written to the EDMinterface current output device. The EDMinterface current output device can be defined by the edmiDefineOutputFunction operation.
9	SdaiString	shortNamesFile	The name of the file containing the mapping matrix between the full entity names and their corresponding unique short names.
10	SdaiOptions	options	See list of available options below.
11	SdaiInteger	realPrecision	Denotes the number of significant digits after the decimal point for REAL numbers in the resulting STEP Physical file. When <realPrecision> is set to zero, a system dependent default value is used.
12	SdaiInteger	stringEncodingCode	The file string encoding
13	SdaiInteger	nbWarnings	Variable that will receive the number of warnings resulting from exporting the STEP Physical file.
14	SdaiInteger	nbErrors	Variable that will receive the number of errors resulting from exporting the STEP Physical file.
15	EdmiError	sdaiError	Variable that will receive any EDMinterface error code resulting from exporting the data in the STEP Physical file it self. System errors in general wil not be returned in this variable.
16	SdaiInvocationId	edmiInvocationId	Currently not used.

Return Value

Error rendering macro 'excerpt-include' : User 'null' does not have permission to view the page 'US:_r_EDMInterface'.

Options

1	Option	Comment
2	NO_STRING_ENCODING	Specifies that no encoding will take place when mapping a STRING data type to the STEP Physical file. The ISO 10303-21 specifies that all characters in a string with an ASCII value less than 32 or greater than 126 should be encoded in a STEP Physical file.
3	NO_LINE_BREAKS	The exported instances will not be separated with new-line characters in the STEP Physical file.
4	NO_HEADER_CHANGE	The header model specified by the <headerModelName> argument will be mapped to the actual STEP Physical file without any changes. Normally the mapping method, time stamp, and schema name will be provided by the EDMstepHandler function, but not when this option is set. This argument is only effective when a header model is specified in the <headerModelName> argument.
5	SHORT_NAMES	The short names specified in the <shortNamesFile> argument will be used for entity names in the resulting STEP Physical file.
6	EDM_IDENTIFIERS	Specifies that the EDMdatabase instanceID will be used as instance identifiers in the STEP Physical File. This makes it easier to find the correlation between a stepIds in the STEP Physical file and their corresponding instanceIds in the EDMdatabase.
7	CONFORMANCE_CLASS_1	The STEP Physical file will be exported according to ISO 10303-21:1994/TC1 CC1. The mapping format will be written to the header section of the STEP file. CONFORMANCE_CLASS_1 is the default mapping method. The options CONFORMANCE_CLASS_1, CONFORMANCE_CLASS_2, and EDM_PRIVATE_FORMAT are mutually exclusive.
8	UTF8_ENCODED_FILE_NAMES	Can use UTF8 string encoding in file names
9	ONE_FILE_STEP_FILE_PACKAGE
10	NUMBER_OF_SUBTYPE_INSTANCES_STATISTICS
11	STEP_FILE_PACKAGE
12	NO_COMMENT_SECTION
13	IFC_VIEWER_INSTANCES
14	AGGREGATE_IN_SDAIERROR_ARG
15	ONLY_USER_DEFINED_ENTITIES
16	ORDER_BY_INSTANCE_TYPE
17	FORMAT_STEP_FILE
18	EDM_IDENTIFIERS
19	USE_MODEL_STRING_ENCODING
20	EXCLUDE_USER_DEFINED_ENTITIES
21	NUMBER_OF_INSTANCES_STATISTICS
22	HEADER_MODEL_ONLY
23	CONFORMANCE_CLASS_2
24	ZIPPED_FILE
25	KEPT_STEP_IDENTIFIERS

EDMsix

edmiRemoteWriteStepFile2Ex

Arguments

Return Value

Options

Example

See also

Filter by label