Bringing GIS data into CAD is often the point where planning context becomes design context. In BricsCAD Pro and above, SHP, GML and KML files can be imported as usable CAD geometry, giving engineers, planners and technicians a practical way to work with boundaries, networks, environmental constraints and site context inside a DWG-based workflow. The GISIMPORT command sits within the Land Surveying toolset and is available in BricsCAD Pro, Mechanical, BIM and Ultimate. It is not available in BricsCAD Lite.
The key is not simply getting the file to appear on screen, but importing it with the right coordinate system, layers, elevations and attribute data so it lines up with the rest of the project.
For UK planning and civil engineering work, this matters. A planning boundary, utility route or protected environmental layer that lands in the wrong place can create confusion, rework and risk. A controlled import process helps turn GIS data in CAD into something reliable, readable and useful.
You import SHP into BricsCAD by using the native GISIMPORT command, selecting the source GIS file, reviewing the coordinate reference system, choosing which layers or feature classes to bring in, and deciding how geometry, elevation and attribute information should be handled. The same general workflow can also apply to GML BricsCAD and KML BricsCAD imports, although the structure of the source data may differ.
A good import starts before the dialog box opens. Check what the file represents, where it came from, what coordinate system it uses, and whether the dataset includes attributes that should be preserved. If you are importing UK planning GIS data, for example, you may be dealing with local authority boundary layers, topographic datasets, flood zones, tree preservation orders, listed building constraints, public rights of way, utilities, or environmental designations. Each may arrive with different levels of detail, different licensing terms and different assumptions about coordinates.
A typical workflow looks like this:
This workflow is simple enough for routine use, but the accuracy depends on the decisions made along the way. The import command brings the data in; the user ensures it lands correctly and remains meaningful.
A coordinate reference system, often shortened to CRS, defines how real-world locations are represented as coordinates. GIS datasets are not just collections of points and lines. They are points and lines measured within a spatial framework. If BricsCAD interprets that framework incorrectly, the imported geometry can appear shifted, rotated, scaled, mirrored, or placed far away from the drawing area.
In UK contexts, this is especially important because many planning and civil datasets are supplied in national or local coordinate systems, while other files may use global latitude and longitude. A KML file, for example, is commonly associated with earth-based mapping workflows, while a DWG used for civil design may be set up in a projected coordinate system suitable for measured engineering work. If those systems are not reconciled, the visual result may look plausible at first glance but fail when checked against survey, topographic or statutory data.
When importing GIS data, pay attention to two coordinate systems:
If both are known, BricsCAD can transform the imported data so it aligns with the drawing. This reprojection step is what allows data prepared in one spatial reference to appear correctly in another. If either CRS is missing, incorrectly assigned or assumed without checking, the transformation may fail or produce a misleading result. If the system you need is simply not in the picker, BricsCAD lets you install the extended CSMAP coordinate system catalogue. For V26 and later, download the Version 1500 archive from Bricsys and copy its contents into C:\ProgramData\Bricsys inside a folder named CoordinateSystemFiles.1500, then restart. The GEOCSMAPPRIORITY system variable decides which engine wins, and it defaults to Off, meaning the internal engine is preferred with CSMAP as the fallback.
Common alignment problems include:
A practical habit is to import a small, recognisable dataset first and compare it with a trusted reference. For example, import a planning boundary and check it against known road edges, parcel lines or topographic detail. If the layer does not align, resolve the coordinate issue before importing larger or more complex datasets.
Layer mapping is the process of deciding where imported GIS features should sit in the CAD layer structure. In GIS, data is often organised by feature class and attributes. In CAD, the drawing is usually organised by layers, colours, linetypes and plotting standards. A thoughtful layer strategy bridges those two ways of working.
For example, a local authority planning export might include polygons for conservation areas, listed building settings, development allocations and settlement boundaries. If all of that geometry is imported onto one generic layer, the drawing becomes hard to read and difficult to manage. If each feature type is mapped to a clear layer, the information can be switched on, frozen, plotted or isolated as needed.
Useful examples of layer mapping include:
Layer mapping is not only about presentation. It also affects how quickly someone else can understand the DWG. A contractor, planner or engineer opening the file should not have to inspect every object to work out what it is. The layer name should give them the first clue, with attributes providing further detail where needed.
GIS geometry tells you where something is. Attribute data tells you what it is. A polygon might represent a planning allocation, a flood zone, a land parcel or a habitat area. A line might be a sewer, a public footpath, a road edge or a cable route. Without attributes, different features can become visually similar, even when they mean very different things.
Attributes are usually stored as fields attached to each GIS feature. These might include names, IDs, classifications, dates, categories, status values, asset references or descriptive notes. When importing GIS data in CAD, preserving attributes can make the DWG far more useful than a simple linework conversion.
For example:
Native BricsCAD keeps imported attributes as GIS data attached to the entities themselves. You read, filter and edit that data in the GIS Attribute Table dialog box, opened from the GIS tab of the Civil Explorer panel, and it also appears in the Properties panel. It survives copying within the drawing, WBLOCK to an external DWG, and copy and paste between drawings. Third-party add-ons take a different route and typically store the equivalent information as DWG Extended Entity Data, or XDATA. Either way, the practical benefit is that users can interrogate features later, filter objects by their original GIS meaning, and from V26 drive civil labels directly from GIS attribute values.
There is a balance to strike. Importing every attribute from a large dataset can increase file complexity, especially when only the geometry is needed for background context. On the other hand, stripping attributes too early can leave you with a drawing that looks correct but has lost the information that made the GIS file valuable. The right choice depends on whether the data is only for visual reference or will be used for analysis, labelling, coordination or decision-making.
SHP, GML and KML can all carry vector spatial data, but they tend to appear in different working contexts. Understanding those differences helps you decide how to handle them during import.
The ESRI Shapefile format is common in planning, environmental and infrastructure workflows. A shapefile is not usually a single file in practice; it is a set of related files that together store geometry, indexing, projection information and attributes. When receiving SHP data, keep the accompanying files together in the same folder and under the same base file name. The .dbf carries the attribute table and the .prj carries the coordinate system definition. If the .prj is absent, BricsCAD has nothing to populate the Source Coordinate System column with and the data will not be reprojected. If the .dbf is absent, you get geometry with no attributes.
SHP is often used for boundary polygons, utility linework, asset points, constraints mapping and extracted GIS layers. When importing SHP into BricsCAD, check whether the layer contains points, lines or polygons, then select geometry options that suit your intended CAD use. For example, polygon planning areas may work well as closed polylines for drafting, while MPolygon may be more suitable where filled areas and boundary behaviour matter.
GML is often used for structured geographic data exchange, and native support for it is recent. GISIMPORT and GISEXPORT gained GML in BricsCAD V26, so the format will not appear in the dialog on V25 or earlier. In a GML BricsCAD workflow, you may receive data from public-sector, planning, land or infrastructure sources where the schema contains both geometry and descriptive fields. GML files can be highly structured, so it is worth reviewing the contents before importing everything into a working drawing.
If the GML contains multiple feature types, bring in only the ones needed for the immediate task. One UK-specific caveat deserves flagging here. GML is a container standard rather than a single schema, and Ordnance Survey MasterMap is supplied as gzipped GML with an OS-specific schema. Bricsys documents GML support in general terms and makes no claim about the MasterMap schema, so test a single tile before committing to a large order, and be prepared to use an add-on such as MapWorks or Spatial Manager, both of which name OS MasterMap explicitly.
For CAD users, the aim is to translate the useful spatial information into an editable and legible drawing without overloading the DWG.
KML and KMZ are often associated with web mapping, stakeholder mark-ups and simple location-based exchanges. Support was added to GISIMPORT and GISEXPORT in BricsCAD V25.2.01, with on-the-fly coordinate conversion enabled in the GIS Import dialog from V25.2, so earlier releases will not offer these formats. Because KML is defined in WGS84 latitude and longitude, that conversion is doing real work on every import into a projected drawing.. A KML BricsCAD import might be used for site extents, route options, access points, survey notes or indicative areas drawn in a mapping tool. KMZ is the compressed version and may include related resources.
Because KML data often comes from lightweight mapping workflows, check its accuracy before relying on it for design decisions. It may be good enough for early feasibility, communication or visual context, but it should be verified against proper survey, planning or authoritative datasets before it informs detailed engineering work.
GIS imports are particularly useful when CAD design needs to respond to real-world constraints. In UK planning and civil engineering workflows, the same BricsCAD drawing may need to accommodate survey, design, land, environmental and statutory information. Importing GIS data directly can reduce the need for awkward conversions and help teams keep context close to the design.
Typical use cases include:
Public datasets are not all licensed in the same way. Some may be open for broad reuse, others may have attribution requirements, restrictions on commercial use, access conditions, update limitations or separate terms from the data publisher. Before using any public planning, environmental, utility or topographic dataset in a project deliverable, check the licence for that specific dataset and source.
BricsCAD’s native GISIMPORT capability is often the best place to start. It supports common vector GIS workflows and allows users to bring files such as SHP, GML, KML/KMZ and supported geodatabase data into a DWG environment. For many day-to-day planning overlays, boundary checks and contextual imports, the built-in route may be enough.
However, some teams need broader format support, more control over reprojection, richer attribute handling or smoother import and export cycles. Third-party tools can help when GIS data becomes a regular part of production rather than an occasional background reference.
Add-ons such as Automapki Application extend GIS import and export inside BricsCAD, adding commands including AmExportMap for export and its import counterpart. It covers SHP, KML, KMZ, GPX and GeoJSON, handles coordinate system conversion so features land correctly on a georeferenced DWG, and preserves attributes as DWG XDATA, which is useful when imported features need to remain queryable or exportable. The publisher lists compatibility with BricsCAD Pro V18 through V26, alongside AutoCAD, GstarCAD and ZWCAD. One thing to check against your own data: GML does not appear in its published format list, so it is not an alternative to the native route if GML is what you receive.
Spatial Manager for BricsCAD is the broadest of the commercial options, working through the SPMIMPORT and SPMEXPORT commands. Its published provider list covers SHP, KML and KMZ, GML including gzipped .gz, GeoPackage, GeoJSON, read-only Esri File Geodatabase, LiDAR LAS and LAZ, GPX, MapInfo TAB and MIF/MID, OpenStreetMap, PostGIS and SQL Server Spatial, WMS, WMTS and XYZ background maps, and WFS or OGC API Features services. The compatibility limits matter before you budget for it: Windows only, BricsCAD v13 to v26, and Pro and Platinum editions only, so it will not install on BricsCAD Lite. MapWorks, also sold as BCSTools, is a second option worth knowing about for UK work, because its import list explicitly includes Ordnance Survey MasterMap GZip alongside SHP, GML, KML/KMZ and GeoPackage, and it can reproject during import.
When choosing between native import and an add-on, consider:
Some users convert files in external GIS software before bringing them into CAD, most commonly QGIS, which is free and writes DXF either one layer at a time through Save Features As, or for a whole project through Project, Import/Export, Export Project to DXF. The project route is the better one, because it lets you set the symbology mode and scale, the encoding, the target CRS that layers are reprojected to, and whether each layer is split into several DXF layers by a field value. Two limitations are worth knowing before relying on it. Attributes do not survive into DXF in a usable form, so you end up with linework and nothing behind it. And you must reproject to a projected CRS in metres before exporting, because a WGS84 layer will arrive at completely the wrong scale and in the wrong place without any error being raised. A direct or well-managed BricsCAD workflow is usually cleaner when the end goal is a usable drawing with its data intact.
The fastest import is not always the best import. A few checks before and after bringing GIS data into BricsCAD can prevent hours of cleanup later.
Before importing, confirm:
During import, watch for:
After import, check:
If the import does not align, avoid manually dragging the data into place unless you fully understand the transformation required. Moving GIS layers by eye may make the drawing look better but can destroy spatial accuracy. It is usually better to correct the CRS assignment, re-import, or use a controlled transformation workflow.
The Civil Explorer panel, opened with CIVILEXPLOREROPEN, is not merely adjacent to the GIS workflow. It is where imported GIS layers actually live. Its GIS tab lists every GIS layer and group in the drawing, controls their visibility, allows groups to be reordered by drag and drop, and offers a right-click menu covering Open attribute table, Edit GIS layer, Select, Zoom to, Add GIS features, Convert GIS data to Object data, Export GIS layer and Remove GIS layer. The same panel’s Civil tab holds surfaces, alignments, corridors, points and other project geometry, so constraints and proposals can be managed side by side. GIS import is not a replacement for good civil modelling practice, but it puts the surrounding information exactly where design decisions are being made.
The value comes from seeing constraints and proposals together, rather than treating GIS and CAD as separate worlds.
For example, a highway or infrastructure team might use GIS layers to understand land ownership constraints, environmental designations and existing utility corridors before developing a layout. A planning consultant might review site boundaries and policy layers in the same DWG used for presentation drawings. A drainage designer might bring in flood constraints, watercourses and topographic context before assessing potential outfall routes or storage locations.
The important principle is data discipline. Imported GIS layers should not be allowed to blur into proposed design layers without clear naming, checks and version control. If a dataset is advisory, call it advisory. If it is statutory, keep the source and licence information accessible. If it is superseded, archive or remove it so the drawing does not carry outdated context into later decisions.
Importing GIS data into BricsCAD is straightforward when the source data, coordinate system and drawing purpose are understood. The GISIMPORT command gives users a practical route for bringing SHP, GML and KML data into CAD as geometry that can be layered, checked and used alongside design information. For more demanding workflows, specialist add-ons can extend format support, reprojection options and attribute handling.
The best results come from treating GIS import as a controlled process rather than a one-click conversion. Know the licence, confirm the CRS, map layers sensibly, preserve attributes where they add value, and check alignment before the data influences decisions. Do that consistently, and BricsCAD becomes a stronger bridge between planning intelligence, civil design and day-to-day drawing production.
