Re: GMU WCS Server supports netCDF output

NOTE: The galeon mailing list is no longer active. The list archives are made available for historical reasons.

On 8/25/05, yliu5@xxxxxxx <yliu5@xxxxxxx> wrote:
    getCoverage (9.6M bytes)
http://data.laits.gmu.edu/cgi-bin/tsunami/wcs100?version=1.0.0&service=WCS&request=getCoverage&coverage=/data4/TSUNAMI/L71131056_05620041229_B10.hdf:Grid:L71131056_05620041229_B10:L71131056_05620041229_B10&crs=EPSG:32647&bbox=23400,534000,267000,747000&resx=300&resy=300&format=netCDF

Yang Liu,

The ncdump of this result looks like:

netcdf wcs100 {
dimensions:
       xdim = 813 ;
       ydim = 711 ;
variables:
       double xdim(xdim) ;
               xdim:standard_name = "projection_x_coordinate" ;
               xdim:units = "m" ;
       double ydim(ydim) ;
               ydim:standard_name = "projection_y_coordinate" ;
               ydim:units = "m" ;
       int projection ;
               projection:grid_mapping_name = "transverse_mercator" ;
               projection:scale_factor_at_central_meridian = 0.9996 ;
               projection:longitude_of_central_meridian = 99 ;
               projection:latitude_of_projection_origin = 0 ;
               projection:false_easting = 500000 ;
               projection:false_northing = 0 ;
       double lon(ydim, xdim) ;
               lon:standard_name = "longitude" ;
               lon:units = "degrees_east" ;
               lon:long_name = "longitude" ;
       double lat(ydim, xdim) ;
               lat:standard_name = "latitude" ;
               lat:units = "degrees_north" ;
               lat:long_name = "latitude" ;
       byte L71131056_05620041229_B10(ydim, xdim) ;
               L71131056_05620041229_B10:long_name
"L71131056_05620041229_B10" ;
               L71131056_05620041229_B10:coordinates = "lat lon" ;
               L71131056_05620041229_B10:grid_mapping = "projection" ;

// global attributes:
               :institution = "LAITS, GMU" ;
               :Conventions = "CF-1.0" ;
...

Is the set of projection parameters standard? Currently the GDAL NetCDF
driver does not seem to support your coordinate system conventions. In fact, I find it odd that you list projection parameters but you don't
give any bounds or other information about the image in that projection.
I think we need a way of encoding the projected origin and offset
vector information in the netcdf result.  You obviously have it for
generating the coverage description.
Best regards,

--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam@xxxxxxxxx
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent


  • 2005 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the galeon archives: