geowolf wrote > > That works once things are configured, but how does a user configure > dimensions from the GUI or from REST config, which mind, are the > only supported configuration mechanisms? (you directly writing the files > is not a supported way, the on disk file format can and will change > without > warning). > Can you clarify regarding the REST config for the coverage.xml file - I know the user (i.e. coverage provider) does not directly write the file, but I thought they directly specified the metadata entries as XML elements. In which case they can simply use a dimensionInfo element - or lack thereof - to indicate whether a particular metadata entry is to be treated as a dimension. Or is there another way to specify metadata in the REST config that I'm not aware of, which would require additional code changes to support custom dimensions?
geowolf wrote > > The GUI must have a way to list the available dimensions, out of the > canonical > ones, and allow the user to enable them. > > An acceptable approach is to mimick the existing metadata keys: > > /** > * The time domain (comma separated list of values) > */ > public static final String TIME_DOMAIN = "TIME_DOMAIN"; > > /** > * Time domain resolution (when using min/max/resolution) > */ > public static final String TIME_DOMAIN_RESOLUTION = > "TIME_DOMAIN_RESOLUTION"; > > /** > * If the time domain is available (or if a min/max/resolution > approach > has been chosen) > */ > public static final String HAS_TIME_DOMAIN = "HAS_TIME_DOMAIN"; > > /** > * The time domain max value > */ > public static final String TIME_DOMAIN_MAXIMUM = > "TIME_DOMAIN_MAXIMUM"; > > /** > * The time domain min value > */ > public static final String TIME_DOMAIN_MINIMUM = > "TIME_DOMAIN_MINIMUM"; > > For a custom dimensions we could have the following keys: > CUSTOM_DIMENSIONS (a comma separated list of the dimensions) > <MYDIMENSION>_TYPE (Date,Number,String?) > > HAS_<MYDIMENSION>_DOMAIN > <MYDIMENSION>_DOMAIN (the only solution for string dimensions) > <MYDIMENSION>_RESOLUTION (makes sense only for numeric/time) > <MYDIMENSION>_MINIMUM (makes sense only for numeric/time) > <MYDIMENSION>_MAXIMUM (makes sense only for numeric/time) > I agree with this approach. Just to clarify: this amplifies but does not conflict with the proposal described in my previous posts, correct? So, besides developing the tests you described - and assuming I were not inclined to build the GUI (which I appreciate your saying I would not necessarily be responsible for!), can you tell me what the next step(s) would be to getting this officially submitted? Thanks, Mike -- View this message in context: http://osgeo-org.1560.n6.nabble.com/Modification-to-support-custom-dimensions-for-coverage-layers-tp4474094p4500433.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
