Not only works in basic AutoCAD: also in Autodesk AutoCAD Map 3D, Autodesk AutoCAD Civil 3D, Autodesk AutoCAD Architecture, etc.

General

Spatial Manager™ for AutoCAD is a powerful AutoCAD plug-in designed for AutoCAD users who need to import, export and manage spatial data in a simple, fast and inexpensive way, which includes many possibilities not seen so far in AutoCAD.

It comes in a lightweight application that runs inside AutoCAD and allows the user to import and export geospatial data between AutoCAD drawings and geospatial tables (files, data servers or data stores), display background maps and manage alphanumeric data and data tables

AutoCAD import

Spatial Manager™ for AutoCAD imports spatial data, into new or existing AutoCAD drawings, as AutoCAD objects and Extended Entity Data (EED/XDATA), using a powerful wizard which lets the user choose or select all the necessary import parameters in order to get differentiated spatial information in a CAD drawing.

Automatic layering, fill with polygons, blocks according to data values and mapped attributes, or labeling are only part of the application functionality when importing from spatial files, data servers, data stores, etc. The user can choose import the polygons using "MPolygon" objects, even on basic AutoCAD.

The "Tasks" save all the import processes parameters and options in order to repeat these processes so many times as desired. It is possible to execute one or more "Tasks" at once

AutoCAD export

Spatial Manager™ for AutoCAD exports objects from the drawing to spatial files or databases and saves their Extended Entity Data (EED/XDATA) as alphanumeric data tables using a wizard, which shares some of the steps with the import wizard. In the same way, the user can choose or select the export parameters to define all the target data among a great number of possibilities.

The export functionality includes options to export the handle and layer of the objects, as well as the block attributes and the text objects properties.

There are options for filtering the objects when exporting, and all the geometric operations needed to fit the target data format are automatically performed.

Transformation of coordinates

Spatial Manager™ for AutoCAD will calculate geometric transformations of the features in line with the import and export processes, which will depend on the chosen Coordinate System (CRS) for the source and target data.

The user can choose the appropriate CRSs from a complete CRS catalog or from a list which includes the most recent used CRSs.

Background Maps

The AutoCAD users (from v.2008), can choose among many Backgrounds Maps from many providers such as OpenStreetMap, Bing, MapBox, Ordnance Survey, etc.

The users can design and edit the structure which will be used to store the data. In addition, the data values can be modified in the palette of the application. There is a command to select objects according to the table that they are attached.

User data sources

Spatial Manager™ for AutoCAD incorporates the UDS technology to easily connect with spatial database servers, or data stores. UDSs avoid having to enter a lot of connection parameters

Import/Export graphical features and alphanumeric data into AutoCAD drawings from/to:

Informace o této verzi

Verze 5.2.0.8276, 5.4.2019

April 1, 2019 - Release 5.2.0
Improvements
The application is now compatible with AutoCAD 2020 and other Autodesk 2020 products [T4964] (see current Compatible AutoCAD applications)
A new button has been included in the data grid to show the table attached to the selected object, or to one of the selected objects if they are more than one [F2884]
The "Forward" row navigation button in the data grid is now also active even if only 1 object is selected [F2914]
When capturing a background map image shown on screen, the user can now define a capture window, not just the full screen as in previous versions [F2581] (Related video)
Image captures can now be inserted into the drawing as OLE objects and not just as external references [F2907] (Related video)
Now it is possible to select a background color or transparent background for those WMS background maps that support it [F2891] (Related video)
Added a new option to allow the user to select the coordinate system in which a XYZ/TMS background map is defined [F2740]
XYZ/TMS type background maps whose origin is defined bottom-left are now supported (OSGeo Specification) [F2854]
When a coordinate system is automatically assigned to a drawing, empty and with no system assigned, when displaying a background map, the system defined for the background map is now taken, not the 3857 system in all cases (this was the case in previous versions) [F2901]
The new NearMap API has been updated for access to its background maps [F2877]
Added NearMap oblique maps [F2911] (Related video)
Now all schemes in a user data source (UDS) can be imported through the application palette right-click menu, except for database servers (SQL Server, PostGIS, etc.) for performance reasons [F998] (Related video)
Now it is possible to import all tables in a schema and all schemas in a file (e.g. GPX or SQLite) through the application palette right-click menu [F999] (Related video)
A "Back" button has been added at the end of an export process so that it can be easily replayed by modifying any of the wizard parameters after a failed export [F2898] (Related video)
The GML data provider now has write capability so it allows you to export to this file type [F2890] (Related video)
The geometries conversion method has been improved in the GML data provider [F2889]
The naming of the images generated when exporting to Google Earth has been improved, as well as their grouping in the resulting KML/KMZ file structure [D2166]
The EPSG tables (CRSs and other objects) have been updated to version 9.6 [T5006]
More than 1300 ESRI coordinate systems have been added to the application systems database [F2903]
Whenever a generic coordinate system is automatically assigned to an unreferenced drawing, a warning is now displayed that it may be inaccurate for some areas of the earth [F2915]
Fixes
Data is no longer lost when renaming a data table if two imports are processed using the same destination table name [D2212]
Fixed a problem that caused errors when importing multi-points as a block selecting its name from a field in the data table [D2206]
Fixed an issue that caused errors when reading improperly finished Shapefiles [D2176]
Fixed a bug where sometimes multi-geometry polygons KML/KMZ were not read [D2213]
Polylines belonging to a collection of geometries are now properly labeled [D2180]
Fixed an error that occurred in some cases when importing datasources with an unknown coordinate system [D2161]
The list of Fields to be exported is now correctly displayed when the option "Also export fields with null values" has been selected [D2004]
In Google Earth exportation, a bug that occurred when overwriting raster image files has been fixed [D2166]
Corrections of other minor bugs and other minor improvements