Sheet 1: Introduction

	
	
	

		
GeoMAPP Geospatial Data File Formats Reference Guide - Introduction (7/1/2011)
		
	

		
Electronic file format support is a fundamental challenge in the long-term preservation of digital materials. 
This issue is especially relevant for geospatial datasets that are created, shared, and 
stored in many different formats, many of which are proprietary to a specific vendor and/or 
software application.  Geospatial data is primarily comprised of raster data,  made up of a 
two dimensional array of equally sized cells where each cell holds a single attribute value and 
location coordinates, or vector data, represented as points,  lines, and polygons. In addition to 
the fundamental geographic information, many datasets also include underlying tables of 
data that further elaborate the geographic elements,  such as population counts, income values, 
average property values, demographic information, or identifying information  for individual 
features such as name, address, etc.  Then all of this data may further be wrapped within an 
encompassing database that enables relationships and analysis across the datasets. Many of the 
geospatial formats are manifested as numerous files in a variety of file types. All of these aspects 
pose challenges to GIS professionals and to archivists both today and in the future.
		

 
		
		
	

		


		
	

		
This spreadsheet provides a quick reference of some of the common geospatial raster and vector 
dataset types, and can serve as a tool to identify geospatial format types based on file extensions.  
The spreadsheet is organized into tabs with a Raster formats tab, a Vector formats tab, a Standards 
tab, and an additional Resources tab. For the raster and vector format tabs, the spreadsheet provides:
		
	

		
 - the file extension, and for multi-file formats a description of the format’s file composition,
		
	

		
 - a brief description,
		
	

		
 - a link to the format specification or standard - if available/applicable,
		
	

		
 - an assessment of the format’s currency - meaning is this a format this is generally in use today,
		
	

		
 - an assessment of the format’s prevalence - meaning how common is it to see this format,  
		
	

		
 - a sampling of tools available to access the file format
		
	

		
 - whether the format is supported by GDAL (for raster files) /OGR (for vector files) or Safe Software's
    Feature Manipulation Engine (FME).  These are tools that can read a large number of file formats,
    and may become more valuable to archivists especially as data formats obsolesce due to vendor
    viability and/or market demand.
		
	

		
 - sustainability issues
 - additional comments
		
Image Source: NOAA National Coastal Development Center. "Geographic Information Systems (GIS)." 
Retrieved 3/29/2011 from: 
http://www.ncddc.noaa.gov/technology/gis/view 
		
	

		
Important Scope Note:
		


		


		


		


		


	
	

		
The GeoMAPP Geospatial Data File formats Guide documents geospatial data storage formats that are most typically encountered in state government GIS and Archives operations. Data presentation and locator files like ESRI map documents (.mxd files) and layer files (.lyr) were not included since they do not directly store source GIS data. Similarly the guide also does not include emerging data/ map packaging files such as MPK or additional context files such as Arc Explorer (.nmf). Note: It is important for GIS and archives staffs to be aware of these file formats and understand their relationship to datasets that are being managed or preserved.  
		


		


	
	

		
Other geospatial data file formats with specific usage among the academic, federal government or commercial realms may also have been omitted due to lack of propagation within the extended 17 state GeoMAPP project partners.
		


		


		


		


		


	



Sheet 2: Raster

	
	
	
	
	
	
	
	
	
	
	

		
Raster Formats
		
File Composition
		
Description
		
Link to Format Standard/ Specification
		
Format Currency
		
Format Prevalence
		
Tools for Viewing Format
		
Supported GDAL
http://www.gdal.org/formats_list.html
		
Supported by Safe Software Feature Manipulation Engine (FME)
http://www.safe.com/fme/format-search/
		
Sustainability Issues
		
Comments
	
	

		
Raster files generally are used to store image information, such as scanned paper maps or scanned aerial photographs. They are also used for data captured by satellite and other airborne imaging systems. Images from these systems are often referred to as remote-sensing data. Unlike other raster files, which express resolution in terms of cell size and dots per inch (dpi), resolution in remotely sensed images is expressed in meters, which indicates the size of the ground area covered by each cell.
(http://data.geocomm.com/helpdesk/formats.html) 
		


		


		


		


		


		


		


		


	
	

		
ASPRS Lidar Data Exchange Format
		
File Extension:  *.las



		
Common LIDAR data exchange format. 

The LAS file format is a public file format for the interchange of LIDAR (Light Detection and Ranging) optical remote sensing data between vendors and customers.  
Reference:
http://www.asprs.org/a/society/committees/lidar/lidar_format.html  
		
LAS Specification Version 1.2 (Aproved by ASPRS Board 09/02/2008)
http://www.asprs.org/a/society/committees/standards/asprs_las_format_v12.pdf 
		
Current
		
Widely Used
 in optical remote sensing
		


		
Not listed
		
Yes
		


		


	
	

		
Arc Digitized Raster Graphic (ADRG) 
		
File Extension:

*.gen - general info file
*.qal - quality file
*.ovr - reduced resolution overview image file.
*.img - ADRG image files
*.sou - source graphic info file
*.lgg- legend image  file



		
ADRG are designed to provide a general purpose data set of support data and computer readable digital images of hardcopy graphic products. 

Each ADRG volume contains a header file, TRANSH01.THF, and a color test patch image file, TESTPA01.CPH. There will also be one or more Distribution Rectangle (DR) subdirectories. 

Each DR subdirectory contains a general information file, (*.GEN), a qualify file (*.QAL), and a reduced resolution overview image file (*.OVR). There will be one or more ADRG image files (*.IMG) and one or more source graphic subdirectories.

Each source graphic subdirectory contains a source graphic information file (*.SOU) and zero or more legend image files (*.Lgg - where gg is based on the naming conventions described in section 3.11.2.

MIL-A-89007 states ADRG is inactive for new design, and is no longer used, except to support existing systems.
		
U.S. Military Specification
MIL-A-89007

http://earth-info.nga.mil/publications/specs/printed/89007/89007_ADRG.pdf
		
Legacy
		
Largely in the Federal government in the military domain. 
		
ESRI Products such as the ArcGIS Military Analyst Suite of Tools (Raster Map Tool, etc.)
		

Creation-Yes
Georeferencing-Yes
Compiled by default-Yes


		
Yes
		
CADRG (Compressed ADRG file) achieves a nominal compression ratio of 55:1. Enhanced Compressed Raster Graphic (ECRG) uses JPEG 2000 compression using a compression ratio of 20:1
Commonly distributed on CD's, which would require a migration to new media for preservation. 
Library of Congress Sustainability Page: http://www.digitalpreservation.gov/formats/fdd/fdd000282.shtml
		
FMEpedia guidance: http://www.fmepedia.com/index.php/ARC_Digitized_Raster_Graphics_%28ADRG%29.  EROS guidance at http://eros.usgs.gov/#/Find_Data/Products_and_Data_Available/DRGs
	
	

		

"BIL, BIP, BSQ are three common methods for organizing image data for multiband images. They are not in themselves image formats but are schemes for storing the actual pixel values in a file."

They are generally produced by remote sensing systems (e.g. satellite, aerial imaging systems)

Various types of imagery are often distributed in simple binary formats such as the BIL (binary interleaved), BSQ (binary sequential), BIP (binary interleaved pixel), and RAW (PCI Geomatics raw binary) formats. These files are usually accompanied by a header file of some kind (usually .hdr, .ers, or .aux) which describes the layout and formatting of the file. Global Mapper requires this header file in addition to the .bil, .bsq, .bip, or .raw data file in order to load the file. 

The raster’s interleave specifies how the pixels and bands in a raster are arranged. Different interleaves allow you to arrange the data non-contiguously to optimize certain methods of access. Interleave is only relevant in multi-banded rasters; the cell values for rasters with one band are written sequentially. BIL data stores pixel information for separate bands within the same file, so that the user can choose to display just one specific band in a multi-band image. The BIL data organization can handle any number of bands, and thus accommodates black and white, grayscale, pseudocolor, true color, and multi-spectral image data. BILs and BSQs are raw data, so a separate text header file (.hdr) is required to indicate the rows, columns, bit depth, and other attributes. 
		


		


		


		


		


		


		


		
Description at:
http://mcmcweb.er.usgs.gov/drc/dlgv32pro/formats.html#40
	
	

		
Band Interleaved by Line (BIL)
		
File Extension:  *.bil, *.hdr

data file(.bil)
header file (.hdr)
		


A Band Interleaved by Line (BIL) image file is a simple uncompressed file containing the actual pixel values of a raster image. 
		
Not Applicable
		
Current
		
Widely Used
One of three methods for encoding image data for multiband raster images.
		
ArcGIS Engine Runtime Spatial Extension

MapInfo

Bentley ProjectWise

ESRI ArcMap Integration support for MXD, MXT, SHP, Personal GeoDatabase, BIL, and BIP

USGS Digital Data Viewer: dlgv32 Pro
http://mcmcweb.er.usgs.gov/drc/dlgv32pro/index.html
(ver 12.01 rls Jan 13, 2011)
		
Not on list

		


		
Because of the need for the ASCII header file, there can be a problem with sustainability.
Preservation Strategy:  Current practice is to store raster data in mosaics and in a Geodatabase raster catalog.
		
This is more of data format than a file format. Additional information at the USGS National Mapping Program Technical Instructions - Part 2 Specifications: Standards for Digital Orthophotos (12/1996):
http://rockyweb.cr.usgs.gov/nmpstds/acrodocs/doq/2DOQ1296.PDF 

More info at ArcGIS:
Description in ArcGIS 9.3 Desktop Help:
http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=BIL,_BIP,_and_BSQ_raster_files 

	
	

		
Band Interleaved by Pixel (BIP)
		
File Extension:  *.bip, *.hdr

data file (.bip)
header file (.hdr)- name of instrument and sensor which acquired the data
		
A Band Interleaved by Pixel (BIP) image file is a simple uncompressed file containing the actual pixel values of a raster image.  BIP is not in itself an image format, but is a scheme for storing the actual pixel values of an image in a file, and is one of the earliest methods of raster data organization based upon a pixel-consecutive scheme.

The raster’s interleave specifies how the pixels and bands in a raster are arranged. Different interleaves allow you to arrange the data non-contiguously to optimize certain methods of access. Interleave is only relevant in multi-banded rasters; the cell values for rasters with one band are written sequentially. BIP format provides optimal spectral processing performance. 
		
Not Applicable
		
Waning
		
Widely Used
One of three methods for encoding image data for multiband raster images.
		
USGS Digital Data Viewer: dlgv32 Pro
http://mcmcweb.er.usgs.gov/drc/dlgv32pro/index.html
(ver 12.01 rls Jan 13, 2011)
		
Not on list
		


		


		
This is more of data format than a file format. Further information in the USGS National Mapping Program Technical Instructions - Part 2 Specifications: Standards for Digital Orthophotos (12/1996):
http://rockyweb.cr.usgs.gov/nmpstds/acrodocs/doq/2DOQ1296.PDF 

More info at ArcGIS:
Description in ArcGIS 9.3 Desktop Help:
http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=BIL,_BIP,_and_BSQ_raster_files 

	
	

		
Band SeQuential Encoding (BSQ)
		
File Extension:  *.bsq, *.hdr

data file (.bsq)
header file (.hdr) - name of instrument and sensor which acquired the data
		
A BSQ image file is a simple uncompressed file containing the actual pixel values of a raster image. The raster’s interleave specifies how the pixels and bands in a raster are arranged. Different interleaves allow you to arrange the data non-contiguously to optimize certain methods of access. In this case, the banded data is stored in band-major order. That is, each image band appears consecutively in the data file. 

There are three ASCII text description files that can be provided with BSQ files: a header file (*.hdr) that describes the layout of the image pixel data and must be provided; a color file (*.clr) that describes the image color map; and a statistics file (*.stx) that describes image statistics for each band of the image. A BSQ file is a binary file and must have the file header to be interpreted properly by ArcGIS. 
		
Not Applicable
		
Current
		
Widely Used
One of three methods for encoding image data for multiband raster images. Frequently encountered, especially in domains dealing with satellite imagery. 
		
USGS Digital Data Viewer: dlgv32 Pro
http://mcmcweb.er.usgs.gov/drc/dlgv32pro/index.html
(ver 12.01 rls Jan 13, 2011)
		
Not on list
		


		
These are compressed imagery files 
Because of the need for the ASCII header file, there can be a problem with sustainability.

		
This is more of data format than a file format. Further information in the USGS National Mapping Program Technical Instructions - Part 2 Specifications: Standards for Digital Orthophotos (12/1996):
http://rockyweb.cr.usgs.gov/nmpstds/acrodocs/doq/2DOQ1296.PDF 

More info at ArcGIS:
Description in ArcGIS 9.3 Desktop Help:
http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=BIL,_BIP,_and_BSQ_raster_files 

	
	

		
Digital Orthophoto Quadrangle (DOQ)
		
Current Distribution Formats:
- Native USGS Format - BIL image with a keyword text header at the beginning of the file

- GeoTIFF Format - georeferenced TIFF file

References Include:
JPG with Native Header Format - a JPEG encoded image with an accompanying header file to provide metadata

See Comments column for reference on file naming conventions


		
A Digital Orthophoto Quadrangle (DOQ) is a computer-generated image of an aerial photograph in which the image displacement caused by terrain relief and camera tilt has been removed. The DOQ combines the image characteristics of the original photograph with the georeferenced qualities of a map. DOQs are available in both Native and GeoTIFF formats. Native format consists of an ASCII keyword header followed by a series of 8-bit binary image lines for B/W and 24-bit band-interleaved-by-pixel (BIP) for color. DOQs in native format are cast to the Universal Transverse Mercator (UTM) projection and referenced to either the North American Datum (NAD) of 1927 (NAD27) or the NAD of 1983 (NAD83). A DOQ can be used on-screen to collect, review, and revise other digital data, especially digital line graphs (DLG) and topographic maps. When the DOQ is combined with other digital products, such as digital raster graphics (DRG) or digital elevation models (DEM), the resulting image provides additional visual information for the extraction and revision of base cartographic information. 

A standard (USGS) DOQ is distributed in a quarter section of a standard 7.5-minute quadrangles.
		
USGS Orthophoto Standards:

http://rockyweb.cr.usgs.gov/nmpstds/doqstds.html
		
Current
		
Widely Used and Widely Distributed. 
		
USGS Earth Explorer: http://edcsns17.cr.usgs.gov/EarthExplorer/.  

Any mapping/design software capable of supporting world files e.g. ESRI ArcGIS, FME, Microstation, AutoDesk, etc.. 
		

First Generation USGS:
Creation-No
Georeferencing-Yes
Compiled by default-Yes

New Labelled USGS:
Creation-No
Georeferencing-Yes
Compiled by default-Yes


		
Yes
		
Library of Congress Sustainability information at http://www.digitalpreservation.gov:8081/formats/fdd/fdd000290.shtml. 

DOQs in native format need close management. 

GeoTIFFs have established management paths. 

About DOQ files - Native Format - Pree 1997 file
http://rockyweb.cr.usgs.gov/software/doqqppt/tsld009.html
		
USGS Digital Orthophoto Quadrangles Fact Sheet (2001) available at http://egsc.usgs.gov/isb/pubs/factsheets/fs05701.html

USGS Earth Resources Observation and Science (EROS) Center guidance at http://eros.usgs.gov/#/Find_Data/Products_and_Data_Available/DOQs

Other resources:
Using Digital Orthophoto Quadrangle (DOQ) Images
http://www.yale.edu/ceo/Documentation/doq.htm 

DOQ File Naming Conventions for CD-ROM Media
http://www.georgiaspatial.org/wp-content/frameworkdata/doqq-naming.htm

JPG description from:
http://www.globalmapper.com/product/formats_raster.htm

	
	

		
Enhanced Compression Wavelet (ECW)
		
File Extension:  *.ecw

Single File
		
ECW (Enhanced Compression Wavelet) is a proprietary wavelet compression image format optimized for geospatial imagery, which can quickly compress and decompress huge images, especially aerial and satellite imagery.  It was developed by Earth Resource Mapping, and is now owned by ERDAS, which is owned by Leica Geosystems. The requirement of using the ECWP format for any application is that it requires the user to download and install enabling software in the form of a plug-in or in the case of the Java applet, a Java runtime environment (JRE).
		
Not Available
Proprietary to ERDAS / Leica
		
Waning - supplanted by MrSID
		
Recently-low use
Older data (greater than a few years ago) was more commonly seen
		
Long list of tools available at http://en.wikipedia.org/wiki/ECW_%28file_format%29
		

Creation-Yes
Georeferencing-Yes
Compiled by default-No, needs ECW SDK


		
Yes
		
Lossy compression and proprietary nature of the format make for significant sustainability issues. 

Web Browser Access dependent upon  either:
- ECW JPEG 2000 plug-in or
- Java Applet that requires the Sun Java Runtime Environment (JRE)
		
For those with ECW 3.3 SDK from ERDAS - images less than 500MB may be compressed for free, while larger images require licensing from ERDAS. 
ECW 4.4 SDK from ERDAS only provides image decompression for free.
http://www.gdal.org/frmt_ecw.html 

Have seen from time to time at local government level - when an agency would have TIFF imagery and covert to ECW as opposed to MrSID.

In late 1990s-early 2000s offered better resolution and higher compression - used to deliver images for handheld devices. 
	
	

		
ERDAS Imagine
		
File Extension:  *.img
*.ige for images greater than 2GB

*.img - Single File
*.igw - World File
		
IMAGINE files are native propriety raster format image files created and used by the ERDAS IMAGINE software. IMAGINE files may contain additional information, such as statistics, ground control points, map information, and image metadata. They also support subsampled raster layers, called pyramid layers, for faster screen display within GIS applications. IMAGINE images use the ERDAS Hierarchal File Format (HFA) to store raster data. Note: ERDAS was acquired by Leica Geosystems.

Description available at:
http://home.gdal.org/projects/imagine/iau_docu0.pdf

		
Not Applicable
Proprietary
		
Current
		
Widely used amoung remote sensing (LIDAR, elevations). 
DEM bare earth models. 

Seen in a lot in academic and remote sensing shops, though datasets are dated from several years ago.
		
ERDAS IMAGINE
Geospatial Data Abstraction Library (GDAL)
http://www.gdal.org/ 

Global Mapper http://rmgsc.cr.usgs.gov/outgoing/ecosystems/USdata/

Imagine to GeoTIFF converter:
http://home.gdal.org/projects/imagine/hfa_index.html
		

Creation-Yes
Georeferencing-Yes
Compiled by default-Yes


		
Yes
		
Proprietary raster format that appears to have limited support from other vendors' tools could pose challenges into the extended future. 

Data will be compressed only when it is stored. ERDAS IMAGINE uses run-length compression.  IMAGINE automatically uncompresses data before the layer is run through a process.


		
Within past couple of years have seen as a dommon format to deliver LIDAR. Single file format is easier for transfer than Esri GRID's directory structure. One institution had 2008-2009 DEM bare earth models delivered delivered (prior bare earth models delivered in Esri GRID)

Leica Geosystems ERDAS IMAGINE Reader/Writer:
provides the FME engine with access to data in ERDAS IMAGINE format
http://www.safe.com/reader_writerPDF/erdas.pdf 

.img - Single File
uses Hierarchical File Format (HFA)
see: http://home.gdal.org/projects/imagine/iau_docu0.pdf for info.
	
	

		
ESRI ArcInfo ASCII Grid
		
File Extension:  *.asc

Single File
		
The ESRI ASCII Grid raster format can be used to transfer information to or from other cell-based or raster systems.  The ArcInfo ASCII Grid format is an ArcInfo GRID exchange file.

A grid defines geographic space as an array of equally sized square grid points arranged in rows and columns. Each grid point stores a numeric value that represents a geographic attribute (such as elevation or surface slope) for that unit of space. Each grid cell is referenced by its x,y coordinate location.
 
The ESRI ASCII Grid  has a very simple format. It has a short header that precedes the raster data which provides the location and size of the raster to follow. The raster is written as a series of rows, which contain one ASCII integer or floating point value per column in the raster.

There are two types of grids: integer and floating point. Integer grids are used to represent discrete data while floating-point grids represent continuous data. 


		
ASCII Grid file format is documented at:

http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/ESRI_ASCII_raster_format/009t0000000z000000/

http://webhelp.esri.com/arcgisdesktop/9.1/index.cfm?id=886&pid=885&topicname=ASCII%20to%20Raster%20(Conversion)

http://resources.esri.com/help/9.3/arcgisengine/java/GP_ToolRef/spatial_analyst_tools/esri_ascii_raster_format.htm


		
Current
		
Widely Used - especially as readable format and transfer file mechanism for ESRI ArcInfo Grid
		
Esri ArcGIS
		

Creation-Yes
Georeferencing-Yes
Compiled by default-Yes


		
Yes
		
ASCII format enables readability and accessibility to the data
		
Header:
<NCOLS xxx>
<NROWS xxx>
<XLLCENTER xxx | XLLCORNER xxx>
<YLLCENTER xxx | YLLCORNER xxx>
<CELLSIZE xxx>
{NODATA_VALUE xxx}
row 1
row 2
where xxx is a number and the keyword NODATA_VALUE is optional and defaults to -9999. Row 1 of the data is at the top of the raster, row 2 is just under row 1, and so on.
	
	

		
ESRI ArcInfo Grid


		
File Extension: 

Stored in an ArcInfo workspace.

Stored on file system as a separate directory with associated tables and files.

In an integer grid directory, the following tables and files are found:
-BND table, which stores the boundary of the grid; 
-HDR file, which stores specific information describing the grid, for example, cell resolution and blocking factor; 
-STA table, which contains statistics for the grid; 
VAT table, which stores the attribute data associated with the zones of the grid; 
-LOG, which monitors the activity that has occurred on the grid; and 
-TILE FILE w001001.adf (q0x1y1), which stores the cell data and 
-INDEX file w001001x.adf (q0x1y1x) that indexes the blocks in the tile and the LOG. 
(Some of these may not exist if created using ArcGIS operators, such as the LOG file.)
		
An ESRI ArcInfo Grid is a binary raster data storage format native to ESRI, widely used within ESRI programs, such as ArcGIS. 

A grid is stored in an ArcInfo workspace. The grid, like an ESRI coverage, is stored as a separate directory with associated tables and files that contain specific information about the grid.
		
Not Available
Proprietary
		
Current
		
Widely Used
		
Not widely supported outside of the Esri ArcGIS tools.  

Grid is an option for NED output from the USGS National Map Viewer.


		

Creation-Yes
Georeferencing-Yes
Compiled by default-Yes


		
Yes
		
Does not support compression 
(per ArcGIS Desktop 9.3 Help: Technical Specifications for raster dataset formats.

Grids use a reun-length raster compression scheme that is adaptive at the block level. 

Not widely supported outside ESRI tools. Multiple file components necessary to retain the understandability of the file. 
Library of Congress Sustainability information: http://www.digitalpreservation.gov:8081/formats/fdd/fdd000281.shtml
		
As with most formats, a grid should not be named with spaces or any other special characters in its name. A multiple-band grid cannot have more than 9 characters in its filename, and a single-band raster dataset cannot have more than 13 characters.

Narrative description of the ESRI Grid format is available at:
http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?id=3104&pid=3101&topicname=About_the_ESRI_Grid_format

To facilitate the transfer of the collection of files that make up an ArcInfo Grid dataset, export to ESRI ASCII Grid . Alternatively, you could zip the entire workspace, though this is not generally regarded as the best practice.
	
	

		
Esri File Geodatabase
		
File Geodatabases are stored as folders in a file system

Folder Name *.gdb Individual files include: .gdbindexes, .gdbtable, .gdbtablx, .freelist, .spx 


		
A collection of various types of GIS datasets held in a file system folder. This is the recommended native data format for ArcGIS stored and managed in a file system folder. File Geodatabases are stored as folders in a file system. Each dataset is held as a file that can scale up to 1 TB in size. This option is recommended over personal Geodatabases.
		
Proprietary,
File Geodatabase API expected in 2011
		
Current
		
Widely Used
		
Primary ArcGIS
		
Not listed
		
Yes
		
A proprietary data framework used for ESRI GIS software applications.
		
Preferred format over personal including increased filesize capacity, the ability to apply spatial indexes, supports compression, etc. 

Does not support versioned workflows.
	
	

		
GeoTiff
		
File Extension:  *.tif, *.tiff, *.tff

Single File that contains both image and geospatial metadata
		
GeoTIFF refers to TIFF files which have geographic (or cartographic) data embedded as tags within the TIFF file. The geographic data can then be used to position the image in the correct location and geometry on the screen of a geographic information display. GeoTIFF is a metadata format that provides geographic information to associate with the image data. But the TIFF file structure allows both the metadata and the image data to be encoded into the same file. GeoTIFF is an openly documented extension to TIFF 6.0.

GeoTIFF uses a small set of reserved TIFF tags to store a broad range of georeferencing information, catering to geographic as well as projected coordinate systems needs (e.g. latitude and longitude). Projections include UTM, US State Plane and National Grids, as well as the underlying projection types such as Transverse Mercator, Lambert Conformal Conic, etc. No information is stored in private structures, IFD's or other mechanisms which would hide information from naive TIFF reading software. GeoTIFF uses numerical codes to describe projection types, coordinate systems, datums, ellipsoids, etc. The projection, datums and ellipsoid codes are derived from the EPSG list compiled by the Petrotechnical Open Software Corporation (POSC), and mechanisms for adding further international projections, datums and ellipsoids has been established. The GeoTIFF information content is designed to be compatible with the data decomposition approach used by the National Spatial Data Infrastructure (NSDI) of the U.S. Federal Geographic Data Committee (FGDC).
		
GeoGIFF Format Specification Rev 1.0
open, public domain,          non-proprietary

http://landsathandbook.gsfc.nasa.gov/handbook/pdfs/geotiff_spec.pdf
		
Current
		
Widely used
		
Any GIS, CAD, Image Processing, Desktop Mapping and any other types of systems using geographic images can read any GeoTIFF files created on any system to the GeoTIFF specification.
		

Creation-Yes
Georeferencing-Yes
Compiled by default-Yes (internal libtiff and libgeotiff provided)


		
Yes
		
The GeoTIFF format is completely open, public domain and non-proprietary. Library of Congress sustainability information at http://www.digitalpreservation.gov/formats/fdd/fdd000279.shtml
		
Detailed information at http://trac.osgeo.org/geotiff/.  Microstation and/or DeCartes has history of issues with compressed TIFFs.
	
	

		
JPEG 2000
		
File Extension:  *.jp2, *.j2c, *.j2k, *.jpx

Single File


		

JPEG 2000 is an ISO-standard based image compression standard and coding system. It was created by the Joint Photographic Experts Group committee in 2000 as a newly designed, wavelet-based method of compression. The standardized filename extension is .jp2 for ISO/IEC 15444-1 conforming files and .jpx for the extended part-2 specifications, published as ISO/IEC 15444-2. It offers lossy and lossless compression, and world files (.j2w) can be used to georeference an image in GIS software. Compression ratios are similar to MrSID and ECW formats. 

		
International Standards Organization Standard

http://www.iso.org/iso/iso_catalogue/catalogue_ics/catalogue_detail_ics.htm?csnumber=27687
		
Current
		
Widely Used
		
List of applications available at http://en.wikipedia.org/wiki/JPEG_2000
		

Creation-Yes
Georeferencing-Yes
Compiled by default-No, needs libjasper


		
Yes
		
Until 2006 there was no standard way to geo-reference JPEG 2000 images. As the new GMLJP2 (http://www.ogcnetwork.net/gml-jp2) standard for georeferencing gains market share and support, JPEG 2000 will be reconsidered as a target format.
		


	
	

		
MrSID
		
File Extension:  *.sid, *.sdw

.sid - Single File
.sdw - World File
		
MrSID is an acronym that stands for Multiresolution Seamless Image Database. It is a wavelet-based file format developed and patented by LizardTech designed to enable portability of massive bit-mapped (raster) images, such as orthophotos. MrSID was originally developed for Geographic Information Systems (GIS). With this format, large raster image files such as aerial photographs or satellite imagery are compressed and can be quickly viewed without having to decompress the entire file. There is no open source implementation of the MrSID format. Some open source GIS systems can read MrSID files, including MapWindow GIS and those based on GDAL. The Decode Software Development Kit (SDK) is made available as a free download from developer.lizardtech.com. This enables the capability to implement MrSID reading capability in any application.
		
Proprietary
Not Available
		
Current
		
Widely Used
		
Most commercial GIS software packages can read MrSID files including those from GE Smallworld, ESRI, Intergraph, Bentley Systems, MapInfo, Safe Software, Autodesk, LizardTech with ERDAS IMAGINE being able to both read and write MrSID files.
		

Creation-No
Georeferencing-Yes
Compiled by default-No, needs MrSID SDK


		
Yes
		
Uses lossy compression.

Library of Congress Sustainability information at http://www.digitalpreservation.gov/formats/fdd/fdd000184.shtml
		


	
	

		
Raster Product Format (RPF)
		
File Extension:  *.rpf

Single File

		
The Raster Product Format (RPF) is a standard data structure developed in 1994 as a U.S. Military Standard for geospatial databases composed of rectangular arrays of pixel values (e.g. in digitized maps or images) in compressed or uncompressed form. RPF is intended to enable application software to use the data in RPF format on computer readable interchange media directly without further manipulations or transformation. RPF is intended to define a common format for interchange of raster data between producers of such data in DoD such as The Military Departments, Office of the Secretary of Defense, Organizations of the Joint Chiefs of Staff, and the Defense Agencies of the Department of Defense (collectively known as DoD components) and users of the data, to help facilitate interoperability among mission-critical systems. RPF is a general, adaptable format to encompass raster products in compressed or uncompressed form such as: (1) non-polar and polar raster maps transformed from DMA's ARC Digitized Raster Graphics (ADRG) maps, as specified in MIL-A-89007;_and (2) imagery transformed from ARC Digital Raster Imagery (ADRI), as specified in MIL-A-89027.
		
Department of Defense Military Standard

http://jitc.fhu.disa.mil/nitf/tag_reg/docs/ms2411.pdf
		
Waning
		
Largely in the Federal government in the military domain. 
		
ESRI - import only
ERDAS-import & export
		

Creation-No
Georeferencing-Yes
Compiled by default-Yes


		


		
Difficult to convert. ESRI software can read the format, but can't write it to another format. Library of Congress Sustainability page: http://www.digitalpreservation.gov/formats/fdd/fdd000298.shtml
		


	
	

		
USGS Digital Elevation Model (DEM)
		
File Extension:  *.dem

Single File


		
The USGS Digital Elevation Model (DEM) data files are self-contained (single file) sets of ASCII-encoded (text) digital representations of cartographic information in a raster form. DEMs consist of a sampled array of elevations for a number of ground positions at regularly spaced intervals. These digital cartographic/geographic data files are produced by the U.S. Geological Survey (USGS) as part of the National Mapping Program. The USGS produces five different digital elevation products. Although all are identical in the manner the data are structured, each varies in sampling interval, geographic reference system, areas of coverage, and accuracy; with the primary differing characteristic being the spacing, or sampling interval, of the data. DEM's are used in the generation of three-dimensional graphics displaying terrain slope, aspect (direction of slope), and terrain profiles between selected points. It is an open standard, and is used throughout the world. It has been superseded by the USGS's own SDTS format but the format remains popular due to large numbers of legacy files, self-containment, relatively simple field structure and broad, mature software support.
		
USGS Digital Elevation Model Standards

http://rockyweb.cr.usgs.gov/nmpstds/demstds.html
		
Legacy
		
Common as a legacy format in the Federal government
		
USGS Digital Data Viewer: dlgv32 Pro
http://mcmcweb.er.usgs.gov/drc/dlgv32pro/index.html
(ver 12.01 rls Jan 13, 2011)

An unauthorized collection of tools to view DEM:
http://www2.cs.uh.edu/~somalley/DemTutorial/#PROGRAMS
		

Creation-Yes
Georeferencing-Yes
Compiled by default-Yes


		
Yes
		
Openly documented but falling into disuse. Uptake of the SDTS has been slow to non-existant. 
		
EROS DEM Guidelines (http://eros.usgs.gov/#/Guides/dem)
	
	

		
USGS Digital Raster Graphic (DRG)
		
File Extension: *.tif

Often a single digital image file usually saved as a .tif

3 Files:
*.tif - TIFF Image
*.txt, *fgd - Metadata file
*.tfw - Arc/Info World file (optional)




		
A digital raster graphic (DRG) is a scanned image of a U.S. Geological Survey (USGS) standard series topographic map, scanned, digitized and georeferenced. 

The USGS DRG consists of three physical files: the TIFF image, a text file of metadata along with a non-required third file, an Arc/Info world file. The DRG image (*.tif), world (*.tfw), and metadata (*.fgd) files incorporate an intelligent data set name (DSN) consisting of descriptive metadata wrapped around a standardized kernel that describes the spatial location of the file. 

Digital Raster Graphics (DRGs) are scanned, digitized and georeferenced USGS topographic maps at 1:24,000, 1:100,00 and 1:250,000 scale. DRGs are in TIFF format (using the GeoTIFF specifications) and are scanned at a minimum resolution of 250 dots per inch.  The digital image is georeferenced to the true ground coordinates of the 2.5-minute grid ticks and projected to the Universal Transverse Mercator (UTM) for projection consistency with USGS Digital Orthophoto Quadrangles (DOQs) and Digital Line Graphs (DLGs). DRGs have been made for all quadrangles in the USGS standard topographic map series for the United States, its territories and trusts. Although the original data program was completed in 1998, the USGS has continued to make new DRGs for to replace data found to contain errors and to make new DRGs of revised maps. About 1,000 replacement and new version DRGs per year have been produced since the completion of the original data program. DRGs are useful as backdrops onto which other digital data can be overlaid. At the USGS, DRGs are used for collecting and validating DLGs. The DRG can help assess the completeness of digital data from other mapping agencies. It can also be used to produce "hybrid" products. These include combined DRGs and DOQs for revising and collecting digital data and combined DRGs and digital elevation models for creating shaded-relief maps.
		
USGS Digital Raster Graphic Standards

http://rockyweb.cr.usgs.gov/nmpstds/drgstds.html 
		
Waning
		
USGS created DRGs for all States, but these are being replaced by the US TOPO maps (http://nationalmap.gov/ustopo/)
		
Most commercial GIS software packages can read image files including world files including those from GE Smallworld, ESRI, Intergraph, Bentley Systems, MapInfo, Safe Software, Autodesk, ERDAS IMAGINE
		
Not on list
		
Yes
		
DRGs created by USGS are typically scanned at 250 dpi and saved as a TIFF.
http://en.wikipedia.org/wiki/Digital_raster_graphic 

DRGs are typically found as *.tif or *.jpg files.  http://services.arcgisonline.com/arcgis/services
		
USGS GeoData Digital Raster Graphics Fact Sheet (2001)
http://egsc.usgs.gov/isb/pubs/factsheets/fs08801.html 

For an example DRGs see

Kent County Delaware DRGs/DLGs
http://www.rdms.udel.edu/drgdlg/dg_kc.html

NCSU guidance at http://www.lib.ncsu.edu/gis/drg.html
	
	

		
World File
		
File Extension: *.xxw

e.g. 
TIFF World File: *.tfw
JPEG World File: *.jgw
PNG World File: *.pgw
Bitmap World File: *.bpw
		
A world file is a plain text computer data file used by geographic information systems to georeference raster map images, which may be produced in several of the basic image formats. The file specification was introduced by Esri. World files establish an image-to-world transformation that converts the image coordinates in raster data to real-world coordinates, where each cell in the image has a row and column number.  Some image formats will store their georeferencing information in a separate file, rather than in the header. World Files do not specify a coordinate system, but contain six-line files that provide the georeferencing information.
		
Proprietary
		
Current
		
MrSID
ERDAS Imagine
		


		
Not on list
		


		
Seen success in moving image files with associated world files across versions and (GIS) platforms
		
Description at:

http://webhelp.esri.com/arcgiSDEsktop/9.3/index.cfm?TopicName=World_files_for_raster_datasets

http://webhelp.esri.com/arcims/9.2/general/topics/author_world_files.htm 

http://en.wikipedia.org/wiki/World_file

Esri provides a Raster World File export tool to create a world file based on the geographic information in a raster dataset.
http://webhelp.esri.com/arcgiSDEsktop/9.3/index.cfm?TopicName=Export_Raster_World_File_%28Data_Management%29
	
	

		


		


		


		


		


		


		


		


		


		


		


	
	

		


		


		


		
URLs were active as of        2011 Mar 4
		
Emerging
		
Widely Used
		


		


		
Yes
		


		


	
	

		


		


		


		


		
Current
		
Moderate Use
		


		


		
No
		


		


	
	

		


		


		


		


		
Waning
		
Niche Use
		


		


		


		


		


	
	

		


		


		


		


		
Legacy
		
*** Qualified by use in state govt context (e.g. widely used in Industry, but uncommon in State Govt)
		


		


		


		


		


	



Sheet 3: Vector

	
	
	
	
	
	
	
	
	
	
	

		
Vector Formats
		
File Composition
		
Description
		
Link to Format Standard/ Specification
		
Format Currency
		
Format Prevalence
		
Tools for Viewing Format
		
Supported by OGR
http://www.gdal.org/ogr/ogr_formats.html
		
Supported by Safe Software Feature Manipulation Engine (FME)
http://www.safe.com/fme/format-search/
		
Sustainability Issues
		
Comments

	
	

		
Vector datasets are based on the interaction between arcs and nodes, represented as points, lines, and polygons A point is a single node, a line is two nodes with an arc between them, and a polygon is a closed group of three or more arcs. With these three elements, it is possible to record most all necessary  information. Vector data is useful for modeling discrete physical features
(http://www.umich.edu/~ipcaa/GIS/General%20GIS%20Concepts.htm) 
(http://www.mass.gov/mgis/GIS_Glossary.pdf)
		


		


		


		


		


		


		


		


	
	

		
Autodesk Drawing eXchange Format
		
File Extension: *.dxf 

		
AutoCAD DXF (Drawing Interchange Format, or) is a CAD data file format developed by Autodesk for enabling data interoperability between AutoCAD and other programs. Versions of AutoCAD from Release 10 (October 1988) and up support both ASCII and binary forms of DXF. Earlier versions support only ASCII. 

		
Proprietary, Published

AutoDesk DXF Reference
http://usa.autodesk.com/adsk/servlet/item?siteID=123112&id=12272454&linkID=10809853   
		
Waning
		
Niche use
		
A long list of tools that can view DXF files can be found here: http://en.wikipedia.org/wiki/AutoCAD_DXF#Software_that_supports_DXF  
		

Creation-No
Georeferencing-Yes
Compiled by default-Yes


		
Yes
		
As AutoCAD has become more powerful, supporting more complex object types, DXF has become less useful.

		


	
	

		
Autodesk Drawing File
		
File Extension: *.dwg
		
DWG ("drawing") is a file format used for storing two and three dimensional design data and metadata. It is the native format for several CAD packages including AutoCAD, IntelliCAD (and its variants) and Caddie. In addition, DWG is supported non-natively by many other CAD applications
		
Proprietary, 
Not Available
		
Current
		
Widely used in CAD(Architecture, Engineering, Design) Industries. Minimal use in traditional geospatial shops
		
Autodesk offers a free DWG viewer: DWG TrueView
http://usa.autodesk.com/adsk/servlet/pc/index?siteID=123112&id=15314320

ArcGIS Products ; AutoCad ; Other Viewers:  http://usa.autodesk.com/adsk/servlet/pc/index?id=15409188&siteID=123112 ;  http://usa.autodesk.com/adsk/servlet/pc/index?id=6703438&siteID=123112; http://www.autodesk.co.uk/adsk/servlet/index?siteID=452932&id=8992673 ; 
		
Not listed
		
Yes
		


		
Third party viewers not including AutoCad should understand dwg design specifications that would limit viewing of certain dwg elements such as unexploded blocks, custom fonts, etc…  

	
	

		
Bentley
Microstation Design File
		
File Extension:  *.dgn
		
DGN is the name used for CAD file formats supported by Bentley Systems' MicroStation and Intergraph's Interactive Graphics Design System (IGDS) CAD programs.
		
Proprietary

Microstation V8 File Format Reference for the native DGN file format is available upon request at: 
http://www.bentley.com/en-GB/Products/MicroStation/OpenDGN/
		
Current
		
Widely Used
		
ArcGIS Products, Bentley Microstaton, Bentley Viewer, AutoCad, etc.
		

Creation-Yes
Georeferencing-No
Compiled by default-Yes


		
Yes
		


		


	
	

		
Digital Line Graph (DLG)
Digital Line Graph Optional (DLG-OPT)
		
File Extension:  *.dlg, *.dlg3, *.opt
digital vector data

Appears to be distributed later in a wide variety of formats: .e00, shp, USGS .dd file (DLG standard),  USGS .do file (DLG option)


		
A Digital Line Graph (DLG) is digital vector data representing cartographic information derived from USGS maps and related soruces. DLGs contain a wide variety of information depicting geographic features (for example, hypsography, hydrography, boundaries, roads, utility lines, etc). DLGs are derived from hypsographic data (contour lines) using USGS 7.5-minute, 15-minute, 2-arc-second (30- by 60-minute), and 1:2 million-scale topographic quadrangle maps. Large-, intermediate-, and small-scale DLG data are useful for the production of cartographic products (e.g., base maps). Also, the data are structured to support (GIS) technologies. A typical use of base category digital cartographic data is to combine them with other geographically referenced data.

Nine different categories of features, or layers, are available in DLGs: Public Land Survey System, Boundaries, Transportation, Hydrography, Hypsography, Non-vegetative features, survey control and markers, man-made features, and Vegetative surface cover. 

DLGs are available in two different formats: optional format, a simple-to-use format that incorporates an 80-byte logical record length, the UTM ground coordinate system, and topology linkages contained in line, node and area elements; and Spatial Data Transfer Standard (SDTS) format, a format that facilitates transferring of spatial data between different computer systems.
Source: http://en.wikipedia.org/wiki/Digital_line_graph 
		
Digital Line Graph Standards:
http://rockyweb.cr.usgs.gov/nmpstds/dlgstds.html

USGS US GeoData Digital Line Graphs Fact Sheet:
http://egsc.usgs.gov/isb/pubs/factsheets/fs07896.html

http://egsc.usgs.gov/isb/pubs/factsheets/fs07896t.pdf
		
Current
		
USGS topographic maps
		
USGS Digital Data Viewer: dlgv32 Pro
http://mcmcweb.er.usgs.gov/drc/dlgv32pro/index.html
(ver 12.01 rls Jan 13, 2011)
		
Not on list
		
Yes
		
The LULC and Native format DEM and DLG data do not contain record delimiters. Some commercial software requires that delimiters be added. In some cases, you will need to add delimiters before using display programs. USGS Windows 95 viewing software (DLGV32) will display the data correctly with or without record delimiters. SDTS formatted data does not require delimiters.
Source: http://edc2.usgs.gov/geodata/public.php

USGS Global Mapper will not display DLG-S data, an older format that is no longer sold or supported. Most USGS DLG-Optional data do not contain record delimeters. Global Maper does not require that delimiters be added, and will display with DLG-O data with or without delimiters.
		
USGS Earth Resources Observation and Science (EROS) Center guidance at http://eros.usgs.gov/#/Guides/dlg 

Example DLGs can be found:
Kent County Delaware DRGs/DLGs
http://www.rdms.udel.edu/drgdlg/dg_kc.html

Much of the Digital Line Graph vector map data produced by U.S. Geological Survey has been converted to SDTS format (http://www.microimages.com/documentation/Tutorials/import.pdf)


	
	

		
Esri ArcInfo Coverage
		
Coverages are organized as a topical directory structure within a Esri feature class.


		
A coverage is ESRI's core data model.  A coverage is a georelational data model that stores vector data only.  Coverages use a set of feature classes to represent geographic features. Each feature class stores a set of points, lines (arcs), polygons, or annotation (text). Coverages can have topology, which determines the relationships between features.  A coverage is stored as a directory within which each feature class is stored as a set of files.

http://webhelp.esri.com/arcgisdesktop/9.2/index.cfm?TopicName=How_coverages_are_stored
		
Proprietary,
Not Available
		
Legacy
		
Widely Used
		
ArcGIS Workstation
		

Creation-No
Georeferencing-Yes
Compiled by default-Yes


		
Yes
		

Creating/Editing coverages requires ArcInfo Workstation license
(source: ArcGIS Desktop 10 online help Coverage toolbox licensing)

Desktop v 10
Esri Conversion Toolbox offers tools to convert Coverages to & from various other formats (e.g. DLG, SDTS, etc.)

Older datasets are seen to be retained in original coverage formats, rather than being converted.  Successful conversion of coverage to shapefile & file / personal geodbs has been experienced.




		
Desktop 10 ArcGIS Resource Center: Coverages
Professional Library -> Data Management -> Geographic data types -> Coverages
http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html 

Esri description of how coverages are stored is documented at:

http://webhelp.esri.com/arcgisdesktop/9.2/index.cfm?TopicName=How_coverages_are_stored

An example directory structure for a Coverage.

=>National park Coverages
 ->roads (coverage)
 ->streams (coverage)
    -> annotation (feat class)
    -> arc (feature class)
    -> tic (feature class)

	
	

		
Esri File Geodatabase
		
File Geodatabases are stored as folders in a file system

Folder Name *.gdb Individual files include: .gdbindexes, .gdbtable, .gdbtablx, .freelist, .spx 


		
A collection of various types of GIS datasets held in a file system folder. This is the recommended native data format for ArcGIS stored and managed in a file system folder. File Geodatabases are stored as folders in a file system. Each dataset is held as a file that can scale up to 1 TB in size. This option is recommended over personal Geodatabases.
		
Proprietary,
File Geodatabase API expected in 2011
		
Current
		
Frequently
		
Primary ArcGIS
		
Not listed
		
Yes
		
A proprietary data framework used for ESRI GIS software applications.
		
Preferred format over personal including increased filesize capacity, the ability to apply spatial indexes, supports compression, etc. 

Does not support versioned workflows.
	
	

		
Esri ArcInfo Interchange File (E00)
		
File Extension:  *.e00
		
ArcInfo Interchange File Format is a vector file format which is produced by ESRI and pre-dates the shapefile. It is as an export file used to enable coverage, grid or TIN and an associated INFO table to be transferred between different machines, which are not connected by any type of file sharing network. A volume has the extension .E00 through .E99.
		
Specification is proprietary and unpublished by ESRI

A non-authoritative version of the specification can be found at:

      http://avce00.maptools.org/docs/v7_e00_cover.html
		
Legacy
		
Widely Used
		
Not a viewable format.  Exported files (*.e00) are imported to ARCINFO coverage format through ArcGIS Toolbox or command line ARCINFO.
		

Creation-No
Georeferencing-Yes
Compiled by default-Yes


		
Yes
		
 .e00 is an Esri-proprietary format, and you should make any transformations for this format using Esri tools. Any *.e00 files or coverages should be converted to either Esri feature classes or Esri shapefiles. 
		
Use of zip compression will result in file corruption.  Also, knowledge of the coverage workspace is critical for data management and portability.
(source: ArcGIS Desktop 9.3 Help) 
	
	

		
Esri Personal Geodatabase
		
File Extension:  .mdb
  
Single file
Geodatabases are stored and managed in Microsoft Access data files
		
This is the original data format for ArcGIS Geodatabases stored and managed in Microsoft Access data files 
This is limited in size and tied to the Windows operating system. All datasets are stored within a Microsoft Access data file, which is limited in size to 2 GB.

The storage size of personal geodatabases are effectively limited to between 250 and 500 MB for the entire geodatabase. 
		
Proprietary,
Not Available
		
Waning
		
Frequently
		
Primary ArcGIS
		

Creation-No
Georeferencing-Yes
Compiled by default-No, needs ODBC library


		
Yes
		
A proprietary data framework used for ESRI GIS software applications.

		
See comments above with Esri File Geodatabase to understand limitations.

The ArcSDE Geodatabase System Tables entity relationship diagram is available at:

http://help.arcgis.com/en/arcgisdesktop/10.0/help/0029/pdf/sdesystables_diagram.pdf
	
	

		
Esri Shapefile
		
Can or should contain up to 7 files
Mandatory files to store the core data :
    * .shp — shape format; the feature geometry itself
    * .shx — shape index format; a positional index of the feature geometry to allow seeking forwards and backwards quickly
    * .dbf — attribute format; columnar attributes for each shape, in dBase IV format

Optional files :
    * .prj — projection format; the coordinate system and projection information, a plain text file describing the projection (used by ARC-GIS)
    * .sbn and .sbx — a spatial index of the features
    * .fbn and .fbx — a spatial index of the features for shapefiles that are read-only
    * .ain and .aih — an attribute index of the active fields in a table or a theme's attribute table
    * .ixs — a geocoding index for read-write shapefiles
    * .mxs — a geocoding index for read-write shapefiles (ODB format)
    * .atx — an attribute index for the .dbf file in the form of shapefile.columnname.atx (ArcGIS 8 and later)
    * .shp.xml — metadata in XML format
    * .cpg — used to specify the code page (only for .dbf) for identifying the character encoding to be used
		
Shapefiles are a simple, nontopological format for storing the geometric location and attribute information of geographic features. The geometry for a feature is stored as a shape comprising a set of vector coordinates. Shapefiles can support point, line, and area features. An Esri shapefile consists of a main file, an index file, and a dBASE table.


		
Proprietary, Documented
 
ESRI Shapefile Technical Description whitepaper at:  http://www.esri.com/library/whitepapers/pdfs/shapefile.pdf

http://en.wikipedia.org/wiki/index.html?curid=2770513 


		
Current
		
Frequently
		
ESRI offers a free shapefile viewer: 
DWG TrueView
http://usa.autodesk.com/adsk/servlet/pc/index?siteID=123112&id=15314320

Primarily ArcGIS however is an openly documented published specification.

Compatible with hydraulic modeling, GPS, GeoMedia, Google Earth Pro, etc
		

Creation-Yes
Georeferencing-Yes
Compiled by default-Yes

		
Yes
		
Shapefiles are complex file sets with up to 7 files.  All of the files need to be kept together to properly read the file. 

Shapefiles are an openly documented, published specification. As such, they are a stable file format for preservation and data exchange. 

Relationships are not maintained when shapefiles are exported from file geodatabases. 
		


	
	

		
GeoPDF
		
File Extension:  *.pdf
		
Map and imagery products created by TerraGo software applications. GeoPDF products use geospatial PDF as a container for maps, imagery, and other data used to deliver an enhanced user experience in TerraGo applications. However, GeoPDF products conform to published specifications including both the OGC best practice for PDF georegistration as well as Adobe's proposed geospatial extensions to ISO 32000
		
Open Geospatial Consortium (OGC)

http://www.opengeospatial.org/standards/bp
		
Current
		
In use in Federal Government/ DoD for past 5+ years
		
Adobe Acrobat, Adobe Reader, Global Mapper, and various TerraGo Tools
		
Not listed
		
No
		



		


	
	

		
Geospatial PDF
		
File Extension:  *.pdf
		
Geospatial PDF refers to geospatial extensions to the Portable Document Format (PDF) that relate a region on a PDF document page to a georeferenced region in physical space. The georeferencing metadata for geospatial PDF is most commonly encoded in one of two ways: the OGC best practice and as Adobe's proposed geospatial extensions to ISO 32000. Features include: the ability to graphically represent vector and raster information, the separation of graphics content into different layers , and the association of tabular information with graphical features 


		
International Standards Organization ISO 32000-1:2008

http://www.iso.org/iso/catalogue_detail.htm?csnumber=51502
		
Current
		
Frequently
		
Adobe Acrobat 9.X, Adobe Reader 9.X, Avenza PDF Maps for Apple iOS, Global Mapper, Geospatial Data Abstraction Library (GDAL), various TerraGo Tools
		
Not listed
		
Yes
		


		


	
	

		
Intergraph GeoMedia
		
File Extension: *.mdb, *.mge

Dataset comprised of single file
		
GeoMedia is a suite of GIS editing tools created by Intergraph. GeoMedia can read/export feature classes into a variety of formats including the proprietary Modular GIS Environment (.mge) and GeoMedia Warehouse (.mdb) (based on MS Access, SQL Server, or Oracle Spatial)
		
Proprietary,
Not Available
		
Current
		
Industry specific use in areas such as Utilities and e-911
		
Intergraph GeoMedia
		

Geomedia .mdb
Creation-No
Georeferencing-No
Compiled by default-No, needs ODBC library


		
Yes
		


		


	
	

		
Keyhole Markup Language (KML)
		
File Extension: *.kml, *.kmz

Contains several files:
		
KML is an Open Geospatial Consortium (OGC) sponsored xml schema file format used to display geographic data in an earth browser, such as Google Earth, Google Maps, and Google Maps for mobile. A KML file is processed in much the same way that HTML (and XML) files are processed by web browsers. Like HTML, KML has a tag-based structure with names and attributes used for specific display purposes. Thus, Google Earth and Maps act as browsers for KML files.
		
Open Geospatial Consortium (OGC)

http://www.opengeospatial.org/standards/kml
		
Current
		
Increasing use for map/ geospatial data creation in non GIS shops

Increasing use for mass market delivery of geospatial delivery
		
Google Earth, 
Marble
		

Creation-Yes
Georeferencing-Yes
Compiled by default-Yes (read support needs libexpat)

		
Yes
		


		
Open Standard for all geobrowsers, became official standard of the OGC, April 14, 2008 http://www.opengeospatial.org/standards/kml

Google Earth and Google Maps act as browsers for KML files.

Seen increase in state/local/federal use of KML to push out versions of their geodata
	
	

		
MapInfo Interchange Format
		
File Extension: .mif, .mid
		
MapInfo Interchange File format is an ASCII text file format that fully describes the contents of a MapInfo table. MIF consists of two related files: one for the graphical data, and one for the tabular data. The graphical data is in a file with a .mif extension, and the tabular data is in a file with a .mid extension. MIF files can be read and written by MapInfo Professional and translated into other formats with other programs. 

MapInfo is now Pitney Bowes Business Insight
		
Non-authoritative source, not published by MapInfo (now PitneyBowes):

http://www.gissky.com/Download/Download/DataFormat/Mapinfo_Mif.pdf   (October 1999)

		
Waning
		
Unknown
		
MapInfo Professional, GeoMedia, ArcGIS
		

MapInfo File
Creation-Yes
Georeferencing-Yes
Compiled by default-Yes

		
Yes
		


		


	
	

		
MapInfo TAB
		
File Extension:  *.tab, *dat, *.id, *.map

According to Wikipedia, two files. 

A minimum of two files are required for the tab format--.dat and .tab

From Wikipedia, four files, the *.DAT, *.TAB, *.ID and *.MAP
		
MapInfo Table (*.tab) TAB is a proprietary geo-spatial 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.
		
Proprietary
Not Available

		
Current
		
Niche use
		
ArcGIS Products 
		
Not listed
		
Yes
		
This is a proprietary format, but it can be exported to ESRI file types using the data interoperability extension.
		


	
	

		
Scalable Vector Graphics
		
File Extension:  *.svg
		
Scalable Vector Graphics (SVG) is a family of specifications of an XML-based file format for describing two-dimensional vector graphics, both static and dynamic (i.e. interactive or animated).
The SVG specification is an open standard that has been under development by the World Wide Web Consortium (W3C) since 1999.
SVG images and their behaviors are defined in XML text files. This means that they can be searched, indexed, scripted and, if required, compressed. Since they are XML files, SVG images can be created and edited with any text editor, but specialized SVG-based drawing programs are also available.
		
W3C

SVG1.2 (Apr 2005) http://www.w3.org/TR/SVG12/

SVG2 is currently under development per W3C
		
Current
		
used mostly as a network payload (e.g. for applications like Polymaps)
		
Per Wikipedia:
All major modern web browsers except MS Internet Explorer support and render SVG markup directly. IE 9 Beta supports the basic SVG feature set.

Long list of applications that support SVG available in Wikipedia entry.
		
not listed
		
Yes
		


		
Other "network payload" formats include: WFS, WCS, domain-specific GML
	
	

		
Topologically Integrated Geographic Encoding and Referencing Files (TIGER)
		
Prior to 2008, published as custom text-based format (TIGER/Line). 

Beginning in 2008, the Census published TIGER line files as shapefiles. 

(See Esri Shapefile description above)
		
Topologically Integrated Geographic Encoding and Referencing, or TIGER, or TIGER/Line is a format used by the United States Census Bureau to describe land attributes such as roads, buildings, rivers, and lakes, as well as areas such as census tracts. TIGER was developed to support and improve the Bureau's process of taking the Decennial Census. The TIGER files do not contain the census demographic data, but merely the map data. GIS can be used to merge census demographics or other data sources with the TIGER files to create maps and conduct analysis. TIGER data is available without cost due to the requirement for U.S. Government publications to be released into the public domain.
		
2010 TIGER/Line Shapefile Descriptions:
http://www.census.gov/geo/www/tiger/tgrshp2010/documentation.html

Previous Versions of TIGER/Line Files Technical Description
http://www.census.gov/geo/www/tiger/oldtechdoc/tgrlinedoc.html

TIGER/Line 1992
http://www.census.gov/geo/www/tiger/t92top.html 
		
Current
		
Widely Used
		
Primarily Esri ArcGIS, but supported by any software that can read shapefiles (after 2008)
		

Creation-No
Georeferencing-Yes
Compiled by default-Yes


		
Yes
		


		
The positional accuracy varies with the source materials used, but at best meets the established National Map Accuracy standards (approximately +/- 167 feet) where 1:100,000-scale maps from the USGS are the source.

TIGER Information Page:
http://www.census.gov/geo/www/tiger/
	
	

		
Vector Product Format
		
File Extension:  *.vpf
		
Vector Product Format (VPF) is a military standard for vector-based digital map products produced by the U.S. Department of Defense (DOD).  The two primary standards are the VMAP Vector World Map formerly known as Digital Chart of the World-DCW and Digital Nautical Chart (DNC) Description: Digital Nautical Chart is a Vector Product Format (VPF) based database containing maritime features of digitally replicated Nautical Charts derived from the National Geospatial-Intelligence Agency.

		
U.S. Department of Defense Military Standard
MIL-STD-2407

http://earth-info.nga.mil/publications/specs/printed/VPF/vpf.html
		
Unknown

Spec is dated 28 June 1996>
1997 ESRI User Conf proceedings - ArcView Viewer extension

maybe not current -- but there may be numerous "artifactual" assets still in this format
		
Used predominately within federal government/ DoD
		
Esri  ArcView
		

Creation-No
Georeferencing-Yes
Compiled by default-No, needs OGDI library


		
Yes
		


		
The National Imagery and Mapping Agency (NIMA) produces its vector digital map products in this format (1997 Esri User Conference Proceedings: "The VPF Viewer Extension for ArcView")
	
	

		


		


		


		


		


		


		


		


		


		


		


	
	

		


		


		


		


		


		


		


		


		


		


		


	
	

		


		


		


		


		


		


		


		


		


		


		


	
	

		


		


		


		
URLs were active as of  2011 Mar 4
		
Emerging
		
Widely Used
		


		


		


		


		


	
	

		


		


		


		


		
Current
		
Moderate Use
		


		


		


		


		


	
	

		


		


		


		


		
Waning
		
Niche Use
		


		


		


		


		


	
	

		


		


		


		


		
Legacy
		
*** Qualified by use in state govt context (e.g. widely used in Industry, but uncommon in State Govt)