PROBLEM

Create and use a property_map for VANILLA option (ARCIGDS)

Last Published: April 25, 2020

Solution or Workaround

Description

When using the property map option of ARCIGDS, the values specified in the property map are ignored. The item in the coverage's .aat, which specifies what level a line is to be placed, is not being used. All lines go to level 1.

Cause

The items that contain the property map values are not defined correctly in the feature attribute table; thus, the values are ignored and the default IGDS-ITEM value is used. For IGDS-LEVEL the default is level 1.

Solution

Create and use a property_map for the VANILLA option in ARCIGDS.

The following are the default values for all items in a property_map.

LEVEL  1
GGNO 1
CLASS 1
PROPS 00000100
COLOR 0
STYLE 0
WEIGHT 0
TEXT

As stated in the arc documentation for ARCIGDS, all of the items in the property_map INFO file, must be defined as 42 42 C. For example:

Code:
ENTER COMMAND >DEFINE PROP_MAP
ITEM NAME, WIDTH [,OUTPUT WIDTH], TYPE [,DECIMAL PLACES] [,PROT.LEVEL]
1
ITEM NAME>FEATURE
ITEM WIDTH>42
ITEM OUTPUT WIDTH>42
ITEM TYPE>C
5
ITEM NAME>LEVEL
ITEM WIDTH>42
ITEM OUTPUT WIDTH>42
ITEM TYPE>C
.
.
.

All of the items listed in the ARCIGDS command reference, under 'vanilla and property_map options,' must be added to the property map.

If the arcs of a coverage are to be placed at different levels, create an item in the arc attribute table or in a coverage.acode INFO file. That item must be declared the same as the IGDS items found in the coverage.acode file created by IGDSARC, for the corresponding feature. The name of the item does not matter, only the definition.

The items definitions are as follows, and can also be found in the IGDSARC command reference under 'the ACODE file':

IGDS-LEVEL  2 2 I
IGDS-GGNO 5 5 I
IGDS-CLASS 1 1 I
IGDS-PROPS 8 8 C
IGDS-COLOR 3 3 I
IGDS-STYLE 1 1 I
IGDS-WEIGHT 2 2 I
IGDS-TEXT 12 12 C

In the following example, two IGDS items called level and color, are used to define values for a property map in the arc attribute table rds.aat. For example:

COLUMN   ITEM NAME        WIDTH OUTPUT  TYPE N.DEC  ALTERNATE NAME    
INDEXED?
1 FNODE# 4 5 B - -
5 TNODE# 4 5 B - -
9 LPOLY# 4 5 B - -
13 RPOLY# 4 5 B - -
17 LENGTH 8 18 F 5 -
25 RDS# 4 5 B - -
29 RDS-ID 4 5 B - -
187 ZIP 5 5 I - -
219 C_STAT 1 1 C - CS -
220 LEVEL 2 2 I - -
222 COLOR 3 3 I - -

1
FNODE# = 5
TNODE# = 8
LPOLY# = 2
RPOLY# = 2
LENGTH = 1.48429
RDS# = 1
RDS-ID = 5490
ZIP = 22170
LEVEL = 6
COLOR = 24
2
FNODE# = 6
TNODE# = 9
LPOLY# = 2
RPOLY# = 2
LENGTH = 1.49667
RDS# = 2
RDS-ID = 5491
ZIP = 22170
LEVEL = 6
COLOR = 24

These two items may then be specified in the property_map for the level and color IGDS-items. The feature class will be N-ARC, because the arcs are to be converted to linestrings.

The next example is of the property map itself. One record is for the N-ARC features of the coverage, which refers to the arcs. The other record is for annotation, which will have default IGDS-item values, except for text. Items can be created in the text attribute table of the subclass in the same manner outlined above. Here an item called 'NAME', exists in the TATsubclass, and it is defined as 12 12 C. Only the text from the item 'NAME' will be placed in the output design file. For example:

PROP_MAP

1
FEATURE =N-ARC
LEVEL =LEVEL
GGNO =
CLASS =
PROPS =
COLOR =COLOR
STYLE =
WEIGHT =
TEXT =

2
FEATURE =ANNO
LEVEL =
GGNO =
CLASS =
PROPS =
COLOR =
STYLE =
WEIGHT =
TEXT =NAME

In order to use the property map, the usage of the ARCIGDS must be correct. To use the example property map on a coverage with arcs and annotation, the following command is used. For example:

Code:
Arc: ARCIGDS test test.dgn complex vanilla meter.dgn # # prop_map featues n-arc anno ~

Arc: elements linestring text

This will result in a design file with linestrings on level 6, with a color of 24, and annotation on level 1.

Note:
Refer to 'the ACODE file' section in the IGDSARC command reference for possible values of all property map items.


Note:
In 7.0.3, it is impossible to specify the level of annotation in the property map, as it always goes to level 1. This was corrected in 7.0.4.

Article ID:000001371

Software:
  • Legacy Products

Get help from ArcGIS experts

Contact technical support

Download the Esri Support App

Go to download options

Discover more on this topic