Index Areas in MultiNet® Shapefile / OSL

See Index Areas in this user guide for a general description of Index Areas. An Index Area is stored as a simple area feature in the product. The capturing on the database level is composed either out of an Index Area Component (Simple Area Feature) or by one or more other area features (Complex Area Feature).

In the case of a complex feature, the components can be any of the following area types: Index Areas are stored as polygons in the oa6 table (Other Named Areas - Index Areas). All Index Orders are stored in one table. The oa6 table has the Official Name, Alternative Name and Index Order as attributes.
Example: A partial listing of the fields in the OA6 table:
ID FEATTYP NAME INDORDER
22826160054351 9200 Central Park 9
22826160165082 9200 Chadderton 8
22826160054365 9200 Chaigley 9
In MultiNet® Shapefile and OSL formats, the following Relationships are used to build and associate indexes:
RELATIONSHIP SHAPEFILE TABLE
Place Within Place pp
Administrative Area Replaced by Index Area ai
Road Element in Named Area ta
Ferry Connection in Named Area ta
Address Area Boundary Element ta
Address Area Boundary Element in Named Area ta
Service in Named Area sa
Built-up Area in Named Area ba
Center Point of Feature Belonging to Feature sa

Place Within Place Relationship for Index Areas in Shapefile

In Shapefile, the Place Within Place Relationship is present between Administrative Places and Administrative Areas, and between Index Areas of different hierarchy levels.

Example: All fields in the pp table:
ID FEATTYP PLYTYP PLID BELPLTYP BELPLID
10560100002001 2400 9200 10561600000036 9200 10561600000031
10560100002002 2400 9200 10561600000040 9200 10561600000031
10560100002003 2400 9200 10561600000042 9200 10561600000031
10560100002004 2400 9200 10561600000037 9200 10561600000031
In the above example, the place type Index Area (PLTYP=9200) with its identifier PLID belongs to another Index Area (BELTYP=9200) with its identifier BELPLID. The Place within Place Class is 3 = "address significant."

Administrative Area Replaced by Index Area in Shapefile

The Shapefile ai table stores all Area identifiers of a certain Area feature type that can be replaced by an Area of a different Area feature type. This can be Administrative Area replaced by Index Area or Index Area replaced by Index Area.

For the "Area replaced by Index Area" Relationship where it concerns an Administrative Area in the AREID field, the INAREID and ARETYP are not filled in. Also, if an Order 8 Administrative Area has multiple Index Areas that cover its surface, there is no possibility to choose one of those Index Areas as the second part of the "Area Replaced by Index Area" Relationship. The relationship only indicates that the Order 8 Administrative Area can be left out of the Index.

Example: All fields in the ai table:
AREID FEATTYP INAREID ARETYP
258261650045630 1120    
258261630006667 1118    
258261630087456 1119