ERDDAP
Easier access to data

Make A Graph

Dataset Title:	Daily Freshwater Discharge Data of the St. Lawrence River at Quebec City Calculated by the Qmec Model \| Débits journalier d'eau douce du fleuve Saint- Laurent à la hauteur de la ville de Québec calculé par le modèle Qmec
Institution:	Institut des sciences de la mer de Rimouski (Dataset ID: ismerDebitsQuebecJournalier)
Range:	time = 1962-01-01 to 2024-12-31
Information:	Summary \| License \| Metadata \| Background \| Data Access Form \| Files

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Graph Type:

X Axis:

Y Axis:

Constraints	Optional Constraint #1		Optional Constraint #2

Server-side Functions

distinct()

Hover here to see a list of options. Click on an option to select it.

(Please be patient. It may take a while to get the data.)

Optional:
Then set the File Type: (File Type information)
and

or view the URL:
(Documentation / Bypass this form

)

[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:

Web page authors can embed a graph of the latest data in a web page using HTML <img> tags.
Anyone can use ERDDAPs Slide Sorter to build a personal web page that displays graphs with the latest data (or other images or HTML content), each in its own, draggable slide.

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range -2.524608e+8, 1.7356032e+9;
    String axis "T";
    String coverage_content_type "coordinate";
    String ioos_category "Time";
    String long_name "Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  Discharge {
    Int32 actual_range 2700, 29400;
    String long_name "Daily discharge";
    Int32 missing_value 2147483647;
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/RFDSCH03/";
    String nerc_standard_name "riverine_discharge_of_water";
    String standard_name "riverine_discharge_of_water_by_water_level_gauge_and_calculation_from_level";
    String units "m3 s-1";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.11, ACDD-1.3, NCCSV-1.2";
    String creator_email "daniel_bourgault@uqar.ca";
    String creator_name "Daniel Bourgault";
    String creator_type "person";
    String defaultDataQuery "&time>=min(time)";
    String defaultGraphQuery "&time>=max(time)-1year&.draw=lines&.bgColor=0xffffffff";
    String history 
"2026-08-18T00:41:44Z (local files)
2026-08-18T00:41:44Z http://erddap.cioos.ca/tabledap/ismerDebitsQuebecJournalier.das";
    String infoUrl "https://www.ismer.ca/";
    String institution "Institut des sciences de la mer de Rimouski";
    String keywords "discharge, freshwater, Quebec City, St. Lawrence River";
    String keywords_fr "débit, Rivière Saint-Laurent, eau douce, ville de Québec";
    String license "Creative Commons Attribution 4.0 International license CC-BY 4.0.";
    String licenseUrl "https://creativecommons.org/licenses/by/4.0/";
    String model_boundary_east "Saint-François I.O. - station 03100";
    String model_boundary_east_info "https://www.marees.gc.ca/fr/stations/03100";
    String model_boundary_east_latitude "46.9965";
    String model_boundary_east_longitude "-70.808167";
    String model_boundary_west "Neuville - Station 03280";
    String model_boundary_west_info "https://www.marees.gc.ca/fr/stations/03280";
    String model_boundary_west_latitude "46.6965";
    String model_boundary_west_longitude "-71.572833";
    String model_reference_1 "Bourgault D and Matte P (2020a) A physically-based method for real-time monitoring of tidal river discharges from water level observations with an application to the St. Lawrence River Journal of Geophysical Research – Oceans 125 e2019JC015992";
    String model_reference_1_doi "https://doi.org/10.1029/2019JC015992";
    String model_reference_2 "Bourgault D and Matte P (2020b) Qmec : a Matlab code to compute tidal river discharge from water level [Source Code]";
    String model_reference_2_doi "https://doi.org/10.24433/CO.7299598.v2";
    String nerc_standard_name_vocabulary "BODC Parameter Usage Vocabulary v1226";
    String related_dataset "https://erddap.ogsl.ca/erddap/tabledap/ismerDebitsQuebecHoraire.html";
    String related_identifiers_1 "https://doi.org/10.1029/2019JC015992";
    String related_identifiers_1_title "Bourgault D and Matte P (2020a) A physically-based method for real-time monitoring of tidal river discharges from water level observations with an application to the St. Lawrence River Journal of Geophysical Research – Oceans 125 e2019JC015992";
    String related_identifiers_2 "https://doi.org/10.24433/CO.7299598.v2";
    String related_identifiers_2_title "Bourgault D and Matte P (2020b) Qmec : a Matlab code to compute tidal river discharge from water level [Source Code]";
    String revision_date "2025-04-24";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v84";
    String summary "Daily freshwater discharge data of the St. Lawrence River at Quebec City (river transect where discharge is calculated: 46.7779°N,-71.2409°E to 46.7695°N,-71.2216°E) as computed by the hydrodynamic model called Qmec developed by Bourgault and Matte (2020a, 2020b).";
    String summary_fr "Débits journaliers d'eau douce du Saint-Laurent au niveau de la ville de Québec (transecte de rivière où le débit est calculé : 46.7779°N,-71.2409°E to 46.7695°N,-71.2216°E) déterminé par le modèle hydrodynamique Qmec développé par Bourgault et Matte (2020a, 2020b).";
    String time_coverage_end "2024-12-31";
    String time_coverage_start "1962-01-01";
    String title "Daily Freshwater Discharge Data of the St. Lawrence River at Quebec City Calculated by the Qmec Model | Débits journalier d'eau douce du fleuve Saint-Laurent à la hauteur de la ville de Québec calculé par le modèle Qmec";
    String version "2";
  }
}

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.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

Tabledap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/pmelTaoDySst.htmlTable?longitude,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 2.28.1
Disclaimers | Privacy Policy | Contact