CARVIEW |
Guidance Notes
EPSG Dataset Supporting Documentation |
||
IOGP Reports 373-07-01 through 373-07-06 form a multi-part document for users of the EPSG Dataset: IOGP Report 373-07-01 (EPSG Guidance Note 7-1) – Understanding the EPSG Dataset, sets out detailed information about the Dataset content and its maintenance. IOGP Report 373-07-02 (EPSG Guidance Note 7-2) – Coordinate conversions and transformations including formulas, provides a detailed explanation of formulas necessary for executing coordinate conversions and transformations using the coordinate operation methods supported in the EPSG Dataset. Geodetic parameters in the EPSG Dataset are consistent with these formulas. IOGP Report 373-07-03 (EPSG Guidance Note 7-3) – EPSG Registry API user guide, is primarily intended to assist computer application developers who wish to use the RESTful API of the EPSG Registry to query and retrieve entities and attributes from the Dataset. IOGP Report 373-07-04 (EPSG Guidance Note 7-4) – EPSG Database and SQL Script user guide, provides guidance for users of the EPSG Database and SQL scripts which may be obtained from the EPSG Registry Download Dataset page. IOGP Report 373-07-05 (EPSG Guidance Note 7-5) – EPSG null and copy transformations to WGS 84, explains aspects of the policies for the inclusion in the EPSG Dataset of datum ensembles and so-called null coordinate transformations to WGS 84, including limitations in the description of WGS 84 through code EPSG:4326. IOGP Report 373-07-06 (EPSG Guidance Note 7-6) – EPSG Dataset - Policies and procedures for data management, documents strategy for populating the EPSG Dataset. The complete texts may be found in the Download section of this page.
Geomatics guidance notesFor all IOGP's Geomatics Committee reports, please go to IOGP Bookstore. |
Download: Guidance Note 7-1 (ver 9, Mar 2025) For an overview to the model changes see here. |
|
|
||
|
|
We use cookies to ensure that we give you the best experience on our website. By continue browsing our site, you consent to our use of cookies.
Wildcard search
Wildcards and filters in text searches
Text searches search the Name and Alias fields, and also the Extent Description field.
Strings which are entirely numeric will additionally search the object Code field.
Users who are logged in may extend the search to also include the Remarks field.
Text searches are case-insensitive.
Wildcards
Wildcard | Example |
% or *
|
Any wildcard characters |
? or _ | One wildcard character |
[ - ] | [ - ] Range e.g. N[a-c] will return all geodetic objects that contains a string starting with the letter 'N' or 'n' followed by any of the letters contained within the range specified within the square bracket, e.g. letters a, b and c. |
| | Or e.g. E[a|e]M will return all geodetic objects that contains a string starting with the letter E(e), ends with the letter M(m) and also contain either the letter a or letter e. |
The text string is automatically prefixed and suffixed by the % wildcard. These prefixes and suffixes are not applied to searches for object code.
Filters
[name] =xxx There is no limit to the length of the text string that can be submitted to the search
[code] =yyy [code]< yyy [code] > yyy, where yyy is an integer and does not accept wildcards
[type] =xxx applies a filter by subtype. It may be used to filter subtypes of CRS, CS, or datum.
Wildcards and filters may be combined together.
See the Support Documentation / User Manual for more detailed information.
© 2025 Geomatic Solutions
All Rights Reserved ®
- EPSG Dataset :
- v12.029
- GeoRepository :
- v2.41.20