Graphic Technologies, Inc.

FRAMME FEATURE DEFINITIONS OVERVIEW

TAKEN FROM INTERGRAPHS FRAMME DATA STRUCTURES REFERENCE GUIDE AND ON-LINE HELP

2729 Deford Mill Road Owens Crossroads, Al, 35763 Tel: (205) 533-3466 Fax: (205) 533-3422 email: gti@traveller.com Page 1

Graphic Technologies, Inc.

SECTION I. FRAMME DATA MODEL REQUIREMENTS

he FRAMME AM/FM/GIS system provides functionality for continuos mapping, Work Order Processing, Transaction Processing, feature level editing and locking, automatic connectivity maintenance and tracing, and etc. To provide these and other functions, the FRAMME system uses a sophisticated data model and rulebase which must be adhered to during the data conversion process. A good working knowledge of FRAMME data structures must be acquired before embarking upon a FRAMME data conversion project. This section will provide an overview on the FRAMME Data Structures and will point out major requirements which must be noted during data conversion activities.

Data Delivery
Master File Delivery - FRAMME data can be delivered in Master File Format, ready for installation on the master data server.

Pros Transaction records are NOT needed. Data posting is not required, therefore delivery is quicker. Cons Reference Records ARE needed. Linear elements must be broken at map sheet boundaries. No posting of facilities to check the data integrity, therefore other QA/QC
methods and/or processing are necessary. Workset Delivery - FRAMME data can be delivered in Workset Format, ready for posting to the master data server.

Pros Reference Records are NOT needed. Linear elements need NOT be broken at map sheet boundaries. No other QA/QC methods and/or processing are necessary. Cons Transaction records are needed! Data posting is required, therefore delivery is slower.

Page 2

Graphic Technologies, Inc.

FRAMME Feature Definition
Example Facilities
In the following example, the facility, a pole, consists of three components: A graphic symbol A graphic text (attribute) record A nongraphic record in the database which describes the pole.
Graphic Annotation 4. POLE __ __ .11 .12 __ __ .23 __ __ .31 .32 __ __ IPID ACCT CODE TYPE HEIGHT CLASS

P-772 30/5

Graphic Symbol Non-graphic Database Record

Page 3

Graphic Technologies, Inc.

In the next example, the facility, a cable, consists of six components: A linear graphic element Two non-graphic records in the database which describe the cable A repeating graphic symbol Two graphic text records.

Graphic Text Record Repeating Graphic Symbol

300 mcm XLPE

Repeating Graphic Symbol

Linear Graphic Element

Circuit 4D11
Graphic Text Record

5. REF_CABLE

Non-graphic Database Record

6. CABLE

Page 4

Graphic Technologies, Inc.

FRAMME Feature Tags (Non-graphic and Graphic)
Non-graphic Feature Tag FRAMME places a feature tag on each facility component in the non-graphic database. The FSC component option specifies that the database table contains a set of attributes referred to as the FRAMME tag, which is to be automatically maintained by FRAMME. This option is for non-graphic components only, and is recommended for all non-graphic components. The FSC option causes FRAMME to use the database component table to maintain information on the facility. This information is required only for those components which are accessed from the non-graphic side of the model. For example, if you would like to search the RDBMS for a particular value, and then read the facility associated with that row, the table (component) must have the /FSC qualifier specified. The RB_FSC attribute requires 8 bytes. It must be defined in the *.rdl file using the following format:
.n .n+1 .n+2 .n+3 .n+4 RB_FSC RB_STATE RB_COMPONENT RB_VERSION RB_OCCURRENCE F=I(32767) F=I(32767) F=I(127) F=I(127) F=I(32767) ; Feature Number ; State Number ; Component Number ; Version Number ; Occurrence Number

The attribute names and data formats cannot be changed. In addition, the following attributes are generally used as a part of each non-graphic component main record:
6. CABLE .100 RB_PRMRY .101 RB_SCNDRY .102 MSLINK .103 RB_LOCK .104 RB_FSC .105 RB_STATE .106 RB_COMPONENT .107 RB_VERSION .108 RB_OCCURRENCE F=I(2147483647) ; Graphic (*.dgn) Identifier (GID) F=I(2147483647) ; Unique Feature Identifier (UFID) F=I(2147483647) ; Microstation Link (not used by FRAMME) F=I(32767) ; Edit Lock Bit F=I(32767) ; Feature Number F=I(32767) ; State Number F=I(127) ; Component Number F=I(127) ; Version Number F=I(32767) ; Occurrence Number

Additional components used for a non-graphic component reference record: (See splitable linear)
5. REF_CABLE .100 RB_PRMRY .101 RB_SCNDRY .102 MSLINK .103 RB_LOCK .104 RB_FSC .105 RB_STATE .106 RB_COMPONENT .107 RB_VERSION .108 RB_OCCURRENCE .109 RB_REFPRMRY .110 RB_REFSCNDRY F=I(2147483647) ; Graphic (*.dgn) Identifier (GID) F=I(2147483647) ; Unique Feature Identifier (UFID) F=I(2147483647) ; Microstation Link (not used by FRAMME) F=I(32767) ; Edit Lock Bit F=I(32767) ; Feature Number F=I(32767) ; State Number F=I(127) ; Component Number F=I(127) ; Version Number F=I(32767) ; Occurrence Number F=I(2147483647) ; Reference Graphic (*.dgn) Identifier (GID) F=I(2147483647) ; Reference Unique Feature Identifier (UFID) Page 5

Graphic Technologies, Inc.

Graphic Feature Tag FRAMME places a feature tag on each facility component in the graphics database. The following figure shows the format for the graphic feature tag. The graphic feature tag uniquely describes each occurrence of a facility in a design file, and includes a unique feature identifier (UFI or UFID) number. This number is maintained by FRAMME. FRAMME maintains the link between the graphic and the non-graphic data through two columns in the relational database tables: The RB_PRMRY column (attribute), which identifies the design file by its graphic identifier (GID). The RB_SCNDRY column, which provides the unique feature identifier (UFID).

The following illustration shows formats for graphic feature tags.

Graphic Feature Tag

U(USER) (BYTE) (ID) 32 7 (BYTE) (WORD)

UNIQUE FEATURE IDENTIFIER (2 WORDS) FEATURE NUMBER STATE NUMBER RULEBASE VERSION NUMBER (BYTE) (WORD) (WORD) COMPONENT NUMBER (BYTE) (WORD)

COMPONENT COUNT

Page 6

Graphic Technologies, Inc.

Graphic Feature Tag Example The following is an example MicroStation EDG display used to review the tag on a FRAMME element. $ edg workorder.dgn EDG> set disp/full EDG> 172 172 (7) TEXT NODE Level = 20 Words to follow = 44 Block=59 Word=103 byte=29900 IGDS format wtf = 41 Range: low = -8670, -8651, -2147483647 high = -7627, -5882, 2147483647 Graphic group: 0 Properties: nohole snappable planar noview_ind attributes nolocked nonew_element modified Class = Primary Symbology: color: 45, weight: 1, style: 0 words in description = 63 number of elements = 1 Node number = 22 font = 0, justification = LT Length and Height multipliers: 28000, 28000 rotation = 105.000 Origin: -7871, -8630 User Data Linkage 1007 20 F 0 1A 1 2 0 EDG> exit

Page 7

Graphic Technologies, Inc.

In the above example, a text node in one facility is under review. The MicroStation EDG display is divided as shown below: User Data Linkage 1007 20 F 1A 1 2
2 bytes Microstation info

0 0
2 bytes Rulebase Identifier rulebase creation: -identifier=n 2 bytes State number 2 bytes Low end of RB_SCNDRY 2 bytes High end of RB_SCNDRY

2 bytes Feature number

2 bytes Component number

2 bytes Component occurrence

For the displayed output, the MicroStation information is 1007. The rulebase identifier is 0x20 (32 decimal). The RB_SCNDRY value is 0x0F (15 decimal). The feature number is 0x1A (26 decimal), the state is 1, the component number is 2, and the occurrence is 0.

Page 8

Graphic Technologies, Inc.

The Index (or Geoindex)
The index is a design file which contains a set of polygons or shapes. Each shape is defined and created by a feature definition and function in the rulebase. There must be at least one non-graphic component associated with the shape and there can be text as well. There is only one index per segment in the model. Each shape represents a geographic (or detail) area in the model. Each shape is also associated with a particular class of data. Two design files (shapes) can represent the same physical area, but they will contain different types of data. This is accomplished through FRAMME class definitions (a class is a categorization of similar or related facilities in the FRAMME model). Each shape then implicitly represents an actual master design file. In these design files, FRAMME stores and manages the actual facility data. Only basic placement and edit of local data can be tested in a FRAMME environment without an index. If we remember that we cannot create or review any master data until we have an index (because it tells us which files are available for review), this limitation is completely logical. Index Creation 1. The application developer must first create a feature definition which contains at least a graphic shape component and a database record. The record MUST use the design file table as specified during the rulebase creation. 2. Next, the developer must create a placement function for the facility. He must also create a function for posting the new facilities. This function can be used later for regular facility data. 3. The functions must be executed to create the shapes and then the post operation performed. FRS, during the posting process, will create the master design files associated with each index shape. The developer, during FRS installation, must create the appropriate seed design files for the successful creation of the master graphic files. 4. The index is now prepared for placing and posting regular facility data. Note: We have not considered sizes of the index shapes, layout, position in the design plane, etc. All these items should be considered prior to creating the shapes. These considerations are too numerous to discuss here, but one basic item should be addressed: - No two shapes of the same class can overlap. Index and Virtual Display Virtual Display uses the index to know which master design files to attach based on the current view or screen display. The shapes which are found in the index in the current view range are queried to find their associated design files. Those files are subsequently displayed to the user.

Page 9

Graphic Technologies, Inc.

Index Shapes
Facilities
F-24-D-15 F-24-D-16 F-24-D-17

L-24-D-15

L-24-D-16

L-24-D-17

Land

Page 10

Graphic Technologies, Inc.

Splittable Linear Features

Table: 6. CABLE

Main Database Record Table: 5. REF_CABLE

RB_PRMRY = 1 RB_SCNDRY = 1

Reference Record

RB_PRMRY = 1 RB_SCNDRY = 1 RB_REFPRMRY = 1 RB_REFSCNDRY = 1

Reference Record

RB_PRMRY = 2 RB_SCNDRY = 1 RB_REFPRMRY = 1 RB_REFSCNDRY = 1

Reference Record

RB_PRMRY = 3 RB_SCNDRY = 1 RB_REFPRMRY = 1 RB_REFSCNDRY = 1

300 mcm XLPE

Circuit 4D11

MAP A

MAP B

MAP C

Page 11