[Geoserver-devel] Missing WCS 1.0.0 Custom Dimension

Hi,

If memory serves me well

“OGC Web Coverage Service (WCS) Specification

Version 1.0.0 (Corrigendum) – OGC Document No. 05-076

Grid coverages have a domain comprised of regularly spaced locations along the 1, 2, or 3 axes of a spatial coordinate reference system. Their domain may also have a time component, which may be regularly or irregularly spaced. A coverage with a homogeneous range set defines, at each location in the domain, either a single (scalar) value (such as elevation), or a series (array / tensor) of values all defined in the same way (such as brightness values in different parts of the electromagnetic spectrum).”

This text is about the same in all WCS 1.0.x and 1.1.x versions so 1, 2, or 3 dimensions and possibly time as fourth dimension should be supported. But standards do not say anything about “custom dimensions”. What are they, are they something Geoserver specific or something new introduced with WCS 2.x?

-Jukka Rahkonen-

Andrea Aime wrote:

···

On Thu, Jun 11, 2015 at 8:25 PM, Marks, David <David.Marks@…4153…> wrote:

In my current GeoServer project, we have a custom dimension that shows up and can be queried against in WMS 1.1.1 and 1.3.0, as well as WCS 2.0.1. But for some reason, none of the layers even display the dimension when viewed via getCapabilities or describeCoverage using WCS 1.0.0.

Anyone able to think of a reason why the custom dimension would just be missing entirely from WCS 1.0.0 and, if so, how to add it back in?

If memory serves me well, WCS 1.0 is limited to support ELEVATION, there is no support for TIME nor for any

custom dimension.

I believe the limit is in the protocol itself, but I may be wrong

Cheers

Andrea

==

GeoServer Professional Services from the experts! Visit

http://goo.gl/it488V for more information.

==

Ing. Andrea Aime

@geowolf

Technical Lead

GeoSolutions S.A.S.

Via Poggio alle Viti 1187

55054 Massarosa (LU)

Italy

phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

http://www.geo-solutions.it

http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.


​It's possible the custom dimensions are a Geoserver specific feature, as I also don't find much mention of them within the standards themselves.

This Geoserver test (https://github.com/geoserver/geoserver/blob/2.6.3/src/wcs1_0/src/test/java/org/geoserver/wcs/DynamicDimensionsTest.java​\) seems to be querying a WCS 1.0.0 layer using a custom dimension named wavelength​ and leads me to believe the custom dimensions I've setup should work within WCS 1.0.0 however. As I said, they seem to function correctly in WMS 1.1.1 and 1.3.0 as well as WCS 2.0.1, just now WCS 1.0.0 (where they're just wholly missing from all layer descriptions).

Thanks,

David Marks

________________________________
From: Rahkonen Jukka (MML) <jukka.rahkonen@...4189...>
Sent: Friday, June 12, 2015 2:39 AM
To: Marks, David
Cc: Geoserver-devel
Subject: Re: [Geoserver-devel] Missing WCS 1.0.0 Custom Dimension

Hi,

If memory serves me well

“OGC Web Coverage Service (WCS) Specification
Version 1.0.0 (Corrigendum) – OGC Document No. 05-076

Grid coverages have a domain comprised of regularly spaced locations along the 1, 2, or 3 axes of a spatial coordinate reference system. Their domain may also have a time component, which may be regularly or irregularly spaced. A coverage with a homogeneous range set defines, at each location in the domain, either a single (scalar) value (such as elevation), or a series (array / tensor) of values all defined in the same way (such as brightness values in different parts of the electromagnetic spectrum).”

This text is about the same in all WCS 1.0.x and 1.1.x versions so 1, 2, or 3 dimensions and possibly time as fourth dimension should be supported. But standards do not say anything about “custom dimensions”. What are they, are they something Geoserver specific or something new introduced with WCS 2.x?

-Jukka Rahkonen-

Andrea Aime wrote:

On Thu, Jun 11, 2015 at 8:25 PM, Marks, David <David.Marks@...4153...<mailto:David.Marks@…4153…>> wrote:
In my current GeoServer project, we have a custom dimension that shows up and can be queried against in WMS 1.1.1 and 1.3.0, as well as WCS 2.0.1. But for some reason, none of the layers even display the dimension when viewed via getCapabilities or describeCoverage using WCS 1.0.0.

Anyone able to think of a reason why the custom dimension would just be missing entirely from WCS 1.0.0 and, if so, how to add it back in?

If memory serves me well, WCS 1.0 is limited to support ELEVATION, there is no support for TIME nor for any
custom dimension.
I believe the limit is in the protocol itself, but I may be wrong

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it/&gt;
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

-------------------------------------------------------

On Fri, Jun 12, 2015 at 8:32 PM, Marks, David <David.Marks@anonymised.com>
wrote:

​It's possible the custom dimensions are a Geoserver specific feature, as
I also don't find much mention of them within the standards themselves.

They are foreseen by the WMS standard, GeoServer exposes them in other
protocols as well (when possible, and/or when we
had time to work on do that).

This Geoserver test (
https://github.com/geoserver/geoserver/blob/2.6.3/src/wcs1_0/src/test/java/org/geoserver/wcs/DynamicDimensionsTest.java​\)
seems to be querying a WCS 1.0.0 layer using a custom dimension named
wavelength​ and leads me to believe the custom dimensions I've setup should
work within WCS 1.0.0 however. As I said, they seem to function correctly
in WMS 1.1.1 and 1.3.0 as well as WCS 2.0.1, just now WCS 1.0.0 (where
they're just wholly missing from all layer descriptions).

I can confirm the code in the WCS 1.0 GetCoverage paths can handle all
extra dimensions:
https://github.com/geoserver/geoserver/blob/master/src/wcs1_0/src/main/java/org/geoserver/wcs/DefaultWebCoverageService100.java#L323

DescribeCoverage wise, Jukka is right, time is also available, and I can
see code to write a
wcs:temporalDomain element to describe it in the DescribeCoverage response,
if it's available and enabled.

There is no custom dimension handling indeed in Describe, and no place
where it could be added in the DescribeCoverage 1.0 response.
In 2.0 we can because there is an extension element that can contain
xs:Any, which allows us to put GeoServer specific extensions
in the response without breaking clients.

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------