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 chang
On Fri, Feb 17, 2012 at 12:19 AM, Mike Benowitz
wrote:
> 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
> wh
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
distin
On Wed, Feb 15, 2012 at 10:54 PM, Mike Benowitz
wrote:
> Hello,
>
> I am working on some modifications to allow GeoServer to support dimensions
> other than TIME and ELEVATION for coverage layers, and I was wondering if
> this group could comment on whether this approach is reasonable, and also
>
Hello,
I am working on some modifications to allow GeoServer to support dimensions
other than TIME and ELEVATION for coverage layers, and I was wondering if
this group could comment on whether this approach is reasonable, and also
what it would take to get my changes included in the mainline GeoSe
