Geodetic Mark Dataset Tables

The geodetic data download includes information from 23 tables in Landonline.

Read the geodetic mark dataset index of tables or see a simplified data model of the geodetic mark dataset tables.

Table:

crs_adjustment_run

Data file: adj1.csv
Primary key: id

The adjustment run table holds information about network adjustment calculations from which one or more coordinates have been calculated. This table is also used to hold information about the source of coordinates that were converted from the previous geodetic database. This table is referenced by the crs_ordinate_adj table.

FieldTypeDescription
idINT(11)The unique id of the adjustment run.
adm_idINT(11)The id of the adjustment method used for the adustment.
cos_idINT(11)The id of the coordinate system used in the adjustment, references the crs_coordinate_sys table.
statusVARCHAR(4)The status of the adjustment run. This references the codes in the crs_sys_code table with code group (scg_code) ADJS
usr_id_execVARCHAR(20)The user id of the person who ran the adjustment.
adjust_datetimeDATETIMEThe time of the adjustment run.
descriptionVARCHAR(100)Descriptive information about the adjustment. This also stores references to the source of coordinates converted from the previous geodetic database.
sum_sqrd_residualsDOUBLE(16,8)The sum of squared residuals of observations in the adjustment.
redundancyDOUBLE(16,4)The number of degrees of freedom in the adjustment
wrk_idINT(11)Not use for geodetic adjustments.
audit_idINT(11)References the crs_audit_detail table which log changes to the status of the adjustment.

Table: crs_audit_detail

Data file: aud1.csv, aud2.csv
Primary key: id,timestamp

This table logs changes to many of the other tables in Landonline. Each logged table contains a field called audit_id, which is linked to the id field in this table. Significant changes to the records in other tables are logged in this table, and there may be many entries in this table for each id.

The bulk data extract only provides two subsets of this table.

  • The aud1.csv file lists any records that have been deleted. This includes information about tables in Landonline that are not part of the geodetic bulk data extract - most entries will not refer to geodetic data. This file does not contain any data for monthly (full) extracts - it is only relevant to incremental updates.
  • The aud2.csv file lists only information about geodetic coordinates. It may be used to determine when coordinates are authorised and decommissioned.
FieldTypeDescription
idINT(11)The id of the audited record. This is referenced by the audit_id field in another table. It is not unique in this table, since there may be several updates applying to the same record. The audit id is unique within the table it refers to.
table_nameVARCHAR(40)The name of the table to which the audit record refers.
timestampDATETIMEThe time of the change.
actionCHAR(1)The type of the change - I = insert, U = update, D = delete.
statusCHAR(4)The value of the status field of the record after the audited changes have been applied.

Table: crs_coordinate

Data file: coo1.csv
Primary key: id

This table holds all coordinate of geodetic marks. This include both postion coordinates and orthometric height coordinates. Each coordinate defines the position of a node (generally a geodetic mark) in terms of a coordinate system. The coordinate systems are defined in the crs_coordinate_sys table.

Each node may have many coordinates in many different coordinate systems. However each node only has one authoritative coordinate in each system (strictly in each coordinate datum), which is the coordinate for which the status field is 'AUTH'.

By way of an example, a node could have an authoritative NZGD2000 coordinate, two decommissioned NZGD2000 coordinates, an authoritative NZGD1949 coordinate, an authoritative orthometric height on Wellington height datum, and a decommissioned height on Wellington height datum.

Note that coordinate values are never altered in Landonline. The authoritative coordinate of a node is changed by creating a new coordinate, setting the status of the current authoritative coordinate to decommissioned, and setting the status of the new coordinate to authoritative.

FieldTypeDescription
idINT(11)The unique identifier for the coordinate
cos_idINT(11)The identifier of the coordinate system of the coordinate. This references the id field the crs_coordinate_sys table.
nod_idINT(11)The identifier of the node which coordinate references. This references the id field in the crs_node table.
ort_type_1CHAR(4)The type of the first ordinate of the coordinate (eg Latitude, Easting). This references the crs_ordinate_type table.
ort_type_2CHAR(4)The type of the second ordinate of the coordinate.
ort_type_3CHAR(4)The type of the third ordinate of the coordinate.
statusCHAR(4)The status of the coordinate. A status of 'AUTH' identifies the current coordinate for the node in the coordinate system. This references the codes in the crs_sys_code table with code group (scg_code) COOS.
sdc_statusCHAR(1)Not used for geodetic data.
sourceCHAR(4)This indicates the source of the coordinate. This is relevant only for coordinates converted from other databases when Landonline was started.
value1DOUBLE(16,8)The value of the first ordinate of the coordinate.
value2DOUBLE(16,8)The value of the second ordinate of the coordinate.
value3DOUBLE(16,8)The value of the third ordinate of the coordinate.
wrk_id_createdINT(11)An identifier of a geodetic work or survey from which the coordinate was created. This does not reference information available in the geodetic download data set.
cor_idINT(11)Defines the order of the coordinate. It references the id field in the crs_cord_order table. Online information is available on NZGD1949 horizontal , and Vertical Orders
audit_idINT(11)References entries in the crs_audit_detail table which log changes to this coordinate (mainly changes to status).

Table: crs_coordinate_sys

Data file: cos.csv
Primary key: id

This table lists the coordinate systems used in Landonline.

Each coordinate system is defined by a datum, which defines how the coordinate is measured, and a coordinate type, which defines how the position on the datum is expressed.

Examples of datums are NZGD2000 (New Zealand Geodetic Datum 2000), NZGD1949, Wellington Height Datum. Examples of coordinate types are geodetic coordinates (latitude, longitude, and ellipsoidal height), easting and northing in Wellington Circuit (a transverse Mercator projection), and orthometric height.

Note that the geodetic download data set does not include the parameters of projections (such as central meridian, scale_factor, and so on). Further information on New Zealand coordinate systems can be found on the Geodetic System Standards & Publications page.

FieldTypeDescription
idINT(11)The unique identifier of the coordinate system in Landonline.
cot_idINT(11)The identifier of the coordinate type of the coordinate system. This references the crs_coordinate_tpe table.
dtm_idINT(11)The identifier of the datum of the coordinate system. This references the crs_datum table
cos_id_adjustINT(11)Used internally by Landonline
nameVARCHAR(100)The name of the coordinate system
initial_sta_nameVARCHAR(100)The name of the initial station of the coordinate system, if there is one.
codeVARCHAR(10)A code used to refer to the coordinate system.
audit_idINT(11)References entries in the crs_audit_detail table which log changes to this coordinate system.

Table: crs_coordinate_tpe

Data file: cot.csv
Primary key: id

This table defines each coordinate type used in Landonline. A coordinate type is a way of representing a position in terms of a datum. It may be a specific projection, or latitude and longitude, or an orthometric height.

FieldTypeDescription
idINT(11)The Landonline identifier for the coordinate type.
nameVARCHAR(100)The name of the coordinate type.
statusVARCHAR(4)The status of the coordinate type. This is mainly for use within Landonline. This references the codes in the crs_sys_code table with code group (scg_code) COTS.
ort_type_1VARCHAR(4)The type of the first ordinate of the coordinate type (eg Latitude, Easting). This references the crs_ordinate_type table.
ort_type_2VARCHAR(4)The type of the second ordinate of the coordinate type (eg Latitude, Easting).
ort_type_3VARCHAR(4)The type of the third ordinate of the coordinate type (eg Latitude, Easting).
categoryVARCHAR(4)The category of the coordinate - for example ellipsoidal coordinates, projection coordinates. This references the codes in the crs_sys_code table with code group (scg_code) COTC.
dimensionVARCHAR(4)This defines the dimensions of the coordinate. This references the codes in the crs_sys_code table with code group (scg_code) COTD.
ord_1_minDOUBLE(16,4)If defined this specifies the minimum valid value of the first ordinate.
ord_1_maxDOUBLE(16,4)If defined this specifies the maximum valid value of the first ordinate.
ord_2_minDOUBLE(16,4)If defined this specifies the minimum valid value of the second ordinate.
ord_2_maxDOUBLE(16,4)If defined this specifies the maximum valid value of the second ordinate.
ord_3_minDOUBLE(16,4)If defined this specifies the minimum valid value of the third ordinate.
ord_3_maxDOUBLE(16,4)If defined this specifies the maximum valid value of the third ordinate.
dataVARCHAR(4)Not used
audit_idINT(11)References entries in the crs_audit_detail table which log changes to this coordinate type.

Table: crs_cor_precision

Data file: cop.csv
Primary key: cor_id,ort_type

This table lists the preferred number of decimal places used to display a coordinate of a given order and ordinate type. For example it may specify that an order 2 easting in NZGD2000 is displayed with three decimal places.

FieldTypeDescription
cor_idINT(11)The id defining the coordinate order (which in turn defines the datum). This references the crs_cord_order table.
ort_typeCHAR(4)The ordinate type - a reference to the crs_ordinate_type table.
decimal_placesSMALLINT(6)The number of decimal places to display.
audit_idINT(11)References entries in the crs_audit_detail table which log changes to this coordinate precision information.

Table: crs_cord_order

Data file: cor.csv
Primary key: id

The crs_cord_order table maintains a list of the orders that can be assigned to coordinates. Each datum (in crs_datum) may have assigned a set of orders.

FieldTypeDescription
idINT(11)The id used in Landonline to reference the coordinate order.
displayVARCHAR(4)The text to display to represent the order (for example "1", "2").
descriptionVARCHAR(100)A description of the order.
dtm_idINT(11)The id of the datum for which the order applies. This references the id field in the crs_datum table.
order_groupSMALLINT(6)A classification of orders used for layering graphical views in Landonline.
errorDOUBLE(16,4)An indicative measure of the accuracy in metres of coordinate of this order. This is used to define the sequence of orders from most to least accurate, and to allow a mapping of orders between different datums.
audit_idINT(11)References entries in the crs_audit_detail table which log changes to the coordinate order information.

Table: crs_datum

Data file: dtm.csv
Primary key: id

This table lists the datums used in Landonline. The datum is the physical framework within which a position (or orthometric height) is measured. Examples of datums are New Zealand Geodetic Datum 2000 (NZGD2000) and Wellington height datum.

FieldTypeDescription
idINT(11)The id used in Landonline to identify the datum.
nameVARCHAR(100)The name of the datum.
typeVARCHAR(4)The type of the datum classifies datums into geodetic, gravimetric, and other datums. This references the codes in the crs_sys_code table with code group (scg_code) DTMT.
dimensionVARCHAR(4)The dimension of the datum indicates the number of ordiantes it supports (ie one, two, or threee dimensional). This references the codes in the crs_sys_code table with code group (scg_code) DTMD.
ref_datetimeDATETIMEThe reference time (if any) that applies to the datum. For example NZGD2000 is defined in terms of positions at epoch 2000.0.
statusVARCHAR(4)The status of the datum - defines how it can be used in Landonline. This references the codes in the crs_sys_code table with code group (scg_code) DTMS.
elp_idINT(11)The id of an ellipsoid defined for the datum. This references the id field in the crs_ellipsoid table.
ref_datum_codeVARCHAR(4)A code used in Landonline to manage coordinate transformations between datums - a transformation may be defined between two datums which have the same reference datum.
codeVARCHAR(10)A code used to refer to the datum outside Landonline.
audit_idINT(11)References entries in the crs_audit_detail table which log changes to the datum information.

Table: crs_ellipsoid

Data file: elp.csv
Primary key: id

This table maintains a list of ellipsoids used in Landonline.

FieldTypeDescription
idINT(11)The Landonline id for the ellipsoid.
nameVARCHAR(100)The name of the ellipsoid.
semi_major_axisDOUBLE(16,4)The length of the semi-major axis of the ellipsoid in metres.
flatteningDOUBLE(16,10)The reciprocal of the flattening of the ellipsoid.
audit_idINT(11)References entries in the crs_audit_detail table which log changes to the ellipsoid information.

Table: crs_locality

Data file: loc1.csv
Primary key: id

This table lists various types of localities (such as land districts) defined in Landonline.

FieldTypeDescription
idINT(11)The Landonline id of the locality.
typeVARCHAR(4)The type of the locality. This references the codes in the crs_sys_code table with code group (scg_code) LOCT.
nameVARCHAR(100)The name of the locality.
loc_id_parentINT(11)The id of another locality to which this locality belongs.
se_row_idINT(11)Landonline administrative information.
audit_idINT(11)References entries in the crs_audit_detail table which log changes to the locality information.
shapeTEXTLandonline information not available in the extract dataset.

Table: crs_maintenance

Data file: mnt1.csv
Primary key: mrk_id,type

This table maintains a list of maintenance required or completed on geodetic marks. This is used to manage outstanding maintenance. For each mark it can hold one entry for the mark, beacon, and protection structure (eg fence, cover). The record of maintenance that has been done on a mark is held in the crs_mrk_phys_state table.

FieldTypeDescription
mrk_idINT(11)The id of the mark requiring maintenance. This references the crs_mark table.
typeVARCHAR(4)Defines whether the maintenance applies to the mark, beacon, or protection structure. This references the codes in the crs_sys_code table with code group (scg_code) MNTT.
statusVARCHAR(4)Defines the type of maintenance required (such as offset, repair). This references the codes in the crs_sys_code table with code group (scg_code) MNTS.
complete_dateDATETIMEDefines the date when the maintenance has been completed.
audit_idINT(11)References entries in the crs_audit_detail table which log changes to the maintance information.
descriptionTEXTA description of the required maintenance

Table: crs_mark

Data file: mrk1.csv
Primary key: id

This table lists the physical marks to which nodes (in the crs_node table) refer. Several marks may refer to the same node, but only one can be current - this is the mark with status COMM (commissioned).

FieldTypeDescription
idINT(11)The Landonline identifier of the mark.
nod_idINT(11)The id of the node which is defined for the mark.
statusVARCHAR(4)The status of the mark, one of pending, commissioned, or decommissioned. This references the codes in the crs_sys_code table with code group (scg_code) MRKS
typeVARCHAR(4)The type of mark - for example Iron Tube. This references the codes in the crs_sys_code table with code group (scg_code) MRKT.
categoryVARCHAR(4)The category of mark. This can have values such as benchmark, urban standard, and so on, but is currently not populated. This references the codes in the crs_sys_code table with code group (scg_code) MRKC.
countryVARCHAR(4)The country in which the mark is located. This references the codes in the crs_sys_code table with code group (scg_code) CTRY.
beacon_typeVARCHAR(4)The type of beacon over the mark. This references the codes in the crs_sys_code table with code group (scg_code) MRKE.
protection_typeVARCHAR(4)The type of protection structure for the mark. This references the codes in the crs_sys_code table with code group (scg_code) MRKR.
maintenance_levelVARCHAR(4)Defines whether or not the mark is to be maintained. This references the codes in the crs_sys_code table with code group (scg_code) MRKM.
mrk_id_distINT(11)If this mark replaces an existing mark then this field holds the mark id of the disturbed mark it replaces.
disturbedCHAR(1)Defines whether this mark has been disturbed (either 'Y' or 'N').
disturbed_dateDATETIMEThe date on which this mark was disturbed.
mrk_id_replINT(11)The id of the mark that has replaces this mark, if any.
replacedCHAR(1)Defines whether this mark has been replaced (either 'Y' or 'N').
replaced_dateDATETIMEThe date on which this mark was replaced.
mark_annotationVARCHAR(50)A comment relating to the disturbance/replacement of the mark.
wrk_id_createdINT(11)The Landonline id of the survey or geodetic work which created the mark.
audit_idINT(11)References entries in the crs_audit_detail table which log changes to the mark information.
descriptionTEXTDescriptive information about the mark. More reliable information may be found in the crs_mrk_phys_state table.

Table: crs_mark_name

Data file: mkn1.csv
Primary key: mrk_id,type

This table lists the names of each geodetic mark. A mark may have several names of various types. In particular, the name with type 'CODE' is the geodetic code of the mark.

FieldTypeDescription
mrk_idINT(11)The Landonline id of the mark to which the name refers.
typeVARCHAR(4)The type of name (for example CODE). This references the codes in the crs_sys_code table with code group (scg_code) MKNT.
nameVARCHAR(100)The name.
audit_idINT(11)References entries in the crs_audit_detail table which log changes to the mark name information.

Table: crs_mrk_phys_state

Data file: mps1.csv
Primary key: mrk_id,wrk_id,type

The crs_mrk_phys_state table holds a list of maintenance applied to a mark and status information about the mark. This information is received as a "geodetic work". It is defined separately for the actual mark, the beacon that may be placed over the mark, and the protection structure associated with the mark. Many marks do not have all three components, and in some cases the beacon and protection structure may be the same thing (for example quadrupod beacons).

The table describes both the maintenance work that may have been done on the mark (or beacon or protection structure), and the state of the mark when the work was completed.

FieldTypeDescription
mrk_idINT(11)The Landonline id of the mark for which the data applies. This reference the id field in the crs_mark table.
wrk_idINT(11)The geodetic work from which the mark state information was received. The bulk data extract does not include details of geodetic works.
typeVARCHAR(4)Specifies which component (mark, beacon, protection structure) the data refers to. This references the codes in the crs_sys_code table with code group (scg_code) MPST.
conditionVARCHAR(4)The condition of the mark, beacon, or protection structure at the completion of the geodetic work. This references the codes in the crs_sys_code table with code group (scg_code) MPSC.
existing_markCHAR(1)Defines whether the mark existed before the geodetic work (either 'Y' or 'N')
statusVARCHAR(4)This references the codes in the crs_sys_code table with code group (scg_code) MPSS.
ref_datetimeDATETIMEThe time at which the mark state information was recorded.
pend_mark_statusVARCHAR(4)Not used for geodetic data
pend_replacedCHAR(1)Not used for geodetic data
pend_disturbedCHAR(1)Not used for geodetic data
mrk_id_pend_repINT(11)Not used for geodetic data
mrk_id_pend_distINT(11)Not used for geodetic data
pend_dist_dateDATETIMENot used for geodetic data
pend_repl_dateDATETIMENot used for geodetic data
pend_mark_nameVARCHAR(100)Not used for geodetic data
pend_mark_typeVARCHAR(4)Not used for geodetic data
pend_mark_annVARCHAR(50)Not used for geodetic data
audit_idINT(11)References entries in the crs_audit_detail table which log changes to the mark state information.
descriptionTEXTDescription of the maintenance done and the state of the mark, beacon, or protection structure.

Table: crs_node

Data file: nod1.csv
Primary key: id

A node is the abstract point to which a coordinate refers. Each node may be referenced by several coordinates in the crs_coordinate table - some current and some historical. It may also be physically represented by one or more marks in the crs_mark table - one current mark and possibly some decommissioned marks.

FieldTypeDescription
idINT(11)The Landonline id of the node.
cos_id_officialINT(11)The preferred coordinate system for the node. This is used to identify the "official coordinate" of the node that is used for plotting purposes. For all marks in New Zealand and the Chatham Islands this is New Zealand Geodetic Datum 2000. For marks in the Ross Dependency in Antarctica this is the Ross Sea Region Geodetic Datum 2000. This references the id in the crs_coordinate_sys table.
typeVARCHAR(4)The type of the node (for example central, eccentric). This references the codes in the crs_sys_code table with code group (scg_code) NODT.
statusVARCHAR(4)The status of the node - authoritative, decommissioned, or pending. This references the codes in the crs_sys_code table with code group (scg_code) NODS.
order_group_offINT(11)Defines the layer in which the node is placed in spatial views (maps) in Landonline.
sit_idINT(11)Defines the site to which the node belongs. The site represents a physical grouping of nodes in an area. For example a site may include No 1 and No 2 versions of geodetic stations. Currently this feature is not used in Landonline - each station has its own distinct site. This references the crs_site table.
wrk_id_createdINT(11)Defines the Landonline id of the geodetic work or survey in which the node was created.
alt_idINT(11)Landonline administrative data.
se_row_idINT(11)Landonline administrative data.
audit_idINT(11)References entries in the crs_audit_detail table which log changes to the node state information.
shapeTEXTNot used in downloaded geodetic data.

Table: crs_node_prp_order

Data file: npo1.csv
Primary key: nod_id,dtm_id

This table lists proposed orders of nodes. This is used when a mark has been proposed as part of a network scheme but has not yet been surveyed or had coordinates calculated to the intended order of the mark.

FieldTypeDescription
dtm_idINT(11)The datum to which the order refers. This references the id in the crs_datum table.
nod_idINT(11)The id of the node for which the order applies. This references the id in the crs_node table.
cor_idINT(11)The proposed coordinate order. This references the id in the crs_cord_order table.
audit_idINT(11)References entries in the crs_audit_detail table which log changes to the proposed order information.

Table: crs_ordinate_adj

Data file: orj1.csv
Primary key: adj_id,coo_id_source

This table associates coordinates (and by implication nodes) with adjustments. For each node used the adjustment requires an input coordinate. For some of the nodes it will also generate a new output coordinate.

When an adjustment is set up this table lists all the input coordinates to the adjustment and defines which are to be held fixed and which are to be calculated. After the adjustment is run the table also lists the generated coordinates and holds statistical information such as the error ellipse and the offset between the original and new coordinates of adjusted node.

The table also holds information about the proposed order that the new coordinates will have when the adjustment (and hence the coordinates) is authorised.

FieldTypeDescription
adj_idINT(11)The id of the adjustment to which the coordinates are associated. This references the crs_adjustment_run table.
coo_id_sourceINT(11)The id of the input coordinate to the adjustment. This implicitly defines the nodes involved in an adjustment. This references the crs_coordinate table.
sdc_status_propCHAR(1)Not relevant in geodetic adjustments - this holds the proposed SDC status of the new coordinate before the adjustment is authorised.
coo_id_outputINT(11)The id of the coordinate generated by the adjustment. This will always refer to the same node as the coo_id_source field. This is only populated after the adjustment has been run, and only if a new coordinate is calculated for the node.
constraint1CHAR(4)Specifies the how the node is used in the adjustment - whether it is fixed, or if not which ordinates are calculated. This references the codes in the crs_sys_code table with code group (scg_code) ORJC
rejectedCHAR(1)Specifies that the node was rejected in the adjustment. Either 'Y' or 'N'.
adjust_fixedCHAR(1)Specifies that the node was fixed in the adjustment. Either 'Y' or 'N'.
cor_id_propINT(11)Stores the proposed order of the new coordinate before the adjustment (and hence the coordinate) is authorised.
change_eastDOUBLE(16,4)The east offset of the new coordinate relative to the input coordinate in metres.
change_northDOUBLE(16,4)The north offset of the new coordinate relative to the input coordinate in metres.
change_heightDOUBLE(16,4)The vertical offset of the new coordinate relative to the input coordinate in metres.
h_max_accuracyDOUBLE(16,4)The length of the semi-major axis of the horizontal error ellipse in metres.
h_min_accuracyDOUBLE(16,4)The length of the semi-minor axis of the horizontal error ellipse in metres.
h_max_azimuthDOUBLE(16,4)The orientation of the semi-major axis of the horizontal error ellipses measured in degrees eastwards from north.
v_accuracyDOUBLE(16,4)The expected error of the vertical coordinate in metres.
audit_idINT(11)References entries in the crs_audit_detail table which log changes to the ordinate adjustment information.

Table: crs_ordinate_type

Data file: ort.csv
Primary key: type

This table defines the types of ordinates (latitude, longitude, easting, etc) that can be used to construct coordinates in Landonline.

FieldTypeDescription
typeVARCHAR(4)A code defining the type.
uom_codeVARCHAR(4)A code defining the units in which the type is defined (eg metres, degrees). This references the crs_unit_of_meas table.
descriptionVARCHAR(100)A description of the type.
format_codeVARCHAR(4)Defines how the ordinate is to be formatted (for example as degrees, minutes, and seconds, or with a fixed number of decimal places). This references the codes in the crs_sys_code table with code group (scg_code) ORTF
mandatoryCHAR(1)Defines whether the ordinate is required in a coordinate. This is either 'Y' or 'N'.
audit_idINT(11)References entries in the crs_audit_detail table which log changes to the ordinate adjustment information.

Table: crs_site

Data file: sit1.csv
Primary key: id

This table lists the sites at which geodetic marks are located. A site is an area in which one or more geodetic marks are located. Reference (or witness) marks, and "Number 2" marks may be on the same site as the principal mark. At present every geodetic mark in Landonline has a distinct site.

This table is reference by the crs_node table.

FieldTypeDescription
idINT(11)The Landonline id for the site.
typeVARCHAR(4)The type of site - eiher maintained or proposed. This references the codes in the crs_sys_code table with code group (scg_code) SITT.
occupierVARCHAR(100)The occupier of the site - generally the the person or organisation that should be contacted to gain access to the site.
audit_idINT(11)References entries in the crs_audit_detail table which log changes to the site information.
descriptionTEXTA description of the site. This does not hold useful information for marks converted from the previous geodetic database.

Table: crs_site_locality

Data file: slo.csv
Primary key: sit_id,loc_id

This table links sites to localities. For geodetic marks this links the site to a land district (which is one type of locality).

FieldTypeDescription
sit_idINT(11)The Landonline id of the site. This references the id field in the crs_site table.
loc_idINT(11)The Landonline id of the locality. This references the id field in the crs_locality table.
audit_idINT(11)References entries in the crs_audit_detail table which log changes to the site locality information.

Table: crs_sys_code

Data file: sco.csv
Primary key: scg_code,code

This table lists codes that are used throughout Landonline. The codes used are four character mnemonics. This table defines the corresponding value to the code. Codes are classified into groups, defined in the crs_sys_code_group table. Each group has a specified data type which is one of date, number, or character string.

FieldTypeDescription
scg_codeVARCHAR(4)This defines the system code group for the code. This references the code field in the crs_sys_code_group table.
codeVARCHAR(4)The system code.
descriptionTEXTA description of what the code represents.
statusVARCHAR(4)The status of the code - either current or historical. This references the codes in the crs_sys_code table with code group (scg_code) SYSS
date_valueDATETIMEThe value for date type codes.
char_valueTEXTThe value for character string type codes.
num_valueDOUBLE(16,4)The value for number type codes.
start_dateDATETIMEThe first date on which the code becomes valid (not used
end_dateDATETIMEThe last date on which the code is valid (not used
audit_idINT(11)References entries in the crs_audit_detail table which log changes to the system code information.

Table: crs_sys_code_group

Data file: scg.csv
Primary key: code

The defines the groups of system codes used in Landonline. It is referenced by the crs_sys_code table.

FieldTypeDescription
codeVARCHAR(4)The code defining the group.
descriptionVARCHAR(100)A description of the group.
user_create_flagCHAR(1)Landonline administrative information.
user_modify_flagCHAR(1)Landonline administrative information.
user_delete_flagCHAR(1)Landonline administrative information.
user_view_flagCHAR(1)Landonline administrative information.
data_typeCHAR(1)This defines the type of data (text, date, number) that the system code group defines. This references the codes in the crs_sys_code table with code group (scg_code) SCGD.
group_typeCHAR(1)This defines a classification of codes that is no longer used. This references the codes in the crs_sys_code table with code group (scg_code) SCGG
audit_idINT(11)References entries in the crs_audit_detail table which log changes to the system code group information.

Table: crs_unit_of_meas

Data file: uom.csv
Primary key: code

This table defines the units (such as metres, hectares) used to define quantities in Landonline.

FieldTypeDescription
codeVARCHAR(4)The code used to identify the unit.
descriptionVARCHAR(100)The name of the unit
audit_idINT(11)References entries in the crs_audit_detail table which log changes to the units information.