. .

U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

Oregon / Washington

GIS Metadata


BLM OR Oregon and Washington Highways Line
FGDC Metadata
Show Definitions
Description | Spatial | Data Structure | Data Quality | Data Source | Data Distribution | Metadata
Description
Citation
Information used to reference the data.
Title: BLM OR Oregon and Washington Highways Line
Originators: Bureau of Land Management Oregon State Office
Publication date: 20120917
Data type: vector digital data
Description
A characterization of the data, including its intended use and limitations.
Abstract:
highways_arc: This file includes all state owned or maintained highways, connections, frontage roads, temporary traveled routes and located lines in the states of Oregon and Washington.
Purpose:
This data provides a detailed view of the state highway system based on the Linear Referencing system (LRS) used by both the Oregon Department of Transportation and the Washington State Department of Transportation. 1:24k resolution.
Supplemental information:
Dataset locally known as highways_arc This data is intended for use at scales of 1:24,000 or smaller.
Dataset credit:
Geographic Information Services Unit, Oregon Department of Transportation and the Cartography/GIS Section of the Washington State Department of Transportation.
Point Of Contact
Contact information for the individual or organization that is knowledgeable about the data.
Organization: Bureau of Land Management
Person: Chris Knauf
Position: Outdoor Recreation Planner
Phone: (503) 808-6427
Email: cknauf@blm.gov
Address type: mailing
Address:
P.O. Box 2965
City: Portland
State or Province: OR
Postal code: 97201
County: US
Data Type
How the data are represented, formatted and maintained by the data producing organization.
Data type: vector digital data
Native dataset environment: Microsoft Windows 2000 Version 5.2 (Build 3790) Service Pack 2; ESRI ArcCatalog 9.3.1.1850
Time Period of Data
Time period(s) for which the data corresponds to the currentness reference.
Date: 20120917 Time: unknown
Currentness reference:
publication date
Status
The state of and maintenance information for the data.
Data status: Complete
Update frequency: As needed
Key Words
Words or phrases that summarize certain aspects of the data.
Theme:
Keywords: Framework
Keyword thesaurus: BLM-Theme
Theme:
Keywords: transportation
Keyword thesaurus: ISO 19115
Theme:
Keywords: roads, highways
Keyword thesaurus: None
Theme:
Keywords: transportation
Keyword thesaurus: ISO 19115 Topic Categories
Place:
Keywords: Oregon, Washington
Keyword thesaurus: BLM-State
Place:
Keywords: WA, USA, US, Pacific Northwest, United States, OR
Keyword thesaurus: None
Data Access Constraints
Restrictions and legal prerequisites for accessing or using the data after access is granted.
Access constraints:
PUBLIC DATA: None, these data are considered public domain.
Use constraints:
These data are provided by Bureau of Land Management (BLM) "as is" and may contain errors or omissions. The User assumes the entire risk associated with its use of these data and bears all responsibility in determining whether these data are fit for the User's intended use. The information contained in these data is dynamic and may change over time. The data are not better than the original sources from which they were derived, and both scale and accuracy may vary across the data set. These data may not have the accuracy, resolution, completeness, timeliness, or other characteristics appropriate for applications that potential users of the data may contemplate. The User is encouraged to carefully consider the content of the metadata file associated with these data. These data are neither legal documents nor land surveys, and must not be used as such. Official records may be referenced at most BLM offices. Please report any errors in the data to the BLM office from which it was obtained. The BLM should be cited as the data source in any products derived from these data. Any Users wishing to modify the data should describe the types of modifications they have performed. The User should not misrepresent the data, nor imply that changes made were approved or endorsed by BLM. This data may be updated by the BLM without notification.
Spatial Reference Information
Horizontal Coordinate System
Reference system from which linear or angular quantities are measured and assigned to the position that a point occupies.
Coordinate System Details
Geographic coordinate system
Latitude resolution: 2e-008
Longitude resolution: 2e-008
Geographic coordinate units: Decimal Degrees
Geodetic model
Horizontal datum name: D North American 1983
Ellipsoid name: GRS 1980
Semi-major axis: 6378137.0
Denominator of flattening ratio: 298.257222101
Spatial Domain
The geographic areal domain of the data that describes the western, eastern, northern, and southern geographic limits of data coverage.
Bounding Coordinates
In Unprojected coordinates (geographic)
Boundary Coordinate
West -124.590343 (latitude)
East -116.833891 (latitude)
North 49.002328 (longitude)
South 41.865135 (longitude)
Data Structure and Attribute Information
Overview
Summary of the information content of the data, including other references to complete descriptions of entity types, attributes, and attribute values for the data.
Direct spatial reference method: Vector
Indirect spatial reference method: Oregon
Attributes of highways_arc
Detailed descriptions of entity type, attributes, and attribute values for the data.
Description:
A segment of highway between two intersecting locations of other highway segments
Source:
Geographic Information Services Unit, Oregon Department of Transportation.
Attributes
SHAPE
Definition:
Feature geometry.
Attribute values: Coordinates defining the features.
Attribute definition source:
ESRI
us_sign_2
Definition:
US Highway route number (overlapping route).
Attribute definition source:
Bureau of Land Management - Oregon State Office
hwyname
Definition:
Highway route name.
Attribute definition source:
Bureau of Land Management - Oregon State Office
objectid
Definition:
Internal feature number.
Attribute values: Sequential unique whole numbers that are automatically generated.
Attribute definition source:
ESRI
hwy_class
Definition:
Highway classification based on highway sign attribute.
Attribute domain values
Value Definition
INT
Interstate Highway
Definition Source:
Bureau of Land Management - Oregon State Office
USH
US Highway
Definition Source:
Bureau of Land Management - Oregon State Office
STH
State Highway
Definition Source:
Bureau of Land Management - Oregon State Office
CNTY
County Highway
Definition Source:
Bureau of Land Management - Oregon State Office
MUN
Municipal Road
Definition Source:
Bureau of Land Management - Oregon State Office
Attribute definition source:
Bureau of Land Management - Oregon State Office
lrs
Definition:
Linear Reference System highway identifier (Oregon only). This is a representation of elements contained in the State of Oregon's database used to identify a highway, connection or frontage road. The first nine characters are the inventory route numbers and the last three characters are the sub-route numbers.
Attribute values: The twelve digit alphanumeric string is broken down into its components as: 1: Place holder 0 (zero) 2-4: Hwy Number 001 to 499 5-6: Hwy Suffix 00 (zero zero), AA-ZZ (alphabetic characters) 7: Roadway Identifier (1-5) 8: Mileage Type (Z,T,Y) 9: Overlap Mileage Code (0-9) 10: Jurisdiction Code (S) 11-12: Two Place holders 00 (zero zero)
Attribute definition source:
Oregon Transportation Management System (OTMS) GIS Base Layer Development Project (GIS01)
rdwy_id
Definition:
The number assigned to a roadway where more than one roadbed exists for the highway.
Attribute domain values
Value Definition
1
The primary roadway. Direction of travel is in the direction of increasing mile points.  (Oregon only)
Definition Source:
Integrated Transportation Information System (ITIS) - Oregon Dept. of Transportation
2
The secondary roadway. Direction of travel is in the direction of decreasing mile points.  (Oregon only)
Definition Source:
Integrated Transportation Information System (ITIS) - Oregon Dept. of Transportation
3
A split roadway with the direction of travel in the direction of increasing mile points.  (Oregon only)
Definition Source:
Integrated Transportation Information System (ITIS) - Oregon Dept. of Transportation
4
A split roadway with the direction of travel in the direction of decreasing mile points.  (Oregon only)
Definition Source:
Integrated Transportation Information System (ITIS) - Oregon Dept. of Transportation
5
Located line.  (Oregon only)
Definition Source:
Integrated Transportation Information System (ITIS) - Oregon Dept. of Transportation
6
Used to differentiate split highways for display at small scales in Washington state only.
Definition Source:
Bureau of Land Management - Oregon State Office
7
Used to differentiate split highways for non display at small scales in Washington state only.
Definition Source:
Bureau of Land Management - Oregon State Office
Attribute definition source:
Oregon Transportation Management System (OTMS) GIS Base Layer Development Project (GIS01)
rdwy_typ
Definition:
A unique identifier assigned to the roadway designating a spur, frontage road, connection or regular roadway.
Attribute domain values
Value Definition
reg
Regular highway
Definition Source:
Geographic Information Services Unit (GISU) - Oregon Dept. of Transportation
frt
Frontage road
Definition Source:
Geographic Information Services Unit (GISU) - Oregon Dept. of Transportation
con
Connection
Definition Source:
Geographic Information Services Unit (GISU) - Oregon Dept. of Transportation
spr
Spur
Definition Source:
Geographic Information Services Unit (GISU) - Oregon Dept. of Transportation
Attribute definition source:
Oregon Transportation Management System (OTMS) GIS Base Layer Development Project (GIS01)
hwy_seg_id
Definition:
A unique identifier assigned to the roadway designating a spur, frontage road, connection or regular roadway.  (Oregon only)
Attribute definition source:
Oregon Transportation Management System (OTMS) GIS Base Layer Development Project (GIS01)
i_sign
Definition:
Interstate route number.
Attribute definition source:
Bureau of Land Management - Oregon State Office
us_sign_1
Definition:
US Highway route number.
Attribute definition source:
Bureau of Land Management - Oregon State Office
hwylocname
Definition:
Alternate name (e.g. local street name).
Attribute definition source:
Bureau of Land Management - Oregon State Office
st_sign_1
Definition:
State Highway route number.
Attribute definition source:
Bureau of Land Management - Oregon State Office
st_sign_2
Definition:
State Highway route number (overlapping route).
Attribute definition source:
Bureau of Land Management - Oregon State Office
DSG_NAME
SPEC_DSGTN
SHAPE_Length
Definition:
Length of feature in internal units.
Attribute values: Positive real numbers that are automatically generated.
Attribute definition source:
ESRI
SDTS Feature Description
Description of point and vector spatial objects in the data using the Spatial Data Transfer Standards (SDTS) terminology.
Spatial data transfer standard (SDTS) terms
Feature class
Type: String
Count: 26321
Data Quality and Accuracy Information
General
Information about the fidelity of relationships, data quality and accuracy tests, omissions, selection criteria, generalization, and definitions used to derive the data.
Logical consistency report:
Where appropriate, line segment ends have been snapped together to eliminate gaps at interchanges, intersections and along contiguous sections of roadway.
Completeness report:
This theme contains all highways and related access features (interchange ramps, frontage roads, etc.) for the states of Oregon and Washington.
Attribute Accuracy
Accuracy of the identification of data entities, features and assignment of attribute values.
Attribute accuracy report:
In Oregon, the Highway segment id, lrs, roadway id, and roadway type were obtained from the Oregon Department of Transportation's Hwy_seg shapefile. Interstate sign, US sign 1, US sign 2, ST sign 1, ST sign 2, and highway name were obtained from ODOT'S routes_xref_2005 shapefile. In Washington, Interstate sign, US sign 1, US sign 2, ST sign 1, ST sign 2 were populated from WSDOT's SR24kLRSLinesSPS shapefile, while roadway id and roadway type were populated by the Bureau of Land Management Oregon State Office. .Highway local name and highway class were created by the Bureau of Land Management Oregon State Office. OBJECTID, Shape and Shape_Length were generated from ArcGIS software. In Washington, State Route numbers were obtained from the 2005B State Highway Log.
Positional Accuracy
Accuracy of the positional aspects of the data.
Horizontal accuracy report:
Oregons highway data has been determined to meet or exceed NSDI map accuracy standards for 1:24,000 scale maps. Accuracy was determined by the combined use of USGS digital ortho photo quads and the NGS benchmarks to apply an accuracy statement to the highway linework via verification of known and visible NGS benchmarks on the orthoquads. The Washington data's positional accuracy has not been determined.
Vertical accuracy report:
No vertical positional accuracy has been determined
Data Source and Process Information
Data Sources
Information about the source data used to construct or derive the data.
Data source information
SR24kLRSLinesSPS.shp
Title: SR24kLRSLinesSPS.shp
Originators: Cartography/GIS Section, Washington State Department of Transportation (WSDOT)
Publication date: 20060724 Publication time: unknown
Data type: vector digital data
Media: None
Hwy_SEG
Title: Hwy_SEG
Originators: Geographic Information Services Unit, Oregon Department of Transportation (ODOT)
Data type: vector digital data
Media: None
USGS DOQ
Title: 1:24,000 7.5 minute United States Geologic Survey Quadrangles
Originators: United States Geologic Survey Denver, Colorado 80225 or Reston, Virginia 22092
Publication date: 19950101
Data type: map
Map scale denominator: 24000
Media: None
Date: 19950101 Time: unknown
Currentness reference:
ground condition
routes_xref_2005
Title: routes_xref_2005
Originators: Geographic Information Services Unit, Oregon Department of Transportation (ODOT)
Publication date: unknown
Data type: vector digital data
Media: None
Date: unknown
Currentness reference:
publication date
Process Steps
Information about events, parameters, tolerances and techniques applied to construct or derive the data.
Process step information
Process Step 1
Process description:
Highway class (hwy_class) attribute field added. Values populated based on highway sign attributes.
Person: Erik Brewster
Position: GIS Specialist
Address type: mailing and physical
Address:
PO BOX 2965
City: Portland
State or Province: OR
Postal code: 97208
County: US
Process date: unknown
Process Step 2
Process description:
The highway sign and name attributes from routes_xref_2005 were spatially joined to the highway segments.
Person: Erik Brewster
Position: GIS Specialist
Address type: mailing and physical
Address:
PO BOX 2965
City: Portland
State or Province: OR
Postal code: 97208
County: US
Process date: unknown
Process Step 3
Process description:
Manual corrections and verfication of attribute transfer were made where necessary.
Person: Erik Brewster
Position: GIS Specialist
Address type: mailing and physical
Address:
PO BOX 2965
City: Portland
State or Province: OR
Postal code: 97208
County: US
Process date: unknown
Process Step 4
Process description:
09-11-08: Populated the DSG_Name field with attribute from Burns district and Roseburg district back country byways layers they gave the state office. Also populated DSG_Name where it overlays with Back_Country_Byways layer in SDE. Our goal is to remove that layer from SDE once we can add a code to query back country byways, scenic routes, etc.
Organization: BLM OR/WA State Office
Person: Ryan Kelley
Phone: 503-808-6495
Email: rkelley@or.blm.gov
Process Step 5
Process description:
The shapefiles were imported to a personal geodatabase and reprojected.
Person: Erik Brewster
Position: GIS Specialist
Address type: mailing and physical
Address:
PO BOX 2965
City: Portland
State or Province: OR
Postal code: 97208
County: US
Process date: unknown
Process Step 6
Process description:
The Hwy_SEG and routes_xref_2005 shapefiles were obtained via ftp from ODOT.
Person: Erik Brewster
Position: GIS Specialist
Address type: mailing and physical
Address:
PO BOX 2965
City: Portland
State or Province: OR
Postal code: 97208
County: US
Process date: 20050608
Process Step 7
Process description:
Copied interstate, US, and state highways from the OR/WA BLM GTRN layer to fill gaps in the ODOT highway Layer
Person: Nate Smith
Position: GIS Specialist
Address type: mailing and physical
Address:
PO BOX 2965
City: Portland
State or Province: OR
Postal code: 97208
County: US
Process date: 20060612
Process Step 8
Process description:
Attributed frontage and connector roads in Jackson and Josephine counties. The hwylocname and hwy_class fields were populated based on John McGlothlin's local data.
Organization: Northrop Grumman - BLM Oregon State Office
Person: Erik Brewster
Process date: 20060825
Process Step 9
Process description:
Added highways from WA DOT source for the state of Washington. Coded RDWY_ID with new values 6 and 7 for cartographic purposes.
Organization: Northrop Grumman - BLM OR/WA State Office
Person: Ryan Kelley
Phone: 503-808-6495
Email: rkelley@blm.gov
Process date: 20080110
Process Step 10
Process description:
Corrected US Highway 30 attribute information for 64 segments near The Dalles. Highway 30 was originally incorrectly attributed as a State Highway. Both HWY_CLASS and US_SIGN_1 fields were populated with the correct information for these segments.
Organization: Northrop Grumman - BLM OR/WA State Office
Person: Ryan Kelley
Phone: 503-808-6495
Email: rkelley@blm.gov
Process date: 20080226
Process Step 11
Process description:
Fixed topology errors using these rules (must not overlap, must not self-overlap, must be single part). Worked with Gavin Hoban in Prineville also for questions about rdwy_typ overlap discrepencies.
Organization: Northrop Grumman - BLM OR/WA State Office
Person: Ryan Kelley
Phone: 503-808-6495
Email: rkelley@blm.gov
Process date: 20080317
Process Step 12
Process description:
Placed Succor Creek Road (from Oregon T22S-R46E Sec 28 to Oregon T27S-R46E Sec 11, connecting Oregon highway 201 to US 95) in BLM's editable GTRN dataset on advice of Vale district office GIS staff indicating that this is a dirt road.
Organization: U.S. BLM Oregon State Office
Person: Steve Salas
Position: GIS Specialist / ArcSDE Administrator
Phone: 503-808-6416
Email: ssalas@blm.gov
Process date: 20090403
Process Step 13
Process description:
Added portion of HWY 95 in Nothern Nevada as requested by Vale District Office
Organization: BLM
Person: Erin Frostad
Position: Carto Tech
Phone: 503-808-6524
Email: efrostad@blm.gov
Process date: 20090630
Process Step 14
Process description:
Updated Salem Highways - removed frontage, overpasses/underpasses from Highways and added them to GTRN. Updated connections and secondary roads to maintain connectivity. Bruce Ahrendt reviewed.
Organization: BLM
Person: Erin Frostad
Position: GIS Tech
Phone: 503-808-6524
Email: efrostad@blm.gov
Process date: 20091027 Process time: 121208
Process Step 15
Process description:
Updated Roseburg Highways - removed frontage, overpasses/underpasses from Highways and added them to GTRN. Updated connections and secondary roads to maintain connectivity. Gary Passow reviewed.
Organization: BLM
Person: Erin Frostad
Position: GIS Tech
Phone: 503-808-6524
Process date: 20091118 Process time: 110811
Process Step 16
Process description:
Updated Coos Bay Highways - removed frontage, overpasses/underpasses from Highways and added them to GTRN. Updated connections and secondary roads to maintain connectivity. Alan Ward reviewed.
Organization: BLM
Person: Erin Frostad
Position: GIS Tech
Phone: 503-808-6524
Process date: 20091120 Process time: 112745
Process Step 17
Process description:
Updated Burns Highways - removed 2 frontage roads and a connection - approved by Pam Keller
Organization: BLM
Person: Erin Frostad
Position: GIS Tech
Phone: 503-808-6524
Process date: 20100114 Process time: 115314
Process Step 18
Process description:
Updated Vale Highways - removed frontage, overpasses/underpasses from Highways and added them to GTRN. Updated connections and secondary roads to maintain connectivity. Brent Grasty reviewed.
Organization: BLM
Person: Erin Frostad
Position: GIS Tech
Phone: 503-808-6524
Process date: 20100120 Process time: 112436
Process Step 19
Process description:
Updated Eugene Highways - removed frontage, overpasses/underpasses from Highways and added them to GTRN. Updated connections and secondary roads to maintain connectivity. Jay Ruegger reviewed.
Organization: BLM
Person: Erin Frostad
Position: GIS Tech
Phone: 503-808-6524
Process date: 20100203 Process time: 055244
Process Step 20
Process description:
Updated Deschutes county highways within urban growth boundary areas Removed frontage roads, overpasses/underpasses from Highways and added them to GTRN.
Person: Noah Layosa
Process date: 20100309 Process time: 072738
Process Step 21
Process description:
Updated Prineville Highways - removed frontage, overpasses/underpasses from Highways and added them to GTRN. Updated connections and secondary roads to maintain connectivity. Greg Daniels ok'd.
Organization: BLM
Person: Erin Frostad
Position: GIS Tech
Phone: 503-808-6524
Process date: 20100608 Process time: 124739
Process Step 22
Process description:
Added a small segement S of KFalls to connect hwy 161 together for Mike Limb.
Organization: BLM
Person: Erin Frostad
Position: GIS Tech
Phone: 503-808-6524
Process date: 20120131
Process Step 23
Process description:
Removed Highway 227 in Douglas County and added as County Route 1 in GTRN.
Organization: BLM
Person: Erin Frostad
Position: GIS Tech
Phone: 503-808-6524
Process date: 20120313
Process Step 24
Process description:
Changed highway names from all-uppercase to mixed case. Correct arcs that were missing designation of Snake River-Mormon BCB. Standardized blanks in several fields to null.
Organization: U.S. Bureau of Land Management, OR/WA State Office
Person: Shelley Moore
Position: GIS Specialist
Phone: 503-808-6566
Email: r1moore@blm.gov
Process date: 20120912
Data Distribution Information
General
Description of the data known by the party from whom the data may be obtained, liability of party distributing data, and technical capabilities required to use the data.
Distribution liability:
The BLM assumes no responsibility for errors or omissions. No warranty is made by the BLM as to the accuracy, reliability, or completeness of these data for individual use or aggregate use with other data; nor shall the act of distribution to contractors, partners, or beyond, constitute any such warranty for individual or aggregate data use with other data. Although these data have been processed successfully on computers of BLM, no warranty, expressed or implied, is made by BLM regarding the use of these data on any other system, or for general or scientific purposes, nor does the fact of distribution constitute or imply any such warranty. In no event shall the BLM have any liability whatsoever for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of the use or reliance on the geographic data or arising out of the delivery, installation, operation, or support by BLM.
Distribution Point of Contact
Contact information for the individual or organization distributing the data.
Organization: Bureau of Land Management
Person: Eric Hiebenthal
Position: GIS Data Management Specialist
Phone: 503-808-6340
Fax: 503-808-6419
Email: ehiebent@blm.gov
Instructions:
contact instructions
Address type: mailing
Address:
P.O Box 2965
City: Portland
State or Province: OR
Postal code: 97208
County: US
Standard Order Process
Common ways in which data may be obtained.
Fees: Contact distributor.
Ordering instructions:
Data are only available through the Oregon/Washington State office of the Bureau of Land Management.
Metadata Reference
Metadata Date
Dates associated with creating, updating and reviewing the metadata.
Last updated: 20110722
Last metadata review date: 20120920
Metadata Point of Contact
Contact information for the individual or organization responsible for the metadata information.
Organization: Bureau of Land Management, Oregon State Office
Person: Roger Mills
Position: GIS Specialist
Phone: (503) 808-6340
Fax: (503) 808-6419
Telecommunications Device or Teletypewriter (TDD/TTY) phone: tdd/tty phone
Email: r2mills@blm.gov
Hours of service: 8:00-4:00
Instructions:
None
Address type: mailing
Address:
P.O. Box 2965
City: Portland
State or Province: OR
Postal code: 97208
County: US
Metadata Standards
Description of the metadata standard used to document the data and reference to any additional extended profiles to the standard used by the metadata producer.
Standard name: FGDC Content Standard for Digital Geospatial Metadata
Standard version: FGDC-STD-001-1998
Time convention: local time
FGDC Plus Metadata Stylesheet
Stylesheet: FGDC Plus Stylesheet
File name: FGDC Plus.xsl
Version: 2.0
Description: This metadata is displayed using the FGDC Plus Stylesheet, which is an XSL template that can be used with ArcGIS software to display metadata. It displays metadata elements defined in the Content Standard for Digital Geospatial Metadata (CSDGM) - aka FGDC Standard, the ESRI Profile of CSDGM, the Biological Data Profile of CSDGM, and the Shoreline Data Profile of CSDGM. CSDGM is the US Federal Metadata standard. The Federal Geographic Data Committee originally adopted the CSDGM in 1994 and revised it in 1998. According to Executive Order 12096 all Federal agencies are ordered to use this standard to document geospatial data created as of January, 1995. The standard is often referred to as the FGDC Metadata Standard and has been implemented beyond the federal level with State and local governments adopting the metadata standard as well. The Biological Data Profile broadens the application of the CSDGM so that it is more easily applied to biological data that are not explicitly geographic (laboratory results, field notes, specimen collections, research reports) but can be associated with a geographic location. Includes taxonomical vocabulary. The Shoreline Data Profile addresses variability in the definition and mapping of shorelines by providing a standardized set of terms and data elements required to support metadata for shoreline and coastal data sets. The FGDC Plus Stylesheet includes the Dublin Core Metadata Element Set. It supports W3C DOM compatible browsers such as IE7, IE6, Netscape 7, and Mozilla Firefox. It is in the public domain and may be freely used, modified, and redistributed. It is provided "AS-IS" without warranty or technical support.
Instructions: On the top of the page, click on the title of the dataset to toggle opening and closing of all metadata content sections or click section links listed horizontally below the title to open individual sections. Click on a section name (e.g. Description) to open and close section content. Within a section, click on a item name (Status, Key Words, etc.) to open and close individual content items. By default, the Citation information within the Description section is always open for display.
Download: FGDC Plus Stylesheet is available from the ArcScripts downloads at www.esri.com.