On Mon, Dec 10, 2012 at 5:08 AM, Phil Scadden wrote:
> >The spec has the writer name on the cover... oddly enough, it seems
> this spec was made
> >by a single person/company alone (first of the kind I see regarding
> OGC specs).
>
> Sounds like a broken specification process to me. No way to a
>The spec has the writer name on the cover... oddly enough, it seems
this spec was made
>by a single person/company alone (first of the kind I see regarding
OGC specs).
Sounds like a broken specification process to me. No way to appeal?
>Thought as much. Still thinking of ways to make the "l
On Sun, Dec 9, 2012 at 9:55 PM, Phil Scadden wrote:
> Ugly! So who worked out the WMS-E/O specification??
The spec has the writer name on the cover... oddly enough, it seems this
spec was made
by a single person/company alone (first of the kind I see regarding OGC
specs).
> I particularly lik
Ugly! So who worked out the WMS-E/O specification?? I particularly like
the idea of a flag though that allows layer group content to be exposed
in the getcaps.
Notice: This email and any attachments are confidential. If received in error
please destroy and immediately notify us. Do not copy or
Hi,
parallel to WCS 2.0 and its EO extension (that will be worked on in 2013)
we are also
looking into supporting WMS EO.
The WMS EO adds some requirements on top of the usual WMS 1.3, in
particular,
it demands that earth observation product are presented in a particular
way in the capabilities do
