| SchemaSpy Analysis of sola.cadastreThe SOLA implementation of the LADM Spatial Unit Package. Represents parcels of land and water that can be associated to rights (a.k.a. Cadastre Objects) as well as general spatial or geographic features such as roads, hydro and place names, etc. General spatial features are also known as Spatial Units in SOLA. | Generated by SchemaSpy |
| Generated by SchemaSpy on Tue May 31 09:57 NZST 2016 | |
| Database Type: PostgreSQL - 9.4.6 |
|
XML Representation Insertion Order Deletion Order (for database loading/purging scripts) |
| Table / View | Children | Parents | Columns | Comments |
|---|---|---|---|---|
| area_type | 2 | 4 | Code list of area types. Identifies the types of area (calculated, official, survey defined, etc) that can be recorded for a parcel (a.k.a. cadastre object). Implementation of the LADM LA_AreaType class. Tags: Reference Table, LADM Reference Object |
|
| building_unit_type | 1 | 4 | Code list of building unit types. Identifies the types of building unit that can exist on a parcel. Implementation of the LADM LA_BuildingUnitType class. Not used by SOLA. Tags: Reference Table, LADM Reference Object, Not Used |
|
| cadastre_object | 4 | 5 | 19 | Specialization of Spatial Unit that represents primary cadastral features such as parcels. Parcels captured in SOLA should have a spatial definition that illustrates the shape and geographic location of the parcel although this is not a mandatory requirement. Parcels without a spatial definition may be referred to as aspatial or textual parcels. Tags: FLOSS SOLA Extension, Change History |
| cadastre_object_node_target | 1 | 8 | Used to store coordinate details for new or modified nodes during the Redefine Cadastre process. Tags: FLOSS SOLA Extension, Change History |
|
| cadastre_object_target | 2 | 8 | Used to identify cadastre objects that are being changed or cancelled by a cadastre related transaction (i.e. Change Cadastre or Redefine Cadastre). These changes are considered pending/unofficial and do not affect the registered state of the cadastre object until the transaction is approved. Note that new cadastre objects are created in the cadastre_object table with a status of pending and they are not recorded in this table. Tags: FLOSS SOLA Extension, Change History |
|
| cadastre_object_type | 2 | 5 | Code list of cadastre object types. E.g. parcel, building_unit, road, etc. Tags: FLOSS SOLA Extension, Reference Table |
|
| dimension_type | 1 | 4 | Code list of dimension types. Identifies the number of dimensions used to define a spatial unit. E.g. 1D, 2D, etc. Implementation of the LADM LA_DimensionType class. SOLA assumes all spatial units are 2D. Tags: Reference Table, LADM Reference Object |
|
| Function: add_topo_points | 0 | Alters the topology of the target geometry by merging selected coordinates from the source geometry into the target geometry. Only those coordinates from the source geometry that are within the map-tolerance distance of the target geometry boundary are merged. Used during spatial editing of parcels to ensure parcels adjacent of the edit remain topologically consistent with any new parcels. | ||
| Function: cadastre_object_name_is_valid | 0 | Verifies that the name assigned to a new cadastre object is consistent with the cadastre object naming rules. | ||
| Function: generate_spatial_unit_group_name | 0 | Determines the hierarchical name to assign a new Spatial Unit Group. | ||
| Function: get_map_center_label | 0 | Returns a value that is displayed in the centre of the Public Display Maps for Systematic Registration. This function has default code that should be updated for each implementation of SOLA. | ||
| Function: get_new_cadastre_object_identifier_first_part | 0 | Used to determine the value for the first name part for a new cadastre object. This function has default code that should be updated for each implementation of SOLA to match the cadastre object naming conventions used by the implementing organisation. | ||
| Function: get_new_cadastre_object_identifier_last_part | 0 | Used to determine the value for the last name part for a new cadastre object. This function has default code that should be updated for each implementation of SOLA to match the cadastre object naming conventions used by the implementing organisation. | ||
| Function: snap_geometry_to_geometry | 0 | Snaps one geometry to the other adding points if required. Not used by SOLA. | ||
| hierarchy | 4 | First (highest) level of the hierarchical spatial unit group object of a hierarchical structure such as administrative rights. | ||
| hierarchy_level | 4 | Code list of hierarchy levels. Used by Systematic Registration functionalty when defining Spatial Unit Groups. Tags: FLOSS SOLA Extension, Reference Table |
||
| land_use_type | 3 | 4 | Code list of land use types. Identifies the general purpose of a cadastre object or property. E.g. Commerical, Residential, Industrial, etc. Implementation of the LADM ExtLandUse class. Tags: Reference Table, LADM Reference Object |
|
| legal_space_utility_network | 3 | 10 | LADM Defintion: A utility network concerns legal space, which does not necessarily coincide with the physical space of a utility network. Implementation of the LADM LA_LegalSpaceUtilityNetwork class. Not used by SOLA. Tags: LADM Reference Object, Change History, Not Used |
|
| level | 2 | 3 | 11 | LADM Definition: A set of spatial units, with geometric, and/or topological, and/or thematic coherence. EXAMPLE 1 - One level for an urban cadastre and another level for a rural cadastre. EXAMPLE 2 - One level with rights and another with restrictions. EXAMPLE 3 - One level with formal rights, a second level with informal rights and a third level with customary rights. EXAMPLE 4 - One level with point based spaital units, a second level with line based spatial units, and a third level with polygon based spatial features. Implementation of the LADM LA_Level class. Used by SOLA to identify the set of spatial features for each layer displayed in the Map Viewer. Tags: Reference Table, LADM Reference Object, Change History |
| level_config_map_layer | 2 | 2 | It provides for each level which layers in the map are used for visualisation | |
| level_content_type | 1 | 4 | Code list of level content types. E.g. geographicLocator, building, customary, primaryRight, etc. Implementation of the LADM LA_LevelContentType class. Tags: Reference Table, LADM Reference Object |
|
| place_name | 3 | View for retrieving place name features for display in the Map Viewer. Not used by SOLA. Layer queries (defined in system.query) are used instead. | ||
| register_type | 1 | 4 | Code list of register types. E.g. all, forest, mining, rural, urban, etc. Implementation of the LADM LA_RegisterType class. Tags: Reference Table, LADM Reference Object |
|
| road | 3 | View for retrieving road and road centreline features for display in the Map Viewer. Not used by SOLA. Layer queries (defined in system.query) are used instead. | ||
| spatial_unit | 5 | 5 | 14 | Single area (or multiple areas) of land, water or a single volume (or multiple volumes) of space. Implementation of the LADM LA_SpatialUnit class. Can be used by SOLA to represent geographic features such as place names and roading centrelines that are not considered as cadastre objects. Tags: LADM Reference Object, Change History |
| spatial_unit_address | 2 | 7 | Associates a spatial unit to one or more address records. Tags: FLOSS SOLA Extension, Change History |
|
| spatial_unit_group | 2 | 1 | 13 | Any number of spatial units considered as a single entity. Implementation of the LADM LA_SpatialUnitGroup class. Tags: LADM Reference Object, Change History |
| spatial_unit_in_group | 2 | 7 | Associates a spatial unit group to one or more spatial units. Implementation of the LADM LA_SpatialUnitGroup and LA_SpatialUnit relationship. Tags: LADM Reference Object, Change History |
|
| spatial_value_area | 2 | 8 | Identifies the area of a 2 dimensional spatial unit. Implementation of the LADM LA_AreaValue class. Tags: LADM Reference Object, Change History |
|
| structure_type | 1 | 4 | Code list of structure types. E.g. point, polygon, sketch, text, etc. Implementation of the LADM LA_StructureType class. Tags: Reference Table, LADM Reference Object |
|
| surface_relation_type | 1 | 4 | Code list of surface relation types. E.g. onSurface, above, below, mixed, etc. Implementation of the LADM LA_SurfaceRelationType class. Tags: Reference Table, LADM Reference Object |
|
| survey_control | 3 | View for retrieving survey control features for display in the Map Viewer. Not used by SOLA. Layer queries (defined in system.query) are used instead. | ||
| survey_point | 1 | 11 | Used to store new survey point details (i.e. boundary and traverse) when capturing a survey plan into SOLA. Survey points can be used to define new cadastre objects. Tags: FLOSS SOLA Extension, Change History |
|
| Trigger Function: f_for_tbl_cadastre_object_trg_geommodify | 0 | Function triggered on insert or update to the cadastre_object table. Uses the add_topo_points function to merge the topology of any parcels adjacent to parcel being updated. Only applied if the parcel being updated has a current status. | ||
| Trigger Function: f_for_tbl_cadastre_object_trg_new | 0 | Function triggered on insert to the cadastre_object table. Inserts a record in the spatial_unit table for the cadastre_object if no spatial_unit record for the new cadastre_object exists. | ||
| Trigger Function: f_for_tbl_cadastre_object_trg_remove | 0 | Function triggered on delete from the cadastre_object table. Cascade deletes the record in the spatial_unit table for the cadastre_object. | ||
| utility_network_status_type | 1 | 4 | Code list of utility network status types. E.g. inUse, outOfUse, planned, etc. Implementation of the LADM LA_UtilityNetworkStatusType class. Not used by SOLA. Tags: Reference Table, LADM Reference Object, Not Used |
|
| utility_network_type | 1 | 4 | Code list of utility network types. E.g. gas, oil, water, etc. Implementation of the LADM LA_UtilityNetworkType class. Not used by SOLA. Tags: Reference Table, LADM Reference Object, Not Used |
|
| 34 Tables | 167 | |||
| 4 Views | 13 |