This section contains technical descriptions of GIS formats supported by MAPublisher. Here you will find an overview of the structure of each format, as well as information on supported format versions and elements unique to each data type. Each file format will carry a checklist covering which core elements are supported by MAPublisher during its import. You can also refer to the Frequently Asked Questions section in this guide for information on any issues associated with the various file formats.

AutoCAD Drawing (dwg) and Drawing Exchange (dxf)

There are two formats used by AutoCAD: DXF and DWG. DXF is a CAD data file format, developed by Autodesk as their solution for enabling data interoperability between AutoCAD and other programs. The DWG format is used for storing two and three dimensional design data and is the internal format for the AutoCAD Computer Aided Design package. DWG is also the common name for AutoCAD proprietary DWG technology developed by Autodesk for their AutoCAD package.

Supported Elements

 

Typical File Extensions        

*.dwg, *.dxf

Automated Translation

Yes

User-Defined Attributes

Yes*

Coordinate System Support

No

Generic Colour Support

Yes

Spatial Index

Never

Schema Required

Yes

3D Support

Yes

*  AutoCAD format only has RecordNum and ElementID attributes.

Supported Geometry

 

Aggregate

No

Circles

Yes

Circular Arc

Yes

Elliptical Arc

Yes

Ellipses

Yes

Polygon

Yes

Donut Polygon

Yes

Point

Yes

Line

Yes

Text

Yes

 Supported Versions

       Windows: Releases vrs. R12 to 2007

 Mac: Releases vrs. R12 to 2007.

Prior to the import process, additional Settings can be made, which will affect how the selected file will import. The following parameters can be applied to the import:

Group Entities - Group entities by Layer Name or Geometry.

Hatches - Check this box if you want MAPublisher to read your hatch patterns upon import.

White Lines and Fills - Enabling the Import as is option will instruct MAPublisher to import the data true to the original colour settings contained in the file. Check the Change white lines and fills to black box to import black lines instead of the files native white lines. Check the Create black background option to incorporate a layer containing a black background to mimic the AutoCAD environment.

Delimited XY Text Data (csv, tsv, txt)

An ASCII file containing a tabular data where delimiters separate the columns and rows. Common delimiters are commas, spaces or tabs. Microsoft Excel and many other spreadsheet programs will export data in these formats.

Supported Elements

 

Typical File Extensions        

*.csv, *.tsv, *.txt

Automated Translation

Yes

User-Defined Attributes

Yes

Coordinate System Support

No

Generic Colour Support

No

Spatial Index

Never

Schema Required

Yes

Supported Geometry

 

Aggregate

No

Circles

No

Circular Arc

No

Elliptical Arc

No

Ellipses

No

Polygon

No

Donut Polygon

No

Point

Yes

Line

No

Text

No

Prior to the import process, additional Settings can be made, which will affect how the selected file will import. The following parameters can be applied to the import:

Axis Column - Specify which columns contain the x and y coordinates for the point data to be read in.

Coordinate Format - Choose the formatting type of the data you wish to import (e.g. Decimal Degrees, Delimited Degrees Minutes Seconds, Packed DMS)

Use first line as header - Allows the user to enable the first line of the text file to be used as column headings.

Esri Interchange File (e00)

An archive of files that describes a complete ArcInfo coverage. This is either ASCII or compressed into a binary and is used to transfer files between different versions of ArcInfo.

A single E00 file describes a complete ArcInfo coverage. The file itself is actually an archive of several smaller files, referred to as subfiles. Some of these subfiles have fixed names which do not vary from coverage to coverage, and follow a predefined data format. The remainder of the subfiles contained within an E00 are the info files. These files may contain user-defined attributes, and have names which vary from coverage to coverage.

Supported Elements

 

Typical File Extensions        

*.e00

Automated Translation

Yes

User-Defined Attributes

Yes

Coordinate System Support

Yes

Spatial Index

Never

Schema Required

Yes

Geometry Type Attribute

e00_type

Supported Geometry

 

Aggregate

No

Circles

No

Circular Arc

Yes

Elliptical Arc

Yes

Ellipses

No

Polygon

Yes

Donut Polygon

Yes

Point

Yes

Line

Yes

Text

Yes

There are essentially four types of geometry defined in E00 files, which will be reproduced as layers during import: Arcs (lines), Points, Polygons, and Text. Prior to the import process, an additional Setting can be made:

Tic points layer - This option enables you to include an additional layer which will hold the registration points for the imported data. The default is to set to Yes.

Esri ArcInfo Generate (gen)

Esri simple ASCII storage and interchange format. There are three different types of .gen files each with of its own syntax one for points, one for lines, and one for text geometries. This is the format exported by ArcInfo generate command. The *.gen files are use by ArcInfo to transfer coverages to other mapping systems.

Supported Elements

 

Typical File Extensions        

*.gen

Automated Translation

Yes

User-Defined Attributes

No

Coordinate System Support

No

Generic Colour Support

No

Spatial Index

Never

Schema Required

Yes

Geometry Type Attribute

arcgen_geometry

Supported Geometry

 

Aggregate

No

Circles

No

Circular Arc

No

Elliptical Arc

No

Ellipses

No

Polygon

No

Donut Polygon

No

Point

Yes

Line

Yes

Text

Yes

File/Personal Geodatabases

A geodatabase is a native Esri ArcGIS data format for storing geographic data. It is a collection of geographic datasets of various types used in ArcGIS and managed in either a file folder or a relational database. There are two main types of geodatabases:

Single-User: Personal Geodatabases (extension *.mdb) and File Geodatabases (extension *.gdb)

Supported Elements

 

Typical File Extensions        

*.mdb (personal), *.gdb (file)

Automated Translation

Yes

User-Defined Attributes

Yes

Coordinate System Support

Yes

Generic Colour Support

No

3D Support

Yes

Schema Required

Yes

Transaction Support

Yes

Enhanced Geometry

Yes

Geometry Type Attribute

geodb_type

Encoding Support

Yes

Supported Geometry

 

Aggregate

Yes

Circles

Yes

Circular Arc

Yes

Elliptical Arc

Yes

Ellipses

Yes

Polygon

Yes

Donut Polygon

Yes

Point

Yes

Line

Yes

Text

Yes

Raster

No

Solid

No

Surface

No

Z value

Yes

Esri Shapefile (shp)

The Esri Shapefile is a geospatial vector data format for geographic information systems software. It is developed and regulated by Esri as a mostly open specification for data interoperability among Esri and other software products. A Shapefile is a digital vector storage format for storing geometric location and associated attribute information. This format lacks the capacity to store topological information. A single logical Shapefile consists of three physical files, each with one of the following file name extensions:

Extension

Description

*.shp

Geometric data

*.shx

Index to the geometric data

*.dbf

Attributes for the geometric data

These extensions are added to the base name of the Shapefile, creating separate physical files that must all reside in the same directory. You must select the *.shp file for import. Point, multipoint, polyline, and polygon geometric data can be stored in *.shp files. However, a single *.shp file can contain only one type of geometry. Each entity in a *.shp file has a corresponding entry in the *.shx index file and a corresponding row of attributes in the associated *.dbf file. The order of the entries in each of these files is synchronized. For example, the 3rd geometric entity in the *.shp file is pointed to by the 3rd entry in the *.shx index file and has the attributes held in the 3rd row of the *.dbf.

A single Shapefile may also consist of a number of additional files, with the following file name extensions:

Extension

Description

*.sbn, *.sbx

Spatial index files for the geometric data. These two files are only generated by an Esri product; however, they are not required by MAPublisher for import and will not be generated when exporting data to the Shapefile format.

*.prj

Spatial coordinate system information.

If a *.prj file exists in your Shapefile directory, holding the coordinate system information of the Shapefile, this will automatically be read by MAPublisher on import. If your Shapefile folder does not contain a .prj file you will be required to specify the coordinate system in order to fully utilize MAPublisher.

Supported Elements

 

Typical File Extensions        

*.shp (*.shx, *.dbf, *.prj)

Automated Translation

Yes

User-Defined Attributes

Yes

Coordinate System Support

Yes (if have *.prj)

Generic Colour Support

No

3D Support

Yes

Schema Required

Yes

Transaction Support

No

Enhanced Geometry

Yes

Geometry Type Attribute

SHAPE_GEOMETRY

Supported Geometry

 

Aggregate

Yes

Circles

No

Circular Arc

No

Elliptical Arc

No

Ellipses

No

Polygon

Yes

Donut Polygon

Yes

Point

Yes

Line

Yes

Text

No

Microsoft Excel (xls, xlsx, xlsm)

Microsoft Excel format is read mainly as a text file containing tabular data where delimiters separate the columns and rows. Common delimiters are commas, spaces or tabs.

Supported Elements

 

Typical File Extensions        

*.xls, *.xlsx, *.xlsm

Automated Translation

Yes

User-Defined Attributes

Yes

Coordinate System Support

No

Generic Colour Support

No

Schema Required

Yes

Transaction Support

No

Geometry Type Attribute

xlsx_none

xlsx_point

Supported Geometry

 

Aggregate

No

Circles

No

Circular Arc

No

Elliptical Arc

No

Ellipses

No

Polygon

No

Donut Polygon

No

Point

No

Line

No

Text

No

Geography Markup Language (gml)

GML was designed as a geographic interface language for the Geo-Web. It is currently in draft as an ISO standard (ISO 19136). The goal of the format is to provide users with a set of abstract base objects that can be built into working real world datasets. It uses as XML base to store geometry and feature information that can easily be transported across the Internet.

The GML simple feature profile was created by the Open Geospatial Consortium as a restricted subset of the GML specification. It provides a reduced geometry and metadata profile that can be shared across many GIS tasks. This simple feature model can be used as a base to generate local application profiles for a specific work area. Since the GML models base abstract classes, these application profiles (schemas) are required for accessing and processing any GML datasets. Generally, GML data has a *.gml extension, and requires any application specific schema files (*.xsd).  For more information on GML, and the GML simple features profile, please visit the Open Geospatial Consortium web site: www.opengeospatial.com.

Supported Elements

 

Typical File Extensions        

*.gml, *.xml, *.xsd

Automated Translation

Varies

User-Defined Attributes

Yes

Coordinate System Support

Yes

Generic Colour Support

No

3D Support

Yes

Schema Required

Yes (*.xsd)

Transaction Support

No

Geometry Type Attribute

xml_type

Supported Geometry

 

Aggregate

Yes

Circles

No

Circular Arc

Yes

Elliptical Arc

No

Ellipses

No

Polygon

Yes

Donut Polygon

Yes

Point

Yes

Line

Yes

Text

No

GeoJSON (geojson, json)

GeoJSON is a format for encoding a variety of geographic data structures. A GeoJSON object may represent a geometry, a feature, or a collection of features. GeoJSON supports the following geometry types: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, and GeometryCollection. Features in GeoJSON contain a geometry object and additional properties, and a feature collection represents a list of features. A complete GeoJSON data structure is always an object (in JSON terms). In GeoJSON, an object consists of a collection of name/value pairs -- also called members. For each member, the name is always a string. Member values are either a string, number, object, array or one of the literals: true, false, and null. An array consists of elements where each element is a value as described above.

Supported Elements

 

Typical File Extensions        

*.json

Automated Translation

Yes

User-Defined Attributes

No

Coordinate System Support

Yes

Generic Colour Support

No

3D Support

-

Schema Required

No

Transaction Support

No

Geometry Type Attribute

json_type

Supported Geometry

 

Aggregate

Yes

Circles

No

Circular Arc

No

Elliptical Arc

No

Ellipses

No

Polygon

Yes

Donut Polygon

No

Point

Yes

Line

Yes

Text

No

Google Earth (kml, kmz)

KML is an XML-based language for managing the display of three-dimensional geospatial data in the programs Google Earth, Google Maps, Google Mobile and WorldWind. The KML file specifies a set of features for display. Each feature always has a longitude and a latitude and can have other data, such as tilt, heading, and altitude. KML shares some of the same structural grammar as GML. KML files are very often distributed as KMZ files, which are zipped KML files with a .kmz extension. MAPublisher uses KML version 2.2 specifications for import and export.

Supported Elements

 

Typical File Extensions        

*.kml, *.kmz

Automated Translation

Yes

User-Defined Attributes

Yes

Coordinate System Support

Yes

Generic Colour Support

Yes

3D Support

Yes

Schema Required

No

Supported Geometry

 

Aggregate

Yes

Circles

No

Circular Arc

No

Elliptical Arc

No

Ellipses

No

Polygon

Yes

Donut Polygon

Yes

Point

Yes

Line

Yes

Text

No

Prior to the import process, additional Settings can be made, which will affect how the selected KML file will import. The following parameters can be applied to the import:

•        Allow Random Colour Mode - This option allows Adobe Illustrator to generate random colour settings for the data.

•        Expand Network Links - Checking this box will enable the use of network linked KML files.

•        Import KML Properties as Visible - Check this option to make KML properties visible attributes (hidden by default).

GPS Exchange Format (gpx, xml)

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 Internet.

Supported Elements

 

Typical File Extensions        

*.gpx, *.xml

Automated Translation

Yes

User-Defined Attributes

No

Coordinate System Support

Yes

Generic Colour Support

No

Schema Required

Yes

Transaction Support

No

Geometry Type Attribute

xml_type

Supported Geometry

 

Aggregate

Yes

Circles

No

Circular Arc

No

Donut Polygon

No

Elliptical Arc

No

Ellipses

No

Line

Yes

None

Yes

Point

Yes

Polygon

No

Raster

No

Text

No

MapInfo Interchange Format (mif)

MIF is a published ASCII storage format used by the MapInfo. It is used as a file format for map and database exporting/importing in MapInfo software products. The MapInfo Reference Manual describes the MIF format and all constants it uses for colour, style, symbol, and fill patterns. MapInfo Interchange Format Files are often called MIF or MIF/MID files.

A single logical MIF file consists of two physical files, having the following file name extensions:

Extension

Description

*.mif

Geometric data

*.mid

Attributes for the geometric data

These extensions are added to the base name of the MIF file, creating separate physical files that must all reside in the same directory. You must select the *.mif file for import.

Each entity in a *.mif file has a row of attributes stored in an associated *.mid file. A single .mif file contains many different types of geometry however, the associated attribute in the *.mid file must have the same number and type of fields for each entity in the *.mif file. The order of the entries in the two files is synchronized. For example, the second geometric entity in the *.mif file has the attributes held in the second row of the *.mid file. The number and type of attributes associated with each entity is specified by the user. There must be at least one attribute field in the *.mid file.

Supported Elements

 

Typical File Extensions        

*.mif, *.mid

Automated Translation

Yes

User-Defined Attributes

Yes

Coordinate System Support

Yes

Generic Colour Support

Yes

Spatial Index

Never

Schema Required

Yes

Geometry Type Attribute

mif_type        

Supported Geometry

 

Aggregate

Yes

Circles

Yes

Circular Arc

Yes

Elliptical Arc

Yes

Ellipses

Yes

Polygon

Yes

Donut Polygon

Yes

Point

Yes

Line

Yes

Text

Yes

Prior to the import process, additional Settings can be made, which will affect how the selected file will import. The following parameters can be applied to the import:

•        Import as Visible Attributes - Enable this option to view the pen and brush pattern values in the imported attribute table.

The MAPublisher MID/MIF importer supports the storage of point, line, polyline, arc, ellipse, rectangle, rounded rectangle, region (polygon), and text geometric data in *.mif files. Each geometric entity present in a *.mif file has display properties such as pen and brush width, pattern, and colour. Supported MID/MIF properties are as follows:

MAPublisher supports the import of line weights (0-7), colours (24 bit RGB), strokes (1-71). It also supports fonts (family, style, justification) for text. In order to use line patterns and fill patterns you must have opened or accessed the style library equivalents. Two library files have been created, MIF - Line Styles.ai and MIF - Area Styles.ai, which provide support for many of the standard MapInfo pen styles (stroke patterns) and brush styles (fill patterns). These files can be found in the Helpful Styles & Symbols folder installed with MAPublisher. Please refer to your Adobe Illustrator User Guide for details about how to add these libraries to your Adobe Illustrator Graphic Style panel.

MapInfo Table (tab)

TAB is a proprietary geospatial vector data format for geographic information systems software used by MapInfo mapping products. A minimum of two files are required for the tab format. The .DAT file which stores the attribute data and the .TAB ASCII file which is the link between all other files and holds information about the type of data file. The MapInfo TAB importer is closely patterned after the MapInfo MIF/MID reader and writer. This commonality makes it easy to support both MIF and MapInfo native formats in the same mapping file.

A single logical TAB file consists of a number of physical files, having the following file name extensions:

Extension

Description

*.tab

The main file for a MapInfo table, it is associated with the appropriate dat, map, id and ind files.

*.dat

Tabular data for a table in MapInfo native format

*.id

An index to a MapInfo graphical objects (MAP) file.

*.map

Contains geographic information describing map objects

*.ind

An index to a MapInfo tabular (DAT) file

These extensions are added to the base name of the TAB file, creating separate physical files that must all reside in the same directory. You must select the *.tab file for import.

Supported Elements

 

Typical File Extensions        

*.tab (*.dat, *.id, *.map, *.ind)

Automated Translation

Yes

User-Defined Attributes

Yes

Coordinate System Support

Yes

Generic Colour Support

Yes

Spatial Index

Always

Schema Required

Yes

Geometry Type Attribute

mapinfo_type

Supported Geometry

 

Aggregate

Yes

Circles

Yes

Circular Arc

Yes

Elliptical Arc

Yes

Ellipses

Yes

Polygon

Yes

Donut Polygon

Yes

Point

Yes

Line

Yes

Text

Yes

Prior to the import process, additional Settings can be made, which will affect how the selected file will import. The following parameters can be applied to the import:

•        Import as Visible Attributes - Enable this option to view the pen and brush pattern values in the imported attribute table.

The MAPublisher TAB importer supports the storage of point, line, polyline, arc, ellipse, rectangle, rounded rectangle, region (polygon), and text geometric data in .tab files. Each geometric entity present in a *.tab file has display properties such as pen and brush width, pattern, and colour. Supported TAB properties match those described for MID MIF files on the previous page.

Raster TAB files cannot be imported in MAPublisher.

MicroStation Design (dgn)

DGN are the native files created for Bentley Systems Inc. MicroStation product. These files consist of a header, followed by a series of elements. The header contains global information including the transformation equation from design units to user coordinates, as well as the dimension of the elements in the file. Each element contains standard display information, such as its colour, level, class, and style, as well as a number of attributes specific to its element type. For example, a text element has fields for font, size, and the text string in addition to the standard display attributes.

Supported Elements

 

Typical File Extensions        

*.dgn

Automated Translation

Yes

User-Defined Attributes

Yes

Coordinate System Support

No

Generic Colour Support

Yes

Spatial Index

Never

Schema Required

Yes

Geometry Type Attribute

igds_type

3D Support

Yes

Supported Geometry

 

Aggregate

No

Circles

Yes

Circular Arc

Yes

Elliptical Arc

Yes

Ellipses

Yes

Polygon

Yes

Donut Polygon

Yes

Point

Yes

Line

Yes

Text

Yes

Supported Versions

Windows: V7, V8. Mac: V7,V8

Prior to the import process, additional Settings can be made, which will affect how the selected file will import. The following parameters can be applied to the import. Note: versions V7 and V8 are supported for import, attached raster files are ignored.

Group Elements - Choose how you want to group the elements of the file on import. If you group the elements by level, it may result in a large number of output files. By Level is the default.

Coordinate Units - Choose Master or UOR (Unit of Resolution) as the coordinate units. Master is the default.

White Lines and Fills - Enabling the Import as is option will instruct MAPublisher to import the data true to the original colour settings contained in the file. Check the Change white lines and fills to black box to import black lines instead of the files native white lines. Check the Create black background option to incorporate a layer containing a black background to mimic the AutoCAD environment.

Other - Check Drop complex chains if you want each component of a complex chain to be returned as its own feature, otherwise all elements of the complex chain will be merged into a single linear feature.

Line weight in Microstation are integer number only, as such, the Microstation export will round the Adobe Illustrator stroke width. 0 is a valid line weight in Microstation.

International Hydrographic Office S-57 format (000)

S-57format is intended for the exchange of digital hydrographic data between national hydrographic offices and for its distribution to manufacturers, mariners and other data users. It is used for the supply of ENC cells (Electronic Navigational Charts) to ECDIS (Electronic Chart Display and Information System).

The format is public, developed and maintained by the IHO (International Hydrographic Office) CHRIS working committee (Committee on Hydrographic Requirements for Information Systems). The objects spatial geometry can be of Point, Line or Area geometry, while object descriptions are categorized in object classes, organized in specific attributes schemas. For a full format description, please visit https://www.iho.int/iho_pubs/IHO_Download.htm#S-57 (Appendix A in particular). An online object catalog is also available on www.s-57.com

An S-57 base file has the extension *.000, while the update files have extensions like .001, .002 and so on. It can also be accompanied by other files:

Extension

Description

*.000

main file

*.001

update file 1

*.002

update file 2

*.00n

update file n

files.TXT and files.JPG

ancillary text and picture files indicated in attribute definition

Update files contains only the changed (new/deleted/modified) objects and are only used as a complement of a .000 file. Only the *.000 file is required for the import into MAPublisher. The update files will be applied at conversion, when present. However, text and image files linked to attributes will be ignored.

Supported Elements

 

Typical File Extensions        

*.000 (*.001 *.002...)

Automated Translation

Yes

User-Defined Attributes

No

Coordinate System Support

Yes

Generic Colour Support

No

3D Support

Yes

Schema Required

N/A

Geometry Type Attribute

s57_type

Supported Geometry

 

Aggregate

No

Circles

No

Circular Arc

No

Elliptical Arc

No

Ellipses

No

Polygon

Yes

Donut Polygon

Yes

Point

Yes

Line

Yes

Text

No

information Most ENC producers (private and public) publish their .000 files in encrypted formats. Only non-encrypted files can be imported in MAPublisher (from NOAA or USACE for example).

TIGER/LINE (rt1, bw1)

Topologically Integrated Geographic Encoding and Referencing (TIGER). TIGER is the United States Census Bureau format for its digital database of geographic features. TIGER includes both land attributes such as roads, buildings, rivers, and lakes, as well as areas such as counties, ZIP codes, census tracts, and census blocks. Some of the geographic areas represented in TIGER are political areas, including counties, congressional districts, school districts, and ZIP codes. Others are statistical areas, including Metropolitan Statistical Areas (MSA), census tracts, census block groups, and census block. The database contains information about these features such as their location in latitude and longitude, the name, the type of feature, address ranges for most streets, the geographic relationship to other features, and other related information. More information on the TIGER/Line file format and data product can be found on the U.S. Census web page at: http://www.census.gov/geo/maps-data/data/tiger.html. This web site contains detailed descriptions of the current TIGER/Line format, with an explanation of field meaning for each feature type.

Supported Elements

 

Typical File Extensions        

*.rt1, *.bw1

Automated Translation

Yes

User-Defined Attributes

Yes

Coordinate System Support

Yes

Generic Colour Support

Yes

Spatial Index

Never

Schema Required

N/A

Transaction Support

No

Geometry Type Attribute

tiger_type

Supported Geometry

 

Aggregate

No

Circles

No

Circular Arc

No

Elliptical Arc

No

Ellipses

No

Polygon

Yes

Donut Polygon

Yes

Point

Yes

Line

Yes

Text

No

Supported Versions:

1992, 1995, 1997, 1998, 1999, 2000, 2002

USGS SDTS (*catd.ddf)

SDTS is the USGS robust way of transferring Earth-referenced spatial data between dissimilar computer systems with the potential for no information loss. It is a transfer standard that embraces the philosophy of self-contained transfers, i.e. spatial data, attribute, georeferencing, data quality report, data dictionary, and other supporting metadata all included in the transfer. More info can be found at http://mcmcweb.er.usgs.gov/sdts. Files in the SDTS format will have the extension *.ddf.

A group of *.ddf files is normally identified by the catalog file, or *CATD.DDF file, which relates the files of a single SDTS transfer, and binds together all the files with a common prefix. Always select the SDTS file which ends in CATD, i.e. HP01CATD.DDF.

Supported Elements

 

Typical File Extensions        

*.ddf

Automated Translation

Yes

User-Defined Attributes

No

Coordinate System Support

Yes

Generic Colour Support

No

Spatial Index

Yes

Schema Required

N/A

Transaction Support

No

Geometry Type Attribute

sdts_type

Supported Geometry

 

Aggregate

No

Circles

No

Circular Arc

No

Elliptical Arc

No

Ellipses

No

Polygon

Yes

Donut Polygon

Yes

Point

Yes

Line

Yes

Text

No

Digital Line Graph (dlg, opt)

DLG is a fixed field record that may or may not have end of line markers. The DLG file structure was designed to accommodate all categories of spatial data represented on a conventional line map. DLG is a published ASCII format developed by the United States Geological Survey (USGS) Federal Agency and is intended to assist in data exchange with the National Digital Cartographic Data Base (NDCDB).

The DLG reader supports all three distinct types of DLG data:

 • Large-scale DLG data (1:24,000-scale)

 • Intermediate-scale DLG (1:100,000-scale)

 • Small-scale DLG data (1:2,000,000-scale)

The three scales of DLG data are physically formatted into files in one of these ways: standard, optional, and graphics formats. MAPublisher supports both the standard and the optional DLG distribution formats; however the graphics format is not supported. Most DLG data is distributed in the optional format. The DLG file structure was designed to accommodate all categories of spatial data represented on a conventional line map. Node, line, and area data types are present within the DLG format, along with linkages and attribute codes. Linkages are references to other features within the same DLG data set, used in a variety of contexts. DLG files do not explicitly store attribute values but use a feature coding approach in which unique feature codes are assigned to the different types of features stored within the data set. MAPublisher will look for the extension .dlg or .opt for the input DLG files.

Supported Elements

 

Typical File Extensions        

*.dlg, *.opt

Automated Translation

Yes

User-Defined Attributes

No

Coordinate System Support

Yes

Generic Colour Support

No

Spatial Index

Never

Schema Required

No

Geometry Type Attribute

dlg_type

Supported Geometry

 

Aggregate

No

Circles

No

Circular Arc

No

Elliptical Arc

No

Ellipses

No

Polygon

Yes

Donut Polygon

Yes

Point

Yes

Line

Yes

Text

No

Copyright © 1995-2020 Avenza Systems. All rights reserved.

 

Last updated: 11/30/2020