Go-Geo! Help - Metadata

Name	TITLE
identifier	1
Type	element
Parent entity group	AGMAP
Parent entity subgroup	Not Applicable
Definition	The name by which the dataset is known.
Obligation type	Mandatory (searchable)
Obligation detail	The Title element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	The Title element provides a field for entering the dataset?s title or formal title. Please provide a title that best describes that dataset. Include references to the subject, spatial and temporal aspects of the dataset. Jargon should be avoided so as to provide clarity to a broad audience from various disciplines. The leading letter and proper nouns of the title only should be capitalised. In the event that there are multiple titles, translations of titles (eg: Gaelic, Welsh), and titles with acronyms, these should be listed under the Alternative Title element field. In the event that it is necessary to include acronyms in the formal title of a dataset, then include both the acronym (in parentheses) and its definition.
Examples	List of Title examples presented under various academic disciplines. ARCHAEOLOGY AND ANTHROPOLGY: 1) A study of the distribution pattern of Iron Age archaeological sites in south-eastern England 2) Results of a resistivity and gradiometer geophysical survey conducted at a Neolithic site on Brown's Farm in Wiltshire, England BIOLOGICAL SCIENCES: 1) Population densities of hedgehogs across Great Britain 2) The incidence of ink disease amongst sessile Oak in Scotland CIVIL ENGINEERING: 1) An Inventory of wind-powered generators across the United Kingdom 2) Map of ground control point locations for United Kingdom surveyors EARTH SCIENCES: 1) Digital elevation model (DEM) map for Wales 2) The distribution of sandstone-based loamy soils of the Upper Thames Valley in Berkshire, England ENVIRONMENTAL SCIENCES: 1) The study of well water contamination and point source pollution across the United Kingdom 2) The incidence of coastal erosion in densely populated areas across eastern England GEOGRAPHY: 1) A landsat satellite-based 1995 land-use classification map for Essex, England 2) Scottish output area boundaries from the 1991 census 3) Panchromatic air photo map of Llandegai, near Bangor, Gwynedd HEALTH SCIENCES: 1) The incidence of smoke-related cancers amongst women in Aberdeenshire, Scotland from 1980 to 2002 2) Long-term health effects associated with beer consumption. A controlled study of population groups in the City of Glasgow, Scotland from 1950 to 1990 HISTORY: 1) Demographic and occupational data for Northern Ireland from 1901 to 1910 2) Examining changes to parish boundaries in Scotland during the nineteenth century SOCIOLOGY: 1) Drugs and crime in the urban setting: A trend analysis for urban areas across the United Kingdom, 1995 to 2000 2) A study of cultural perceptions of environmental risks in the United Kingdom

Name	CREATOR
identifier	3
Type	element
Parent entity group	G1: Citation (What)
Parent entity subgroup	Not Applicable
Definition	Organisation or person that developed the dataset and has primary responsibility for the intellectual content of the dataset.
Obligation type	Mandatory (searchable)
Obligation detail	The Creator element must have information entered in its field.
Max. occurrence type	Unlimited
Data type	Free text
Comments	The Creator element field should contain information about the person or organisation that assumes primary responsibility for the intellectual content of the dataset. This is not necessarily the person or organisation named as Custodian or Distributor for the dataset, or the Metadata Creator. The creator is not necessarily that person who owns the intellectual property rights of the dataset. The entry format should list title first, without full-stops, then surname, middle name or initials, again, without full-stops, and given name. If relevant, organisations should include department names. All acronyms and abbreviations should be contained in parentheses. Examples are provided below for individuals and organisations. Use of initials or full name is acceptable, though the full name and title is preferable to assure that the correct person can be identified. Some confusion could occur with several people sharing the same surname and first letter of their given names, e.g: J Doe could be Jane or John Doe.
Examples	Individuals: 1) Professor Doe, Jane 2) Dr Doe, Jane 3) Ms Doe, Jane 4) Miss Doe, Jane 5) Mrs Doe, Jane 6) Doe, Mary Jane 7) Doe, M Jane 8) Doe, Jane 9) Mr Doe, John Organisations: 1) EDINA, University of Edinburgh 2) School of Geosciences, Department of Geography, University of Edinburgh 3) Edinburgh Centre for Rural Research, University of Edinburgh

Name	ALTERNATIVE TITLE
identifier	2
Type	element
Parent entity group	G1: Citation (What)
Parent entity subgroup	Not Applicable
Definition	Short name, other name, acronym or alternative language title.
Obligation type	Optional
Obligation detail	The Alternative Title element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Unlimited
Data type	Free text
Comments	The Alternative Title element allows for entries of multiple titles, translations of titles (e.g: Cornish, Gaelic, Welsh), and those with acronyms. The leading letter and proper nouns of the title only should be capitalised. In the event that the alternative title includes acronyms in the formal title of a dataset, then include both the acronym (in parentheses) and its definition. Acronyms should not include full-stops between each letter.
Examples	List of Alternative Title examples presented under various academic disciplines (return to p12) (Alternative Title element, Identifier 2) ARCHAEOLOGY AND ANTHROPOLGY: 1) Iron Age settlement patterns in south-eastern England 2) Brown?s Farm geophysical survey in Wiltshire, England BIOLOGICAL SCIENCES: 1) Population densities of hedgehogs (Erinaceus europaeus) across Great Britain 2) Ink disease amongst sessile oak/darach (Quercus petraea) in Scotland CIVIL ENGINEERING: 1) An inventory of WPGs across the UK 2) Map of GCP locations in the UK EARTH SCIENCES: 1) DEM map for Wales 2) Mapped sandstone-based loamy soils of the Upper Thames Valley in Berkshire ENVIRONMENTAL SCIENCES: 1) Well water contamination and pollution sources across the UK 2) Erosion impact on eastern English coastline communities GEOGRAPHY: 1) Essex: A 1995 land-use classification map 2) Scottish OAs 3) Map o awyrlun o Landygái, ger Bangor, Gwynedd HEALTH SCIENCES: 1) Smoke-related cancer cases amongst female cohorts in Aberdeenshire, Scotland from 1980 to 2002 2) Long-term effects of beer consumption. Results from a Glasgow, Scotland study conducted from 1950 to 1990 HISTORY: 1) Early 20th century demographic and occupational data for Northern Ireland 2) Parish boundary changes of the 19th century in Scotland SOCIOLOGY: 1) A trend analysis study on drugs and crime in urban areas across the UK 2) Cultural perceptions of environmental risks in the UK

Name	SPATIAL REPRESENTATION TYPE
identifier	15
Type	element
Parent entity group	G2: Identification Information (What)
Parent entity subgroup	Not Applicable
Definition	Method used to spatially represent geographic information.
Obligation type	Optional
Obligation detail	Spatial Representation Type element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Unlimited
Data type	Free text
Data type domain	ISO 19115 B.5.26 (MD_SpatialRepresentationTypeCode) 1. vector 001 Vector data is used to represent geographic data. 2. grid 002 Grid data is used to represent geographic data. 3. textTable 003 Textual or tabular data is used to represent geographic data. 4. tin 004 Triangulated Irregular Network. 5. stereoModel 005 Three-dimensional view formed by the intersecting homologous rays of an overlapping pair of images. 6. video 006 Scene from a video recording.
Comments	Vector data is the storage of X, Y, Z coordinates connected to form points, lines, areas, and volumes. Vector data is best suited to store discrete, well-defined data that can clearly be delimited. These data can represent features such as roads, rivers, buildings and wells. Grid data provides a matrix of pixels arranged in rows and columns which form images that can be displayed on a computer screen. Aerial and satellite photos and digital elevation models are examples of grid data. A Text Table contains text values in a comma or tab delimited format. A Tin (Triangulated Irregular Network) is a surface representation derived from irregularly spaced points and breakline features. Each sample point has an x, y coordinate and a z value or surface value. A Stereo Model is a three-dimensional view formed by the intersecting homologous rays of an overlapping pair of images. A Video is a scene from a video recording representing a film clip or animation. A video could be a simulated flyover across a three-dimensional elevation terrain model or a film capturing information or monitoring activities at a location which can be spatially referenced. A video monitor might track population movement and numbers at selected study areas.

Name	IDENTIFIER
identifier	4
Type	element
Parent entity group	G1: Citation (What)
Parent entity subgroup	Not Applicable
Definition	A unique string or number used to identify the dataset.
Obligation type	Optional
Obligation detail	The Identifier element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	The Identifier element provides the option of entering a unique string or number that identifies the dataset in a given context. Many datasets are assigned unique strings or numbers for the purpose of identifying individual datasets. If your organisation follows the same practice, the entry of the dataset?s identifier in this element?s field will serve as a useful tracking code to access information about the dataset. If the identifier code is embedded into the metadata file name, which can be cross-referenced on a spreadsheet, this would provide an expeditious means for locating the dataset to answer internal or external enquiries about it. There are a number of identifiers that are recognised and used internationally. One of the more common identifiers, the ISSN (International Standard Serial Number), is an eight-digit number, which references and identifies periodical or serial publications. The ISBN (International Standard Book Number) is a unique machine-readable identification 10 digit number that is assigned to individual monographs (books). Maps, microform publications, pamphlets, software and multimedia kits with printed material can also be included for ISBN numbers. In addition to these, there are other types of identifiers. European Article Numbers (EANs) and Universal Product Codes (UPCs) are used as bar codes. Digital Object Identifiers (DOI) are commonly used for digital commerce. Uniform Resource Locator (URL), Uniform Resource Identifier (URI), Uniform Resource Name (URN) and Persistent (Uniform Resource Locator), or PURL, are used to identify and locate web resources. The recently approved ISAN (International Standard Audiovisual Number) is a voluntary numbering system used for referencing and identifying audiovisual works. The ISAN is a 16 digit code.
Examples	1) ISBN:L 00 101 020 12 2) ISBN: 00-101-020-12 3) ISSN: 0010-1012 4) ISAN: 123456787654-4321 5) http://identifier.ac.uk

Name	EDITION
identifier	5
Type	element
Parent entity group	G1: Citation (What)
Parent entity subgroup	Not Applicable
Definition	The number of the edition of the dataset.
Obligation type	Mandatory
Obligation detail	The Edition element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	The Edition element provides a field to enter the dataset edition. Typically datasets with periodic releases are assigned edition numbers. There is no need to write Edition in the field. Please include a reference to the original edition to get a sense of the number of editions that fall under a dataset. An example would be to write it as follows: 1.6 of 2.0. This element can provide a potential dataset user the information about the existence of earlier editions of the dataset. The user can match dataset editions to track changes made to the dataset, especially if there is a need to make comparisons between editions should a fee payment structure be in place. As an example, an edition 1.0 dataset may cost less than an edition 2.0 version. A potential user may have interest in an area that was not revised during changes made to the dataset, so it would be more cost-effective if he/she were to acquire the edition 1.0 version of the dataset. Data developers who do not support a edition scheme for their datasets have several options. Because this element requires an entry in its field, the data developer can establish an internal scheme to assign editions to datasets. The edition increments could done in ones (1.0, 2.0, 3.0) or tenths (1.1, 1.2, 1.3), etc., depending on the types of changes made to the dataset. Additions and subtractions to datasets would constitute the necessary conditions for changes to dataset versions. Edits to datasets might be treated as not significant enough to warrant changes to a version update. If a data developer doesn?t wish to track changes made to a dataset, please enter a default version of 1.0 and leave it at that. It is recommended that a version scheme is employed.
Examples	1) 1.0 2) 1 3) First 4) 1.5 of 2.0

Name	DATASET DATE CODE
identifier	6
Type	element
Parent entity group	G1: Citation (What)
Parent entity subgroup	Not Applicable
Definition	Identification of when a given dataset event occurred.
Obligation type	Mandatory
Obligation detail	The Dataset Date Code element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Data type domain	ISO 19115 B.5.2 (CI_DateTypeCode) 1) creation 001 Date identifies when the resource was brought into existence. 2) publication 002 Date identifies when the resource was issued. 3) revision 003 Date identifies when the resource was examined or re-examined and improved or amended. *4) deletion Not an ISO 19115 value but added in anticipation of amendment to ISO 19115 to address the complete life cycle of a dataset.
Comments	Select the term from the list that best defines the dataset?s event. The selection of the dataset event can be based on intent. If a dataset is documented for internal data management purposes, the creation event value on the list might be most appropriate because this announces to other organisation users that the dataset has been completed. The creation date in this instance pertains to the actual completion date of the dataset as opposed to the G3.1-22 Status of the Data Creation Process element, which is directed at the process status of the dataset. Post-process reviews of a dataset might take place before a dataset is declared created. If a dataset is to be shared or made available to the open public, then the publication event value should be selected. This pertains to the actual date when the dataset is being made available or released for use. This supersedes the creation event, but it is to the discretion of the dataset custodian to determine whether to create a separate metadata record for each event or switch from one event value to the other in the original metadata record. The basic criterion that separates the two events is the decision to share or manage a dataset. However, it can be left to the discretion of each organisation to decide whether to use one or both values, as long as there is an adherence to consistency in practice. When a dataset is revised, it is recommended that the dataset custodian creates a new metadata record. The revision value implies that a dataset has been changed as a consequence of edits or updates. These changes should be reflected in the metadata record, hence requiring a new record and retention of the old record so that data users can track changes of a dataset over the course of its life cycle. Deletion is not an ISO 19115 value but was added in anticipation of a future amendment to ISO 19115 which would cover the complete life cycle of a dataset. There will be instances when datasets are deleted, especially those derived from licensed data which would require the data developer to delete the dataset in the event of a change in status (e.g.: a student leaving academia who has used Digimap OS datasets). If a dataset is deleted, its metadata record could be retained so that other data developers can reference it to recreate the same dataset. The dataset developer can consider using Status of Data Creation Process (G3.1-22) list value of ?Obsolete? as a solution. The Description element (G2-14) can also be amended with a reference to the dataset?s deletion.
Examples	1) Creation (Refers to event when dataset was created). 2) Publication (Refers to event when created dataset was published for released for users, both internal and external). 3) Revision (Refers to event when created dataset was revised as part of updates and edits). 4) Deletion (Refers to event when created dataset was permanently deleted).

Name	DATASET EVENT DATE
identifier	7
Type	entity
Parent entity group	G1: Citation (What)
Parent entity subgroup	Not Applicable
Definition	The Dataset Event Date element must have information entered in its field.
Obligation type	Mandatory
Obligation detail	The Dataset Event Date element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Data type domain	YYYY-MM-DD
Comments	Enter the date when the dataset event occurred. If possible, please enter the date to the day. If unknown, enter the month and year or, if the month is not known, enter only the year. The date format is based on ISO 8601, which is expressed as YYYY-MM-DD (Year-Month-Day), and uses hyphens ( - ) as separators. It is based on the Gregorian Calendar but denoted using the Common Era Calendar format.
Examples	1) 2001-01-31 (Entire date known, including year, month and day day) 2) 2001-01 (Year and month of date known, but not day) not day) 3) 2001 (Year known, but not month and day)

Name	DATASET UPDATE FREQUENCY
identifier	8
Type	element
Parent entity group	G1: Citation (What)
Parent entity subgroup	Not Applicable
Definition	The frequency with which revisions and updates are made to the dataset after its initial completion.
Obligation type	Mandatory
Obligation detail	The Dataset Update Frequency element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Data type domain	ISO 19115 B.5.18 (MD_MaintenanceFrequencyCode) 1) continual 001 Data is repeatedly and frequently updated. 2) daily 002 Data is updated each day. 3) weekly 003 Data is updated on a weekly basis. 4) fortnightly 004 Data is updated every two weeks. 5) monthly 005 Data is updated each month. 6) quarterly 006 Data is updated every three months. 7) biannually 007 Data is updated twice each year. 8) annually 008 Data is updated every year. 9) asNeeded 009 Data is updated as deemed necessary. 10) irregular 010 Data is updated in intervals that are uneven in duration. 11) notPlanned 011 There are no plans to update the data. 12) unknown 012 Frequency of maintenance for the data is not known.
Comments	Select the term from the list that best defines the time frequency established for dataset revisions and updates.
Examples	None

Name	DATASET LANGUAGE
identifier	9
Type	element
Parent entity group	G2: Identification Information (What)
Parent entity subgroup	Not Applicable
Definition	The language(s) used within the dataset.
Obligation type	Mandatory
Obligation detail	The Language element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Data type domain	ISO 639.2 Language Codes 1) ENG English 2) COR Cornish 3) GLA Gaelic (Scottish) 4) GLE Gallic (Irish) 5) WEL or CYM Welsh
Comments	Select the relevant language from the list using the corresponding three letter codes for English, Gaelic (Scottish), Gallic (Irish) and Welsh. If more than one language is selected, then please provide a brief explanation in the Description element?s field. This may occur if, for example, a study of place name distribution patterns has been conducted in Wales. The list of place names in the database table could include, in each instance, the Welsh name and its English equivalent.
Examples	None

Name	DATASET TOPIC
identifier	10
Type	element
Parent entity group	G2: Identification Information (What)
Parent entity subgroup	Not Applicable
Definition	Main theme(s) of the dataset.
Obligation type	Mandatory
Obligation detail	The Topic element must have information entered in its field.
Max. occurrence type	Unlimited
Data type	Free text
Data type domain	ISO 19115 B.5.27 (MD_TopicCategoryCode) 1) farming 001 rearing of animals and/or cultivation of plants Examples: agriculture, irrigation, aquaculture, plantations, herding, pests and diseases affecting crops and livestock 2) biota 002 Flora and/or fauna in natural environment. 3) boundaries 003 Legal land descriptions. 4) climatologyMeteorologyAtmosphere 004 Processes and phenomena of the atmosphere. 5) economy 005 Economic activities, conditions and employment. 6) elevation 006 Height above or below sea level. 7) environment 007 Environmental resources, protection and conservation. 8) geoscientificInformation 008 Information pertaining to earth sciences. 9) health 009 Health, health services, human ecology and safety. 10) imageryBaseMapsEarthCover 010 Base maps. 11) intelligenceMilitary 011 Military bases, structures, activities. 12) inlandWaters 012 Inland water features, drainage systems and their characteristics. 13) location 013 Positional information and services. 14) oceans 014 Features and characteristics of salt water bodies (excluding inland waters). 15) planningCadastre 015 Information used for appropriate actions for future use of the land. 16) society 016 Characteristics of society and cultures. 17) structure 017 Man-made construction. 18) transportation 018 Means and aids for conveying persons and/or goods. 19) utilitiesCommunication 019 Energy, water and waste systems and communications infrastructure and services.
Comments	The Topic element provides a thematic classification for geographic data. It groups datasets under more general terms for the purpose of topical keyword searches. The Topic element comprises a list of words that describe the main subject of the dataset. This list originates from the International Standards Organisation (ISO) 19115 topic list. There are 19 topic names available from which to choose. Select the topic or topics that best represent the dataset's theme. See examples for more detailed definitions.
Examples	NAME: [Definition and Examples] FARMING: Rearing of animals and/or cultivation of plants. [Agriculture; Irrigation; Aquaculture; Plantations; Herding; Pests and Diseases affecting Crops and Livestock] BIOTA: Flora and/or fauna in natural environment. [Wildlife; Vegetation; Biological Sciences; Ecology; Wilderness; Sea Life; Wetlands; Habitat] BOUNDARIES: Legal land descriptions. [Political and Administrative Boundaries] ClIMATOLOGY/METEOROLOGY/ATMOSPHERE: Processes and phenomena of the atmosphere. [Cloud cover; Weather; Climate; Atmospheric conditions; Climate change; Precipitation] ECONOMY: Economic activities, conditions and employment. [Production; Labour; Revenue; Commerce; Industry; Tourism and Eco-tourism; Forestry; Fisheries; Commercial or Subsistence Hunting; Exploration and Exploitation of Resources such as Minerals; Oil and Gas] ELEVATION: Height above or below sea level. [Altitude; Bathymetry; Digital Elevation Models (DEMs); Slope Derived Products] ENVIRONMENT: Environmental resources, protection and conservation. [Environmental pollution; Waste Storage and Treatment; Environmental Impact Assessment; Monitoring Environmental Risk; Nature Reserves; Landscape] GEO-SCIENTIFIC INFORMATION: Information pertaining to earth sciences. [Geophysical Features and Processes; Geology; Minerals; Sciences dealing with the Composition, Structure and Origin of the Earth?s Rocks; Risks of Earthquakes; Volcanic Activity; Landslides; Gravity Information; Soils; Permafrost; Hydrogeology; Erosion] HEALTH: Health, health services, human ecology and safety. [Disease and Illness; Epidemiology; Factors affecting Health; Hygiene; Substance Abuse; Mental and Physical Health; Health Services] IMAGERY/BASE MAPS/EARTH COVER: Base maps. [Land Cover; Topographic Maps; Imagery; Unclassified Images; Annotations] INTELLIGENCE/MILITARY: Military bases, structures and activities. [Barracks; Training Grounds; Military Transportation; Information Collection] INLAND WATERS: Inland water features, drainage systems and their characteristics. [Rivers and Glaciers; Salt Lakes; Water Utilisation Plans; Dams; Currents; Floods; Water Quality; Hydrographic Charts] LOCATION: Positional information and services. [Addresses; Geodetic Networks; Control Points; Postal Zones and Services; Place Names] OCEANS: Features and characteristics of salt water bodies (excluding inland waters). [Tides; Tidal Waves; Coastal Information; Reefs] PLANNING/CADASTRE: Information used for appropriate actions for future use of the land. [Land-use maps; zoning maps; cadastral surveys; land ownership] SOCIETY: Characteristics of society and cultures. [Settlements; Anthropology; Archaeology; Education; Traditional Beliefs; Manners and Customs; Demographic Data; Recreational Areas and Activities; Social Impact Assessments; Crime and Justice; Census Information] STRUCTURE: Man-made construction. [Buildings; Museums; Churches; Factories; Housing; Monuments; Shops; Towers] TRANSPORTATION: Means and aids for conveying persons and/or goods. [Roads; Airports/Airstrips; Shipping Routes; Tunnels; Nautical Charts; Vehicle or Vessel Location; Aeronautical Charts; Railways] UTILITIES/COMMUNICATION: Energy, water and waste systems and communications infrastructure and services. [Hydroelectricity; Geothermal; Solar and Nuclear Sources of Energy; Water Purification and Distribution; Sewage Collection and Disposal; Electricity and Gas Distribution; Data Communication; Telecommunication; Radio; Communication Networks] Examples (format for values entered manually): 1) farming 2) planningCadastre 3) utilitiesCommunication

Name	CONTROLLED VOCABULARY
identifier	11
Type	element
Parent entity group	G2: Identification Information (What)
Parent entity subgroup	Not Applicable
Definition	Name of the controlled vocabulary used as a source for the controlled keywords.
Obligation type	Mandatory (searchable)
Obligation detail	The Controlled Vocabulary element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Data type domain	UNESCO Thesaurus. See comments.
Comments	The UNESCO thesaurus has been selected as the best source for controlled keywords, thus it is the default input for the controlled vocabulary field. The Controlled Vocabulary element was created in the event that another controlled keyword thesaurus could be added at a later date.
Examples	1) UNESCO

Name	CONTROLLED KEYWORDS
identifier	12
Type	element
Parent entity group	G2: Identification Information (What)
Parent entity subgroup	Not Applicable
Definition	Keywords taken from a controlled vocabulary summarising the subject of the dataset.
Obligation type	Mandatory (searchable)
Obligation detail	The Controlled Keywords element must have information entered in its field.
Max. occurrence type	Unlimited
Data type	Free text
Data type domain	Controlled Keywords selected from UNESCO Thesaurus. See comments.
Comments	These are controlled keywords that are found in the UNESCO thesaurus and are used to describe the subject or theme of the dataset. Enter a list of keywords that best describe the detailed subject information about the dataset. The on-line Go-Geo! metadata editor tool is designed to provide the metadata creator direct access to the UNESCO thesaurus, though as another option, the thesaurus can be accessed through the following link: http://www.ulcc.ac.uk/unesco/ Here, keywords may be browsed alphabetically and hierarchically. Enter those keyword terms that best describe the dataset. As a means to simplify the process for metadata creators, it is advised that metadata records be submitted without the controlled keywords. The Go-Geo! metadata co-ordinator will take responsibility for entering the keywords to the metadata record and returning it to the metadata creator for review and approval.
Examples	A sample list of Controlled Keyword examples presented under various academic disciplines. (Terms selected from UNESCO thesaurus) ARCHAEOLOGY AND ANTHROPOLGY: 1) Archaeology, Archaeological Sites, Ancient History, Antiquity, Iron Age, Settlement Patterns, Commerce, Landscape, Trade, Maps 2) Archaeology, Archaeological Sites, Ancient History, Antiquity, Neolithic Age, Physics, Geophysical Prospecting, Surveys, Field Work BIOLOGICAL SCIENCES: 1) Biology, Animal Biology, Biological Research, Zoology, Ecosystems, Population Density, Fauna, Animals, Mammals, Pest Control, Maps 2) Biology, Plant Biology, Botany, Biological Research, Ecosystems, Biological Control, Trees, Plant Diseases, Vegetation Maps CIVIL ENGINEERING: 1) Civil Engineering, Natural Resources, Renewable Energy Sources, Winds, Wind Power, Maps 2) Civil Engineering, Surveying, Surveys, Geodesy, Maps, Satellites EARTH SCIENCES: 1) Topography, Models, Maps 2) Soils, Soil Surveys, Soil Maps, Rocks, Sedimentary Rocks, ENVIRONMENTAL SCIENCES: 1) Hydrology, Drinking Water, Wells, Aquifers, Ground Water, Water Resources, Water Supply, Water Treatment, Environmental Health, Pollution, Water Pollution, Soil Pollution, Agricultural Waste, Contaminates, Waste, Lead, Water Treatment 2) Erosion, Coastal Erosion, Soil Erosion, Coastal Zones, Landslides, Damage, Harbor and Coastal Engineering, Human Activities Effects, Communities, Houses, Urban Development GEOGRAPHY: 1) Remote Sensing, Land use, Maps, Satellites 2) Boundaries, Population Censuses, Statistical Data, Demography 3) Aerial Photography, Maps HEALTH SCIENCES: 1) Health, Women, Diseases, Cancer, Smoking, Death, Mortality, Everyday Life, Cultural Life, Working Life, Smoking, Diet, Social Stratification, Population, Females, Environmental Health, Contaminates 2) Health, Alcoholic Beverages, Beer, Addiction, Mortality, Quality of Life, Group Size, Target Groups HISTORY: 1) Social History, Demographic Statistics, Population Censuses, Population Dynamics, Age Groups, Birth Rate, Mortality, Life Expectancy, Nuptiality, Immigration, Emigration, Employment, Occupations, Social Status, Agriculture, Agroforestry, Fishing Industry, Industry, Manufacturing Industry 2) Social History, Political History, Boundaries SOCIOLOGY: 1) Crime, Drug traffic, Youth Unrest, Social Problems, Domestic Violence, Addiction, Drug Abuse, Urban Population, Urban Sociology, Urban Youth, Heroin, Cocaine 2) Risk Assessment, Environmental Awareness, Cultural Behaviour, Perception, Cultural Identity, Ethno-Psychology, English, Welsh, Natural Disasters, Landslides, Earthquakes, Floods, Storms, Global Warming, Ozone, Hazardous Materials, Nuclear Wastes, Radioactive Wastes, Environmental, Endangered Species

Name	OTHER KEYWORDS
identifier	13
Type	element
Parent entity group	G2: Identification Information (What)
Parent entity subgroup	Not Applicable
Definition	Other words or phrases summarising the subject of the dataset.
Obligation type	Optional
Obligation detail	Optional and searchable. The Other Keywords element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Unlimited
Data type	Free text
Comments	This element allows the metadata creator to enter other keywords that are not found in the UNESCO thesaurus but which are useful for summarising the subject content of the dataset. These keywords are especially useful for very specific terms that may be better known within the respective discipline and provide users with the ability to narrow their searches further.
Examples	A sample list of Other Keyword (Terms without a thesaurus source) examples presented under various academic disciplines. ARCHAEOLOGY AND ANTHROPOLGY: 1) Celts, Romans, Hillforts, Enclosures, Point Coverage 2) Geophysical Survey, Gradiometer, Magnetometer, Resistivity, Resistance, Magnetics, Anomalies, Raster Images, GPS, Global Positioning System, GPR, Ground Penetrating Radar BIOLOGICAL SCIENCES: 1) Hedgehogs, Shrews, Moles 2) Oak, Sessile Oak, Ink Disease CIVIL ENGINEERING: 1) Wind Turbines, Coriolis Force, Anemometers, Wind Shear, Prevailing Wind Direction, Sea Winds, Electrical Grid, Megawatt 2) Ground Control Points, GCP, Global Positioning System, GPS EARTH SCIENCES: 1) Digital Elevation Model, DEM, Digital Terrain Model, DTM, Raster Grid, Elevation 2) Loam, Sandstone, Polygon Coverage ENVIRONMENTAL SCIENCES: 1) Micro-organisms, Coliforms, Chlorine, Inorganic Chemicals, Arsenic, Asbestos, Copper, Organic Chemicals, Nitrite, Benzine, Atrazine, Clay, Loam, Silt, Sand, Depth, pH, Alkaline, Acidic 2) Coastal Defences, Hard Defences GEOGRAPHY: 1) Landsat Thematic Mapper 5, Landsat TM 5, Supervised Classification 2) Output Areas, Scottish 3) Air Photos, Panchromatic HEALTH SCIENCES: 1) Lung Cancer, Oesophagal Cancer, Breast Cancer, Chemotherapy, Treatment, Cigarettes, Packs, Cohorts, Hazardous Chemicals 2) Pints, Litres, Treatment, Health Benefits, Health Risks, Cohorts HISTORY: 1) Borough, County, Forestry, Fishing, Fishing, Death Rate, Marriage Rate 2) Scottish, Parish, Registration Districts SOCIOLOGY: 1) Burglary, Robbery, Overdose Rate, Relapse Rate, Cure Rate 2) Northern Irish, Scottish, Tornadoes, Ozone Depletion, Hazardous Waste Sites

Name	ABSTRACT
identifier	14
Type	element
Parent entity group	G2: Identification Information (What)
Parent entity subgroup	Not Applicable
Definition	A brief description of the dataset. This should include some explanation as to why the dataset was produced and how it has been used since its creation.
Obligation type	Mandatory (searchable)
Obligation detail	The Abstract element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	The Abstract element is intended to provide information about the dataset content, the source data and the reasons for creating the dataset. There is no limitation to the amount of text that can be written, however, it is best to write a concise abstract that best describes all of the dataset?s details and summarises how the dataset was used or applied in the context of the relevant project or study.
Examples	Abstract examples presented under various academic disciplines. These correspond with first examples presented for Dataset Title, Alternative Dataset Title, Controlled Keywords, Other Keywords and Related Dataset elements. ARCHAEOLOGY AND ANTHROPOLGY: 1) This dataset is a point coverage showing the distribution pattern of Iron Age sites in south-eastern England. This dataset was created as part of another study at the University of Essex that examines commercial and trade networks between Roman and the indigenous populations situated in this region. The study area is restricted to the counties of Kent, East and West Sussex and Surrey. Data collection is quite extensive for this area and was derived from various field surveys conducted over intermittent periods from 1922 to 1995. The point coverage includes 188 sites that are associated with indigenous and Roman populations. Attribute information for the point coverage includes site occupation dates, site types, material culture and site size. BIOLOGICAL SCIENCES: 1) This dataset was created as part of a University of Essex Department of Zoology?s study to assess population densities of hedgehogs across Great Britain and examine their impact on local bird populations. The study areas include England, Scotland and Wales. Teams of research students, in groups of ten, were sent across Britain during the summers of 1996 to 1997 to observe and collect hedgehog population counts. A grid system map layer using 30 x 30 kilometre cells was imposed as part of the collection strategy. A locational map layer was also generated as an aid for field teams to use for navigation. In addition, a Landsat satellite image was processed to create a land classification map that revealed potential habitat areas for hedgehogs. The Landsat-derived map was superimposed as a layer over the grid and locational maps with the three being merged together. In addition to these maps, the research teams used global positioning system technology (GPS) to navigate their way in the field and locate the hedgehog habitat areas. Subsequently, the population data were collected and used to generate a polygon feature coverage, which presented estimated hedgehog population densities across Britain. CIVIL ENGINEERING: 1) This dataset represents an inventory of wind-powered generators across the United Kingdom. The study area includes England, Northern Ireland, Scotland and Wales and is part of an effort to assess current and future placement of generators. The survey was conducted in 1994. The aim of the inventory is to collect data and assess the current state of turbine facility installations and electrical grid infrastructure in the United Kingdom. The results of this study will be used for planning future wind turbine facilities. These results will examine the correlations between wind turbines and design and prevailing wind patterns. Global positioning system technology (GPS) was used to collect co-ordinates and elevations for each generator station. These co-ordinates were later converted to a point coverage, which included attribute information about each generator station. This included station orientation, turbine blade sizes, electrical output, years in service and shutdown periods. EARTH SCIENCES: 1) The Digital Elevation Model (DEM) Map for Wales represents a three-dimensional (3-D) elevation model, which covers the entire nation of Wales. This DEM is converted into a raster grid cell format and was derived from scanned 1997 aerial photographs of Wales. The DEM?s grid cell resolution is 30 x 30 metres and this can be suitable for generating slope, aspect, watershed and viewshed models and elevation contour maps. These can be combined with other raster and vector datasets to generate slope stability and landslide probability maps, water runoff models and visibility assessment models. Two-dimensional aerial photographs and satellite images can also be draped over the Wales DEM to create a 3-D visual display to simulate a landscape scene. Some GIS software packages offer tools that can simulate a fly-over across a 3-D scene. ENVIRONMENTAL SCIENCES: 1) The results of a study in 1996 of well water contamination and source pollution across the United Kingdom included a point coverage dataset for all wells. The purpose of the study was to create an inventory of all abandoned and operational wells across the UK. The total number of wells reached 2,350 in count. Water samples were collected and analysed for organic, inorganic and chemical contaminates. Location of the wells was established though liaisons with local government agencies and locational accuracy was improved with the use of Global positioning system technology (GPS). Coring tests were also conducted to determine soil types and geological maps were referenced to identify the local bedrock. The results revealed that only 8 percent of the operational wells had various levels of contamination. Sources of pollution contamination were traced and found for almost 80 percent of these wells. Abandoned wells accounted for 76 percent of all wells and of these, 68 percent had various levels of contamination. The pollution source was found for only 22 percent of these wells. GEOGRAPHY: 1) This 1995 Essex land-use classification dataset is derived from a Landsat 5 Thematic Mapper satellite-based image. The satellite captured the image on the 19th May, 1994 and it was subsequently processed and converted from a raster image to a vector file format. A supervised classification was performed on the raster imagery and 25 classes were created, which represent various types of land cover. In general, this includes water, arable land, grass and moors, woodlands and urban areas. Once converted to these classes, the raster image was converted into a vector format with each raster class becoming a polygon. The Essex land-use map can be used for planning and managing resources and monitoring changes to the landscape that occur with land development and effects of natural events. HEALTH SCIENCES: 1) A health study was conducted that tracked lung cancer rates amongst women in Aberdeenshire County, Scotland from 1980 to 2002. The study examined age, status, diet, smoking and drinking habits and environmental hazards. It also provides information about cancer and morbidity rates and types of cancers, treatment methods and survival rates. The dataset holds information collected at the household level across the county. The data have been stored in tabular format and include street address references for those interested in mapping distribution patterns or supplementing other datasets. Specific addresses were not provided to assure individuals? privacy. HISTORY: 1) Census data from 1901 to 1910 were collected for Northern Ireland to examine demographic and occupational trends for this period of time. This is part of another study to examine the political and social changes occurring in Northern Ireland at the turn of the century and just prior to the first world war. The data are sorted at the county level and stored in a tabular format. SOCIOLOGY: 1) This study examines the correlation between drugs and crime in the urban setting across the United Kingdom between 1995 and 2000. The cities of London, Manchester, Birmingham, Glasgow, Belfast and Cardiff were included in the study. Data were collected at the ward level and included drug arrests, drug-related crimes and drug overdoses. These data were stored in tabular format and linked to GIS-based ward boundary files available for each of the cities. The study also examined treatment programmes and evaluated their success and failure rates. These rates were then compared to changes in drug arrests, drug-related crimes and drug overdoses to determine if there were any correlations between them.

Name	PRESENTATION TYPE
identifier	16
Type	element
Parent entity group	G2: Identification Information (What)
Parent entity subgroup	Not Applicable
Definition	Form in which the dataset is available.
Obligation type	Optional
Obligation detail	Presentation Type element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Unlimited
Data type	Free text
Data type domain	ISO 19115 B.5.4 (CI_PresentationFormCode) 1) documentDigital 001 Digital representation of a primarily textual item (can contain illustrations also). 2) documentHardcopy 002 Representation of a primarily textual item (can contain illustrations also) on paper, photographic material, or other media 3) imageDigital 003 Likeness of natural or man-made features, objects, and activities acquired through the sensing of visual or any other segment of the electromagnetic spectrum by sensors, such as thermal infrared, and high resolution radar and stored in digital format. 4) imageHardcopy 004 Likeness of natural or man-made features, objects, and activities acquired through the sensing of visual or any other segment of the electromagnetic spectrum by sensors, such as thermal infrared, and high resolution radar and reproduced on paper, photographic material, or other media for use directly by the human user. 5) mapDigital 005 Map represented in raster or vector form. 6) mapHardcopy 006 Map printed on paper, photographic material, or other media for use directly by the human user. 7) modelDigital 007 Multi-dimensional digital representation of a feature, process, etc. 8) modelHardcopy 008 Three-dimensional, physical model. 9) profileDigital 009 Vertical cross-section in digital form. 10) profileHardcopy 010 Vertical cross-section printed on paper, etc. 11) tableDigital 011 Digital representation of facts or figures systematically displayed, especially in columns 12) tableHardcopy 012 Representation of facts or figures systematically displayed, especially in columns, printed on paper, photographic material, or other media. 13) videoDigital 013 Digital video recording. 14) videoHardcopy 014 Video recording on film.
Comments	Select one or more of the terms from the list that best describes the presentation of the dataset made available to the user. Presentation can be in the form of digital and/or hard copy in document, image, map, model, profile, table and/or video formats. Typically hard copy datasets are presented on paper and digital datasets as electronic files. Documents, images, models, profiles, tables and videos must have a spatial context and reference in order to be considered relevant; maps provide spatial representation. ? A document pertains to a text (words and sentences) dataset. The text could provide a description of a place or observations made there. ? An Image can be a still aerial and satellite photograph. Images might also represent photographs of locations comparable to those in the British Geological Survey Photographic Collection. ? A map is a spatial representation, usually graphic on a flat surface, of spatial phenomena. ? A model is a data representation of reality such as landscape features. A model can be the result of applied structural rules and procedures to one or more spatial data overlays to conduct spatial analysis to derive new information to assist in problem solving and planning. A model can also represent a process of simulation, prediction and description dependent on changing spatial parameters which generate new models or outcomes. ? A profile is a cross-section. A profile can represent stratigraphic features (e.g.: geologic or pedologic formations) or correspond to sample statistical data derived from segments of a study group which can be used to describe it. ? A table pertains to numbers and statistical numbers that are typically associated with databases and spreadsheets. ? A video represents a medium which provides moving images of real objects or computer generated animation scenes.
Examples	None

Name	SAMPLE
identifier	17
Type	element
Parent entity group	G2: Identification Information (What)
Parent entity subgroup	Not Applicable
Definition	A sample of the dataset and its approximate file size (Megabytes).
Obligation type	Optional
Obligation detail	Sample element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Unlimited
Data type	Free text
Data type domain	Image or Free Text. CGM/GIF/JPEG/TIFF or Text
Comments	The Sample element offers the user the opportunity to visualise a portion of the dataset for further evaluation. The sample can be presented as a standard graphic or text file, and include the file size of the sample graphic. A text file would be more commonly used to display tabular data. The sample image is typically a screen shot capture or exported image/text file that provides a sample presentation of the dataset. It is to the discretion of the dataset provider to determine how much detail is to be presented in the image, though it should convey enough information without exposing the entire dataset to the user. It might also be recommended to add COPYRIGHT in light grey text across the image or employ other means to obscure some of the data to prevent unauthorised use of the sample graphic presentation of the data. The data creator should ultimately be responsible for determining if this practice should be employed unless the data distributor is licensed to alter the sample files. It is the responsibility of the metadata creator to ensure that all such images are presented correctly and with the copyright owner?s permission. The recommended formats are as follows for sample files:Computer Graphics Metafile (CGM) is an ISO/IEC standard format for storing and transferring vector graphics). Less commonly used in comparison to JPEG and TIFF. Joint Photographic Experts Group (JPEG) is not a file format, but rather a compression method that is used in file formats such as TIFF or JFIF, but saves graphic images as *.jpeg or *.jpeg files. Probably the most suitable file format to use because of its compression method, which accounts for smaller file sizes. The Tag Image File Format (TIFF) is a common public domain image file format that is supported by many graphic applications and saves graphic images as *.tif or *.tiff files. File size tends to be larger than the JPEG file format. Text file format is based on the ASCII (American Standard Code for Information Interchange), which is a common format for text files. This is most suitable for displaying portions of documents or samples of tabular datasets and is saved in a *.txt format. Industry standard spreadsheet and tables can be saved as tab delimited text files.
Examples	1) sample.cgm 2) sample.jpg 3) sample.jpeg 4) sample.tiff 5) sample.tif 6) sample.txt 7) Figure 1 (Below)

Name	FURTHER INFORMATION
identifier	18
Type	element
Parent entity group	G2: Identification Information (What)
Parent entity subgroup	Not Applicable
Definition	Source of further information about the dataset.
Obligation type	Optional
Obligation detail	The Further Information element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Unlimited
Data type	Free text
Comments	It would be useful to state where these sources might be found, including URL addresses and other access or contact details. The contact details would need to be included in this element?s field if someone else other than the custodian or distributor held further information about the same source. Please include the leading code, which is most usually http:// for web addresses.
Examples	1) http://further-info.ac.uk 2) Help Desk Contact: +44 (0) 1234 567 3) Department of Geography, University of UK, Building A, 123 High Street, Edinburgh, Scotland, United Kingdom

Name	RELATED DATASETS
identifier	19
Type	element
Parent entity group	G2: Identification Information (What)
Parent entity subgroup	Not Applicable
Definition	Information about other, related datasets of a similar theme or derived from a common source, which may be of interest to the user.
Obligation type	Optional
Obligation detail	The Related Datasets element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Unlimited
Data type	Free text
Comments	Comparable to a bibliography, this element can inform the user about other sources of information or datasets that could complement or augment the dataset. These might be datasets or data sources that cover the same geographic study area or extent as the documented dataset, but represent different features or data capture periods. There could also be datasets and data sources that cover an adjacent area or extend partially into the documented dataset?s study area/extent. Related Datasets can be digital and/or hard copy.
Examples	List of Related Dataset examples presented under various academic disciplines. It is recommended that the author-date system (or sometimes called the ?Harvard System?) format be used for citations. Examples are also provided for various types of material or media and can be applied to all disciplines. ARCHAEOLOGY AND ANTHROPOLGY: (Journal) 1) Doe, J. (1936). A 1935 survey of Iron Age sites in Kent, England. Journal of Iron Archaeology, 2, 33-43. Doe, E. (1938). A 1936 survey of Iron Age sites in Surrey, England. Journal of Iron Archaeology, 4, 21-46. (Edited Contribution) Doe, L. (1939). A 1937 survey of Iron Age sites in East and West Sussex, England. In J. Doe, M. Doe, & Z. Doe (Eds.) The Iron Age (pp. 200-220). London: Iron Press. (Journal) 2) Doe, M. (1999). The 1998 archaeological excavations at a Neolithic site on Brown?s Farm in Wiltshire, England, Journal of Geophysics and Archaeology, 28, 41-60. BIOLOGICAL SCIENCES: (Book) 1) Doe, J (1984). Hedgehogs and their habitats in the United Kingdom. Glasgow: H.H. Press. (Dissertation Work) 2) Doe, F. (1991). The effects of ink disease on sessile oak trees in Scotland. [Unpublished Msc dissertation, University of UK]. CIVIL ENGINEERING: (Book) 1) Doe, W.T. (1991). A study of wind turbine designs: Birmingham: Wind Press. (Internet Address/URL) 2) Doe, T. (1999). UK Map Office Datums and Waypoints: Retrieved June 15, 2002: http://www.maps.gov.uk/datums.html EARTH SCIENCES: (Images and Maps) 1) Panchromatic Aerial Photographs (1997). 1:50 000 (Wales Series; plates 1-56). 2) West Berkshire Soil Series Maps (1981). 1:25 000 (Sheets 1-45). ENVIRONMENTAL SCIENCES: 1) UK County Council Environmental and Water Services Offices 1996 well location datasets. 2) British Geological Survey?s Digital Geological Map of Great Britain (1980). 1:50 000 (British series; 1-456). GEOGRAPHY: 1) Landsat TM satellite image (19 May 1994). 30 metre resolution (Row 201, Path 24) . 2) 1989 Postcode Boundaries of the General Register?s Office for Scotland. 3) Panchromatic Aerial Photograph (2000). 1:25 000 (Bangor Series; plates 16-18). HEALTH SCIENCES: (Journal) 1) Doe, A. (2003). The Incidence of Smoke-related Cancers amongst Women in Aberdeenshire County, Scotland from 1980 to 2002. The Journal of Medicine, 13, 11-23. (Conference Proceedings) 2) Doe, B. (1992). Long-term health effects associated with beer consumption: A controlled study of population groups in the city of Glasgow, Scotland from 1950 to 1990. In, Health and social policy: proceedings of the fifth annual seminar, January 1992, London. Ed. by K. Doe. British Health Initiative: 42-67. HISTORY: (Computer Database Source): 1) Doe, J. M. & Doe, G. (1988) National Statistical Data from 1901 to 1910 [computer file]. Colchester: ESRC Data Archive [distributor]. (CD-ROM) British National Statistics, 1905 (1996) [CD-ROM] Colchester: UKDA Press. Paper and Digital Maps (Datasets) 1) County and Parish Maps of Scotland (1750-1928). 1: 100 000 (Caledonian Series; sheets 1-280). *Scottish County Digital Maps, 1988. *Scottish Parish Digital Maps, 1987, 1988 and 1989. *Scottish National Digital Maps, 2000. *The latter three are references to digital dataset titles that were also used in the study. In practice, each of these datasets would have its own metadata file even if all were used for this one study. SOCIOLOGY: 1) Doe, S. (2001). Drugs and Crime in the Urban Setting: A Trend Analysis for Urban Areas across the United Kingdom, 1995 to 2000. The Journal of British Medicine, 21, 67-99. 2) Doe, P. (1998). A Study of Cultural Perceptions of Environmental Risks in the United Kingdom. Journal of Environmental Perception, 12, 78-96.

Name	SPATIAL REFERENCE SYSTEM
identifier	20
Type	element
Parent entity group	G2: Identification Information (What)
Parent entity subgroup	G2.1: Spatial Reference System of Dataset
Definition	Name or description of the spatial referencing system used within the dataset, which can be based on co-ordinates (e.g.: British National Grid) or geographic identifiers (e.g.: Postcode).
Obligation type	Mandatory
Obligation detail	The Spatial Reference System element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Data type domain	UK GEMINI Spatial Reference System National Grid of Great Britain Irish Grid Irish Transverse Mercator WGS84 Postcode Ward Local Authority (County/Unitary/District/Borough) Region Country Other area Parish Health Authority Area Electoral Constituency Travel to work area Other Area Type
Comments	This is usually associated with spatial datasets that have been geo-referenced to a co-ordinate system. This can also apply to point datasets created with the use of Global Positioning System (GPS) technology. There are three commonly used co-ordinate systems for British Isle datasets. These are the British National Grid and Irish National Grid Systems and WGS84, which is a global reference system. The British National Grid is based on the National Grid System of England, which is administered by the British Ordnance Survey. It is based on a Transverse Mercator projection. Co-ordinates are expressed in international metres. The British National Grid System covers all areas of England, Scotland and Wales and extends to the Channel Islands and the Isle of Man. The Irish Grid is administered by the Irish Ordnance Survey and is also based on a Transverse Mercator projection with co-ordinates expressed in international metres. The Irish Grid System extends across all of the Republic of Ireland and Northern Ireland. Additional information about the British and Irish Grid Systems can be found at the following web sites. Ordnance Survey URL : http://www.ordnancesurvey.co.uk/ Ordnance Survey Ireland URL : http://www.osi.ie/ WGS84 (World Geodetic System of 1984) is a global geocentric datum and geographic co-ordinate system. Established by the US Defence Mapping Agency, the WGS84 includes a geocentric reference ellipsoid, a coordinate system and a gravity field model. WGS84 is commonly associated with Global Positioning Systems (GPS). The WGS84 website is located at this URL: http://www.wgs84.com/ Postcode, Ward, Local Authority (County/Unitary/District/Borough), Region, Country, Parish, Health Authority Area and Electoral Constituency represent geographic identifiers as opposed to co-ordinate based systems and correspond to administrative boundaries. Travel to Work Area and Other Area Type are commonly used for census data. An authoritative source is at the National Statistics website URL: http://www.statistics.gov.uk/geography/
Examples	None

Name	NAME OF CUSTODIAN
identifier	55
Type	element
Parent entity group	G5: Custodian (Who)
Parent entity subgroup	Not Applicable
Definition	The name of the organisation or person responsible for the maintenance of the dataset.
Obligation type	Mandatory
Obligation detail	The Name of Custodian element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	If an organisation?s name is listed, please provide both its full name and associated acronyms. Please place any acronyms between parentheses. If providing the name of a person, please include, in this order, her/his surname, given name and job title. If preferable, please list the job title of the responsible person. Listing only the job title eliminates the need to update this field in the event staff departures, internal transfers and the changes in the roles of staff members.
Examples	Individuals: 1) Professor Doe, Jane 2) Dr Doe, Jane 3) Ms Doe, Jane 4) Miss Doe, Jane 5) Mrs Doe, Jane 6) Doe, Mary Jane 7) Doe, M Jane 8) Doe, Jane 9) Mr Doe, John Job Title: 1) Geographic Information Systems Manager 2) Lecturer 3) Service Co-ordinator 4) Data and Support Officer 5) Professor of Geography 6) Information Officer 7) PhD Graduate Student of History 8) Reader in Urban Planning 9) Statistician Organisations: 1) UK Data Archive (UKDA), University of Essex 2) EDINA, University of Edinburgh 3) Department of Geography, University of Edinburgh 4) Institute for Labour Research, University of Essex

Name	POSTAL STREET ADDRESS OF CUSTODIAN
identifier	56
Type	element
Parent entity group	G5: Custodian (Who)
Parent entity subgroup	Not Applicable
Definition	Postal Street part of address for organisation or person responsible for the maintenance of the dataset.
Obligation type	Mandatory
Obligation detail	The Postal Street Address of Custodian element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	The address information should include the following: organisation?s name; the building name and/or building number; the street name; department names, house names, boroughs or any other descriptive addresses that aren?t part of the city/town/village name, county or postal code.
Examples	1) Department of Geography, University of United Kingdom, Building A, 123 High Street

Name	POSTAL CITY OF CUSTODIAN
identifier	57
Type	element
Parent entity group	G5: Custodian (Who)
Parent entity subgroup	Not Applicable
Definition	Postal city part of address for organisation or person responsible for the maintenance of the dataset.
Obligation type	Mandatory
Obligation detail	The Postal City of Custodian element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	The Postal City also refers to any populated place that is listed as a city, town or village in an address.
Examples	1) London 2) Edinburgh 3) Belfast 4) Cardiff 5) Norwich 6) Colchester 7) Manchester 8) Keele Village

Name	POSTAL COUNTY OF CUSTODIAN
identifier	58
Type	element
Parent entity group	G5: Custodian (Who)
Parent entity subgroup	Not Applicable
Definition	Postal county part of address for organisation or person responsible for the maintenance of the dataset.
Obligation type	Optional
Obligation detail	Postal County of Custodian element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	If the organisation or person is located in a county, please list the county?s name. If there is no county to list in the address, then the element?s field may be left blank.
Examples	1) Essex 2) Stirling 3) Glamorganshire 4) County Antrim

Name	POSTAL CODE OF CUSTODIAN
identifier	59
Type	element
Parent entity group	G5: Custodian (Who)
Parent entity subgroup	Not Applicable
Definition	Postal code part of address for the organisation or person responsible for the maintenance of the dataset.
Obligation type	Mandatory
Obligation detail	The Postal Code of Custodian element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	Enter the complete postal code for the contact organisation or person.
Examples	1) CO1 1UB 2) EH8 9LJ 3) BT7 1NN 4) CF10 3YE 5) W9 3NN

Name	POSTAL COUNTRY OF CUSTODIAN
identifier	60
Type	element
Parent entity group	G5: Custodian (Who)
Parent entity subgroup	Not Applicable
Definition	Postal country part of address for the organisation or person responsible for the maintenance of the dataset.
Obligation type	Mandatory
Obligation detail	The Postal Country of Custodian element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	The Postal Countries can be entered as England, Northern Ireland, Scotland, Wales, Republic of Ireland, Channel Islands, Isle of Man or United Kingdom. This does not exclude the names of other postal countries if the custodian is located or residing in another country and maintaining data for a study area situated on the British Isles. The ISO 3166 provides a good source for official names that can be used for postal countries.
Examples	1) United Kingdom 2) Great Britain 3) England 4) Northern Ireland 5) Scotland 6) Wales 7) Channel Isles 8) Isle of Man 9) Republic of Ireland

Name	TELEPHONE NUMBER OF CUSTODIAN
identifier	61
Type	element
Parent entity group	G5: Custodian (Who)
Parent entity subgroup	Not Applicable
Definition	Telephone number by which individuals can talk to the organisation or person responsible for the maintenance of the dataset.
Obligation type	Optional
Obligation detail	Telephone Number of Custodian element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	The international format should be used for listing the telephone number. This includes the plus sign (+) followed by the United Kingdom?s country code, the area code (with the zero in brackets) and the number.
Examples	1) +44 (0) 123 456 789

Name	FACSIMILE NUMBER OF CUSTODIAN
identifier	62
Type	element
Parent entity group	G5: Custodian (Who)
Parent entity subgroup	Not Applicable
Definition	Facsimile number which individuals can use to contact the organisation or person responsible for the maintenance of the dataset.
Obligation type	Optional
Obligation detail	Facsimile Number of Custodian element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	The international format should be used for listing the telephone number. This includes the plus sign (+) followed by the United Kingdom?s country code, the area code (with the zero in brackets) and the number.
Examples	1) +44 (0) 123 456 789

Name	EMAIL ADDRESS OF CUSTODIAN
identifier	63
Type	element
Parent entity group	G5: Custodian (Who)
Parent entity subgroup	Not Applicable
Definition	Internet email address which individuals can use to contact the organisation or person responsible for the maintenance of the dataset.
Obligation type	Optional
Obligation detail	Email Address of Custodian element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	The email address should be associated with the contact name or organisation that is listed in element ID 38 (CONTACT NAME); however, as recommended there, it is preferable to provide an email address that is associated with a job title, an organisation or an internal department. This will reduce the need to provide metadata updates any time there is a change in the staff responsible for metadata.
Examples	1) anyone@university.ac.uk

Name	WEB ADDRESS OF CUSTODIAN
identifier	64
Type	element
Parent entity group	G5: Custodian (Who)
Parent entity subgroup	Not Applicable
Definition	Custodian?s World Wide Web site Uniform Resource Locator (URL) address.
Obligation type	Optional
Obligation detail	Web Address of Custodian element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	This element provides the URL address for the dataset?s custodian?s organisation?s web site. The URL address may link to the home page, the responsible internal department or a page that contains additional information about the dataset. Please include the leading code, which is most usually http:// for web addresses.
Examples	1) http://www.data-custodian.ac.uk/

Name	NAME OF DISTRIBUTOR
identifier	65
Type	element
Parent entity group	G6: Distributor (Access)
Parent entity subgroup	Not Applicable
Definition	The name of the organisation or person from whom the dataset may be obtained.
Obligation type	Mandatory
Obligation detail	The Name of Distributor element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	If an organisation is to be listed, please provide both the full name and, if used, the organisation?s acronym between parentheses. If providing the name of a person, please include, in this order, her/his surname, given name and job title. If it is preferable not to provide a name, then please list the organisation.
Examples	Individuals: 1) Professor Doe, Jane 2) Dr Doe, Jane 3) Ms Doe, Jane 4) Miss Doe, Jane 5) Mrs Doe, Jane 6) Doe, Mary Jane 7) Doe, M Jane 8) Doe, Jane 9) Mr Doe, John Organisations: 1) UK Data Archive (UKDA), University of Essex 2) EDINA, University of Edinburgh 3) Department of Geography, University of Edinburgh 4) Institute for Labour Research, University of Essex

Name	DISTRIBUTOR CONTACT TITLE
identifier	66
Type	element
Parent entity group	G6: Distributor (Access)
Parent entity subgroup	Not Applicable
Definition	Role or position of the responsible person for the distribution of the dataset.
Obligation type	Optional
Obligation detail	Distributor Contact Title element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	Entering the job title is advised in order to account for staff departures, internal transfers and the changing roles of staff members. The assumption is that a job title can be associated with specific duties which would include metadata creation and maintenance.
Examples	Contact Title: 1) Geographic Information Systems Manager 2) Lecturer 3) Professor 4) Researcher 5) Service Co-ordinator 6) Data and Support Officer 7) Professor of Geography 8) Information Officer 9) PhD Graduate Student of History 10) Reader in Urban Planning 11) Statistician

Name	POSTAL STREET ADDRESS OF DISTRIBUTOR
identifier	67
Type	element
Parent entity group	G6: Distributor (Access)
Parent entity subgroup	Not Applicable
Definition	Postal address for the dataset distributor including organisation name, building name or number, and street name.
Obligation type	Mandatory
Obligation detail	The Full Postal Address of Distributor element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	The address information should include the following: organisation?s name; the building name and/or building number; the street name; department names, house names, boroughs or any other descriptive addresses that aren?t part of the city/town/village name, county or postal code.
Examples	1) Department of Geography, University of United Kingdom, Building A, 123 High Street

Name	POSTAL CITY OF DISTRIBUTOR
identifier	68
Type	element
Parent entity group	G6: Distributor (Access)
Parent entity subgroup	Not Applicable
Definition	Postal city part of address for organisation or person responsible for the distribution of the dataset.
Obligation type	Mandatory
Obligation detail	The Postal City of Distributor element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	The Postal City also refers to any populated place that is listed as a city, town or village in an address.
Examples	1) London 2) Edinburgh 3) Belfast 4) Cardiff 5) Norwich 6) Colchester 7) Manchester 8) Keele Village

Name	POSTAL CODE OF DISTRIBUTOR
identifier	69
Type	element
Parent entity group	G6: Distributor (Access)
Parent entity subgroup	Not Applicable
Definition	Postal code part of the address for organisation or person responsible for the distribution of the dataset.
Obligation type	Mandatory
Obligation detail	The Full Postal Code of Distributor element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	Enter the complete postal code for the contact organisation or person.
Examples	1) CO1 1UB 2) EH8 9LJ 3) BT7 1NN 4) CF10 3YE 5) W9 3NN

Name	POSTAL COUNTRY OF DISTRIBUTOR
identifier	70
Type	element
Parent entity group	G6: Distributor (Access)
Parent entity subgroup	Not Applicable
Definition	Postal country part of address for the organisation or person responsible for the distribution of the dataset.
Obligation type	Mandatory
Obligation detail	The Postal Country of Distributor element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	The Postal Countries can be entered as England, Northern Ireland, Scotland, Wales, Republic of Ireland, Channel Islands, Isle of Man or United Kingdom. This does not exclude the names of other postal countries if the custodian is located or residing in another country and maintaining data for a study area situated on the British Isles. The ISO 3166 provides a good source for official names that can be used for postal countries.
Examples	1) United Kingdom 2) Great Britain 3) England 4) Northern Ireland 5) Scotland 6) Wales 7) Channel Isles 8) Isle of Man 9) Republic of Ireland

Name	TELEPHONE NUMBER OF DISTRIBUTOR
identifier	71
Type	element
Parent entity group	G6: Distributor (Access)
Parent entity subgroup	Not Applicable
Definition	Telephone number by which individuals can talk to the organisation or person responsible for the distribution of the dataset.
Obligation type	Optional
Obligation detail	Telephone Number of Distributor element does not require information to be entered in its field, but recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	The international format should be used for listing the telephone number. This includes the plus sign (+) followed by the United Kingdom?s country code, the area code (with the zero in brackets) and the number.
Examples	1) +44 (0) 123 456 789

Name	FACSIMILE NUMBER OF DISTRIBUTOR
identifier	72
Type	element
Parent entity group	G6: Distributor (Access)
Parent entity subgroup	Not Applicable
Definition	Facsimile number which individuals can use to contact the organisation or person responsible for the distribution of the dataset.
Obligation type	Optional
Obligation detail	Facsimile Number of Distributor element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	The international format should be used for listing the telephone number. This includes the plus sign (+) followed by the United Kingdom?s country code, the area code (with the zero in brackets) and the number.
Examples	1) +44 (0) 123 456 789

Name	EMAIL ADDRESS OF DISTIBUTOR
identifier	73
Type	element
Parent entity group	G6: Distributor (Access)
Parent entity subgroup	Not Applicable
Definition	Internet email address which individuals can use to contact the organisation or person responsible for the distribution of the dataset.
Obligation type	Optional
Obligation detail	Email Number of Distributor element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	The email address should be associated with the contact name or organisation that is listed in the Contact Name element (identifier 49); however, as recommended there, it is preferable to provide an email address that is associated with a job title, an organisation or an internal department, rather than an individual person. This will reduce the need to provide metadata updates any time there is a change in the staff responsible for metadata.
Examples	1) anyone@university.ac.uk

Name	WEB ADDRESS OF DISTRIBUTOR
identifier	74
Type	element
Parent entity group	G6: Distributor (Access)
Parent entity subgroup	Not Applicable
Definition	Dataset distributor organisation?s World Wide Web site Uniform Resource Locator (URL) address.
Obligation type	Optional
Obligation detail	Web Address of Distributor element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	This element provides the URL address for the dataset?s distributor?s organisation?s web site. The distributor may also decide to use the URL address to provide a direct on-line link to the dataset with the option of accessing and downloading the dataset. If the download option is available, then further details and instructions can be explained under the Access Details element (identifier 61). Please include the leading code, which is most usually http:// for web addresses.
Examples	1) http://www.data-distributor.ac.uk/

Name	SUPPLY MEDIA
identifier	75
Type	element
Parent entity group	G6: Distributor (Access)
Parent entity subgroup	Not Applicable
Definition	Media formats in which the dataset can be supplied.
Obligation type	Optional
Obligation detail	Supply Media element does not require information to be entered in its field, but recommended if applicable.
Max. occurrence type	Unlimited
Data type	Free text
Data type domain	ISO 19115 B.5.20 (MD_MediumNameCode) 1) cdRom 001 Read-only optical disk. 2) dvd 002 Digital versatile disk. 3) dvdRom 003 Digital versatile disk, read only. 4) 3halfInchFloppy 004 3,5 inch magnetic disk. 5) 5quarterInchFloppy 005 5,25 inch magnetic disk. 6) 7trackTape 006 7 track magnetic tape. 7) 9trackTape 007 9 track magnetic tape. 8) 3480Cartridge 008 3480 cartridge tape drive. 9) 3490Cartridge 009 3490 cartridge tape drive. 10) 3580Cartridge 010 3580 cartridge tape drive. 11) 4mmCartridgeTape 011 4 millimetre magnetic tape. 12) 8mmCartridgeTape 012 8 millimetre magnetic tape. 13) 1quarterInchCartridgeTape 013 0,25 inch magnetic tape. 14) digitalLinearTape 014 Half inch cartridge streaming tape drive. 15) onLine 015 Direct computer linkage. 16) satellite 016 Linkage through a satellite communication system. 17) telephoneLink 017 Communication through a telephone network. 18) hardcopy 018 Pamphlet or leaflet giving descriptive information.
Comments	Select one or more of the relevant media provided on the list.
Examples	None

Name	ON-LINE LINKAGE
identifier	76
Type	element
Parent entity group	G6: Distributor (Access)
Parent entity subgroup	Not Applicable
Definition	The name of the World Wide Web site or other on-line source that contains the dataset.
Obligation type	Optional
Obligation detail	On-line Linkage element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	This element provides the URL or FTP address for the user to directly access the dataset or resource.
Examples	1) http://www.data-distributor.ac.uk/ 2) ftp://data-distributor/data/

Name	ACCESS CONSTRAINTS
identifier	80
Type	element
Parent entity group	G6: Distributor (Access)
Parent entity subgroup	G6.2: Access and Use Constraints
Definition	Restrictions and legal prerequisites for accessing the dataset. These include any access constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the dataset.
Obligation type	Optional
Obligation detail	Access Constraints element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Unlimited
Data type	Free text
Data type domain	ISO 19115 B.5.24 (MD_RestrictionCode) 1). copyright 001 Exclusive right to the publication, production, or sale of the rights to a literary, dramatic, musical, or artistic work, or to the use of a commercial print or label, granted by law for a specified period of time to an author, composer, artist, distributor. 2) patent 002 Government has granted exclusive right to make, sell, use or license an invention or discovery. 3) patentPending 003 Produced or sold information awaiting a patent. 4) trademark 004 A name, symbol, or other device identifying a product, officially registered and legally restricted to the use of the owner or manufacturer. 5) license 005 Formal permission to do something. 6) intellectualPropertyRights 006 Rights to financial benefit from and control of distribution of non-tangible property that is a result of creativity. 7) restricted 007 Withheld from general circulation or disclosure. 8) otherRestrictions 008 Limitation not listed.
Comments	Select one or more of the choices from the list that best describes the type of USE CONSTRAINTS applied to the dataset. Financial constraints would probably require a licensing agreement that includes fee structures and payments for use or acquisition of the dataset. Legal constraints may impose a number of conditions such as how the dataset may be used, or who may have access to the dataset. When there is uncertainty about conditions, it is recommended that the data developer limits dataset access and use to internal staff or selected, relevant individuals. Access constraint issues should ultimately be resolved through an organisation?s legal channels or consuls.
Examples	None. Each organisation must determine which condition applies to the use constraints. Each organisation must establish and write its own access details statements through internal consultation with the responsible parties or legal consul.

Name	USE CONSTRAINTS DETAILS
identifier	82
Type	element
Parent entity group	G6: Distributor (Access)
Parent entity subgroup	G6.2: Access and Use Constraints
Definition	Description of the restrictions and legal prerequisites for accessing the dataset.
Obligation type	Optional
Obligation detail	Use Constraints Details element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Unlimited
Data type	Free text
Comments	This element states the details surrounding the conditions that must be accepted before gaining access to the dataset. These details can often address conditions such as the protection of privacy, security of intellectual property rights, copyright issues, patents and pending patents, trademarks, and other restrictions or limitations that the dataset distributor and/or custodian establish as terms for dataset access. This element may also instruct the potential user on the procedures and steps needed to fulfil the requirements embodied in the access details that are presented in this element?s field. It may also include other contact information that directs the user to licensing departments or other internal departments or agencies that handle these affairs.
Examples	None. These guidelines cannot provide examples of use detail statements. Each organisation must establish and write its own access details statements through internal consultation with the responsible parties or legal consul.

Name	USE CONSTRAINTS
identifier	81
Type	element
Parent entity group	G6: Distributor (Access)
Parent entity subgroup	G6.2: Access and Use Constraints
Definition	Restrictions and legal prerequisites for using the dataset. These include any use constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the dataset.
Obligation type	Optional
Obligation detail	Use Constraints element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Unlimited
Data type	Free text
Data type domain	ISO 19115 B.5.24 (MD_RestrictionCode) 1). copyright 001 Exclusive right to the publication, production, or sale of the rights to a literary, dramatic, musical, or artistic work, or to the use of a commercial print or label, granted by law for a specified period of time to an author, composer, artist, distributor. 2) patent 002 Government has granted exclusive right to make, sell, use or license an invention or discovery. 3) patentPending 003 Produced or sold information awaiting a patent. 4) trademark 004 A name, symbol, or other device identifying a product, officially registered and legally restricted to the use of the owner or manufacturer. 5) license 005 Formal permission to do something. 6) intellectualPropertyRights 006 Rights to financial benefit from and control of distribution of non-tangible property that is a result of creativity. 7) restricted 007 Withheld from general circulation or disclosure. 8) otherRestrictions 008 Limitation not listed.
Comments	Select one or more of the choices from the list that best describes the type of USE CONSTRAINTS applied to the dataset. Financial constraints would probably require a licensing agreement that includes fee structures and payments for use or acquisition of the dataset. Legal constraints may impose a number of conditions such as how the dataset may be used, or who may have access to the dataset. When there is uncertainty about conditions, it is recommended that the data developer limits dataset access and use to internal staff or selected, relevant individuals. Access constraint issues should ultimately be resolved through an organisation?s legal channels or consuls.
Examples	None. Each organisation must determine which condition applies to the use constraints. Each organisation must establish and write its own access details statements through internal consultation with the responsible parties or legal consul.

Name	OTHER CONSTRAINTS DETAILS
identifier	83
Type	element
Parent entity group	G6: Distributor (Access)
Parent entity subgroup	G6.2: Access and Use Constraints
Definition	Description of the restrictions and legal prerequisites for accessing the dataset.
Obligation type	Optional
Obligation detail	Access Details element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Unlimited
Data type	Free text
Comments	This element states the details surrounding the conditions that must be accepted before gaining access to the dataset. These details can often address conditions such as the protection of privacy, security of intellectual property rights, copyright issues, patents and pending patents, trademarks, and other restrictions or limitations that the dataset distributor and/or custodian establish as terms for dataset access. This element may also instruct the potential user on the procedures and steps needed to fulfil the requirements embodied in the access details that are presented in this element?s field. It may also include other contact information that directs the user to licensing departments or other internal departments or agencies that handle these affairs.
Examples	None. These guidelines cannot provide examples of access detail statements. Each organisation must establish and write its own access details statements through internal consultation with the responsible parties or legal consul.

Name	NAME OF METADATA CREATOR
identifier	84
Type	element
Parent entity group	G7: Metadata Creator Information (Record Creator)
Parent entity subgroup	Not Applicable
Definition	The name of the organisation or person responsible for the metadata and their updates.
Obligation type	Mandatory
Obligation detail	The Name of Metadata Creator element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	If an organisation?s name is listed, please provide both its full name and associated acronyms (without full stops). Please place any acronyms between parentheses. If providing the name of a person, please include, in this order, her/his surname, given name and job title. If preferable, please list the job title of the responsible person. Listing only the job title eliminates the need to update this field in the event staff departures, internal transfers and the changes in the roles of staff members.
Examples	Individuals: 1) Professor Doe, Jane 2) Dr Doe, Jane 3) Ms Doe, Jane 4) Miss Doe, Jane 5) Mrs Doe, Jane 6) Doe, Mary Jane 7) Doe, M Jane 8) Doe, Jane 9) Mr Doe, John Job Title: 1) GIS Manager 2) Lecturer 3) Service Co-ordinator 4) Data and Support Officer 5) Professor of Geography 6) Information Officer 7) PhD Graduate Student of History 8) Reader in Urban Planning 9) Statistician Organisations: 1) EDINA, University of Edinburgh 2) UK Data Archive (UKDA), University of Essex 3) Department of Geography, University of Edinburgh 4) Institute for Labour Research, University of Essex

Name	POSTAL STREET ADDRESS OF METADATA CREATOR
identifier	85
Type	element
Parent entity group	G7: Metadata Creator Information (Record Creator)
Parent entity subgroup	Not Applicable
Definition	Postal address of the organisation or person responsible for the metadata, including organisation name, building name and/or number, street name, city, county and country.
Obligation type	Mandatory
Obligation detail	The Full Postal Address of Metadata Creator element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	The address information should include the following: organisation?s name; the building name and/or building number; the street name; department names, house names, boroughs or any other descriptive addresses that aren?t part of the city/town/village name, county or postal code.
Examples	1) Department of Geography, University of United Kingdom, Building A, 123 High Street

Name	POSTAL CITY OF METADATA CREATOR
identifier	86
Type	element
Parent entity group	G7: Metadata Creator Information (Record Creator)
Parent entity subgroup	Not Applicable
Definition	Postal city part of address for organisation or person responsible for the metadata.
Obligation type	Mandatory
Obligation detail	The Postal City of Metadata Creator element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	The Postal City also refers to any populated place that is listed as a city, town or village in an address.
Examples	1) London 2) Edinburgh 3) Belfast 4) Cardiff 5) Norwich 6) Colchester 7) Manchester 8) Keele Village

Name	POSTAL CODE OF METADATA CREATOR
identifier	87
Type	element
Parent entity group	G7: Metadata Creator Information (Record Creator)
Parent entity subgroup	Not Applicable
Definition	Postal code part of the address for organisation or person responsible for metadata.
Obligation type	Mandatory
Obligation detail	The Postal Code of Metadata Creator element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	Enter the complete postal code for the contact organisation or person.
Examples	1) CO1 1UB 2) EH8 9LJ 3) BT7 1NN 4) CF10 3YE 5) W9 3NN

Name	POSTAL COUNTRY OF METADATA CREATOR
identifier	88
Type	element
Parent entity group	G7: Metadata Creator Information (Record Creator)
Parent entity subgroup	Not Applicable
Definition	Postal country part of address for organisation or person responsible for the metadata creation and updates.
Obligation type	Mandatory
Obligation detail	The Postal Country of Metadata Creator element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	The Postal Countries can be entered as England, Northern Ireland, Scotland, Wales, Republic of Ireland, Channel Islands, Isle of Man or United Kingdom. This does not exclude the names of other postal countries if the custodian is located or residing in another country and maintaining data for a study area situated on the British Isles. The ISO 3166 provides a good source for official names that can be used for postal countries.
Examples	1) United Kingdom 2) Great Britain 3) England 4) Northern Ireland 5) Scotland 6) Wales 7) Channel Isles 8) Isle of Man 9) Republic of Ireland

Name	TELEPHONE NUMBER OF METADATA CREATOR
identifier	89
Type	element
Parent entity group	G7: Metadata Creator Information (Record Creator)
Parent entity subgroup	Not Applicable
Definition	Telephone number by which individuals can talk to the organisation or person responsible for metadata updates.
Obligation type	Optional
Obligation detail	Telephone Number of Metadata Creator element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	The international format should be used for listing the telephone number. This includes the plus sign (+) followed by the United Kingdom?s country code, the area code (with the zero in brackets), and the number.
Examples	1) +44 (0) 123 456 789

Name	FACSIMILE NUMBER OF METADATA CREATOR
identifier	90
Type	element
Parent entity group	G7: Metadata Creator Information (Record Creator)
Parent entity subgroup	Not Applicable
Definition	Facsimile number which individuals can use to contact the organisation or person responsible for the metadata.
Obligation type	Optional
Obligation detail	Facsimile Number of Metadata Creator element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	The international format should be used for listing the telephone number. This includes the plus sign (+) followed by the United Kingdom?s country code, the area code (with the zero in brackets), and the number.
Examples	1) +44 (0) 123 456 789

Name	EMAIL ADDRESS OF METADATA CREATOR
identifier	91
Type	element
Parent entity group	G7: Metadata Creator Information (Record Creator)
Parent entity subgroup	Not Applicable
Definition	Internet email address which individuals can use to contact the organisation or person responsible for metadata updates.
Obligation type	Optional
Obligation detail	Email Address of Metadata Creator element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	The email address should be associated with the contact name or organisation that is listed under the Contact Name element (identifier 63); however, as recommended there, it it is preferable to provide an email address that is associated with a job title, an organisation or an internal department. This will reduce the need to provide metadata updates any time there is a change in the staff responsible for metadata.
Examples	1) anyone@university.ac.uk

Name	WEB ADDRESS OF METADATA CREATOR
identifier	92
Type	element
Parent entity group	G7: Metadata Creator Information (Record Creator)
Parent entity subgroup	Not Applicable
Definition	Metadata creator?s World Wide Web site Uniform Resource Locator (URL) address.
Obligation type	Optional
Obligation detail	Web Address of Metadata Creator element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	This element provides the URL address for the metadata creator organisation?s web site. The URL address may link to the home page, the responsible internal department, or a page that contains additional information about the organisation?s metadata. Please include the leading code, which is most usually http:// for web addresses.
Examples	1) http://www.metadata-creator.ac.uk/

Name	METADATA RECORD IDENTIFIER
identifier	93
Type	element
Parent entity group	G7: Metadata Creator Information (Record Creator)
Parent entity subgroup	Not Applicable
Definition	Unique identifier for the metadata record.
Obligation type	Optional
Obligation detail	Metadata Record Identifier element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	The Metadata Record Identifier element provides the option of entering a unique string or number that identifies the metadata record of a dataset. A metadata record can be assigned unique strings or numbers for the purpose of identifying individual records. If your organisation follows the same practice, the entry of the metadata record?s identifier in this element?s field will serve as a useful code to track changes made to the dataset and metadata record. Edits and updates to a dataset should also be documented in the metadata record and in conjunction with the Parent Metadata Record Identifier G7-93), it is also possible to establish a lineage for metadata records associated with an individual dataset over its complete life cycle. As a metadata record is updated, it is to the discretion of the data developer to determine if the update constitutes the need for a new metadata record. In the event that a new metadata record is created, it receives a new unique identifier and the unique identifier in the superseded metadata record is carried forward and added as a value under the Parent Metadata Record Identifier element field. This procedure is repeated with the creation of all new metadata records associated with the same dataset. As recommended for the element, Identifier (G1-4), there are a number of identifiers that are recognised and used internationally which can be applied to datasets. These in turn might be used for metadata record identifiers, though an organisation can establish its own internal coding system. Individual organisations should also consider if datasets and metadata records share the same unique identifier coding system or establish separate ones. There are international sources that can be used as references for establishing a unique identifier system. One of the more common identifiers, the ISSN (International Standard Serial Number), is an eight-digit number, which references and identifies periodical or serial publications. The ISBN (International Standard Book Number) is a unique machine-readable identification 10 digit number that is assigned to individual monographs (books). Maps, microform publications, pamphlets, software and multimedia kits with printed material can also be included for ISBN numbers. In addition to these, there are other types of identifiers. European Article Numbers (EANs) and Universal Product Codes (UPCs) are used as bar codes. Digital Object Identifiers (DOI) are commonly used for digital commerce. Uniform Resource Locator (URL), Uniform Resource Identifier (URI), Uniform Resource Name (URN) and Persistent (Uniform Resource Locator), or PURL, are used to identify and locate web resources. The recently approved ISAN (International Standard Audiovisual Number) is a voluntary numbering system used for referencing and identifying audiovisual works. The ISAN is a 16 digit code.
Examples	1) ISBN:L 00 101 020 12 2) ISBN: 00-101-020-12 3) ISSN: 0010-1012 4) ISAN: 123456787654-4321 5) http://www.metadata_record_identifier.ac.uk

Name	METADATA LAST UPDATED
identifier	95
Type	element
Parent entity group	G7: Metadata Creator Information (Record Creator)
Parent entity subgroup	Not Applicable
Definition	Date on which the metadata record was created or last updated.
Obligation type	Mandatory
Obligation detail	The Metadata Last Updated element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Data type domain	YYYY-MM-DD
Comments	When a metadata data file has been created and completed or an existing one updated, the date of that occurrence must be entered in this element?s field. If possible, please enter the date to the day. If unknown, enter the month and year or, if the month is not known, enter only the year. The date format is based on ISO 8601, which is expressed as YYYY-MM-DD (Year-Month-Day), and uses hyphens ?-? as separators. It is based on the Gregorian Calendar but denoted using the ?Common Era Calendar? format.
Examples	1) 2002-01-31 (Complete date known, including year, month and day) 2) 2002-01 (Year and month of date known, but not day) 3) 2002 (Year known, but not month and day)

Name	METADATA STANDARD NAME
identifier	96
Type	element
Parent entity group	G7: Metadata Creator Information (Record Creator)
Parent entity subgroup	Not Applicable
Definition	Name of the metadata standard (including the profile) used.
Obligation type	Optional
Obligation detail	Metadata Standard Name element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	This refers to the name for the ISO 19115 standard and the UK Academic Geospatial Metadata Application Profile (AGMAP). The input format requires that the values are entered in two hyphen separate brackets with the ISO 19115 name listed in the first bracket and AGMAP in the second.
Examples	1) [ISO 19115]-[AGMAP]

Name	METADATA STANDARD VERSION
identifier	97
Type	element
Parent entity group	G7: Metadata Creator Information (Record Creator)
Parent entity subgroup	Not Applicable
Definition	Version of the metadata standard (including the profile) used.
Obligation type	Optional
Obligation detail	Metadata Standard Version element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	This refers to the version for the ISO 19115 standard and the UK Academic Geospatial Metadata Application Profile (AGMAP). The input format requires that the values are entered in two hyphen separate brackets with the ISO 19115 version listed in the first bracket and the AGMAP version in the second.
Examples	1) [1.0 ]-[1.0]

Name	PARENT METADATA RECORD IDENTIFIER
identifier	94
Type	element
Parent entity group	G7: Metadata Creator Information (Record Creator)
Parent entity subgroup	Not Applicable
Definition	Identifier used for parent or original metadata record.
Obligation type	Mandatory
Obligation detail	If metadata record is a subset or offspring of an original record, then Metadata Record Identifier value should be entered
Max. occurrence type	Once
Data type	Free text
Comments	The Parent Metadata Record Identifier element provides the option of entering a unique string or number that identifies the metadata record of a dataset. A metadata record can be assigned unique strings or numbers for the purpose of identifying individual records. If your organisation follows the same practice, the entry of the metadata record?s identifier in this element?s field will serve as a useful code to track changes made to the dataset and metadata record. Edits and updates to a dataset should also be documented in the metadata record and in conjunction with the Metadata Record Identifier G7-92), it is also possible to establish a lineage for metadata records associated with an individual dataset over its complete life cycle. As a metadata record is updated, it is to the discretion of the data developer to determine if the update constitutes the need for a new metadata record. In the event that a new metadata record is created, it receives a new unique identifier and the unique identifier in the superseded metadata record is carried forward and added as a value under the Parent Metadata Record Identifier element field. This procedure is repeated with the creation of all new metadata records associated with the same dataset. As recommended for the element, Identifier (G1-4), there are a number of identifiers that are recognised and used internationally which can be applied to datasets. These in turn might be used for metadata record identifiers, though an organisation can establish its own internal coding system. Individual organisations should also consider if datasets and metadata records share the same unique identifier coding system or establish separate ones. There are international sources that can be used as references for establishing a unique identifier system. One of the more common identifiers, the ISSN (International Standard Serial Number), is an eight-digit number, which references and identifies periodical or serial publications. The ISBN (International Standard Book Number) is a unique machine-readable identification 10 digit number that is assigned to individual monographs (books). Maps, microform publications, pamphlets, software and multimedia kits with printed material can also be included for ISBN numbers. In addition to these, there are other types of identifiers. European Article Numbers (EANs) and Universal Product Codes (UPCs) are used as bar codes. Digital Object Identifiers (DOI) are commonly used for digital commerce. Uniform Resource Locator (URL), Uniform Resource Identifier (URI), Uniform Resource Name (URN) and Persistent (Uniform Resource Locator), or PURL, are used to identify and locate web resources. The recently approved ISAN (International Standard Audiovisual Number) is a voluntary numbering system used for referencing and identifying audiovisual works. The ISAN is a 16 digit code.
Examples	1) ISBN:L 00 101 020 12 2) ISBN: 00-101-020-12 3) ISSN: 0010-1012 4) ISAN: 123456787654-4321 5) http://www.parent_metadata_record_identifier.ac.uk

Name	DATASET FORMAT NAME
identifier	78
Type	element
Parent entity group	G6: Distributor (Access)
Parent entity subgroup	G6.1: Dataset Name and Format
Definition	Format in which digital data can be provided (e.g.: DXF, DLG, MapInfo, IDRISI, ARC/INFO, ERDAS, DBF, RTF, etc.).
Obligation type	Mandatory
Obligation detail	The Dataset Format Name element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	Entries for this element can include software and file format names associated with the datasets. The individual dataset filenames do not need to be entered in this field. Only the software types and extension names and are necessary, with the software name first, followed with a space, then asterix, full-stop and extension (e.g.: IDRISI Kilimanjaro *.RST ). If there are multiple extensions for one dataset file, then provide a recognised extension (e.g.: ArcView *.SHP). Please also see the Partial List of Commonly used Digital Dataset Formats list below. Partial List of Commonly Used Digital Data Formats ASCII (American Standard Code for Information Interchange), which is a common format for text files. This is most suitable for displaying portions of documents or samples of tabular datasets and is saved in a *.txt format. AutoCAD (*.dwg) A commercial software design tool used for creating two and three-dimensional drawings. This is a tool that is commonly used for architectural designs and engineering projects. AutoCAD file format is *.dwg and can export files in the commonly used *.dxf standard format. AtlasGIS (*.agf) Commercial GIS mapping and geographic analysis software program. Atlas GeoFile format for GIS software package used primarily for viewing maps and demographic datasets. *.dbf This is a data file format used for most database software programs. *.dem DEM is a raster format used by the United States Geological Survey (USGS) to record elevation information using cells to represent elevations of points on the earth?s surface. *.dlg Digital Line Graph format used previously for United States Geological Survey (USGS) to display vector cartographic information. Now replaced with an SDTS format. *.dgn See IGDS. *.dxf The Drawing Exchange Format (*.dxf) enables the interchange of drawings between AutoCAD and other programs. These files can either be ASCII or binary formats. ENVI (*.hdr) A commercial image processing software tool, ENVI uses the *.hdr file format. ERDAS IMAGINE (*.img, *.lan, *.trl) The file formats for ERDAS IMAGINE, a commercial imagery processing software tool. The *.trl file is the colour map extension. ER Mapper (*.ers) The file format for ER Mapper, a commercial imagery processing software tool. ESRI Arc/Info (*.e00) Commercial GIS mapping and geographic analysis software program. An Arc/Info dataset comprises a set of binary, proprietary files that cannot be interchanged with other GIS software programs. Files (coverages) can be converted to the *.e00 format extension for transfer to Arc/Info programs on other operating systems. The ESRI *.e00 interchange data format allows all spatial and descriptive information for vectors and rasters to be combined into a single ASCII file. The file can be used to move themes into and out of ESRI software. ESRI ArcView/ArcMap (*.shp, *.shx, *.dbf, *.prj) Commercial GIS mapping and geographic analysis software program. Mapping and geographic analysis software program file formats. A shapefile stores non topological geometry and attribute information for the spatial features in a data set. A shapefile consists of a set of three mandatory files, along with several optional files. Each file in the set shares the shapefile name with a different extension. The main file (*.shp)stores the geometry and must always have an index file (*.shx). A dBASE file (*.dbf) stores all the attributes of the shapes in the main file. Additionally, a projection file (*.prj) stores the projection information. GeoTIFF A GeoTIFF represents a geo-referenced image file. It contains the geospatial information (such as projection, datum, etc.) for a *.tif file. *.hdf Hierarchical Data Format is a physical file format for storing scientific data. Many raster and image datasets use this format and numerous commercial image processing software packages support it. IDRISI/ Cartalinx/Kilimanjaro (*.img,/*.doc, *.rst/*.rdc, *.vec, /*.dvc, *.vct/*.vdc) A Clark Labs GIS product, IDRISI32 and Kilimanjaro raster image consists of at least two files; IDRISI32 and previous versions used the *.img (image) file and the other a header *.doc file containing spatial reference information. IDRISI Kilimanjaro raster images are stored as *.rst/*.rdc files (*.rdc representing the header file. Clark Labs also offer a product (Cartalinx) for creating vector GIS datasets. With previous IDRISI versions, two filename extensions were generated for vector datasets (*.vec and *.dvc), but Kilimanjaro now uses *.vct and *.vdc filename extensions. Intergraph (*.dgn) Commercial GIS mapping and geographic analysis software program. Landsat (*.hdf) Earth-orbiting satellites (NASA) that provide panchromatic and multi-spectral imagery for a wide range of applications. Landsat satellites 4 and 5 imagery can also be distributed using seven files that constitute separate wavelength bands, which can be collated and processed to produce single, composite images. Imagery can also be distributed as header, image and leader files or include the formats listed under satellite imagery as well as other raster formats. Current Landsat 7 uses an *.hdf file format. Microstation (*.dgn) Bentley Microstation?s internal format data. Also known as IGDS (Interactive Graphic Design Software), which is the internal format. MapInfo (*.mid/*.miff) Commercial GIS mapping and geographic analysis software program interchange file formats. MOSS Map Overlay Statistical System (MOSS) is a public domain GIS format. This is a non-topological formats for vector data with translators to several common spatial data formats. MrSID (*.sid) MrSID is an acronym for Multi-resolution Seamless Image Database. This software product is an image compressor that is used for very large raster image files. It provides high compression while maintaining image quality. Many GIS software packages support its file format. *.ntf The UK National Transfer Format (NTF) represents the Ordnance Survey?s file format for some of their digital cartographic products. *.pcx PCX is a raster format that is commonly produced using scanners and computer software drawing programs. The Ordnance Survey?s colour raster maps are available in this format. *.png The Portable Network Graphic (PNG) format provides a portable, legally unencumbered, well-compressed, well-specified standard for lossless bitmapped raster files. It is meant as a replacement for GIF and supports a large range of bit depths, from monochrome all the way to 64-bit colour. PCI Geomatics (*.pix/*.gav) Commercial GIS mapping, geographic analysis and image processing software tool. Raster (*.bmp, *.cgm, *.gif, *.jpeg, *.tiff) Bitmap (*.bmp) is a standard format for storing RGB graphics data. This format also supports a wide range of RGB image data, which can also be stored as compressed files. Computer Graphics Metafile (*.cgm) is an ISO/IEC standard format for storing and transferring vector graphics). Less commonly used in comparison to JPEG and TIFF. The *.gif file format refers to Graphics Interchange Format, which is a bitmap graphic format used frequently for images on the World Wide Web. It is also a common format used for scanned images. It also supports colour and various resolutions and files can be stored using compression. Joint Photographic Experts Group (*.jpeg) is not a file format, but rather a compression method that is used in file formats such as TIFF or JFIF, but saves graphic images as *.jpeg or *.jpg files. Probably the most suitable file format to use because of its compression method, which accounts for smaller file sizes. The Tag Image File Format (*.tiff) is a common public domain image file format that is supported by many graphic applications and saves graphic images as *.tif or *.tiff files. File size tends to be larger than the JPEG file format. Satellite Imagery Formats (*.bil, *.bip, *.bsq) Band Interleaved by Line, Band Interleaved by Pixel and Band Sequential. Not formats, but schemes for storing the pixel values of raster images. Commonly associated with earlier Landsat and SPOT satellite imagery. SDTS SDTS (Spatial Data Transfer System) represents a new transfer format developed by the US government to replace the *.dlg format. The SDTS was designed to handle all types of geographic data including vector and raster datasets. SPOT (*.dat) French satellite company (Satellite Pour l'Observation de la Terre) that provides satellite panchromatic and multi-spectral imagery for a wide range of applications. Surfer (*.srf) Surfer is a commercial software product used for contouring and 3D surface mapping. It converts data into outstanding contour, surface, wireframe, vector, image, shaded relief, and post maps. *.tfw A world file which accompanies the *.tif file. It contains spatial information about the data associated with the *.tif file.
Examples	1) IDRISI Kilimanjaro *.RST Files 2) MapInfo *.MID/MIF Files 3) ArcView *.SHP

Name	DATASET FORMAT VERSION
identifier	79
Type	element
Parent entity group	G6: Distributor (Access)
Parent entity subgroup	G6.1: Dataset Name and Format
Definition	Format version in which digital data can be provided (e.g. 1.0, 3.1, 8.0).
Obligation type	Mandatory
Obligation detail	The Dataset Format Version element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	Entries for this element can include software or file format versions associated with the datasets. The individual dataset filenames do not need to be entered in this field.
Examples	1) 14.02 2) 6.5 3) 9.0

Name	DATA HIERARCHICAL LEVEL
identifier	21
Type	element
Parent entity group	G3: Data Quality (Quality)
Parent entity subgroup	Not Applicable
Definition	Hierarchical level of the data stated in the process steps and quality statement.
Obligation type	Optional
Obligation detail	The default is set to ?Dataset?. If a value is entered in one of the element fields under Data Process Step, Quality Statement or Level of Spatial Detail, and the value pertains to a different hierarchical level, then the corresponding value must be sele
Max. occurrence type	Once
Data type	Free text
Data type domain	ISO 19115 B.5.25 (MD_ScopeCode) 1. attribute 001 Information applies to the attribute class. 2. attributeType 002 Information applies to the characteristic of a feature. 3. collectionHardware 003 Information applies to the collection hardware class. 4. collectionSession 004 Information applies to the collection session. 5. dataset 005 Information applies to the dataset. 6. series 006 Information applies to the series. 7. nonGeographicDataset 007 Information applies to non-geographic data. 8. dimensionGroup 008 Information applies to a dimension group. 9. feature 009 Information applies to a feature. 10. featureType 010 Information applies to a feature type. 11. propertyType 011 Information applies to a property type. 12. fieldSession 012 Information applies to a field session. 13. software 013 Information applies to a computer program or routine. 14. service 014 Information applies to a capability which a service provider entity makes available to a service user entity through a set of interfaces that define a behaviour, such as a use case. 15. model 015 Information applies to a copy or imitation of an existing or hypothetical object. 16. tile 016 Information applies to a tile, a spatial subset of geographic data.
Comments	The default value is set to ?Dataset?. If the data processing, quality statements or level of spatial detail element or elements pertain to a different hierarchical level, then that value must be selected from the list.
Examples	1. Attribute Information applies to the attribute class. An attribute is information about a geographic feature represented as a vector dataset would have attributes stored in a table and linked to the feature by a unique identifier. For example, attributes of a soil might include texture, colour and soil name. 2. Attribute Type Information applies to the characteristic of a feature. 3. Collection Hardware Information applies to the collection hardware class. 4. Collection Session Information applies to the data collection session. 5. Dataset Information applies to the dataset. A dataset is a collection of associated data with a common geographical theme. 6. Series Information applies to the series. 7. Non Geographic Dataset Information applies to non-geographic data. 8. Dimension Group Information applies to a dimension group. Entity definition of codes comprising common, aligned, linear and rotated, radical and diameter, angular and ordinate groups which are found in the ENTITIES section of a DXF file (Computer Aided Design (CAD) geometry). 9. Feature Information applies to a feature. A feature represents a real world object on a map presented in vector (points, lines, or polygons) and raster (cells) data format. A feature can also be described as an object in a geographic or spatial database with a distinct set of characteristics which corresponds to a defined aspect of the earth's surface that is not further subdivided. For example, trees, fauna and flora sharing the same ecosystem type. 10. Feature Type Information applies to a feature type. 11. Property Type Information applies to a property type. 12. Field Session Information applies to a field session. 13. Software Information applies to a computer program or routine. 14. Service Information applies to a capability which a service provider entity makes available to a service user entity through a set of interfaces that define a behaviour, such as a use case. 15. Model Information applies to a copy or imitation of an existing or hypothetical object. More specifically, a model can be a data representation of reality such as landscape features. A model can be the result of applied structural rules and procedures to one or more spatial data overlays to conduct spatial analysis to derive new information to assist in problem solving and planning. A model can also represent a process of simulation, prediction and description dependent on changing spatial parameters which generate new models or outcomes. 16. Tile Information applies to a tile, a spatial subset of geographic data or sub-area of a digital map.

Name	STATUS OF DATA CREATION PROCESS
identifier	22
Type	element
Parent entity group	G3: Data Quality (Quality)
Parent entity subgroup	G3.1: Dataset Process Steps
Definition	Declaration on the status of the data creation process.
Obligation type	Optional
Obligation detail	The Status of the Data Creation Process element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Data type domain	ISO 19115 B.5.23 (MD_ProgressCode) 1. completed 001 Production of the data has been completed. 2. historicalArchive 002 Data has been stored in an offline storage facility. 3. obsolete 003 Data is no longer relevant. 4. onGoing 004 Data is continually being updated. 5. planned 005 Fixed date has been established upon or by which the data will be created or updated. 7. required 006 Data needs to be generated or updated. 8. underDevelopment 007 Data is currently in the process of being created.
Comments	The dataset developer can consider using the value ?Obsolete? as a solution to addressing the Dataset Date Code?s (G1-6) lack of a value for the deletion of a dataset. Deletion is not an ISO 19115 value but was added in anticipation of a future amendment to ISO 19115 which would cover the complete life cycle of a dataset. There will be instances when datasets are deleted, especially those derived from licensed data which would require the data developer to delete the dataset in the event of a change in status (e.g.: a student leaving academia who has used Digimap OS datasets). If a dataset is deleted, its metadata record could be retained so that other data developers can reference it to recreate the same dataset.
Examples	None

Name	START DATE OF DATA CAPTURE PERIOD
identifier	23
Type	element
Parent entity group	G3: Data Quality (Quality)
Parent entity subgroup	G3.1: Dataset Process Steps
Definition	Date on which data for dataset were first collected.
Obligation type	Conditional
Obligation detail	If a Status of Data Creation Process value is selected, then a start date should be entered.
Max. occurrence type	Once
Data type	Free text
Data type domain	YYYY-MM-DD
Comments	Enter the date when the data capture or collection started. If possible, please enter the date to the day. If unknown, enter the month and year or, if the month is not known, enter only the year. The date format is based on ISO 8601, which is expressed as YYYY-MM-DD (Year-Month-Day), and uses hyphens ?-? as separators. It is based on the Gregorian Calendar but denoted using the ?Common Era Calendar? format. Numbers that are less than 10 for day and month are written with a leading zero. Leading zeroes are also added for year dates that fall between 1000 BC and AD 1000. For dates preceding the Year AD 1, then a ?-? (minus) sign or hyphen is used to signify BC dates. This could be relevant for studies that include data (e.g.: census or tribute records) that were collected and recorded during antiquity.
Examples	1) 2001-01-31 (Entire date known, including year, month and day) 2) 2001-01 (Year and month of date known, but not day) 3) 2001 (Year known, but not month and day) 4) -0055 (The year 55 BC) 5) 0450 (The year AD 450)

Name	END DATE OF DATA CAPTURE PERIOD
identifier	24
Type	element
Parent entity group	G3: Data Quality (Quality)
Parent entity subgroup	G3.1: Dataset Process Steps
Definition	Date on which data for dataset were last collected.
Obligation type	Conditional
Obligation detail	If a Status of Data Creation Process value is selected, then an end date should be entered.
Max. occurrence type	Once
Data type	Free text
Data type domain	YYYY-MM-DD
Comments	Enter the date when the data capture or collection was completed. If possible, please enter the date to the day. If unknown, enter the month and year or, if the month is not known, enter only the year. The date format is based on ISO 8601, which is expressed as YYYY-MM-DD (Year-Month-Day), and uses hyphens ?-? as separators. It is based on the Gregorian Calendar but denoted using the ?Common Era Calendar? format. Numbers that are less than 10 for day and month are written with a leading zero. Leading zeroes are also added for year dates that fall between 1000 BC and AD 1000. For dates preceding the Year AD 1, then a ?-? (minus) sign or hyphen is used to signify BC dates. This could be relevant for studies that include data (e.g.: census or tribute records) that were collected and recorded during antiquity.
Examples	1) 2001-01-31 (Entire date known, including year, month and day) 2) 2001-01 (Year and month of date known, but not day) 3) 2001 (Year known, but not month and day) 4) -0055 (The year 55 BC) 5) 0450 (The year AD 450)

Name	DATASET LINEAGE
identifier	25
Type	element
Parent entity group	G3: Data Quality (Quality)
Parent entity subgroup	G3.1: Dataset Process Steps
Definition	Information about the source data used in the construction of the dataset.
Obligation type	Optional
Obligation detail	The Dataset Lineage element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	The Dataset Lineage information can represent a list of feature and attribute sources compiled to create the dataset. The dataset could be derived from a single or composite source of data. These sources can include maps, photography, images and people involved in data collection.

Name	DESCRIPTION OF DATASET PROCESS STEPS
identifier	26
Type	element
Parent entity group	G3: Data Quality (Quality)
Parent entity subgroup	G3.1: Dataset Process Steps
Definition	A general description of how the dataset was generated or derived.
Obligation type	Optional
Obligation detail	The Dataset Lineage element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	The Description of the Dataset Process Steps information provides comprehensive details of the steps conducted to construct a dataset and the processes used to process the data. This provides a descriptive history of the dataset which is very useful in determining the dataset's fitness-for-use for particular applications or analyses. The description should also include hardware and software used, processing tolerances, scanning or digitisation specifications and other relevant details that AGMAP elements do not cover. Recording this information can also be important for re-tracing the process steps taken to create a dataset in the event the dataset is deleted. It can also be used as a reference for data users wanting to re-construct an existing dataset which isn?t accessible to them due to various restrictions.

Name	LOGICAL CONSISTENCY
identifier	27
Type	element
Parent entity group	G3: Data Quality (Quality)
Parent entity subgroup	G3.2: Data Quality Statement
Definition	An indication of topological problems such as overshoots, undershoots, unwanted intersections, unclosed polygons, missing or duplicate labels, etc.
Obligation type	Optional
Obligation detail	The Logical Consistency element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	This is a reliability statement about relationships in a dataset?s structure and processes involved in its creation. This should include a review of a dataset?s topology (e.g.: arc/node structures and statements about intersections, overshoots and undershoots); a comparison between real world geographical features and corresponding attributes and representative structure in the dataset; a review of the uniformity within the dataset; and a report on the people involved in processing the dataset. In some instances, numerous people working on a single dataset can increase the potential for introducing errors or inconsistencies into a dataset and it might be necessary to retrace the process steps and the individuals responsible or assigned to each of these.

Name	COMPLETENESS
identifier	28
Type	element
Parent entity group	G3: Data Quality (Quality)
Parent entity subgroup	G3.2: Data Quality Statement
Definition	Information about omissions, commissions, selection criteria, generalisation definitions used to derive the dataset that may affect the completeness of the dataset?s content.
Obligation type	Optional
Obligation detail	The Completeness element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	This statement provides a summary of omissions and commissions associated with both the data and the dataset. These should be identified and explained in detail with reasons given for these exclusions or inclusions. There can be a range of exclusions including geographical (data was not available for Wales); categorical (cities with populations greater than 250,000 were not included in the study); or thematic (coniferous forests were mapped as forests). Omissions can also pertain to data where the results are less than the predicted outcome. Conversely, commission would take place when results exceed the predicted outcome. Processed satellite imagery might yield a classification that indicates the presence of oak trees in 38 percent of a forest, but actual field surveys indicate 24 percent oak coverage (omission). In another instance, imagery classification could indicate that 51 percent of the forest comprises oak coverage, but field checking reveals that oak trees cover 63 percent (commission) of the forest. If data or a dataset requires further developmental work, then a summary should be provided which describes the remaining process steps required to complete the dataset. If no further work can be done, then reasons for this should be stated (e.g.: time or budgetary constraints). Dataset users should also be informed about instances when ?null? or ?0? values are intentionally introduced into a dataset.

Name	POSITIONAL ACCURACY
identifier	29
Type	element
Parent entity group	G3: Data Quality (Quality)
Parent entity subgroup	G3.2: Data Quality Statement
Definition	An explanation of the accuracy of the horizontal positions (co-ordinates) of spatial objects and a description of the tests or line of reasoning used to arrive at the estimate.
Obligation type	Optional
Obligation detail	The Positional Accuracy element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	Positional accuracy can be described in terms of accuracy and precision. Accuracy refers to the difference between measured quantities and accepted or true values, plus a description of how these values were attained. Precision refers to the number of significant digits used for measurements during the data recording process. There are different positional accuracy based criteria between data captured with Global Positioning System (GPS) equipment and data captured from maps or imagery. Accuracy of data collected with a GPS are dependent on the type of GPS equipment (mapping grade, survey grade), settings used, the number of satellites used, the logging intervals of position and post-processing techniques (such as differential correction). Maps and imagery accuracy is based on the RMS (root mean square) error and the number of registration points used. Imagery that is registered to existing coverages should include the final image-to-coverage RMS error, the number of registration links used and the maximum positional offset accepted for the links. In addition to registration error, error should be quantified, or at the very least estimated, for each of these steps in the production process. These all contribute to the final accuracy of the data and should be noted. These measures are critical for potential dataset users wanting to assess a dataset?s positional accuracy. This information can be critical for those data users wishing to match or overlay datasets or those wanting to provide accurate maps for emergency navigation routing, locating buried utility lines or establishing property boundaries.

Name	ATTRIBUTE ACCURACY
identifier	30
Type	element
Parent entity group	G3: Data Quality (Quality)
Parent entity subgroup	G3.2: Data Quality Statement
Definition	An explanation of how accurately the entities have been identified or how accurately values have been assigned in the dataset. This can be the results of quantitative analysis, steps taken to ensure accuracy during development or known deficiencies.
Obligation type	Optional
Obligation detail	The Attribute Accuracy element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	The attribute accuracy statement should be quantified if possible and include measures used to validate attributes. Accuracy statements might include attribute comparisons or cross-referencing, visual checks or independent sampling. Attribute comparison requires a separate but comparable data source which provides attributes based on greater accuracy or larger scale. Field or visual checks can be conducted to measure or ascertain if attributes and values correspond to real world observations and data capture. An independent sampling strategy can be employed to reduce bias. A visual check can also summarise a dataset?s attribute accuracy based on the percentage of the attributes and values subjected to review. In the event that a review is quantified through an automated statistical process, then a description of the process and parameters should be described.

Name	SOURCE SCALE DENOMINATOR
identifier	31
Type	element
Parent entity group	G3: Data Quality (Quality)
Parent entity subgroup	G3.3: Level of Spatial Detail
Definition	Denominator of the representative fraction on the source map(s) (e.g. on a 1: 50,000 scale map, the source scale denominator is 50000). If no source map used, enter 0 (zero). If multiple source map scales were used, enter the source scale denominator of the smallest scale map (largest denominator).
Obligation type	Optional
Obligation detail	The Source Scale Denominator element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	Only enter the denominator and not the fraction for the scale. If the dataset was derived from several map sources, use the denominator from the smallest scale map rather than listing all the scale denominators. Regarding scale, a small scale map displays the least detail. The City of London could be represented as a dot on a map of the United Kingdom. Conversely, a large scale map of London would probably be represented as polygons, lines, and points displaying streets, buildings, landmarks, local administrative boundaries and other details that wouldn?t be seen on a small scale map. Only one entry is permitted, so it is recommended that the smallest scale map be used as the reference for the source scale denominator. Please keep in mind that the scale is taken from the data source of the derived dataset, and not the dataset itself. In the case of multiple map sources, It is important that the user knows the smallest scale used in order to determine the spatial accuracy of the dataset. As the map scale becomes smaller, the inaccuracy increases, which means that comparisons are difficult to make between the locations of features of one scale to those features associated with another scale. It is; therefore, critical for the user to know about the smallest scale map to assure that discrepancies can be accounted for when comparing maps or adding maps with different scales. If the dataset has been derived from data sources of various scales, the Description element can be used to enter all the scales used along with the titles of their respective maps.
Examples	Maps 1 and 2 (Figures 1 and 2) provide illustrated examples of scale for metric and imperial measures. This is the ratio or relationship between a distance or area on a map and the corresponding distance or area on the ground. Geo-referenced maps, or those with co-ordinates, have ground units of measurement. Ground distances can be expressed in terms of metres/kilometres or feet/miles. Typically the original map of a derived dataset is the source for the denominator scale. Maps 1 and 2 have been derived from an Ordnance Survey 1:50,000 Scale Colour Raster dataset (tile NJ 86), which is provided through Digimap services. The scale for this series is expressed as a representative fraction (1:50,000 or 1/50,000). This means that one unit of measure on the map corresponds to 50000 units in the real world. If the map distance units are expressed in centimetres, then 1.0 centimetres on the map equals 10,000 centimetres ground distance in the real world. If imperial measure is used and the map distance units are expressed in inches, then 1 inch on the map equals 10,000 inches ground distance in the real world. Most maps provide a scale which is expressed in a text format, e.g.: 1:50,000 or 1/50,000. In some instances, maps provide only a scale bar, and in this situation, the map scale must be calculated to acquire the source scale denominator value. Map 1 displays two scale bars with map distance units expressed in centimetres and ground distance units expressed in metres. The map distance unit scale bar is usually not displayed on a map, but for this example, it has been included as it is common practice to use a ruler for measuring map distances on a paper map. Most GIS software packages have tools for measuring distances on digital maps. Map 1 uses a scale bar with 1 centimetre increments for The map distance scale bar on Map 1 provides 1 centimetre increments; the ground distance scale bar a 500 metre and 1,000 metre increments. The scale bars indicate that a map distance of 1 cm corresponds to 500 metres (0.5 km) on the ground. In order to calculate scale, the units of measure for both scale bars must correspond. As there are 100 centimetres in a metre, 500 metres must be multiplied by 100 (500 x 100) and divided by 1. This yields a value of 50,000, which is the scale of Map 1. As a further example, the ground distance can be measured between two points to calculate scale. The red line between New Aberdour and Tyrie indicates the distance measured between the two locations. Based on the ground distance scale bar, the one typically associated with a map, the distance between the two locations is 4,000 metres (4 km). This map distance on a ruler would measure 8 centimetres. Multiple 4,000 by 100 (100 cm in a metre) and divide by 8 and the value is 50,000. Scale Map 2 provides an example using imperial measures for map (inches) and ground distances (feet). Again, the red line between New Aberdour and Tyrie indicates the distance measured between the two locations. Based on the ground distance scale bar, the one typically associated with a map, the distance between the two locations is 13,123.359 feet (2.48 miles). This map distance on a ruler would measure 3.1496 inches. Multiple 13,123.359 by 12 (12 inches in a foot) and divide by 3.1496 and the value is 50,000.

Name	GROUND SCALE DISTANCE
identifier	32
Type	element
Parent entity group	G3: Data Quality (Quality)
Parent entity subgroup	G3.3: Level of Spatial Detail
Definition	The ground sample distance.
Obligation type	Optional
Obligation detail	The Ground Scale Distance element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Data type domain	Real Number
Comments	This is the area of the ground represented in each pixel. Also described as the horizontal ground resolution or area of the ground represented in each pixel of an image. High resolution aerial photographs or satellite images can provide sub-metre ground sample resolution.

Name	IMAGERY OR GRID x-DIMENSION NAME
identifier	33
Type	element
Parent entity group	G3: Data Quality (Quality)
Parent entity subgroup	G3.3: Level of Spatial Detail
Definition	Name of the x-axis. (Default = Column)
Obligation type	Optional
Obligation detail	The Imagery or Grid x-Dimension Name element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Data type domain	ISO 19115 B.5.14 (MD_DimensionNameTypeCode) 1) row 001 Ordinate (y) axis. 2) column 002 Abscissa (x) axis. 3) vertical 003 Vertical (z) axis. 4) track 004 Along the direction of motion of the scan point. 5) crossTrack 005 Perpendicular to the direction of motion of the scan point. 6) line 006 Scan line of a sensor. 7) sample 007 Element along a scan line. 8) time 008 Duration.
Comments	The default is set to column for the x-axis. Though the ISO 19115 (B.5.14) list includes other values, the x and y-axes (column and row) have been selected because the level of spatial detail pertains to dimensions of grid or raster cells, which can also be referred to as resolution. These cells are typically associated with images such as digital aerial photographs and satellite images. They can also represent Digital Terrain Models (DTM), which are raster grids.

Name	IMAGERY OR GRID RASTER CELL/PIXEL SIZE (x-VALUE)
identifier	34
Type	element
Parent entity group	G3: Data Quality (Quality)
Parent entity subgroup	G3.3: Level of Spatial Detail
Definition	The column width of a raster cell expressed in distance units of measure.
Obligation type	Conditional
Obligation detail	If the Grid Raster Cell/Pixel y-Value element has a value entered, then a Grid Raster Cell x-Value element must have a value entered.
Max. occurrence type	Once
Data type	Free text
Data type domain	Real Number
Comments	This value is associated with raster datasets and represents the x-value length of the raster cell. A raster dataset contains rows and columns of cells. These can also be characterised as a matrix of screen pixels. Each cell or pixel contains an attribute value, thus cells sharing the same value may represent a feature. Many times, these cells also contain location co-ordinates that provide a reference to points in the real world. These cells are typically associated with images such as digital aerial photographs and satellite images. They can also represent Digital Terrain Models (DTM), which are raster grids that store the x, y and z values in each cell. The x and y values provide the locational co-ordinates and resolution, and the z-value provides the surface elevation. Regarding this element, the information required pertains only to the x-value length of the cell. The lengths of the x and y-values provide the dataset?s resolution. If the x and y- values both equal 30 metres, then the surface area covered represents 30 x 30 metres or 900 square metres.

Name	IMAGERY OR GRID y-DIMENSION NAME
identifier	35
Type	element
Parent entity group	G3: Data Quality (Quality)
Parent entity subgroup	G3.3: Level of Spatial Detail
Definition	Name of the y-axis. (Default = Row)
Obligation type	Optional
Obligation detail	The Imagery or Grid y-Dimension Name element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Data type domain	ISO 19115 B.5.14 (MD_DimensionNameTypeCode) 1) row 001 Ordinate (y) axis. 2) column 002 Abscissa (x) axis. 3) vertical 003 Vertical (z) axis. 4) track 004 Along the direction of motion of the scan point. 5) crossTrack 005 Perpendicular to the direction of motion of the scan point. 6) line 006 Scan line of a sensor. 7) sample 007 Element along a scan line. 8) time 008 Duration.
Comments	The default is set to row for the y-axis. Though the ISO 19115 (B.5.14) list includes other values, the x and y-axes (column and row) have been selected because the level of spatial detail pertains to dimensions of grid or raster cells, which can also be referred to as resolution. These cells are typically associated with images such as digital aerial photographs and satellite images. They can also represent Digital Terrain Models (DTM), which are raster grids.

Name	IMAGERY OR GRID RASTER CELL/PIXEL SIZE (y-VALUE)
identifier	36
Type	element
Parent entity group	G3: Data Quality (Quality)
Parent entity subgroup	G3.3: Level of Spatial Detail
Definition	The row height of a raster cell expressed in distance units of measure.
Obligation type	Optional
Obligation detail	If the Grid Raster Cell/Pixel x-Value element has a value entered, then a Grid Raster Cell y-Value element must have a value entered.
Max. occurrence type	Once
Data type	Free text
Data type domain	Real Number
Comments	This value is associated with raster datasets and represents the y-value length of the raster cell. A raster dataset contains rows and columns of cells. These can also be characterised as a matrix of screen pixels. Each cell or pixel contains an attribute value, thus cells sharing the same value may represent a feature. Many times, these cells also contain location co-ordinates that provide a reference to points in the real world. These cells are typically associated with images such as digital aerial photographs and satellite images. They can also represent Digital Terrain Models (DTMs), which are raster grids that store the x, y and z values in each cell. The x and y values provide the locational co-ordinates and resolution, and the z-value provide the surface elevation. Regarding this element, the information required pertains only to the y-value length of the cell. The lengths of the x and y-values provide the dataset?s resolution. If the x and y values both equal 30 metres, then the surface area covered represents 30 x 30 metres or 900 square metres.

Name	SMALLEST ADMINISTRATIVE UNIT
identifier	37
Type	element
Parent entity group	G3: Data Quality (Quality)
Parent entity subgroup	G3.3: Level of Spatial Detail
Definition	The smallest representative unit associated with disaggregated statistical data.
Obligation type	Optional
Obligation detail	The Smallest Administrative Unit element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	There are cases when scale or resolution do not apply or are unknown. If the data collected are based on areas defined within representative units, then the smallest disaggregated representative unit in which data were collected can be used to define the smallest administrative unit. If a county-wide survey has been conducted using parishes as disaggregated areas or sampling units for data collection, ?parish? would be listed as the smallest representative unit.

Name	SPATIAL REFERENCE SYSTEM USED FOR THE BOUNDING RECTANGLE / BOUNDING POLYGON
identifier	38
Type	element
Parent entity group	G4: Extents of Dataset (Where/When)
Parent entity subgroup	Not Applicable
Definition	Name of the spatial reference system used for the geographic co-ordinates of the study area?s extent.
Obligation type	Mandatory
Obligation detail	The Spatial Reference System Used for the Bounding Rectangle/Bounding Polygon element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Data type domain	AGMAP Element 1) British National Grid 2) Irish National Grid 3) Latitude and Longitude
Comments	This element states which spatial referencing system is used to provide the co-ordinates for the farthest western, eastern, northern and southern points of a bounding rectangle, which defines the extents of a dataset?s study area. This has nothing to do with the internal spatial reference system of the dataset, which is stated under Metadata subgroup G2.1-20 (Spatial Reference System). Co-ordinates for both the British and Irish National Grids are based on Easting and Northing measurements expressed in metric units. Latitude/longitude are measured in degrees/minutes/seconds and need to be converted to decimal degree units. The Irish National Grid System applies to study areas associated with Northern Ireland and the Republic of Ireland. Please see examples for further details.
Examples	None

Name	WEST BOUNDING CO-ORDINATE
identifier	39
Type	element
Parent entity group	G4: Extents of Dataset (Where/When)
Parent entity subgroup	G4.1: Extents of Dataset Based on Coordinates of Bounding Rectangle
Definition	Westernmost co-ordinate of a bounding rectangle.
Obligation type	Mandatory
Obligation detail	The West Bounding Co-ordinate element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Data type domain	Grid or Longitude Value (Real Number)
Comments	This element lists the geospatial co-ordinate of a point representing the farthest westernmost extent of a dataset?s study area. The co-ordinate value can be expressed as a National Grid co-ordinate or in longitude of a geographic co-ordinate. Grid co-ordinates should be expressed in metric units to the nearest kilometre or as a longitude value to the nearest hundredth of a degree (0.01). In terms of longitude, any value that is west of the Prime Meridian (Greenwich Meridian) must be expressed as a negative number. Degrees of longitude to the east of the meridian are expressed as positive numbers. It is recommended that the rectangle co-ordinates of a sensitive study area be generalised to assure that the actual location is not revealed to the general public. Such study areas might include archaeological sites and endangered species habitats.

Name	EAST BOUNDING CO-ORDINATE
identifier	40
Type	element
Parent entity group	G4: Extents of Dataset (Where/When)
Parent entity subgroup	G4.1: Extents of Dataset Based on Coordinates of Bounding Rectangle
Definition	Easternmost co-ordinate of a bounding rectangle.
Obligation type	Mandatory
Obligation detail	The East Bounding Co-ordinate element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Data type domain	Grid or Longitude Value (Real Number)
Comments	This element lists the geospatial co-ordinate of a point representing the farthest easternmost extent of a dataset?s study area. The co-ordinate value can be expressed as a National Grid co-ordinate or in longitude of a geographic co-ordinate. Grid co-ordinates should be expressed in metric units to the nearest kilometre or as a longitude value to the nearest hundredth of a degree (0.01). In terms of longitude, any value that is west of the Prime Meridian (Greenwich Meridian) must be expressed as a negative number. Degrees of longitude to the east of the meridian are expressed as positive numbers. There are several web sites that provide converters for latitude/longitude to decimal degree conversions. The example box will also include conversion examples. It is recommended that the rectangle co-ordinates of a sensitive study area be generalised to assure that the actual location is not revealed to the general public. Such study areas might include archaeological sites and endangered species habitats.

Name	NORTH BOUNDING CO-ORDINATE
identifier	41
Type	element
Parent entity group	G4: Extents of Dataset (Where/When)
Parent entity subgroup	G4.1: Extents of Dataset Based on Coordinates of Bounding Rectangle
Definition	Northernmost co-ordinate of a bounding rectangle.
Obligation type	Mandatory
Obligation detail	The North Bounding Co-ordinate element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Data type domain	Grid or Latitude Value (Real Number)
Comments	This element lists the geospatial co-ordinate of a point representing the farthest northernmost extent of a dataset?s study area. The co-ordinate value can be expressed as a National Grid co-ordinate or in latitude of a geographic co-ordinate. Grid co-ordinates should be expressed in metric units to the nearest kilometre or as a longitude value to the nearest hundredth of a degree (0.01). Though no part of the British Isles lies near the equator, it is important to note that in terms of latitude, any value that is south of the equator must be expressed as a negative number. Degrees of latitude to the north of the Equator are expressed as positive numbers. Because the British Isles are wholly north of the Equator, all latitudinal values will be positive. It is recommended that the rectangle co-ordinates of a sensitive study area be generalised to assure that the actual location is not revealed to the general public. Such study areas might include archaeological sites and endangered species habitats.

Name	SOUTH BOUNDING CO-ORDINATE
identifier	42
Type	element
Parent entity group	G4: Extents of Dataset (Where/When)
Parent entity subgroup	G4.1: Extents of Dataset Based on Coordinates of Bounding Rectangle
Definition	Southernmost co-ordinate of a bounding rectangle.
Obligation type	Mandatory
Obligation detail	The South Bounding Co-ordinate element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Data type domain	Grid or Latitude Value (Real Number)
Comments	This element lists the geospatial co-ordinate of a point representing the farthest southernmost extent of a dataset?s study area. The co-ordinate value can be expressed as a National Grid co-ordinate or in latitude of a geographic co-ordinate. Grid co-ordinates should be expressed in metric units to the nearest kilometre or as a longitude value to the nearest hundredth of a degree (0.01). Though no part of the British Isles lies near the equator, it is important to note that in terms of latitude, any value that is south of the equator must be expressed as a negative number. Degrees of latitude to the north of the Equator are expressed as positive numbers. Because the British Isles are wholly north of the Equator, all latitudinal values will be positive. It is recommended that the rectangle co-ordinates of a sensitive study area be generalised to assure that the actual location is not revealed to the general public. Such study areas might include archaeological sites and endangered species habitats.

Name	SPATIAL REFERENCING USING CO-ORDINATES OF A BOUNDING POLYGON
identifier	43
Type	element
Parent entity group	G4: Extents of Dataset (Where/When)
Parent entity subgroup	G4.2: Extents of Dataset Based on Coordinates of Bounding Polygon
Definition	The set of x and y co-ordinates (first number = easting of a point, second number = northing of a point) that make up the bounding polygon.
Obligation type	Optional
Obligation detail	The Spatial Referencing Using Co-ordinates of a Bounding Polygon element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Unlimited
Data type	Free text
Data type domain	Real Number
Comments	It is hoped that a tool may be provided in the future for capturing the x and y co-ordinates of a bounding polygon. As it stands now, the effort to collect and enter all the x and y values would be extremely time consuming. There are some existing Geographic Information System (GIS) software packages that will capture these co-ordinates, but conversion represents an obstacle. Entering a limited number of values of a bounding polygon might be considered as an option for capturing co-ordinates of an area that resembles the shape of the study area?s extent. This is somewhat more precise than the bounding rectangle, which defines an area within a box and includes a greater area outside the study area unless its dimensions are similar to a rectangle. Please see example. It is recommended that the polygon co-ordinates of a sensitive study area be generalised to assure that the actual location is not revealed to the general public. Such study areas might include archaeological sites and endangered species habitats.

Name	NATIONS
identifier	44
Type	element
Parent entity group	G4: Extents of Dataset (Where/When)
Parent entity subgroup	G4.3: Extents of Dataset Based on Geographic Identifiers
Definition	Geographic coverage expressed in terms of nations within the British Isles.
Obligation type	Optional
Obligation detail	The Nations element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Unlimited
Data type	Free text
Data type domain	UK GEMINI Extent List 1) England 2) England and Wales 3) Great Britain 4) Northern Ireland 5) Scotland 6) Wales 7) Isle of Man 8) Channel Islands 9) United Kingdom
Comments	Select the relevant name(s) on the Nations list. The study area extent of a dataset should cover most, if not all of a nation. If the study area extends over only a part of a nation, then consider using Administrative Areas or Postcode Districts elements instead to define the extent. Another option would be to use a combination of Nations, Administrative Areas and Postcode Districts elements to define the study area. This would be practical for data collected at various geographic identifier levels as opposed to one.

Name	ADMINISTRATIVE AREAS
identifier	45
Type	element
Parent entity group	G4: Extents of Dataset (Where/When)
Parent entity subgroup	G4.3: Extents of Dataset Based on Geographic Identifiers
Definition	Geographic coverage expressed in terms of administrative areas.
Obligation type	Optional
Obligation detail	The Administrative Areas element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Unlimited
Data type	Free text
Comments	Enter the relevant name(s) for the ADMINISTRATIVE AREA. The extent of the study area of a dataset can cover either the entire administrative area or a portion of it in order for the area to be considered a valid entry. If nations or postcode districts provide a better representation of the study area, consider using them to define the extent rather than administrative areas. Another option would be to use a combination of Nations, Administrative Areas and Postcode Districts elements to define the study area. This would be practical for data collected at various geographic identifier levels as opposed to one.

Name	POSTCODE DISTRICTS
identifier	46
Type	element
Parent entity group	G4: Extents of Dataset (Where/When)
Parent entity subgroup	G4.3: Extents of Dataset Based on Geographic Identifiers
Definition	Geographic coverage expressed in terms of postcode districts.
Obligation type	Mandatory (searchable)
Obligation detail	The Postcode Districts element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Unlimited
Data type	Free text
Comments	Please refer to existing postcode sources such as All Fields Postcode Directory (AFPD). These can be found at EDINA?s UKBORDERS website. http://edina.ac.uk/ukborders/ Enter the relevant postcode(s). The extent of the study area of a dataset can cover either the entire postcode district or a portion of it in order for the district to be considered a valid entry. Another option would be to use a combination of Nations, Administrative Areas and Postcode Districts elements to define the study area. This would be practical for data collected at various geographic identifier levels as opposed to one.

Name	CONTROLLED PLACE NAME VOCABULARY
identifier	47
Type	element
Parent entity group	G4: Extents of Dataset (Where/When)
Parent entity subgroup	G4.3: Extents of Dataset Based on Geographic Identifiers
Definition	Name of the controlled vocabulary used as a source for the controlled place name keywords.
Obligation type	Optional
Obligation detail	The Controlled Place Name Vocabulary element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Comments	Currently, the Ordnance Survey (OS) 1:50,000 gazetteer is available to those organisations with DIGIMAP service. This gazetteer represents one source for Controlled Place Name Keywords, thus it is the default input for the Controlled Place Name Vocabulary field. The geo-X-walk gazetteer will eventually replace the OS gazetteer as a place name source at a later undetermined date. The Getty Thesaurus of Geographic Names represents a second source for place name keywords for those without access to the OS 1:50,000 gazetteer. It is anticipated that, geoXwalk, a controlled place name gazetteer will be added at a later date, which will replace the aforementioned gazetteers. This gazetteer provides comprehensive coverage for the United Kingdom.

Name	CONTROLLED PLACE NAME KEYWORDS
identifier	48
Type	element
Parent entity group	G4: Extents of Dataset (Where/When)
Parent entity subgroup	G4.3: Extents of Dataset Based on Geographic Identifiers
Definition	The geographic name of a location(s) covered by a dataset.
Obligation type	Optional
Obligation detail	The Controlled Place Name Keywords element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Unlimited
Data type	Free text
Data type domain	See comments.
Comments	These are controlled keywords that are found in the Ordnance Survey (OS) 1:50,000 gazetteer and are used to provide the geographic location(s) that are covered by the dataset. Search for place name keywords using the DIGIMAP Ordnance Survey 1:50,000 gazetteer. If access isn?t available to the DIGIMAP service, then enter all relevant place names and these will be checked automatically and updated to conform with the OS gazetteer. No abbreviations should be used for place names (e.g: ?UK? for the United Kingdom?). Selection of the correct place name to define the same area also needs to be considered. The choice between British Isles, Great Britain and United Kingdom may pose a problem for those unfamiliar with the regional geography. The United Kingdom pertains to England, Northern Ireland, Scotland and Wales. Great Britain comprises England, Scotland and Wales, and the British Isles represent all the islands and nations, including the Republic of Ireland, the Isle of Man and the Channel Islands. A hierarchical listing of place names should also be entered in the Controlled Place Name Keywords element?s field. This would include a range of names for nations and local areas associated with the study area. Examples are provided in the example box below. For those without access to the OS 1:50,000 gazetteer, the Getty Thesaurus of Geographic Names may also be used. This site can be reached at the following web address: http://www.getty.edu/research/tools/vocabulary/tgn/index.html

Name	MINIMUM VALUE
identifier	49
Type	element
Parent entity group	G4: Extents of Dataset (Where/When)
Parent entity subgroup	G4.4: Vertical Extents of Dataset
Definition	Lowest vertical extent contained in the dataset.
Obligation type	Optional
Obligation detail	If value entered for any element in VERTICAL EXTENTS OF A DATASET group, then the Minimum Value element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Data type domain	Real Number
Comments	The minimum value of the highest vertical extent can be declared in UK (Imperial) or Metric System of Measurements. This must be consistent with the value entered for the Unit of Measure AGMAP element G4.4-51. If the former is used, then the value entered for G4.4-51 could be inches, feet et al; the value for the latter could millimetres, centimetres, metres, et al. Negative values can be entered, though there are only a few places in Britain where the land area is below sea level. The Fens, considered the lowest point in Britain, is estimated to be at an elevation of -2.75 metres.

Name	MAXIMUM VALUE
identifier	50
Type	element
Parent entity group	G4: Extents of Dataset (Where/When)
Parent entity subgroup	G4.4: Vertical Extents of Dataset
Definition	Highest vertical extent contained in the dataset.
Obligation type	Conditional
Obligation detail	If value entered for any element in VERTICAL EXTENTS OF A DATASET group, then the Maximum Value element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Data type domain	Real Number
Comments	The maximum value of the highest vertical extent can be declared in UK (Imperial) or Metric System of Measurements. This must be consistent with the value entered for the Unit of Measure AGMAP element G4.4-51. If the former is used, then the value entered for G4.4-51 could be inches, feet et al; the value for the latter could millimetres, centimetres, metres, et al. This represents the highest elevation value of a dataset, which is typically associated with Digital Elevation Models (DEM). The highest known point in Britain is Ben Nevis, with an elevation of 1,343 metres.

Name	UNIT OF MEASURE
identifier	51
Type	element
Parent entity group	G4: Extents of Dataset (Where/When)
Parent entity subgroup	G4.4: Vertical Extents of Dataset
Definition	Vertical units used for vertical extent.
Obligation type	Conditional
Obligation detail	If value entered for any element in VERTICAL EXTENTS OF A DATASET group, then the Unit of Measure element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	The Unit of Measure value can be based on UK (Imperial) or Metric System of Measurements. Typically, units of measurement are expressed in feet or metres.
Examples	1) Feet 2) Metres

Name	VERTICAL DATUM
identifier	52
Type	element
Parent entity group	G4: Extents of Dataset (Where/When)
Parent entity subgroup	G4.4: Vertical Extents of Dataset
Definition	The origin from which the elevation values are measured.
Obligation type	Conditional
Obligation detail	If value entered for any element in VERTICAL EXTENTS OF A DATASET group, then the Vertical Datum element must have information entered in its field.
Max. occurrence type	Once
Data type	Free text
Comments	Enter Ordnance Datum Newlyn (ODN) as the value for vertical extents in Britain and Malin Head for Northern Ireland. Ordnance Datum Newlyn (ODN), a traditional vertical coordinate system, consisting of a tide gauge datum with initial point at Newlyn (Cornwall) and a terrestrial reference frame (TRF) observed by spirit levelling between 200 fundamental bench marks (FBMs) across Britain. The TRF is densified by more than half a million lower-accuracy bench marks. Each bench mark has an orthometric height only (not ellipsoid height or accurate horizontal position). This coordinate system is important because it is used to describe vertical positions of features on British maps (for example, spot heights and contours) in terms of height above mean sea level. Again, its historical origins and observation methods are not of interest to most users. The word Datum in the title refers, strictly speaking, to the tide gauge initial point only, not to the national TRF of levelled bench marks. The Malin Head Datum for Northern Ireland is fixed as Mean Seal Level of the tide gauge at Malin Head, County Donegal. It was adopted as the national datum in 1970 from readings taken between January 1960 and December 1969. All heights on National Grid mapping since then are in International metres above this datum.
Examples	1) Ordnance Datum Newlyn (ODN) 2) Malin Head

Name	START DATE FOR TIME PERIOD COVERED BY THE DATASET
identifier	53
Type	element
Parent entity group	G4: Extents of Dataset (Where/When)
Parent entity subgroup	G4.5: Temporal Extents of Dataset
Definition	The start date of the actual time period the dataset covers.
Obligation type	Optional
Obligation detail	The Start Date for Time Period Covered by Dataset element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Data type domain	YYYY-MM-DD
Comments	This element captures the temporal aspects of the data or content of the dataset. The start date represents the beginning of the time period associated with the dataset. It can be a period of time that is different from the data capture period, or it can correspond with the data capture period if it represents a snapshot in which both are contemporaneous. The date format is based on ISO 8601, which is expressed as YYYY-MM-DD (Year-Month-Day), and uses hyphens ?-? as separators. It is based on the Gregorian Calendar but denoted using the ?Common Era Calendar? format. Numbers that are less than 10 for day and month are written with a leading zero. Leading zeroes are also added for year dates that fall between 1000 BC and AD 1000. For dates preceding the Year AD 1, then a ?-? (minus) sign or hyphen is used to signify BC dates.
Examples	1) 2001-01-31 (Entire date known, including year, month and day day) 2) 2001-01 (Year and month of date known, but not day) not day) 3) 2001 (Year known, but not month and day) 4) -0055 (The year 55 BC) 5) 0450 (The year AD 450)

Name	END DATE FOR TIME PERIOD COVERED BY THE DATASET
identifier	54
Type	element
Parent entity group	G4: Extents of Dataset (Where/When)
Parent entity subgroup	G4.5: Temporal Extents of Dataset
Definition	The end date of the actual time period the dataset covers.
Obligation type	Optional
Obligation detail	The End Date for Time Period Covered by Dataset element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Data type domain	YYYY-MM-DD
Comments	This element captures the temporal aspects of the data or content of the dataset. The start date represents the ending of the time period associated with the dataset. It can be a period of time that is different from the data capture period, or it can correspond with the data capture period if it represents a snapshot in which both are contemporaneous. The date format is based on ISO 8601, which is expressed in a YYYY-MM-DD format, with hyphens as separators, and based on the Gregorian Calendar but denoted using the ?Common Era Calendar? format. Numbers that are less than 10 for day and month are written with a leading zero. Leading zeroes are also added for year dates that fall between 1000 BC and AD 1000. For dates preceding the Year AD 1, then a ?-? (minus) sign or hyphen is used to signify BC dates.
Examples	1) 2001-01-31 (Entire date known, including year, month and day day) 2) 2001-01 (Year and month of date known, but not day) not day) 3) 2001 (Year known, but not month and day) 4) -0055 (The year 55 BC) 5) 0450 (The year AD 450)

Name	DATASET FILE SIZE
identifier	77
Type	element
Parent entity group	G6: Distributor (Access)
Parent entity subgroup	Not Applicable
Definition	The name of the World Wide Web site or other on-line source that contains the dataset.
Obligation type	Optional
Obligation detail	The Dataset File Size element does not require information to be entered in its field, but it is recommended if applicable.
Max. occurrence type	Once
Data type	Free text
Data type domain	Real Number
Comments	The estimated size of a file or unit in the specified transfer format expressed in megabytes. A value of 284.0 would be entered for a 284 kilobyte file and a value of 0.56 would be entered as a value for a 56 kilobyte file. A dataset comprising multiple files would require entering a value that includes the total sum of all files. The Clark Labs Idrisi Kilimanjaro software package generates three files for a vector dataset, e.g.: dataset.mdb (345 kilobytes), dataset.vct (3,250 kilobytes) and dataset.vdc (1 kilobyte). The value entered for these combined files would be 3.596 (345 + 3,250 + 1 = 3,596 kilobytes or 3.596 megabytes or 0.345 + 3.250 + 0.001 = 3.596 megabytes). Remember to perform addition using the same configuration (bytes).
Examples	1) 284.0 2) 0.56