Sensitivity of Coastal Environments and Wildlife to Spilled Oil: Southern California: FISHL (Fish Lines)
Office of Response and Restoration
Data Set
(DS)
| ID: 40819
| Published / External
Created: 2017-04-05
|
Last Modified: 2023-05-30
Project (PRJ) | ID: 46696
ID: 40819
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | Sensitivity of Coastal Environments and Wildlife to Spilled Oil: Southern California: FISHL (Fish Lines) |
---|---|
Short Name | scal_fishl |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2010-03 |
* » Abstract |
This data set contains sensitive biological resource data for threatened/endandered/rare and/or anadromous fish species in Southern California. Vector lines in this data set represent threatened/endandered/rare and/or anadromous fish species in streams and rivers. Species-specific abundance, seasonality, status, life history, and source information are stored in relational data tables (described below) designed to be used in conjunction with this spatial data layer. This data set comprises a portion of the ESI data for Southern California. ESI data characterize the marine and coastal environments and wildlife by their sensitivity to spilled oil. The ESI data include information for three main components: shoreline habitats, sensitive biological resources, and human-use resources. See also the FISH data layer, part of the larger Southern California ESI database, for additional fish information. |
* Purpose |
The ESI data were collected, mapped, and digitized to provide environmental data for oil spill planning and response. The Clean Water Act with amendments by the Oil Pollution Act of 1990 requires response plans for immediate and effective protection of sensitive resources. |
Notes |
2101 |
Other Citation Details |
Prepared by Research Planning, Inc., Columbia, South Carolina for the National Oceanic and Atmospheric Administration (NOAA), National Ocean Service, Office of Response and Restoration, Emergency Response Division, Seattle, Washington. |
• Supplemental Information | |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category | biota |
ISO 19115 Topic Category | environment |
NOS Data Explorer Topic Category | Environmental Monitoring |
None | Coastal resources |
None | Coastal Zone Management |
None | Environmental Monitoring |
None | ESI |
None | Fish |
None | Oil spill planning |
None | Sensitivity maps |
None | Wildlife |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* Spatial Keywords
Thesaurus | Keyword |
---|---|
None | Southern California |
Stratum Keywords
Thesaurus | Keyword |
---|---|
Instrument Keywords
Thesaurus | Keyword |
---|---|
Platform Keywords
Thesaurus | Keyword |
---|---|
Physical Location
• » Organization | Office of Response and Restoration |
---|---|
• » City | Silver Spring |
• » State/Province | MD |
• Country | |
• » Location Description |
Data Set Information
* Data Set Scope Code | Data Set |
---|---|
• Data Set Type | |
• Maintenance Frequency | None Planned |
Maintenance Note | |
» Data Presentation Form | vector digital data |
• Entity Attribute Overview |
In addition to the geographic data layers, six relational attribute or data tables (BIORES, BREED, SEASONAL, SOURCES, SPECIES, and STATUS) are used to store the complex biological data in the ESI data structure. The geographic data layer containing biological resource information (in this case, FISHL) is linked to the Biological Resources table (BIORES) using the unique ID and the lookup table BIO_LUT, or it can be linked directly using RARNUM. The ID is a unique combination of the atlas number (for the Southern California atlas, the number is 209), an element/layer specific number (BIRDS are layer 1, FISH are layer 2, etc.), and a unique record number. The RARNUM represents a unique combination of species, seasonalities, concentrations, and source information. For each of these groupings, a number is generated. That number is concatenated with the atlas number to create a "resource at risk" number that is unique across atlases. BIORES and the other relational data tables are described in detail in the Detailed_Description sections. See the Browse_Graphic section for a link to the entity-relationship diagram, which describes the way these tables relate to the geographic data layers and other attribute tables in the ESI data structure. Due to the complexity of the relational database model, the data items are also post-processed into a flat file format. This table, called BIOFILE, may be used in place of the relational files described below to ease simple data queries. The items in the flat file are ELEMENT, SUBELEMENT, NAME, GEN_SPEC, S, F, NHP, DATE_PUB, CONC, JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC, BREED1, BREED2, BREED3, BREED4, BREED5, RARNUM, G_SOURCE, S_SOURCE, and BREED. All of these items are the same as their counterparts in the individual data tables (described in the Detailed_Description sections), except the BREED1-BREED5 and BREED items. BREED is a newly generated variable used to link to the BREED_DT data table, a modified, more compact version of the relational BREED data table. BREED1-BREED5 give a text summary of when each life stage occurs within the associated map object. The life stages referred to are the same as those listed in the Detailed_Description of the BREED data table. The link to the BIOFILE may be made through the BIO_LUT, using ID to link to RARNUM, or BIOFILE may be linked directly to the RARNUM in each of the geographic layer's attribute data tables. As mentioned, BREED_DT is an auxiliary support data table to the flat file structure, which allows the user to do searches based on month for seasonal breeding activities. The link from the flat file to BREED_DT is the BREED item. A second supporting data table is SOURCES. This is the same as the source file described above, and the link from the flat file is both G_SOURCE and S_SOURCE. It should be noted that although the flat file eases data query, it is not a normalized database structure, and actual updates performed by the states and other responsible agencies should be done using the relational data tables. The entity-relationship diagram, describing relationships between attribute tables in the ESI data structure, does NOT include the BIOFILE data table, and this data table is NOT described in a Detailed_Description section. |
Entity Attribute Detail Citation |
A complete description of entity types, attributes, and attribute values for ESI atlases can be found in the NOAA ESI Guidelines (http://response.restoration.noaa.gov/esi_guidelines). |
Entity Attribute Detail URL | |
Distribution Liability |
Although these data have been processed successfully on a computer system at the National Oceanic and Atmospheric Administration, no warranty, expressed or implied, is made by NOAA regarding the utility of the data on any other system, nor shall the act of distribution constitute any such warranty. NOAA warrants the delivery of this product in computer-readable format, and will offer a replacement copy of the product when the product is determined unreadable by computer input peripherals, or when the physical medium is delivered in damaged condition. |
Data Set Credit | This project was supported by the National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Office of Response and Restoration (OR&R), Emergency Response Division (ERD), Seattle, Washington; the Department of Homeland Security (DHS), United States Coast Guard (USCG), Office of Incident Management and Preparedness Washington, D.C.; and the California Department of Fish and Game (CDF&G), Office of Spill Prevention and Response (OSPR), Sacramento, California. |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2010-03 |
Date Effective To | |
Position | ESI Program Manager |
Address |
7600 Sand Point Way NE Seattle, WA 98115 |
Email Address | orr.esi@noaa.gov |
Phone | |
Fax | |
Mobile | |
URL | |
Business Hours | |
Contact Instructions |
* » Support Role | Distributor |
---|---|
* » Date Effective From | 2010-03 |
Date Effective To | |
Position | ESI Program Manager |
Address |
7600 Sand Point Way NE Seattle, WA 98115 |
Email Address | orr.esi@noaa.gov |
Phone | |
Fax | |
Mobile | |
URL | |
Business Hours | |
Contact Instructions |
* » Support Role | Metadata Contact |
---|---|
* » Date Effective From | 2010-03 |
Date Effective To | |
Position | ESI Program Manager |
Address |
7600 Sand Point Way NE Seattle, WA 98115 |
Email Address | orr.esi@noaa.gov |
Phone | |
Fax | |
Mobile | |
URL | |
Business Hours | |
Contact Instructions |
* » Support Role | Point of Contact |
---|---|
* » Date Effective From | 2010-03 |
Date Effective To | |
Position | ESI Program Manager |
Address |
7600 Sand Point Way NE Seattle, WA 98115 |
Email Address | orr.esi@noaa.gov |
Phone | |
Fax | |
Mobile | |
URL | |
Business Hours | |
Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
Extents
Currentness Reference | The data were compiled during 2008-2010. The currentness dates for the data range from 2005 to 2009 and are documented in the Lineage section. |
---|
Extent Group 1
Extent Description |
---|
Extent Group 1 / Geographic Area 1
* » W° Bound | -120.601 |
---|---|
* » E° Bound | -117.001 |
* » N° Bound | 34.5 |
* » S° Bound | 32.445 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2005 |
End | 2009 |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Spatial Information
Spatial Resolution
Angular Distance | |
---|---|
Angular Distance Units | |
Horizontal Distance | |
Horizontal Distance Units | |
Vertical Distance | |
Vertical Distance Units | |
Equivalent Scale Denominator | |
Level of Detail Description |
Spatial Representation
Grid Representation Used? | |
---|---|
Vector Representation Used? | Yes |
Text / Table Representation Used? | |
TIN Representation Used? | |
Stereo Model Representation Used? | |
Video Representation Used? |
Grid Representation
Dimension Count | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Cell Geometry | |||||||||||||
Transformation Parameter Available? | |||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
Vector Representation
Topology Level | |
---|---|
Complex Object Present? | |
Complex Object Count | |
Composite Object Present? | |
Composite Object Count | |
Curve Object Present? | Yes |
Curve Object Count | 298 |
Point Object Present? | |
Point Object Count | |
Solid Object Present? | |
Solid Object Count | |
Surface Object Present? | Yes |
Surface Object Count | 89 |
Vector Representation
Topology Level | |
---|---|
Complex Object Present? | |
Complex Object Count | |
Composite Object Present? | |
Composite Object Count | |
Curve Object Present? | |
Curve Object Count | |
Point Object Present? | |
Point Object Count | |
Solid Object Present? | |
Solid Object Count | |
Surface Object Present? | |
Surface Object Count |
Reference Systems
Reference System
EPSG Code | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Access Information
Data License | |
---|---|
Data License URL | |
Data License Statement | |
* » Security Class | Unclassified |
* Security Classification System | |
Security Handling Description | |
• Data Access Policy | |
» Data Access Procedure |
Contact NOAA for distribution options (see Distributor). ESI data are processed into multiple formats to make them useful to the widest community of GIS/mapping users. Distribution formats include Geodatabase; ARC export, MOSS, and Shape files; and MARPLOT map folders. An ArcMap .mxd file, an ArcView 3.x ESI project, and an ESI_Viewer product for use with the MARPLOT data are also included on the distribution CDs/DVDs for ease of use of the ESI data. The database files are distributed both in the NOAA standard relational database format (see NOAA Technical Memorandum NOS ORCA 115) and in a simplified desktop flat file format. This metadata document includes information on both of these database formats.; |
• » Data Access Constraints |
None |
• Data Use Constraints |
DO NOT USE MAPS FOR NAVIGATIONAL PURPOSES. Besides the above warning, there are no use constraints on these data. Note that the ESI database should not be used to the exclusion of other pertinent data or information held by state or federal agencies or other organizations. Likewise, information contained in the database cannot be used in place of consultations with environmental, natural resource, and cultural resource agencies, or in place of field surveys. Recognize that the information contained in the ESI database represents known concentration areas or occurrences of natural, cultural, and human-use resources, but does not necessarily represent the full distribution or range of each species or resource. This is particularly important to recognize when considering potential impacts to protected resources, such as endangered species, wetlands, etc. Acknowledgment of the originators, publishers, contributors, and sources listed would be appreciated in products derived from these data. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Archive Information
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
URLs
URL | http://response.restoration.noaa.gov/esi |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
Activity Log
Activity Time | 2010-09-27 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Date that the source FGDC record was last modified. |
Activity Time | 2017-04-05 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Converted from Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details. |
Activity Time | 2017-09-13 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Partial upload of Spatial Info section only. |
Activity Time | 2017-11-01 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Replaced entire Lineage section to populate new Source Contribution field. |
Activity Time | 2018-02-08 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Partial upload of Positional Accuracy fields only. |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Issues
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Technical Environment
Description |
The software packages used to develop the atlas are Environmental Systems Research Institute's ARC/INFO(R) (version 9.3) and SQL SERVER(R) (version 2000). The hardware configuration is PC's with Windows Operating System (2000/XP/2003). The Spatial_Data_Organization Information section refers only to the source files in the ARC export format. The following files are included in the data set: acp.e00, birds.e00, esi.e00, fish.e00, fishl.e00, habitats.e00, hydro.e00, index.e00, invert.e00, m_mammal.e00, mgt.e00, nests.e00, reptiles.e00, socecon.e00, and t_mammal.e00. Associated relational and desktop data tables provided in Arc export and text format are bio_lut.e00, biofile.e00, biores.e00, breed.e00, breed_dt.e00, seasonal.e00, soc_dat.e00, soc_lut.e00, sources.e00, species.e00, and status.e00. |
---|
Data Quality
Representativeness | |
---|---|
Accuracy |
A multi-stage error checking process is used to verify both attribute accuracy and logical consistency throughout data production. The process includes a standardized data entry methodology, hardcopy data review by in-house and external resource experts, a final Quality Assurance/Quality Control (QA/QC) process, and multiple automated logical consistency checks. Quantitative data (such as densities, counts, abundances, or concentrations) provided by resource experts for inclusion in the data set may vary widely in attribute accuracy, depending upon the methodology used to collect and compile such data. For a more detailed evaluation of source data attribute accuracy, contact the sources listed in the Lineage section. |
Analytical Accuracy | |
Horizontal Positional Accuracy |
Spatial components for the biological data layers can come from expert interviews, hardcopy, or digital sources. Some of the spatial components of the biological data layers may have been developed using regional experts who estimate concentration areas. It is difficult to estimate the positional accuracy of such data, except to state that they are compiled on hardcopy base maps with a scale of 1:24,000. Some of the spatial components of the biological data sets are developed from pre-existing digital or hardcopy sources and reflect the positional accuracy of these original data. Note that biological resource data by their very nature are considered "fuzzy", and this should be understood when considering the positional accuracy of vector digital objects representing these resources. See the Lineage and Process_Description sections for more information on the original source data and how these data were integrated or manipulated to create the final data set. |
Vertical Positional Accuracy | |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
These data represent a synthesis of expert knowledge and available hardcopy documents on threatened/endandered/rare and/or anadromous fish species in streams and rivers. See also the FISH data layer, part of the larger Southern California ESI database, for additional fish information. These data do not necessarily represent all fish occurrences in Southern California. The following species are included in this data set: (Species_ID, Common Name, Scientific Name [n/a if not applicable]): 74, Rainbow trout, Oncorhynchus mykiss; 226, Tidewater goby, Eucyclogobius newberryi; 1142, Arroyo chub, Gila orcuttii. |
Conceptual Consistency |
A multi-stage error checking process, described in the above Attribute_Accuracy_Report, is used to verify both attribute accuracy and logical consistency throughout data production. This process includes multiple automated logical consistency checks that test the files for missing or duplicate data, rules for proper coding, GIS topological consistencies (such as dangles, unnecessary nodes, etc.), and SQL SERVER(R) to ARC/INFO(R) consistencies. A final review is made by the GIS manager, where the data are written to CD/DVD and the metadata are written. After the data are delivered to NOAA, they are again subjected to a number of quality and consistency checks. In the process of checking for topological and database consistencies, new ID's and RARNUM's or HUNUM's are also generated. The new ID's are a combination of atlas number, element number, and record number. In addition, the value used to represent the element is modified to reflect the type of feature being mapped. In the case of an element that is normally represented by a point or polygon, a value of 20 is added to the standard element value for mapping of linear features. In the case where an element usually mapped as a polygon is represented by a point, a value of 30 is added to the regular element value. The RARNUM's are also modified to include the atlas number, so multiple atlases can be combined and RARNUM's remain unique. RARNUM's are redefined on an element basis, so "resource at risk" groupings will contain only a single element. HUNUM's are also modified to include the atlas number. |
» Quality Control Procedures Employed |
Data Management
» Have Resources for Management of these Data Been Identified? | |
---|---|
» Approximate Percentage of Budget for these Data Devoted to Data Management | |
» Do these Data Comply with the Data Access Directive? | |
» Is Access to the Data Limited Based on an Approved Waiver? | |
» If Distributor (Data Hosting Service) is Needed, Please Indicate | |
» Approximate Delay Between Data Collection and Dissemination | |
» If Delay is Longer than Latency of Automated Processing, Indicate Under What Authority Data Access is Delayed |
|
» Actual or Planned Long-Term Data Archive Location | |
» If World Data Center or Other, Specify | |
» If To Be Determined, Unable to Archive, or No Archiving Intended, Explain |
|
» Approximate Delay Between Data Collection and Archiving | |
» How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive? |
|
Lineage
» Lineage Statement |
---|
Sources
Citation Title | AREA CONTINGENCY PLAN (ACP) SECTOR LOS ANGELES/LONG BEACH; 2008 USCG SECTOR SAN DIEGO AREA CONTINGENCY PLAN (ACP) |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | CDF&G, OFFICE OF SPILL PREVENTION AND RESPONSE (OSPR), DEPARTMENT OF HOMELAND SECURITY (DHS), UNITED STATES COAST GUARD (USCG) |
Publish Date | 2008-01-01 |
Extent Type | Discrete |
Extent Start Date/Time | 2008 |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
FISHL INFORMATION | Source Geospatial Form: HARDCOPY TEXT | Type of Source Media: online |
Citation Title | RECOVERY PLAN FOR THE TIDEWATER GOBY (EUCYCLOGOBIUS NEWBERRYI) |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | U.S. FISH AND WILDLIFE SERVICE |
Publish Date | 2005-01-01 |
Extent Type | Discrete |
Extent Start Date/Time | 2005 |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
FISHL INFORMATION | Source Geospatial Form: HARDCOPY TEXT | Type of Source Media: paper |
Citation Title | SOUTHERN CALIFORNIA SPECIES PROFILE: ARROYO CHUB |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | DRILL, S. (UC COOPERATIVE EXTENSION NATURAL RESOURCE PROGRAM LA AND VENTURA COUNTIES) |
Publish Date | 2009-01-01 |
Extent Type | Discrete |
Extent Start Date/Time | 2009 |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | http://celosangeles.ucdavis.edu/natural_resources/ |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
FISHL INFORMATION | Source Geospatial Form: HARDCOPY TEXT | Type of Source Media: online |
Citation Title | SPECIES DISTRIBUTION, LOS ANGELES COUNTY |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | PRYOR, D. |
Publish Date | 2009-01-01 |
Extent Type | Discrete |
Extent Start Date/Time | 2009 |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
FISHL INFORMATION | Source Geospatial Form: EXPERT KNOWLEDGE | Type of Source Media: PERSONAL COMMUNICATION |
Citation Title | THREATENED/ENDANGERED (T/E) SPECIES IN VENTURA COUNTY |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | DELITH, C. (USFWS) |
Publish Date | 2009-01-01 |
Extent Type | Discrete |
Extent Start Date/Time | 2009 |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
FISHL INFORMATION | Source Geospatial Form: EXPERT KNOWLEDGE | Type of Source Media: PERSONAL COMMUNICATION |
Citation Title | USFWS RESOURCES IN SAN DIEGO AND ORANGE COUNTIES |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | AVERY, J. (USFWS) |
Publish Date | 2009-01-01 |
Extent Type | Discrete |
Extent Start Date/Time | 2009 |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
FISHL INFORMATION | Source Geospatial Form: EXPERT KNOWLEDGE | Type of Source Media: PERSONAL COMMUNICATION |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Process Steps
Process Step Number | 1 |
---|---|
» Description |
Two main sources of data were used to depict fish distribution and seasonality for this data layer: 1) personal interviews with resource experts from the U.S. Fish and Wildlife Service (USFWS) and California State Parks (CSP), and 2) published reports provided by USFWS and California Department of Fish and Game (CDF&G). The above digital and/or hardcopy sources were compiled by the project biologist to create the FISHL data layer. Depending on the type of source data, three general approaches are used for compiling the data layer: 1) information gathered during initial interviews and from hardcopy sources are compiled onto U.S. Geological Survey 1:24,000 topographic quadrangles and digitized; 2) hardcopy maps are digitized at their source scale; 3) digital data layers are evaluated and used "as is" or integrated with the hardcopy data sources. See the Lineage section for additional information on the type of source data for this data layer. The compiled ESI, biology, and human-use data are plotted onto hardcopy draft maps. Following the delivery of draft maps to the participating resource experts, a second set of interviews are conducted to review the maps. If necessary, edits to the FISHL data layer are made based on the recommendations of the resource experts, and final hardcopy maps and digital data are created. |
Process Date/Time | 2010-03-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Acquisition Information
Instruments
Instrument Unavailable Reason |
---|
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Platforms
Platform Unavailable Reason |
---|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
FAQs
Date | |
---|---|
Author | |
Question | |
Answer |
Child Items
Rubric scores updated every 15m
Score | Type | Title |
---|---|---|
Entity (ENT) | BIORES | |
Entity (ENT) | BIO_LUT | |
Entity (ENT) | BREED | |
Entity (ENT) | FISHL.AAT | |
Entity (ENT) | SEASONAL | |
Entity (ENT) | SOURCES | |
Entity (ENT) | SPECIES | |
Entity (ENT) | STATUS | |
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Catalog Details
Catalog Item ID | 40819 |
---|---|
Metadata Record Created By | Tyler Christensen |
Metadata Record Created | 2017-04-05 14:54+0000 |
Metadata Record Last Modified By | SysAdmin InPortAdmin |
» Metadata Record Last Modified | 2023-05-30 18:09+0000 |
Metadata Record Published | 2018-02-08 |
Owner Org | ORR |
Metadata Publication Status | Published Externally |
Do Not Publish? | N |
Metadata Workflow State | Published / External |
Metadata Last Review Date | 2018-02-08 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2019-02-08 |
Tags |
---|