Back to the top

FAQ

Frequently Asked Questions
Does GLOS charge for access to data?

No, access to Great Lakes data and information is free through GLOS.

There could be circumstances where an organization has customized data management needs, atypical data access requirements, or other features requiring engineering development work by GLOS. In those situations, GLOS may charge a cost-recovery fee to help offset expenses to support these requirements.

Access to the new information technology platform is made possible through funding from the Integrated Ocean Observing System (IOOS) program and other donor funds.

Does Seagull have an API?

We have two main ways to access GLOS Seagull platform data via API or API-like service:

Seagull ERDDAPhttps://seagull-erddap.glos.org/erddap/index.html

  • Look for your dataset on Seagull either through the map, clicking on the platform, and clicking on Dive Deeper in the bottom left of the panel that’s revealed.
  • OR click on Console in the upper left of Seagull, and click on the Platform Name from which you want API access to.
  • Look in the URL bar. For instance 45029 at Port Sheldon: https://seagull.glos.org/data-console/3
  • The number at the end of the URL is what you’ll use to find the data in ERDDAP. From the front page of Seagull ERDDAP, search in the upper right corner for “obs_[number]” or per the example, “obs_3”
  • Find the platform you want in the list of results.
  • Feel free to explore the links within the target row, but for the purposes here, click on the data link in the target row.
  • You’ll find a form to fill out for the platform’s parameters you want. At the bottom of the form there’s a drop down from which you can select the output you desire.
  • You can then click “Just generate the URL” for the URL you’d use to download the data in your format. (To better understand the format, click Submit and view the downloaded data.)
  • From there, you can modify the URL for time range, for example, acting as an API to the data you want.

Seagull APIhttps://seagull-api.glos.org/docs

For a platform like Port Sheldon, you’ll want to use the ‘obs_dataset_id’ as you did for ERDDAP to navigate. In this example, it’s 3. This won’t be an exhaustive guide on the API, but it should be enough to get started. Under Observation Datasets:

  • /api/v1/obs-dataset-summaries provides summary information on a platform, including its obs_dataset_id, associated platform_id, which is how its parameters are associated, a list of parameters, and more
  • /api/v1/obs-datasets provides similar output to the summaries, without parameter and other information.
  • /api/v1/obs-datasets.geojson provides a GeoJSON layer with the locations of available platforms on Seagull.
  • /api/v1/obs-datasets/{obsDatasetId}/metadata provides metadata for a platform. For example: /api/v1/obs-datasets/3/metadata
  • /api/v1/obs provides observations for a platform. For example: https://seagull-api.glos.org/api/v1/obs?startDate=2022-08-10&obsDatasetId=3. The result is a massive JSON object shaped like:

[ {

“obs_dataset_id”: 3,

“parameters”: [

{

“observations”: [

{

“latitude”: 42.899572,

“longitude”: -86.272291,

“timestamp”: “2022-08-12T18:40:00+00:00”,

“value”: 3

},…

],

“parameter_id”: 178

},…]}] where the information the parameter_id can be found in /api/v1/parameters

 

Please feel free to reach out with any questions to support@glos.org.

How does data currently get from platforms to your servers? How will Seagull do this?

Currently, most of the buoys in our network use cellular telemetry, while a few use satellite telemetry. However, the path data takes from sensor to our servers really varies. Many buoys send data directly from their datalogger to our server, while others have an in-between server that translates the data and sends it to us.

On our current systems, we ingest the data from the buoys through FTP. Each data provider has their own FTP account that they can use to send the data in a GLOS-required XML format.

However, for Seagull, we developed a completely new architecture to allow the data providers to send data to us using other secure protocols like HTTPs in flexible formats like JSON. Though not preferable, we will be also support our current FTP/XML protocol in 2022, just in case the data providers are unable to send data to us through a secure protocol.

If you have flexibility to select a data logger, we recommend selecting one that is capable of transmitting data over secure protocols like HTTPs. If not, there is also an option to send data, not directly from the datalogger but from a local server, if that is more practical for your system.

If my platform is already sending data to GLOS, will it automatically be added to Seagull?

Yes. If the platform is part of the current system, it will be part of Seagull. In the future, since Seagull will feature enriched metadata, you will likely need to add to or update some information.

When will older GLOS apps stop working?

As functionality from each legacy app is transferred to Seagull, we will begin decommissioning each legacy app. This is dependent on the pace of Seagull development.

After Seagull launches on April 28, 2022, in late April or Early May, we will be shutting down GL Buoys, the HABs Portal, and our THREDDS server. Please reach out to us with any concerns.

GLOS