Andrea, Thanks for your reply. Regarding the three concerns you expressed:
1) I think distinguishing dimension metadata from other random metadata can be handled without changing the API or relying on a naming convention. From what I can tell, dimension entries in the coverage.xml file are distinguished by the dimensionInfo element, which gets translated to a DimensionInfo (or more specifically, org.geoserver.catalog.impl.DimensionInfoImpl) value in the corresponding entry in the MetadataMap received by DimensionHelper. The modified DimensionHelper should be able to scan the MetadataMap for all entries whose values are assignable to type DimensionInfo, and process only those entries as dimensions. 2) It's true that the core logic would not be able to assume the data type for non-standard dimensions, but this does not seem particularly problematic. We could include processing to recognize whether strings are numeric and if so convert them to Double, or whether they are in a recognizable date/time format and if so convert them to Date. In any case, it seems reasonable that values that are not in a recognized format would just be treated as strings, and the interpretation left to the custom plugin/client. 3) I believe the modified DefaultWebCoverageService100.getCoverage method can handle custom dimensions regardless of whether they are numeric. As it is now, the axis subset list items (created from the axisSubset elements in the request document) that are processed by this method are of type TypedLiteralType, which specifies all values as strings. The ELEVATION processing assumes that the values can be parsed to numbers, but I don't see anything requiring the custom dimension processing to make such an assumption. -- View this message in context: http://osgeo-org.1560.n6.nabble.com/Modification-to-support-custom-dimensions-for-coverage-layers-tp4474094p4478043.html Sent from the GeoServer - Dev mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
