This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| EPSG Registry | |
|---|---|
| Name | EPSG Registry |
| Type | Geodetic coordinate reference dataset |
| Established | 1985 |
| Maintained by | International Association of Oil & Gas Producers standards committee (original); successor bodies |
| Primary language | English |
| Website | See Accessibility and Formats |
EPSG Registry.
The EPSG Registry is a widely used database of coordinate reference systems, datums, coordinate transformations and related geodetic parameters. It provides standardized identifiers and metadata for spatial reference objects referenced in cartography, surveying, remote sensing and geospatial software. The Registry underpins interoperability among systems such as geographic information systems, global navigation satellite systems, and mapping services.
The Registry assigns numeric codes to geodetic objects including projected coordinate systems, geographic coordinate systems, vertical datums and transformation methods. It has been integrated into products and standards from vendors and organizations such as Esri, Google, Microsoft, Open Geospatial Consortium, International Organization for Standardization, and European Petroleum Survey Group (the origin of the numeric codes). Implementations rely on it for consistent interpretation of spatial reference metadata across tools like PROJ, GDAL, QGIS, PostGIS, ArcGIS, and MapServer. The Registry’s identifiers are commonly embedded in geospatial file formats such as GeoTIFF, GML, KML, Shapefile, and NetCDF.
The numeric coding scheme originated in the 1980s within petroleum industry coordination involving bodies like European Petroleum Survey Group and later coordination with organizations including Association of Petroleum Industry committees and contributors from British Geological Survey. Over decades the dataset evolved through contributions and harmonization with standards from International Hydrographic Organization, United Nations, International Association of Geodesy, and national mapping agencies such as Ordnance Survey and National Geospatial-Intelligence Agency. Software projects like PROJ and libraries within OSGeo played major roles in promulgation and reinterpretation of Registry entries. Governance and hosting arrangements have shifted as commercial and open communities sought stable stewardship, involving entities such as Open Geospatial Consortium and various national mapping institutions.
Entries in the Registry describe objects with attributes: identifier, name, datum relationships, axis order, unit definitions and transformation parameters. Key object types include geographic coordinate reference systems, projected coordinate reference systems, vertical reference frames, temporal frames, and coordinate operation methods. The Registry encodes parameters for transformations such as seven-parameter Helmert, Molodensky, and affine methods referenced in standards from International Organization for Standardization and European Petroleum Survey Group. Metadata links entries to authority citations and notes from organizations like International Association of Oil & Gas Producers and national geodetic services such as National Geodetic Survey and Instituto Geográfico Nacional.
Practitioners in fields including petroleum exploration, cadastral mapping, remote sensing, climate science, urban planning and navigation rely on Registry identifiers. Workflows in software like ArcGIS, QGIS, GRASS GIS, CartoDB and libraries such as Proj4js and GeoServer utilize entries to reproject datasets between systems like WGS 84, NAD83, ETRS89 and regional projections such as British National Grid, Lambert Conformal Conic, and Universal Transverse Mercator. Interoperability across platforms from vendors like Trimble and Leica Geosystems to open projects such as OpenStreetMap and Mapbox depends on consistent Registry mappings for map display, spatial analysis, and sensor fusion with systems like Galileo and GLONASS.
Maintenance has involved collaboration among industry bodies, standards organizations and national mapping agencies. Historically stewardship has moved through committees of European Petroleum Survey Group and later coordination with the Open Geospatial Consortium and national institutions such as Ordnance Survey and Institut Géographique National. Contributions and updates are proposed by experts from institutions including National Oceanic and Atmospheric Administration, United States Geological Survey, Natural Resources Canada, and academic groups from universities such as Massachusetts Institute of Technology and ETH Zurich. Processes for adding or revising entries include technical review, compatibility checks with ISO 19111 and consultation with stakeholders like satellite mission teams and surveying authorities.
The Registry is available in machine-readable formats used by software ecosystems: SQL dumps, XML, JSON, and serialized forms consumed by libraries like PROJ and GDAL. It is referenced within spatial data standards including GeoTIFF, ISO 19111, ISO 19162, and OGC WKT serializations. Users access the dataset through vendor integrations in ArcGIS, command-line tools in PROJ, and open platforms such as GitHub mirrors and registries maintained by mapping authorities. Documentation and mappings enable conversion between legacy identifiers and contemporary implementations used by projects like PostGIS and Mapnik.
Critiques focus on coverage gaps for local vertical datums, inconsistent metadata completeness across jurisdictions, and periodic mismatches between Registry entries and national definitions maintained by agencies like National Geodetic Survey and Geoscience Australia. Some stakeholders highlight lag in incorporating newly defined reference frames from initiatives such as International Terrestrial Reference Frame updates, and challenges in reconciling competing definitions from commercial vendors like Esri and independent projects like PROJ. The Registry’s reliance on community stewardship has produced fragmentation in derivative datasets and spawned forks maintained by vendors and open-source communities, complicating canonical resolution in multi-vendor workflows.