| CARVIEW |
Data Model
EPSG Data Model |
||
|
Following the publication of the revised ISO 19111:2019 data model, IOGP has upgraded the EPSG data model. The changes to the data model which apply from version 10.0 of the EPSG Dataset (September 2020) are: - Identification of dynamic datums and of CRSs based on these. For datums and CRSs affected by this change, there will be no changes to existing EPSG codes. - Addition of a new construct of ‘datum ensemble’. A datum ensemble groups together successive realizations of a datum as one. Some CRSs will be associated with a datum ensemble rather than a single datum. These will include the generic WGS 84 CRSs (EPSG CRS codes 4326 [geographic 2D], 4979 [geographic 3D] and 4978 [geocentric]). Existing EPSG codes will be unchanged. - Addition of a new CRS subtype ‘derived projected’. The term is from the ISO model and is consistent with other terms in the model, but is a misnomer. It is a CRS which is based upon an existing projected CRS, so ‘derived from projected’ would be a more accurate description. Many seismic bin grids are defined relative to a projected CRS – others are defined independently and later referenced to a projected CRS. Examples of both approaches will be included in the upgraded dataset. - Some CRS, datum or coordinate operation entities will be associated with multiple ‘usages’ – scope/extent (area) pairings. |
Download: Details of data model changes to relational tables |
|
|
The changes to the data model which apply from version 11.0 (November 2023) of the EPSG Dataset are: - Addition of an anchor_epoch attribute to the datum table. Further details of the data model mapping from the previous implementation to the current implementation may be accessed through the panel to the right. |
|
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