[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDV #PPS-393493]: TDS WMS for GFS CONUS 191km not projected correctly

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [IDV #PPS-393493]: TDS WMS for GFS CONUS 191km not projected correctly
  • Date: Wed, 05 Aug 2009 06:50:05 -0600
Hi Ethan-

> Full Name: Ethan Davis
> Email Address: address@hidden
> Organization: Unidata
> Package Version: 2.7u2 build date:2009-08-04 07:07 UTC
> Operating System: Windows XP
> Hardware: Java: home: C:\Program Files\Java\jre6 version: 1.6.0_13 j3d:1.5.2 
> fcs (build4)
> Description of problem: Hi,
> 
> Here's the GetCapabilities URL:
> 
> http://motherlode.ucar.edu:8080/thredds/wms/fmrc/NCEP/GFS/CONUS_191km/files/GFS_CONUS_191km_20090803_1200.grib1?service=WMS&version=1.3.0&request=GetCapabilities
> 
> I put it in the "Catalog" selector and it opened fine. I selected the 
> "Temperature" layer and the data was displayed but it looks like the 
> projection is not interpreted correctly.

The projection is based on the bounding box in the capabilities document.  Here 
is the request for one of these images:

url:http://motherlode.ucar.edu:8080/thredds/wms/fmrc/NCEP/GFS/CONUS_191km/files/
GFS_CONUS_191km_20090803_1200.grib1?version=1.3.0&request=GetMap&Styles=&format=
image/png&SRS=CRS:84&CRS=CRS:84&Layers=Pressure_reduced_to_MSL&BBOX=-141.1426607
314765,7.1132244386297785,-17.641385589402987,34.93241126350566&width=681&height
=600&reaspect=false

The capabilities document lists:

<BoundingBox CRS="CRS:84" minx="-141.1426607314765" maxx="-17.641385589402987" 
miny="7.1132244386297785" maxy="34.93241126350566"/>

I'm not sure what CRS:84 relates to in terms of a projection, but the IDV 
uses the min/max x/y for the request.  When you click on the link in the 
chooser, you'll see that the region highlighted corresponds to the bounds 
above. I don't think we handle anything but rectillinear images, though.

I'm guessing that this is a problem with the server's interpretation of the 
projection instead of the IDV's, since this grid covers Alaska.

Let me know if you need more help tracking this down.

Don



Ticket Details
===================
Ticket ID: PPS-393493
Department: Support IDV
Priority: Normal
Status: Open