Geodetic Mark Dataset Index of Tables
The geodetic data download includes information from 23 tables in Landonline. Most of these tables are used to hold information about both cadastral and geodetic marks - these extracts comprise only the rows relating to geodetic marks.
For the purposes of this extract a geodetic mark is defined as a mark which has a geodetic code.
Geodetic marks in Landonline are primarily represented in two tables. The crs_node table defines the logical location to which the mark refers, and the crs_mark tables defines the physical mark at that location. Several marks may refer to the same node, but only one will apply at one time. The mark currently associated with the node is identified by its status, which is 'COMM' (for commissioned).
Each mark may have several names associated with it. These names are stored in the crs_mark_name table and are distinguished by their type. For geodetic work the most important name is the geodetic code, which has type 'CODE'.
Similarly, each node may have many coordinates associated with it. These may include coordinates in different datums (for example NZGD200, NZGD49, and orthometric height datums), and coordinates that are either proposed new coordinates or decommissioned old coordinates. All these coordinates are stored in the crs_coordinate table, and are distinguished by coordinate system and status. The current authorised coordinate of a node for a datum is the coordinate with status 'AUTH'.
The crs_coordinate_sys table lists all the coordinate systems that are used in Landonline. Each coordinate system is defined in terms of a datum in the crs_datum table, and a coordinate type in the crs_coordinate_tpe table. The crs_cord_order table lists the coordinate orders that apply for each datum.
Each time a mark is surveyed or maintained is recorded in the crs_mrk_phys_state table.
The following list defines all the tables that are included in the geodetic data set.
Data file | Table name | Description |
---|---|---|
adj1.csv | crs_adjustment_run | Defines adjustment runs used to calculate coordinates and source information for coordinates converted from the old geodetic database. |
aud1.csv, aud2.csv | crs_audit_detail | Logs significant changes to records in the other tables. |
coo1.csv | crs_coordinate | Holds all coordinates of nodes (including orthometric height coordinates) |
cos.csv | crs_coordinate_sys | Lists all coordinate systems used in Landonline |
cot.csv | crs_coordinate_tpe | Defines the representations of coordinates (lat/lon, projections) |
cop.csv | crs_cor_precision | Lists the number of decimal places used to display coordinates of different types and orders |
cor.csv | crs_cord_order | Lists the coordinate orders that may be assigned to coordinates. |
dtm.csv | crs_datum | Lists the datums to which coordinates may be referenced |
elp.csv | crs_ellipsoid | Lists the ellipsoid models used. |
loc1.csv | crs_locality | Lists land districts and other areas of interest. |
mnt1.csv | crs_maintenance | Tracks maintenance required on marks |
mrk1.csv | crs_mark | Defines the physical marks associated with nodes |
mkn1.csv | crs_mark_name | Lists the various names used to refer to a mark including the geodetic code |
mps1.csv | crs_mrk_phys_state | Lists maintenance done and the state of the mark, beacon, and protection structure. |
nod1.csv | crs_node | Lists the nodes - the abstract points to which coordinates are referenced. |
npo1.csv | crs_node_prp_order | Lists the proposed order of nodes for which coordinates have not yet been calculated. |
orj1.csv | crs_ordinate_adj | Relates each coordinate to the adjustment that created it. |
ort.csv | crs_ordinate_type | Defines the types of ordinate (lat, lon, height) used. |
sit1.csv | crs_site | Lists sites at which one or more survey marks are located. |
slo.csv | crs_site_locality | Relates sites to land districts |
sco.csv | crs_sys_code | Lists codes used in the database |
scg.csv | crs_sys_code_group | Defines the various groups of codes used in the database. |
uom.csv | crs_unit_of_meas | Defines the units (such as metres) used in the database. |