Caro-COOPS.org Discussion Board :: View topic - SEACOOS obs WMS and WFS enabled

Caro-COOPS.org Discussion Board Forum Index

Caro-COOPS.org Discussion Board
Discussion area for Caro-COOPS-related initiatives

FAQ Search

Memberlist

Usergroups Calendar

Profile

SEACOOS obs WMS and WFS enabled

   Caro-COOPS.org Discussion Board Forum Index
   -> Other, Project Management
   -> Charlton, Charlton
   -> SEACOOS, 2004 July remote sensing layers for cached images

View previous topic :: View next topic

Author

Message

cpurvis

Joined: 24 Feb 2025
Posts: 255

Posted: Wed Oct 20, 2025 11:09 am Post subject: SEACOOS obs WMS and WFS enabled

The base WMS and WFS requests are here (it will return XML to you):

Code:

http://nautilus.baruch.sc.edu/wms/seacoos_in_situ?REQUEST=GetCapabilities
AND
http://nautilus.baruch.sc.edu/wfs/seacoos_in_situ?service=wfs&request;=getcapabilities&version;=1.0.0

All of these layers are available via the
* production interactive map: http://nautilus.baruch.sc.edu/portal_obs
* and/or the development interactive map: http://nautilus.baruch.sc.edu/rs

For quick reference, the layer names (for both WMS and WFS reqeusts) are here:

Code:

sst_obs_hourly
wind_obs_hourly
wind_obs_normalized_hourly

You may notice that if you do a WMS or WFS GetCapabilties, you will see layers like sst_obs_hourly_archive and sst_obs_hourly_recent returned to you. Do *not* use those layers -- a CGI wrapper checks your original request to see from which DB your records will be returned, and it substitutes these resultant layer names automatically for you. Moral of the story is to use the higher level, i.e. _hourly, layers ONLY.

Parameter notes:

* time : Optional. If nothing is passed, it will return hourly obs that are 1.5 hours old relative to now. Otherwise it will return hourly obs closest to your timestamp. The data online currently goes back to late July, 2004. At some point I will develop a tolerance for time ranges rather than only handling specific points in time like it does now.

* wind_speed_units : Optional. Valid values are mps (default), mph, and knots.

* station_id : Optional. If you pass a station_id, the resultant dataset will return only those records that have the station_id parameter as a substring of the entire station_id. E.g., a station_id parameter of usgs would return all records for a given time frame that have 'usgs' as part of the station_id.

station_id substrings that are generally in the system are:

Code:

nccoos
ndbc
nos
nps
nws
skio
skio_R2
skio_R8
um
usf
usgs

Attached are example URL's that show how to get the picture (below) as well as the data values of NDBC real-time SST observations.

Also, see this post, http://caro-coops.org/bb/posting.php?mode=editpost&p;=564 for related information and layers, e.g. an SST legend colorbar.

in_situ.png

Description:

Filesize:

1.31 KB

Viewed:

69 Time(s)

obs_urls.txt

Description:

Download

Filename:

obs_urls.txt

Filesize:

312 Bytes

Downloaded:

7 Time(s)

Display posts from previous:

	Caro-COOPS.org Discussion Board Forum Index -> Other, Project Management -> Charlton, Charlton -> SEACOOS, 2004 July remote sensing layers for cached images	All times are GMT - 5 Hours
Page 1 of 1

Jump to:

You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum