PacIOOS ERDDAP
Easier access to scientific data

ERDDAP > wms > neowave_agat_bay

Dataset Title:  NEOWAVE Regional Tsunami Model: Guam: Agat Bay Subscribe RSS
Institution:  Pacific Islands Ocean Observing System (PacIOOS)   (Dataset ID: neowave_agat_bay)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Data Access Form | Make a graph

This web page is using Leaflet (external link) to display maps which are created on-the-fly by ERDDAP's Web Map Server (WMS) version 1.3.0.
The control on the left of the map lets you zoom in (+) or out (-).
The control on the right manages the layers.
You can select different values for the data variable's dimension(s): (none for this dataset)
 

The current_event01 legend.

The current_event02 legend.

The current_event03 legend.

The current_event04 legend.

The current_event05 legend.

The current_event06 legend.

The current_event07 legend.

The current_event08 legend.

The current_event09 legend.

The current_event10 legend.

The current_event11 legend.

The current_event12 legend.

The current_event13 legend.

The current_event14 legend.

The current_event15 legend.

The current_event16 legend.

The current_event17 legend.

The current_event18 legend.

The current_event19 legend.

The current_event20 legend.

The current_event21 legend.

The current_event22 legend.

The current_event23 legend.

The current_event24 legend.

The current_event25 legend.

The current_event26 legend.

The current_event27 legend.

The current_event28 legend.

The current_event29 legend.

The current_event30 legend.

The current_event31 legend.

The current_event32 legend.

The current_event33 legend.

The current_event34 legend.

The current_event35 legend.

The current_event36 legend.

The current_event37 legend.

The current_event38 legend.

The current_event39 legend.

The current_event40 legend.

The current_event41 legend.

The current_event42 legend.

The current_event43 legend.

The current_event44 legend.

The current_event45 legend.

The current_event46 legend.

The current_event47 legend.

The drawdown_event01 legend.

The drawdown_event02 legend.

The drawdown_event03 legend.

The drawdown_event04 legend.

The drawdown_event05 legend.

The drawdown_event06 legend.

The drawdown_event07 legend.

The drawdown_event08 legend.

The drawdown_event09 legend.

The drawdown_event10 legend.

The drawdown_event11 legend.

The drawdown_event12 legend.

The drawdown_event13 legend.

The drawdown_event14 legend.

The drawdown_event15 legend.

The drawdown_event16 legend.

The drawdown_event17 legend.

The drawdown_event18 legend.

The drawdown_event19 legend.

The drawdown_event20 legend.

The drawdown_event21 legend.

The drawdown_event22 legend.

The drawdown_event23 legend.

The drawdown_event24 legend.

The drawdown_event25 legend.

The drawdown_event26 legend.

The drawdown_event27 legend.

The drawdown_event28 legend.

The drawdown_event29 legend.

The drawdown_event30 legend.

The drawdown_event31 legend.

The drawdown_event32 legend.

The drawdown_event33 legend.

The drawdown_event34 legend.

The drawdown_event35 legend.

The drawdown_event36 legend.

The drawdown_event37 legend.

The drawdown_event38 legend.

The drawdown_event39 legend.

The drawdown_event40 legend.

The drawdown_event41 legend.

The drawdown_event42 legend.

The drawdown_event43 legend.

The drawdown_event44 legend.

The drawdown_event45 legend.

The drawdown_event46 legend.

The drawdown_event47 legend.

The surge_event01 legend.

The surge_event02 legend.

The surge_event03 legend.

The surge_event04 legend.

The surge_event05 legend.

The surge_event06 legend.

The surge_event07 legend.

The surge_event08 legend.

The surge_event09 legend.

The surge_event10 legend.

The surge_event11 legend.

The surge_event12 legend.

The surge_event13 legend.

The surge_event14 legend.

The surge_event15 legend.

The surge_event16 legend.

The surge_event17 legend.

The surge_event18 legend.

The surge_event19 legend.

The surge_event20 legend.

The surge_event21 legend.

The surge_event22 legend.

The surge_event23 legend.

The surge_event24 legend.

The surge_event25 legend.

The surge_event26 legend.

The surge_event27 legend.

The surge_event28 legend.

The surge_event29 legend.

The surge_event30 legend.

The surge_event31 legend.

The surge_event32 legend.

The surge_event33 legend.

The surge_event34 legend.

The surge_event35 legend.

The surge_event36 legend.

The surge_event37 legend.

The surge_event38 legend.

The surge_event39 legend.

The surge_event40 legend.

The surge_event41 legend.

The surge_event42 legend.

The surge_event43 legend.

The surge_event44 legend.

The surge_event45 legend.

The surge_event46 legend.

The surge_event47 legend.

What is WMS?

ERDDAP's Web Map Service (WMS) lets you request an image with data plotted on a map. WMS (external link) is an Open Geospatial Consortium (OGC) (external link) and ISO (19128) (external link) standard for "the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple remote and heterogeneous sources." See the list of datasets available via WMS at this ERDDAP installation.

Three Ways to Make Maps with WMS

  1. In theory, anyone can download, install, and use WMS client software.
    Some clients are: ArcGIS (external link) and uDig (external link). To make a client work, you would install the software on your computer. Then, you would enter the URL of the WMS service into the client. For example, in ArcGIS (not yet fully working because it doesn't handle time!), use
    "Arc Catalog : Add Service : Arc Catalog Servers Folder : GIS Servers : Add WMS Server". In ERDDAP, this dataset has its own WMS service, which is located at
    https://pae-paha.pacioos.hawaii.edu/erddap/wms/neowave_agat_bay/request?
    (Some WMS client programs don't want the ? at the end of that URL.) See the list of datasets available via WMS at this ERDDAP installation.

    In practice, we haven't found any WMS clients that properly handle dimensions other than longitude and latitude (e.g., time), a feature which is specified by the WMS specification and which is utilized by most datasets in ERDDAP's WMS servers. You may find that using Make A Graph and selecting the .kml file type (an OGC standard) to load images into Google Earth (external link) provides a good (non-WMS) map client. See the list of datasets with Make A Graph at this ERDDAP installation.

  2. Web page authors can embed a WMS client in a web page.
    For the map above, ERDDAP is using Leaflet (external link), which is a very versatile WMS client. Leaflet doesn't automatically deal with dimensions other than longitude and latitude (e.g., time), so you will have to write JavaScript (or other scripting code) to do that. (Adventurous JavaScript programmers can look at the Souce Code for this web page.) Another commonly used JavaScript WMS client is OpenLayers (external link).
     
  3. A person with a browser or a computer program can generate special WMS URLs.
    For example, See the list of datasets available via WMS at this ERDDAP installation.
    For more information about generating WMS URLs, see ERDDAP's WMS Documentation .

    In practice, it is easier, more versatile, and more efficient to use this dataset's Make A Graph web page than to use WMS for this purpose. See the list of datasets with Make A Graph at this ERDDAP installation.


 
ERDDAP, Version 2.23
Disclaimers | Privacy Policy | Contact