Database Linkages
The following parameters define the methods for making Database Linkages. See
Database Linkages for the description of how this
works.
Handle Based
| PARAMETER |
HANDLE BASED |
| Purpose |
This parameter specifies that Handle Based Database Linkages are to be created. The Room Layer (-RL) parameter must be used to define the Room Polygons and the Text Layer (-TL) parameter must NOT be used. If TL is defined then an error is output and nothing happens. |
| Example |
-HB |
| JSON |
{“HandleBased”:""}
{“HB” : true} |
| Alias |
-HB |
| Use |
With SVG Only |
Room Layer
| PARAMETER |
ROOM LAYER |
| Purpose |
This parameter specifies the “Room Layer” for either Automated Area Linkage or Handle Based Database Linkages to be created. While it is called “Room” layer, it is actually any layer where closed polygons are used to define areas to be used for database linkages. For Automated Area Linkage the Text Layer (-TL) parameter is used to define the layer to search for Room/Area Names. The Handle Based (-HB) parameter must NOT be used. For Handle Based Database Linkages the Handle Based (-HB) parameter must be used to specify the mode and the Text Layer (-TL) parameter must NOT be used. If TL is defined then an error is output and nothing happens. |
| Example |
-RL=RM$ |
| JSON |
{“RoomLayer”: [“RM$”, “OFFICE”]}
This is in the “Layers” section of the JSON file, not the “General” portion |
| Alias |
-RL |
| Use |
With SVG Only |
Text Layer
| PARAMETER |
TEXT LAYER |
| Purpose |
This parameter specifies the “Text Layer” for Automated Area Linkage to be created. It is used to define the layer to search for Room/Area Names For Automated Area Linkage the Room Layer (-RL) parameter must be used to define the layers to search for room outlines. The Handle Based (-HB) parameter must NOT be used. Text Layer must NOT be used for Handle Based Database Linkages. If HB and TL are both defined then an error is output and nothing happens. |
| Example |
-TL=RM$TXT |
| JSON |
{“TextLayer”: [“RM$TXT”, “OFFICE_NAME”]}
This is in the “Layers” section of the JSON file, not the “General” portion |
| Alias |
-TL |
| Use |
With SVG Only |
Attribute Key
| PARAMETER |
AttributeKey |
| Purpose |
This parameter specifies an Attribute for processing similar to Automated Area Linkage. It is used to define the Blocks to be processed into clickable areas. Any Block Instance that has the listed Attribute Key will be processed just like if the Block Name was used. Since the Blocks do not have an outline like Rooms would, the extents of the block instance are used as the clickable area. If BNA is used, then the value of that tag is used for the ID of the clickable area. If BNA is not used, then the Block Reference Handle is used. This can be used in conjunction with RL/TL processing. You can separate multiple block names with a semicolon (";"). |
| Example |
-ATTRIBUTEKEY=“Codice;Pano” |
| Alias |
-AK |
| JSON |
{“BlockName”: [“BlockOne”, “BlockTwo”]}
This is in the “General” section of the JSON file, not the “Layers” portion like RL/TL |
| Use |
With SVG Only |
Block Name
| PARAMETER |
BlockName |
| Purpose |
This parameter specifies the “Block Name” for processing similar to Automated Area Linkage. It is used to define the Blocks to be processed into clickable areas. Since the Blocks do not have an outline like Rooms would, the extents of the block instance are used as the clickable area. If BNA is used, then the value of that tag is used for the ID of the clickable area. If BNA is not used, then the Block Reference Handle is used. This can be used in conjunction with RL/TL processing. You can separate multiple block names with a semicolon (";"). |
| Example |
-BLOCKNAME=“BlockOne;BlockTwo” |
| JSON |
{“BlockName”: [“BlockOne”, “BlockTwo”]}
This is in the “General” section of the JSON file, not the “Layers” portion like RL/TL |
| Use |
With SVG Only |
Block Name Layer
| PARAMETER |
BlockNameLAYER |
| Purpose |
This parameter specifies the layer(s) to search for BlockNames. All non-anonymous blocks on that layer(s) are added to the Block Name list and treated just like they had been listed on the BLOCKNAME parameter. You can separate multiple layer names with a semicolon (";"). |
| Example |
-BLOCKNAMELAYER=“LayerOne;LayerTwo” |
| JSON |
{“BlockNameLayer”: [“LayerOne”, “LayerTwo”]}
This is in the “General” section of the JSON file, not the “Layers” portion like RL/TL |
| Alias |
-BNL |
| Use |
With SVG Only |
Ignore Attributes
| PARAMETER |
IGNOREATTRIBUTES |
| Purpose |
This parameter controls whether AutoCAD Attributes are output or not. With IgnoreAttributes on, then Attributes are not exported to the SVG file. If output, the Attributes will follow the Block Instance definition in the SVG file. |
| Example |
-IgnoreAttributes |
| JSON |
{“InvisibleAttributes”, true} |
| Use |
SVG |
Invisible Attributes
| PARAMETER |
INVISIBLEATTRIBUTES |
| Purpose |
This parameter controls whether AutoCAD Attributes that are not displayed are output or not. With InvisibleAttributes on, then the non-displayed Attributes are exported to the SVG file, but in such a way that the table is defined but not displayed. The Attributes will follow the Block Instance definition in the SVG file. |
| Example |
-IA |
| JSON |
{“InvisibleAttributes”, true} |
| Alias |
-IA |
| Use |
SVG |
Blank Attributes
| PARAMETER |
BLANKATTRIBUTES |
| Purpose |
This parameter allows the definition of blank attributes (attributes that have no text) in the SVG file. Normally blank attributes are suppressed, but since attributes can be overwritten using CADViewer, maintaining blank attributes allows those attributes to be updated on-the-fly. |
| Example |
-BATTR |
| JSON |
{“BlankAttributes”, true} |
| Alias |
-BATTR |
|
-BA |
| Use |
SVG |
Block Name Attribute
| PARAMETER |
Block Name Attribute |
| Purpose |
This parameter specifies the “Block Name Attribute” for processing of Block Names. The Block Name Attribute is used as the ID of the areas create by Block Name processing. If the Block Name Attribute is not defined or not found, then the Block Reference Handle is used instead. |
| Example |
-BNA=“SOME_ATTRIB” |
| JSON |
{“BNA”: “SOME_ATTRIB”}
This is in the “General” section of the JSON file, not the “Layers” portion like RL/TL |
| Use |
With SVG Only |
Text Layer Attribute Tag
| PARAMETER |
TEXT LAYER ATTRIBUTE TAG |
| Purpose |
This parameter specifies a block Attribute Tag on the “Text Layer” for Automated Area Linkage to be created. The layer to search for Room/Area Names For Automated Area Linkage the Room Layer (-RL) parameter must be used to define the layers to search for room outlines. The Text Layer (-TL) must additionally be defined. This parameter automatically calculates the outline area (_LA). |
| Example |
-TLTAG=ROOMNUMBER |
| JSON |
{“AttributeName”: “RoomNumber”} |
| Alias |
-TAG |
| Use |
With SVG Only |
Attribute Tag
| PARAMETER |
TEXT LAYER ATTRIBUTE TAG |
| Purpose |
This parameter specifies a block Attribute Tag on the “Text Layer” for Automated Area Linkage to be created. The layer to search for Room/Area Names For Automated Area Linkage the Room Layer (-RL) parameter must be used to define the layers to search for room outlines. The Text Layer (-TL) must additionally be defined. This parameter automatically calculates the outline area (_LA). |
| Example |
-TAG=ROOMNUMBER |
| JSON |
{“AttributeName”: “RoomNumber”} |
|
{“Tag”: “RoomNumber”} |
| Alias |
-TLTAG |
| Use |
With SVG Only |
Layer Area
| PARAMETER |
Layer Area |
| Purpose |
When running the (-TL/-RL) process, the parameter (-LA) will additionally calculate the area of each space, based on the given units information provided in the source DWG file. |
| Example |
-LA |
| JSON |
{“ListArea” : true } |
| Alias |
-LA |
| Use |
With SVG Only |
Text Layer Postfix
| PARAMETER |
TEXT LAYER POSTFIX |
| Purpose |
When running the (-TL/-RL) process and the ID calculation counters dublicates, the generation process will create an unique duplicate ID based on the original ID. This new ID can be controlled through -TLPOSTFIX. If you use “%DCNT” in the Postfix string it will be replaced with the duplicate count. |
| Example |
-TLPOSTFIX=“mypostfix” , -TLPOSTFIX="-xx-%DCNT" |
| JSON |
{“TLPOSTFIX” : “mypostfix”} |
| Use |
With SVG Only |
Ignore Blocks
| PARAMETER |
Ignore Blocks |
| Purpose |
Because AutoCAD Blocks tend to be placed on the special layer, 0, decluttering by simply turning layers off is not always sufficient. The Ignore Blocks (IB, BO, IGNORE_BLOCK[S]) parameter allows you to turn off processing of individual types of blocks. Block Names are separated by a semi-colon. |
| Example |
-IB=“WOODEN” , -IB=“WOODEN;CEMENT;HEAD” |
| JSON |
{“IgnoreBlocks”: “WOODEN;CEMENT;HEAD”} |
| Alias |
-IGNORE_BLOCK[S], -BO |
| Use |
With DWG/DXF Input Only |
No Hyperlinks
| PARAMETER |
NOHYPERLINKS |
| Purpose |
Will cause Hyperlink processing not to be performed, so the resulting SVG will not have DWG Hyperlinks in it. |
| Example |
-NOHYPER |
| JSON |
{“NOHYPERLINKS”} |
| Alias |
-NOHYPER, -NO_HYPERLINKS |
| Use |
With SVG Output Only |
|
Last updated on 30 Dec 2023
Published on 9 Jun 2020
