Rhode Island Geographic Information System Data --- RIGIS Data

Metadata Standards and Specifications

For The

Rhode Island Geographic Information System

October, 1993

Data Set Documentation For Spatially Related Information
Contained in the RIGIS Data Base
RI Department of Administration
Division of Planning - RIGIS
One Capitol Hill
Providence, RI 02908-5872

I. INTRODUCTION:

The RIGIS and Its Database - The Rhode Island Geographic Information System is a consortium of public and private organizations working together to further the development of and share the tools available from geographic information system and automated mapping technology. The duties and functions of its major participants are outlined in Rhode Island Public Law, Chapters 42 and 16. The RIGIS database is a assemblage of spatially related information which has been developed or collected by its participants. These data have been contributed into a common resource, collectively held by the University of Rhode Island. The contents of this database are made available through a licensing and distribution system to any and all requesters. Need for Metadata Standards - Data documentation for both indexing and assessment of quality and characteristics is referred to as metadata. It is sometimes termed as "data about data". Without this information, the value of data derived from varied sources and shared among several parties lessens. This is especially true when dealing with complex sets of digital data such as are included in geographic information spatial data bases. Information from the RIGIS data base is widely employed by a variety of users both within and outside the system. Therefore, the presence of metadata is considered essential. Standards for RIGIS metadata provide consistent and comprehensive documentation for all RIGIS data sets and coverages. These metadata include delineation of the content, spatial characteristics, attribute listings, sources and origins and lineage of individual data sets.

Return to Index

II. PURPOSE:

To establish metadata standards for RIGIS participants, and foster their implementation. These standards will apply to all individual data set coverages contributed to and included in the RIGIS database.

To provide specifications for data entry into a standardized metadata format for information in the RIGIS database.
To provide educational and interpretive guidelines for users of these data in their entry and application.

*In the formulation of metadata as detailed in these standards, there is no intent to fully substitute this information for, or eliminate requirements for full documentation on data set development or maintenance. Written reports or logged and recorded automated procedures are essential in the normal development or data, and should be continued to be required.

Return to Index

III. STANDARDS:

Presence and Implementation of Metadata:

Each individual data set coverage in the RIGIS database will contain metadata entries conforming with the listed specifications of this document. It will be the obligation of the organization with custodial responsibility for maintaining the data set to also maintain the metadata listing.
Metadata for all newly developed or acquired data set coverages will be completed prior to their acceptance into the RIGIS database. It is the obligation of the organization developing or sponsoring the submission of a data set coverage to ensure that contained metadata meets these RIGIS standards.

Metadata File Names:

Metadata files for data sets or coverages included in the RIGIS database will have file names consisting of the RIGIS-CAT-ID identification code, (see Appendix A), with a three character *.met or *.doc file name extension. For metadata files generated with relational data base management software, file name extensions common to that software are permitted, but must be clearly identified in transfer documentation and related correspondence.

Metadata File Format:

Metadata for each data set coverage will be in a computer automated format in ASCII text, or relational database management system field/record format. The automated format will be specified by the party developing the data and completing the automated tabulation of the metadata file. For those organizations which do not have the technical capability to produce automated records, metadata may be submitted in the form of hard copy text. However, it will remain the responsibility of the RIGIS participant, which automates those data for inclusion into the RIGIS database, to complete the automated entry of submitted textual metadata information.*

Transfer of Metadata:

Metadata for each individual data set coverage will accompany those data at the time of transfer between RIGIS participants, their clients, or to licensed requesters outside the RIGIS. It shall be the responsibility of the party originating the transfer of RIGIS data to ensure that the metadata file(s) accompanies each RIGIS data set or coverage being transferred. The metadata file(s) will accompany the data files distributed on the media used in the exchange of data, and/or as hard copy accompanying other documents involved in each transfer.

*(The RIGIS (RIDOA/DoP) has developed a program for incorporating metadata within the ESRI ARC/INFO** (c) files used on UNIX based workstations. The resulting metadata files are readable by microcomputer users with MSDOS operating systems employing relational data base management software capable of reading or converting *.dbf files.)

** ARC/INFO is a registered trademark, and copyrighted product of the Environmental Systems Research Institute of Redlands, CA.

Return to Index

IV. SPECIFICATIONS:

Field or item entries in the metadata file attached to each RIGIS data set coverage will conform to the minimum line entry specifications as delineated in this document. These entries are separated into five general subject type blocks, covering:

Identification and Description (items 1-12)
Spatial Features and Geographic Parameters (items 13-23)
Relational Database and Attribute Information (items 24-28) Information regarding field or item information (items 24-28) should be included and repeated for each significant field or item in the relational data base or associated table. In data sets or coverages where the number of significant fields exceeds six (6) items, it is recommended that a separate relate or look up table be generated and listed in item 28 line.
Data Set Source and Automation History (items 29-43)
Data Set and Metadata Primary Contact (items 44-50)- The contact and organization indicated in this section will normally be responsible for maintaining the data set and its attributes, as well as the metadata listing itself. Since changes in personnel assignments within organizations occur on a regular basis, with the exception of the metadata writer's initials indicated in (42. METADATA-LST), the listing of titles, rather than names is preferred.

**Examples shown within these specification listings may not apply to any specific RIGIS data set coverage**

Numbered items indicate line number on metadata file.

RIGIS-CAT-ID RIGIS data set catalog identification code. The internally set eight character code used by the RIGIS for data catalog reference purposes. (See Appendix A.) (Example: s44hhp88)
DATA-SET-IDENT RIGIS user assigned data set identity. The abbreviated name or acronym assigned by an individual user to identify the data set on a local storage media. This normally refers to the data set as used by the originator of the metadata file. (Example: hydropol)
DISTRIB-NOTES Distribution restrictions/other sources. Notes on copyright status, or any restrictions on the availability of the data set, and/or listings of other organizations from which like or similar data are available. (Example: (c) rigis 1989 similar data from usgs)
THEME-KEYWORDS Common terms used to describe contents. Words or phrases used in the description of the data set or its attributes which may be helpful in automated search patterns. (Example: lakes, ponds, water bodies)
DATA-SET-DESC A brief textual description of the data set. (Example: state wide lakes and ponds in ri)
ACC-REV-DATE The date by month and year of acceptance by the RIGIS or last revision of the data set and/ or its attribute information as included in the RIGIS database. (Example: 0688)
DATA-STRUCTURE The basic structure of the data set model, and the existence of tabular and/or relational data base attributes. (Example: vector topological with feature attributes and name annotation)
COORD-PRECISION The precision with which object coordinates are managed by the software used to generate the automated data set. (Example: arc-info single precision)
INTENDED-USE The application or purpose for which the data was intended when automated. (Example: state wide natural resource inventory)
INTENDED-SCALE The map scale at which the data was originally intended to be used when automated. This refers to a proportional relationship in single map units to identical units on the ground. (Example: 24000)
TRANSFER-FORMAT The type of the data transfer file output format normally used by the RIGIS for data exchange. (Example: arc-info export)
TRANSFER-SIZE The size of the transfer file in megabytes and tenths in an uncompressed form. (Example: 7-4)
SPL-OBJ-TYPE The type(s) of spatial objects depicted. When multiple object types exit, each will be specified. (Example: polygon)
RESOLUTION The dimension of intended resolution for the smallest spatial object included in the data. (Example: one quarter acre)
SPL-OBJECT-COUNT The total number of spatial objects by type included in the data set in the native form in which it is stored within the RIGIS database. (Example: 177600)
AREA-EXT-BND Area extent boundary. The bounded extent of the area covered in lower left, upper right coordinate limits and/or a textual geographic/political bounded area name. (Example: ll_257609_4558001 ur_322958_4654478 state of rhode island)
AREA-EXCL-BND Area exclusion boundary. The area(s) excluded within the area extent boundary where data is not included in the data set. (Example: usgs chepachet quad)
PROJECTION The map projection on which the data set is based as depicted in its native form within the RIGIS data base. (Example: transverse mercator)
COORDSYS-UNITS The coordinate system, zone and units of measure employed in defining the spatial relationship of features within the data set. (Example: utm_19_meters)
HORIZ-DATUM The horizontal mapping datum and/or spheroid on which the coordinate system is based.(Example: nad27)
VERT-DATUM The vertical reference datum on which elevations are based. (Example: navd29)
REL-DB-ID The name of the relational database file or related table to which linked or related information is stored. (Example: hydropol-pat)
REL-DB-ORG The organization which defines contents and/or updates the relational database file attributes in the associated relational database or table. (Example: ridem)
FIELD-NAME The field or item name as it appears in the relational data base file or table. (Example: comname)
FIELD-CHAR The field character type, input and output width and number of significant decimals in the field or item listing. (Example: n-20-2-2)
FIELD-DESC The field or item description. A brief textual description of the field or item attribute listing. (Example: common names for lakes and ponds)
FIELD-DOMAIN The domain or valid range of values and their units appearing in the field or attribute item listing. The word 'text' may be used for domain character entries. (Example: 1 thru 5 feet inclusive)
FIELD-ASSC Associated files, Relates, Look-Up-Tables for field or item listings containing additional attribute listings and/or descriptions. (Example: usds-scs soils table for ri)
SOURCE-CRTR The organization responsible for creating the original source material used in the data automation process. (Example: usda-scs)
SOURCE-ORIG A brief description of the original source material used to automate or create the data. (Example: usgs mylar topo quad maps)
BIBLIOG-REF The bibliographic document referencing or amplifying on the source material. (Example: usda-scs soil survey of ri 1977)
SOURCE-SCAL The map scale of the source material if in a graphically displayed form. The proper relationship in single map units corresponding to identical distance units on the surface of the earth. (Example: 24000)
SOURCE-DATE The year(s) date(s) of creation or last revision of the source material used in the data automation process. This is usually the date aerial photography was flown, or the most recent date of revision printed on map products. (Example: 1976-1983)
DATA-DATE The month year date(s) of compilation of information used to enhance or augment the source material used for data entry during the automation process. (Example: 1991-1992)
AUTO-EQPT The primary hardware platform type and software package used in the automation process. (Example: pc arc-info)
AUTO-PROC Automation procedures. - The methods or processing steps used to automate the data. (Example: manual digitization directly from the enhanced source maps on a digitizing tablet)
PROC-TOL Procedure Tolerances - A description of processing tolerances and/or standards adhered to in automating the data. (Example: rigis standards rms_005 fuzzy-002)
PROC-DATE Procedure Date - The month and year of completion of the original automation process. (Example: 0893)
POS-ACCU Positional Accuracy - The measure or best estimate of error of spatial objects represented relative to true position on the ground. (Example: plus or minus 100 feet)
POS-ACCUCK Positional Accuracy Assurance Checks- The method(s) by which the positional accuracy was determined or checked. (Example: manual graphic overlay comparison with source material no field check)
ATTRIB-ACCU Attribute Accuracy Assurance- The measure or estimate of the confidence level with which the attributes associated with spatial features are identified or coded in the data set. (Example: rigis standards 99 percent)
ATT-ACCUCK Attribute Accuracy Check - The method(s) by which the attribute accuracy was determined or checked. (Example: manual comparison of attribute printout listing with source no field check)
DATA-INTEGRITY An explanation of the integrity of the relationships between objects in the data set. (Example: topologically complete arc-info coverage)
METADATA-LIST The month and year revision date for the current metadata listing, and the initials of the person actually writing this file. (Example: 0893-jds)
CONTACT-TITLE The title of the contact individual responsible for maintenance or update of the data set coverage. (Example: rigis coordinator)
CONTACT-ORG The organization name of the contact. (Example: ri department of administration-planning-rigis)
CONTACT-ADDR The street address of the contact. (Example: one capitol hill)
CONTACT-CTYST The city, state, and zip code of the contact. (Example: providence ri 02908-5872)
CONTACT-PHONE The area code and telephone number of the contact. (Example: 401 277-6483)
CONTACT-EMAIL The e-mail type and address of the contact. (Example: internet rigis@ridoa.gov)

Return to Index

V. References

Content Standards for Spatial Metadata (DRAFT)

Federal Geographic Data Committee. October 19, 1992

Federal Geographic Data Committee Secretariat

U.S. Geological Survey
590 National Center
Reston, Virginia 22092

Digital Database Standards for the Rhode Island

Geographic Information System, Version 1., 1989

The Environmental Data Center
Department of Natural Resources Science
The University of Rhode Island
210B Woodward Hall
Kingston, Rhode Island 02881

General Laws of the State of Rhode Island and Providence Plantations

16-32-30 Education - Geographic Information System Laboratory at the URI

42-11-2 Administration - Powers and Duties of the RI Department of Administration

42-11-10 RI Department of Administration Division of Planning

Return to Index

APPENDIX A

SPECIFICATIONS FOR DATA SET COVERAGE CATALOG NAMING CONVENTIONS

FOR THE

RHODE ISLAND GEOGRAPHIC INFORMATION SYSTEM

RIGIS METADATA ITEM RIGIS-CAT-ID

SEPTEMBER 1993

RI Department of Administration Division of Planning-RIGIS

One Capitol Hill, Providence, RI 02908-5872

Appendix A Index:

A-1. Introduction

A-2. Purpose

A-3. Specifications

Return to Main Index

A-1. Introduction

Most RIGIS data users assign their own identifying coding to a coverage when they 'import' it from a supplied 'export', 'dxf', or 'dlg' file. The resulting internal name varies from user to user, and from one hardware platform to the next. This has the potential to create confusion in identifying like data for local system administrators, and data base managers as well as among our individual users. The implementation of a unique coding system, which will identify individual data set coverages across the database, will alleviate these problems.

Questions and comments referring to these specifications should be addressed to:

The RIGIS Coordinator

Rhode Island Department of Administration

Division of Planning-RIGIS

One Capitol Hill

Providence, RI 02908-5872

Tel (401) 277-6483

FAX (401) 277-3809

e-mail:

Return to Appendix A Index

Return to Main Index

A-2. Purpose

The purpose of assigning a "RIGIS_CAT_ID" is to provide unique coding to each and every coverage in the RIGIS database. It is an additional identifier which will augment local naming conventions, and will be attached to new coverages as they are accepted into the RIGIS database. The RIGIS-CAT-ID will be specified in new metadata files as they are written for existing coverages, and will be used to identify coverages as they are listed in the RIGIS Data Listing and Data Catalog. In the future, it will be highly recommended that all 'export' or transfer files exchanged between different organizations be named for the RIGIS-CAT-ID (xnnxxnn.e00,xnnxxxnn.dxf, etc.).

Return to Appendix A Index

Return to Main Index

A-3. SPECIFICATIONS

The coding scheme specified in this document will provide a means for identifying geographic area covered, subject matter, and acceptance or revision date.

A. GENERAL EXPLANATION OF THE RIGIS_CAT_ID CODING SCHEME

RIGIS_CAT_ID - A field record with a total of eight alpha/numeric characters (xnnxxxnn)

1. AREA DESIGNATION

First Character (x-------)- Area Type - 1 Lower Case (l.c.) Character (c,b,p,q,s,t) Examples: (First Letter): (s)tate (q)uad (t)own (c)ounty (p)roject (b)lock

Second and Third Characters (-nn-----) - Area Code - 2 Integers (01-99) Examples: State, Quad, County Town, Project Block (tile) 01-99 01-37 01-09 01-39 01-99 01-99

2. SUBJECT DESIGNATION

Fourth Character (---x----)- Layer Type - 1 l.c. Character (a-z) Examples: (a)nno, (b)oundary, (c)ultural, (d)emographic,

Fifth and Sixth Characters (----nn--)- Coverage Code - 2 l.c. Characters (aa-zz) Examples: gn - Geographic Names Inventory System

nl - Quad Neatlines
hp - Historic Points
cb - Census Blocks
bd - Bedrock Geology

2. ACCEPTANCE/REVISION DATE DESIGNATION

Seventh and Eighth Characters (------xx)- Acceptance Year Code- 2 Integers (00-99) Decade-Year Example: 93

RIGIS_CAT_ID Examples:

Statewide Annotation Geographic Names Inventory System (GNIS) - s44agn86
USGS Quad S. Kingstown Boundary Neatlines (neatlines)- q29bnl86
Town of Warwick Cultural Historic Points 1990 Version - t35chp90
Providence County Demographic Census Blocks 1990 - c07dcb90
Scituate Watershed Project Bedrock Geology from 1988- p02gbd88

ASSIGNED RIGIS_CAT_ID CODING CHARACTERS
AREA DESIGNATION - RIGIS_CAT_ID CHARACTERS 1-3

AREA TYPE

c County - Federal Information Processing codes (FIPS) and two additional numeric codes for two combined counties in the eastern Narragansett Bay and Southern Rhode Island areas.

COUNTY CODES (c--, codes are 01-09)

01 - Bristol
02 - Bristol and Newport combined
03 - Kent
04- Kent and Providence combined
05 - Newport
07 - Providence
08 - Kent and Washington combined
09 - Washington

AREA TYPE

b Block - Assigned by RIGIS for block or tile structures created by developers or user modifiers of data sets or coverages 01-99 As assigned

p Project - Assigned by RIGIS for individual projects.

PROJECT AREA CODES (p--, codes are 01-99)

01 - Narragansett Bay Project
02 - Scituate Watershed Management
03 - Solid Waste Landfill Siting
04 - GreenSpace 2000
05 - T.F Green Airport
06 - Narragansett Bay Commission CSO
07 - Cranston-Howard Complex

q USGS Quad - Assigned by RIGIS

QUAD CODES (q--, codes are 01-37)

For Rhode Island

01 - Oxford
02 - Uxbridge
03 - Blackstone
04 - Franklin
05 - Thompson
06 - Chepachet
07 - Georgiaville
08 - Pawtucket
09 - Attleboro
10 - E Killingly
11 - Clayville
12 - N Scituate
13 - Providence
14 - E. Providence
15 - Oneco
16 - Coventry
17 - Crompton
18 - E Greenwich
19 - Bristol
20 - Fall River
21 - Voluntown
22 - Hope Valley
23 - Slocum
24 - Wickford
25 - Prudence Island
26 - Tiverton
27 - Ashaway
28 - Carolina
29 - Kingston
30 - Narragansett Pier
31 - Newport
32 - Sakonnet Point
33 - Watch Hill
34 - Quonochontaug
35 - Block Island
36 - Westport
37 - Mystic

AREA TYPE

� State - Federal Information Processing Codes (FIPS)

STATE FIPS CODES, for New England and nearby northeastern states (s--, codes are 2 digits as below)

09 - Connecticut
23 - Maine
25 - Massachusetts
34 - New Hampshire
35 - New Jersey
36 - New York
42 - Pennsylvania
44 - Rhode Island
50 - Vermont

AREA TYPE

� Town - Office of State Planning Number (OSP)

TOWN OSP CODES (t--, codes are 01-39)

01 - Barrington
02 - Bristol
03 - Burrillville
04 - Central Falls
05 - Charlestown
06 - Coventry
07 - Cranston
08 - Cumberland
09 - E Greenwich
10 - E Providence
11 - Exeter
12 - Foster
13 - Glocester
14 - Hopkinton
15 - Jamestown
16 - Johnston
17 - Lincoln
18 - Little Compton
19 - Middletown
20 - Narragansett
21 - Newport
22 - New Shoreham
23 - N Kingstown
24 - N Providence
25 - N Smithfield
26 - Pawtucket
27 - Portsmouth
28 - Providence
29 - Richmond
30 - Scituate
31 - Smithfield
32 - S. Kingstown
33 - Tiverton
34 - Warren
35 - Warwick
36 - Westerly
37 - W Greenwich
38 - W Warwick
39 - Woonsocket

2: SUBJECT DATA LAYER TYPE - CHARACTER 4 (Single l.c. Alpha)

a-z permitted

Char. Layer Examples

a Annotation, Names (gnis)
b Boundary Lines (quad. neatlines, town lines)
c Cultural/Historic (historic districts, schools)
d Demographic/Census (rimaps, census tracts)
e Economic (economic development zones)
f Flood Plains/Zones (FEMA A & V, floodways)
g Geology (bedrock, glacial)
h Hydrography/Hydrology (hydropolys, basins, gw res)
i. Unassigned
j Unassigned
k Unassigned
l Land Use/Land Cover (giras, lu_88 quads)
m Unassigned
n Natural Resources/Ecology (rare species, forest)
o Open Space/Recreation (Open Space, RIDEM Mngt A)
p Parcels/Properties (Block Island parcels, Scituate parcels)
q Unassigned
r Raster/Images (Block Island orthophoto)
s Soils (Soils quads)
t Transportation (roads, railroads)
u Utilities (public water and sewer, gas)
v Vertical (DEMs, topographic contours)
w Wetlands (Wet_88 Quads)
x Hazardous Materials (RIDEM GW facilities inventory, CERCLIS)
y Unassigned
z Zoning (industrial zones)

COVERAGE CODE - CHARACTERS 5 AND 6 (aa-zz)

These CHARACTERS will be assigned by the creator of the originator of the metadata file at the time that the metadata file is written. Close coordination will be required between the RIGIS Database Manager or RIGIS Coordinator to ensure duplication of coding letters does not occur within a subject layer type. (Duplicative use of alpha CHARACTERS is expected and permitted between different subject data layers. (Hhp for hydropolys and Chp for historical points).)

3. DATE DESIGNATION

ACCEPTANCE REVISION DATE DESIGNATION CHARACTERS 7-8 (00-99)

These integers will be assigned by the originator of the metadata file for each individual coverage. The year and decade date will indicate the year that those data were accepted by the RIGIS for inclusion in the database. Coordination between the originator and the RIGIS Coordinator or Database Manager will be required.

Return to Appendix A Index

Return to Main Index