GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
GeezerVison is showing epsg.io — EPSG.io Documentation EPSG.ioThe EPSG.io service helps you discover coordinate systems from across the globe, view their parameters, and choose the most suitable transformations. The service is developed and maintained by the MapTiler team. EPSG.io serves as a custom interface to the EPSG database, offering an extensive list of projections and coordinate systems, their bounding boxes, and transformation options to enhance the precision of coordinate transformations. Contents:
Migrate endpoints from EPSG.io to MapTiler Coordinates API
EPSG.io has transitioned to the MapTiler
Coordinates API for Old endpoints:
New endpoints:
For more details on migration, including JSON response changes and how to get your MapTiler key, read the migration guide. Discover coordinate systems and their parameters
To explore coordinate reference systems, use the search bar at epsg.io. You can
search for coordinate systems, datums, ellipsoids, units, transformation operations, and more. Enter the EPSG
code (e.g., Pick the right transformation
Transformation parameters are often essential for improved accuracy, especially when the source and target
coordinate reference systems use different ellipsoids. Applying the Each projection that supports multiple transformations offers a list of options on its dedicated page, such as Swiss CH1903+ / LV95 (EPSG:2056). Try selecting a different transformation if your GPS data doesn't align with the local coordinate system. Choosing the correct transformation is also crucial for reverse transformations, such as converting local coordinates back to WGS84 (EPSG:4326). This can also help when switching to a different coordinate system or achieving greater precision. Exporting coordinate reference systems in GIS-compatible formatsEach coordinate reference system definition can be exported in various text formats compatible with transformation libraries and GIS tools, including OGC WKT, PROJ, ESRI WKT, PROJ4JS, GeoServer, MapServer, PostGIS, and more. Example PROJ definition for the Pseudo Mercator CRS (EPSG:3857): +proj=merc +a=6378137 +b=6378137 +lat_ts=0 +lon_0=0 +x_0=0 +y_0=0 +k=1 +units=m +nadgrids=@null +wktext +no_defs +type=crs Example ESRI WKT definition for the Pseudo Mercator CRS: PROJCS["WGS_1984_Web_Mercator_Auxiliary_Sphere",
GEOGCS["GCS_WGS_1984",
DATUM["D_WGS_1984",
SPHEROID["WGS_1984",6378137.0,298.257223563]],
PRIMEM["Greenwich",0.0],
UNIT["Degree",0.0174532925199433]],
PROJECTION["Mercator_Auxiliary_Sphere"],
PARAMETER["False_Easting",0.0],
PARAMETER["False_Northing",0.0],
PARAMETER["Central_Meridian",0.0],
PARAMETER["Standard_Parallel_1",0.0],
PARAMETER["Auxiliary_Sphere_Type",0.0],
UNIT["Meter",1.0]]
Endpoints for coordinate reference systemsYou do not have to rely on the web interface. EPSG.io delivers endpoints that can be automated in applications.
List of output formats
List of supported objects
Coordinates API by
|
| Parameters | Description | Example |
|---|---|---|
| COORDS |
Pair or triplets of coordinates separated by, More coordinates pairs are separated by ; |
17,50 17,50,300 17,50,300;17.1,50.1,310 |
| s_srs | Source coordinate reference system | 4326 |
| t_srs | Target coordinate reference system definition | 5514 |
| ops | Coordinate transformation operation | 1623 |
Example coordinate transformation URL call:
https://api.maptiler.com/coordinates/transform/17,50.json?s_srs=4326&t_srs=5514&ops=1623
The universal search URL format is:
https://api.maptiler.com/coordinates/search/{QUERY}.json?PARAMS
| Parameters | Description | Example |
|---|---|---|
| QUERY | Query on CRS |
2056.json swiss.json czechia deprecated:1.json |
| PARAMS | Parameter for showing exports in WKT and Proj4, limit the number of results or show transformations. |
swiss.json?limit=1 swiss.json?exports=true&limit=5 |
Example coordinate search URL call:
https://api.maptiler.com/coordinates/search/swiss deprecated=0.json?exports=true&limit=5
To use MapTiler API services, you must include your MapTiler API key in all API calls by appending &key=xxxxxxxxxxxxxxxxxxxx to the URL.
A custom API key is provided upon free registration to the MapTiler Cloud platform. For more details, read the MapTiler documentation.
MapTiler Client JS is a JavaScript/TypeScript library designed for seamless integration with MapTiler services. It provides quick and easy access to the Coordinates API:
Install MapTiler SDK
npm install --save @maptiler/client
Search coordinate reference system
// in an async function, or as a 'thenable':
const result = await maptilerClient.coordinates.search('mercator');
Transform coordinates
const resultA = await maptilerClient.coordinates.transform([1, 45], {targetCrs: 9793})
Read more about the MapTiler Client JS for coordinates API.
OpenLayers simplifies embedding dynamic maps into web pages. It supports displaying map tiles, vector data, and markers from any source.
In addition to rendering, OpenLayers allows on-the-fly transformation of raster and vector data. Coordinate transformations are easily handled using the Proj4js definition powered by the MapTiler Coordinates API. For more details, visit the OpenLayers Proj4js documentation.
Read MapTiler Documentation to learn how to use OpenLayers with MapTiler maps and services.