UK Academic Geospatial Metadata Application Profile (UK AGMAP) Guidelines Version 1.0
€ Crown Copyright/database right 2008
TABLE OF CONTENTS 1.0 Introduction............................................................................................................3 1.1 What are Metadata ..............................................................................................3 1.2 What are the Benefits of Creating Geospatial Metadata?....................................3 1.3 Go-Geo! UK Academic Geospatial Metadata Application Profile (UK AGMAP) Overview.......................................................................................................................4 1.4 Metadata Entities and Element Groups ...............................................................6 1.5 Guideline Review Notes for Users .....................................................................10 2.0 UK AGMAP element and entity attributes .........................................................15 3.0 Appendix A (UK AGMAP) .................................................................................. 115 4.0 Appendix B (Examples)..................................................................................... 128 5.0 Glossary and References.................................................................................. 174 6.0 Bibliography....................................................................................................... 177
2
1.0 Introduction
This document presents the first version of the Go-Geo! UK Academic Geospatial Metadata Application Profile (UK AGMAP) Guidelines, which have been written to serve as a reference resource for individuals and organisations within Higher and Further Education wishing to document and create metadata records for their spatial datasets. Use of these guidelines can also ensure that compliant metadata can be created for publication on the Go-Geo! portal (www.gogeo.ac.uk) or support of institutional or departmental spatial data management schemes. 1.1 What are Metadata Metadata represent an ordered summary of information that describes something, in this case, a geospatial dataset. These details include the What, Where, When, Who and Why of the dataset, plus the means to access and use it. Metadata reveal information that isn’t apparent when looking at dataset files in a directory. The details of a dataset are embedded in the metadata file and often address the following questions:
What is the purpose of the dataset? Where did the dataset originate? What attribute information does it contain? What processes or algorithms were employed to create it? What spatial reference system does the dataset use? What is the granularity of the data? When was the dataset created? What time period does the dataset content cover? What geographic area or extent does it cover? Whom do I contact for more information or access to the dataset? How do I obtain the dataset? What are the access and use restrictions and how much will it cost? Who is responsible for creating the metadata record for the dataset?
If these questions can be answered this ensures and instils confidence that the information in the metadata file can be accessed quickly and preserved for future reference. It also means that metadata can serve as a medium for the HFE geospatial community to discover and share datasets. This is most often achieved through gateway and portal technology. It is this technology that the Go-Geo! UK Academic Geospatial Metadata Application Profile and guidelines serve. 1.2 What are the Benefits of Creating Geospatial Metadata? A data creator might not consider geospatial metadata relevant or important. However, there are many benefits to be considered. Geospatial metadata creation can achieve the following:
provides support to create a mindset and operational structure for managing and storing dataset information for departmental and intra-departmental use; ensures integrity of existing and new datasets using metadata as a tracking mechanism to monitor changes and edits to datasets; maintains an inventory of datasets to reduce redundancy and time required to reassess existing datasets for new and future applications;
3
eliminates or reduces the risk of redundancy in data collection or deletion of existing datasets; reduces effects of staff turnover and minimises its disruptive effects; protects investments of time and cost dedicated to data development; ensures that other organisations will not replicate data at added cost and time; provides potential users with a dataset catalogue to view and select datasets to complement or augment existing in-house datasets for new applications; allows for more spontaneity amongst users as they browse the Go-Geo! portal and metadata; the discovery of a dataset may instigate the user to develop an idea for a new application; metadata on the portal can be referenced and cited for project proposals; the portal’s node can serve as a repository for organisations to locally store, manage and share their metadata and data; can provide a quick, short-term solution for data creators to announce their datasets and applications; allows organisations and individuals to advertise and sell their datasets to other interested parties in academia and in the private and public sectors; interoperability between the Go-Geo! portal, GIgateway and other geo-data portals allows for data advertisement to reach a large audience of data users; and the metadata and portal will complement and augment other UK academic portals, JISC projects and collections and the GIgateway site.
1.3 Go-Geo! UK Academic Geospatial Metadata Application Profile (UK AGMAP) Overview The Go-Geo! UK Academic Geospatial Metadata Application Profile (UK AGMAP), (Appendix A) is a template designed to support the documentation and discovery of spatial datasets within Higher and Further Education. The Profile contains all the elements, required to generate compliant metadata records for the Go-Geo! portal. In addition, the Profile was created to achieve the following:
serve as a metadata element field template for the Go-Geo! portal and the GeoDoc metadata editor tool; deliver support of geospatial dataset documentation across an eclectic academic community; facilitate data management and sharing requirements within academia; ensure compliance with the new ISO 19115 geospatial metadata standard and ISO 19115 compliant UK GEMINI, which was ratified in 2004 and supersedes the National Geospatial Data Framework (NGDF) for the UK; and provide academic users the necessary information to reveal the dataset type, its location, quality and completeness, temporal aspects in terms of data collection and content and contact details that allows users to acquire the dataset.
4
The UK AGMAP profile is based primarily on ISO 19115, the international geographic information metadata standard which was ratified in 2003. ISO 19115 comprises and defines more than 300 metadata elements that can be used to describe spatial datasets. These elements are available for geographic information (GI) communities to select and use to generate community profiles to support dataset documentation. ISO 19115 provides a small core element group of mandatory elements that should be incorporated every profile. The numerous optional ISO 19115 elements available for profile creation can support a range of needs at the GI community level, whether it be the public or private sector or academia. The incorporation of these elements into a profile should be intended to support the documentation of datasets generally created within a specific GI community. In addition, a profile can be extended to provide further benefits each community. In this instance, metadata elements are included in the profile to ensure document support to describe a spatial dataset’s specific conditions that would be relevant to data users within a specialised community. Often, there are no equivalents in the ISO 19115 standard to support this level of detail in a spatial dataset, but augmenting a profile with these elements best serves the intended GI community. This stresses the importance of the inclusion of ISO 19115 core mandatory elements in all profiles to ensure that data users outside a specialised GI community can discover these and all other spatial datasets using any geo-data portal. The UK AGMAP profile (Figure 1) comprises the ISO 19115 core mandatory elements and a considerable number of its optional elements. The optional elements have been selected based on the eclectic nature of academic disciplines using GI technology for research and teaching and learning. These elements also provide further information that describes a dataset in detail including applications, quality assessment, processing steps and feature descriptions. Inclusion of this detailed metadata information allows a potential user the opportunity to assess the suitability of a dataset for a specific application or serve as a support mechanism for local data management. In addition, the UK AGMAP profile includes elements which provide contact details or on-line links so that a data user can access the dataset.
Figure 1. UK AGMAP profile for UK academia The UK AGMAP profile is also extended to support specialised needs of the academic community and ensure interoperability between other UK spatial data portals. Part of this extension includes 41 elements from UK GEMINI, an ISO 19115-compliant standard ratified in 2004 for use in the UK geospatial community. UK GEMINI (2004) supersedes the National Geospatial Data Framework (NGDF) (2000), the previous UK metadata standard for geospatial data, which was originally derived from the US Federal Geographic Data Committee’s (FGDC) Content Standard for Digital Geospatial Metadata (CSDGM).
5
The UK AGMAP profile provides 97 elements which can be used for describing the when, where, how and what of a dataset, its access and use conditions and the metadata record itself. Though the total number of elements in the UK AGMAP profile is considerable, only 36 of these elements are mandatory. Providing information for only these 36 elements will satisfy the minimum conditions required for creating a compliant metadata record. This makes the task of metadata creation less onerous, and considering that 15 of these 36 mandatory elements require only contact information, a metadata creator can produce a template file containing these contact details. Subsequently, this information can be transferred to each new metadata record, hence demanding even less time of the metadata creator. It should be worth noting that almost half (nine) of the remaining mandatory elements include lists, so the metadata creator only needs to select the relevant values, which have been incorporated into the GeoDoc metadata editor tool. Combined, the UK AGMAP profile elements reflect and support the eclectic range of disciplines within academia using geospatial technology for research and training purposes and provide the academic user the information required to assess the dataset type, its location, quality and completeness, temporal aspects in terms of data collection and content, and the necessary contact details to inquire further about access and use. The Go-Geo! portal, the GeoDoc metadata editor tool and metadata resources primarily support spatial data captured and generated within the United Kingdom, but GeoDoc also offers users an interface to document international spatial datasets. There are minor differences such as the ‘Nation’ element offering a list of all nations, and the ‘Coordinate System’ element list including only ‘Latitude and Longitude’ for a value. The UK version’s element list includes ‘Latitude and Longitude’, British National Grid and ‘Irish Grid’. This is to support the documentation (extent) of spatial data created in Britain and Northern Ireland. 1.4 Metadata Entities and Element Groups UK AGMAP uses seven metadata compound element or entity headings to categorise and group the 97 elements. As a means to provide further clarification for metadata creators and editors, metadata entity subheadings were also created to separate and categorise relevant elements into subgroups. The metadata entity headings and subheadings are as follows: G1 G2 G3 Citation (8 elements); Identification Information (What) (12 elements); G2.1 Spatial Reference System of the Dataset Data Quality Information (17 elements); G3.1 Data Process Steps G3.2 Data Quality Statement G3.3 Level of Spatial Detail Extents of Dataset (Where and When) (17 element); G4.1 Extents of a Dataset Based on the Co-ordinates of a Bounding Rectangle G4.2 Extents of a Dataset Based on the Co-ordinates of a Bounding Polygon G4.3 Extents of a Dataset Based on Geographic Identifiers G4.4 Vertical Extents of a Dataset G4.5 Temporal Extents of a Dataset Custodian (Who) (10 element); Distributor (Access) (19 elements); G6.1 Dataset Name and Format G6.2 Access and Use Constraints Metadata Creator (14 elements).
6
G4
G5 G6
G7
A complete structural diagram of the UK AGMAP profile can be found on page 11, with a more detailed presentation of UK AGMAP in Appendix A. The use of these metadata entity headings and subheadings provides the structure to arrange the elements into logical and user friendly groupings. This in turn directs users to the entity group sections as they navigate through the guidelines to find the relevant elements to reference. This arrangement also offers support to the template design for the metadata results pages on the Go-Geo! portal (Figure 2) as well as the GeoDoc metadata editor tool (Figure 3).
Figure 2. A metadata record displayed on the Go-Geo! Portal with UK AGMAP elements which are used to describe a dataset (under the ‘What’ tab).
7
Figure 3. GeoDoc metadata editor tool with UK AGMAP elements which are used to describe the spatial and temporal extent of a dataset (under ‘Where/When section). Each element displayed with metadata records on Go-Geo! is also directly linked to the page in the guidelines holding specific information about that element. In the event a user is unfamiliar with an element on the metadata results page, the element can be clicked with the mouse which then opens a window containing this information (Figure 4).
8
Figure 4. Example of direct link between ‘Edition’ element in Go-Geo! Metadata record and relevant page in UK AGMAP guidelines holding specific information for that element.
Figure 5. Example of direct link between Start Date for Time Period Covered by Dataset’ element in GeoDoc metadata editor tool and relevant page in UK AGMAP guidelines holding specific information for that element.
9
The UK AGMAP profile and guidelines should establish an effective, streamlined system that introduces clear and logical steps in the process of creating complete and compliant metadata that can be displayed on the Go-Geo! portal or used for internal management of dataset documentation. Most importantly, the UK AGMAP Profile ensures continuity, through a common thread or language, which is written and understood by an eclectic academic geospatial community. 1.5 Guideline Review Notes for Users The guideline pages introduce each entity and element name to the user. Included with each entity and element name is a set of attributes, which include obligation, occurrence, identifier, data type, domain, comments and examples. These are discussed in greater detail on page 7. Combined, these attributes provide the information and guidance necessary for the metadata creator to produce accurate and compliant metadata, especially for organisations generating their own records using a template built into a word processing, spreadsheet or database file. The guidelines also serve as a supplementary reference for users of the GoGeo! Portal and GeoDoc metadata editor tool. The names and attributes are presented in a tabular format. Entity and element names, and their associated attributes, are referred to as a section. The name and attributes are presented in the left column with relevant content in the right column; the 11 attributes comprise the following:
Entity Name Element Name Identifier Definition of Entity Definition of Element Obligation Maximum Occurrence Data Type Domain Comments Examples
Each attribute is separated into rows/boxes and when an attribute isn’t relevant, and reference is to the other name (element or entity), the text is faded in grey (e.g.: Entity Name or Not Applicable). There are a number of elements that require additional examples to provide greater clarity for the user. In this instance, there is a link to a supplemental examples document. References to page numbers are also included for those who wish to print the guidelines and examples supplement. This document represents an extension to the guidelines and contains examples that address a broader audience. These are meant to address disciplines such as archaeology and anthropology, biological sciences, civil engineering, earth sciences, environmental sciences, geography, health sciences, history and sociology. This approach is intended to introduce examples in a manner that is clear to the specific discipline. Too often, geospatial metadata guidelines are written in a generic fashion or specifically for the geographical information community. Each entity section provides a complete list of its group of elements in the comment box. If there are entity subheadings, these are also included in the comment box. An overview of the attribute list and definitions follows (Table 1), along with the UK AGMAP’s structural framework (Table 2), element and entity attribute guidelines index (Table 3) and the complete element and entity attribute guidelines (Table 4).
10
Table 1. UK AGMAP element and entity attribute overview of conditions and definitions. ATTRIBUTE DEFINITION HEADING Identifier An alpha-numeric reference applied to each entity and element. The elements are numbered sequentially from 1 to 97. The entities are referred to as Metadata Entities for Element Groups. There are seven main element groups, so the entity heading sequence is G1 to G7. Subheadings that fall under some of these groups are presented in the following format: G5.1. (Group 5.subgroup 1). This type of coding convention addresses the hierarchical nature of the UK AGMAP Profile which is intended to categorise and collate similar elements into groups with descriptive headings and subheadings. Definition of Provides a brief description of the entity or element. Entity/ Element Obligation States the obligation of the metadata creator to use and provide information for an element. When applied to an entity, it suggests that the stated obligation applies to one or many of its elements. These are the following obligations: (M) Mandatory. The element or an entity’s element(s) requires information. In these instances, the word Mandatory will be presented in bold to bring this to the attention of the user. (O) Optional. The element or an entity’s element(s) does not require information, but it is recommended if applicable and available. (C) Conditional. Elements that are conditional are paired with other elements in such a way that where one element is used, the other one must also be used, for the record to make sense, and therefore one element becomes mandatory. This relationship of dependency is explained for each element that has a conditional obligation. Maximum Occurrence This specifies the number of instances that an element can be repeated. A single occurrence is displayed as ‘1’ and ‘N’ is used for one or more occurrences. The Dataset Title element allows for only one ‘1’ title. The Alternative Dataset Title element allows for more than one ‘N’, so an unlimited number of titles related to the same dataset can be entered in the element’s field. Refers to the data type applicable to each field. An entity is not a data type, but elements assume various data types. These include Character String, Enumerated Lists, Real Numbers, Integers and Dates. Character string elements can have free text entered and Dates are entered using the ISO 8601 format (YYYY-DD-MM). Specifies the values allowed for each metadata element. These include predefined lists of terms for the enumerated list, free text for character string, date in the ISO 8601 format and numeric values for real numbers and integers. Some elements include UK GEMINI and ISO 19115 enumerated lists. The ISO 19115 lists include numeric codes which are machine readable, but aren’t user friendly, so metadata creators using the GeoDoc metadata editor tool will only see the list of terms and not the codes. Comments provide additional details, guidance and references for the metadata creator. They can be used to introduce element groups and entity subheadings. This is also a means to explain and demonstrate further the type of information, and its format, to be entered for the respective element; each example presented comes numbered sequentially, and when relevant, includes comments stated within brackets, e.g.: 1) 2001-0131 [ Entire date known, including year, month and day ]. Here, the value for a dataset published on 24 October 2004 would be entered as 2004-10-24. Examples are also provided for the various disciplines within academia. These include Archaeology and Anthropology, Biological Sciences, Civil Engineering, Earth Sciences, Environmental Sciences, Geography, Health Sciences, History and Sociology. More complex and detailed overviews of some examples are provided to Appendix B.
Data Type
Domain
Comments Examples
11
Table 2. Structure of UK AGMAP Identification Data Quality Citation Information Information
Dataset Title Dataset Language Data Hierarchical Level
*Red text connotes mandatory elements
Extents of a Dataset
Spatial Reference System used for the Bounding Rectangle/ Bounding Polygon
Custodian
Name of Custodian
Distributor
Name of Distributor
Metadata Creator
Name of Metadata Creator
Alternative Dataset Title
Dataset Topic
Data Process Steps
Status of Data Creation Process Start Date of Data Capture Period End Date of Data Capture Period Dataset Lineage
Extents of a Dataset Based on Co-ordinates of a Bounding Rectangle
West Bounding Co-ordinate East Bounding Co-ordinate North Bounding Co-ordinate South Bounding Co-ordinate
Postal Street Address of Custodian Postal City of Custodian Postal County of Custodian Postal Code of Custodian Postal Country of Custodian Telephone Number of Custodian Facsimile Number of Custodian Email Address of Custodian Web Address of Custodian
Distributor Contact Title Postal Street Address of Distributor Postal City of Distributor Postal Code of Distributor Postal Country of Distributor Telephone Number of Distributor Facsimile Number of Distributor Email Address of Distributor Web Address of Distributor Supply Media
Postal Street Address of Metadata Creator Postal City of Metadata Creator Postal Code of Metadata Creator Postal Country of Metadata Creator Telephone Number of Metadata Creator
Creator Identifier Edition Dataset Date Code Dataset Event Date Dataset Update Frequency
Controlled Vocabulary Controlled Keywords Other Keywords Abstract
Spatial Representation Type Presentation Type
Description of Dataset Process Steps
Extents of a Dataset Based on Co-ordinates of a Bounding Polygon
Co-ordinates of a Bounding Polygon
Facsimile Number of Metadata Creator
Data Quality Statement
Logical Consistency
Email Address of Metadata Creator
Sample
Extents of a Dataset Based on Geographic Identifiers
Nations Administrative Areas
Web Address of Metadata Creator Metadata Record Identifier Parent Metadata Record Identifier Metadata Last Updated
Further Information Related Datasets
Completeness Spatial Accuracy
Spatial Reference System of the Dataset
Spatial Reference System
Attribute Accuracy
Postcode Districts
On-line Linkage
Level of Spatial Detail
Source Scale Denominator Ground Scale Distance Imagery or Grid Dimension Name Imagery or Grid Raster Cell/Pixel Size (X-Value) Imagery or Grid Dimension Name Imagery or Grid Raster Cell/Pixel Size (Y-Value) Smallest Administrative Unit
Controlled Place Name Vocabulary Controlled Place Name Keywords
Dataset File Size
Metadata Standard Name Metadata Standard Version
Dataset Name and Format
Dataset Format Name Dataset Format Version
Vertical Extents of a Dataset
Minimum Value
Maximum Value Unit of Measure Vertical Datum
Access and Use Constraints
Access Constraints Use Constraints Use Constraints Details Other Constraints Details
Temporal Extents of a Dataset
Start Date for Time Period Covered by Dataset End Date for Time Period Covered by Dataset
12
Table 3. UK AGMAP element and entity attribute guidelines index. Metadata Elements Metadata Entity Metadata Entity Red text = mandatory elements Element Group Element Subgroup Bold number in parentheses (14) = page number reference for entity and element. Headings (Level 1) Headings (Level 2)
(To reach page: Ctrl and click page number)
G1 CITATION (15)
G2 IDENTIFICATION INFORMATION (WHAT) (23)
G.2.1 Spatial Reference System of the Dataset ( 34) G3 DATA QUALITY INFORMATION (37)
1) Dataset Title (15) 2) Alternative Dataset Title (16) 3) Creator (17) 4) Identifier (18) 5) Edition (19) 6) Dataset Date Code (20) 7) Dataset Event Date (21) 8) Dataset Update Frequency (22) 9) Dataset Language (23) 10) Dataset Topic (25) 11) Controlled Vocabulary (26) 12) Controlled Keywords (27) 13) Other Keywords (28) 14) Abstract (28) 15) Spatial Representation Type (29) 16) Presentation Type (30) 17) Sample (32) 18) Further Information (33) 19) Related Datasets (34) 20) Spatial Reference System (35)
21) Data Hierarchical Level (38) G3.1 Dataset Process Steps (41) 22) Status of the Data Creation Process (41) 23) Start Date of Data Capture Period (43) 24) End Date of Data Capture Period (44) 25) Dataset Lineage (45) 26) Description of Dataset Process Steps (45) 27) Logical Consistency (47) 28) Completeness (47) 29) Positional Accuracy (48) 30) Attribute Accuracy (49) 31) Source Scale Denominator (51) 32) Ground Scale Distance (52) 33) Imagery or Grid x-Dimension Name (52) 34) Imagery or Raster Cell/Pixel Size (x- Value) (53) 35) Imagery or Grid y-Dimension Name (54) 36) Imagery or Raster Cell/Pixel Size (y- Value) (55) 37) Smallest Administrative Unit (56) 38) Spatial Reference System used for the Bounding Rectangle/Bounding Polygon (59) 39) W est Bounding Co-ordinate (60) 40) East Bounding Co-ordinate (61) 41) North Bounding Co-ordinate (62) 42) South Bounding Co-ordinate (62) 43) Co-ordinates of a Bounding Polygon (64)
G3.2 Data Quality Statements (46)
G3.3 Level of Spatial Detail (50)
G4 EXTENTS OF A DATASET (WHERE AND WHEN) (57)
G4.1 Extents of a Dataset Based on Co-ordinates of a Bounding Rectangle (59) G4.2 Extents of a Dataset Based on Co-ordinates of a Bounding Polygon (63) G4.3 Extents of a Dataset Based on Geographic Identifiers ( 64)
44) 45) 46) 47) 48)
Nations (65) Administrative Areas (66) Postcode Districts (67) Controlled Place Name Vocabulary (67) Controlled Place Name Keywords (68) 13
G4.4 Vertical Extents of a Dataset (69)
G4.5 Temporal Extents of a Dataset (73) G5 CUSTODIAN (76)
G6 DISTRIBUTOR (ACCESS) (83)
G6.1 Data Format Name and Version (93) G6.2 Access and Use Constraints (98)
G7 METADATA CREATOR (103)
49) 50) 51) 52) 53) 54) 55) 56) 57) 58) 59) 60) 61) 62) 63) 64) 65) 66) 67) 68) 69) 70) 71) 72) 73) 74) 75) 76) 77) 78) 79) 80) 81) 82) 83) 84) 85) 86) 87) 88) 89) 90) 91) 92) 93) 94) 95) 96) 97)
Minimum Value (70) Maximum Value (71) Unit of Measure (71) Vertical Datum (72) Start Date for Time Period Covered by Dataset (74) End Date for Time Period Covered by Dataset (75) Name of Custodian (76) Postal Street Address of Custodian (78) Postal City of Custodian (78) Postal County of Custodian (79) Postal Code of Custodian (79) Postal Country of Custodian (80) Telephone Number of Custodian (81) Facsimile Number of Custodian (81) Email Address of Custodian (82) W eb Address of Custodian (82) Name of Distributor (84) Distributor Contact Title (85) Postal Street Address of Distributor (86) Postal City of Custodian (86) Postal Code of Distributor (87) Postal Country of Distributor (87) Telephone Number of Distributor (88) Facsimile Number of Distributor (89) Email Address of Distributor (89) W eb Address of Distributor (90) Supply Media (90) On-line Linkage (92) Dataset File Size (92) Dataset Format Name (94) Dataset Format Version (98) Access Constraints (99) Use Constraints (100) Use Constraints Details (102) Other Constraint Details (102) Name of Metadata Creator (104) Postal Street Address of Metadata Creator (105) Postal City Address of Distributor (106) Postal Code of Metadata Creator (106) Postal Country of Metadata Creator (107) Telephone Number of Metadata Creator (108) Facsimile Number of Metadata Creator(108) Email Address of Metadata Creator (109) W eb Address of Metadata Creator (109) Metadata Record Identifier (110) Parent Metadata Record Identifier (111) Metadata Last Update (113) Metadata Standard Name (113) Metadata Standard Version (114)
14
2.0 UK AGMAP element and entity attributes
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
CITATION
Not Applicable G1 (Element Group 1)
Return to index page
Dataset reference information. Not Applicable (M) Mandatory. This entity contains elements that require information. (1) Once. Dataset information may be recorded only once at the CITATION entity level. This rule applies only to the element group as a whole and not each element. Each element has a separate condition or rule for the number of occurrences permitted. Metadata Entity for Element Group 1 Not Applicable The following eight terms comprise the group of elements listed under the CITATION metadata entity: 1) Dataset Title 2) Alternative Dataset Title 3) Creator 4) Identifier 5) Edition 6) Dataset Date Code 7) Dataset Event Date 8) Dataset Update Frequency
Maximum Occurrence:
Data Type: Domain: Comments:
Examples:
Not Applicable
Entity Name:
Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum
CITATION DATASET TITLE
1 Not Applicable The name by which the dataset is known.
Return to index page
(M) Mandatory. The Dataset Title element must have information entered in its field. (1) Once. No more than one Dataset Title entry permitted for this element.
15
Occurrence: Data Type: Domain: Comments: Character String Free Text The Dataset 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 (e.g.: Gaelic, Welsh), and those with acronyms, these should be listed under the Alternative Dataset 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: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments: 1) Link to Dataset Title examples [Ctrl and click here] p 129
CITATION ALTERNATIVE DATASET TITLE
2 Not Applicable
Return to index page
Short name, other name, acronym or alternative language title for dataset. (O) Optional. The Alternative Dataset Title element does not require information to be entered in its field, but it is recommended if applicable. (N) Unlimited number of Alternative Dataset Title entries permitted for this element.
Character String Free Text 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:
1) Link to Alternative Dataset Title examples [Ctrl and click here] p 130
16
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
CITATION CREATOR
3 Not Applicable
Return to index page
Organisation or person that developed the dataset and has primary responsibility for the intellectual content of the dataset. (M) Mandatory. The Creator element must have information entered in its field. (N) Unlimited number of Creator entries permitted for this element.
Character String Free Text 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 either. The entry format should list title first, without full-stops, then given name, middle name or initials, full-stop recommended with initials, and surname. 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 ensure 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 Jane Doe 2) Dr Jane Doe 3) Ms Jane Doe 4) Miss Jane Doe 5) Mrs Jane Doe 6) Mary Jane Doe 7) Jane M Doe 8) Jane Doe 9) Mr John Doe
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
17
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
CITATION IDENTIFIER
4 Not Applicable A unique string or number used to identify the dataset.
Return to index page
(O) Optional. The Identifier element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Identifier entry permitted for this element. Character String Free Text 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, it can be cross-referenced on a spreadsheet as 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 for referencing and identifying 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
18
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
CITATION EDITION
5 Not Applicable The number of the edition of the dataset.
Return to index page
(M) Mandatory. The Edition element must have information entered in its field. (1) Once. No more than one Edition entry permitted for this element.
Character String Free Text 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. There will be instances where edits or updates might be applied to an earlier edition of a dataset. Please include a reference to the final edition to reveal the number of editions for a dataset. An example would be to write it as follows: [1.6 of 2.0], where 1.6 refers to the dataset being documented in the metadata record 2.0 pertains to the most current edition of this dataset’s lineage. 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, the 1.0 edition of a dataset may cost less than the 2.0 edition. 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 an 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 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. A version scheme is recommended.
Examples:
1) 1.0 2) 1 3) First 4) 1.5 of 2.0
19
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain:
CITATION DATASET DATE CODE
6 Not Applicable Identification of when a given dataset event occurred.
Return to index page
(M) Mandatory. The Dataset Date Code element must have information entered in its field. (1) Once. No more than one selection from the Dataset Date Code element’s enumerated list permitted for this element. Enumerated List ISO 19115 B.5.2 (CI_DateTypeCode)
1) creation 001 Date identifies when the resource was brought into existence. (Refers to event when dataset was created). 2) publication 002
Date identifies when the resource was issued. (Refers to event when created dataset was published for released for users, both internal and external). 3) revision 003 Date identifies when the resource was examined or re-examined and improved or amended. (Refers to event when created dataset was revised as part of updates and edits). *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. (Refers to event when created dataset was permanently deleted). 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
20
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 a dataset is deleted, especially one derived from licensed data with a condition that would require the data developer to delete the derived 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 could 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 an option. Examples: 1) creation 2) publication Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
CITATION DATASET EVENT DATE
7 Not Applicable Event date for the dataset.
Return to index page
(M) Mandatory. The Dataset Event Date element must have information entered in its field. (1) Once. No more than one Dataset Event Date entry permitted for this element. Date YYYY-MM-DD 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 (YearMonth-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 2) 2001-01 3) 2001 4) 2004-10-04
[ Entire date known, including year, month and day ] [ Year and month of date known, but not day ] [ Year known, but not month and day ] [ The value entered for a dataset published on 24 October 2004 ]
21
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain:
CITATION DATASET UPDATE FREQUENCY
8 Not Applicable
Return to index page
The frequency with which revisions and updates are made to the dataset after its initial completion. (M) Mandatory. The Dataset Update Frequency element must have information entered in its field. (1) Once. No more than one selection from the Dataset Update Frequency element’s enumerated list permitted for this element. Enumerated List 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.
22
Comments:
Select the term from the list that best defines the time frequency established for dataset revisions and updates. The numeric code does not need to be selected or entered. 1) weekly 2) biannually 3) notPlanned
Examples:
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence:
IDENTIFICATION INFORMATION (WHAT)
Not Applicable G2 (Element Group 2)
Return to index page
Basic information about the dataset. Not Applicable (M) Mandatory. This entity contains elements that require information. (1) Once. Dataset information may be recorded only once at the IDENTIFICATION INFORMATION entity level. This rule applies only to the element group as a whole and not each element. Each element has a separate condition or rule for the number of occurrences permitted. Metadata Entity for Element Group 2 Not Applicable Under the IDENTIFICATION INFORMATION metadata entity group there is one subgroup metadata entity: (G2.1) SPATIAL REFERENCE SYSTEM OF THE DATASET. The following 12 terms comprise the group of elements listed under the IDENTIFICATION INFORMATION metadata entity and one subgroup entity: 9) Dataset Language 10) Dataset Topic 11) Controlled Vocabulary 12) Controlled Keywords 13) Other Keywords 14) Abstract 15) Spatial Representation Type 16) Presentation Type 17) Sample 18) Further Information 19) Related Datasets
23
Data Type: Domain: Comments:
(G2.1) SPATIAL REFERENCE SYSTEM OF THE DATASET: 20) Spatial Reference System. Examples: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Not Applicable
IDENTIFICATION INFORMATION (WHAT) DATASET LANGUAGE
9 Not Applicable The language(s) used within the dataset.
Return to index page
(M) Mandatory. The Language element must have information entered in its field. (N) Unlimited number of selections from the Language element’s enumerated list permitted for this element. Enumerated List 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 the metadata record is generated manually (without the GeoDoc metadata editor tool) for internal use, then the full language name can be entered as well for clarification. The three letter GLE abbreviation for Irish Gallic isn’t as apparent as ENG for English. If more than one language is selected, then please provide a brief explanation in the Description element’s field. An example might be a bilingual study of place name distribution patterns in Wales which would include the Welsh name and its English equivalent.
Examples:
1) ENG 2) GLE 3) ENG/English [ Example for internal use ]
24
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain:
IDENTIFICATION INFORMATION (WHAT) DATASET TOPIC
10 Not Applicable Main theme(s) of the dataset.
Return to index page
(M) Mandatory. The Dataset Topic element must have information entered in its field. (N) Unlimited number of selections from the Topic element’s enumerated list permitted for this element. Enumerated List 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 Base maps. 11) intelligenceMilitary 011 Military bases, structures, activities. 12) inlandWaters 012 Inland water features, drainage systems and their characteristics.
25
010
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 Dataset Topic element provides a thematic classification for geographic data. It groups datasets under more general terms for the purpose of topical keyword searches. The Dataset 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 or enter the topic or topics that best represent the dataset’s theme. The link below provides access to more detailed definitions for each topic. Link to definitions for Dataset Topic List [Ctrl and click here] p 131 Examples: 1) farming 2) planningCadastre 3) utilitiesCommunication Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence:
IDENTIFICATION INFORMATION (WHAT) CONTROLLED VOCABULARY
11 Not Applicable
Return to index page
Name of the controlled vocabulary used as a source for the controlled keywords. (M) Mandatory. The Controlled Vocabulary element must have information entered in its field. (1) Once. No more than one Controlled Vocabulary entry permitted for this element.
26
Data Type: Domain: Comments:
Character String Free Text 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: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
1) UNESCO
IDENTIFICATION INFORMATION (WHAT) CONTROLLED KEYWORDS
12 Not Applicable
Return to index page
Keywords taken from a controlled vocabulary summarising the subject of the dataset. (M) Mandatory. The Controlled Keywords element must have information entered in its field. (N) Unlimited number of selections from the Controlled Keywords element’s enumerated list permitted for this element. Enumerated List See 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 GeoDoc 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 coordinator will take responsibility for entering the keywords to the metadata record and returning it to the metadata creator for approval.
Examples:
1) Link to Controlled Keywords examples [Ctrl and click here] p 133
27
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
IDENTIFICATION INFORMATION (WHAT) OTHER KEYWORDS
13 Not Applicable Other words or phrases summarising the subject of the dataset.
Return to index page
(O) Optional. The Other Keywords element does not require information to be entered in its field, but it is recommended if applicable. (N) Unlimited number of Other Keywords entries permitted for this element.
Character String Free Text 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. 1) Link to Other Keyword examples [Ctrl and click here] p 135
Examples: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
IDENTIFICATION INFORMATION (WHAT) Abstract
14 Not Applicable
Return to index page
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. (M) Mandatory. The Abstract element must have information entered in its field. (1) Once. No more than one Abstract entry permitted for this element.
Character String Free Text 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.
28
Examples: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain:
1) Link to Abstract examples [Ctrl and click here] p 137
IDENTIFICATION INFORMATION (WHAT) SPATIAL REPRESENTATION TYPE
15 Not Applicable Method used to spatially represent geographic information.
Return to index page
(O) Optional. Spatial Representation Type element does not require information to be entered in its field, but it is recommended if applicable. (N) Unlimited number of selections from the Spatial Representation Type enumerated list permitted for this element. Enumerated List
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.
29
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. Examples: 1) Grid 2) textTable Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain:
IDENTIFICATION INFORMATION (WHAT) PRESENTATION TYPE
16 Not Applicable Form in which the dataset is available.
Return to index page
(O) Optional. Presentation Type element does not require information to be entered in its field, but it is recommended if applicable. (N) Unlimited number of selections from the Presentation Type element’s enumerated list permitted for this element. Enumerated List
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.
30
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
31
databases and spreadsheets. A video represents a medium which provides moving images of real objects or computer generated animation scenes. Videos could include flyovers of threedimensional models or monitoring stations that can be geo-referenced. Examples: 1) imageDigital 2) tableHardCopy Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
IDENTIFICATION INFORMATION (WHAT) SAMPLE
17 Not Applicable
Return to index page
The name of the file that contains the graphic or data that provides a sample illustration of the dataset. (O) Optional. Sample element does not require information to be entered in its field, but it is recommended if applicable. (N) Multiple number of Sample entries permitted for this element. Image or Free Text CGM/GIF/JPEG/TIFF or Text 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 a watermark or type ‘COPYRIGHT’ 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 procedure should be practiced 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). This is 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
32
Maximum Occurrence: Data Type: Domain: Comments:
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) samplemap.cgm 2) samplemap.jpg 3) samplemap.jpeg 4) samplemap.tiff 5) samplemap.tif 6) sampledata.txt Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
IDENTIFICATION INFORMATION (WHAT) FURTHER INFORMATION
18 Not Applicable Source of further information about the dataset.
Return to index page
(O) Optional. The Further Information element does not require information to be entered in its field, but it is recommended if applicable. (N) Unlimited number of Further Information entries permitted for this element.
Character String Free Text This element can be used to record information not captured elsewhere in the UK AGMAP profile or to reveal important information that may be inconspicuously placed elsewhere in the metadata record. It can also be used to point where data 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 usually http:// for web addresses. This element can also be used to enter the filename of the spatial dataset that the metadata record represents. This is especially useful for local data management in the instance that the Identifier element of UK AGMAP is not used.
33
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 4) mydataset.dxf
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
IDENTIFICATION INFORMATION (WHAT) RELATED DATASETS
19 Not Applicable
Return to index page
Information about other, related datasets of a similar theme or derived from a common source, which may be of interest to the user. (O) Optional. The Related Datasets element does not require information to be entered in its field, but it is recommended if applicable. (N) Unlimited number of Related Dataset entries permitted for this element. Character String Free Text 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: Entity Name: Subgroup Entity Name: Element Name: Identifier:
1) Link to Related Dataset examples [Ctrl and click here] p
IDENTIFICATION INFORMATION (WHAT) SPATIAL REFERENCE SYSTEM OF THE DATASET
Not Applicable G2.1 (Group 2.subgroup 1)
Return to index page
34
Definition of Entity:
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). Not Applicable (M) Mandatory. This entity contains elements that require information. (1) Once. Dataset information may be recorded only once at the Spatial Reference System of the Dataset subgroup entity level. This rule applies only to the entity level’s element subgroup which comprises one element. Metadata Entity for Element Subgroup 1 of Identification Information Group 2 Not Applicable The following term is an element listed under the SPATIAL REFERENCE SYSTEM OF THE DATASET metadata subgroup entity: 20) Spatial Reference System *The list of values available for Spatial Reference System is based on UK GEMINI, the ISO 19115 compliant metadata standard for the United Kingdom. The document is available for download at this URL: http://www.govtalk.gov.uk/schemasstandards/metadata_document.asp?docnum=903 or if this link is broken, then through the GovTalk website: http://www.govtalk.gov.uk/
Definition of Element: Obligation: Maximum Occurrence:
Data Type: Domain: Comments:
Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type:
Not Applicable
IDENTIFICATION INFORMATION (WHAT)
Return to index page
SPATIAL REFERENCE SYSTEM OF THE DATASET SPATIAL REFERENCE SYSTEM
20 Not Applicable 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). (M) Mandatory. The Spatial Reference System element must have information entered in its field. (1) Once. No more than one selection from the Spatial Reference System element’s enumerated list permitted for this element. Enumerated List
35
Domain:
UK GEMINI Spatial Reference System List 1) National Grid of Great Britain 2) Irish Grid 3) Irish Transverse Mercator 4) WGS84 5) Postcode 6) Ward 7) Local Authority (County/Unitary/District/Borough) 8) Region 9) Country 10) Other area 11) Parish 12) Health Authority Area 13) Electoral Constituency 14) Travel to Work Area 15) 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 Ordnance Survey administers the Irish Grid and is also based on a Transverse Mercator projection with co-ordinates expressed in international metres. The Irish Grid System extends across 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.
36
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: 1) WGS84 2) National Grid of Great Britain 3) Travel To Work Area
Intentionally left blank for document format purposes
Entity Name: Element Name: Identifier: Definition of Entity:
DATA QUALITY INFORMATION
Not Applicable G3 (Element Group 3)
Return to index page
A general assessment of the quality of a dataset for determining its fitness for use. Quality is stated in terms of dataset process steps, capture periods, quality summary statements and spatial granularity. Not Applicable (O) Optional. This entity does not contain elements which require information. (1) Once. Dataset information may be recorded only once at the DATA QUALITY INFORMATION entity level. This rule applies only to the element group as a whole and not each element. Each element has a separate condition or rule for the number of occurrences permitted. Metadata Entity for Element Group 3 Not Applicable
37
Definition of Element: Obligation: Maximum Occurrence:
Data Type: Domain:
Comments:
Under the DATA QUALITY INFORMATION metadata entity group there are the following four subgroup metadata entities: (G3.1) DATA PROCESS STEPS; (G3.2) DATA QUALITY STATEMENTS; (G3.3) LEVEL OF SPATIAL DETAIL. The following 17 terms comprise the group of elements listed under the DATA QUALITY INFORMATION metadata entity and four subgroup entities: 21) Data Hierarchical Level. (G3.1) DATA PROCESS STEPS: 22) Status of Data Creation Process 23) Start Date of Data Capture Period 24) End Date of Data Capture Period 25) Dataset Lineage 26) Description of Dataset Process Steps (G3.2) DATA QUALITY STATEMENTS: 27) Logical Consistency 28) Completeness 29) Positional Accuracy 30) Attribute Accuracy (G3.3) LEVEL OF SPATIAL DETAIL: 31) Source Scale Denominator 32) Ground Scale Distance 33) Imagery or Grid x-dimension 34) Imagery or Grid Raster Cell/Pixel Size (x-Value) 35) Imagery or Grid y-dimension 36) Imagery or Grid Raster Cell/Pixel Size (y-Value) 37) Smallest Administrative Unit
Examples: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element:
Not Applicable
DATA QUALITY INFORMATION DATA HIERARCHICAL LEVEL
21 Not Applicable
Return to index page
Hierarchical level of the data stated in the process steps and quality statement.
38
Obligation:
(O) Optional. The default is set to ‘Dataset’. If information is entered in one of the element fields under Data Process Step, Quality Statement or Level of Spatial Detail, and this information pertains to a different data hierarchical level, then the corresponding enumerated list value must be selected. (1) Once. No more than one selection from the Data Hierarchical Level element’s enumerated list permitted for this element. Enumerated List ISO 19115 B.5.25 (MD_ScopeCode)
Maximum Occurrence: Data Type: Domain:
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.
39
Comments:
The default value is set to ‘Dataset’ on the GeoDoc metadata editor tool. If information pertains to a different data hierarchical level, then that value must be selected from the list, and information provided for Data Process Step, Quality Statement or Level of Spatial Detail elements must correspond with that value. 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. An attribute type is information that applies to the characteristic of a feature. Collection hardware is information that applies to the collection hardware class. A collection session applies to information of a data collection session. A dataset is a collection of associated data with a common geographical theme. Series is information that applies to a series (e.g.: time series data). A non-geographic dataset is information that applies to non-geographic data. A dimension group represents an entity definition of codes comprising common, aligned, linear and rotated, radical and diameter, angular and ordinate groups found in the ENTITIES section of a DXF file (Computer Aided Design (CAD) geometry). 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. A feature type describes a type of feature (e.g.: point, line or polygon). Property type information applies to a property type. Field session information can pertain to specific time frame or frames when data are collected in the field. Software information applies to a computer program or routine. Service information applies to a capability which a service provider entity makes available to a service user entity through a set of interfaces that defines a behaviour, such as a use case. Model information applies to a copy or imitation of an existing or hypothetical object. 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. Tile information applies to a spatial subset of geographic data or sub-area of a digital map.
Examples:
1) dataset 2) nonGeographicDataset
40
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity:
DATA QUALITY INFORMATION DATA PROCESS STEPS
Not Applicable G3.1 (Element Group 3.subgroup 1)
Return to index page
Overview of the dataset creation process steps including the status and time periods for data capture, and a dataset’s lineage and process steps. Not Applicable (O) Optional. This entity contains elements that do not require information, but it is recommended if applicable. (1) Once. Data information may be recorded only once at the Data Process Steps subgroup entity level. This rule applies only to the entity level’s element subgroup as a whole and not each element. Each element has a separate condition or rule for the number of occurrences permitted, though in this subgroup, there isn’t an element that requires more than one entry. Metadata Entity for Element Subgroup 1 of Data Quality Information Group 3 Not Applicable The following five terms are elements listed under the DATA PROCESS STEPS metadata subgroup entity: 22) Status of the Data Creation Process 23) Start Date of the Data Capture Period 24) End Date of the Data Capture Period 25) Dataset Lineage 26) Description of Dataset Process Steps
Definition of Element: Obligation: Maximum Occurrence:
Data Type: Domain: Comments:
Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element:
Not Applicable
DATA QUALITY INFORMATION DATA PROCESS STEPS STATUS OF DATA CREATION PROCESS
22 Not Applicable Declaration on the status of the data creation process.
Return to index page
41
Obligation: Maximum Occurrence: Data Type: Domain:
(O) Optional. The Status of the Data Creation Process element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one selection from the Status of the Data Creation Process element’s enumerated list permitted for this element. Enumerated List 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 element’s lack of an enumerated list 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:
1) completed 2) underDevelopment
42
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
DATA QUALITY INFORMATION DATA PROCESS STEPS START DATE OF DATA CAPTURE PERIOD
23 Not Applicable Date on which data for dataset were first collected.
Return to index page
(C) Conditional. If a Status of Data Creation Process value is selected, then a start date should be entered. (1) Once. No more than one Start Date of Data Capture Period entry permitted for this element. Date YYYY-MM-DD 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 (YearMonth-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 2) 2001-01 3) 2001 4) -0055 5) 0450 6) 2004-10-04
[ Entire date known, including year, month and day ] [ Year and month of date known, but not day ] [ Year known, but not month and day ] [ The year 55 BC ] [ The year AD 450 ] [ The value entered for a dataset started on 24 October 2004 ]
43
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
DATA QUALITY INFORMATION DATA PROCESS STEPS END DATE OF DATA CAPTURE PERIOD
24 Not Applicable Date on which data for dataset were last collected.
Return to index page
(C) Conditional. If a Status of Data Creation Process value is selected, then an end date should be entered. (1) Once. No more than one End Date of Data Capture Period entry permitted for this element. Date YYYY-MM-DD 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 (YearMonth-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.
Maximum Occurrence: Data Type: Domain: Comments:
Examples:
1) 2001-01-31 2) 2001-01 3) 2001 4) -0055 5) 0450 6) 2004-10-04
[ Entire date known, including year, month and day ] [ Year and month of date known, but not day ] [ Year known, but not month and day ] [ The year 55 BC ] [ The year AD 450 ] [ The value entered for a dataset completed on 24 October 2004 ]
44
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
DATA QUALITY INFORMATION DATA PROCESS STEPS DATASET LINEAGE
25 Not Applicable
Return to index page
Information about the source data used in the construction of the dataset. (O) Optional. The Dataset Lineage element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Dataset Lineage entry permitted for this element.
Character String Free Text 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. 1) Link to Dataset Lineage examples [Ctrl and click here] p 143
Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain:
DATA QUALITY INFORMATION DATA PROCESS STEPS DESCRIPTION OF DATASET PROCESS STEPS
26 Not Applicable A general description of how the dataset was generated or derived.
Return to index page
(O) Optional. The Dataset Lineage element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Dataset Lineage entry permitted for this element.
Character String Free Text
45
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 other UK 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 inadvertently 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.
Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier:
1) Link to Description of Dataset Process Steps examples [Ctrl and click here] p 144
DATA QUALITY INFORMATION DATA QUALITY STATEMENT
Not Applicable G3.2 (Element Group 3.subgroup 2)
Return to index page
Definition of Entity: Definition of Element: Obligation:
An assessment of data quality based on logical consistency, completeness, positional accuracy and attribute accuracy. Not Applicable (O) Optional. This entity contains elements that do not require information, but it is recommended if applicable. (1) Once. Data information may be recorded only once at the DATA QUALITY STATEMENT subgroup entity level. This rule applies only to the entity level’s element subgroup as a whole and not each element. Each element has a separate condition or rule for the number of occurrences permitted, though in this subgroup, there isn’t an element that requires more than one entry. Metadata Entity for Element Subgroup 2 of Data Quality Information Group 3 Not Applicable The following terms are elements listed under the DATA QUALITY STATEMENT metadata entity: 27) Logical Consistency 28) Completeness 29) Positional Accuracy 30) Attribute Accuracy
Maximum Occurrence:
Data Type: Domain: Comments:
Examples:
Not Applicable
46
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
DATA QUALITY INFORMATION DATA QUALITY STATEMENT LOGICAL CONSISTENCY
27 Not Applicable
Return to index page
An indication of topological problems such as overshoots, undershoots, unwanted intersections, unclosed polygons, missing or duplicate labels, etc. (O) Optional. The Logical Consistency element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Logical Consistency entry permitted for this element.
Maximum Occurrence: Data Type: Domain: Comments:
Character String Free Text 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. 1) Link to Logical Consistency examples [Ctrl and click here] p 146
Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
DATA QUALITY INFORMATION DATA QUALITY STATEMENT COMPLETENESS
28 Not Applicable
Return to index page
Information about omissions, commissions, selection criteria, generalisation definitions used to derive the dataset that may affect the completeness of the dataset’s content. (O) Optional. The Completeness element does not require information to be entered in its field, but it is recommended if applicable.
47
Maximum Occurrence: Data Type: Domain: Comments:
(1) Once. No more than one Completeness entry permitted for this element. Character String Free Text 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.
Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
1) Link to Completeness examples [Ctrl and click here] p 147
DATA QUALITY INFORMATION DATA QUALITY STATEMENT POSITIONAL ACCURACY
29 Not Applicable
Return to index page
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. (O) Optional. The Positional Accuracy element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Positional Accuracy entry permitted for this element.
Maximum Occurrence: Data Type: Domain:
Character String Free Text
48
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, other errors 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.
Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
1) Link to Positional Accuracy examples [Ctrl and click here] p 148
DATA QUALITY INFORMATION DATA QUALITY STATEMENT ATTRIBUTE ACCURACY
30 Not Applicable
Return to index page
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. (O) Optional. The Attribute Accuracy element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Attribute Accuracy entry permitted for this element. Character String Free Text
Maximum Occurrence: Data Type: Domain:
49
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.
Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity:
1) Link to Attribute Accuracy examples [Ctrl and click here] p 149
DATA QUALITY INFORMATION LEVEL OF SPATIAL DETAIL
Not Applicable G3.3 (Element Group 3.subgroup 3)
Return to index page
Description of the spatial level of detail for the source data measured in terms of absolute size, relative size, resolution, granularity, or the smallest representative unit associated with disaggregated, statistical data. Not Applicable (O) Optional. This entity contains elements that do not require information, but it is recommended if applicable. (1) Once. Dataset information may be recorded only once at the LEVEL OF SPATIAL DETAIL entity level. This rule applies only to the element group as a whole and not each element. Each element has a separate condition or rule for the number of occurrences permitted, though in this subgroup, there isn’t an element that requires more than one entry. Metadata Entity for Element Subgroup 3 of Element Group 3 Not Applicable The following seven terms form the group of elements listed under the LEVEL OF SPATIAL DETAIL metadata entity: 31) Source Scale Denominator 32) Ground Scale Distance 33) Imagery or Grid x-dimension 34) Imagery or Grid Raster Cell/Pixel Size (x-Value) 35) Imagery or Grid y-dimension 36) Imagery or Grid Raster Cell/Pixel Size (y-Value)
50
Definition of Element: Obligation: Maximum Occurrence:
Data Type: Domain: Comments:
37) Smallest Administrative Unit Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Not Applicable
DATA QUALITY INFORMATION LEVEL OF SPATIAL DETAIL SOURCE SCALE DENOMINATOR
31 Not Applicable
Return to index page
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). (O) Optional. The Source Scale Denominator element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Source Scale Denominator entry permitted for this element. Character String Free Text 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 ensure 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.
Obligation:
Maximum Occurrence: Data Type: Domain: Comments:
Examples:
1) Link to Source Scale Denominator examples [Ctrl and click here] p 150
51
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
DATA QUALITY INFORMATION LEVEL OF SPATIAL DETAIL GROUND SCALE DISTANCE
32 Not Applicable The ground sample distance.
Return to index page
(O) Optional. The Ground Scale Distance element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Ground Scale Distance entry permitted for this element. Real Number Real Number 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. See: Source Scale Denominator examples [Ctrl and click here] p 150
Maximum Occurrence: Data Type: Domain: Comments:
Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type:
DATA QUALITY INFORMATION LEVEL OF SPATIAL DETAIL IMAGERY OR GRID x-DIMENSION NAME
33 Not Applicable Name of the x-axis. (Default = Column)
Return to index page
(O) Optional. The Imagery or Grid x-Dimension Name element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Imagery or Grid x-Dimension Name entry permitted for this element. Enumerated List
52
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 for the GeoDoc metadata editor tool 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 many spatial datasets are raster-based, and in these instances, 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 form raster grids. The other dimension name values can also be used if pertinent to a dataset. The GeoDoc metadata editor tool also allows for any combination of entries from the list, but default is set to support row and column. Examples: 1) column
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element:
DATA QUALITY INFORMATION LEVEL OF SPATIAL DETAIL
Return to index page
IMAGERY OR GRID RASTER CELL/PIXEL SIZE (x-VALUE)
34 Not Applicable The column width of a grid cell expressed in distance units of measure (metres).
53
Obligation:
(C) Conditional. 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. (1) Once. No more than one Grid Raster Cell/Pixel x-Value entry permitted for this element. Real Number Real Number 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 and Digital Terrain Models (DTM). 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. Values must be entered in metres, hence 70 centimetres would be entered as 0.70 for a value.
Maximum Occurrence: Data Type: Domain: Comments:
Examples:
1) 30 2) 0.70 3) 2.4 4) Link to Grid Raster Cell/Pixel Size x-value examples [Ctrl and click here] p 153
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type:
DATA QUALITY INFORMATION LEVEL OF SPATIAL DETAIL IMAGERY OR GRID y-DIMENSION NAME
35 Not Applicable Name of the y-axis. (Default = Row)
Return to index page
(O) Optional. The Imagery or Grid y-Dimension Name element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Imagery or Grid y-Dimension Name entry permitted for this element. Enumerated List
54
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 for the GeoDoc metadata editor tool 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 many spatial datasets are raster-based, and in these instances, 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 form raster grids. The other dimension name values can also be used if pertinent to a dataset. The GeoDoc metadata editor tool also allows for any combination of entries from the list, but default is set to support row and column. Examples: 1) row
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element:
DATA QUALITY INFORMATION LEVEL OF SPATIAL DETAIL
Return to index page
IMAGERY OR GRID RASTER CELL/PIXEL SIZE (y-VALUE)
36 Not Applicable The row height of a grid cell expressed in distance units of measure (metres).
55
Obligation: Maximum Occurrence: Data Type: Domain: Comments:
(C) Conditional. 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. (1) Once. No more than one Grid Raster Cell/Pixel y-Value entry permitted for this element. Real Number Real Number This value is associated with raster datasets and represents the y-value length of the raster/grid 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 and Digital Terrain Models (DTM). 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. Values must be entered in metres, hence 70 centimetres would be entered as 0.70 for a value.
Examples:
1) 30 2) 0.70 3) 2.4 4) Link to Grid Raster Cell/Pixel y-value examples [Ctrl and click here] p 153
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence:
DATA QUALITY INFORMATION LEVEL OF SPATIAL DETAIL SMALLEST ADMINISTRATIVE UNIT
37 Not Applicable
Return to index page
The smallest representative unit associated with disaggregated statistical data. (O) Optional. The Smallest Administrative Unit element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Smallest Administrative Unit entry permitted for this element.
56
Data Type: Domain: Comments:
Character String Free Text 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.
Examples:
1) Link to Smallest Administrative Unit examples [Ctrl and click here] p 157
Entity Name:
EXTENTS OF A DATASET (WHERE AND WHEN)
Return to index page
Element Name: Identifier: Definition of Entity:
Not Applicable G4 (Element Group 4)
The geographic coverage of the dataset expressed in terms of geographic identifiers (e.g. nations, administrative areas, or postcode districts) or geographic co-ordinates. Not Applicable (M) Mandatory. This entity contains elements that require information input. (1) Once. Dataset information may be recorded only once at the first order entity level of the EXTENTS OF DATASET entity. This rule does not apply to metadata entity subgroups and individual elements. Each entity subgroup has a separate condition or rule for the number of occurrences permitted. Each element also has a separate condition or rule for the number of occurrences permitted. Metadata Entity for Element Group 5 Not Applicable
Definition of Element: Obligation: Maximum Occurrence:
Data Type: Domain:
57
Comments:
Under the EXTENTS OF DATASET metadata entity group there are the following five subgroup metadata entities: G4.1) EXTENTS OF A DATASET BASED ON CO-ORDINATES OF A BOUNDING RECTANGLE G4.2) EXTENTS OF A DATASET BASED ON CO-ORDINATES OF A BOUNDING POLYGON G4.3) EXTENTS OF A DATASET BASED ON GEOGRAPHIC IDENTIFIERS G4.4) VERTICAL EXTENTS OF A DATASET G4.5) TEMPORAL EXTENTS OF A DATASET The following 17 terms comprise the group of elements listed under the EXTENTS OF A DATASET metadata entity and five subgroup entities: 38) Spatial Reference System used for the Bounding Rectangle/Polygon. G4.1) EXTENTS OF A DATASET BASED ON CO-ORDINATES OF A BOUNDING RECTANGLE: 39) West Bounding Co-ordinate 40) East Bounding Co-ordinate 41) North Bounding Co-ordinate 42) South Bounding Co-ordinate G4.2) EXTENTS OF A DATASET BASED ON CO-ORDINATES OF A BOUNDING POLYGON: 43) Spatial Referencing Using the Co-ordinates of a Bounding Polygon. G4.3) EXTENTS OF A DATASET BASED ON GEOGRAPHIC IDENTIFIERS: 44) Nations 45) Administrative Areas 46) Postcode Districts 47) Controlled Place Name Vocabulary 48) Controlled Place Name Keywords G4.4) VERTICAL EXTENTS OF A DATASET: 49) Minimum Value 50) Maximum Value 51) Unit of Measure 52) Vertical Datum G4.5) TEMPORAL EXTENTS OF A DATASET: 53) Start Date for Time Period Covered by Dataset 54) End Date for Time Period Covered by Dataset
Examples:
Not Applicable
58
Entity Name: Element Name:
EXTENTS OF A DATASET (WHERE AND WHEN)
Return to index page
SPATIAL REFERENCE SYSTEM USED FOR THE BOUNDING RECTANGLE / BOUNDING POLYGON
38 Not Applicable Name of the spatial reference system used for the geographic co-ordinates of the study area’s extent. (M) Mandatory. The Spatial Reference System Used for the Bounding Rectangle / Bounding Polygon element must have information entered in its field. (1) Once. No more than one selection from the Spatial Reference System Used for the Bounding Rectangle / Bounding Polygon element’s enumerated list permitted for this element. Enumerated List UK AGMAP Element 1) British National Grid 2) Irish National Grid 3) Latitude and Longitude
Identifier: Definition of Entity: Definition of Element: Obligation:
Maximum Occurrence: Data Type: Domain:
Comments:
This element states which spatial referencing system is used to provide the coordinates 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. None
Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity:
EXTENTS OF A DATASET (WHERE AND WHEN)
Return to index page
EXTENTS OF A DATASET BASED ON THE CO-ORDINATES OF A BOUNDING RECTANGLE
Not Applicable G4.1 (Element Group 4.subgroup 1)
The geographic coverage of the dataset expressed in terms of geographic coordinates of a bounding rectangle. Not Applicable
59
Definition of Element:
Obligation: Maximum Occurrence:
(M) Mandatory. This entity contains elements that require information. (N) Dataset information may be recorded multiple times at the SPATIAL REFERENCING USING CO-ORDINATES OF A BOUNDING RECTANGLE entity level. This rule applies only to the entity level’s element subgroup as a whole and not each element. Each element has a separate condition or rule for the number of occurrences permitted. Metadata Entity for Element subgroup 1 of Element Group 4. Not Applicable The following four terms are elements listed under the EXTENTS OF A DATASET BASED ON THE CO_ORDINATES OF A BOUNDING RECTANGLE metadata subgroup entity: 39) West Bounding Co-ordinate 40) East Bounding Co-ordinate 41) North Bounding Co-ordinate 42) South Bounding Co-ordinate
Data Type: Domain: Comments:
Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
Not Applicable
EXTENTS OF A DATASET (WHERE AND WHEN)
Return to index page
EXTENTS OF A DATASET BASED ON THE CO-ORDINATES OF A BOUNDING RECTANGLE WEST BOUNDING CO-ORDINATE
39 Not Applicable Westernmost co-ordinate of a bounding rectangle. (M) Mandatory. The West Bounding Co-ordinate element must have information entered in its field. (1) Once. No more than one West Bounding Co-ordinate entry permitted for this element. Real Number Grid or Longitude Value 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
60
Maximum Occurrence: Data Type: Domain: Comments:
are expressed as positive numbers. It is recommended that the rectangle co-ordinates of a sensitive study area be generalised to ensure that the actual location is not revealed to the general public. Such study areas might include archaeological sites and endangered species habitats. Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments: 1) Link to Bounding Co-ordinate example [Ctrl and click here] p 159
EXTENTS OF A DATASET (WHERE AND WHEN)
Return to index page
EXTENTS OF A DATASET BASED ON THE CO-ORDINATES OF A BOUNDING RECTANGLE EAST BOUNDING CO-ORDINATE
40 Not Applicable Easternmost co-ordinate of a bounding rectangle. (M) Mandatory. The East Bounding Co-ordinate element must have information entered in its field. (1) Once. No more than one East Bounding Co-ordinate entry permitted for this element. Real Number Grid or Longitude Value 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 ensure that the actual location is not revealed to the general public. Such study areas might include archaeological sites and endangered species habitats.
Examples:
1) Link to Bounding Co-ordinate example [Ctrl and click] p 159
61
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
EXTENTS OF A DATASET (WHERE AND WHEN)
Return to index page
EXTENTS OF A DATASET BASED ON THE CO-ORDINATES OF A BOUNDING RECTANGLE NORTH BOUNDING CO-ORDINATE
41 Not Applicable Northernmost co-ordinate of a bounding rectangle. (M) Mandatory. The North Bounding Co-ordinate element must have information entered in its field. (1) Once. No more than one North Bounding Co-ordinate entry permitted for this element. Real Number Grid or Latitude Value 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 ensure that the actual location is not revealed to the general public. Such study areas might include archaeological sites and endangered species habitats.
Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element:
1) Link to Bounding Co-ordinate example [Ctrl and click] p 159
EXTENTS OF A DATASET (WHERE AND WHEN)
Return to index page
EXTENTS OF A DATASET BASED ON THE CO-ORDINATES OF A BOUNDING RECTANGLE SOUTH BOUNDING CO-ORDINATE
42 Not Applicable Southernmost co-ordinate of a bounding rectangle.
62
Obligation: Maximum Occurrence: Data Type: Domain: Comments:
(M) Mandatory. The South Bounding Co-ordinate element must have information entered in its field. (1) Once. No more than one South Bounding Co-ordinate entry permitted for this element. Real Number Grid or Latitude Value 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 ensure that the actual location is not revealed to the general public. Such study areas might include archaeological sites and endangered species habitats.
Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
1) Link to Bounding Co-ordinate example [Ctrl and click here] p 159
EXTENTS OF A DATASET (WHERE AND WHEN)
Return to index page
EXTENTS OF A DATASET BASED ON CO-ORDINATES OF A BOUNDING POLYGON
Not Applicable G4.2 (Element Group 4.subgroup 2)
The geographic coverage of the dataset expressed in terms of geographic coordinates of a bounding polygon. Not Applicable (O) Optional. This entity contains elements that do not require information, but it is recommended if applicable. (N) Dataset information may be recorded multiple times at the EXTENTS OF A DATASET BASED ON CO-ORDINATES OF A BOUNDING POLYGON entity level. This rule applies only to this entity level’s element. Metadata Entity for Element subgroup 2 of Element Group 4. Not Applicable The following term is an element listed under the EXTENTS OF A DATASET BASED ON CO-ORDINATES OF A BOUNDING POLYGON metadata subgroup entity:
63
43) Co-ordinates of a Bounding Polygon. Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments: Not Applicable
EXTENTS OF A DATASET (WHERE AND WHEN)
Return to index page
EXTENTS OF A DATASET BASED ON CO-ORDINATES OF A BOUNDING POLYGON CO-ORDINATES OF A BOUNDING POLYGON
43 Not Applicable 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. (O) Optional. The Co-ordinates of a Bounding Polygon element does not require information to be entered in its field, but it is recommended if applicable. (N) Unlimited number of Co-ordinates of a Bounding Polygon entries permitted for this element. Character String Free Text It is anticipated that a tool will be made available for capturing the x and y coordinates 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 coordinates, 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 ensure that the actual location is not revealed to the general public. Such study areas might include archaeological sites and endangered species habitats.
Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier:
1) Link to Bounding Polygon example [Ctrl and click here] p166
EXTENTS OF A DATASET (WHERE AND WHEN)
Return to index page
EXTENTS OF A DATASET BASED ON GEOGRAPHIC IDENTIFIERS
Not Applicable G4.3 (Element Group 4.subgroup 3)
64
Definition of Entity: Definition of Element: Obligation: Maximum Occurrence:
Geographic coverage expressed in terms of geographic identifiers. Not Applicable (O) Optional. This entity contains elements that do not require information input, but it is recommended if applicable. (1) Dataset information may be recorded only once at the EXTENTS OF A DATASET BASED ON GEOGRAPHIC IDENTIFIERS entity level. This rule applies only to the element group as a whole and not each element. Each element has a separate condition or rule for the number of occurrences permitted. Metadata Entity for Element subgroup 3 of Element Group 4. Not Applicable The following five terms are elements listed under the EXTENTS OF A DATASET BASED ON GEOGRAPHICS INDENTIFIERS metadata subgroup entity: 44) Nations 45) Administrative Areas 46) Postcode Districts 47) Controlled Place Name Vocabulary 48) Controlled Place Name Keywords
Data Type: Domain: Comments:
Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
Not Applicable
EXTENTS OF A DATASET (WHERE AND WHEN)
Return to index page
EXTENTS OF A DATASET BASED ON GEOGRAPHIC IDENTIFIERS NATIONS
44 Not Applicable Geographic coverage expressed in terms of nations within the British Isles. (O) Optional. The Nations element does not require information to be entered in its field, but it is recommended if applicable. (N) Unlimited number of Nations entries permitted for this element. Enumerated List UK GEMINI Extent List 1) England 2) England and Wales
65
Maximum Occurrence: Data Type: Domain:
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. 1) Link to Nation, Administrative Area, Postcode examples [Ctrl and click here] p 169
Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
EXTENTS OF A DATASET (WHERE AND WHEN)
Return to index page
EXTENTS OF A DATASET BASED ON GEOGRAPHIC IDENTIFIERS ADMINISTRATIVE AREAS
45 Not Applicable Geographic coverage expressed in terms of administrative areas. (O) Optional. The Administrative Areas element does not require information to be entered in its field, but it is recommended if applicable. (N) Unlimited number of Administrative Areas entries permitted for this element.
Character String Free Text Enter the relevant name(s) for the Administrative Areas. 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.
Examples:
1) Link to Nation, Administrative Area, Postcode examples [Ctrl and click here] p 169
66
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
EXTENTS OF A DATASET (WHERE AND WHEN)
Return to index page
EXTENTS OF A DATASET BASED ON GEOGRAPHIC IDENTIFIERS POSTCODE DISTRICTS
46 Not Applicable Geographic coverage expressed in terms of postcode districts. (O) Optional. The Postcode Districts element does not require information to be entered in its field, but it is recommended if applicable. (N) Unlimited number of Postcode Districts entries permitted for this element. Character String Free Text 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.
Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element:
1) Link to Nation, Administrative Area, Postcode examples [Ctrl and click here] p169
EXTENTS OF A DATASET (WHERE AND WHEN)
Return to index page
EXTENTS OF A DATASET BASED ON GEOGRAPHIC IDENTIFIERS CONTROLLED PLACE NAME VOCABULARY
47 Not Applicable Name of the controlled vocabulary used as a source for the controlled place name keywords.
67
Obligation:
(OS) Optional and searchable. The Controlled Place Name Vocabulary element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Controlled Place Name Vocabulary entry permitted for this element. Character String Free Text Currently, the Ordnance Survey (OS) 1:50,000 gazetteer is available to those organisations with subscriptions to the EDINA 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 GeoCrossWalk gazetteer provides comprehensive coverage for the United Kingdom. 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.
Maximum Occurrence: Data Type: Domain: Comments:
Examples:
1) Ordnance Survey (OS) 1:50,000 Gazetteer 2) Getty Thesaurus of Geographic Names 3) GeoCrossWalk
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
EXTENTS OF A DATASET (WHERE AND WHEN)
Return to index page
EXTENTS OF A DATASET BASED ON GEOGRAPHIC IDENTIFIERS CONTROLLED PLACE NAME KEYWORDS
48 Not Applicable The geographic name of a location(s) covered by a dataset. (OS) Optional and searchable. The Controlled Place Name Keywords element does not require information to be entered in its field, but it is recommended if applicable. (N) Unlimited number of selections from the Controlled Place Name Keywords element’s enumerated list is permitted for this element. Enumerated List See Comments
Maximum Occurrence: Data Type: Domain:
68
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 to 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
Examples:
1) A study area that is associated with the town of Colchester, England could include the following place names, which can all be found on-line using the Getty Thesaurus of Geographic Names web site search: United Kingdom, England, Essex, Colchester 2) A study area that is associated with the town of Haddington, Scotland could include the following place names: United Kingdom, Scotland, East Lothian, Haddington
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
EXTENTS OF A DATASET (WHERE AND WHEN) VERTICAL EXTENTS OF A DATASET
Not Applicable G4.4 The vertical extent of the dataset. Not Applicable
Return to index page
(O) Optional. This entity contains elements that do not require information, but it is recommended if applicable.
69
Maximum Occurrence:
(N) Dataset information may be recorded multiple times at the VERTICAL EXTENTS OF A DATASET entity level. This rule applies only to the entity level’s element subgroup as a whole and not each element. In this subgroup each element has a single entry condition applied. Metadata Entity for Element subgroup 4 of Element Group 4. Not Applicable The following four terms are elements listed under the VERTICAL EXTENTS OF A DATASET metadata subgroup entity: 49) Minimum Value 50) Maximum Value 51) Unit of Measure 52) Vertical Datum
Data Type: Domain: Comments:
Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
Not Applicable
EXTENTS OF A DATASET (WHERE AND WHEN) VERTICAL EXTENTS OF A DATASET MINIMUM VALUE
49 Not Applicable Lowest vertical extent contained in the dataset.
Return to index page
(C) Conditional. 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. (1) Once. No more than one Minimum Value entry permitted for this element. Real Number Real Number 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 UK 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.
Maximum Occurrence: Data Type: Domain: Comments:
Examples:
1) -2.75
70
2) 10.0 3) Link to Minimum Value examples [Ctrl and click here] p 172 Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
EXTENTS OF A DATASET (WHERE AND WHEN) VERTICAL EXTENTS OF A DATASET MAXIMUM VALUE
50 Not Applicable Highest vertical extent contained in the dataset.
Return to index page
(C) Conditional. 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. (1) Once. No more than one Maximum Value entry permitted for this element. Real Number Real Number 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 UK AGMAP element G4.4-51. If the former is used, then the value entered for G4.4-51 could be in inches, feet et al; the value for the latter could in 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.
Maximum Occurrence: Data Type: Domain: Comments:
Examples:
1) 1,343 2) 10.0 3) Link to Maximum Value examples [Ctrl and click here] p 172
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of
EXTENTS OF A DATASET (WHERE AND WHEN) VERTICAL EXTENTS OF A DATASET UNIT OF MEASURE
51 Not Applicable Vertical units used for vertical extent.
Return to index page
71
Element: Obligation: (C) Conditional. 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. (1) Once. No more than one Unit of Measure entry permitted for this element. Character String Free Text 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. 1) Feet 2) Metres Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
Maximum Occurrence: Data Type: Domain: Comments: Examples:
EXTENTS OF A DATASET (WHERE AND WHEN) VERTICAL EXTENTS OF A DATASET VERTICAL DATUM
52 Not Applicable The origin from which the elevation values are measured.
Return to index page
(C) Conditional. 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. (1) Once. No more than one Vertical Datum entry permitted for this element.
Maximum Occurrence: Data Type: Domain:
Character String Free Text
72
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 loweraccuracy 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
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence:
EXTENTS OF A DATASET (WHERE AND WHEN) TEMPORAL EXTENTS OF A DATASET
Not Applicable G4.5 Time period that the content of a dataset covers. Not Applicable
Return to index page
(O) Optional. This entity contains elements that do not require information, but it is recommended if applicable. (N) Dataset information may be recorded multiple times at the TEMPORAL EXTENTS OF A DATASET entity level. This rule applies only to the entity level’s element subgroup as a whole and not each element. In this subgroup each element has a single entry condition applied. Metadata Entity for Element subgroup 5 of Element Group 4. Not Applicable The following two terms are elements listed under the TEMPORAL EXTENTS OF A DATASET metadata subgroup entity: 52) Start Date for Time Period Covered by the Dataset 53) End Date for Time Period Covered by the Dataset
Data Type: Domain: Comments:
Examples:
Not Applicable
73
Entity Name: Subgroup Entity Name: Element Name:
EXTENTS OF A DATASET (WHERE AND WHEN) TEMPORAL EXTENTS OF A DATASET
Return to index page
START DATE FOR TIME PERIOD COVERED BY THE DATASET
53 Not Applicable The start date of the actual time period the dataset covers. (O) Optional. 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. (1) Once. No more than one Start Date for Time Period Covered by Dataset entry permitted for this element. Date YYYY-MM-DD 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 (YearMonth-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.
Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
Examples:
1) 2001-01-31 2) 2001-01 3) 2001 4) -0055 5) 0450
[ Entire date known, including year, month and day ] [ Year and month of date known, but not day ] [ Year known, but not month and day ] [ The year 55 BC ] [ The year AD 450 ]
74
Entity Name: Subgroup Entity Name: Element Name:
EXTENTS OF A DATASET (WHERE AND WHEN) TEMPORAL EXTENTS OF A DATASET
Return to index page
END DATE FOR TIME PERIOD COVERED BY THE DATASET
54 Not Applicable The end date of the actual time period the dataset covers. (O) Optional. 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. (1) Once. No more than one End Date for Time Period Covered by Dataset entry permitted for this element. Date YYYY-MM-DD 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.
Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
Examples:
1) 2001-01-31 2) 2001-01 3) 2001 4) -0055 5) 0450
[ Entire date known, including year, month and day ] [ Year and month of date known, but not day ] [ Year known, but not month and day ] [ The year 55 BC ] [ The year AD 450 ]
75
Entity Name:
CUSTODIAN
Not Applicable G5 (Element Group 5)
Return to index page
Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
The organisation or person responsible for the maintenance of the dataset. Not Applicable (M) Mandatory. This entity is contains elements that require information. (1) Dataset information may be recorded only once at the CUSTODIAN entity level. This rule applies only to the element group as a whole and not each element. Each element has a separate condition or rule for the number of occurrences permitted. Metadata Entity for Element Group 5. Not Applicable The following 10 terms comprise the group of elements listed under the CUSTODIAN metadata entity: 55) Name of Custodian 56) Postal Street Address of Custodian 57) Postal City of Custodian 58) Postal County of Custodian 59) Postal Code of Custodian 60) Postal Country of Custodian 61) Telephone Number of Custodian 62) Facsimile Number of Custodian 63) Email Address of Custodian 64) Web Address of Custodian
Examples:
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
Not Applicable
CUSTODIAN NAME OF CUSTODIAN
55 Not Applicable
Return to index page
The name of the organisation or person responsible for the maintenance of the dataset. (M) Mandatory. The Name of Custodian element must have information entered in its field.
76
Maximum Occurrence: Data Type: Domain: Comments:
(1) Once. No more than one Name of Custodian entry permitted for this element. Character String Free Text 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 title, given name, middle name or initial(s) with full-stop and surname. If it is preferable not to provide a name, then please list the organisation. 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 Jane Doe 2) Dr Jane Doe 3) Ms Jane Doe 4) Miss Jane Doe 5) Mrs Jane Doe 6) Mary Jane Doe 7) Jane M Doe 8) Jane Doe 9) Mr John Doe 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
77
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
CUSTODIAN POSTAL STREET ADDRESS OF CUSTODIAN
56 Not Applicable
Return to index page
Postal Street part of address for organisation or person responsible for the maintenance of the dataset. (M) Mandatory. The Postal Street Address of Custodian element must have information entered in its field. (1) Once. No more than one Postal Street Address of Custodian entry permitted for this element. Character String Free Text 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
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain:
CUSTODIAN POSTAL CITY OF CUSTODIAN
57 Not Applicable
Return to index page
Postal city part of address for organisation or person responsible for the maintenance of the dataset. (M) Mandatory. The Postal City of Custodian element must have information entered in its field. (1) Once. No more than one Postal City of Custodian entry permitted for this element. Character String Free Text
78
Comments: Examples:
The Postal City also refers to any populated place that is listed as a city, town or village in an address. 1) London 2) Edinburgh 3) Belfast 4) Cardiff 5) Norwich 6) Colchester 7) Manchester 8) Keele Village
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments: Examples:
CUSTODIAN POSTAL COUNTY OF CUSTODIAN
58 Not Applicable
Return to index page
Postal county part of address for organisation or person responsible for the maintenance of the dataset. (O) Optional. Postal County of Custodian element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Postal County of Custodian entry permitted for this element. Character String Free Text 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. 1) Essex 2) East Lothian 3) Glamorganshire 4) County Antrim
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element:
CUSTODIAN POSTAL CODE OF CUSTODIAN
59 Not Applicable
Return to index page
Postal code part of address for the organisation or person responsible for the maintenance of the dataset.
79
Obligation: Maximum Occurrence: Data Type: Domain: Comments: Examples:
(M) Mandatory. The Postal Code of Custodian element must have information entered in its field. (1) Once. No more than one Postal Code of Custodian entry permitted for this element. Character String Free Text Enter the complete postal code for the contact organisation or person. 1) CO1 1UB 2) EH8 9LJ 3) CF10 3YE 4) W9 3NN
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
CUSTODIAN POSTAL COUNTRY OF CUSTODIAN
60 Not Applicable
Return to index page
Postal country part of address for the organisation or person responsible for the maintenance of the dataset. (M) Mandatory. The Postal Country of Custodian element must have information entered in its field. (1) Once. No more than one Postal Country of Custodian entry permitted for this element. Character String Free Text 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. 1) United Kingdom 2) Great Britain 3) England 4) Northern Ireland 5) Scotland 6) Wales
80
Maximum Occurrence: Data Type: Domain: Comments:
Examples:
7) Channel Isles 8) Isle of Man 9) Republic of Ireland Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
CUSTODIAN TELEPHONE NUMBER OF CUSTODIAN
61 Not Applicable
Return to index page
Telephone number by which individuals can talk to the organisation or person responsible for the maintenance of the dataset. (O) Optional. Telephone Number of Custodian element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Telephone Number of Custodian entry permitted for this element. Character String Free Text The international format should be used for listing the telephone number. This includes the plus sign (+) followed by the United Kingdom’s country code, area code (with the zero in brackets) and number. 1) +44 (0) 123 456 789
Maximum Occurrence: Data Type: Domain: Comments:
Examples: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain:
CUSTODIAN FACSIMILE NUMBER OF CUSTODIAN
62 Not Applicable
Return to index page
Facsimile number which individuals can use to contact the organisation or person responsible for the maintenance of the dataset. (O) Optional. Facsimile Number of Custodian element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Facsimile Number of Custodian entry permitted for this element. Character String Free Text
81
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. 1) +44 (0) 123 456 789
Examples: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
CUSTODIAN EMAIL ADDRESS OF CUSTODIAN
63 Not Applicable
Return to index page
Internet email address which individuals can use to contact the organisation or person responsible for the maintenance of the dataset. (O) Optional. Email Address of Custodian element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Email Address of Custodian entry permitted for this element. Character String Free Text The email address should be associated with the contact name or organisation that is listed in Name of Custodian element, 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. 1) anyone@university.ac.uk
Examples: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain:
CUSTODIAN WEB ADDRESS OF CUSTODIAN
64 Not Applicable
Return to index page
Custodian’s World Wide Web site Uniform Resource Locator (URL) address. (O) Optional. Web Address of Custodian element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Web Address of Custodian entry permitted for this element. Character String Free Text
82
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. 1) http://www.data-custodian.ac.uk/
Examples: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence:
DISTRIBUTOR (ACCESS)
Not Applicable G6 (Element Group 6)
Return to index page
The organisation or person responsible for the distribution of the dataset. Not Applicable (M) Mandatory. This entity is contains elements that require information. (N) Dataset information may be recorded multiple times at the DISTRIBUTOR entity level. This rule applies only to the entity level’s element subgroup as a whole and not each element. Each element has a separate condition or rule for the number of occurrences permitted. Metadata Entity for Element Group 6 Not Applicable Under the DISTRIBUTOR (ACCESS) metadata entity there are the two following subgroup metadata entities: G6.1) DATASET FORMAT NAME AND DATASET FORMAT VERSION G6.2) ACCESS AND USE CONSTRAINTS The following 19 terms comprise the group of elements listed under the DISTRIBUTOR (ACCESS) metadata entity and two subgroup entities: 65) Name of Distributor 66) Distributor Contact Title 67) Postal Street Address of Distributor 68) Postal City of Distributor 69) Postal Code of Distributor 70) Postal Country of Distributor 71) Telephone Number of Distributor 72) Facsimile Number of Distributor 73) Email Address of Distributor 74) Web Address of Distributor 75) Supply Media
83
Data Type: Domain: Comments:
76) On-line Linkage 77) Dataset File Size G6.1) DATASET FORMAT NAME AND DATASET FORMAT VERSION 78) Dataset Format Name 79) Dataset Format Version G6.2) ACCESS AND USE CONSTRAINTS 80) Access Constraints 81) Use Constraints 82) Use Constraints Details 83) Other Constraints Details Examples: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments: Not Applicable
DISTRIBUTOR (ACCESS) NAME OF DISTRIBUTOR
65 Not Applicable
Return to index page
The name of the organisation or person from whom the dataset may be obtained. (M) Mandatory. The Name of Distributor element must have information entered in its field. (1) Once. No more than one Name of Distributor entry permitted for this element. Character String Free Text 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 title, given name, middle name or initial(s) with full-stop and surname. If it is preferable not to provide a name, then please list the organisation.
84
Examples:
Individuals: 1) Professor Jane Doe 2) Dr Jane Doe 3) Ms Jane Doe 4) Miss Jane Doe 5) Mrs Jane Doe 6) Mary Jane Doe 7) Jane M Doe 8) Jane Doe 9) Mr John Doe
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
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
DISTRIBUTOR (ACCESS) DISTRIBUTOR CONTACT TITLE
66 Not Applicable
Return to index page
Role or position of the responsible person for the distribution of the dataset. (O) Optional. Distributor Contact Title element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Distributor Contact Title entry permitted for this element. Character String Free Text 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. 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
85
Examples:
10) Reader in Urban Planning 11) Statistician Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
DISTRIBUTOR (ACCESS) POSTAL STREET ADDRESS OF DISTRIBUTOR
67 Not Applicable
Return to index page
Postal address for the dataset distributor including organisation name, building name or number, and street name. (M) Mandatory. The Full Postal Address of Distributor element must have information entered in its field. (1) Once. No more than one Full Postal Address of Distributor entry permitted for this element. Character String Free Text 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 are not 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
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type:
DISTRIBUTOR (ACCESS) POSTAL CITY OF DISTRIBUTOR
68 Not Applicable
Return to index page
Postal city part of address for organisation or person responsible for the distribution of the dataset. (M) Mandatory. The Postal City of Distributor element must have information entered in its field. (1) Once. No more than one Postal City of Distributor entry permitted for this element. Character String
86
Domain: Comments: Examples:
Free Text The Postal City also refers to any populated place that is listed as a city, town or village in an address. 1) London 2) Edinburgh 3) Belfast 4) Cardiff 5) Norwich 6) Colchester 7) Manchester 8) Keele Village
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
DISTRIBUTOR (ACCESS) POSTAL CODE OF DISTRIBUTOR
69 Not Applicable
Return to index page
Postal code part of the address for organisation or person responsible for the distribution of the dataset. (M) Mandatory. The Full Postal Code of Distributor element must have information entered in its field. (1) Once. No more than one Full Postal Code of Distributor entry permitted for this element. Character String Free Text Enter the complete postal code for the contact organisation or person. 1) CO1 1UB 2) EH8 9LJ 3) CF10 3YE 4) CF10 3YE
Maximum Occurrence: Data Type: Domain: Comments: Examples:
Entity Name: Element Name: Identifier: Definition of Entity:
DISTRIBUTOR (ACCESS) POSTAL COUNTRY OF DISTRIBUTOR
70 Not Applicable
Return to index page
87
Definition of Element: Obligation:
Postal country part of address for the organisation or person responsible for the distribution of the dataset. (M) Mandatory. The Postal Country of Distributor element must have information entered in its field. (1) Once. No more than one Postal Country of Distributor entry permitted for this element. Character String Free Text 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. 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
Maximum Occurrence: Data Type: Domain: Comments:
Examples:
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
DISTRIBUTOR (ACCESS) TELEPHONE NUMBER OF DISTRIBUTOR
71 Not Applicable
Return to index page
Telephone number by which individuals can talk to the organisation or person responsible for the distribution of the dataset. (O) Optional. Telephone Number of Distributor element does not require information to be entered in its field, but recommended if applicable. (1) Once. No more than one Telephone Number of Distributor entry permitted for this element. Character String Free Text
88
Maximum Occurrence: Data Type: Domain:
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, area code (with the zero in brackets) and number. 1) +44 (0) 123 456 789
Examples: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
DISTRIBUTOR (ACCESS) FACSIMILE NUMBER OF DISTRIBUTOR
72 Not Applicable
Return to index page
Facsimile number which individuals can use to contact the organisation or person responsible for the distribution of the dataset. (O) Optional. Facsimile Number of Distributor element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Facsimile Number of Distributor entry permitted for this element. Character String Free Text The international format should be used for listing the telephone number. This includes the plus sign (+) followed by the United Kingdom’s country code, area code (with the zero in brackets) and number. 1) +44 (0) 123 456 789
Maximum Occurrence: Data Type: Domain: Comments:
Examples: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain:
DISTRIBUTOR (ACCESS) EMAIL ADDRESS OF DISTIBUTOR
73 Not Applicable
Return to index page
Internet email address which individuals can use to contact the organisation or person responsible for the distribution of the dataset. (O) Optional. Email Number of Distributor element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Email Number of Distributor entry permitted for this element. Character String Free Text
89
Comments:
The email address should be associated with the contact name or organisation that is listed in Name of Distributor element, 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. 1) anyone@university.ac.uk
Examples: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
DISTRIBUTOR (ACCESS) WEB ADDRESS OF DISTRIBUTOR
74 Not Applicable
Return to index page
Dataset distributor organisation’s World Wide Web site Uniform Resource Locator (URL) address. (O) Optional. Web Address of Distributor element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Web Address of Distributor entry permitted for this element. Character String Free Text 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: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
1) http://www.data-distributor.ac.uk/
DISTRIBUTOR (ACCESS) SUPPLY MEDIA
75 Not Applicable Media formats in which the dataset can be supplied.
Return to index page
(O) Optional. Supply Media element does not require information to be entered in its field, but recommended if applicable.
90
Maximum Occurrence: Data Type: Domain:
(N) Unlimited number of selections from the Supply Media element’s enumerated list permitted for this element. Enumerated List 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 0,25 inch magnetic tape. 013
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.
91
Comments: Examples:
Select one or more of the relevant media provided on the list. 1) cdRom 2) digitalLinearTape 3) hardcopy
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
DISTRIBUTOR (ACCESS) ON-LINE LINKAGE
76 Not Applicable
Return to index page
The name of the World Wide Web site or other on-line source that contains the dataset. (O) Optional. The On-line Linkage element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one On-line Linkage entry permitted for this element.
Maximum Occurrence: Data Type: Domain: Comments: Examples:
Character String Free Text This element provides the URL or FTP address for the user to directly access the dataset or resource. 1) http://www.data-distributor.ac.uk/ 2) ftp://data-distributor/data/
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain:
DISTRIBUTOR (ACCESS) DATASET FILE SIZE
77 Not Applicable
Return to index page
The name of the World Wide Web site or other on-line source that contains the dataset. (O) Optional. The Dataset File Size element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Dataset File Size entry permitted for this element. Real Number Real Number
92
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). 1) 284.0 2) 0.56 3) 3.596
Examples:
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence:
DISTRIBUTOR (ACCESS) DATASET NAME AND FORMAT
Not Applicable G6.1 (Group 6.subgroup 1)
Return to index page
Dataset name and format in which digital data can be provided. Not Applicable (M) Mandatory. This entity contains elements that require information. (N) Dataset information may be recorded multiple times at the DATASET FORMAT NAME AND DATASET FORMAT VERSION entity level. This rule applies only to the entity level’s element subgroup as a whole and not each element. Each element in this instance allows for only a single entry. Metadata Entity for Element Subgroup 1 of Identification Information Group 6 Not Applicable The following two terms are elements listed under the DATASET NAME AND FORMAT metadata subgroup entity: 78) Dataset Format Name; 79) Dataset Format Name.
Data Type: Domain: Comments:
Examples:
Not Applicable
93
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
DISTRIBUTOR (ACCESS) DATASET NAME AND FORMAT DATASET FORMAT NAME
78 Not Applicable
Return to index page
Dataset format name in which digital data can be provided (e.g.: DXF, DLG, MapInfo, IDRISI, ARC/INFO, ERDAS, DBF, RTF, etc.). (M) Mandatory. The Dataset Format Name element must have information entered in its field. (1) Once. No more than one Dataset Format Name entry permitted for this element. Character String Free Text 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 asterisk, full-stop and extension (e.g.: IDRISI Kilimanjaro *.RST ). 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.
94
*.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 nontopological geometry and attribute information for the spatial features in a dataset. 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. Geography Markup Language (*.gml) 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/Andes (*.img,/*.doc, *.rst/*.rdc, *.vec, /*.dvc, *.vct/*.vdc) A Clark Labs GIS product, IDRISI32, Kilimanjaro and Andes raster image consists of
95
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 (Hierarchical Data 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
96
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. 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) *.RST 3) *.Shp [ IDRISI Kilimanjaro ] [ MapInfo ] [ ArcView ] 2) *.MID/MIF
97
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments: Examples:
DISTRIBUTOR (ACCESS) DATASET NAME AND FORMAT DATASET FORMAT VERSION
79 Not Applicable
Return to index page
Dataset format version in which digital data can be provided (e.g.: 1.0, 3.1, 8.0). (M) Mandatory. The Dataset Format Version element must have information entered in its field. (1) Once. No more than one Dataset Format Version entry permitted for this element. Character String Free Text 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. 1) 14.02 2) 6.5 3) 9.0
Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
DISTRIBUTOR (ACCESS) ACCESS AND USE CONSTRAINTS
Not Applicable G6.2 (Element Group 6.subgroup 2)
Return to index page
Not Applicable Restrictions and legal prerequisites for accessing or using the dataset. (O) Optional. This entity contains elements that do not require information, but it is recommended if applicable. (N) Dataset information may be recorded multiple times at the ACCESS AND USE CONSTRAINTS entity level. This rule applies only to the entity level’s element subgroup as a whole and not each element. Each element has a separate condition or rule for the number of occurrences permitted. Metadata Entity for Element subgroup 2 of Element Group 6
98
Maximum Occurrence:
Data Type:
Domain: Comments:
Not Applicable The following four terms are elements listed under the ACCESS AND USE CONSTRAINTS metadata subgroup entity: 80) Access Constraints; 81) Use Constraints; 82) Use Constraints Details; 83) Other Constraints Details.
Examples: Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type:
Not Applicable
DISTRIBUTOR (ACCESS) ACCESS AND USE CONSTRAINTS ACCESS CONSTRAINTS
80 Not Applicable
Return to index page
Restrictions and legal prerequisites for accessing the dataset. These include any access constraints applied to ensure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the dataset. (O) Optional. Access Constraints element does not require information to be entered in its field, but it is recommended if applicable. (N) Unlimited number of selections from the Access Constraints element’s enumerated list permitted for this element. Enumerated List
99
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 Limitation not listed. Comments: 008
Select one or more of the choices from the list that best describes the type of ACCESS 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. Each organisation must determine which condition applies to the access constraints. This is done through internal consultation with the responsible parties or legal consul. The ISO 19115 committee has chosen the spelling of ‘license’ rather than ‘licence’.
Examples:
1) copyright 2) otherRestrictions
Entity Name: Subgroup Entity Name: Element Name: Identifier:
DISTRIBUTOR (ACCESS) ACCESS AND USE CONSTRAINTS USE CONSTRAINTS
81
Return to index page
100
Definition of Entity: Definition of Element: Obligation:
Not Applicable Restrictions and legal prerequisites for using the dataset. These include any use constraints applied to ensure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the dataset. (O) Optional. Use Constraints element does not require information to be entered in its field, but it is recommended if applicable. (N) Unlimited number of selections from the Use Constraints element’s enumerated list permitted for this element. Enumerated List ISO 19115 B.5.24 (MD_RestrictionCode)
Maximum Occurrence: Data Type: Domain:
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 Limitation not listed. Comments: 008
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. Each organisation must determine which condition applies to the use constraints. This is done through internal consultation with the responsible parties or legal consul.
101
The ISO 19115 committee has chosen the spelling of ‘license’ rather than ‘licence’. Examples: 1) intellectualPropertyRights 2 license Entity Name: Subgroup Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
DISTRIBUTOR (ACCESS) ACCESS AND USE CONSTRAINTS USE CONSTRAINTS DETAILS
82 Not Applicable
Return to index page
Description of the restrictions and legal prerequisites for accessing the dataset. (O) Optional. Use Constraints Details element does not require information to be entered in its field, but it is recommended if applicable. (N) Multiple number of Access Details entries permitted for this element. Character String Free Text 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.
Entity Name: Subgroup Entity Name: Element Name: Identifier:
DISTRIBUTOR (ACCESS) ACCESS AND USE CONSTRAINTS OTHER CONSTRAINTS DETAILS
83
Return to index page
102
Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
Not Applicable Description of the restrictions and legal prerequisites for accessing the dataset. (O) Optional. Access Details element does not require information to be entered in its field, but it is recommended if applicable. (N) Multiple number of Access Details entries permitted for this element.
Character String Free Text 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.
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence:
METADATA CREATOR
Not Applicable G7 (Element Group 7)
Return to index page
The organisation or person responsible for the last update of the metadata. Not Applicable (M) Mandatory. This entity contains elements that require information. (1) Dataset information may be recorded only once at the METADATA CREATOR entity level. This rule applies only to the element group as a whole and not each element. Each element has a separate condition or rule for the number of occurrences permitted. Metadata Entity for Element Group 7 Not Applicable
Data Type: Domain:
103
Comments:
The following 14 terms comprise the group of elements listed under the METADATA CREATOR metadata entity: 84) Name of Metadata Creator 85) Postal Address of Metadata Creator 86) Postal City of Metadata Creator 87) Postal Code of Metadata Creator 88) Postal Country of Metadata Creator 89) Telephone Number of Metadata Creator 90) Facsimile Number of Metadata Creator 91) Email Address of Metadata Creator 92) Web Address of Metadata Creator 93) Metadata Record Identifier 94) Parent Metadata Record Identifier 95) Metadata Last Updated 96) Metadata Standard Name 97) Metadata Standard Version
Examples: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
Not Applicable
METADATA CREATOR NAME OF METADATA CREATOR
84 Not Applicable
Return to index page
The name of the organisation or person responsible for the metadata and their updates. (M) Mandatory. The Name of Metadata Creator element must have information entered in its field. (1) Once. No more than one Name of Metadata Creator entry permitted for this element. Character String Free Text 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 title, given name, middle name or initial(s) with full-stop and surname. If it is preferable not to provide a name, then please list the organisation. 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.
104
Examples:
Individuals: 1) Professor Jane Doe 2) Dr Jane Doe 3) Ms Jane Doe 4) Miss Jane Doe 5) Mrs Jane Doe 6) Mary Jane Doe 7) Jane M Doe 8) Jane Doe 9) Mr John Doe 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
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain:
METADATA CREATOR
Return to index page
POSTAL STREET ADDRESS OF METADATA CREATOR
85 Not Applicable Postal address of the organisation or person responsible for the metadata, including organisation name, building name and/or number and street name. (M) Mandatory. The Full Postal Address of Metadata Creator element must have information entered in its field. (1) Once. No more than one Full Postal Address of Metadata Creator entry permitted for this element. Character String Free Text
105
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
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments: Examples:
METADATA CREATOR POSTAL CITY OF METADATA CREATOR
86 Not Applicable
Return to index page
Postal city part of address for organisation or person responsible for the metadata. (M) Mandatory. The Postal City of Metadata Creator element must have information entered in its field. (1) Once. No more than one Postal City of Metadata Creator entry permitted for this element. Character String Free Text The Postal City also refers to any populated place that is listed as a city, town or village in an address. 1) London 2) Edinburgh 3) Belfast 4) Cardiff 5) Norwich 6) Colchester 7) Manchester 8) Keele Village
Entity Name: Element Name: Identifier:
METADATA CREATOR POSTAL CODE OF METADATA CREATOR
87
Return to index page
106
Definition of Entity: Definition of Element: Obligation:
Not Applicable Postal code part of the address for organisation or person responsible for metadata. (M) Mandatory. The Postal Code of Metadata Creator element must have information entered in its field. (1) Once. No more than one Postal Code of Metadata Creator entry permitted for this element. Character String Free Text Enter the complete postal code for the contact organisation or person. 1) CO1 1UB 2) EH8 9LJ 3) BT7 1NN 4) CF10 3YE 5) W9 3NN
Maximum Occurrence: Data Type: Domain: Comments: Examples:
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
METADATA CREATOR POSTAL COUNTRY OF METADATA CREATOR
88 Not Applicable
Return to index page
Postal country part of address for organisation or person responsible for the metadata creation and updates. (M) Mandatory. The Postal Country of Metadata Creator element must have information entered in its field. (1) Once. No more than one Postal Country of Metadata Creator entry permitted for this element. Character String Free Text 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.
107
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
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
METADATA CREATOR TELEPHONE NUMBER OF METADATA CREATOR
89 Not Applicable
Return to index page
Telephone number by which individuals can talk to the organisation or person responsible for metadata updates. (O) Optional. Telephone Number of Metadata Creator element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Telephone Number of Metadata Creator entry permitted for this element. Character String Free Text The international format should be used for listing the telephone number. This includes the plus sign (+) followed by the United Kingdom’s country code, area code (with the zero in brackets) and number. 1) +44 (0) 123 456 789
Examples: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
METADATA CREATOR FACSIMILE NUMBER OF METADATA CREATOR
90 Not Applicable
Return to index page
Facsimile number which individuals can use to contact the organisation or person responsible for the metadata. (O) Optional. Facsimile Number of Metadata Creator element does not require information to be entered in its field, but it is recommended if applicable.
108
Maximum Occurrence: Data Type: Domain: Comments:
(1) Once. No more than one Facsimile Number of Metadata Creator entry permitted for this element. Character String Free Text 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 number. 1) +44 (0) 123 456 789
Examples:
Entity Name:
Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
METADATA CREATOR EMAIL ADDRESS OF METADATA CREATOR
91 Not Applicable
Return to index page
Internet email address which individuals can use to contact the organisation or person responsible for metadata updates. (O) Optional. Email Address of Metadata Creator element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Email Address of Metadata Creator entry permitted for this element. Character String Free Text The email address should be associated with the author or creator of the metadata record. It might be 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. 1) anyone@university.ac.uk
Examples: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
METADATA CREATOR WEB ADDRESS OF METADATA CREATOR
92 Not Applicable
Return to index page
Metadata creator’s World Wide Web site Uniform Resource Locator (URL) address. (O) Optional. Web Address of Metadata Creator element does not require information to be entered in its field, but it is recommended if applicable.
109
Maximum Occurrence: Data Type: Domain: Comments:
(1) Once. No more than one Web Address of Metadata Creator entry permitted for this element. Character String Free Text 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. 1) http://www.metadata-creator.ac.uk/
Examples: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
METADATA CREATOR METADATA RECORD IDENTIFIER
93 Not Applicable Unique identifier for the metadata record.
Return to index page
(O) Optional. Metadata Record Identifier element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Metadata Record Identifier entry permitted for this element. Character String Free Text 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 element, 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 Identifier element, there are a number of identifiers that are recognised and used internationally which can be applied to datasets. These in turn
110
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 Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation:
METADATA CREATOR PARENT METADATA RECORD IDENTIFIER
94 Not Applicable Identifier used for parent or original metadata record.
Return to index page
(C) Conditional. If metadata record is a subset or offspring of an original record, then Metadata Record Identifier value should be entered
Maximum Occurrence:
(1) Once. No more than one Metadata Record Identifier entry permitted for this element.
Data Type: Domain:
Character String Free Text
111
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 element, 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 the data developer’s discretion 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 Identifier element, 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
112
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
METADATA CREATOR METADATA LAST UPDATED
95 Not Applicable Date on which the metadata record was created or last updated.
Return to index page
(M) Mandatory. The Metadata Last Updated element must have information entered in its field. (1) Once. No more than one Metadata Last Updated entry permitted for this element. Date YYYY-MM-DD 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 (YearMonth-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 3) 2002 [ Year and month of date known, but not day ] [ Year known, but not month and day ]
Return to index page
Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain:
METADATA CREATOR METADATA STANDARD NAME
96 Not Applicable Name of the metadata standard (including the profile) used.
(O) Optional. Metadata Standard Name element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Metadata Standard Name entry permitted for this element. Character String Free Text
113
Comments:
This refers to the name for the ISO 19115 standard and the UK Academic Geospatial Metadata Application Profile (UK AGMAP). The input format requires that the values are hyphen separated with the ISO 19115 name listed first and the UK AGMAP name in the second. 1) ISO 19115 - UK AGMAP
Examples: Entity Name: Element Name: Identifier: Definition of Entity: Definition of Element: Obligation: Maximum Occurrence: Data Type: Domain: Comments:
METADATA CREATOR METADATA STANDARD VERSION
97 Not Applicable Version of the metadata standard (including the profile) used.
Return to index page
(O) Optional. Metadata Standard Version element does not require information to be entered in its field, but it is recommended if applicable. (1) Once. No more than one Metadata Standard Version entry permitted for this element. Character String Free Text This refers to the version for the ISO 19115 standard and the UK Academic Geospatial Metadata Application Profile (UK AGMAP). The input format requires that the values are hyphen separated with the ISO 19115 version listed first and the UK AGMAP version in the second. 1) 1.0 - 1.0
Examples:
114
3.0 Appendix A (UK AGMAP) Go-Geo! UK Academic Geospatial Metadata Application Profile (UK AGMAP)
SUBGROUP
GROUP
Entity Go-Geo! Metadata and Entity and Element Element Names ID G1
1 2 3 4 5
Go-Geo! Definition
Obligation
MO
(Maximum Occurrence)
Data Type
Domain
CITATION
Dataset Title Alternative Dataset Title Creator Identifier Edition Dataset Date Code Dataset Event Date
Dataset reference information
Mandatory
N
Metadata Entity GROUP 1 Character String Character String Character String Character String Character String Text Text Text Text Text Creation Publication Revision Deletion Date Continual Daily Weekly Fortnightly Monthly Quarterly Biannually Annually As Needed Irregular Not Planned Unknown
The name by which the dataset is known. Short name, other name, acronym or alternative language title for dataset. Organisation or person that developed the dataset and has primary responsibility for the intellectual content of the dataset. A unique string or number used to identify the dataset. The number of the edition of the dataset.
Mandatory (1) Optional Mandatory (2) Optional Mandatory (3)
1 N N 1 1
CITATION
6
Dataset event used for reference date.
Mandatory (4)
1
Enumerated List
7
Event date for the dataset.
Mandatory (5)
1
Date
8
Dataset Update Frequency
The frequency with which revisions and updates are made to the dataset after its initial completion.
Mandatory (6)
1
Enumerated List
115
G2
IDENTIFICATION INFORMATION (WHAT)
Basic Information about the dataset
Mandatory
1
Metadata Entity GROUP 2
9
Dataset Language
The language(s) used within the dataset.
Mandatory (7)
N
Enumerated List
IDENTIFICATION INFORMATION
10
Dataset Topic
Main theme(s) of the dataset.
Mandatory (8)
N
Enumerated List
English Cornish Gaelic (Scottish) (Gallic) Irish Welsh Farming Biota Boundaries Climatology/Meteorology/Atmosphere Economy Elevation Environment Geo-scientific Information Health Imagery/Base Maps/Earth Cover Intelligence/Military Inland Waters Location Oceans Planning/Cadastre Society Structure Transportation Utilities/Communication UNESCO Thesaurus Search UNESCO for term(s) Text
11 12 13
Controlled Vocabulary Controlled Keywords Other Keywords
Name of the controlled vocabulary used as a source for the controlled keywords. Keywords taken from a controlled vocabulary summarising the subject of the dataset. Other words or phrases summarising the subject of the dataset. 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.
Mandatory (9) Mandatory (10) Optional
1 N N
Character String Enumerated List Character String
14
Abstract
Mandatory (11)
1
Character String
Text Vector Grid Text Table Tin Stereo Model Video
15
Spatial Representation Type
Method used to spatially Represent geographic information.
Optional
N
Enumerated List
116
16
Presentation Type
Form in which the dataset is represented.
Optional
N
Enumerated List
Digital Document Hardcopy Document Digital Image Hardcopy Image Digital Map Hardcopy Map Digital Model Hardcopy Model Digital Profile Hardcopy Profile Digital Table Hardcopy Table Digital Video Hardcopy Video Text Text
17 18
Sample Further Information
The name of the file that contains the graphic that provides an illustration of the dataset. Source of further information about the dataset.
Optional Optional
N N
Character String Character String
19
Related Datasets
Information about other, related datasets of a similar theme or derived from a common source which may be of interest to the user.
Optional
N
Character String
Text
G2.1
SPATIAL REFERENCE SYSTEM OF THE DATASET
Name or description of the spatial referencing system used within the dataset.
Mandatory
1
Metadata Entity GROUP 2 SUBGROUP 1 National Grid of Great Britain Irish National 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
SPATIAL REFERENCE SYSTEM OF THE DATASET
20
Spatial Reference System
Name of the spatial referencing system used within the dataset It can be based on co-ordinates (e.g.: National Grid of Great Britain) or geographic identifiers (e.g.: Postcode).
Mandatory (12)
1
Enumerated List
117
G3
DATA QUALITY INFORMATION
A general assessment of the quality of a dataset for determining its fitness for use. Quality is stated in terms of dataset process steps, data capture, quality summary statements and spatial granularity.
Optional
1
Metadata Entity GROUP 3 Attribute Attribute Type Collection Hardware Collection Session Dataset Series Non-Geographic Dataset Dimension Group Feature Feature Type Property Type Field Session Software Service Model Tile
21
Data Hierarchical Level
Hierarchical level of the data stated in the process steps and quality statement. Default = Dataset
DATA QUALITY INFORMATION
Optional/Conditional: The default is set to ‘Dataset’. If a value is entered in an element field under Data Process Step, Quality Statement or Level of Spatial Detail, and the value pertains to a different hierarchical level, then corresponding value must be selected.
1
Enumerated List
G3.1
DATA PROCESS STEPS
Overview of the dataset creation process steps including the status and time periods for data capture, and a dataset’s lineage and process steps.
Optional
1
Metadata Entity GROUP 3 SUBGROUP 1 Completed Historical Archive Obsolete Ongoing Planned Required Under Development
22 DATASET PROCESS STEPS
Status of Data Creation Process
Declaration on the status for the data processing steps.
Optional
1
Enumerated List
23
Start Date of Data Capture Period
Date on which data were first collected.
24
End Date of Data Capture Period
Date on which data were last collected.
Conditional: If a Status of Data Creation Process value is selected, then a start date should be entered. Conditional: If a Status of Data Creation Process value is selected, then an end date should be entered. Optional Optional
1
Date
Date
1
Date
Date
25 26
Dataset Lineage Description of Dataset Process Steps
Information about the source data used in the construction of the dataset. A general description of how the dataset was generated or derived.
1 1
Character String Character String
Text Text
118
G3.2
DATA QUALITY STATEMENT
An assessment of data quality based on logical consistency, completeness, spatial accuracy and attribute accuracy.
Optional
N
Metadata Entity GROUP 3 SUBGROUP 2
27 DATA QUALITY STATEMENT
Logical Consistency
Degree of adherence to logical rules of data structure, attribution and relationships.
Optional
1
Character String
Text
28
Completeness
Presence and absence of features, their attributes and their relationships. Positional accuracy of the data. Accuracy of quantitative attributes.
Optional
1
Character String
Text
29 30
Positional Accuracy Attribute Accuracy
Optional Optional
1 1
Character String Character String
Text Text
G3.3
LEVEL OF SPATIAL DETAIL
Description of the spatial level of granularity or the smallest representative unit associated with disaggregated, statistical data.
Optional
1
Metadata Entity GROUP 3 SUBGROUP 3
LEVEL OF SPATIAL DETAIL
31
Source Scale Denominator
Denominator of the representative fraction on the source map(s) (e.g. on a 1: 50 000 scale map, the source scale denominator value is 50000). It is also the number below the line of a vulgar fraction. If no source map used, enter the number 0. If multiple source map scales were used, enter the Source Scale Denominator of the smallest scale map (largest denominator).
Optional
1
Integer
Integer
32
Ground Scale Distance
The ground sample distance.
Optional
1
Real Number
Real Number
119
33
Imagery or Grid x-Dimension
Name of the X-axis. (Default = Column)
Optional
1
Enumerated List
Row Column Vertical Track Cross Track Line Sample Time
34
Imagery or Grid Raster Cell/Pixel Size (x-Value)
The width of a raster cell expressed in distance units of measure.
Conditional: If X-Value entered then Raster Cell/Pixel Size value must be entered.
1
Real Number
Real Number
35
Imagery or Grid y-Dimension
Name of the Y-axis. (Default = Row)
Optional
1
Enumerated List
Row Column Vertical Track Cross Track Line Sample Time
36
Imagery or Grid Raster Cell/Pixel Size (y-Value)
The height of a raster cell expressed in distance units of measure.
Conditional: If Y-Value entered then Raster Cell/Pixel Size value must be entered.
1
Real Number
Real Number
37
Smallest Administrative Unit
The smallest representative unit associated with disaggregated statistical data.
Optional
1
Character String
Text
120
G4
EXTENTS OF A DATASET (WHERE AND WHEN)
The geographic and temporal extents of the dataset expressed in terms of geographic co-ordinates of a bounding rectangle, bounding polygon, geographic identifiers, vertical heights and time period.
Mandatory
1
Metadata Entity GROUP 4
Any combination of the following five extent options may be used, but bounding rectangle, temporal extents and nations are mandatory.
38
Spatial Reference System used for the Bounding Rectangle/ Bounding Polygon
Name of the spatial reference system used for the geographic co-ordinate extents of a bounding rectangle or bounding polygon.
Mandatory (13)
1
Enumerated List
British National Grid Irish Grid Latitude and Longitude
EXTENTS OF A DATASET WHERE AND WHEN)
G4.1
EXTENTS OF A DATASET BASED ON CO-ORDINATES OF A BOUNDING RECTANGLE
West Bounding Co-ordinate
The geographic coverage of the dataset expressed in terms of geographic co-ordinates of a bounding rectangle.
Mandatory
N
Metadata Entity GROUP 4 SUBGROUP 1
Enter either grid or longitude and latitude values, but not both.
39
Westernmost co-ordinate of a bounding rectangle.
Mandatory (14)
1
Real Number
Grid or Longitude value
EXTENTS OF A DATASET BASED ON THE CO-ORDINATES OF A BOUNDING RECTANGLE
40
East Bounding Co-ordinate
Easternmost co-ordinate of a bounding rectangle.
Mandatory (15)
1
Real Number
Grid or Longitude value
41
North Bounding Co-ordinate
Northernmost co-ordinate of a bounding rectangle.
Mandatory (16)
1
Real Number
Grid or Latitude value
42
South Bounding Co-ordinate
Southernmost co-ordinate of a bounding rectangle.
Mandatory (17)
1
Real Number
Grid or Latitude value
121
G4.2
EXTENTS OF A DATASET BASED ON CO-ORDINATES OF A BOUNDING POLYGON
The geographic coverage of the dataset expressed in terms of geographic co-ordinates of a bounding polygon.
Optional
N
Metadata Entity GROUP 4 SUBGROUP 2
Enter either grid or longitude and latitude values, but not both.
EXTENTS OF A DATASET BASED ON THE CO-ORDINATES OF A BOUNDING POLYGON
43
Co-ordinates of a Bounding Polygon
The set of x and y co-ordinates (first number = easting of a point, second number = northing of a point) that make up the co-ordinates of a bounding polygon.
Optional
N
Real Number
Real Number
G4.3
EXTENTS OF A DATASET BASED ON GEOGRAPHIC IDENTIFIERS
Geographic coverage expressed in terms of geographic identifiers.
Mandatory
1
Metadata Entity GROUP 4 SUBGROUP 3
Any of the national, administrative area, ,postcode district or place name keyword geographic identifiers may be used, though nations is mandatory. England England and Wales Great Britain Northern Ireland Scotland Wales Isle of Man Channel Islands United Kingdom List of Administrative Areas List of Postcode Districts Getty’s Thesaurus of Geographic Names or Ordnance Survey’s 1: 50 000 Gazetteer Search Getty or Ordnance Survey Gazetteers for term(s)
EXTENTS OF A DATASET BASED ON GEOGRAPHIC IDENTIFIERS
44
Nations
Geographic coverage expressed in terms of nations within the British Isles.
Mandatory (18)
N
Enumerated List
45 46
Administrative Areas Postcode Districts
Geographic coverage expressed in terms of administrative areas. Geographic coverage expressed in terms of postcode districts. Name of the controlled vocabulary used as a source for the controlled place name keywords.
Optional Optional
N N
Enumerated List Enumerated List
47
Controlled Place Name Vocabulary
Optional
1
Character String
48
Controlled Place Name Keywords
The geographic name of a location(s) covered by a dataset.
Optional
N
Enumerated List
122
G4.4
VERTICAL EXTENTS OF A DATASET
The vertical extent of the dataset.
Optional Conditional: If value entered for any element in vertical extent group, then value required for Minimum Value. Conditional: If value entered for any element in vertical extent group, then value required for Maximum Value. Conditional: If value entered for any element in vertical extent group, then value required for Unit of Measure. Conditional: If value entered for any element in vertical extent group, then value required for Vertical Datum.
N
Metadata Entity GROUP 4 SUBGROUP 4
If a value is entered for any one element field, then values must be provided for all other element fields in vertical extent group.
49
Minimum Value
Lowest vertical extent contained in the dataset.
1
Real Number
Real Number
VERTICAL EXTENT
50
Maximum Value
Highest vertical extent contained in the dataset.
1
Real Number
Real Number
51
Unit of Measure
Vertical units used for vertical extent.
1
Character String
Text
52
Vertical Datum
The origin from which the elevation values are measured.
1
Character String
Text
G4.5
TEMPORAL EXTENTS OF A DATASET
Time period that the content of a dataset covers.
Optional
N
Metadata Entity GROUP 4 SUBGROUP 5
TEMPORAL EXTENT
53
Start Date for Time Period Covered by Dataset End Date for Time Period Covered by Dataset
The start date of the actual time period the dataset covers.
Optional
1
Date
Date
54
The end dates of the actual time period the dataset covers.
Optional
1
Date
Date
123
G5
CUSTODIAN (WHO)
The organisation or person responsible for the maintenance of the dataset.
Mandatory
1
Metadata Entity GROUP 5
55
Name of Custodian
The name of the organisation or person responsible for the maintenance of the dataset.
Mandatory (19)
1
Character String
Text
56
Postal Street Address of Postal Street part of address for organisation or person Mandatory (20) Custodian responsible for the maintenance of the dataset. Postal City of Custodian Postal County of Custodian Postal Code of Custodian Postal Country of Custodian Postal city part of address for organisation or person responsible for the maintenance of the dataset. Postal county part of address for organisation or person responsible for the maintenance of the dataset. Postal code part of address for organisation or person responsible for the maintenance of the dataset. Mandatory (21)
1
Character String
Text
57
1
Character String
Text
58
Optional
1
Character String
Text
59
Mandatory (22)
1
Character String
Text
CUSTODIAN (WHO)
60
Postal country part of address for organisation or Mandatory (23) person responsible for the maintenance of the dataset.
1
Character String
Text
61
Telephone Number of Custodian
Telephone number of the organisation or person responsible for the maintenance of the dataset.
Optional
1
Character String
Text
62
Facsimile Number of Custodian
Facsimile number of the organisation or person responsible for the maintenance of the dataset.
Optional
1
Character String
Text
63
Email Address of Custodian
Internet email address of the organisation or person responsible for the maintenance of the dataset.
Optional
1
Character String
Text
64
Web Address of Custodian
World Wide Web site Uniform Resource Locator (URL) address for the organisation or person responsible for maintenance of the dataset.
Optional
1
Character String
Text
124
G6
65 66 67 68 69 70 71
DISTRIBUTOR (ACCESS)
Name of Distributor
The organisation or person responsible for the distribution of the dataset.
Mandatory
N 1 1 1 1 1 1 1 1 1 1
Metadata Entity GROUP 6 Character String Character String Character String Character String Character String Character String Character String Character String Character String Character String Text Text Text Text Text Text Text Text Text Text CD-ROM DVD DVD-ROM 3.5 Inch Floppy Disk 5.25 Inch Floppy Disk 7 Track Tape 9 Track Tape 3480 Cartridge Tape 3490 Cartridge Tape 3580 Cartridge Tape 4 mm Cartridge Tape 8 mm Cartridge Tape 0.25 Inch Magnetic Tape Digital Linear Tape Online Satellite Telephone Link Hardcopy Text Real Number
The name of the organisation or person responsible Mandatory (24) for the distribution of the dataset. Distributor Contact Role or position of the responsible person Optional Title for the distribution of the dataset. Postal Street Address of Postal Street part of address for organisation or person Mandatory (25) Distributor responsible for the distribution of the dataset. Postal City of Postal city part of address for organisation or person Mandatory (26) Distributor responsible for the distribution of the dataset. Postal Code of Postal code part of address. Mandatory (27) Distributor Postal Country of Distributor Telephone Number of Distributor Facsimile Number of Distributor Email Address of Distributor Web Address of Distributor Postal country part of address for organisation or person responsible for the distribution of the dataset. Telephone number of the organisation or person responsible for the distribution of the dataset. Facsimile number of the organisation or person responsible for the distribution of the dataset. Internet email address of the organisation or person responsible for the distribution of the dataset. World Wide Web site Uniform Resource Locator (URL) address for the organisation or person responsible for the distribution of the dataset. Mandatory (28) Optional Optional Optional Optional
DISTRIBUTOR (ACCESS)
72 73 74
75
Supply Media
Media format in which the dataset can be supplied.
Optional
N
Enumerated List
76 77
On-line Linkage Dataset File Size
The name of the World Wide Web site or other on-line source that holds the dataset. The estimated size of the dataset file to be transferred.
Optional Optional
N N
Character String Character String
125
G6.1
DATASET NAME AND FORMAT
Dataset Format Name Dataset Format Version
Dataset name and format in which digital data can be provided. Format name in which digital data can be provided (e.g.: DXF, DLG, DBF, MapInfo, IDRISI, ARC/INFO, ERDAS). Format version in which digital data can be provided (e.g. 1.0, 3.1, 8.0). Restrictions and legal prerequisites for accessing or using the dataset.
Mandatory
N
Metadata Entity GROUP 6 SUBGROUP 1
78
Mandatory (29)
1
Character String
Text
79
Mandatory (30)
1
Character String Metadata Entity GROUP 6 SUBGROUP 2
Text
G6.2
ACCESS AND USE CONSTRAINTS
Optional
1
80
Access Constraints
Restrictions and legal prerequisites for accessing the dataset. These include any access constraints applied to ensure the protection of privacy or intellectual property and any special restrictions or limitations on obtaining the dataset.
Optional
N
Enumerated List
ACCESS AND USE CONSTRAINTS
Copyright Patent Patent Pending Trademark Licence Intellectual Property Rights Restricted Other Restrictions Copyright Patent Patent Pending Trademark Licence Intellectual Property Rights Restricted Other Restrictions Text
81
Use Constraints
Constraints applied to ensure the protection of privacy or intellectual property and any specific restrictions or limitations on using the dataset.
Optional
N
Enumerated List
82
Use Constraints Details
Limitations affecting the dataset’s fitness for use.
Optional
N
Character String
83
Other Constraints Details
Other restrictions and legal prerequisites for accessing the dataset.
Optional
N
Character String
Text
126
G7
METADATA CREATOR INFORMATION
Name of Metadata Creator
The organisation or person responsible for creating and updating metadata record(s). The name of the organisation or person responsible for creating and updating the metadata record(s).
Mandatory
1
Metadata Entity GROUP 7
84
Mandatory (31)
1
Character String
Text
85 86 87
Postal Street Address of Postal Street part of address for organisation or person Mandatory (32) Metadata Creator responsible for metadata creation and updates. Postal City of Metadata Creator Postal Code of Metadata Creator Postal Country of Metadata Creator Telephone Number of Metadata Creator Facsimile Number of Metadata Creator Email Address of Metadata Creator Postal city part of address for organisation or person responsible for metadata creation and updates. Postal code part of address. Postal country part of address for organisation or person responsible for the metadata creation and updates. Telephone number of the organisation or person responsible for metadata creation and updates. Facsimile number of the organisation or person responsible for creating and updating the metadata record(s). Internet email address of the organisation or person responsible for creating and updating the metadata record(s). World Wide Web site Uniform Resource Locator (URL) address for the organisation or person responsible for creating and updating the metadata record(s). Unique identifier for the metadata record. Mandatory (33) Mandatory (34)
1 1 1
Character String Character String Character String
Text Text Text
METADATA CREATOR INFORMATION
88
Mandatory (35)
1
Character String
Text
89 90
Optional Optional
1 1
Character String Character String
Text Text
91
Optional
1
Character String
Text
92
Web Address of Metadata Creator Metadata Record Identifier
Optional
1
Character String
Text
93
Optional Conditional: If metadata record is a subset or offspring of an original record, then parent metadata record identifier value should be entered. Mandatory (36) Optional Optional
1
Character String
Text
94
Parent Metadata Record Identifier
Identifier used for parent or original metadata record.
N
Character String
Text
95 96 97
Metadata Last Updated Metadata Standard Name Metadata Standard Version
Date on which the metadata record was last updated. Name of the HFE Profile used. Version of the HFE Profile used.
1 1 1
Date Character String Character String
Date Text Text
127
4.0 Appendix B (Examples) Overview of Examples Section for the UK Academic Geospatial Metadata Application Profile (UK AGMAP)
This section is intended to serve as a supplement to the UK Academic Geospatial Metadata Application Profile (UK AGMAP) Guidelines. These examples should elucidate key UK AGMAP elements for geospatial metadata creators and Go-Geo! Portal users. Referencing these examples should also improve the quality of metadata records if creators are uncertain about specific elements, especially those associated with the quality statement. Where appropriate, examples will be listed under several academic disciplines that are likely to use or create spatial datasets. These include the following:
Archaeology and Anthropology Biological Sciences Civil Engineering Earth Sciences Environmental Sciences Geography, Health Sciences History and Sociology
In addition, some continuity will be imposed on many of the examples presented in this document. Common themes have be applied across examples so that comparisons can be made, thus further expanding examples in a greater context to provide more clarity. The title example, A study of the distribution pattern of Iron Age archaeological sites in south-eastern England, represents a recurrent spatial data theme used for alternative title, topic, description and other elements. In all instances, fictitious examples have been used. Any examples that might exist would be coincidental.
128
Dataset Title examples presented under various academic disciplines (Dataset Title element, Identifier 1)
return to p15
Key points: full-stop not necessary; titles should be comprehensive and include place names associated with the study area of the dataset. Archaeology and Anthropology
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
129
Alternative Dataset Title examples presented under various academic disciplines (Alternative Dataset Title element, Identifier 2) Archaeology and Anthropology
1) Iron Age settlement patterns in south-eastern England 2) Brown’s Farm geophysical survey in Wiltshire, England
return to p16
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
130
Dataset Topic and Definitions List (Dataset Topic, Identifier 10)
Please use the appropriate topic from the left-hand column (titled ‘Name’) Name Definition Rearing of animals and/or cultivation of plants. 1. Farming
return to p 26
[Agriculture; Irrigation; Aquaculture; Plantations; Herding; Pests and Diseases affecting Crops and Livestock] Flora and/or fauna in natural environment. [Wildlife; Vegetation; Biological Sciences; Ecology; Wilderness; Sea Life; Wetlands; Habitat] Legal land descriptions. [Political and Administrative Boundaries] Processes and phenomena of the atmosphere. [Cloud cover; Weather; Climate; Atmospheric conditions; Climate change; Precipitation] 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] Height above or below sea level. [Altitude; Bathymetry; Digital Elevation Models (DEMs); Slope Derived Products] Environmental resources, protection and conservation.
2.
Biota
3.
Boundaries Climatology, Meteorology, Atmosphere
4.
5.
Economy
6.
Elevation
7.
Environment
[Environmental pollution; Waste Storage and Treatment; Environmental Impact Assessment; Monitoring Environmental Risk; Nature Reserves; Landscape] 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 services, human ecology and safety. [Disease and Illness; Epidemiology; Factors affecting Health; Hygiene; Substance Abuse; Mental and Physical Health; Health Services] Base maps. [Land Cover; Topographic Maps; Imagery; Unclassified Images; Annotations] Military bases, structures and activities. [Barracks; Training Grounds; Military Transportation; Information Collection] Inland water features, drainage systems and their characteristics. [Rivers and Glaciers; Salt Lakes; Water Utilisation Plans; Dams; Currents; Floods; Water Quality; Hydrographic Charts] Positional information and services. [Addresses; Geodetic Networks; Control Points; Postal Zones and Services; Place Names] Features and characteristics of salt water bodies (excluding inland waters). [Tides; Tidal Waves; Coastal Information; Reefs] Information used for appropriate actions for future use of the land. [Land-use maps; zoning maps; cadastral surveys; land ownership] 131
8.
Geo-scientific Information
9.
Health Imagery, Base Maps, Earth Cover Intelligence, Military Inland Waters
10. 11.
12.
13.
Location
14.
Oceans Planning, Cadastre
15.
Name
Definition 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] Man-made construction. [Buildings; Museums; Churches; Factories; Housing; Monuments; Shops; Towers] Means and aids for conveying persons and/or goods. [Roads; Airports/Airstrips; Shipping Routes; Tunnels; Nautical Charts; Vehicle or Vessel Location; Aeronautical Charts; Railways] 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]
16.
Society
17.
Structure
18.
Transportation
19.
Utilities, Communication
132
Controlled Keyword examples presented under various academic disciplines (Controlled Keyword element, Identifier 12)
(Selected terms from UNESCO thesaurus)
return to p27
Archaeology and Anthropology
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 133
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
134
Other Keywords examples presented under various academic disciplines (Other Keywords element, Identifier 13)
return to p28
Key point: Keywords not found in the UNESCO thesaurus but corresponding to those provided as examples for Controlled Keyword.
Archaeology and Anthropology
1) GPS, Global Positioning System, Point Coverage, Romans 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
135
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
136
Abstract examples presented under various academic disciplines (Abstract element, Identifier 14)
return to p29
Key point: Abstract text examples correspond to first examples under each discipline for Controlled Keyword and Other Keyword.
Archaeology and Anthropology
This dataset is a point coverage showing the distribution pattern of Iron Age sites in south-eastern England. The dataset was created as part of another study at the University of Edinburgh which examined 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 was quite extensive for this area, based on various field surveys conducted over intermittent periods from 1922 to 2002. Global Positioning Satellite (GPS) was used for mapping sites during field surveys conducted from 2000 to 2002. Sites found during previous field surveys had been plotted on Ordnance Survey maps; these were copied to mylar, scanned and geo-referenced. 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
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 vector 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 displaying estimated hedgehog population densities across Britain.
Civil Engineering
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
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, 137
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
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. Locations of wells were established though contacts with local government agencies; 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
This 1995 Essex land-use classification dataset is derived from a Landsat 5 Thematic Mapper satellite-based image. The satellite captured the image on 19 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 represented as 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
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 ensure an individuals’ privacy.
History
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 twentieth century. The data are sorted at the county level and stored in a tabular format.
Sociology
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, drugrelated 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. 138
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.
139
Example for the Sample element
(return to p77)
(Sample element, Identifier 17) (Figures 1 and 2)
These graphics illustrate how sample graphics of datasets should be submitted for potential users to view. One graphic (Figure 27) uses a watermark and copyright statement to protect the image rights, and in other instances (Figure 28), obscures the dataset sample to ensure that it cannot be used. These samples and text are presented as only an example. The metadata creator or data producer should decide which disclaimers and warnings are most suitable to include and should confer with a consul if deemed necessary.
Figure 1. Example of a dataset sample that provides a watermark and copyright.
Figure 2. Example of a dataset sample providing a superimposed text warning. 140
Related Dataset examples presented under various academic disciplines (Related Dataset element, Identifier 19)
return to p34
Key points: It is recommended that the author-date system (or sometimes called the ‘Harvard System’) format be used for citations. Examples are also provided for other material or media and can be applied to all disciplines. Other datasets, derived from or incorporated into dataset, should be listed.
Archaeology and Anthropology
(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, 2146. (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. 141
2) British Geological Survey’s Digital Geological Map of Great Britain (1980). 1:50 000 (British series; 1456).
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 1280). *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 hypothetical 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.
142
Example for the Dataset Lineage element (Dataset Lineage element, Identifier 25) Key points:
Each lineage source should include the following:
return to p45
Name of data source; Parent/child references may be used to identify primary and derived datasets which have been incorporated into the dataset; Name of each data source’s creator; Scale (UK AGMAP follows ISO 19115, and for the Source Scale Denominator element, only one value is permitted for a dataset’s metadata record); Media or presentation type (e.g.: paper map, mylar map, digital map; report, publication, etc); Temporal extent content (YYYY-MM-DD); Creation or publication date; The purpose or intent of use for the data source (which set of features, which attributes?).
Example of a statement for a Yorkshire County Soil dataset’s lineage. 1. Title: 1970 Yorkshire County Aerial Photography (1:50,000) Source for soil map delineations and special soil feature locations. 2. Title: 1999 National Soil Map (NATMAP) (1:250,000) Source for soil attribution which was collected and classified in 1968. 3. 1925 British Geological Survey (BGS) Geological Map (1:10,000) Source for parent material. 4. The British Geological Survey (BGS) Lexicon of Named Rock Units (1993). Source for Source for information about all allostratigraphical, lithostratigraphical and lithodemic units of member (or equivalent) and higher status that are used, or have been used, on BGS maps and in BGS publications for the UK. It includes information about lesser named units, notably beds (and their equivalents), and some information about names not currently recognised by the BGS or now regarded as obsolete. Some 25% of current Lexicon entries include full definitions, in the BGS context, of formal or informal type. Parent source of the BGS Lexicon of Named Rock Units is the BGS 1:50,000 Geological Maps. 5. LandIS Soil Data Gateway, Cranfield University, http://www.landis.org.uk/gateway/ooi/welcome.cfm Data source for ancillary soil information for Yorkshire.
143
Example for the Description of Dataset Process Steps element (Description of Dataset Process Steps element, Identifier 26)
return to p45
Key points: List dataset processes in steps. It is recommended to identify individuals involved with each of the processing steps, and if possible, contact details for each person should be included. Dataset processing steps should also include dates and software used to process data. Example of a statement for mapping archaeological survey an sites dataset using maps and mylar for transferring data for scanning, conversion and editing. PROCESS Description: Process Step 1: PREPARATION FOR SCANNING: A blueprint paper copy of original Mylar was produced. Archaeological site surveys and site boundaries were highlighted with black and red marker. Four outer coordinate tick marks were highlighted and labelled with numerical geographical reference. (Processing date: 2008-10-15; Contact Name: John Doe; Contact Address: University of Edinburgh, Department of Archaeology). Process Step 2: SCANNING: Blueprint copies, with archaeological surveys extent and site boundaries highlighted, were scanned into raster files. The raster files were converted to vector, creating digital lines. (Processing date: 2008-10-17; Contact Name: John Doe; Contact Address: University of Edinburgh, Department of Archaeology). Process Step 3: CONVERSION: Digital lines were converted to Microsoft ArcInfo 9.2 coverages and then converted to ArcMap 9.2 shapefiles. (Processing date: 2008-10-17; Contact Name: Mary Doe and Tony Mathys; Contact Address: University of Edinburgh, Department of Archaeology). Process Step 4: EDITING: Coverages were sorted first. Scanned images were initially evaluated, separating those that were complete and nearly ready for distribution versus those requiring extensive editing. Editing included: 1. Deletion of polygons not associated with archaeological survey and site boundaries which were present in the digital version. 2. Closing polygons that were open in the digital version. These were mostly attributed to archaeological sites mapped more than once on multiple map sheets. The multiple coverages were joined to create one continuous area where the archaeological surveys were conducted. 3. Joining of individual archaeological survey areas into one contiguous area. 4. Adding pertinent data to the attribute table. Data included was information from the original Ordnance Survey map names used for the surveys: archaeological survey dates; archaeological site types; archaeological sites discovery dates; archaeological sites dates; and catalogue identification number for artefacts collected at sites. The joining of archaeological survey areas created slivers, overlaps and gaps. These were manually removed using ArcInfo 9.2 to edit and subsequently clean the single archaeological survey coverage. (Processing date: 2008-11-13; Contact Name: Mary Doe and Tony Mathys; Contact Address: University of Edinburgh, Department of Archaeology). Example of a statement for a GPS forestry inventory dataset which includes previously collected field data. PROCESS Description: Process Step 1: MS Access database was designed to contain field data. Previous survey data was obtained from Professor John Doe stored in MS Excel spreadsheets. These data were imported into MS Access and appended to database. (Processing date: 2008-03-13; Contact Name: Mary Doe and Tony Mathys; Contact Address: University of Edinburgh, Department of Environmental Sciences). 144
Process Step 2. Missing data was entered into tables through MS Access forms from paper copies or scanned images of original datasheets. (Processing date: 2008-03-15; Contact Name: Mary Doe and Tony Mathys; Contact Address: University of Edinburgh, Department of Environmental Sciences). Process Step 3. Data was proofed by reviewing each data element with the original datasheets by viewing data through MS Access forms. (Processing date: 2008-04-01; Contact Name: Mary Doe and Tony Mathys; Contact Address: University of Edinburgh, Department of Environmental Sciences). Process Step 4. Survey data of plots were collected using a Trimble GPS Pathfinder„ ProXT™ receiver unit. Tree plot locations were collected using real-time corrected European Terrestrial Reference System 89 (ETRS89) enabled GPS readings. A Percent Dilution of Position (PDOP) of 6 or less was applied to 100 position readings which were averaged to create a point location. These positions are believed to be accurate to a submetre level. ArcPad Quick forms were created to collect tree data. Understory data for the 1.0 metre quadrants were captured on paper field forms and entered into the database using the MS Access forms. (Processing date: 2008-06-06; Contact Name: Mary Doe and Tony Mathys; Contact Address: University of Edinburgh, Department of Environmental Sciences). Process Step 5. ArcPad Quick forms were used for digital data collected to attribute plot points. These were imported into the MS Access database and subsequently converted into an ESRI Personal Database; ArcCatalog 9.2 was used for creating the feature class. The feature class attributes for the point locations were appended to the existing tables in MS Access. (Processing date: 2008-06-06; Contact Name: Mary Doe and Tony Mathys; Contact Address: University of Edinburgh, Department of Environmental Sciences). Process Step 6. Data was processed for updating plant identifications to the currently accepted taxonomic nomenclature using the National Biodiversity Network (NBN) Species Dictionary. See MS Access Design View’s tabular field descriptions for more information. (Processing date: 2008-06-06; Contact Name: Mary Doe and Tony Mathys; Contact Address: University of Edinburgh, Department of Environmental Sciences). Example of a statement for a Landsat-derived Land-use dataset’s tabular source. PROCESS Description: The Centre for Ecology and Hydrology (CEH) were responsible for creating this dataset in 2007-04-06 using Landsat Thematic Mapper imagery (bands 3,4, and 5 only), which was captured on 1999-05-10. This Landsat image was classified for a Cumbria land use map using a supervised maximum likelihood classification within ERDAS Imagine software. Process Step 1: Three iterations of classification were typically performed prior to subjecting the data to a comprehensive manually verification and editing process where each classified area was compared with 1:25,000 scale colour, black and white and infrared photography for correct interpretation. Poorly classified areas were recoded or aggregated, as appropriate, at this stage. Transitional feature types (e.g. coniferous, mixed, deciduous forest classes) were handled by first developing a classification using relatively pure samples of individual types and performing a limited classification around a tightly controlled confidence interval. Mixed classes falling outside of the pure class confidence interval were then allowed to fall out into a single mixed class following verification and manual editing processes. Process Step 2: The data were then subject to the ARCINFO Spatial Analyst filtering function NIBBLE to remove road features. NIBBLE uses a Euclidean distance-nearest neighbour algorithm to reassign values to the pixels that originally were assigned road class values. Because the road pixels existed singly or in groups of two, the NIBBLE function effectively reassigned all of these pixels in a single processing pass.
145
Example for the Logical Consistency element (Logical Consistency element, Identifier 27)
Example of a statement for a boundary dataset.
return to p47
Polygons intersecting the neatline are closed along the border. Segments making up the outer and inner boundaries of a polygon tie end-to-end to completely enclose the area. Line segments are a set of sequentially numbered coordinate pairs. No duplicate features exist nor duplicate points in a data string. Intersecting lines are separated into individual line segments at the point of intersection. Point data are represented by two sets of coordinate pairs, each with the same coordinate values. All nodes are represented by a single coordinate pair which indicates the beginning or end of a line segment. The neatline is generated by connecting the four corners of the digital file, as established during initialization of the digital file. All data crossing the neatline are clipped to the neatline and data within a specified tolerance of the neatline are snapped to the neatline. DBFmeta consistency were performed on the dataset’s database. DBFmeta available via this url link. ( http://geology.usgs.gov/tools/metadata/tools/doc/dbfmeta.html ) Example of a statement for a Digital Elevation Model (DTM) dataset derived from a LiDAR survey. Compliance with the accuracy standard was validated by the collection of photo identifiable GPS ground control points during the acquisition of LiDAR. The following checks were performed:
The LiDAR DEM data was checked against the project ground control The technical staff confirmed the accuracy of the points during initial processing Airborne GPS was also utilized during processing
146
Example for the Completeness element (Completeness element, Identifier 28)
Can be a simple statement such as the following: Dataset is topologically correct within ARC/INFO 9.2. or: Data are stored within a valid ARC/INFO data structure.
or: Data are topologically correct using ARC/INFO 9.2. All polygons are closed and lines intersect where intended. Or:
return to p48
Topology for this dataset was built using the ARC/INFO 9.2 CLEAN and BUILD commands. With more detail such as the following: This is a topologically clean dataset; there are no duplicate features. Polygon features begin and end at the same point, contain no overshoots or undershoots, and contain a single label. Initial topology was created by running a CLEAN command in ARC/INFO 9.2 at a fuzzy tolerance of 0.00000000001 and dangle tolerance of 0. ARC/INFO commands, NODEERRORS and LABELERRORS, were used to find any missing or deviant data. Dataset then reviewed manually with ARC/INFO's ArcEdit module, deleting overshoot arcs and verifying complete closure off all intended polygons. After ArcEdit session, topology was rebuilt using the ArcInfo BUILD command. Can pertain to other source data and ground conditions such as the following: Example of a statement for a Wetland Survey in Cumbria. All photo-interpretable wetlands in Cumbria were mapped. In the moors, wetlands greater than 100 m2 were mapped. In forested areas, small open water and emergent wetlands were mapped. In general, the minimum mapping unit is from 1 to 5 hectares depending on the wetland type and the scale and emulsion of the source aerial photography. In regions Cumbria where evergreen forested wetlands predominate, wetlands smaller than 0.5 hectares may not have been mapped, hence, a detailed on-the-ground and historical analysis of a single site may result in a revision of the wetland boundaries established through photographic interpretation. In addition, some small wetlands and those obscured by dense forest cover may not have been included in this dataset.
147
Example for the Positional Accuracy element (Positional Accuracy element, Identifier 27)
Key point: Recommended information to include with a Spatial Accuracy statement. GPS data: the type of GPS equipment (mapping grade, survey grade) settings number of satellites used logging intervals of position, and post-processing techniques (such as differential correction). Maps: RMS (root mean square) error; number of registration points used; Satellite imagery data: final image-to-coverage RMS error number of links used in registration, and the maximum positional offsets. Example of a statement for a Land-use map derived from a Landsat image.
return to p49
The 30 metre source Landsat imagery sampling size automatically introduces a potential offset of this amount. Geo-registration processes would likely introduce an additional 30-60 metres offset. Individual area feature boundaries may exhibit additional offsets of up to 0.5 pixel (15 metres) based on theoretical limitations in image sampling devices. Additional offsets may be present due to a lack of boundary clarity between some classes, edge pixel effects, and image post-processing (smoothing) effects. Example of a statement for a Digital Elevation Model (DTM)dataset derived from a LiDAR survey. The DEM was acquired to meet +/- 1 metre vertical accuracy (RMSE of 0.5 metre - 95% confidence level). This is suitable for rectification of digital ortho-photography and for the creation of 1 and 2 metre contours (with the addition of 3D compiled breaklines). Other examples Estimated accuracies in the X and Y direction of 1 to 20 metres from the true location. The horizontal positional accuracy was tested by verifying the location of the data on-screen relative to the corresponding 1:25,000 Ordnance Survey Colour Raster maps. Horizontal positional accuracy for the digital data is tested by visual comparison of the source with map sources. Enhanced digital data is also snapped to existing boundaries and is compared to adjacent files.
148
Example for the Attribute Accuracy element (Attribute Accuracy element, Identifier 27)
Example of a statement for a Cumbria Land-use dataset derived from a Landsat image.
return to p50
The Cumbria Land use dataset exhibits a per class and overall classification accuracy of not less than 95 percent. Accuracy assessment was conducted using a random, area-based sampling scheme, with the number of samples per class chosen to reflect the relative area occupied by each class within the individual areas being evaluated. Random samples were generated within each dataset for evaluation. Sample areas were then checked against aerial colour infrared photography for correctness within the fixed sample plot. Results of the analysis were plotted in confusion matrices and analysed for conformance to the 95 percent classification accuracy specification. The Centre for Ecology and Hydrology (CEH) staff spot field checked the category of 'young forest/regeneration' against their forest inventory data, and this resulted in ascertaining that data were 100 percent accurate. Example of a statement for a Wetland Survey in Cumbria. Statistically valid attribute accuracy information is not available for this dataset. Attribute accuracy was tested (during production) by manual comparison of the source with hard copy printouts and/or symbolised display of the digital wetlands data on an interactive computer graphic system. In addition, DBFmeta tests were applied to these attributes against a master set of valid wetland attributes. Anecdotal information through use by Centre of Ecology and Hydrology (CEH) staff suggests that attribute information for this data set becomes less reliable in the smallest delineations. DBFmeta available via this url link. ( http://geology.usgs.gov/tools/metadata/tools/doc/dbfmeta.html )
149
Example for the Source Scale Denominator element (Source Scale Denominator element, Identifier 31) (Figure 3 and Figure 4)
return to p51
Maps 1 and 2 (Figures 2 and 3) on pages 147 and 148 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.
150
Figure 3. Example of scale and metric distance between points on Scale Map 1
151
Figure 4. Example of scale and imperial distance between points on Scale Map 2
152
Examples for the Imagery or Grid Raster Cell/Pixel Size X- and Y-Value elements (Raster Cell/Pixel Size X and Y - Value elements, Identifiers 34 and 36) (Figures 5 to 10)
return to p54
Raster refers to datasets that are made of rows and columns of cells. Each cell contains a value, and groups of cells sharing the same value can represent a geographic feature. Typically, raster datasets are geo-referenced and store co-ordinate information. Raster cells can also be referred to as pixels. Another term used for raster data is grid, which is commonly associated with equally sized square cells that are also arranged in rows and columns. Again, each cell contains an attribute value. Typically, remotely sensed imagery and digital elevation model (DEM) are considered raster or grid-based datasets. In terms of the level of spatial detail, or resolution, the x- and y-values of a single cell are entered into the respective x and y value element fields. There is one value for the x length (column) of the cell and another for the y length (row). Most raster datasets contain this information in their metadata or purchase order. A number of satellite imagery products have standard grid cell sizes; the same holds true for a digital elevation models (DEM). Landsat 5 and 7 satellites provide multi-spectral imagery with 30 x 30 metre cells, though it is important to note that Landsat 7’s panchromatic images have 15 x 15 metre resolution and its thermal band resolution measures at 60 x 60 metres. A standard DEM dataset has grid cell sizes of 30 x 30 metres, though LIDARderived DEM datasets can have a grid size of 1 metre. It should be noted that high and low resolutions indicate the amount of detail that can be seen in an image. A high resolution image, often associated with low flying aerial photographs or new generation satellites, provides sub-metre resolution. Ground objects of that size can be articulated and seen in a photograph because each cell or pixel captures more detail. An image with sub-metre resolution would enable a user to see individual cars and probably people. Conversely, a low resolution image would not offer the same detail. The thermal band of Landsat 7 measures at 60 x 60 metres, which surely means that a car would not be seen. Ground objects would need to cover an area of 60 x 60 metres or more in order to be distinctive and identifiable; any object smaller than that could not be identified. The purpose of this band is to measure heat that is emitted from the earth and is not to be used for mapping surface features. The difference in cell size can also affect accuracy. The larger the area that a cell covers, the more uncertain it is about the values within it. A 30 x 30 metre DEM has only one elevation value for an area of 900 square metres. It might be best explained that the value represents an average for the area. An average for an area this size would not account for the presence of a narrow ditch measuring two metres wide. A 1 x 1 metre DEM would provide the resolution or cell size to capture this ditch feature and provide elevation values for it. If uncertain about the cell size/resolution, one option is to use a measurement tool and zoom function to determine the x and y values; most GIS and CAD software packages have these capabilities. The two sets of raster images (Figures 5 to 10) introduce the nature of image resolution and cell size for this measurement. The first set of images (Figures 5 to 8) show a Landsat 7 satellite multi-spectral image. It has a 30 x 30 metre resolution (Figure 8), hence the x and y values are the same measurements. The last two images (Figures 9 to 10) represent a 30 x 30 metre digital elevation model (DEM); again resolution and cell size are one the same at 30 x 30 metres (Figure 10).
153
€U.S. Geological Survey EROS Data Center
Figure 5. Landsat Image (30 x 30 metre resolution) at full extent and no evident pixellation.
€ U.S. Geological Survey EROS Data Center
Figure 6. Landsat Image, in closer with pixellation effect becoming apparent.
154
€ U.S. Geological Survey EROS Data Center
Figure 7. Landsat Image, in closer with further pixellation.
€ U.S. Geological Survey EROS Data Center
Figure 8. Landsat Image (30 x 30 metre resolution) and the x- and y-values of a cell.
155
€ U.S. Geological Survey EROS Data Center
Figure 9. Digital Elevation Model (30 x 30 metre) with pixellation effect becoming apparent.
€ U.S. Geological Survey EROS Data Center
Figure 10. Digital Elevation Model (30 x 30 metre) and the x- and y-values of a cell.
156
Example for the Smallest Administrative Unit element (Smallest Administrative Unit element, Identifier 37) (Figures 11and 12 )
return to p57
The Smallest Administrative Unit element is selected when a dataset of a study area has no spatial reference system, and thus no means to measure scale. A typical example is a survey conducted with the use of a paper map that provides survey unit boundaries. These units can be postcodes, wards, counties, or whatever area that defines the smallest representative unit associated with disaggregated data. In this situation too, the captured data are stored in a database or copied to a paper map, with a value written inside each polygon on the map. In these instances it certainly might be possible to calculate the scale by measuring two points on a map and then acquiring the actual real world distance. For the purposes of this element, maps will be presented with the assumption that the user doesn’t want to calculate scale, but would rather use a distinctive administrative unit. These maps (Figures 11 and 12) provide two examples of representative administrative units that could be entered as values in the Smallest Administrative Unit element’s field. The first shows a block of 10 regions (Figure 12) which constitutes a study area (Nation A). Each region represents a separate sampling unit within the survey or study area. It is at this level the data are collected separately or are considered disaggregated. For this example, ‘Region’ would be the value entered in the Smallest Administrative Unit element’s field. The latter map (Figure 12), provides another example, but in this case, postcode districts represent the smallest administrative units. There are 12 postcode districts associated with administrative area 3, which represents the study area, and each postcode district is a sampling unit. ‘Postcode district’ would be the value entered in the Smallest Administrative Unit element’s field.
Figure 11. First example showing regions as the smallest administrative units.
157
Figure 12. Second example showing postcode districts as the smallest administrative units.
158
Examples for the West, East, North and South Bounding Co-ordinate elements return to p60 (West, East, North and South Bounding Co-ordinate elements, Identifiers 39, 40, 41 and 42) (Figure to ) Defining the extent of a dataset
This map (Figure 13) defines the western, eastern, northern and southern-most points of a study area which corresponds to England using the British National Grid reference system. The first step is to open and view the study area and find the points representing the farthest extents. Once these have been located, as demonstrated on the map with arrows, the values can be calculated using several methods. Many GIS software packages display co-ordinate values as the cursor moves across the screen display of the map or points at a specific location. Usually the co-ordinate values appear in a box alongside the margins of the software program. GIS software packages can also provide extent values under relevant menu options (See: Figure 16).
Figure 13. Definition of the system of spatial referencing and British National Grid System extents. The next map (Figure 14) provides an example of the values acquired, which are presented in metres. It is important to keep in mind that one value is needed for each extent point. Any cursor point on the screen will display two values. One will be associated with an x-grid value and the other the y-grid value. The x-value will apply to the horizontal range across the screen and y-value to the vertical. Moving the cursor one way or the other will verify this as the x- or y-grid numbers will increase or decrease. If the unit of measures are within the ranges of page sizes, then the map hasn’t been geo-referenced and those values will not provide a real-world extent, but only that of the monitor screen. The aforementioned details also assume that the map hasn’t been rotated, which means that the top of the screen is north. The British Nation Grid System values can be entered to the nearest metre into the respective element fields. British National Grid will always be expressed as positive values as well. This is based on the OSGB36 159
(Ordnance Survey Great Britain 1936) datum which has a false origin (0,0) in the Atlantic Ocean near the Isles of Scilly off the coast of Land’s End in Cornwall. Here are the expressed values in metres and co-ordinates for West Bounding Co-ordinate = 134,447.6 East Bounding Co-ordinate = 653,907.4 North Bounding Co-ordinate = 657,392.5 South Bounding Co-ordinate = 13,261.7 or: 134447 or: 653907 or: 657392 or: 13261
Figure 14. Display of the British National Grid System extent values. This next map (Figure 15) is based on the geographic co-ordinate system or latitude and longitude, which accounts for the compressed appearance of the study area (England) in comparison to previous maps projected to the British National Grid system (Transverse Mercator). The latitude and longitude system would need to be entered in the System of Spatial Referencing by Co-ordinates (identifier 38) element field. Again, the same approach is used to capture the co-ordinates for the extent points. Here again the extent points don’t change despite the type of co-ordinate system used. The shape of the study area has changed, but it is still at the same location on the earth’s surface. These variations in shape account for different types of projections that are used to adjust two-dimensional maps to the three-dimensional curvature of the earth and reduce distortion. The British National Grid uses a Transverse Mercator projection. As with the British National Grid co-ordinates, the cursor can be pointed to the extent points of the study area. There will be again two sets of numbers that correspond to parallel degrees latitude and meridian degrees longitude. Degrees longitude will be associated with the horizontal and degrees latitude for the vertical. The 160
values are presented in terms of degrees minutes and seconds. Longitude degrees west are expressed as -5† 42’ 41.8’ represent -5 degrees 42 minutes and 41.8 seconds. The element requires that this expression of fractional parts of a degree must be converted and entered in decimal degrees and to the nearest hundredth of a degree (0.01). Converting this can be done with the following equations: Decimal degrees (Positive numbers) = degrees + (minutes/60) + (seconds/3,600) Decimal degrees (Negative numbers) = degrees - (minutes/60) - (seconds/3,600) The following example demonstrates how longitude degrees west and other values are converted: -5† 42’ 41.8” 1† 44’ 52.3” 49† 58’ 35.8” 55† 49’ 24.5” -5 + 42/60 + 41.8/3600 = -5 - 0.7 - 0.0116 = -5.711 decimal degrees (dd) 1 + 44/60 + 52.3/3600 = 1 + 0.733 + 0.014527 = 1.747 decimal degrees (dd) 49 + 58/60 + 35.8/3600 = 49 + 0.966 + 0.00994 = 49.976 decimal degrees (dd) 55 + 49/60 + 24.5/3600 = 55 + 0.816 + 0.006805 = 55.822 decimal degrees (dd)
Figure 15. The geographic extent values in degrees, minutes and seconds. The internet also provides links to numerous web sites with converters. Any internet search engine should locate them. Though not an endorsement, the Nearby.org.uk website http://www.nearby.org.uk/ provides converters.
161
A much easier solution to acquiring the co-ordinate values of a dataset’s extent is to use GIS software packages. IDRISI Kilimanjaro (Figure 16) allows the user to zoom to a select area of a dataset visible in the display window. The user can open ‘Map Properties’ and read the co-ordinate values representing the extent visible in the ‘Current View’. Other GIS software packages contain similar features, though it is important to determine which reference system is used to ensure that the corresponding reference system has been selected for UK AGMAP element 38 (Spatial Reference System used for Bounding Rectangle/Polygon). The UK AGMAP profile supports British National Grid, Irish Grid and latitude/longitude (geographic) reference system.
€ 2007 Clark Labs
Figure 16. Acquiring a dataset’s geographic extent values from a GIS software package (IDRISI Kilimanjaro)
162
Greenwich Prime Meridian
Another critical issue that needs to be addressed with regards to geographic co-ordinates is the Greenwich Prime Meridian, which runs through the heart of London and of course Greenwich (Figure 17).
Figure 17. The Greenwich Prime Meridian. Parallels of latitude and Meridians of longitude form the Geographic Reference System. This system treats the globe as a sphere or spheroid. The sphere is divided into 360 equal parts called degrees. Each degree can be further subdivided into 60 minutes, each composed of 60 seconds. The standard origin is where the Greenwich Prime Meridian intersects the Equator and divides the globe into four quadrants: northwest, northeast, southwest and southeast. All points are positive north of the Equator and east of the Prime Meridian, and negative south of the Equator and west of the Prime Meridian. For the purposes of the United Kingdom, it is important to keep in mind that the degrees longitude for any study area extent east of the Greenwich Prime Meridian will be positive and any to the west will be negative. As it appears on the map, much of the United Kingdom lies to the west of the Meridian. Regarding degrees of latitude, all values are positive for the United Kingdom.
The Bounding Box
The co-ordinate values for the west, east, north and south extents generate a bounding box that defines the maximum extent of a dataset’s study area (Figure 18). This bounding box includes the entire study area as well as an extraneous zone (diagonal lines) that falls between the study area and the bounding box limits. Any spatial searches conducted would include all information wholly inside the bounding rectangle and not be restricted to the study area. This could mean that more information or metadata records will come back during any queries made to this study area. A user may wish to acquire additional information or datasets associated specifically with this area. A better and more effective means to define a study area is with a bounding polygon, which represents all the x- and y- co-ordinates of the study area’s actual boundary and not four points. 163
Figure 18. The extents of a bounding rectangle.
The co-ordinates of a bounding rectangle will be displayed on the Go-Geo! portal’s metadata results page under the ‘Where/When’ tab (Figure 19). This tab will also include two generalised maps that show the bounding box in relation to the study area (large scale map on Where/When tab’s the bottom left) and its location in the United Kingdom (small scale map on the Where/When tab’s bottom right).
164
Figure 19. Example of a metadata record presented on Go-Geo!, displaying the bounding rectangle extent of the English Registration Counties, 1881 dataset. (€EDINA)
165
Example for the Bounding Polygon element return to p64 (Co-ordinates of a Bounding Polygon elements, Identifiers 43) (Figures 20 to 24)
These are examples (Figures 20 and 21) of a study area’s bounding polygon, which for purposes of spatial queries, discovers metadata or datasets specific to the study area. The x and y co-ordinates are provided for points along the boundary as illustrated in the lower map (Figure 20). Because it entails considerable time to collect so many x- and y- values, a tool will eventually be introduced that captures these values. The values will be stored internally in the Go-Geo! portal’s database, but not be presented in the metadata file other than as a part of a map display, as demonstrated for the co-ordinates of a bounding rectangle (Figure 19). Some GIS software packages can also export these values.
Figure 20. A study area’s bounding polygon with x- and y-co-ordinate points presented.
Figure 21. A close zoom window view of a study area’s co-ordinate points of a bounding polygon. 166
Another simplified solution to capturing x- and y- co-ordinates of a bounding polygon is to collect co-ordinate values for selected points around a study area (Figures 22 and 23). This approach doesn’t provide the precision of the actual study area boundary, but it defines an extent that corresponds to the study area’s shape. This eliminates the additional area that the bounding rectangle creates (Figure 24).
Figure 22. Example of simplified polygon extent of a dataset’s study area using x- and y co-ordinate values from 15 points.
Figure 23. Example of polygon extent based on a study area’s shape using the x- and y co-ordinate values.
167
Figure 24. Example of bounding shape polygon and rectangle showing differences between extent ranges.
168
Example for the Spatial Referencing by Geographic Identifiers for Nation, return to p66 Administrative Areas and Postcode Districts elements (Nation, Administrative Areas and Postcode Districts elements, Identifiers 44, 45 and 46)
(Figures 25 to 27) The following maps (Figures 25, 26 and 27) provide an example of geographic identifiers used to define the geographic extent of a study area. There are two possible approaches to entering the extents of geographic identifiers. One option is to select only one level of geographic identifiers to define the extents. The second option can take a hierarchical approach that uses all levels of geographic identifiers to define the extent a dataset’s study area. The latter option is probably preferable for defining the extents of small study areas, especially if they’re associated with different levels or types of geographic identifiers. Using only one level or type of geographic identifier would mean excluding the other two options. If a value for nation were entered then administrative area and postcode district would be excluded). As an example, if a study area represents an entire nation, as illustrated below (Figure 25), ‘Nation A’ would be entered as a value. In this same illustration, if the study area were to extend into any portion of ‘Nation B’, then that would be included as well. As it stands with this example, all of ‘Nation B’ would be considered part of the study area even if only a portion were covered.
Figure 25. Example showing a study area that uses a nation for a geographic identifier.
If it were such that administrative areas were used to define study area units, then all of the administrative areas of ‘Nation A’ and those only covering the portion of ‘Nation B’ would be entered as values. Taking this approach would require more entries than at the nation level. As presented in the next map (Figure 256, there are 10 administrative areas in ‘Nation A’. Each area would need to be entered as a value, so this would require 10 values as opposed to one. The benefit is that if administrative areas were used in for study area units in an 169
adjacent nation, again ‘Nation B’ as an example, this would provide an extent that is more accurate than that at the nation level. The same would apply if postcode districts are used to define the extent; however, this would mean entering more values than would have been expected at the nation or possibly administrative area level depending if the areas represent counties, wards or other level. If a study area assumes collecting data within only one administrative area level, the next map (Figure 26), demonstrates this approach. Here, ‘Nation A’ is divided into 10 administrative areas. The study area in this case is confined to Administrative Area 3, so this is the value that would be entered in the Administrative Area element’s field. Again, if the study area is expanded to include adjacent administrative areas, such as Administrative Area 1 and Administrative Area 2, then those too would be entered as values in the Administrative Area element’s field.
Figure 26. Example showing a study area that uses an administrative area for a geographic identifier.
The last map (Figure 27), provides an example for postcode district extents. This map indicates that within Administrative Area 3, there are 13 postcode districts. If the assumption is that all these postcodes comprise the study area, the value entered would be Administrative Area 3 in the Administrative Area element’s field. If the study area covers only postcode districts CO1, CO2, CO3 and CO4, these values would be entered in the Postcode District element’s field.
170
Figure 27. Example showing a study area that uses postcode districts for a geographic identifier. Reverting back to paragraph two, a second, hierarchical option was recommended, and one that is especially suited to address different the situation when different geographic identifier levels are used to define one study area’s extent. This would entail the use of any combination of geographic identifiers to define the extent. Using the three previous maps (Figures 24, 25 and 26), as an example, the following values would be entered into the respective Nation, Administrative Area and Postcode District element fields if a study area comprised the 13 postcode districts (Figure 26). Element Nation = Value Nation A
Administrative Area = Administrative Area 3 Postcode District = CO1, CO2, CO3, CO4, CO5, CO6, CO7, CO8, CO9, CO10, CO11, CO12, CO13
171
Example for the Minimum and Maximum Value elements return to p71 (Minimum Value element, Identifier 49 and Maximum Value, Identifier 50) (Figures 28 to 30)
The following 3D model displayed below (Figure 28) represents the full extent of the dataset’s study area. The approximate locations of the highest and lowest vertical extents can be determined with visual inspections of this image though the highest peak is more prominent in comparison to other peaks whereas the lowest point isn’t as apparent.
Figure 28. Example showing a 3D terrain model displaying the highest and lowest vertical extents.
GIS software packages can also provide vertical extent values in databases and graphs. An example of this is the Clark Lab’s IDRISI Kilimanjaro edition (Figures 29 and 30). The first screenshot presents a value selected in the DEM’s blue area representing the lowest terrain. The lowest value for the vertical extent of this dataset is 2.3 metres. The histogram also presents the range of values and includes a ‘Summary Statistics’ for the dataset, which includes the 2.3 metres value. Clicking the dark red area of the DEM on display displays the highest value for the vertical extent of the dataset, which is 62 metres. Again, the ‘Summary Statistics’ for the dataset presents the same value of 62 metres.
172
€ 2007 Clark Labs
Figure 29. Example showing a 3D terrain model displayed in Kilimanjaro showing the lowest vertical extent value.
€ 2007 Clark Labs
Figure 30. Example showing a 3D terrain model displayed in Kilimanjaro showing the highest vertical extent value. 173
5.0 Glossary and References
Academic Geospatial Metadata Application Profile (UK AGMAP) UK AGMAP is a template designed to support the documentation and discovery of spatial datasets within UK Higher and Further Education. UK AGMAP also serves as a metadata element field template for the Go-Geo! portal and GeoDoc metadata editor tool. UK AGMAP includes 97 elements which provide information about the when, where, how and what of a dataset, its access and use conditions and the metadata record itself. UK AGMAP is available via the Go-Geo! portal’s homepage. http://www.gogeo.ac.uk ANZLIC ANZLIC is the Spatial Information Council’s joint initiative of the Australian Government, the New Zealand Government and the governments of the States and Territories of Australia. ANZLIC's role is to facilitate easy and cost effective access to the wealth of spatial data and services provided by a wide range of organisations in the public and private sectors. ANZLIC has been at the forefront with the mapping of its geo-spatial metadata standard to ISO 19115. http://www.anzlic.org.au/index.html Association for Geographic Information (AGI) The AGI plays a pivotal role in developing and promulgating geographic information policy in the UK so as to maximise the use of geographic information for the benefit of the country. The AGI also manages the GIgateway„ data locator web site, a gateway service for the data discovery. It is also maintains the current GIgateway„ Discovery Metadata Specifications (previously known as the National Geospatial Data Framework (NGDF)), a geo-spatial metadata standard for the UK. This standard was a derivative of both the ANZLIC and FGDC standards. http://www.agi.org.uk/ Content Standard for Digital Geospatial Metadata (CSDGM) It was created by the Federal Geographic Data Committee (FGDC) to provide a common set of terminology and definitions for the documentation of digital geo-spatial data. The standard establishes the names of data elements and compound elements (groups of data elements) to be used for these purposes, the definitions of these compound elements and data elements, and information about the values that are to be provided for the data elements. http://www.fgdc.gov/ DDI (Data Documentation Initiative) The Data Documentation Initiative (DDI) is an effort to establish an international criterion and methodology for the content, presentation, transport, and preservation of "metadata" about datasets in the social and behavioural sciences. Metadata (data about data) constitute the information that enables the effective, efficient, and accurate use of those datasets. DDI is written in eXtensible Markup Language, or XML. The Data Documentation Initiative (DDI) is mapped to Dublin and is essential for the content, presentation, transport and preservation of metadata about datasets in the social and behavioural sciences. Elements were recently added and approved for defining the geographical extents of a study area using co-ordinates of a bounding rectangle or polygon. These will tie into both the FGDC and ISO 19115 standards. http://www.icpsr.umich.edu/DDI/ Dublin Core (ISO 15836) A metadata element set that is specifically designed to describe digital resources. There are fifteen elements in total (e.g., Title, Creator), which you can qualify with sub elements. It can be used as descriptive metadata to describe objects, containers, and collections. The ISO 19115 has been mapped to Dublin Core under the auspices of the European Committee for Standardization (CEN) and the Information Society Standardization System (ISSS). Elements to define the geographic extent of a dataset are also being added in 2006. http://www.dublin.org e-Government Metadata Standard (e-GMS) The e-Government Metadata Standard (e-GMS) provides the list of elements and refinements used by the UK public sector to create metadata for information resources. It also gives guidance on the purpose and use of each element. This standard is also mapped to Dublin Core. http://www.purl.oclc.org/net/e-GMS_v2 174
EUROGI the European Umbrella Organisation for Geographic Information EUROGI was established at the end 1993 as an initiative of the European Commission. Its mission is to maximise the effective use of geographic information for the benefit of the citizen, good governance and commerce in Europe to represent the views of the geographic information community to promote, stimulate, encourage and support the development and use of geographic information and technology. http://www.eurogi.org/index_1024.html Federal Geographic Data Committee The FGDC is the authoring body of the Content Standard for Digital Geospatial Metadata (CSDGM). It also promotes the co-ordinated development, use, sharing, and dissemination of geographic data. It is composed of representatives from the Departments of Agriculture, Commerce, Defence, Energy, Housing and Urban Development, the Interior, State, and Transportation; the Environmental Protection Agency; the Federal Emergency Management Agency; the Library of Congress; the National Aeronautics and Space Administration; the National Archives and Records Administration; and the Tennessee Valley Authority. Additional Federal agencies participate on FGDC subcommittees and working groups. The Department of the Interior chairs the committee. FGDC subcommittees work on issues related to data categories coordinated under the circular. Subcommittees establish and implement standards for data content, quality, and transfer; encourage the exchange of information and the transfer of data; and organize the collection of geographic data to reduce duplication of effort. Working groups are established for issues that transcend data categories. http://www.fgdc.gov/ Go-Geo! Portal A simple online interface designed to be used as a tool for UK academia to run queries to discover spatial datasets. The portal enables searching by the use of various options including free text, date, resource type and geographic location. http://www.gogeo.ac.uk/ IGGI (Intra-governmental Group on Geographic Information) The Intra-governmental Group on Geographic Information was established in 1993 following the Chorley Report, to enable departments to liaise effectively and exchange best practice for geographic information. IGGI’s mission is to increase the efficiency of central government while enabling it to meet its responsibilities for provision of geographic information to the general public. http://www.iggi.gov.uk/about_iggi/iggi.htm INSPIRE (Infrastructure for Spatial Information in Europe) INSPIRE is a recent initiative launched by the European Commission and developed in collaboration with Member States and accession countries. It aims at making available relevant, harmonised and quality geographic information to support formulation, implementation, monitoring and evaluation of Community policies with a territorial dimension or impact. http://inspire.jrc.it/home.html ISO (International Organization for Standardization) A worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject, for which a technical committee has been established, has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electro-technical Commission (IEC) on all matters of electrotechnical standardisation. http://www.iso.ch ISO 19115 International Metadata Standard This International Standard, adopted March 2003, defines the schema required for describing geographic information and services. It provides information about the identification, the extent, the quality, the spatial and temporal schema, spatial reference, and distribution of digital geographic data. A separate ISO 19139 Dataset Implementation Model and Schema is currently being developed and is anticipated to be released during the 175
first quarter of 2006. As it stands, European countries are developing a profile of ISO 19115 and Canada, Mexico and the US will collaborate to create a North American profile. http://www.iso.ch GIgatewayÄ - Geographic Information Gateway GIgateway„ is a web service aimed at increasing awareness of and access to geospatial datasets and geographical information in the UK. Funded by the Government through the National Interest Mapping Services Agreement (NIMSA), GIgateway„ is a not-for-profit service set up specifically to address GI industry wide problems. AGI currently contracts with Ordnance Survey for the delivery of this program. http://www.gigateway.org.uk National Geospatial Data Framework (NGDF) The National Geospatial Data Framework (NGDF) was a name given to the geo-spatial data infrastructure of the United Kingdom. This initiative aimed to improve awareness and access to geo-spatial information and encourage its wider use. The NGDF’s mission was to encourage greater awareness of data availability and improve access to it, expand the market for geospatial information, assist with data integration leading to more practical solutions to everyday problems to avoid data duplication, make people aware of what geo-spatial data was available, improve methods of data management and fill the gaps in the market place for data supply where none existed. The NGDF evolved into the askGIraffe service, with GIgateway„ superseding it in 2004. http://www.agi.org.uk/ Open Geospatial Consortium OGC is an international industry consortium of 308 companies, government agencies and universities participating in a consensus process to develop publicly available geo-processing specifications. Open interfaces and protocols defined by OpenGIS„ Specifications support interoperable solutions that "geoenable" the Web, wireless and location-based services, and mainstream IT, and empower technology developers to make complex spatial information and services accessible and useful with all kinds of applications. http://www.opengeospatial.org/ Portal A portal is a network service that brings together content from diverse distributed resources using technologies such as cross searching, harvesting, and alerting, and collate this into an amalgamated form for presentation to the user. This presentation is usually via a web browser, though other means are also possible. For users, a portal is a, possibly personalised, common point of access where searching can be carried out across one or more than one resource and the amalgamated results viewed. Information may also be presented via other means, for example, alerting services and conference listings or links to e-prints and learning materials. For more information about portals in academia, please visit the JISC web site. http://www.jisc.ac.uk/ SGML: Standard Generalized Markup Language A standard framework, defined in ISO 8879, for defining particular text markup languages. The SGML framework allows for mixing structural tags that describe format with the plain text content of documents, so that fancy text can be fully described in a plain text stream of data. UK GEMINI The UK GEMINI Discovery Metadata Standard is a defined element set for describing geo-spatial, discovery level metadata within the United Kingdom. The profile is the result of a year-long collaboration between the Association for Geographic Information (AGI) and the e-Government Unit, with additional representation from national and local government, and the academic community, including EDINA. The UK GEMINI document is available for download at UK GovTalk website. An INSPIRE- compliant version (UK GEMINI 2) should be released during the summer of 2009. http://www.govtalk.gov.uk/schemasstandards/metadata_document.asp?docnum=903 XML: eXtensible Markup Language A subset of SGML constituting a particular text markup language for interchange of structured data. The Unicode Standard is the reference character set for XML content. (See also SGML) XML is a trademark of the World Wide Web Consortium. 176
6.0 Bibliography
Federal Geographic Data Committee. (1998). Content standard of digital geospatial metadata, version 2, 1998. Washington, D.C.: Federal Geographic Metadata Committee. ISO 19115 Geographic Information Standard http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=26020 National Geographic Data Framework Management Board. (2000). Discovery metadata guidelines, version 1.2. Southampton: National Geographic Data Framework Management Board. UK GEMINI Spatial Data Discovery Standard http://www.govtalk.gov.uk/schemasstandards/metadata_document.asp?docnum=903
177