ArcGIS REST Services Directory Login | Get Token
JSON | SOAP | WMS

nowcoast/guidance_model_greatlakes_lmofs_time (MapServer)

View In:   ArcGIS JavaScript   ArcGIS Online map viewer   Google Earth   ArcMap   ArcGIS Explorer

View Footprint In:   ArcGIS Online map viewer

Service Description:
Last Revised: February 2016

Map Information

This nowCOAST™ time-enabled map services provides map of the latest nowcasts and forecast guidance of water temperature, water currents, and water level guidance from the NOS Lake Michigan Operational Forecast System (LMOFS) at hourly increments out to 60 hours. The direction of the water currents are depicted by white streaklets. The magnitude of the current is indicated by the length and width of the streaklet as well as by the color-coded speed background. The water levels are referenced to Low Water Datum of IGLD85. The maps of LMOFS forecast guidance are updated in the nowCOAST™ map service four times per day. For more detailed information about layer update frequency and timing, please reference the nowCOAST™ Dataset Update Schedule.

Background Information

LMOFS is based on the Princeton Ocean Model (POM), a terrain following numerical ocean or hydrodynamic prediction model. The POM has been modified for use in the Great Lakes by NOAA/GLERL and The Ohio State University. The OFS grid domain covers Lake Michigan. LMOFS is a 3-D forecast modeling system with a spatial horizontal resolution of 5 km and 20 terrain or sigma vertical levels. It has four forecast cycles per day (0000, 0600, 1200, and 1800 UTC) which generate forecast guidance out to 60 hours. The forecast cycle uses forecasts of surface wind velocity and surface air temperature from the NWS National Digital Forecast Database (NDFD). Each forecast cycle is preceded with a 1-hr long nowcast cycle. The latest nowcast serves as the initial conditions for each forecast cycle. The nowcoast cycle is driven by surface analyses of surface wind, air temperature, dew point temperature, and total cloud cover. LMOFS was developed and evaluate by NOAA/GLERL and the NOAA/NOS/CSDL Coastal Marine Modeling Branch. It was implemented operationally on the NOAA Weather and Climate Operational Supercomputer System (WCOSS) by the NOS Center for Operational Oceanographic Products and Services (CO-OPS) in collaboration with NWS/NCEP Central Operations. For more information, please see http://tidesandcurrents.noaa.gov/ofs/glofs.html.

The maps are generated using a visualization technique developed by the Data Visualization Research Lab at The University of New Hampshire's Center for Coastal and Ocean Mapping (http://www.ccom.unh.edu/vislab/). The method combines two techniques. First, equally spaced streamlines are computed in the flow field using Jobard and Lefer's (1977) algorithm. Second, a series of "streaklets" are rendered head to tail along each streamline to show the direction of flow. Each of these varies along its length in size, color and transparency using a method developed by Fowler and Ware (1989), and later refined by Mr. Pete Mitchell and Dr. Colin Ware (Mitchell, 2007).

Time Information

This map service is time-enabled, meaning that each individual layer contains time-varying data and can be utilized by clients capable of making map requests that include a time component.

In addition to ArcGIS Server REST access, time-enabled OGC WMS 1.3.0 access is also provided by this service.

This particular service can be queried with or without the use of a time component. If the time parameter is specified in a request, the data or imagery most relevant to the provided time value, if any, will be returned. If the time parameter is not specified in a request, the latest data or imagery valid for the present system time will be returned to the client. If the time parameter is not specified and no data or imagery is available for the present time, no data will be returned.

This service is configured with time coverage support, meaning that the service will always return the most relevant available data, if any, to the specified time value. For example, if the service contains data valid today at 12:00 and 12:10 UTC, but a map request specifies a time value of today at 12:07 UTC, the data valid at 12:10 UTC will be returned to the user. This behavior allows more flexibility for users, especially when displaying multiple time-enabled layers together despite slight differences in temporal resolution or update frequency.

When interacting with this time-enabled service, only a single instantaneous time value should be specified in each request. If instead a time range is specified in a request (i.e. separate start time and end time values are given), the data returned may be different than what was intended.

Care must be taken to ensure the time value specified in each request falls within the current time coverage of the service. Because this service is frequently updated as new data becomes available, the user must periodically determine the service's time extent. However, due to software limitations, the time extent of the service and map layers as advertised by ArcGIS Server does not always provide the most up-to-date start and end times of available data. Instead, users have three options for determining the latest time extent of the service:

  1. Issue a returnUpdates=true request (ArcGIS REST protocol only) for an individual layer or for the service itself, which will return the current start and end times of available data, in epoch time format (milliseconds since 00:00 January 1, 1970). To see an example, click on the "Return Updates" link at the bottom of the REST Service page under "Supported Operations". Refer to the ArcGIS REST API Map Service Documentation for more information.
  2. Issue an Identify (ArcGIS REST) or GetFeatureInfo (WMS) request against the proper layer corresponding with the target dataset. For raster data, this would be the "Image Footprints with Time Attributes" layer in the same group as the target "Image" layer being displayed. For vector (point, line, or polygon) data, the target layer can be queried directly. In either case, the attributes returned for the matching raster(s) or vector feature(s) will include the following:
    • validtime: Valid timestamp.
    • starttime: Display start time.
    • endtime: Display end time.
    • reftime: Reference time (sometimes referred to as issuance time, cycle time, or initialization time).
    • projmins: Number of minutes from reference time to valid time.
    • desigreftime: Designated reference time; used as a common reference time for all items when individual reference times do not match.
    • desigprojmins: Number of minutes from designated reference time to valid time.
  3. Query the nowCOAST™ LayerInfo web service, which has been created to provide additional information about each data layer in a service, including a list of all available "time stops" (i.e. "valid times"), individual timestamps, or the valid time of a layer's latest available data (i.e. "Product Time"). For more information about the LayerInfo web service, including examples of various types of requests, refer to the nowCOAST™ LayerInfo Help Documentation

References



Map Name: NOAA NOS Lake Michigan Operational Forecast System (LMOFS) Forecast Guidance (Time Enabled)

Legend

All Layers and Tables

Dynamic Legend

Dynamic All Layers

Layers: Description:

Copyright Text: NOAA/NOS/OCS nowCOAST, NOS/CSDL/MMAP, NOS/CO-OPS, OAR/GLERL, Ohio State University and NWS/NCEP/NCO

Spatial Reference: 102100  (3857)


Single Fused Map Cache: false

Initial Extent: Full Extent: Time Info: Units: esriMeters

Supported Image Format Types: PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP

Document Info: Supports Dynamic Layers: true

MaxRecordCount: 1000

MaxImageHeight: 4096

MaxImageWidth: 4096

Supported Query Formats: JSON, AMF, geoJSON

Min Scale: 0

Max Scale: 0

Supports Datum Transformation: true



Child Resources:   Info   Dynamic Layer

Supported Operations:   Export Map   Identify   Find   Return Updates