|Introduction | Sustainability Factors | Content Categories | Format Descriptions | Contact|
|Full name||GeoPDF (TerraGo) Encoding, Version 2.2|
GeoPDF (a registered trademark of TerraGo Technologies) defines an encoding of georegistration information that allows association of an arbitrary coordinate reference system to an illustration on a page of a PDF document. GeoPDF is specified as an extension to Adobe PDF, as described in PDF Reference 1.7. This encoding supports the functionality in the GeoPDF Toolbar and other TerraGo products designed to "deliver complex maps and images from the desks of a few technical experts to the hands of many field operators in a simple to use format." The specification of version 2.2 of this encoding was published in 2007 by the Open Geospatial Consortium (OGC) as OGC 08-139.
To quote from the OGC Best Practice document, "Conceptually, GeoPDF® specifies map frames associated with a PDF page. A minimal map frame describes a coordinate reference system that is associated with the entire document page. This association provides a collection of tuples that map the page (PDF) coordinate system to the known coordinate reference system." Often, the document consists of one page containing a single map or other georegistered illustration. However, a map frame may be associated with a region on a page; there may be multiple map frames on a given page; and a document may have more than one page containing illustrations with GeoPDF encoding.
One intended functionality of the encoding is to support calculation of the position in coordinates of any point on the map image and thus to associate annotations and linked files with a particular geospatial location. This location can be expressed in any coordinate reference system, since the encoding includes sufficient information to perform conversions between coordinate systems. The georegistration encoding also supports measurement, such as calculation of distances between points.
Although the GeoPDF encoding for georegistration is publicly specified, the position of TerraGo Technologies is that the only file that is a GeoPDF file is a file created using a TerraGo product (either a TerraGo product or a TerraGo module incorporated into a GIS from another vendor, such as ESRI's ArcGIS). Such files can contain data payloads associated with locations on the georegistered image. The detailed encoding for these data payloads does not appear to be publicly specified. Comments welcome.
|Relationship to other formats|
|Used by||PDF, Portable Document Format. Although GeoPDF 2.2 was developed with PDF, Version 1.7 in mind, both OGC and the developers believe that it can be used with earlier versions, at least from Version 1.3.|
|Has earlier version||Earlier versions of GeoPDF were used in products of Layton Graphics and TerraGo. They are not publicly specified and are not described on this Web site.|
|LC experience or existing holdings||None.|
|LC preference||The Library of Congress Recommended Formats Statement (RFS) includes GeoPDF as a preferred format for cartographic materials in digital form. The RFS does not specify a version of GeoPDF.|
|Disclosure||The GeoPDF technique for embedding georegistration information for maps into a PDF file was developed at Layton Graphics, Inc. and is now maintained by TerraGo Technologies. The specification of version 2.2 has been accepted and published as a best practice by the Open Geospatial Consortium (OGC).|
|Documentation||As of September 2010, the best practice listed by the Open Geospatial Consortium was published on April 16, 2009 as OGC 08-139r2: GeoPDF Encoding Best Practice Version 2.2. Available online at http://portal.opengeospatial.org/files/?artifact_id=33332.|
As of September 2010, several U.S. government agencies produced and distributed maps as PDF files with GeoPDF encoding, including the United States Geological Survey (USGS), the U.S. Army Corps of Engineers, and the National Geospatial-Intelligence Agency. See U.S. Army Corps of Engineers 2012 factsheet on Geospatial PDF for information on the use of GeoPDF for map distribution by the U.S. Army Corps of Engineers. TerraGo Technologies has worked with several GIS vendors, such as ESRI and Intergraph, to develop modules that can create PDF files with GeoPDF encoding and import annotations added in the field back into a GIS system.
In September 2011, USGS published documents about techniques and methods (including formats) for two programs established recently. Both programs use GeoPDF as a format for distribution of digital maps for public use. See http://pubs.usgs.gov/tm/tm11b2/, US Topo Product Standard, for a specification of the digital replacement for the standard USGS printed maps at 1:24,000. See also http://pubs.usgs.gov/tm/11b03/, Standards for Scanned U.S. Geological Survey Historical Topographic Quadrangle Collection.
The compilers of this document welcome comments contributing additional information about adoption of GeoPDF as a georegistration encoding.
|Licensing and patents||
GeoPDF is a registered trademark of TerraGo Technologies. According to the specification published by OGC, the term GeoPDF may only be applied to products created under license from Terrago. However, the intent behind publishing the specification under a royalty-free license was to allow others to write software to read and write files using this method of geo-registration.
See PDF description for patent and licensing information associated with PDF.
|Transparency||Judging from example files, this georegistration encoding can usually be read by using an ASCII text editor to open the PDF file. In practice, most PDFs have compression filters applied to most of the file content.|
|Self-documentation||The GeoPDF encoding itself supplies limited geospatial metadata for maps or other georegistered illustrations in a PDF file.|
|External dependencies||To get full value from a PDF with GeoPDF encoding as a user, you need the TerraGo Toolbar, an add-on to Adobe Reader or the equivalent application for mobile devices. At October 2011, the toolbar is freely downloadable (after registration), but works only on Windows.|
|Technical protection considerations||The encoding itself has no means of protection. Encryption or other forms of technical protection may be applied to the file in which the georegistration information is embedded.|
|Normal rendering||The geospatial encoding is independent of image quality and functionality. See PDF for discussion of quality and functionality factors for images in PDF documents.|
|Clarity (high image resolution)||See PDF.|
|Color maintenance||See PDF.|
|Support for vector graphics, including graphic effects and typography||See PDF.|
|Support for multispectral bands||TBD|
|Functionality beyond normal rendering||See PDF.|
|GIS images and datasets|
The GeoPDF encoding for georegistration of an illustration in a PDF file defines a map frame for the image, by providing data to map the coordinate system of the PDF page to a known coordinate reference system. Three types of coordinate reference systems are supported: geodetic, projected, and unregistered cartesian (for engineering). The map frame specifies the coordinate transformation matrix, all parameters required for a map projection (if used), the reference ellipsoid, and the geodetic datum.
GeoPDF supports a list predefined geodetic datums and ellipsoids, by means of codes that correspond to names used by the GeoTrans software from the U.S. National Geospatial-Intelligence Agency. Note that in its specification of the GeoPDF encoding [OGC 08-139r2], "the OGC recognizes that the specification of the datum, ellipsoid, and CRS codes as used in this document do not conform to the EPSG database, the current de-facto normative reference for CRS metadata." GeoPDF also supports custom geodetic datum definitions. A geodetic datum is comprised of an ellipsoid, a known origin point, and a prime meridian. For GeoPDF encodings, a Greenwich prime meridian is assumed. The description for a custom geodetic datum may also specify a shift operation that converts (at least approximately) the geodetic datum’s coordinates to the widely-used World Geodetic System 1984 geodetic datum (WGS84).
|Support for GIS metadata||GeoPDF encoding provides specific geospatial metadata associated with an image within a document. GeoPDF makes no assumptions or recommendations with respect to GIS metadata for the PDF document as a whole. Version 1.4 of PDF and later support embedding of any metadata in XMP packages.|
|Filename extension||Not applicable.||GeoPDF does not define a file format, but an encoding for georegistration information that may be associated with an image. In practice, it will be embedded in a file in some version of the PDF format, and that file will likely have the extension pdf.|
||A PDF file including GeoPDF encoding will be recognized by the existence of an LGIDict entry associated with at least one page in the PDF.|
|Pronom PUID||See note
||No PUID as of Feb 2017.|
|Wikidata Title ID||Q5533911
The TerraGo product line uses the GeoPDF georegistration encoding to support the collection of information in the field using annotations (markups) associated with a point on the map. Application domains include emergency management, and management of natural resources and remote assets such as utility poles and railway track.
GeoPDF uses features of the PDF architecture to embed georegistration information into a page object. It was the first widely adopted technique for supporting georegistration within a PDF. With the release of Acrobat 9.0 and ExtensionLevel 3 to PDF, Version 1.7 in June 2008, Adobe introduced its own schemes for recording georegistration and 3D information in PDF documents. It remains to be seen whether users of GeoPDF migrate to the Adobe geospatial encoding.
The original GeoPDF encoding was developed at Layton Graphics, Inc. in the early 2000s. The use of the name LGIDict for the encoding object within a PDF file reflects that origin. Version 1 was drafted in 2002; version 2 was introduced in November 2003. The mapping group of Layton Graphics was spun off as TerraGo Technologies in September 2005.
The specification of version 2.2 of the GeoPDF encoding was published as a best practice by the Open Geospatial Consortium (OGC) in April 2009.
The TerraGo product line now supports the Adobe geospatial extensions (introduced with Acrobat 9.1 in June 2008) as well as GeoPDF "under the hood."