The EPSG Geodetic Parameter Dataset is a structured collection of definitions for coordinate reference systems, reference frames, and coordinate operations used to describe positions on Earth. Maintained by the International Association of Oil & Gas Producers (IOGP), it supplies identifiers and technical parameters that allow mapping, surveying, and geospatial software to interpret coordinates consistently. Its best-known identifiers include EPSG:4326, for a two-dimensional geographic coordinate reference system based on WGS 84, and EPSG:3857, for the projected system widely used in web maps.
The dataset is a reference resource, not a collection of maps or an executable coordinate-transformation service. Software incorporates its definitions and implements the mathematical operations they describe.
Origins and maintenance
“EPSG” originally stood for European Petroleum Survey Group, an organization concerned with surveying and positioning in the petroleum industry. The name persisted after responsibility for the dataset passed into the organizational framework now represented by IOGP.
Its original industrial purpose reflected a general geospatial problem: coordinates supplied by different organizations can use different reference frames, projections, units, and conventions. Numeric coordinates alone therefore do not necessarily identify a unique physical location.
The dataset developed into a resource used far beyond the petroleum industry. Its maintenance includes reviewing proposed additions and corrections, documenting sources, assigning identifiers, and publishing updated releases. Records may be deprecated when definitions are superseded or found unsuitable, while remaining available to interpret older data.
The EPSG Geodetic Parameter Registry provides an online interface to the information. The registry interface, the underlying dataset, and the copies incorporated into software are related but distinct resources; a software installation may contain an older release.
What the dataset contains
EPSG information is organized into linked record types rather than a flat list of projection names.
Coordinate reference systems
A coordinate reference system, or CRS, connects a mathematical coordinate system to a reference datum or reference frame. EPSG defines several types:
- Geographic CRSs, using angular coordinates such as latitude and longitude, sometimes with ellipsoidal height.
- Geocentric CRSs, using three-dimensional Cartesian coordinates related to Earth's centre.
- Projected CRSs, expressing positions on a plane through a map projection.
- Vertical CRSs, describing heights or depths relative to a specified vertical reference.
- Compound CRSs, combining component systems, commonly a horizontal CRS and a vertical CRS.
A definition includes more than a recognizable name. Coordinate axes, their order and directions, units, and the underlying reference information are integral to its meaning.
Reference datums, frames, and ellipsoids
A geodetic datum or reference frame establishes the relationship between a coordinate system and Earth. An ellipsoid supplies a mathematical approximation to Earth's shape, commonly specified through its semi-major axis and flattening.
These concepts are not interchangeable. Different reference frames can use the same ellipsoid but assign different coordinates to the same physical point.
The dataset also represents datum ensembles: groups of reference-frame realizations treated as sufficiently equivalent for specified purposes and accuracy levels. This matters for widely used global systems whose realizations have evolved over time.
Coordinate operations
EPSG records describe operations that relate coordinates in different systems. They include:
- Conversions, which change coordinate representation without changing the datum, such as applying a map projection.
- Transformations, which relate different datums or reference frames and commonly depend on empirically determined parameters.
- Concatenated operations, which combine several operations into a defined sequence.
An operation record can specify its source and target CRSs, method, parameters, area of use, scope, and stated accuracy. Some methods use simple parameter sets; others require external correction grids or models.
Supporting definitions
Other records define coordinate-system axes, units, prime meridians, operation methods, and operation parameters. Their explicit representation helps distinguish systems that appear similar but differ in consequential details, such as metres versus feet or latitude–longitude versus longitude–latitude ordering.
EPSG identifiers
An EPSG code identifies a particular record within the EPSG authority namespace. The notation EPSG:4326 combines the authority name with the numeric code.
The dataset assigns identifiers not only to CRSs but also to datums, ellipsoids, operation methods, coordinate operations, and other objects. Consequently, an EPSG number should be interpreted in its record-type context rather than assumed to identify a projection.
Two common examples illustrate important distinctions:
| Identifier | Definition | Important qualification |
|---|---|---|
| EPSG:4326 | WGS 84 geographic 2D CRS | Its defined axis order is latitude, then longitude, with angular units of degrees. |
| EPSG:3857 | WGS 84 / Pseudo-Mercator projected CRS | Uses easting and northing in metres; it is intended for web mapping and visualization, not distortion-free measurement. |
The WGS 84 name encompasses more than one coordinate representation. EPSG:4326 does not include a height coordinate; the WGS 84 geographic three-dimensional CRS has a separate identifier.
Similarly, Web Mercator coordinates being expressed in metres does not mean that coordinate differences directly equal ground distances everywhere. Projection scale varies strongly with latitude.
Role in geospatial software and standards
The dataset is widely used by geographic information systems, spatial databases, surveying applications, and coordinate-processing libraries. Software can resolve a short authority identifier into a detailed CRS definition, reducing the need for users or data producers to reproduce every parameter manually.
The PROJ coordinate-transformation library incorporates EPSG information, and many other geospatial applications use PROJ directly or indirectly. Software may also support definitions from other authorities and locally defined CRSs; EPSG is influential but not exhaustive.
EPSG definitions fit within the conceptual framework of the ISO 19111 standard for spatial referencing by coordinates. They can be represented in formats such as Well-Known Text for coordinate reference systems. The Open Geospatial Consortium uses and specifies mechanisms for referencing CRS definitions in geospatial services and data exchange.
An authority identifier and a serialized definition serve related purposes. The identifier points to a maintained definition; the serialization carries an explicit representation of that definition. Differences in format versions and software support can affect how completely the information is preserved.
Interpretation and limitations
Axis order and units
A common interoperability problem arises when software conventions differ from the formal CRS definition. EPSG:4326 specifies latitude before longitude, whereas many mapping interfaces use longitude before latitude.
Neither convention can safely be inferred from a pair of numbers alone. The governing file format, service protocol, or application programming interface determines how coordinate tuples are supplied and interpreted.
Choosing a transformation
A source CRS and target CRS do not always determine one uniquely appropriate transformation. Several operations may exist for different regions, accuracy requirements, or available resources.
A transformation's stated accuracy describes that operation under its applicable conditions; it does not guarantee the accuracy of the input measurements. An operation outside its area of use, or one applied without required correction grids, may yield unsuitable results.
Installing EPSG definitions also does not necessarily install all external files needed to execute every registered operation.
Time-dependent coordinates
High-accuracy positions can change with time because of plate motion and other deformation. Dynamic reference frames and time-dependent transformations require temporal information in addition to a CRS identifier.
A coordinate epoch describes the time associated with coordinates. It is distinct from a reference epoch used in defining a dynamic frame or transformation parameters. Naming a CRS alone may therefore be insufficient for reproducible, high-accuracy positioning.
Versioning and provenance
Software packages can contain different EPSG releases and may choose different available operations. Reproducible coordinate processing can require recording the dataset or software version, selected operation, external grids, and relevant epochs, rather than only the source and target EPSG codes.
Finally, assigning an EPSG identifier to a dataset does not establish that its coordinates were actually measured or calculated in that CRS. The identifier describes the declared spatial reference; the correctness of that declaration depends on the data's provenance.