Easier access to scientific data
log in    
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  California Commercial Fish Landings, 1931-1978 Subscribe RSS
Institution:  NOAA SWFSC FED   (Dataset ID: fedCalLandings)
Range: time = 1931-01-15T00:00:00Z to 1978-12-15T00:00:00Z
Information:  Summary ? | License ? | Metadata | Background (external link) | Subset | Data Access Form | Files
Graph Type:  ?
X Axis: 
Y Axis: 
-1 +1
Constraints ? Optional
Constraint #1 ?
Constraint #2 ?
Server-side Functions ?
 distinct() ?
? (" ")
Graph Settings
Marker Type:   Size: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Y Axis Minimum:   Maximum:   Ascending: 
(Please be patient. It may take a while to get the data.)
Then set the File Type: (File Type information)
or view the URL:
(Documentation / Bypass this form ? )
    Time range:    <<    -              
[The graph you specified. Please be patient.]


Things You Can Do With Your Graphs

Well, you can do anything you want with your graphs, of course. But some things you might not have considered are:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  market_category {
    Int16 actual_range 0, 999;
    String description 
"When using this data it is critical to understand that a market category is
NOT a species code - it is a sort group.  While landings in some market
categories may consist entirely of the species for which they are named,
landings in other market categories may contain few of the species for which
they are named.  This is particularly true for the rockfish market
categories.  For example, we know that only about 50% of the fish landed in
market category 253 (bocaccio) prior to 1991 were actually bocaccio.  We are
currently in the process of estimating species specific landings from 1930
through 1968 (we already have the estimates from 1969-2007).

Many market categories were used in the past which are no longer included in
current market category definitions used by Fish and Game.  In addition, some
market categories have been redefined including 264, 265, and 266.  This
column uses the currently accepted codes and old codes were converted to new
codes.  In addition, codes which are no longer used by Fish and Game, but
which were used in the past, are now included in the MASTER_MARKET_CATEGORIES
    String ioos_category "Identifier";
    String long_name "Market Category";
    Int16 missing_value -9999;
  description {
    String ioos_category "Identifier";
    String long_name "Description of Market Category";
  nominal_species {
    String ioos_category "Fish Species";
    String long_name "Nominal Species of Market Category";
  species_group {
    String ioos_category "Taxonomy";
    String long_name "Species Group of Market Category";
  comments {
    String ioos_category "Other";
    String long_name "Comments about Market Category";
  area {
    String description "This column indicates the general area where the fish were caught if known.  The values used are:  Northern California, Central California, San Francisco Bay, Southern California, Mexico, Oregon, Washington, Unknown, and many international codes.";
    String ioos_category "Location";
    String long_name "Area";
  region {
    Int16 actual_range 0, 8;
    String description "This is the California marine region in which the fish were landed.  No values were present from 1951-1968.  Marine regions were originally identified using 2 different numbering schemes: 10, 20, 30, 40, 50, 60, 70, 80; or 1, 2, 3, 4, 5, 6, 7, 8.  For this table, the first series was converted to the second series.  Definitions:  1=Crescent City area, 2=Eureka area, 3=San Francisco Bay, 4=San Francisco Ocean, 5=Monterey, 6=Santa Barbara/Morro Bay, 7=Los Angeles, 8=San Diego.";
    String ioos_category "Location";
    String long_name "Region";
    Int16 missing_value -9999;
  block {
    Int16 actual_range 0, 3920;
    String description "This column contains Fish and Game block number.  Some block numbers are not present on charts, in particular, blocks >1299 are not shown on charts.  All block numbers > 1299 (and some less than 1300) are used for fish imported into California.  The AREA column indicates where the fish were imported from.  In order to get only fish caught in California waters, you must restrict block number to less than 900.  Block 0 indicates unknown area.  Some information on area can be obtained from the REGION column; however, REGION is where the fish were landed and may not be where they were actually caught.  This could be a problem for the northern and southern regions where fish could have been caught outside state waters.  Caution should be used when using data with block=0.";
    String ioos_category "Location";
    String long_name "Block";
    Int16 missing_value -9999;
  imported {
    String description "'N': the fish were likely to have been caught by US vessels and landed in California.  'Y': the fish were caught and landed outside California and imported to California.";
    String ioos_category "Other";
    String long_name "Imported";
  region_caught {
    Int16 actual_range 1, 13;
    String description "This column was created by Pearson.  It is the best guess of what CDFG region the fish were caught in.  It was created by using block number (if known).  If the block is unknown, then the REGION value is used (note that REGION is actually where the fish were landed).";
    String ioos_category "Location";
    String long_name "Region Caught";
    Int16 missing_value -9999;
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range -1.2295584e+9, 2.82528e+8;
    String axis "T";
    String ioos_category "Time";
    String long_name "Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  year {
    Int16 actual_range 1931, 1978;
    String ioos_category "Time";
    String long_name "Year";
    Int16 missing_value -9999;
  month {
    Int16 actual_range 1, 12;
    String ioos_category "Time";
    String long_name "Month";
    Int16 missing_value -9999;
  pounds {
    Int32 actual_range 0, 62580090;
    String ioos_category "Productivity";
    String long_name "Pounds";
    Int32 missing_value -9999;
    String units "pounds";
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String history 
"2018-01-23T21:44:18Z (local files)
    String infoUrl "";
    String institution "NOAA SWFSC FED";
    String keywords "about, animals, aquatic, area, biological, biosphere, block, california, category, caught, classification, coastal, comments, commercial, description, Earth Science > Biological Classification > Animals/Vertebrates > Fish, Earth Science > Biosphere > Aquatic Ecosystems > Coastal Habitat, Earth Science > Biosphere > Aquatic Ecosystems > Marine Habitat, Earth Science > Oceans > Aquatic Sciences > Fisheries, ecosystems, fed, fish, fish species, fisheries, group, habitat, identifier, imported, landings, marine, market, month, noaa, nominal, oceans, pounds, productivity, region, sciences, species, swfsc, taxonomy, time, vertebrates, year";
    String keywords_vocabulary "GCMD Science Keywords";
    String license 
"The data may be used and redistributed for free but is not intended
for legal use, since it may contain inaccuracies. Neither the data
Contributor, ERD, NOAA, nor the United States Government, nor any
of their employees or contractors, makes any warranty, express or
implied, including warranties of merchantability and fitness for a
particular purpose, or assumes any legal liability for the accuracy,
completeness, or usefulness, of this information.";
    String naming_authority "gov.noaa.pfeg.coastwatch";
    String observationDimension "row";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v29";
    String subsetVariables "market_category, description, nominal_species, species_group, area, region, block, imported, region_caught";
    String summary 
"The Groundfish Analysis Team at the SWFSC Fisheries Ecology Division (Santa
Cruz) completed work on a California commercial landings database, which
includes landings from 1931 through 2007. Landings from 1931 through 1968
were recovered using funds and services provided by the NESDIS Climate
Database Modernization Program (CDMP). The recovered data, when combined with
more recent landings estimates from the California Cooperative Groundfish
Survey from 1969 to 2007, forms one of the longest detailed catch records in
the US. The 1931-68 period includes monthly summaries of catches by 10-minute
geographic blocks.  These data are now openly available to the public for use
in stock assessments and monitoring of climate effects. Pearson is currently
working with the California Department of Fish and Game to extend the
geographic summary information to more recent years. Also, the taxa reported
in the historical data are the \"market categories\" used by fish processors,
and may involve multiple species groupings. A project has been initiated to
resolve historical landings to provide best estimates for individual species.

When using this data it is critical to understand that a market category is
NOT a species code - it is a sort group.  While landings in some market
categories may consist entirely of the species for which they are named,
landings in other market categories may contain few of the species for which
they are named.

General Notes:
The data from 1930-1932 has a lot of unknown block data.  When the trawl
landing data is entered, some of this may be resolved.  At the same time,
some gear data will be available.

When Source Corp finishes data entry of the landing receipt data, gear code
data will be available from 1951-1968; however, this will not be completed
until around 2011.

Block Maps:
Data Source: California Department of Fish & Game.
Data Assembly: NOAA SWFSC FED; Contact:";
    String time_coverage_end "1978-12-15T00:00:00Z";
    String time_coverage_start "1931-01-15T00:00:00Z";
    String title "California Commercial Fish Landings, 1931-1978";


Using tabledap to Request Data and Graphs from Tabular Datasets

tabledap lets you request a data subset, a graph, or a map from a tabular dataset (for example, buoy data), via a specially formed URL. tabledap uses the OPeNDAP (external link) Data Access Protocol (DAP) (external link) and its selection constraints (external link).

The URL specifies what you want: the dataset, a description of the graph or the subset of the data, and the file type for the response.

Tabledap request URLs must be in the form{?query}
For example,,latitude,time,station,wmo_platform_code,T_25&time>=2015-05-23T12:00:00Z&time<=2015-05-31T12:00:00Z
Thus, the query is often a comma-separated list of desired variable names, followed by a collection of constraints (e.g., variable<value), each preceded by '&' (which is interpreted as "AND").

For details, see the tabledap Documentation.

ERDDAP, Version 1.82
Disclaimers | Privacy Policy | Contact