[Geoserver-users] Non-numeric elevations

OGC has published a BP for serving time/elevation dependent data
(https://portal.opengeospatial.org/files/?artifact_id=56394)

I am working on a project that is required to use GeoServer and also conform
to this BP which, according to the document, operates within the confines of
the WMS 1.3.0 spec.

We have some custom coverage plugins to handle our coverage needs (and are
looking at moving to gs-netcdf for some of our data), but one problem we are
running into is the assumption throughout the GeoServer WMS and possibly the
WCS that elevation values are always numeric. This makes it difficult for
'computed surface' elevations (i.e 'tropopause','surface') to even make it
to a coverage plugin where it can be handled appropriately. The WMS 1.3.0
spec does not appear to explicitly limit the elevation dimension to numeric
values, and the publication of the BP linked above further indicates that
non-numeric values should be possible (see section 6.4.2 in the document
linked above).

So my question is:

What is the position of the core GeoServer developers on non-numeric
elevations and the best practice linked above (is this even on your radar?)
Would there be interest in accepting patches/pull requests to allow non
numeric elevations or are you guys directly opposed to this?

Thanks in advance.

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Non-numeric-elevations-tp5171521.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

On Thu, Nov 6, 2014 at 5:01 AM, clifford.harms <clifford.harms@anonymised.com>
wrote:

So my question is:

What is the position of the core GeoServer developers on non-numeric
elevations and the best practice linked above (is this even on your radar?)
Would there be interest in accepting patches/pull requests to allow non
numeric elevations or are you guys directly opposed to this?

Willing to accept for sure I believe?

The current design is done as is because we haven't seen examples of non
numeric elevations yet, or have not needed them.

See the contribution guidelines about what we need in order to accept a pull
request: https://github.com/geoserver/geoserver/blob/master/CONTRIBUTING.md

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 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.

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