British Columbia Lightstation Sea-Surface Temperature and Salinity Data (Pacific), 1914-present
Daily sea surface temperature and salinity observations have been carried out at several locations on the coast of British Columbia since the early part of the 20th century. Observations started at the Pacific Biological Station (Departure Bay) in 1914; 11 stations were added in the mid-1930s and several more in the 1960s. The number of stations reporting at any given time has varied as sampling has been discontinued at some stations and started or resumed at others.
Presently termed the British Columbia Shore Station Oceanographic Program (BCSOP), there are 12 active participating stations. Most of the stations are at lighthouses staffed by Fisheries and Oceans Canada, but three (Race Rocks, Amphitrite Point, and Active Pass) are sampled by contracted observers.
Observations are made daily using seawater collected in a bucket lowered into the surface water at or near the daytime high tide. This sampling method was designed long ago by Dr. John P. Tully and has not been changed in the interests of a homogeneous data set. This means, for example, that if an observer starts sampling one day at 6 a.m., and continues to sample at the daytime high tide on the second day the sample will be taken at about 06:50 the next day, 07:40 the day after etc. When the daytime high-tide gets close to 6 p.m. the observer will then begin again to sample early in the morning, and the cycle continues. Since there is a day/night variation in the sea surface temperatures the daily time series will show a signal that varies with the14-day tidal cycle. This artifact does not affect the monthly sea surface temperature data.
Datasets available for download
-
BC Lightstations and Other Sample SitesCSV
-
Data DictionaryPDF
-
DATA - In-Active SitesCSV
-
DATA - Active SitesCSV
-
BC Lightstations and Other Sample SitesCSV
-
DATA - Archived SitesCSV
-
DATA - BC Lightstations and Other Sample SitesSHP
-
DATA - BC Lightstations and Other Sample SitesSHP
-
BC Lightstations and Other Sample SitesEsri REST
-
BC Lightstations and Other Sample SitesEsri REST
Additional Info
| Field | Value |
|---|---|
| Last Updated | October 20, 2025, 02:29 (UTC) |
| Created | October 20, 2025, 02:29 (UTC) |
|
Domain / Topic
Domain or topic of the dataset being cataloged.
|
Oceans |
|
Title
Title for the Dataset.
|
British Columbia Lightstation Sea-Surface Temperature and Salinity Data (Pacific), 1914-present |
|
Description
A description of the dataset.
|
Daily sea surface temperature and salinity observations have been carried out at several locations on the coast of British Columbia since the early part of the 20th century. Observations started at the Pacific Biological Station (Departure Bay) in 1914; 11 stations were added in the mid-1930s and several more in the 1960s. The number of stations reporting at any given time has varied as sampling has been discontinued at some stations and started or resumed at others. Presently termed the British Columbia Shore Station Oceanographic Program (BCSOP), there are 12 active participating stations. Most of the stations are at lighthouses staffed by Fisheries and Oceans Canada, but three (Race Rocks, Amphitrite Point, and Active Pass) are sampled by contracted observers. Observations are made daily using seawater collected in a bucket lowered into the surface water at or near the daytime high tide. This sampling method was designed long ago by Dr. John P. Tully and has not been changed in the interests of a homogeneous data set. This means, for example, that if an observer starts sampling one day at 6 a.m., and continues to sample at the daytime high tide on the second day the sample will be taken at about 06:50 the next day, 07:40 the day after etc. When the daytime high-tide gets close to 6 p.m. the observer will then begin again to sample early in the morning, and the cycle continues. Since there is a day/night variation in the sea surface temperatures the daily time series will show a signal that varies with the14-day tidal cycle. This artifact does not affect the monthly sea surface temperature data. |
|
Tags / Keywords
Keywords/tags categorizing the dataset.
|
|
|
Format (CSV, XLS, TXT, PDF, etc)
File format of the dataset.
|
|
|
Dataset Size
Dataset size in megabytes.
|
|
|
Metadata Identifier
Metadata identifier – can be used as the unique identifier for catalogue entry
|
|
|
Published Date
Published date of the dataset.
|
2017-04-04 |
|
Time Period Data Span (start date)
Start date of the data in the dataset.
|
|
|
Time Period Data Span (end date)
End date of time data in the dataset.
|
|
|
GeoSpatial Area Data Span
A spatial region or named place the dataset covers.
|
| Field | Value |
|---|---|
|
Access category
Type of access granted for the dataset (open, closed, service, etc).
|
|
|
License
License used to access the dataset.
|
Open Government Licence - Canada |
|
Limits on use
Limits on use of data.
|
|
|
Location
Location of the dataset.
|
https://open.canada.ca/data/en/dataset/719955f2-bf8e-44f7-bc26-6bd623e82884 |
|
Data Service
Data service for accessing a dataset.
|
|
|
Owner
Owner of the dataset.
|
Fisheries and Oceans Canada | Pêches et Océans Canada |
|
Contact Point
Who to contact regarding access?
|
Government of Canada; Fisheries and Oceans Canada; Ecosystems and Ocean Science/Pacific Science/Ocean Science Division, [email protected] |
|
Contact Point Email
The email to contact regarding access?
|
|
|
Publisher
Publisher of the dataset.
|
|
|
Publisher Email
Email of the publisher.
|
[email protected] |
|
Author
Author of the dataset.
|
|
|
Author Email
Email of the author.
|
|
|
Accessed At
Date the data and metadata was accessed.
|
| Field | Value |
|---|---|
|
Identifier
Unique identifier for the dataset.
|
|
|
Language
Language(s) of the dataset
|
|
|
Link to dataset description
A URL to an external document describing the dataset.
|
|
|
Persistent Identifier
Data is identified by a persistent identifier.
|
|
|
Globally Unique Identifier
Data is identified by a persistent and globally unique identifier.
|
|
|
Contains data about individuals
Does the data hold data about individuals?
|
|
|
Contains data about identifiable individuals
Does the data hold identifiable data about individual?
|
|
|
Contains Indigenous Data
Does the data hold data about Indigenous communities?
|
|
|
Portal Type
Platform type of the source portal.
|
| Field | Value |
|---|---|
|
Version
Version of the datatset
|
None |
|
Source
Source of the dataset.
|
None |
|
Version notes
Version notes about the dataset.
|
|
|
Is version of another dataset
Link to dataset that it is a version of.
|
|
|
Other versions
Link to datasets that are versions of it.
|
|
|
Provenance Text
Provenance Text of the data.
|
|
|
Provenance URL
Provenance URL of the data.
|
|
|
Temporal resolution
Describes how granular the date/time data in the dataset is.
|
|
|
GeoSpatial resolution in meters
Describes how granular (in meters) geospatial data is in the dataset.
|
|
|
GeoSpatial resolution (in regions)
Describes how granular (in regions) geospatial data is in the dataset.
|
| Field | Value |
|---|---|
|
Indigenous Community Permission
Who holds the Indigenous Community Permission. Who to contact regarding access to a dataset that has data about Indigenous communities.
|
|
|
Community Permission
Community permission (who gave permission).
|
|
|
The Indigenous communities the dataset is about
Indigenous communities from which data is derived.
|
| Field | Value |
|---|---|
|
Number of data rows
If tabular dataset, total number of rows.
|
|
|
Number of data columns
If tabular dataset, total number of unique columns.
|
|
|
Number of data cells
If tabular dataset, total number of cells with data.
|
|
|
Number of data relations
If RDF dataset, total number of triples.
|
|
|
Number of entities
If RDF dataset, total number of entities.
|
|
|
Number of data properties
If RDF dataset, total number of unique properties used by the triples.
|
|
|
Data quality
Describes the quality of the data in the dataset.
|
|
|
Metric for data quality
A metric used to measure the quality of the data, such as missing values or invalid formats.
|
0 Comments