### Install MapTiler Client JS SDK Source: https://epsg.io/docs/index Instructions for installing the MapTiler Client JS SDK using npm, a package manager for JavaScript. This SDK enables seamless integration with MapTiler services, including the Coordinates API. ```JavaScript npm install --save @maptiler/client ``` -------------------------------- ### MapTiler Coordinates API: Example Coordinate System Search Call Source: https://epsg.io/docs/index Illustrates a practical example of a URL call to the MapTiler Coordinates API for searching coordinate systems. It shows how to query for 'swiss' CRS, limit results, and include export details. ```APIDOC https://api.maptiler.com/coordinates/search/swiss deprecated=0.json?exports=true&limit=5 ``` -------------------------------- ### MapTiler Coordinates API: Example Coordinate Transformation Call Source: https://epsg.io/docs/index Provides a concrete example of a URL call to the MapTiler Coordinates API for transforming coordinates. It demonstrates the use of specific coordinate values, source and target CRS codes, and an operation ID. ```APIDOC https://api.maptiler.com/coordinates/transform/17,50.json?s_srs=4326&t_srs=5514&ops=1623 ``` -------------------------------- ### MapTiler Client JS: Search Coordinate Reference System Source: https://epsg.io/docs/index Demonstrates how to use the MapTiler Client JS library to search for coordinate reference systems. The example shows an asynchronous call to the `coordinates.search` method with a query string. ```JavaScript // in an async function, or as a 'thenable': const result = await maptilerClient.coordinates.search('mercator'); ``` -------------------------------- ### MapTiler Client JS: Transform Coordinates Source: https://epsg.io/docs/index Illustrates how to perform coordinate transformations using the MapTiler Client JS library. The example shows an asynchronous call to the `coordinates.transform` method, providing input coordinates and a target CRS. ```JavaScript const resultA = await maptilerClient.coordinates.transform([1, 45], {targetCrs: 9793}) ``` -------------------------------- ### Deprecated EPSG.io API Endpoints for Search and Transform Source: https://epsg.io/docs/index Examples of the old, deprecated API endpoints previously used by EPSG.io for searching coordinate systems and performing coordinate transformations. These endpoints have been superseded by the MapTiler Coordinates API. ```APIDOC https://epsg.io/?q=swiss&format=json ``` ```APIDOC https://epsg.io/trans?data=7.457914,46.948563&s_srs=4326&t_srs=2056 ``` -------------------------------- ### EPSG.io API Output Formats Source: https://epsg.io/docs/index A comprehensive list of supported output formats for EPSG.io API requests. This includes various Well-Known Text (WKT) versions, JSON, PROJ4, and formats compatible with GIS software like GeoServer, MapServer, and PostGIS, along with examples for each. ```APIDOC Output Formats: - wkt / ogcwkt Description: OGC Well Known Text Example: https://epsg.io/2056.wkt - prettywkt Description: Styled OGC Well Known Text Example: https://epsg.io/2056.prettywkt - wkt2 Description: OGC Well Know Text v2 Example: https://epsg.io/2056.wkt2 - esriwkt Description: ESRI definition of Well Known Text Example: https://epsg.io/2056.esriwkt - json Description: JSON encoded format Example: https://epsg.io/2056.json - proj4 Description: PROJ library definition Example: https://epsg.io/2056.proj4 - js / proj4js Description: Proj4JS implementation definition Example: https://epsg.io/2056.js (or .proj4js) - geoserver Description: GeoServer specification Example: https://epsg.io/2056.geoserver - mapfile Description: Usable directly in the Map Server configuration file Example: https://epsg.io/2056.mapfile - mapnik Description: Usable directly in Mapnik configuration file Example: https://epsg.io/2056.mapnik - sql Description: SQL statement for PostGIS or SpatialLite Example: https://epsg.io/2056.sql - html Description: HyperText Markup Language Example: https://epsg.io/2056.html - mapnik Description: XML with Mapnik definition Example: https://epsg.io/2056.mapnik - mapnikpython Description: Python code for Mapnik Example: https://epsg.io/2056.mapnikpython - mapserverpython Description: Python code for Map Server Example: https://epsg.io/2056.mapserverpython ``` -------------------------------- ### EPSG.io Supported Object Suffixes Reference Source: https://epsg.io/docs/index Lists the various object suffixes used in EPSG.io URLs, providing a description and an example URL for each type of geodetic object like datum, prime meridian, ellipsoid, and coordinate system components. ```APIDOC Object Suffixes: - datum: Geodetic datum definition (Example: https://epsg.io/6274-datum) - primem: Prime meridian definition (Example: https://epsg.io/8901-primem) - ellipsoid: Reference ellipsoid definition (Example: https://epsg.io/7004-ellipsoid) - method: Transformation method (Example: https://epsg.io/1025-method) - cs: Coordinate system definition (Example: https://epsg.io/1024-cs) - axis: Axis definitions (Example: https://epsg.io/32773-axis) - area: Area valid for the coordinate system (Example: https://epsg.io/1044-area) - units: Map units definition (Example: https://epsg.io/9001-units) ``` -------------------------------- ### Current MapTiler Coordinates API Endpoints for Search and Transform Source: https://epsg.io/docs/index Examples of the current API endpoints provided by MapTiler Coordinates API for searching coordinate systems and performing coordinate transformations. These new endpoints offer improved security, robustness, and scalability, requiring a MapTiler API key for access. ```APIDOC https://api.maptiler.com/coordinates/search/swiss.json?key=MapTiler-key ``` ```APIDOC https://api.maptiler.com/coordinates/transform/7.457914,46.948563.json?s_srs=4326&t_srs=2056&key=MapTiler-key ``` -------------------------------- ### PROJ Definition for Pseudo Mercator CRS (EPSG:3857) Source: https://epsg.io/docs/index An example of a PROJ string definition for the Pseudo Mercator Coordinate Reference System (EPSG:3857), commonly used by transformation libraries like PROJ. It specifies projection parameters, spheroid, units, and other CRS characteristics. ```PROJ +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 ``` -------------------------------- ### ESRI WKT Definition for Pseudo Mercator CRS Source: https://epsg.io/docs/index An example of an ESRI Well-Known Text (WKT) definition for the Pseudo Mercator Coordinate Reference System. This format details the geographic coordinate system, datum, spheroid, projection type, and specific parameters required for GIS software compatibility. ```ESRI WKT 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]] ``` -------------------------------- ### EPSG.io API Endpoints for Coordinate Reference Systems Source: https://epsg.io/docs/index This section outlines the various URL endpoints provided by EPSG.io for programmatic access to coordinate reference system definitions, transformations, and search functionalities. It includes patterns for accessing CRS data, transformations, and searching by specific criteria. ```APIDOC URL Endpoints: - https://epsg.io/{CODE} Description: Transformation or CRS Example: https://epsg.io/2056, https://epsg.io/1676 - https://epsg.io/{EPSG}-{CODE} Description: CRS with transformation Example: https://epsg.io/2056-1676 - https://epsg.io/{EPSG}-{CODE}.{FORMAT} Description: CRS with transformation in specific FORMAT Example: https://epsg.io/2056-1676.wkt, https://epsg.io/2056-1676.proj4 - https://epsg.io/{CODE}-{OBJECT} Description: Other types of registered OBJECTS, besides of transformation or CRS, such as prime meridian, datum, ellipsoid, … Example: https://epsg.io/7004-ellipsoid - https://epsg.io/?q=KEY:VALUE[+KEY:VALUE[+…]] Description: Search interface using the KEY:VALUE pairs for filtering results. Example: https://epsg.io/?q=kind%3ACOORDOP+deprecated%3A1 Documentation: https://docs.maptiler.com/cloud/api/coordinates/#search-coordinate-systems - https://epsg.io/{VALUE}-crs-{CODE} Description: Search by OGC GML values (OGP, IOGP, EPSG) Example: https://epsg.io/epsg-crs-2065 - https://epsg.io/urn:ogc:def:{CODE} Description: Search by URN Example: https://epsg.io/urn%3Aogc%3Adef%3Acrs%3AEPSG%3A%3A2056 ``` -------------------------------- ### MapTiler Coordinates API: Transform URL Format Source: https://epsg.io/docs/index Documents the universal URL format for performing coordinate transformations using the MapTiler Coordinates API. It details the required parameters such as coordinates, source CRS, target CRS, and optional operation codes. ```APIDOC Endpoint: https://api.maptiler.com/coordinates/transform/{COORDS}.json?s_srs={CODE}&t_srs={CODE} Parameters: - COORDS: Pair or triplets of coordinates separated by comma. Multiple coordinate pairs are separated by semicolon. Example: 17,50 | 17,50,300 | 17,50,300;17.1,50.1,310 - s_srs: Source coordinate reference system code. Example: 4326 - t_srs: Target coordinate reference system definition code. Example: 5514 - ops: Coordinate transformation operation code. Example: 1623 ``` -------------------------------- ### MapTiler Coordinates API: Search URL Format Source: https://epsg.io/docs/index Outlines the universal URL format for searching coordinate systems via the MapTiler Coordinates API. It specifies the query parameter for CRS search and additional parameters for controlling output format, limits, and transformations. ```APIDOC Endpoint: https://api.maptiler.com/coordinates/search/{QUERY}.json?PARAMS Parameters: - QUERY: Query string for Coordinate Reference System (CRS). Example: 2056.json | swiss.json | czechia deprecated:1.json - PARAMS: Additional parameters for showing exports in WKT and Proj4, limiting results, or showing transformations. Example: swiss.json?limit=1 | swiss.json?exports=true&limit=5 ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.