Attribute Info

Attribute name	Description	Specification
data_custodian	the organisation that provided the data	Auto generated by Spatial Hub based on organisation providing the data.
object_id	The field identified is created automatically and is unique within each dataset. It is a function of each dataset and should not be used as a UID	Text string
record_id	Primary ID allowing it to be linked to further info in a database	Text string
site_name	The geographical name associated with the area	Text string
class	The CLASS field is the top level thesaurus term. Ideally, the data should be sourced from a Monuments Thesaurus.	Text string
type	The TYPE field is the second tier thesaurus term. (Actually, this should state the narrowest term)	Text string
polytype	The field differentiates between data where the shape of the polygon is meaningful and data where the form of the polygon is an arbitrary shape to enable data discovery. FORM or DISCOVERY	Text string
url	Where the LA record is available online, the link should be embedded.	Should be resolvable
source	This field gives the user information on what source was used to create the polygon.	Text string
accuracy	This field gives the user information on how confident they can be in the accuracy of the polygon. The field is linked to the accuracy of the source data. For instance, an area polygon created using survey equipment in the field is more accurate than a polygon created from 19th century 1st edition Ordnance Survey mapping	Text string
c_scale	The scale that the polygon was captured at in the GIS	Text string
notes	Free text descriptive note (Note: May be unlimited MEMO field if data is stored in a database). This will be truncated to 254 if the data is exported in a download format. If this is the case it is important to make sure key notes are stored in the first 254 characters of this field or the notes state: Long note: Please consult if truncated?	Text string
buffer	This field details the size of any buffer included in a polygon. The field should contain a number in metres or the word BESPOKE capitalised where a buffer of varying width has been used. If no buffer has been used, ?0? should be entered as the default entry.	Text string
contact	The entity responsible for providing more info about the feature upon request	Text string
comporg	This field provides the user with a guide to the organisation that created the polygon and populated the attribution.	Text string
compdate	The date the polygon is processed. This may also be the date the polygon was created but if this is not known, it is not essential.	Date.
editdate	Date of last edit of polygon.Knowing the date of update enables different parties to be sure they are using the same information.	Date
council	Local authority / Council area in which the feature is located	Text string
la_s_code	9-digit alpha/numeric unique ID, beginning with S (for Scotland), for the geographical area of each LA/NP.	Alphanumeric Text String. Auto-generated by Spatial Hub using current list from: https://statistics.gov.scot/resource?uri=http%3A%2F%2Fstatistics.gov.scot%2Fdata%2Fstandard-geography-code-register
sh_date_uploaded	Date on which the data was provided to the Spatial Hub.	Date. Auto-generated by Spatial Hub upon dataset registration. In format:yyyy-mm-dd
sh_src	Unique reference assigned to the LA/NP upload file. Used for reporting any issues back to LA.	Text String. Auto-generated by Spatial Hub upon dataset registration.
sh_src_id	ID for each record per Spatial Hub upload. Used for reporting any issues back to LA/NP.	Integer. Auto-generated by Spatial Hub upon dataset registration.

Additional Information

Field	Value
Updated	April 16, 2024
Metadata Updated	April 16, 2024
Metadata Created	unknown
Format	WFS
License	Other (Not Open)
Created	3 years ago
alternative name	herst
has views	False
id	4646dad6-e73d-41c2-8072-e333ac4e5d93
package id	c192dd22-6804-4f17-8f7d-c4fe9d8b5a52
position	1
state	active