[THREDDS #FMI-790390]: THREDDS WMS Server on http://motherlode.ucar.edu:8080/thredds/wms/

Hi Richard,

Sorry about that. The SERVICE parameter requirement slipped in during the 
integration of the  ncWMS code into the TDS. I have fixed the problem in our 
code. It should be fixed on our motherlode server in a few days.

Ethan 

> I know the WMS Server on motherlode is "considered experimental" but I
> wondered if anyone had mentioned that it appears not to be fully OGC
> compliant?
> 
> Specifically according to the OGC specification (v. 1.3.0 -
> http://portal.opengeospatial.org/files/?artifact_id=14416) the SERVICE
> parameter is only required for a GetCapabilities() request but the
> service on motherlode requires SERVICE for a GetMap() request.
> 
> Attempts to submit a WMS GetMap() request without the SERVICE parameter
> yields the following response:
> 
> <?xml version="1.0" encoding="UTF-8" ?>
> -
> <http://motherlode.ucar.edu:8080/thredds/wms/fmrc/NCEP/GFS/Global_onedeg
> /runs/NCEP-GFS-Global_onedeg_RUN_2009-05-15T00:00:00Z?version=1.3.0&requ
> est=GetMap#>  <ServiceExceptionReport version="1.3.0"
> xmlns="http://www.opengis.net/ogc";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://www.opengis.net/ogc
> http://schemas.opengis.net/wms/1.3.0/exceptions_1_3_0.xsd";>
> <ServiceException>Must provide a value for parameter
> SERVICE</ServiceException>
> </ServiceExceptionReport>
> 
> This means that any client applications that do conform to the OGC
> standard cannot consume data via this implementation of the WMS
> interface.
> 
> Are there any plans to correct the problem?
> 
> Thanks,
> 
> Richard



Ticket Details
===================
Ticket ID: FMI-790390
Department: Support THREDDS
Priority: Normal
Status: Closed