Registry Class |
Inheritance HierarchyNamespace: Ptv.Components.Projections
Assembly: Ptv.Components.Projections (in Ptv.Components.Projections.dll) Version: 1.7.10.0
SyntaxThe Registry type exposes the following members.
Methods| Name | Description | |
|---|---|---|
  | Add(String, CoordinateReferenceSystem, Boolean) |
Stores a CoordinateReferenceSystem in the registry.
|
| Add(String, String, Boolean) |
Creates, initializes and stores a CoordinateReferenceSystem in the registry.
|
| Contains |
Checks if the registry contains a specific coordinate reference system.
|
| Dispose |
Disposes the CoordinateReferenceSystem objects currently stored in the registry.
|
| Get |
Tries to find a CoordinateReferenceSystem in the registry.
|
| GetContent |
Returns the contents of the registry in CSV format.
|
| GetIds |
Returns the identifiers of the coordinate reference systems currently known to the registry.
|
| SetContent |
Adds the coordinate references system defined by a CSV formatted string to the registry.
|
RemarksThe Registry stores CoordinateReferenceSystem instances and provides an access using CRS identifiers, e.g. EPSG:4326.
On startup, the Registry is initialized from an internal EPSG database so that it is ready to provide access to all well known coordinate reference systems, e.g. EPSG:4326 (WGS84), EPSG:76131 (PTV Mercator) or EPSG:3857 (Google Mercator) to name a few. At the very base, the EPSG database included was generated out of the EPSG Geodetic Parameter Dataset, which is maintained by the Geodesy Subcommittee of OGP. In addition to those EPSG codes, aliases are injected (e.g. CoordinateReferenceSystem.Mapserver, CoordinateReferenceSystem.XServer) to make the access more convenient. For the rare case that coordinate reference systems are missing, coordinate reference systems can be added or overwritten using Registry.Add.
See Also