ERDDAP
Easier access to scientific data

Brought to you by NOAA NMFS SWFSC ERD

Make A Graph

Dataset Title:	IMIDA Observatorio del Mar Menor Narejos buoy
Institution:	+ATLANTIC_CoLAB (Dataset ID: Narejos)
Range:	longitude = -0.82730687 to -0.82730687°E, latitude = 37.74758 to 37.74758°N, time = 2026-03-25T09:25:47Z to 2026-07-20T18:16:00Z
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Subset \| 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:

Color:

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.

Graph Settings

Marker Type:

Size:

Color:

Color Bar:

Continuity:

Scale:

Minimum:

Maximum:

N Sections:

Draw land mask:

Y Axis Minimum:

Maximum:

(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

)

Click on the map to specify a new center point.

Zoom:

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:

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 {
  TEMP {
    Float64 _FillValue NaN;
    Float64 actual_range -12.51, 32.23;
    Float64 colorBarMaximum 32.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Temperature";
    String long_name "Sea Water Temperature";
    String standard_name "sea_water_temperature";
    String units "degree_C";
  }
  PSAL {
    Float64 _FillValue NaN;
    Float64 actual_range 0.0, 48.43;
    Float64 colorBarMaximum 37.0;
    Float64 colorBarMinimum 32.0;
    String ioos_category "Salinity";
    String long_name "Practical salinity";
    String standard_name "sea_water_practical_salinity";
    String units "PSU";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.774430747e+9, 1.78457136e+9;
    String axis "T";
    String calendar "gregorian";
    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";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 37.7475802546, 37.7475802546;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "station latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue NaN;
    Float64 actual_range -0.82730686707, -0.82730686707;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "station longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  platform_id {
    String ioos_category "Identifier";
    String long_name "Platform Id";
  }
  station_id_coord {
    String ioos_category "Identifier";
    String long_name "Station Id Coord";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String citation "These data were collected by IMIDA and made freely available by +ATLANTIC CoLAB (Portugal) as part ot  EMODnet Ingestion.";
    String contact "emodnet at omm.imida.es";
    String contributors_orcid "0000-0003-0335-2274, 0000-0002-4808-8940, 0009-0007-0157-2202, 0009-0009-5457-0870, 0000-0002-6853-4952";
    String contributors_role "monitoring leader, monitoring assistant, data scientist, data scientist, coordinator data distribution";
    String Conventions "OceanSITES v1.4,SeaDataNet_1.0,COARDS, CF-1.10, CMEMS INSTAC v3.2, ACDD-1.3";
    String creator_email "emodnet at colabatlantic.com";
    String creator_name "+ATLANTIC_CoLAB";
    String creator_orcid "0009-0007-0157-2202";
    String creator_type "institution";
    String creator_uri "https://colabatlantic.com/";
    String creator_url "https://www.seadatanet.org/";
    String data_assembly_center "+ATLANTIC CoLAB, Portugal";
    String data_assembly_center_edmo_code "5952";
    String data_assembly_center_edmo_uri "https://edmo.seadatanet.org/report/5952";
    String data_assembly_center_ror_code "05avbyr67";
    String data_assembly_center_ror_uri "https://ror.org/05avbyr67";
    String data_assembly_center_uri "https://colabatlantic.com/";
    String data_format_original "csv";
    String data_mode "R";
    String data_owner "IMIDA";
    String data_owner_country "Spain";
    String data_owner_country_code "ES";
    String data_owner_country_code_vocabulary "ISO3166";
    String data_owner_ror_code "00zj9v924";
    String data_owner_ror_uri "https://ror.org/00zj9v924";
    String data_owner_uri "https://www.imida.es";
    String data_type "TimeSeries";
    String data_update_frequence "irregular";
    String data_version "1";
    String date_created "2025-10-28T15:04:48Z";
    Float64 Easternmost_Easting -0.82730686707;
    String epsg_code "EPSG:4326";
    String format_version "1.5";
    Float64 geospatial_lat_max 37.7475802546;
    Float64 geospatial_lat_min 37.7475802546;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -0.82730686707;
    Float64 geospatial_lon_min -0.82730686707;
    String geospatial_lon_units "degrees_east";
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"Created on 2026-07-21 13:55:16
2026-07-21T22:31:26Z (local files)
2026-07-21T22:31:26Z http://localhost:8080/tabledap/Narejos.das";
    String infoUrl "https://omm.imida.es";
    String inspire "Oceanographic geographical features, Sea reagions, Hydrography";
    String institution "+ATLANTIC_CoLAB";
    String keywords "+atlantic, buoy, chemistry, chlorophyll, chlorophyll-a, CNDC, colab, color, concentration, conductivity, coord, CPHL, data, del, density, depth, dissolved, dissolved o2, DOX1, earth, Earth Science > Oceans > Ocean Chemistry > Chlorophyll, Earth Science > Oceans > Ocean Chemistry > Oxygen, Earth Science > Oceans > Ocean Temperature > Water Temperature, Earth Science > Oceans > Salinity/Density > Conductivity, Earth Science > Oceans > Salinity/Density > Salinity, electrical, EMODnet Ingestion, fraction, identifier, imida, latitude, longitude, mar menor, mass, mass_concentration_of_chlorophyll_a_in_sea_water, measurement, menor, mooring buoys, murcia, narejos, nodc/cedo, O2, observatorio, ocean, ocean color, oceans, oxygen, platform, platform_id, practical, PSAL, salinity, science, sea, sea_water_electrical_conductivity, sea_water_practical_salinity, sea_water_temperature, seawater, station, station_id_coord, TEMP, temperature, time, volume, volume_fraction_of_oxygen_in_sea_water, water";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "CC-BY";
    String license_uri "https://creativecommons.org/licenses/by/4.0/";
    String logo "https://www.imida.es/image/layout_set_logo?img_id=795448&t=1777881245265";
    String naming_authority "IMIDA";
    Float64 Northernmost_Northing 37.7475802546;
    String platform_id_orig "IMIDA_OMM_Narejos_buoy";
    String platform_type "Surface Mooring";
    String QC_indicator "unkown";
    String references "Data was collected by moored multiparametric buoys";
    String research_infrastructure "IMIDA OMM";
    String source "Data was collected by the Mar Menor mooring monitoring network";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 37.7475802546;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String station_id "Narejos";
    String station_name "Narejos";
    String subsetVariables "latitude, longitude, platform_id, station_id_coord";
    String summary "Narejos. +ATLANTIC_CoLAB data from a local source.";
    String testOutOfDate "now-31days";
    String time_coverage_end "2026-07-20T18:16:00Z";
    String time_coverage_start "2026-03-25T09:25:47Z";
    String title "IMIDA Observatorio del Mar Menor Narejos buoy";
    Float64 Westernmost_Easting -0.82730686707;
  }
}

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