2019_1YR_DataServiceSOW_Final_8-15-20.docx

Contract Statement of Work 2019 – 2020

Introduction for Deliverable A:

The U.S. Bureau of Land Management (BLM) administers ecologically diverse and biologically important lands in federal ownership and is committed to using the best available scientific information when fulfilling its responsibility to manage its valuable resources. For the BLM to effectively protect, manage, and monitor at-risk species on its lands, the Bureau seeks additional information regarding the occurrence of at-risk species on lands it administers as well as occurrences of species managed by other federal agencies within the BLM footprint and on federal lands within states surrounding BLM lands.

BLM seeks a scientifically credible organization with access to biodiversity data and expertise that is locally precise and nationally consistent, that can provide a Multi-Jurisdictional Dataset (biodiversity location data) or MJD, with the most precise locational data available, for vulnerable species, including all federally listed threatened and endangered species.

Introduction for Deliverable B:

This portion of the contract seeks services that will provide BLM with analyses of the Contractor botanical data from their national-level MJD for rare plants. The analyses will include pertinent background data and decision-quality science that will assist BLM to define and conserve rare plants within their ecosystems. This contract will transform plant data into knowledge products and visualizations, and provide meaning through expert analyses and support to guide decision-making, implement species actions, and enhance conservation of rare plants.

Introduction for Deliverable C:

In order for the BLM to effectively protect, manage, and monitor at-risk species on its lands, the BLM seeks additional information regarding the occurrence of at-risk species on lands it administers as well as occurrences of species managed by other federal agencies within the BLM footprint. These maps and analyses can help BLM to determine where to seek potential conservation projects on its own lands and in coordination with other Federal agencies for high priority species. BLM is seeking a qualified source to provide an analysis of species at risk on BLM and other federal agency lands, providing lists of species by agency, maps and quantify known occurrences. This analysis must be based on best-available scientific, nationally consistent biodiversity data provided by State Natural Heritage Programs or equivalent entities.

Introduction for Deliverable D:

To aid in conservation while managing for multiple uses, BLM needs predictive habitat models for rare plant species. This project would pilot in New Mexico and expand to other BLM areas once proven successful. These models would act as improvements, technologies, or scientific studies that streamline, enhance, or inform the NEPA process for plans of development and will lead to more efficient development. The Habitat Predictive Models are prime examples of improvements that would promote the orderly and responsible development of resource uses (i.e. oil and gas, grazing, habitat improvement projects, mining, etc). The habitat models will identify three levels of importance: occupied habitat (highest probability), suitable habitat (mid-probability), and potential habitat (lowest probability). The highest and mid-probability areas will allow BLM and lessees to use in planning on a landscape level. This planning tool will aid in not only species conservation, but also in streamlining of implementation level issues. Any level of probability area (high, mid, low) will also provide companies an idea of where pre-development surveys will be required to occur to assess direct and indirect impacts in the NEPA process.

Deliverable A will be referred to as CONUS Data Service. Deliverable B will be referred to as Expert Botanical Analysis, Deliverable C will be referred to as Conservation Analysis and Mapping, and Deliverable D will be referred to as Predictive Habitat Models.

Deliverable A, CONUS Data Service:

The BLM will acquire licensed data from a nationally-recognized source specializing in combined state heritage data for A) CONUS BLM States and AK.

Deliverable A will provide BLM with 150 annual one-year licenses (2019 through 2020) to access the MJD in its analysis of at-risk plants and animals over landscape and regional scales in BLM western states to include: CA, WA, AK, OR, NV, NM, UT, WY, CO, MT, ID, AZ.

With Eastern States funding AR, LA, MN, OK, TX, ND, SD, ND, MO, KS, OK, TX, MO, MN, WI, MD, AL, AR, FL, GA, KY, LA, MS, NC, SC, TN, VA and WI may be included.

The Contractor will provide precise species location data for all counties in listed BLM states, except for a few possible exceptions where certain states may restrict either geographic access (e.g., to certain counties of interest) or precision of the data (e.g., provide species data on a coarser scale than precise locations). Negotiations with the state programs will be coordinated by the contractor before the data is provided on December 1, 2019, and each year forward through 2024. Known data restrictions will be provided to BLM prior to annual Data License Agreement renewals. The contractor will track BLM Species Status Species (e.g. federally listed and Bureau Sensitive) in the least.

The MJD dataset will be provided as a geodatabase to be used by a specified number of BLM staff (e.g., up to 100 staff), as specified in the Data License Agreement to be developed with BLM as part of this work for Western Data. The Contractor will provide the Data Users all necessary data, metadata, and support necessary to ensure proper use of the Licensed Dataset.

Collaborate on the development of observation data standards.

a. The Contractor will Collaborate with BLM regarding developing consistency with observation data standards and methods for Element Occurrence (EO’s) and aggregation of observations into EO’s.

b. The Contractor will develop and deliver a webinar targeted to BLM field staff on automating field observation data collection.

Identify and address data gaps throughout the life cycle.

1. The Contractor will define new heritage program information gaps (known geographic, taxonomic, and other information gaps) in the MJD, as new species and data is acquired and will provide BLM with program information gap analysis, on an annual basis prior to deliver of the annual data service.

1. The Contractor will conduct, analyze, and report on a survey of western state programs to assess 1) the data life cycle, 2) data backlogs, and 3) BLM field and state office data exchange processes. This will include a program-by-program assessment of taxonomic and geographic data gaps, issues with data collection, data entry, element data development (taxonomy and ranking), negative data, and data backlogs. This survey will involve appropriate BLM field staff and Heritage Program staff working together to meaningfully audit the full data life cycle while working with the contractor to identify gaps and issues between the three organizational levels. (BLM, State Heritage Programs, Contractor)

1. The Contractor will collaboratively develop a prioritized approach for addressing the data gaps identified by Tasks (a) and (b) of this section.

1. Improve data delivery for security and ease of use.

Data delivery tools for BLM via Contractor updates to the MJD data delivery vehicle(s), will be provided to BLM as soon as they are developed and tested. BLM and Contractor Contact:

Deliverable A: BLM Name Kim Tripp Position T/E Program Lead Phone 202-912-7237 Contractor Name______________________________ Position____________________________ Phone___________________

Deliverable B, Expert Botanical Analysis:

Contractor will provide botanical species analyses based on best-available scientific, nationally consistent biodiversity data provided by both the Contractor and State Natural Heritage Programs. Conservation target species used for this analysis include rare plants that are regarded as critically imperiled or imperiled (G1, G2, or G3) throughout their range and as identified by BLM Plant Conservation & Restoration Program Lead with NatureServe Lead Botanist.

The Contractor will provide deliverables, in the form of a report, excel file and presentation that includes updated conservation status assessment, locality information, and other information pertinent to rare plant conservation.

BLM and Contractor Contact:

Deliverable B: BLM Name Peggy Olwell Position Botanist Phone 202-912-7273 Contractor Name______________________________ Position____________________________ Phone___________________

Deliverable C, Conservation Analysis, Modelling and Mapping:

Conservation target species used for this section on analysis, updated species ranking, modelling or mapping include plants and animals that are either federally listed under the Endangered Species Act, identified as BLM sensitive species, or are regarded as critically imperiled or imperiled (G1, G2, G3) throughout their range according to State Natural Heritage Programs.

After analysis of data gaps, the Contractor shall develop observation data standards as well as observation to EO methods to support consistency throughout the network. The Contractor will review the Element Occurrence in light of technological and data advances brought by the new information age. Many Heritage Programs are collecting observations in addition to Element Occurrences, and several programs have developed methods for aggregating observations into EO’s. As the umbrella organization of the network, the Contractor will coordinate and development observation data standards with the collaboration of the BLM data standard group (e.g. employees in the NOC and Washington Office).

Species maps may be based on known occurrences and potential habitats for the species. Specific analyses, modelling and/or mapping will be determined in coordination with BLM staff and may include:

· For high priority species (for example, species with a large percentage of known occurrences on BLM lands), create maps of the species that show locations of the species on BLM lands and other potential or known habitats.

· For high priority species (for example, species with a large percentage of known occurrences on both BLM and other Federal lands), create maps of the species and/or habitats that show locations on BLM and other Federal lands.

· For high priority species (for example, species with a large percentage of known occurrences on both BLM and other Federal lands), create collaborative models for species and/or habitats, with given parameters and variable data sets as determined and pre-negotiated, on BLM and other Federal lands.

BLM and Contractor Contact:

Deliverable C: BLM Name Frank Quamen Position Wildlife Program Lead Phone 202-912-7274 Contractor Name______________________________ Position____________________________ Phone___________________ Deliverable D:

Contractor will provide species distribution models to the BLM and make available for public use, both to view and to download. The models will be used within the BLM GIS program and all metadata will be FGDC compliant (see Appendix 1). The habitat models will identify three levels of importance: occupied habitat (highest probability), suitable habitat (mid-probability), and potential habitat (lowest probability).

· The Contractor will collaborate with BLM resource specialists to ensure the most relevant inputs are being used for the modelling programs.

· Work with local experts or other agencies to acquire or develop additional layers applicable to target species (i.e., derive gypsum predictor layer)

· The Contractor will complete a comprehensive ensemble modelling approach.

· Generate outputs to reflect additional algorithms and develop comparative confidence statistics.

· Complete field surveys in collaboration with the BLM to verify the model accuracy.

· The models will also be peer-reviewed to ensure defensibility.

· Models will be provided to the BLM-National Operations Center with FGDC compliant metadata. Additionally models will be provided to partners and stakeholders (i.e. industry). All users require a version to use in-house with the respective GIS, mapping, or planning programs.

· Once model outputs are completed, the Contractor will collaborate with the BLM State Botanist to provide the BLM Field Office and other stakeholders (i.e. industry) with a webinar and written instructions on how to use the habitat model.

Deliverable D: BLM Name Zoe Davidson Position Botanist Phone 505-901-7524 Contractor Name______________________________ Position____________________________ Phone___________________

Timelines Deliverable A: One Year Data License Access BLM CONUS (Western States) - Active December 1, 2019 through November 30, 2020.

Deliverable B, C, and D: Start Dates: October 1, 2019. Due Date: September 30, 2019.

Appendix 1, See also: attached zip files

BLM Metadata Requirements and Guidance for Contracted Data Products Data Documentation

The BLM’s data resources are high-value business assets that must be documented and maintained in accordance with other critical business assets. Proper documentation allows internal and external customers to improve business and technical understanding of data and data-related processes by helping them to:

a) Find and access the data;

b) Understand data that are found;

c) Understand the reliability of data;

d) Understand the intended use of the data;

e) Know how and when the data were collected and by whom;

f) Know how and when data are maintained;

g) Understand any ways in which the data are manipulated; and

h) See any warnings or disclaimers that may apply to the data.

A successful project always employs rigorous standards for maintaining, managing, and applying data and derived information. The data and resultant information must be carefully managed, documented, and applied to withstand public, scientific, and legal scrutiny, and at the same time, facilitate the efficient development and operation of the Bureau’s mapping and data management systems such as GIS. For these reasons, the corporate data used in these projects require a high level of consistency, standardization, and established quality control procedures.

Metadata Metadata is the term used to describe the content, quality, condition, and other characteristics of data. By Executive Order, geospatial data used by the Bureau must be accompanied by metadata in the format set forth by the Federal Geographic Data Committee and be accessible to all interested parties.

BLM policy further requires the development of FGDC compliant metadata for spatial data and Dublin Core BLM compliant metadata for non-spatial data. The primary documents that establish this policy are listed below. .

a) BLM Data Management Handbook (H-1283-1, especially Chapter 6: Metadata and Data Documentation),

b) BLM Land Use Planning Handbook (H-1601-1),

c) BLM Land Use Planning Manual (M-1601, especially Appendix G: Managing and Applying Data and Information).

d) The Content Standard for Digital Geospatial Metadata (CSDGM), Version 2, (FGDC-STD-001-1998) (www.fgdc.gov)

e) Dublin Core Metadata Initiative (dublincore.org) – customized implementation for BLM non-spatial resources and supporting information The Content Standard for Digital Geospatial Metadata (CSDGM), Version 2, (FGDC-STD-001-1998) 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.

BLM has developed the BLM FGDC CSDGM Metadata Requirements Profile for geospatial data. This guidance is provided in the form of a template that shows which elements are required to be populated and which elements are recommended. Contractors performing data collection for BLM use are required to use this guidance to collect FGDC compliant metadata that will satisfy the BLM requirements. There are three categories of guidance specified for each metadata element: Required, Required if Applicable, and Recommended. The Required if Applicable elements will be enforced if it is deemed that those elements apply to the specific dataset being documented. For example: if input datasets were used in the creation of another dataset, those input datasets should be listed in the Data Quality\Lineage\Source Information elements - as those are Required if Applicable. Additionally, for the Recommended elements, if that information is known about a dataset, you are encouraged to provide it.

All datasets created by the contractor must have a comprehensive metadata record, with particular focus on the quality and completeness of the following elements:

· Abstract: brief narrative summary of the dataset

· Purpose: summary of the intentions with which the dataset was developed, and the appropriate purposes for which the data may be used.

· Time Period: point in time, or range of dates corresponding to the data

· Data Quality (attribute and positional accuracy): statements about the expected quality of the data (see Quality Assurance section below)

· Source Citations: reference identification for each source. The source citation shall include, at a minimum, Title, Originator, and Publication Date.

· Processes: explanation of events conducted against the data, these could include tools, scripts, models, and other geoprocessing actions.

· Entity/Attribute names and definitions: details about the information content

· Enumerated attribute domains: where appropriate, valid values that can be assigned to an attribute shall be enumerated with names and descriptions

Metadata items referring to publication (i.e. publisher, publication date in FGDC, and dc:date in Dublin Core, and links to published data in both) can be omitted in contractor created datasets as BLM will evaluate suitability for publication and populate those items if published. Do not change these items in metadata for source or input datasets and provide that metadata directly from the source, unchanged with respect to publication items.

Constraints (FGDC access/use constraints, distrib liab; DC license, rights elements) - provide any constraints on the data that you are aware of: use of restricted or license data as input, products where input metadata states a restriction of any sort on derived/value-added products, products where the contractor requested permission to use but that does not directly pass on to the BLM. BLM will evaluate and apply the appropriate agency constraint value to enhance what is provided by the contractor. Do not change these items in metadata for source or input datasets if values exist, and provide that metadata directly from the source, unchanged with respect to constraint items.

Data Ownership and Use

a) Data Ownership

· All resources created by the contractor - data, models, products, code, etc. are property of the BLM unless otherwise agreed to by the BLM at the onset of the project.

· Individual data layers supplied by other sources are the property of and under the stewardship of the source organization. The BLM Project Coordinator is responsible for maintaining an index catalog of the source data.

· BLM data may not be trademarked or copyrighted.

b) Data Use Agreements

· The BLM must exercise due diligence in its use of non-BLM geospatial data. Therefore, the following information must be investigated before downloading.

· Do metadata exist?

· Are there any use/access restrictions?

· Are there known source and contact information for the data?

· Are attribute codes explained adequately in the metadata?

1) If no, are the codes explained in an easily available document?

· Are units of measure clear in the attributes?

· Are the projection and datum known?

· Might the data be sensitive (i.e. archaeological, cave, sensitive species, trademark, copyright, commercially protected or homeland security protected information)?

· After the data are downloaded, the following information must be known and documented in the metadata:

· Is there any Privacy Act personal information contained in the data?

· Is there any confidential information that may be one of the nine FOIA exceptions? Please see Appendix 6 for a listing of the FOIA Exemptions (from DOI Handbook located at http://www.doi.gov/foia/foiahandbook.html)

· Can BLM share the data with others via the internet without written permission? If not, can the BLM share the data with others if written permission is granted?

· Can “value added” information be incorporated and shared by BLM without restrictions?

If data are acquired from a public internet site but do not include any information in the Use or the Constraints portion of the metadata (or do not have metadata), then the BLM or its contractor will label the data as public. One exception to this rule of thumb is data downloaded from the internet that contain Privacy Act or personally identifiable information.

Whenever data are not collected from a public internet source and an assessment for Privacy Act information or confidential data is not documented in the metadata, the data are to be treated as confidential information. In such an instance, the BLM and its contractors will attempt to secure an assessment from the source agency and approval to include that assessment in the metadata. If the assessment and approval are not forthcoming from the source, the data will be documented as “Confidential” and subsequent users must contact the source agency for viewing or use of the data. Further use of such data by the BLM must be made on a case by case basis (by the BLM).

c) Data Sharing Agreement

· If BLM contractors will be handling confidential data, a confidential data sharing agreement between the contractor and the BLM must be completed. Likewise, any partner agency or other entity that would like access to BLM confidential data, either to view a map containing confidential information, or to download data, must also complete a Confidential Data Sharing Agreement according to BLM Records Management Policy contained in Manual 1278.

· All contractors have signed a Non-Disclosure Agreement (NDA) that serves as the basis for proper use and sharing of sensitive datasets. Any dataset flagged as sensitive and provided by the BLM shall not be used for any other purpose than the project for which the NDA is signed.

Description of Data Quality

1. Data Quality Guidance

· For BLM purposes, data quality means “fitness for the intended use.” Data quality may be considered as the sum of all data characteristics that determine how useful the data are in performing specific business processes.

· There is no universal quantitative standard of quality that all BLM data should meet. Rather, the right quality is the quality that minimizes the risk of failure. The International Standards Organization (ISO) also defines “quality” in a way that supports this viewpoint. ISO 8402 defines quality as: “The totality of characteristics of an entity that bear on its ability to satisfy stated and implied needs.”

· The DOI Office issued data quality guidance in August of 2008. The “Data Quality Management Guide” is to be used as guidance for evaluating data quality for DOI and thus BLM. The documentation has numerous examples of methods for measuring alpha-numeric data quality and thus geospatial attribute quality. While there are no specific examples for geospatial data quality measures relating to geometry or topology, there is a draft addendum available that addresses those issues. The BLM Information Quality Guidelines, updated February 9, 2012, supplement the DOI guidelines.

2. Characteristics of Data Quality

· Objectivity consists of:

1) presentation, which focuses on whether disseminated information is being presented in an accurate, clear, complete, and unbiased manner within a proper context, and

2) substance, which focuses on ensuring accurate, usable, and reliable information

· Utility refers to the usefulness of the information to its intended users, from the perspectives of both internal network users and the general public

· Integrity refers to the security of information, e.g., protection from unauthorized access or revision to ensure that the information is not compromised through corruption or falsification

3. From these characteristics, DOI guidance identifies eleven dimensions by which data quality can be evaluated (DOI 2008) and documented as illustrated in the Table 1 below.

Table 1: Data Quality Criteria (Source: DOI Data Quality Management Guide, 2008.

ISO 19115 Topic Categories To be ISO (International Standards Organization) compliant at this time, using an FGDC metadata editor, add ISO keyword (text below within parentheses) and cite ISO 19115 Topic Category as Theme Keyword Thesaurus.

ISO keywords

· (boundaries)—Legal land descriptions

· (farming)—The rearing of animals or cultivation of plants. For example, resources describing irrigation, aquaculture, herding, and pests and diseases affecting crops and livestock.

· (climatologyMeteorologyAtmosphere)—Atmospheric processes and phenomena. For example, resources describing cloud cover, weather, atmospheric conditions, climate change, and precipitation.

· (biota)—Naturally occurring flora and fauna. For example, resources describing wildlife, biological sciences, ecology, wilderness, sea life, wetlands, and habitats.

· (economy)—Economic activities or employment. For example, resources describing labor, revenue, commerce, industry, tourism and ecotourism, forestry, fisheries, commercial or subsistence hunting, and exploration and exploitation of resources, such as minerals, oil, and gas.

· (planningCadastre)—Land use. For example, resources describing zoning maps, cadastral surveys, and land ownership.

· (society)—The characteristics of societies and cultures. For example, resources describing natural settlements, anthropology, archaeology, education, traditional beliefs, manners and customs, demographic data, crime and justice, recreational areas and activities, social impact assessments, and census information.

· (elevation)—Height above or below sea level. For example, resources describing altitude, bathymetry, digital elevation models, slope, and products derived from this information.

· (environment)—Environmental resources, protection, and conservation. For example, resources describing pollution, waste storage and treatment, environmental impact assessment, environmental risk, and nature reserves.

· (structure)—Man-made construction. For example, resources describing buildings, museums, churches, schools, hospitals, factories, housing, monuments, and towers.

· (geoscientificInformation)—The earth sciences. For example, resources describing geophysical features and processes; minerals; the composition, structure, and origin of the earth’s rocks; earthquakes; volcanic activity; landslides; gravity information; soils; permafrost; hydrogeology; and erosion.

· (health)—Health services, human ecology, and safety. For example, resources describing human disease and illness, factors affecting health, hygiene, mental and physical health, substance abuse, and health services.

· (imageryBaseMapsEarthCover)—Basemaps. For example, resources describing land cover, topographic maps, and classified and unclassified images.

· (inlandWaters)—Inland water features, drainage systems, and their characteristics. For example, resources describing rivers and glaciers, salt lakes, water use plans, dams, currents, floods, water quality, and hydrographic charts.

· (location)—Positional information and services. For example, resources describing addresses, geodetic networks, postal zones and services, control points, and place names.

· (intelligenceMilitary)—Military bases, structures, and activities. For example, resources describing barracks, training grounds, military transportation, and information collection.

· (oceans)—The features and characteristics of salt water bodies excluding inland waters. For example, resources describing tides, tidal waves, coastal information, and reefs.

· (transportation)—The means and aids for conveying people and goods. For example, resources describing roads, airports and airstrips, shipping routes, tunnels, nautical charts, vehicle or vessel location, aeronautical charts, and railways.

· (utilitiesCommunication)— Energy, water and waste systems, and communications infrastructure and services. For example, resources describing hydroelectricity, geothermal, solar, and nuclear sources of energy, water purification and distribution, sewage collection and disposal, electricity and gas distribution, data communication, telecommunication, radio, and communication networks.

BLM Theme Keywords At least one of the BLM-THEME keywords is required to be present in the metadata. See included document BLM Keyword Thesaurus vers 1.2.docx in the provided files for the domain. The thesaurus name is “BLM-THEME” BLM State keywords At least one of the BLM-STATE keywords is required to be present in the metadata. The domain consists of geopolitical state names and ‘Eastern States’, and the thesaurus name is “BLM-STATE”.

Related References Data Administration/Management

· BLM Manual 1283 – Data Administration and Management

· BLM Handbook H 1283 1 - Data Administration and Management

· BLM Handbook H 1283 2 – Data Administration and Management

· BLM Manual 1220 - Records and Information Management

· BLM Manual 1270 – Records Administration

· BLM Manual 1278 - External Access to BLM Records

Data Quality

· Information/Data Quality Act

· OMB Guidelines for Ensuring and Maximizing the Quality, Objectivity, Utility, and Integrity of Information Disseminated by Federal Agencies

· http://www.whitehouse.gov/omb/fedreg/reproducible.html

· DOI Information Quality Guidelines

· http://www.doi.gov/ocio/information_management/upload/515Guides.pdf

· BLM Information Quality Guidelines

· http://www.blm.gov/pgdata/etc/medialib/blm/national/national_page.Par.7549.File.dat/guidelines.pdf

· Federal Geographic Data Committee Metadata Content Standard

· http://www.fgdc.gov/metadata/geospatial-metadata-standards

Land Use Planning, Land Health and other National Standards

· BLM Manual 1601 - Land Use Planning Manual

· http://www.blm.gov/style/medialib/blm/wo/Information_Resources_Management/policy/blm_manual.Par.96580.File.dat/1601.pdff

· BLM Handbook 1601-1 Land Use Planning Handbook

· http://www.blm.gov/style/medialib/blm/wo/Information_Resources_Management/policy/blm_handbook.Par.38665.File.dat/h1601-1.pdf

· BLM Manual 4180 Rangeland Health

· http://www.blm.gov/style/medialib/blm/wo/Information_Resources_Management/policy/blm_manual.Par.23764.File.dat/4180.pdf

· § 4180.1 Fundamentals of rangeland health

· http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&sid=efd4de4cc52ef90a7501b559708d1ba8&rgn=div6&view=text&node=43:2.1.1.4.92.9&idno=43

· Federal Geographic Data Committee Metadata Content Standard

· http://www.fgdc.gov/metadata/geospatial-metadata-standards

Freedom of Information Act and Privacy Act

· Department of the Interior Freedom of Information Act Handbook

· http://www.doi.gov/foia/upload/handbook_2004.pdf

· Freedom of Information Act Website

· http://www.foia.gov/

· Department of the Interior Privacy Program website

· http://www.doi.gov/ocio/information_assurance/privacy/index.cfm

· Department of Justice Privacy Act of 1974 website

· http://www.justice.gov/opcl/privacyact1974.htm

USGS Cartographic Standards

· Contractors are requested to follow FGDC’s Digital Cartographic Standard for Geologic Map Symbolization. The website is: http://ngmdb.usgs.gov/fgdc_gds/geolsymstd.php.

· Contractors are requested to follow USGS Topographic Map Symbol Standards as documented at http://egsc.usgs.gov/isb/pubs/booklets/symbols/

National Systems

· National Archives & Records Administration (NARA )

· www.archives.gov