Documents may be imported from object channel (POINT) and document channel (CONISIO), using the same FI2002 format.
In TDXM, two generic types of documents are distinguished:
Navigation (background) documents. They are delivered from POINT import as background for geometry information about spaces’ objects delivered with POINT import and presented in HyperDoc in Object Overlay vector drawing as clickable spots linked to database objects. In target database, this type of document is mapped to special type of document (FI2Dokument in RFS domain).
Other application documents. They are delivered from CONISIO import independently. Specific classes of these documents are mapped to specific types of documents defined in target database (A, K, SRÖ, WS, Mark, El, Foton, Dl, Övrigt in RFS domain).
In FI2002 domain, there are several FI2DOKUMENT and FI2DOKUMENTVERSION fields that may be passed together with imported data. Some of them are of special interest and are handled separately:
FI2002
FI2DOKUMENT
FI2DOKUMENTVERSION
FI2DokumentID. This field identifies document’s identity.
FI2DokumentID
FI2DokumentKlass. This field identifies document class.
FI2DokumentKlass
FI2DokumentversionKallfil. This field identifies name of drawing file described in document data.
FI2DokumentversionKallfil
FI2DokumentVersionUpprattaddatum. This field identifies date of document version.
FI2DokumentVersionUpprattaddatum
In POINT import, the FI2DokumentKlass field is missed and value of FI2DokumentID field is dummy. In this case, TDXM fills FI2DokumentKlass field as FI2Dokument, and FI2DokumentID field with special ID constructed so as to identify uniquely navigation document basing on location of its owner in hierarchy tree.
FI2Dokument
In CONISIO import, the FI2DokumentID and FI2DokumentKlass fields are assumed to be non-empty and valid. If somebody wants to deliver – via CONISIO import – updated or missed background drawings referenced from POINT import, it is necessary to leave the FI2DokumentKlass field empty.
The FI2DokumentversionKallfil field defines the name of the drawing file that is to be delivered separately and placed somewhere on known path. Since original drawing files referenced from POINT import are of DWG type that is not usable in HyperDoc environment due to performance reasons, alternative rasterized files with the same name and TIF, CAL or GIF extension are assumed to be reasonable substitutes for original drawings, if delivered.
The FI2DokumentVersionUpprattaddatum field serves as base for version comparison during import. In HyperDoc RFS domain, it is mapped to DOCUMENT_ADD3 field that is common to all document types.
The class/type-dependent mapping of other FI2002 FI2DOKUMENT and FI2DOKUMENTVERSION fields to HyperDoc DocAttr fields is neither defined nor implemented so far.
FI2002 FI2DOKUMENT
HyperDoc DocAttr
In TDXM Pipeline Process, TDXMMiscNode performs searching for physical drawing files delivered separately.
Rasterized files are searched on alternative path for drawing files, if file with original name passed in FI2DokumentversionKallfil field cannot be found. Please remember that FI2DokumentversionKallfil should be valid file name (with extension). The original FI2DokumentversionSokvag field is not used in this context.
FI2DokumentversionSokvag
To declare alternative path for drawing files, set value of DrwPath attribute in <Drawings> element of <Config> section for <Node> with Assembly="TDXMMiscNode".
DrwPath
Drawings
Config
Node
TDXMMiscNode
In TDXM Pipeline Process, TDXMMiscNode performs optional replacing of DWG physical drawings by their rasterized version, if delivered.
Rasterized files are searched on alternative path for drawing files, if file with original name passed in FI2DokumentversionKallfil field cannot be found.
The set of supposed extensions for rasterized files is hard-coded and consist of TIF, CAL and GIF files. There are no configurable aspects in this context.
TIF
CAL
GIF
In TDXM Pipeline Process, TDXMMiscNode performs optional substituting missed drawing files by empty raster background. This substitution is allowed only for POINT import, where spaces and spots should not be disregarded. In CONISIO import, documents without physical drawings are rejected obligatory.
Template to be used instead of missed background drawings should be prepared as raster GIF file, placed together with its TAF parameter file in appropriate path.
To declare template for missed drawing files, set value of EmptyFileName attribute in <Drawings> element of <Config> section for <Node> with Assembly="TDXMMiscNode". The EmptyFileName attribute should point to existing pair of GIF-TAF files, but with no explicit extension.
EmptyFileName
GIF-TAF
If the EmptyFileName attribute is missed, imported documents with absent drawing files are rejected (together with all geometry spots that are linked to them).
In TDXM Pipeline Process, TDXMInputNode transforms from FI2002 format to HyperDoc format in FI2002 domain, passing all FI2DOKUMENT and FI2DOKUMENTVERSION fields. Then TDXMDomainsNode is responsible for conversion from FI2002 domain to target RFS domain.
The only document field handled so far in import data is FI2DokumentVersionUpprattaddatum field, mapped to DOCUMENT_ADD3 field common to all document types in RFS domain.
DOCUMENT_ADD3
Rules for class/type-dependent mapping of other FI2002 FI2DOKUMENT and FI2DOKUMENTVERSION attributes to HyperDoc DocAttr attributes have to be defined. Code for honoring this kind of mapping is being currently implemented.
In TDXM Pipeline Process, TDXMMatchNode matches imported documents against documents found in HyperDoc database, after matching database objects (floors) they are connected to.
If the referenced objects match, matching documents is performed basing on ID attribute for LogDoc element.
If there are no objects that match with objects referenced from imported documents, then two cases are considered.
With import from POINT containing objects definitions, new objects are imported (building, floor and spaces), together with document that is linked to floor.
With import from CONISIO containing only object references, new objects are not added to HyperDoc database. Instead, documents are imported as disconnected ones. To connect them to objects that can be imported later, manual intervention is required.
In TDXM Pipeline Process, TDXMMatchNode decides if imported documents are worth to be considered for update in target database.
After finding matching document, date comparison may be performed.
In POINT import, background drawings are imported regardless of their date. This is so because we assume that background drawings are associated with spots and spaces being imported and we cannot import spaces with geometries, rejecting accompanying background document in the same time. Currently there are no tools implemented for comparing and matching geometries of individual spaces – expressed in spots’ shapes – between import and database content.
In CONISIO import, the value of DOCUMENT_ADD3 attribute is used to compare versions of imported documents against documents from HyperDoc database that match.
If the date of import is older than or equal to that from HyperDoc, then the imported documents are rejected. Otherwise, new document version is created in HyperDoc.
There are no user interface elements in Input Node UI to control imported document fields.
There are no user interface elements in Miscellaneous Node UI to control drawing search path, substituting missed drawings by their rasterized version or by empty background.
In Document Attributes window, values of imported document fields are presented against those matched from HyperDoc database, if any.
Currently there is no possibility to edit imported document fields.
If imported document has been rejected due to date comparison during batch process, nothing is presented in Document Attributes window.
Otherwise, user can reject importing document manually by choosing Ignore button in Document Actions pane.
If imported document cannot be rejected because it has accompanying spots, the Import – Ignore buttons are disabled.
