Services

Participation

If you have realtime sealevel data that you would like to share via this facility, become one of the data provider by sending an email to .

Enter or edit station metadata

Station metadata can be edited manually by the operator responsible for the respective station.
You should register to the "Edit gauges metadata (gauges)" to manage station metadata
Edit station metadata

BGAN service

We provide a service that allows data providers to post messages to the Global Telecommunication System (GTS).
Messages can be provided via a BGAN terminal or any station that is able to do TCP/IP socket communication.
Bgan Documentation

Sealevel Station Catalog (SSC)

The catalog provides an overview of all station identifiers used by the different GLOSS data centers and PTWC (hereafter named the "data centers").
As such the SSC facilitates mapping of data holdings amongst the various data centers.
Three (3) core fields are stored in the database:

name
latitude & longitude
data provider identifier

Additional information is taken directly (synchronized) from the station metadata catalogs of the data centers.
RSS feeds and web services are provided to retrieve information from the SSC.
Data providers are encouraged to verify and/or add their own stations. Feedback welcome via contact
Access the catalog

Direct data access web service

Most of the station descriptive metadata and the station realtime data is accessible through a REST web service.
Users are required to register for this service. Having your contact details will enable us to keep track of the use of this facility, solve performance problems at network level and contact you in case of changes or maintenance activities.
Simply register by sending an email to contact including your IP address and reason for registering.

Notice: Long-term mean sea level (MSL) data is not the aim of this service. See the note on the front page.

FAQ

Outlier detection and spike removal on station graphs

The outlier detection works as follow:

All values X where abs(X – median) > tolerance are hidden.
With tolerance = 3*abs(percentile90 - median)
The statistics (median and percentile90) are calculated on the data being plotted (12h, 1d, 7d, 30d)

For the spike removal we take the median out of a window with size 3.

What does the 'offset' value represents

The offset is the average (from all values in the current start-end time frame), that we subtracted to make sure the graph evolves around zero.
This allows us to align multiple sensors with different offsets on top of each other.
This is a purely mathematical value, not the actual physical offset/datum or absolute sea level

Where can I find the vertical datum information (absolute, referenced sea level)

We only deal with relative data, we don't have the vertical datum information available.
For referenced data you should contact the station operator, or click on the 'Long-term MSL data' link on the station details page.

Via what methods can you deliver data

Real-time sea level data can be delivered in an automated way via:

Global Telecommunication System (GTS): requires you to have access to it
HTTP POST: you upload the data to our website via a HTTP request. See BGAN for more info
HTTP pull: you provide a web service that we can read
FTP upload: you upload to our FTP server
FTP pull: you provide an FTP server that we can read
Socket connection: you provide a TCP port that we can read

Data access help

Please be economic with the resources, use the most effective query or contact us if you need something specific.
It is useless to poll for stationdata more than once a minute. For best performance use the sensorlist query every minute.

Remember this is realtime data that has undergone only limited quality control.

This is a REST webservice that is accessed through an url with this format:

service.php?query=xxx&format=xxx[&additional partameters]

with possible values :

query= "data", "station", "stationlist" , default= null
format= "json", "xml" or sometimes "ascii", default = json
optional additional parameters depend on the query :

query	additional paramaters	use
data	"code=" + stationcode "timestart=" + ISOdate (YYYY-MM-DDTHH:MM), default = now()-12 hours "timestop=" + ISOdate (YYYY-MM-DDTHH:MM), default = now "format"= "json", "xml" ,"ascii","xtab","html", default = json "includesensors[]=" + sensor; i.e. &includesensors[]=rad&includesensors[]=prs, default is all "nofilter=true" will show all values, otherwise only values > -999 and values < 999 are used; note: -999 is used for missing values "skip_gaps_until=" + ISOdate (YYYY-MM-DDTHH:MM)	will give data for station with code stationcode from timestart till timestop, in the specified format note: with skip_gaps_until parameter: if there is no data available within the specified 'starttime' to 'stoptime' interval, the interval will be shifted to the next datetime for which data is available, while maintaining the original interval size in days. If no data is available before "skip_gaps_until" date, the response will be empty.
stationlist	"showall=" "all", "gts", "web", "ftp", "bgan", "email", "socket", "g" for GLOSS or "a" for active, default is "a" "format"= "json", "xml" , default = json "output"="contacts","performance", default= general	will give stationlist restricted according to the 'showall' parameter, in the specified format, 'output' specifies different field lists
sensorlist	"showall=" "all", "gts", "web", "ftp", "bgan", "email", "socket", "g" for GLOSS or "a" for active, default is "a" "format"= "json", "xml" , default = json	will give list of all sensors, with last data and time stamp restricted according to the 'showall' parameter, in the specified format
station	"code=" + stationcode "format"= "json", "xml" , default = json	will give all details for this station ,in the specified format

Change log:

2024-02-21
Added parameter skip_gaps_until
2021-12-15
Fix documentation for "showall" parameter.
2013-08-08
Bugfix for displaying the same sensor more than once on the 'stationlist' page. Date format changed to ISOdate consistently.
2012-11-08
Added documentation about the 'includesensors' parameter.
2011-12-12
Added documentation about missing values and 'nofilter' option.
2011-04-18
Put all date formats to YYYY-MM-DD HH:MM,
added formats xtab and html for data query, fixed chronology bug in bgraph output
2011-03-22
Changed XML output to reduce size, fields are trimmed, dates sent as normal string with CDATA tag
2011-03-14
Bug correction in XML output for query=station, first sensor was dropped
2011-03-13
We simplified the ascii output of the stationlist query by removing the message examples, url's and graph_urls. And removed tabs from all strings.
We added the optional =contacts and =performance formats for all formats of the stationlist query.
Added sensorid to the sensorlist output.