When configuring the TDS 5 catalog to expose the WMS service on a GRIB2 dataset containing u/v vector component variables, ncWMS2 does not generate a combined/derivative vector field layer as it should, per ncWMS2 documentation, even though the variable names conform to the expected convention.
I have reproduced this problem using both a simple <dataset>:
To my knowledge, this issue only seems to affect GRIB2 datasets. TDS 5 + ncWMS2 was successful in visualizing similar u/v component variables into a vector field when a CF-compliant NetCDF was used with a <featureCollection featureType="FMRC">.
The sample GRIB2 files I used were from NOAA/NWS/NCEP Global Forecast System (GFS), which can be downloaded from the NCEP FTP server in subdirectories of [ftp://ftp.ncep.noaa.gov/pub/data/nccf/com/gfs/prod](), e.g. [ftp://ftp.ncep.noaa.gov/pub/data/nccf/com/gfs/prod/gfs.2017022800/gfs.t00z.pgrb2.0p25.f048]().
When configuring the TDS 5 catalog to expose the WMS service on a GRIB2 dataset containing u/v vector component variables, ncWMS2 does not generate a combined/derivative vector field layer as it should, per ncWMS2 documentation, even though the variable names conform to the expected convention.
I have reproduced this problem using both a simple
<dataset>
:as well as with a
<featureCollection>
:To my knowledge, this issue only seems to affect GRIB2 datasets. TDS 5 + ncWMS2 was successful in visualizing similar u/v component variables into a vector field when a CF-compliant NetCDF was used with a
<featureCollection featureType="FMRC">
.The sample GRIB2 files I used were from NOAA/NWS/NCEP Global Forecast System (GFS), which can be downloaded from the NCEP FTP server in subdirectories of [ftp://ftp.ncep.noaa.gov/pub/data/nccf/com/gfs/prod](), e.g. [ftp://ftp.ncep.noaa.gov/pub/data/nccf/com/gfs/prod/gfs.2017022800/gfs.t00z.pgrb2.0p25.f048]().