Autodesk DWG

The Autodesk DWG Data Store is available for reading and writing data in 1Integrate.

Read and Write Support

Read	Write
Read	Commit	Copy To

Data Support

Data	Support	Notes
Non-Spatial
2D
Measured
Heighted
3D		For more information about 3D data in 1Integrate, please refer to Full 3D Support.

Key Information

When configuring Copy To mapping any attribute named COLOR with the integer type will be written as the colour of the entity. If COLOR does not match the required integer type it will be written to XDATA.
- Note: Any Attribute other than COLOR will be written into the XDATA (Extended Data) attribute when using Copy To.

Read Attributes

The following attribute types are Read in by the Autodesk DWG Data Store.

Attributes

Attribute	Type	Description
`BLOCK_NAME`	string	The name of an AutoCAD block.
`BLOCK_NUMBER`	integer	Block references in a layer are given a number. This can be used to link the block reference to its insert point.
`ENTITY_TYPE`	string	The entity type in the drawing (e.g. line, point or shape). This is used to simplify specifications of feature types.
`INSUNITS`	string	The drawing units value used for scaling.
`LUNITS`	integer	The linear unit format.
`VERSION`	string	The version of the AutoCAD drawing file. Reads in with the `acDbDwgVersion` format version number e.g. `kDHL_1027`.
`ENTITY_HANDLE`	string	The unique identifier for the entity.
`VISIBILITY`	string	Used to indicate the visibility of the entity.
`LAYER_COLOR`	integer	The colour of the entity layer.
`COLOR`	integer	The colour of the entity itself.
`LINE_TYPE`	string	The property assigned to a line to determine the pattern of the line (e.g. dashes, dots, text and symbols). Would override `layer_line_type` for this entity.
`LINE_WEIGHT`	integer	The property assigned to a line to determine thickness. Would override `layer_line_weight` for this entity.
`LAYER_LINE_TYPE`	string	The property assigned to lines in the layer to determine the pattern of the line (e.g. dashes, dots, text and symbols).
`LAYER_LINE_WEIGHT`	integer	The property assigned to lines to determine thickness.
`FILE _NAME`	string	The name of the DWG file.
`TEXT`	string	Text applied to entities as a label.
`THICKNESS`	integer	Determines how tall entities are.
`UCS_NAME`	string	The name of the User Coordinate System (UCS)
`UCS_ORIGIN_X`	real	The x coordinate of the origin.
`UCS_ORIGIN_Y`	real	The y coordinate of the origin.
`UCS_ORIGIN_Z`	real	The z coordinate of the origin.
`UCS_XDIRECTION_X`	real	The x-axis' x coordinate for the UCS.
`UCS_XDIRECTION_Y`	real	The x-axis' y coordinate for the UCS.
`UCS_XDIRECTION_Z`	real	The x-axis' z coordinate for the UCS.
`UCS_YDIRECTION_X`	real	The y-axis' x coordinate for the UCS.
`UCS_YDIRECTION_Y`	real	The y-axis' y coordinate for the UCS.
`UCS_YDIRECTION_Z`	real	The y-axis' z coordinate for the UCS.
`XREF_PATH`	string	The path for any external references.
`XREF_STATUS`	string	Indicates the status of the externally referenced file.
`BLOCK_INSERT_X`	real	The x coordinate of the insert point for the block entity.
`BLOCK_INSERT_Y`	real	The y coordinate of the insert point for the block entity.
`BLOCK_INSERT_Z`	real	The z coordinate of the insert point for the block entity.
`LAYOUT_NAME`	string	The layout name.
`SCALE`	string	The annotation scale for the drawing.
`BLOCK_ATTRIBUTES`	string	A label or tag giving more information about a block e.g. a block representing a desk may have the user's name as an attribute.
`XDATA`	string	Extended data information. When presented in a `\"key=value\"` pair from your source data it will be added as attributes to the layer. Otherwise, an XDATA attribute will contain the external data of an entity in a JSON format.

Parameters

Read and Commit

Parameter	Description
Source Files Required: .dwg/.dxf Zipped: .zip/.gz	Click the Upload button and drag and drop the file anywhere or click to browse. Note: You can only provide one .dwg or .dxf file at a time and if using a zipped file, there should only be one .dwg or .dxf file inside.
Add Attributes from Extended Data	If selected, any additional extended data information that follows a `\"key=value\"` format in your source data will be added as attributes to the layer. Otherwise, an `XDATA` attribute will contain the external data of an entity in a JSON format. Note: This will cause 1Integrate to read all data in the DWG file to determine the external data attributes. This may impact performance when refreshing the Schema.
Add Attributes from Block Reference	If selected, any additional block attributes in your source data will be added as attributes to the layer. Otherwise, a `BLOCK_ATTRIBUTES` attribute will contain all the block attributes of an entity in a JSON format. Note: This will cause 1Integrate to read all data in the DWG file to determine the block attributes. This may impact performance when refreshing the Schema.
Coordinate reference system	This parameter can be used to specify a Coordinate Reference System (CRS) code of the input data. The input format will be `SRID=######` for Spatial Reference Identifiers (SRID) and `EPSG=######` for EPSG codes. See Coordinate Reference System for more information on this parameter, and when it may be required. This will not re-project the data, but allows its current CRS to be defined (e.g to enable multiple data stores to open where one does not have a CRS defined). Note: When you override the CRS you must refresh the Data Store's schema before it will take effect. Note: Coordinate Reference System parameters are required in a session that will write data to Oracle.
Allow invalid geometries	Allows features with invalid geometries (e.g. duplicate vertices, self-intersections) to be imported. This is necessary if they need to be imported in order to be validated or corrected. If not ticked then features with invalid geometries are not imported and are logged as feature errors in the open data task.
Read all geometries as 2D	If selected, all geometries will be read as 2D and any Z or M coordinates will be discarded.
Unit Length	Unit length (scale factor to metres). This controls the tolerance of what distance can be considered insignificant. Tolerance is a key factor in determining how closely two points, lines, or shapes are considered to be the same (duplicates). If the distance between two points is less than the tolerance, they will be treated as duplicates or simplified into a different shape. This is critical when managing large datasets and affects the overall precision and efficiency of spatial operations. Note: Tolerance set here overrides tolerance set by the CRS parameter. Example: The larger the Unit Length is, the higher the tolerance for geometries are, meaning geometries will be more accurate. However, as the geometries are denser, the data will be slower to load and process (which may be noticeable in the Map Viewer). Conversely, the smaller the unit length is, the simpler geometries become. This means that geometries will be less accurate but will load much faster. If there are geometries where the distance between two points is less than the tolerance, 1Integrate treats them as a duplicates. This is important as some geometries may be converted to a different shape (i.e. a circle may be transformed into a line, or a line may be transformed into a point). This transformation can be seen in the images below: The data with no Unit Length set. The data with the Unit Length set to 10. The data with the Unit Length set to 0.001. If your data contains geometries with very small distances between two points, using a larger Unit Length will ensure that these geometries are read correctly. For geometries with larger distances between points, a smaller Unit Length will allow these geometries to be processed more efficiently.

Copy To

Parameter	Description
Destination Files (.DWG)	Results are available to download by clicking Download.
DWG Format Version	Select the DWG format version from the drop down list. By default this is set to the 2010/2011/2012 version.
Allow invalid geometries	Allows features with invalid geometries (e.g. duplicate vertices, self-intersections) to be imported. This is necessary if they need to be imported in order to be validated or corrected. If not ticked then features with invalid geometries are not imported and are logged as feature errors in the open data task.