Map Compiler

The SISfm Map Compiler is an administrator utility which translates site and building plans from Cadcorp Spatial Information System™ SWD (SIS Workspace Definition) files into Facility maps as SVG and XML files for use by the SISfm Map Enquiry module.

Map Compiler is available:

as a desktop edition, in the SISfm Administrator installation, which requires Cadcorp SIS Desktop also installed, and a Cadcorp SIS ActiveX Manager or Modeller licence.
as a web edition, in the SISfm Administrator module, which requires access by the SISfm website to a Cadcorp GeognoSIS service using a full GeognoSIS (not GeognoSIS Express) licence.
as the Administrator module utility Compile DWG Floor Plan, a web page which uploads a DWG floor plan and runs the desktop edition on the SISfm server to compile it.
as the Administrator module utility Compile Plans, a web page which runs the desktop edition on the SISfm server to compile existing site and floor plans there.

Map Compiler reads Cadcorp SIS files at the following physical locations:

DataFolderSis\site_code\site.SWD

and:

DataFolderSis\site_code\floor_loc_code.SWD

where:

DataFolderSis is the value of that setting for this application (see below)
site_code is the site code defined by the SiteId and SiteCode settings for this application

floor_loc_code is the building floor location code

Instead of SWD files at these locations, Windows shortcut files with the same names can be used to refer to SWD files at other locations.

Use Compile DWG Floor Plans to translate building floor plan DWG files, specified by the field to the left, into corresponding SVG and XML files. See Compiling DWG Floor Plans below. The field must be as for Compile Floor Plans.

Use Compile Floor Plans to translate building floor plan SWD files, specified by the field to the left, into corresponding SVG and XML files. The field value must be a valid building floor location code, or a partial one to select all that start with that value (for legacy reasons, any asterisk (*) characters are removed from the value first).

Use Compile Site Plan to translate an SWD file for a site, selected from the dropdown selector to the left, into corresponding SVG and XML files.

Use Update Areas to update room areas (rm.area) and gross floor areas (fl.area_gross_int and fl.area_gross_ext) in the database, specified by the field to the left as for Compile Floor Plans.

Use Help in the desktop edition to view this documentation.

Batch Compilation

The desktop edition of Map Compiler can also be run non-interactively (e.g. as a Windows scheduled task) by including the following command line parameters. These are all optional and may be specified in any order. Parameter names and qualifiers are not case-sensitive, parameter values must be enclosed in double quotes if they contain spaces, names and values must be separated by one or more spaces.

/BATCH Run Map Compiler non-interactively. By default no data is compiled.

/LOGFILE filename Write the log to the specified file. If omitted, or if the specified file is invalid, the log is written to the console.

/APPEND Append entries to the log file if it already exists. If omitted the contents of an existing log file are replaced.

/DWGDATA [code[,code...]] Compile map data from DWG files, optionally restricted by one or more comma-separated codes. Each code may be a Compile Floor Plans field value.
/MAPDATA [code[,code...]] Compile map data from SWD files, optionally restricted by one or more comma-separated codes. Each code may be either a site_id value or a Compile Floor Plans field value.
/UPDATEAREAS [code[,code...]] Update room and gross floor areas, optionally restricted by one or more comma-separated codes. Each code may be a Compile Floor Plans field value.
/SINCE [SWD|DATASET] [date/time] Restrict map data compilation to files modified since a specified date/time if supplied, otherwise to the date/time that Map Compiler was last run on the same computer. The qualifier SWD or DATASET may be used to further restrict /MAPDATA compilation to only internal overlays, or to only external file overlays.

Configuration

The web edition of Map Compiler uses Cadcorp GeognoSIS stored procedures supplied in the SISfm Administrator installation as Map Compiler\GeognoSIS\SP_SISfm.dll, which must be copied to the Cadcorp GeognoSIS StoredProcedures\DotNet folder.

The web edition of Map Compiler reads its settings from the SISfm web configuration (see the Map Compiler section of Configuration Settings, and requires setting MapCompilerGeognoSIS.

The desktop edition of Map Compiler reads its settings from the file MapCompiler.exe.config in the same folder as MapCompiler.exe. Use a plain text editor such as Notepad to change settings to suit your environment.

Most Map Compiler settings should be the same for both editions, and should therefore be in a shared configuration file (see Configuration Administration) as shown in the example below.

File folder settings must be specified separately as URLs in the non-shared web configuration, and as physical paths in MapCompiler.exe.config.

The desktop edition requires the following settings in MapCompiler.exe.config:

Key		Value
`CadcorpLicenceServer`		The name or IP address of the Cadcorp licence server, or `no-net` to specify a local licence. Optional, if omitted a local licence will be used if present, otherwise the server specified in Windows environment variable `CADCORP_LICENCE_SERVER_LIST`, otherwise a server obtained by network broadcast.
`CadcorpLicenceLevel`		The level of the Cadcorp licence to use, either `Modeller` or `Manager`. Optional, if omitted a Modeller licence will be used if available, otherwise a Manager licence.
`MapDatasetFolder`		The physical path of a folder under which all map dataset files are stored, corresponding to the URL defined by the web application MapDatasetFolder setting. Optional, if both are not defined the Map Enquiry Layer download button is not displayed.

Map Compiler also reads the following settings which should normally be shared with the SISfm web application:

DbConnectionIFM
DbConnectionAFM

FacilityType

LocCodeFormat
LocCodeOutput
LocCodeOutputB

EmView
EmNameFields
EmNumberField
EmExtraKeyField

BlAreaField

SiteId
SiteCode

MapTheme
MapLegend

MapLayerAlias

MapLayerPoint
MapLayerLink
MapLayerNetwork
MapLayerTopo

Following are typical configuration files, with Map Compiler settings for the test data supplied with the SISfm web application at its default web site location:

`MapCompiler.exe.config`

<?xml version="1.0"?>
<configuration>
  <appSettings file="C:\inetpub\wwwroot\SISfm\shared.config">

    <add key="CadcorpLicenceServer"    value="" />
    <add key="CadcorpLicenceLevel"     value="Modeller" />

    <add key="DataFolderSis"           value="C:\inetpub\wwwroot\SISfm\test\sisdata\" />
    <add key="DataFolderMap"           value="C:\inetpub\wwwroot\SISfm\test\mapdata\" />
    <add key="DataFolderMapIcon"       value="C:\inetpub\wwwroot\SISfm\test\mapicons\" />

    <add key="MapDatasetFolder"        value="" />

    <add key="UploadWebsite"           value="" />
    <add key="UploadAuthTokenUrl"      value="" />
    <add key="UploadAuthClientId"      value="" />
    <add key="UploadAuthClientSecret"  value="" />
  </appSettings>
</configuration>

`app.config`

<?xml version="1.0"?>
<appSettings>
  <add key="AppConfigFile" value="shared.config" />

  <add key="DataFolderSis"             value="~/test/sisdata/" />
  <add key="DataFolderMap"             value="~/test/mapdata/" />
  <add key="DataFolderMapIcon"         value="~/test/mapicons/" />

  <add key="MapDatasetFolder"          value="" />

  <add key="MapCompilerGeognoSIS"      value="http://localhost:4601/GeognoSIS/GeognoSIS.wsdl" />
</appSettings>

`shared.config`

<?xml version="1.0"?>
<appSettings>
  <add key="NolFile1"                  value="C:\inetpub\wwwroot\SISfm\test\sisdata\test.nol" />

  <add key="DwgTemplateSwd"            value="C:\inetpub\wwwroot\SISfm\test\sisdata\DwgTemplate.swd" />
  <add key="DwgDataFolder"             value="C:\inetpub\wwwroot\SISfm\test\dwgdata\" />
  <add key="DwgDataFolderAfm"          value="C:\inetpub\wwwroot\SISfm\test\dwg_afm\" />
  <add key="DwgDataFolderAfmFlat"      value="FALSE" />
  <add key="DwgDataFolderForOverlay1"  value="" />
  <add key="DwgInsertParams"           value="" />
  <add key="DwgGrossAreaType"          value="BOTH" />
  <add key="DwgGrossAreaLayer"         value="Gross Areas" />
  <add key="DwgRoomAreaLayer"          value="Space" />
  <add key="DwgRoomNumberLayer"        value="Room Numbers" />
  <add key="DwgSaveSwd"                value="FALSE" />

  <add key="OverlayExclude"            value="route-vehicle,route-pedestrian" />
  <add key="OverlayLinks"              value="buildings,carparks,otherlinks,space" />

  <add key="ExplodeShapes"             value="TRUE" />

  <add key="ExportSVG"                 value="TRUE" />
  <add key="ExportSVGZ"                value="FALSE" />
  <add key="ExportPDF"                 value="TRUE" />
  <add key="ExportCentroids"           value="TRUE" />

  <add key="PDFPrintTemplate"          value="IFM A3 Landscape PDF" />
  <add key="PDFPaperFormat"            value="A3*@600" />

  <add key="PDFParameters"             value="" />

  <add key="ViewRotationAttribute"     value="" />

  <add key="BuildingName"              value="" />

  <add key="LinkColours"               value="" />

  <add key="LinkAttribute"             value="" />
  <add key="DescAttribute"             value="" />
  <add key="LocCodeAttribute"          value="" />

  <add key="MapFloorLayerPointParams1" value="Room Zones|db=2+tables=RoomZones,RoomZones,RoomZones,RoomZones,RoomZones,RoomZones,RoomZones,RoomZones+columns=map_name,x,y,scale,angle,icon,link,description+where=map_name='$$map_name$$'+nFieldX=1+nFieldY=2" />
  <add key="MapFloorLayerPointParams2" value="HAZMAT|db=2+tables=hazmat,hazmat,hazmat,hazmat,hazmat+columns=hazmat_id,x,y,name,notes+where=site_id='$$site_id$$' AND bl_id='$$bl_id$$' AND fl_id='$$fl_id$$'+nFieldX=1+nFieldY=2" />
</appSettings>

Cadcorp Data

Map Compiler obtains two extents from the SWD for use by Map Enquiry:

Home extent - the un-padded extent of the current map window when the SWD is saved.
Data extent - the extent of all data, regardless of overlay status and ignoring any WMS overlays.

The view rotation is ignored for a site plan SWD but is compiled as the Map Enquiry building alignment for a floor plan SWD so that floors can be viewed orthogonally, when it must be the same for all floors of a building. The view rotation is as defined by the Cadcorp SIS View / Map Views / Rotate command unless setting ViewRotationAttribute is set.

Overlays can be renamed or excluded by using MapLayerAlias settings. In the resulting names, the dot (".") character is interpreted as a folder path separator. Note that overlay names should not be the same as folder names (i.e. if there is an overlay named A.B.C there should not be overlays named A.B or A.

The last separator in a folder path may instead be a double dot ("..") to signify that such overlays are alternatives: their selection will use radio (option) buttons instead of checkbox buttons (or equivalent button styles).

LINKS OVERLAYS

Overlay names matching the values in the setting OverlayLinks are processed as containing items with links to buildings for a site plan SWD, with links to rooms for a floor plan SWD, and in both cases with optional links to other external resources.

For a links overlay, only Point, Node, LineString, Link, Polygon, MultiPoint, MultiLineString, MultiPolygon items are processed. For area items, the item origin determines the Map Enquiry label position. In a links overlay:

Building items in site SWDs have the attribute defined by the BuildingLocCodeAttribute setting containing the location code of the floor to be initially displayed. (This may optionally be a comma-separated list of floor location codes, when the first will initially be displayed; values may be followed by .swd.)
Room items in building floor SWDs have the attribute defined by the LocCodeAttribute setting containing the room location code.
Other link items must be in overlays specified by MapLayerLink settings:
- They must have a description (which may contain HTML text formatting tags) specified either in the attribute defined by the DescAttribute setting, or by an item expression stored in overlay attribute DescAttributeFormula$.
- They may have a hyperlink URI (which may alternatively take the form plan:loc_code to specify a plan to be loaded in Map Enquiry) specified either in the attribute defined by the LinkAttribute setting, or by an item expression stored in overlay attribute LinkAttributeFormula$.
- They may have other attributes, which are displayed in the Map Enquiry item dialog after the item description.
- Item colours are compiled from the colour of item brushes for area items or otherwise item pens if LinkColours is TRUE, otherwise Map Enquiry will display them according to the MapColourLink setting. If LinkColoursAreaPen is TRUE, And LinkColours Is TRUE, the pen colour is also used for area items.
- Item line thickness can be overridden using overlay attribute svgStrokeWidth#. This attribute overrides the SVGStrokeWidth setting.
- Item symbol names (_shape$) beginning with mapicons. are compiled as map icons, and corresponding icon graphics are obtained from image files under the DataFolderMapIcon folder. The symbol name may end in -gif, -jpg or -png to specify the image file type, default gif. Examples:
  
  Symbol name Icon file name
  
  mapicons.Info Info.gif
  
  mapicons.WiFi.AccessPoint-png WiFi/AccessPoint.png
- Item scale is according to overlay property _pointScaleOverride# and item property _scale#:
  - non-scalable (constant size), according to the MapIconScale setting.
  - scalable, according to the MapIconScaleFactor setting.
- Item rotation is horizontal unless the point item has attribute UseAngle$ set to TRUE, when it is item property _angleDeg$.
- Node and Link item topology is an experimental approach to network layers (the MapLayerNetwork setting provides a different approach).

OGC WMS OVERLAY

An Open Geospatial Consortium (OGC) Web Map Service (WMS) overlay can be included, e.g. to display aerial photography. Its connection details must also be specified in the MapOgcWmsUrl or MapLayerOgcWms setting.

RASTER OVERLAYS

Map Enquiry does not explicitly support raster overlays, however it is possible to implement one using a point item with a large icon.

VIEW POINTS OVERLAYS

If the overlay dataset type is View Points, and overlay attribute DbConnectionMap& exists, it is processed as a real time overlay: the View Points database details are compiled and Map Enquiry obtains its content from the database specified by the corresponding DbConnectionMap setting, or if DbConnectionMap&=0 by the DbConnectionIFM or DbConnectionAFM setting. The following optional database columns are specially interpreted:

`scale`	point icon scale: if absent, null or 0 - non-scalable (constant size), according to the `MapIconScale` setting. otherwise - scalable, according to the `MapIconScaleFactor` setting.
`angle`	point icon angle (clockwise degrees from horizontal), 0 if absent or null
`icon`	point icon file name, `Pin.gif` if absent or null
`link`	point hyperlink URI (or `plan:loc_code` as above), none if absent or null
`description`	point description, shown in point dialog by default, found by Local Search.

Table and column names may not contains spaces, but may be in any alphabetic case.

MapLayerPoint settings must be used to declare View Points overlays. These may optionally define a key column name, a description column name, and default values for other special table columns if these are undefined or do not exist.

The following additional View Points features are available:

Point feature editing is available to users according to access control defined in table sisfm_layeredit if the table has a key column, and a single View Points table is used.
If the View Points WHERE clause includes column='value' for columns map_name, site_id, bl_id, fl_id, it is set to value for inserted point features.
If it exists, column bl_id or rm_id is set according to the location of a point feature within a building or room.
Additional columns may be used, when the point feature dialog will display their values in a full dialog with the layer name as its title and column names as value labels (or as specified by MapTheme settings), otherwise in a single button dialog displaying the description.
The additional columns, plus the icon and description columns, may be specially defined for editing, using table sisfm_flds fields (in the same database as the View Points table) as follows:
- using pulldown selectors, with entries that display description and specify value when selected (if icon is not defined in this way, its editing pulldown selector will include all icons under the DataFolderMapIcon folder):
  - if enum_list is defined, it specifies a value;description;... list (as for feature fields with the enum descriptor).
  - if ref_table is defined, it specifies a validation table of value (field with same name) and description (field with sisfm_flds.sisfm_type=2055 (Desc)) fields. Only single key (dep_cols=NULL) validation is supported.
- using a barcode reader:
  - if sisfm_type=2065 (Barcode) the "pic2shop" barcode reader app is used. EAN 13 digit barcodes are supported.
MapLayerNetwork settings can be used to define networks.

Room zone layers (see MapRoomZoneLayer) must have description values commencing rm_id-zone_no if either the MapRoomZoneDialogAdvanced or the ModuleWorkstationBookings function is accessible. This is normally achieved using SQL in a MapFloorLayerPointView setting.

TOPOLOGICAL OVERLAYS

Topological overlays are used to represent utility networks on site and floor plans as directed graphs (or trees), each with a single source and multiple destinations, which may share the same network infrastructure.

MapLayerTopo settings are used to declare topological overlays, whose data is stored as Cadcorp Node, Link, TopoPoint and TopoLineString items. Each setting value (e.g. Service) specifies the first facet of a set of overlays; such as:

Service.Pit - infrastructure Node items
Service.Trench - infrastructure Link items

Service.Light.Lamp - light network TopoPoint items
Service.Light.Circuit - light network TopoLineString items

Service.Power.Outlet - (example of another network using this infrastructure)
Service.Power.Line

These overlays filter these items from the same BDS file dataset. If more than one network uses the same infrastructure, their overlays also need to filter items by the network type, for which the _layer$ property is recommended.

Map Compiler populates the database with item data including relevant topological properties, using one database table per overlay and named after it, such as:

service_pit
service_trench
service_light_lamp
service_light_circuit

Each database table has an AUTOINCREMENT field as Primary Key, named after its table (e.g. service_pit_id), and a field named id corresponding to the Item ID (_id&) property. The values of these two fields may change when topological overlays are recompiled.

Database tables for Node and TopoPoint items include the fields shape and angledeg containing _shape$ and _angleDeg# property values for their icons and their orientations, and those for Link and TopoLineString items include fields pencolour, penoffset and penpattern containing the colour, offset and pattern values of their _pen$ properties. Values for _shape$ and _pen$ take account of their overlay values and overrides. Pen offsets can be used to display coincident items. For offset and pattern scaling, see the MapPenStyleFactor setting.

All items have an attribute named after their overlay (e.g. Pit_ID$, Trench_ID$, Circuit_ID$, Lamp_ID$) which uniquely identify them and will not change when topological overlays are recompiled.

TopoLineString and TopoPoint items also have the attribute Network_ID$ which identifies the network they are a member of.

Each item class may also have any number of other user defined attributes (e.g. pit depth, lamp working status) of string ($), integer (&) or floating point (#) data types. The database tables are populated with all attributes in the overlay schema, using corresponding field names and types.

When recompiling topological overlays, item attribute values are compared with the corresponding database field values, and if they differ the attribute values are updated to the database values in the BDS file dataset (for example, a lamp's working status may have been changed in the database). This means that the master copy of user attribute values is the database, whereas the master copy of everything else is the BDS file.

Topological database tables include the fields site_id, bl_id, fl_id, rm_id which are populated to identify the plan. When recompiling a plan, all its previous data is deleted from these tables, which are then repopulated.

The field Building Code (bl_id) for site plans, and Room Code (rm_id) for floor plans, may be updated in the database to specify the building or room an item is associated with, and these values are retained when recompiling; they are not stored in the BDS file.

Topological database tables may be specified by AssetTable settings, and for this purpose the Link, TopoPoint and TopoLineString tables include the fields x and y populated with item centroids, for use by the Show on Plan functions in asset details and in Asset Manager. For asset details to include descriptions, their item class identifier fields (e.g. Pit_ID$, Lamp_ID$) are assigned the Desc type (sisfm_flds.sisfm_type=2055).

If topological database tables do not exist, or are unsuitable (e.g. because a new item attribute is present), Map Compiler logs the SQL required to create them, including their database schema entries in tables sisfm_tables and sisfm_flds. The Database Manager's SQL page can then be used to execute this SQL, after which all plans must be recompiled.

The topological database tables are used by Map Enquiry to display corresponding layers, but may also be used elsewhere, e.g. by Report Maker.

The Map Compiler setting OverlayExclude can be used to exclude any topological overlay from the compiled layers, though it is still otherwise processed.

Map Enquiry MapLayerAlias settings can also be used to exclude any of these layers, or to rename them (e.g. to avoid Feature dialog name trees).

A set of topological overlays can consist of Node and Link overlays only (with no TopoPoint or TopoLineString overlays).

Here is a summary of the database fields in each table for the example above, with corresponding Cadcorp properties and attributes:

	`service_pit`	`service_trench`	`service_light_lamp`	`service_light_circuit`
`table_id`	●	●	●	●		Primary Key `AUTOINCREMENT` field (e.g. `service_pit_id`)
`site_id`	●	●	●	●		Site ID
`bl_id`	●	●	●	●		Building ID
`fl_id`	●	●	●	●		Floor ID
`rm_id`	●	●	●	●		Room ID
`id`	●	●	●	●	`_id&`	Item ID
`x`	●	●	●	●	`_ox#`	Node Item X (or asset centroid X)
`y`	●	●	●	●	`_oy#`	Node Item Y (or asset centroid Y)
`node`			●		`_node&`	Connected Node Item ID
`links`	●			●	`_links$`	Connected Link Item IDs (negated if reversed) *
`id1`		●			`_id1&`	Link Item Start Node Item ID
`id2`		●			`_id2&`	Link Item End Node Item ID
`angle`	●		●		`_angleDeg#`	Icon angle (degrees)
`icon`	●		●		`_shape$`	Icon filename (see `DataFolderMapIcon` setting)
`pencolour`		●		●	`_pen$`	Pen colour (hex `RRGGBB`)
`penoffset`		●		●	`_pen$`	Pen offset (see `MapPenStyleFactor` setting)
`penpattern`		●		●	`_pen$`	Pen pattern (see `MapPenStyleFactor` setting)
`name_id`	●	●	●	●	`name_ID$`	i.e. `pit_id`, `trench_id`, `lamp_id`, `circuit_id`
`network_id`			●	●	`Network_ID$`	Network ID
`attribute`	●	●	●	●	`attribute& attribute$ attribute#`	User defined attributes

* Note that the first two redundant values of the _links$ property of TopoLineString items are omitted in the corresponding links field.

OTHER OVERLAYS

For all other overlays:

all items supported by Cadcorp SVG export are compiled as SVG and/or SVGZ files.
Bitmap overlays are not currently supported.
overlay attribute svgStrokeWidth# can be used to override the thickness of SVG/SVGZ lines; if present, and positive, each stroke-width style is set to its value in the SVG for that overlay. This can be used for overlays whose extents are larger than others (e.g. for roads nearby a site) when the default line thickness may be too large due to a minimum line thickness constraint in the Cadcorp SVG exporter. This attribute overrides the SVGStrokeWidth setting.
overlay attribute svgUseLevels@ can be used to honour the item _levels& property, which may increase SVG size and affect display performance.
Insert items with Block name blockname are replaced by inserts of Blocks named SISfm.name in the loaded NOL files, where blockname contains name (e.g. to simplify their graphics).

Compiling DWG Floor Plans

Compiling DWG floor flans requires the Map Compiler settings commencing with Dwg.

Use Compile DWG Floor Plans to compile floor plans from DWG files to SISfm (without requiring SWD files). The following options are available:

Compile a DWG file in DwgDataFolder to SISfm (setting DwgDataFolderAfm is not defined).
Convert a DWG file in DwgDataFolder to an Archibus DWG file in DwgDataFolderAfm and compile this to SISfm.
Compile an Archibus DWG file in DwgDataFolderAfm to SISfm (setting DwgDataFolder is not defined).

Archibus DWG files include xData for linking elements such as room numbers and polylines to Archibus, and from this xData SISfm room location codes are derived.

Options 1 and 2 create an intermediate Archibus DWG file in DXF format (at a temporary location for option 1). DXF format is used because Cadcorp cannot export MTEXT entities, so these are created by editing the exported DXF. Furthermore, Cadcorp does not provide access to the DWG entity handles, so these do not match those in the xData. Therefore option 2 currently does not work, and option 3 requires Archibus DWG files prepared using the Archibus Smart Client.

Note that Map Compiler does not publish Archibus enterprise graphics. This must be done using the Archibus DWG Editor (or AutoCAD with the corresponding Archibus plug-in).

For options 1 and 2, DWG files are processed as follows.

Gross area, room area and room number layers are renamed from those specified in DwgGrossAreaLayer, DwgRoomAreaLayer, DwgRoomNumberLayer settings to GROS$, RM$, A-ROOM-NO and their data is verified.
Layer GROS$ and layer RM$ items are converted from LineString to Polygon. If there is one GROS$ polygon then it is processed as internal, if two the one with the smaller area is processed as internal and the other as external.
Layer GROS$TXT is created containing BoxText items in Archibus format (bl_id, fl_id, Internal/External, area) and are assigned Archibus xData.
Layer GROS$ items are assigned Archibus xData.
Layer RM$ items and layer A-ROOM-NO items are matched by testing that each area contains one number.
Layer RM$TXT is created from layer A-ROOM-NO containing BoxText items in Archibus format (number, area) and are assigned Archibus xData.
Layer RM$ items are assigned Archibus xData.
In table sisfm_dwgs, fields dwg_file, base_metric_units=0 (millimeters), units=0 (metric) are updated if dwg_name exists, otherwise a new row is inserted with those fields plus zeros for the six report_* fields with a not null constraint.
In table gros, fields dwgname, layer_name='GROS$', ehandle, area are updated if bl_id,fl_id,gros_type exist, otherwise a new row is inserted with those fields plus bl_id, fl_id and gros_type='INT' (internal) or 'EXT' (external).
In table fl, fields area_gross_int and area_gross_ext (if the external gross area exists) are updated.
In table rm, fields dwgname, layer_name='RM$', ehandle, area are updated for this bl_id,fl_id,rm_id (with warnings listing unmatched values on either side).
An Archibus DWG file is created (as DXF) in DwgDataFolderAfm for option 2, at a temporary location for option 1.

For options 1 and 2 (continued) and for option 3, the SWD file specified by setting DwgTemplateSwd is loaded and:

For each overlay with a DWG or DXF file dataset, the dataset is changed to the DXF file just created by options 1 and 2, or to the DWG file in the DwgDataFolderAfm folder for option 3, and Links overlays (matching OverlayLinks) are identified.
For each Links overlay:
- Items not in layer EQ$ (e.g. in layer RM$) are converted from LineString to Polygon, and loc_code$ attributes added with values obtained from their xData.
- Items in layer EQ$ DescAttribute and LinkAttribute attributes are added with values obtained from their xData. Note that equipment linework can be difficult to select in Map Enquiry, therefore it is recommended that the svgStrokeWidth# attribute is set (say to 4) for the applicable template overlay.
Additional DWG file overlays may be added according to DwgNameRegularExpression and DwgAddOverlay settings
The resulting SWD is then compiled in the usual way, and saved if DwgSaveSwd is TRUE.

Note that the SWD file specified by setting DwgTemplateSwd should contain File overlays referencing a representative DWG or DXF file (e.g. located alongside it) with Expression layer filters such as _layer$ In ("RM$") and Not _layer$ In ("EQ$","RM$").

Messages

The following messages may be issued in a dialog box, or to the log in batch mode:

Setting MapCompilerGeognoSIS is not defined
The MapCompilerGeognoSIS setting must be defined to use the web edition.

No Cadcorp SIS ActiveX Manager or Modeller licence is available
Check that Cadcorp SIS is installed, including one of these licences, to use the desktop edition.

Unable to access page (message)
Check that the UploadWebsite settiing is correctly defined.

Cadcorp library not found: filename
Check that filename exists, or adjust NolFile configuration settings.

The following messages may be issued to the console in batch mode:

Error creating specified log file filename
File name not specified
No value was supplied for the /LOGFILE parameter.

Error creating specified log file filename
message
The value supplied for the /LOGFILE parameter is invalid.

The following messages may be issued to the log:

MapCompiler parameters
Confirms the supplied command line parameters for batch compilation.

Invalid command line arguments: arguments
Command line arguments are not those required for batch compilation.

Invalid date/time value: value
Invalid /SINCE date value for batch compilation.

Invalid last run date/time value: value
The LastRun value in the key HKEY_CURRENT_USER\Software\VB and VBA Program Settings\IFM\SISfm Map Compiler is not a date (if value is (undefined), use /SINCE with a date value, otherwise remove this value from the registry).

Compiling plan [ SWDs | DATASETs ] updated since [ last run at ] date
Confirms /SINCE action for batch compilation.

Select plan to compile
The initial log panel message, or no plan was specified.

No plans found
You have tried to compile an item or range of items which do not exist in the database.

filename.swd read
filename.dwg read
Advice that a plan compilation is starting.

ERROR: Topology overlay name name is invalid
ERROR: Topology overlays have different datasets: name1, name2,...
ERROR: Topology "topoRoot" tables invalid - valid SQL for schema and DDL is: SQL
ERROR: Topology overlay "name" item with attNamePoint="idPoint" and attNameLine="idLine" is not reached by that line
ERROR: Topology requires two overlays name.* - one filtering pointClass items, the other lineClass items
ERROR: Topology table "table" name is invalid
ERROR: Topology overlay name has duplicate itemClass items, IDs id1,id2,...
ERROR: Topology overlay name has Link items with more than two vertices, id1,id2,...
ERROR: Topology overlay name has Link items with line not straight, id1,id2,...
ERROR: Topology overlay name items do not all have attribute idAtt
ERROR: Topology overlay name items with idAtt="id" do not form a single directed network, unconnected node IDs id1,id2,...
ERROR: Topology "topoRoot" table "table" would require more than one field "field" due to an item property/attribute name clash
ERROR: Topology "topoRoot" table "table" does not exist
ERROR: Topology "topoRoot" table "table" requires field field
ERROR: Topology overlay "name" must have Editable status to update its item attribute "att" value(s)
Refer to Topological overlays above.

filename.dwg added as overlay name
A DWG file overlay has been added when compiling a DWG file.

ERROR: Compiling DWG files with DwgDataFolder defined is not supported with UploadWebsite set
Check the DwgDataFolder and UploadWebsite settings.

ERROR: DWG dataset invalid: filename.dwg
DWG compilation was unable to read this DWG file.

ERROR: no dwgname value is defined for rooms on floor loc_code
ERROR: different dwgname values are defined for rooms on floor loc_code
DWG compilation obtains the names of Archibus DWG files from the rm.dwgname field for rooms on that floor, or from fl.dwgname if the floor has no rooms.

ERROR: DWG layer setting cannot be renamed to layer because it already exists
DWG compilation found that the layer GROS$, RM$ or A-ROOM-NO already exists, when setting DwgGrossAreaLayer, DwgRoomAreaLayer or DwgRoomNumberLayer is used.

WARNING: DWG layer RM$ contains count1 Polygon items, layer A-ROOM-NO contains count2 BoxText items
DWG compilation found a mismatch between the number of room polygons and their numbers.

ERROR: DWG layer RM$TXT already exists
DWG compilation found that the layer it creates for Archibus room numbers already exists.

ERROR: DWG layer GROS$ contains count Polygon items
DWG compilation found that the gross area layer does not contain either 1 or 2 polygons.

WARNING: DWG layer GROS$TXT already exists - renamed to GROS$TXT_OLD
DWG compilation found that the layer it creates for Archibus gross area labels already exists.

WARNING: DWG layer RM$ area [ at extents ] contains count room numbers [ list ]
DWG compilation found a room polygon which does not contain 1 room number. When no room number is found, extents are provided for locating the room, otherwise a room number list.

WARNING: DWG layer RM$TXT values not in rm.rm_id: list
DWG compilation found room numbers in the DWG which do not match any value of field rm.rm_id for this floor.

WARNING: Compiling DWG files with DwgViewRotationField defined is not supported with UploadWebsite set
Check the DwgViewRotationField and UploadWebsite settings.

WARNING: rm.rm_id values not in DWG layer RM$TXT: list
DWG compilation found values of field rm.rm_id for this floor which do not match any room number in the DWG.

WARNING: Unable to get room ID from DWG xData for count rooms
DWG compilation found invalid xData values.

INVALID SWD: Link overlay index contains items other than Point, Node, LineString, Link, Polygon, MultiPoint, MultiLineString, MultiPolygon
The SWD is compiled but unexpected results may occur.

INVALID SWD: Link overlay index contains count items with attribute='value'
INVALID SWD: Link overlay index contains items with attribute values not in the database: 'value,...'
INVALID SWD: Link overlay index does not contain building 'value' that is in the database
INVALID SWD: Link overlay index does not contain rooms with attribute values that are in the database: 'value,...'
The SWD is compiled but unexpected results may occur. On a site or floor plan, a BuildingLocCodeAttribute or LocCodeAttribute value does not specify a building or room that exists in the database, or vice versa.

INVALID SWD: Link overlay index contains more than one item for building 'value'
The SWD is compiled but unexpected results may occur.

INVALID SWD: Link overlay index contains items with no description, which is required for point layers
The SWD is compiled but unexpected results may occur. A MapLayerPoint setting specifies that the overlay is to be compiled as a point layer for. The overlay DescAttributeFormula$ attribute and the DescAttribute setting are used to determine item descriptions.

ERROR: Unable to copy filename to filename (message)
Check filing system permissions.

ERROR: Unable to export to filename (message)
Check filing system permissions.

ERROR: cannot export width x height PNG: filename
Check filing system permissions. Check ExportFloor PNG scale.

ERROR: file does not exist: filepath
You have tried to compile an item which exists in the database, but its Cadcorp SWD file or Archibus DWG file is not present.

ERROR: file filename does not exist under folderpath
You have tried to compile an item which exists in the database, but a search for its Archibus DWG file has not found it.

ERROR: n files filename exist under folderpath
You have tried to compile an item which exists in the database, but a search for its Archibus DWG file has found more than one.

ERROR reading item (WriteLayerXml): message
An unexpected error occurred, consult IFM for assistance.

WARNING: Manager licence in use, and Insert items found - not exploded or simplified
A Cadcorp SIS ActiveX Modeller licence is required to process Insert items correctly.

WARNING: Manager licence in use, and Point items found - symbols not exploded
A Cadcorp SIS ActiveX Modeller licence is required to process Point items correctly.

filename created
Advice that PDF, DWG, SWD, SVG, XML and image files have been created or replaced.

Overlay building_floors..N added
Advice that for a site plan an overlay has been added for building_floors level N.

Uploading to upload_website
Advice that file uploading is commencing.

filename uploaded
Advice that a file has been uploaded.

n plan[s] generated
n file[s] generated
Summary of the plans and files generated.

Compiling building data is not supported with UploadWebsite set
Check the UploadWebsite setting.

filename created, n buildings
Summary of the building data generated while compiling a site plan.

Compiling floor data is not supported with UploadWebsite set
Check the UploadWebsite setting.

`DataFolderSis`	is the value of that setting for this application (see below)
`site_code`	is the site code defined by the `SiteId` and `SiteCode` settings for this application
`floor_loc_code`	is the building floor location code

`/BATCH`	Run Map Compiler non-interactively. By default no data is compiled.
`/LOGFILE filename`	Write the log to the specified file. If omitted, or if the specified file is invalid, the log is written to the console.
`/APPEND`	Append entries to the log file if it already exists. If omitted the contents of an existing log file are replaced.
`/DWGDATA [code[,code...]]`	Compile map data from DWG files, optionally restricted by one or more comma-separated codes. Each code may be a Compile Floor Plans field value.
`/MAPDATA [code[,code...]]`	Compile map data from SWD files, optionally restricted by one or more comma-separated codes. Each code may be either a site_id value or a Compile Floor Plans field value.
`/UPDATEAREAS [code[,code...]]`	Update room and gross floor areas, optionally restricted by one or more comma-separated codes. Each code may be a Compile Floor Plans field value.
`/SINCE [SWD\|DATASET] [date/time]`	Restrict map data compilation to files modified since a specified date/time if supplied, otherwise to the date/time that Map Compiler was last run on the same computer. The qualifier `SWD` or `DATASET` may be used to further restrict `/MAPDATA` compilation to only internal overlays, or to only external file overlays.

Symbol name	Icon file name
`mapicons.Info`	`Info.gif`
`mapicons.WiFi.AccessPoint-png`	`WiFi/AccessPoint.png`