Hey all,
I think I stumbled across a bug in the time & elevation dimension handling of 
the NetCDF-out extension.  Our source data contains elevations in Pascals and 
so we configured the elevation dimension accordingly under the "Dimensions" 
tab.  When I execute a DescribeCoverage request for the coverage, the Elevation 
domain is correctly labled with uom="Pa".  However, when I execute a 
getCoverage request, the response data defines the elevation units as "m".  
Looking through the source code I think the bug may be caused by something as 
trivial as the capitalization (or lack thereof) used for the enabledDimensions 
key in org.geoserver.wcs2_0.response.WCSDimensionsSubsetHelper.java.  The 
"setupDimensions()" method calls "setupDimensionBean()" for both time & 
elevation dimensions using all caps.  As I step through the code in the 
debugger, my enabledDimensions map contains both "time" and "elevation" as 
lower case keys.  The result is that the dimension is not retrieved from the 
map of enabledDimensions and the "fallback" case is hit which uses default 
values for unit type and symbol.

I have tried modifying the coverage.xml to use capital names for time & 
elevation dimensions, but this causes GeoServer to ignore the dimensions 
altogether.  Am I configuring my GeoServer incorrectly or is this an actual bug?

Also, and this is a slightly unrelated question, is there a way to provide 
additional attributes to a dimensions output?  As stated before, my source data 
contains elevation info in Pascals.  I would like to output the following 
attributes under my elevation dimensions if possible:
positive = "down"
long_name = "Isobaric surface"
standard_name = "air_pressure"

Thanks,

Kevin M. Weiss
Software Engineer
CRITICAL NETWORKS / HARRIS CORPORATION
harris.comĀ  / [email protected]



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to