Generate Display pages automatically from with symbols or map markers positioned at the coordinates of your GIS or CAD files — GeoJSON, Shapefile, KML/KMZ, DXF, DWGfeatures.
Reference → Solution → Designer → Settings and Tools → Import Tags → GIS/CAD Display
| Info |
|---|
New in 10.1.5 (draft). Page is a work-in-progress preview. Screenshots and final wording will land before the 10.1.5 release. |
The GIS/CAD Display Generator creates Display pages with symbols positioned at coordinates derived from GIS or CAD feature data. Unlike the tag importers, this wizard does not create tags or device points — it creates visual displays with symbols bound to tag names you have already imported (or will import separately).
Typical use: you have imported 400 solar inverters as tags using the GIS File Tag Importer, and now want a single-page overview display showing each inverter at its geographic location on the plant layout.
Access: Solution → Import Tags → GIS/CAD Display
reads the same file formats as the GIS File and AutoCAD File Tag Importers and produces FrameworX Display pages whose elements are placed at the coordinates of each feature. Use it to build an overview screen of a solar plant, a pipeline-network map, or a P&ID-derived schematic without manual placement.
The wizard has two output modes. Canvas mode draws symbols on a canvas using a relative coordinate projection. Map mode generates a full-page map with a marker per feature. The mode is auto-selected from the input file type and is editable in Step 2.
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Accepts every format supported by the two companion tag importers:
GIS: GeoJSON (Format | Extensions | Default Mode |
|---|---|---|
GeoJSON |
.geojson, .json |
Map | |
Esri Shapefile | .shp, .zip |
Map | |
KML / KMZ |
.kml, .kmz |
See GIS File Tag Importer and AutoCAD File Tag Importer for format-specific details on how features and attributes are extracted.
Map | ||
AutoCAD DXF | .dxf | Canvas |
AutoCAD DWG | .dwg | Canvas |
The wizard auto-detects the mode from the extension in Step 2 and keeps the auto-default until you change the Display Mode combo. After an explicit choice, the wizard remembers the choice across Back and Next.
Draws a Canvas-type Display page with one symbol per feature. Coordinates are projected to page pixels using a relative bounding box so the symbols fit the page regardless of input units. Best for small to medium datasets (up to a few thousand features), for CAD drawings, and for layouts where absolute geographic accuracy is not required (tank farms, building floor plans, one-line diagrams).
Canvas mode supports per-layer symbol overrides, page width and height, margin, engine choice (Portable, WPF, HTML5), and Group By Layer to produce one page per layer.
Draws a single-element Display page containing a full-page TMapsOSM control and generates code-behind that calls AddMarker per feature on display open. Markers are bound to @Tag.<markerName>, so tooltip and runtime data flow through the tag system. Best for GIS input where geographic context matters.
Map mode uses the OpenStreetMap basemap by default. The view zooms to the bounding box of all markers on first open. Each display holds up to 10,000 markers. Larger datasets are truncated to the first 10,000 with the remainder counted as skipped.
Open Solution → Import Tags → GIS/CAD Display. The wizard has three steps.
Click Start. The wizard routes to the Canvas pipeline or the Map pipeline based on the mode. Progress shows current display, features consumed, symbols placed (Canvas) or markers placed (Map), and features skipped. Display writes are serialised on the UI thread.
Option | Mode | Description | Default |
|---|---|---|---|
Display Mode | Both | Canvas or Map. Auto-default from file type. | Map for GIS, Canvas for CAD |
Display Name Pattern | Both | Pattern used for each generated display page |
Browse for a GIS or CAD file. The wizard auto-detects the format and shows feature count, layer list, and attribute list.
| Field | Purpose | Default | |||
|---|---|---|---|---|---|
Display Name Pattern | Template for generated display page names. Tokens: {Layer}, {FileName}, {FeatureType}. | {Layer} | |||
Tag Name Pattern | Both | Pattern bound to the symbol label (Canvas) or the marker data tag (Map). Same token syntax as the tag importers. | {Name} | ||
Group By Layer | Both | When checkedon, generates one display page per layer. When unchecked, all features land on a single display. | Checked | On | |
Included Layers | Both | Whitelist of layer names. Empty list means all layers. | (empty) | ||
Symbol | Canvas | Default symbol library path for every feature. | Default Symbol | Symbol library path used for every feature, e.g., HMI/Pumps/PumpSymbol | (required) |
Per-layer Symbol Layer Overrides | Canvas | Layer-to-symbol mapping grid. Overrides the default for listed Assign different symbols to specific layers. | (noneempty) | ||
Symbol Width / Height | Canvas | Pixel dimensions for size of each placed symbol on the canvas. | 40 x / 40 | ||
Page Width / Height / Margin | Display page dimensions in pixels | 1920 x 1080, 40 px margin | |||
Engine | Rendering engine: Portable, WPF, or HTML5 | Portable | |||
Tag Name Pattern | Template for the tag name each symbol binds to (uses the same token syntax as the GIS/CAD Tag Importers) |
| |||
Label Property | Property on the symbol to which the tag name is bound | Tag | |||
Included Layers | Whitelist filter; empty = include all layers | (all) |
Progress bar with counters for displays created and symbols placed. Features without valid coordinates, or features on layers with no symbol assigned, are skipped with a log entry.
For GIS inputs (lat/lon): the wizard computes a bounding box from all imported features, then projects each feature's latitude/longitude onto the canvas so the full extent fits inside the page margins. Latitude is inverted (higher latitude = smaller Y) so north appears up on the display.
Canvas | Dimensions of each generated display page. | 1920 / 1080 / 40 | |
Engine | Canvas | Display engine used for the created pages. | Portable |
Label Property | Canvas | Symbol property bound to the resolved tag name. | Tag |
Marker Color | Map | Marker color applied to every generated marker. | green |
Map Provider | Map | Basemap tile provider. OpenStreetMap. | OpenStreetMap |
Features are projected to canvas pixels by a relative bounding-box transform. The top-left of the used area is the northwest corner of the bounding box, shifted in by the Margin. Latitude is inverted so higher latitudes sit higher on the page. If every feature shares the same coordinates, the range collapses and the wizard substitutes a minimum of 0.01 so the single symbol lands at the page centre.
Markers are added with map.AddMarker(lat, lon, name, color, shape, "@Tag." + name) on the OnDisplayOpening event. Marker data is embedded in the generated code-behind as a compact comma-separated block and parsed at runtime. The view runs ZoomToCoordinates on first open so the initial viewport fits all markers.
Coordinates must be WGS84 latitude and longitude. Non-WGS84 input is placed at the raw numeric location, which produces incorrect positions on the basemap. CAD inputs are not supported in Map mode in 10.1.5.
Produce a Map-mode display from a GeoJSON file and verify it at runtime.
For CAD inputs (raw X/Y): the same bounding-box projection applies. Drawing units are preserved as relative positions.
When all features share the same coordinates (zero-area bounding box), a fallback range ensures the symbol still renders visibly at the canvas centre.
A KML file with four Folder layers (Intake, Treatment, Chemicals, Output), each containing Placemarks for process equipment. With Group By Layer checked, the wizard produces four Display pages — one per process area.
Display Name Pattern |
|
Group By Layer | Checked |
Default Symbol | HMI/Generic/StatusIndicator |
Per-layer Overrides | Intake to HMI/Pumps/PumpSymbol; Treatment to HMI/Tanks/TankSymbol |
Tag Name Pattern |
|
Engine | Portable |
Result: four new display pages in the Displays list, each with symbols positioned by latitude/longitude and bound to the corresponding tag names.
| Page Tree | ||
|---|---|---|
|