each feature record needs an alias for migration and linking of MERLIN data

[geoderekh]

to allow linking of data in the geo props DB, each of these features needs to have an alias to act as a foreign key to the merlin. CPF_STRUCTURAL_UNITS.STRUCT_UNIT_KEY will be the alias, with an alias source "Merlin Structural Unit Key" and alias detail "Structural Unit key as migrated from MERLIN CPF_STRUCTURAL_UNITS"

[johnmckellar]

I presently do not have access to MERLIN, and thus the CPF_STRUCTURAL_UNITS TABLE. So, Derek would you please disentangle the following and advise what you require of us: “to allow linking of data in the geo props DB, each of these features needs to have an alias to act as a foreign key to the merlin. CPF_STRUCTURAL_UNITS.STRUCT_UNIT_KEY will be the alias, with an alias source "Merlin Structural Unit Key" and alias detail "Structural Unit key as migrated from MERLIN CPF_STRUCTURAL_UNITS".
Many thanks,
John

[geoderekh]

Apologies John, Following discussion with @KellyVance, we will likely be able to persist the MERLIN IDs into GeoProps Feature_PID because the notation of each feature class (which will be the prefix for the Feature PID) is unique. These MERLIN IDs (the structural unit key) will need to be added to each record so that we can make the links from site to feature. There are about 500000 such linkages in MERLIN.

[geoderekh]

CPF_STRUCTURAL_UNITS.xlsx

From the readme tab of the attached file:
CPF_STRUCTURAL_UNITS should be the source of data for the geofeatures dataset

The feature classes herein all have unique notations to act as PID prefixes to allow us to link MERLIN sites to features at migration. Between structural units and rock units (both are tables of features), there are 500000 such linkages.
The heirarchy presented in github (reproduced below) needs to be reformed to reflect the outcome of SWEET discussions. Note that some basins have a structural rank of "province" which probably must be changed. We need to add classes to reflect the feature types used in MERLIN (see next point below)
Current state |  
Geological Feature |  
  | Province |  
  |   | Sub Province
  |   | Orogen
  |   | Craton
  |   | Depression
  |   | Basin
  |   | Trough
  |   |  
The number of classes must be expanded to allow us to link all sites to features as they are linked in MERLIN. The list below is all of the classes in MERLIN, as metched and de-duped in the SUs linked to sites tab
Feature types in MERLIN
PROVIN |   |  
SUBPRO |   |  
SUPER |   |  
RIDGE |   |  
STRU |   |  
NOTQLD |   |  
MISCEL |   |  
OBSOLE |   |  
INLIER |   |  
IGNPRO |   |  
IGNSPR |   |  
BLOCK |   |  
  |   |  
There is an attribure called Preferred_structural_unit_key that im not sure of the relevance. Perhaps @BlakePaul can advise.
  |   |  
The only other important information in this table is the Parent_struct_unit_key attribute, but I think these feature relationships will need to be created after the go-live on June 30.