- AutoCAD – Support is provided for reading most versions of AutoCAD DXF and writing AutoCAD 2000 version files.
- CSV files are a common interchange format between software packages supporting tabular data and are also easily produced manually with a text editor or with end-user written scripts or programs.
- (DD) Dump Data Dragon format is an easy to read and comprehend plain text format.
- DGN – Microstation DGN files from Microstation versions predating version 8.0 are supported for reading. The entire file is represented as one layer (named “elements”)
- ESRI GBD File – This provides read access to File Geodatabases (.gdb directories) created by ArcGIS 9. It can also read directly zipped .gdb directories (.gdb.zi
- GML – There is limited support for GML reading and writing. Update of existing files is not supported.
- GPX (the GPS Exchange Format) is a light-weight XML data format for the interchange of GPS data (waypoints, routes, and tracks) between applications and Web services on the Interne
- GeoPackage – This element provides access to spatial tables in the OGC GeoPackage format standard. The GeoPackage standard uses a SQLite database file as a generic container, and the standard defines:
- IHO S-57 – IHO S-57 datasets are supported for read access.
- JPEG Exif – Creates a layer containing information about the JPEG files, including location information and other information contained with the EXIF metadata stored in the JPEG files.
- KML – Keyhole Markup Language (KML) is an XML-based language for managing the display of 3D geospatial data. KML has been accepted as an OGC standard, and is supported in one way or another on the major GeoBrowsers.
- MS SQL Server – This element implements support for access to spatial tables in Microsoft SQL Server 2008+ which contains the geometry and geography data types to representation the geometry columns.
- MapInfo – MapInfo datasets in native (TAB) format and in interchange (MIF/MID) format are supported for reading and writing.
- Microsoft XLS – This element reads spreadsheets in MS Excel format. Formulas are not supported.
- Microsoft XLSX – This element can read, write and update spreadsheets in Microsoft Office Open XML (a.k.a. OOXML) spreadsheet format, generated by applications like Microsoft Office 2007 and later version
- Open Street – Support is provided for OpenStreetMap files in .osm (XML based) and .pbf (optimized binary) formats.
- Oracle – This element supports reading and writing data in Oracle Spatial (8.1.7 or later) Object-Relational format.
- PostGIS – This element provides support for access to tables in PostgreSQL including those with PostGIS spatial data support.
- SDTS TVP – SDTS TVP (Topological Vector Profile) and Point Profile datasets are supported for read access. Each primary attribute, node (point), line and polygon module is treated as a distinct layer.
- SQLite – This element supports spatial and non-spatial tables stored in SQLite 3.x database files. SQLite is a “light weight” single file based RDBMS engine with fairly complete SQL semantics and respectable performance.
- Shape – All varieties of ESRI Shapefiles should be available for reading, and simple 3D files can be created.
- Shape XY(Z)M – This element is specifically for reading ShapeFiles in PointM format. Using this element the Point and Measure (M) values can be separated into their own columns.
- Smallworld – To connect to a Smallworld Dataset, the Data Dragon Smallworld Module must first be loaded. Use the Smallworld Module Dialog (in Smallworld) to load this module. The module code is located in the Data Dragon product directory. Prior to loading for the first time, edit DataDragonInitialise.magik on the first line of the file to set a suitable working directory – it is currently set to “C:\Temp”.
- TIGER – TIGER/Line file sets are supported for read access
- UK NTF – The National Transfer Format, mostly used by the UK Ordnance Survey, is supported for read access. This element treats a directory as a dataset and attempts to merge all the .NTF files in the directory, producing a layer for each type of feature (but generally not for each source file). Thus a directory containing several Landline files will have three layers (LANDLINE_POINT, LANDLINE_LINE and LANDLINE_NAME) regardless of the number of landline files.