The version of the Nomenclature Data Model has been updated to reflect that used to create a new Nomenclature system based on Oracle and an html user interface. The content of the class NAMED_FEATURE has not significantly changed, however other classes have been introduced to cater for attributes recorded in the original Nomenclature database. (eg MAPS25, MAPS100, COORDS)
These attributes (Classes) were not included in earlier versions of the model as it was intended that such relationships be determined through a spatial overlay. Whilst this will be possible, the link to spatial data will be delayed sufficiently to warrant this data being retained in the short term.
The attribute List_class will enable a connection to be made between the NAMED FEATURE and the relevant table in the database which records the detailed spatial definition of that feature.
There is a need to identify the first and last piece of correspondence in the relevant Nomenclature file which relates to the NAMED FEATURE. This will be managed through the attributes of From_folio and To_folio.
The Easting and Northing from the current database will be preserved for the time being, however over time it is expected that features will be referenced directly to the spatial representation in other LIST data sets and this will replace the need for a single coordinate pair.
A file managed by the Nomenclature Board may contain references to a number of NAMED FEATUREs. However information on a feature will only occur in one file as these are established on a spatial basis (1:100,000 map sheets).
The Class NAMED_FEATURE_EXTENT has been added to this model as it relates to the naming of features. This Class can also be used for the naming of indefinite features such as mountain ranges, Points, Plateaus etc.